You are here: Home » Reply

Reply To: ogg problem.. whatever

#5020

fizze
Participant

Right!
Finally some progress with my “huge” ogg files, thingy.

2007-03-24 12:48:37 (00342405): Session 0: Streaming file 'world_wide_20050109.ogg' to 192.168.1.112 (offset 0)
2007-03-24 12:48:37 (00342405): Executing /opt/sbin/mt-daapd-ssc.sh "/share/hdd/data/public/music/new/world_wide_20050109.ogg" 0 7065.000 "ogg"
2007-03-24 12:50:20 (00349805): Session 0: Streaming file 'world_wide_20041219.mp3' to 192.168.1.112 (offset 0)
2007-03-24 12:50:20 (00339404): Write error: Broken pipe
2007-03-24 12:50:20 (00339404): Finished streaming file to remote: 2195456 bytes
2007-03-24 12:50:22 (0034a004): Session 0: Streaming file 'world_wide_20050109.ogg' to 192.168.1.112 (offset 0)
2007-03-24 12:50:22 (0034a004): Executing /opt/sbin/mt-daapd-ssc.sh "/share/hdd/data/public/music/new/world_wide_20050109.ogg" 0 7065.000 "ogg"
2007-03-24 12:50:28 (0034ac04): Session 0: Streaming file 'world_wide_20041219.mp3' to 192.168.1.112 (offset 0)
2007-03-24 12:50:29 (00349805): Write error: Broken pipe

now, the ogg file is some88MB in sice. its a 2h recording of a radio broadcast. Now decoding this as a complete piece on the NSLU2 would take up a considerable amount of time.
When exactly does mt-daapd or wavstreamer start to stream? Does this really happen on the fly?
I guess that oggdec chokes because the slug lacks memory.

I guess a workaround for this could be to save the wav file in a temporary directory, or even save it at all, as suggested by someone with a patch earlier….

edit:
Although the log sais, that bytes were streamed to he client, the soundbridge doesnt actually play anything. It immediatly aborts, telling me unable to play content.