Hi again, > >> $ curl -o foo.mpc http://server:3689/rsp/stream/42 > >> > >> and replace 42 with the id of the file. > >> > >> You can then check what gets sent out by mt-daapd, and you'll probably > >> find it's your .mpc file (sha1sum should match, too).
Ok, I have done this test, and it is indeed the unchanged .mpc file: chr...@baba:~$ curl -o foo.mpc http://baba.sadnet:3689/rsp/stream/12122 % Total % Received % Xferd Average Speed Time Time Time Dload Upload Total Spent Left 100 6164k 100 6164k 0 0 26.8M 0 --:--:-- --:--:-- --:--:-- chr...@baba:~$ ll -rw-r--r-- 1 chrisc chrisc 6312787 2009-04-29 17:13 foo.mpc chr...@baba:~$ cmp foo.mpc /archive/Music/Ratt/1984-Out\ Of\ The\ Cellar/01-Wanted\ Man.mpc chr...@baba:~$ ... shows that there are no differing bytes. > Transcoding is done through ffmpeg (libavcodec, libavformat). If > ffmpeg supports that format, mt-daapd will be available to transcode > from that format. If ffmpeg doesn't support it or ffmpeg is buggy, > then mt-daapd is impacted directly. So should I reassing this as a bug in libavcodec or libavformat? Versions are as per the original bug report. Thanks, CC -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
