(Fixed) Flac to ogg transcode breeds ffmpeg processes
Posted: Fri Apr 15, 2011 12:01 amStreaming from Ubuntu 10.10 64b to Android. Using the following transcode command:
ffmpeg -loglevel error -v 0 -i %s -f ogg -vn -acodec libvorbis -ar 44100 -aq 4 -ac 2 -map_metadata 0:0 -
Had worked, but now it hangs -- the Subsonic log shows multiple starts of the transcode process for the same track <edited to remove log clip>
and top shows a screenfull of ffmpeg processes. Any ideas where to begin troubleshooting this one?
Solution: More troubleshoot made clear that it wasn't ffmpeg itself -- command runs fine from cl, and similar problems popped up if I tried to steam the file after a successful conversion to ogg outside of Subsonic. The flac also transcoded fine to a web browser interface, which suggested a problem with the Android client.
The files in question had rather long titles and filenames, so I retagged and renamed the files, at which point on-the-fly transcoding in Subsonic worked again.
My guess at this point is that there is something about an odd and/or overlong file name or title tag that causes the Android client to start looping, sending one request after another to the server rather than just crashing.
ffmpeg -loglevel error -v 0 -i %s -f ogg -vn -acodec libvorbis -ar 44100 -aq 4 -ac 2 -map_metadata 0:0 -
Had worked, but now it hangs -- the Subsonic log shows multiple starts of the transcode process for the same track <edited to remove log clip>
and top shows a screenfull of ffmpeg processes. Any ideas where to begin troubleshooting this one?
Solution: More troubleshoot made clear that it wasn't ffmpeg itself -- command runs fine from cl, and similar problems popped up if I tried to steam the file after a successful conversion to ogg outside of Subsonic. The flac also transcoded fine to a web browser interface, which suggested a problem with the Android client.
The files in question had rather long titles and filenames, so I retagged and renamed the files, at which point on-the-fly transcoding in Subsonic worked again.
My guess at this point is that there is something about an odd and/or overlong file name or title tag that causes the Android client to start looping, sending one request after another to the server rather than just crashing.