Chris Carr <[email protected]> wrote: Hi,
> mt-daapd recognises .mpc files while it is scanning my library, and > offers them to clients, but does not actually stream them. I have > 2009-04-29 13:40:40 (b62d2b90): Session 0: Streaming file '03-Round And > Round.mpc' to 192.168.1.24 (offset 0) > 2009-04-29 13:40:44 (b62d2b90): Write error: Broken pipe That's your client closing the connection because it doesn't like the data it's getting. Which means the file is not getting transcoded. That can be trivially verified if you know the id of the file in the database, just do $ 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). > I assume the package has been built without the --enable-musepack Nope, it is, but --enable-musepack only enables the metadata parser for musepack files. The actual transcoding is done by ffmpeg, so that would be a case of ffmpeg not handling musepack. Try transcoding the file with ffmpeg to something else (mt-daapd transcodes to wav 44.1 kHz, stereo). Something as simple as $ ffmpeg -i file.mpc foo.wav should do. (what client are you using, btw?) JB. -- Julien BLACHE - Debian & GNU/Linux Developer - <[email protected]> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
