Thursday, September 22, 2005

problem transcoding AAC files to mp3

I am having a problem getting AAC files to work with Jinzora. By default, Jinzora attempts to transcode all AAC files into MP3 files. (Which I think is reasonable, as not many players can support AAC.

The command that it attempts to use to transcode the file is:

/usr/bin/mplayer -ao pcm:file=/dev/stdout "/data/music/Daft Punk/Discovery/Daft Punk-Discovery-10 - Voyager.m4a" | /usr/local/bin/lame -S --silent --quiet -h -m j -b 128 -f - > /tmp/test.mp3

This puts noise in the resulting mp3 file. Here is the first 100KB of the file that has the noise in it.

But if I do the two commands seperately, the resulting sound file sounds great. These commands work great:

/usr/bin/mplayer -ao pcm:file=/dev/stdout "/data/music/Daft Punk/Discovery/Daft Punk-Discovery-10 - Voyager.m4a" > /tmp/test.wav
/usr/local/bin/lame -S --silent --quiet -h -m j -b 128 -f /tmp/test.wav > /tmp/test.mp3

Here a sample of the transcode that worked perfectly

I haven't been able to find a solution for this, but I will keep looking

Technorati Tags: ,


  1. Why not try the two lines, with a ; between them. This should do one, then the other.

  2. This will not work from within Jinzora. Jinzora runs one command for the source format, and one for the destination format, and then it pipes the commands together. The '|' character is hard coded.
    Ideally, there would be a way to have the two commands piped together and have it work. I was think that if there was a way to change the buffering by the mplayer or lame


DIY Cloud Storage: A Step-by-Step Guide to Setting Up Nextcloud on Your Raspberry Pi

In this post, I'm going to walk you through the process of setting up Nextcloud on a Raspberry Pi using NextcloudPi . If you're loo...