Comment 13 for bug 64905

Can confirm this behaviour in Gutsy with Sound-juicer. A workaround would be to install the ffmpeg-packages and editing the gstreamer-pipeline (in Sound-Juicer or by "gnome-audio-profile-properties") something like this:
"audio/x-raw-int,rate=44100,channels=2 ! lame name=enc quality=2 mode=0 vbr=4 vbr-quality=2 vbr-min-bitrate=192 ! ffmux_mpeg ! id3v2mux"

The important part to solve this isse is to use "ffmux_mpeg" then instead of "xingmux". (Though xingmux and xingheader seem both (!) to be broken in gutsy, because when using both of them, one is not able to active the profile at all. You can clikc activate, but it won't show up in the menu and therefore can't be selected. But this is another bug. The behaviour in feisty at the beginning, that you must have closed the profiles list before you could edit a profile seems to be fixed and has nothing to do with this new bug.)

It's sad, but also "ffmux_mpeg" produces corrupt lenght and bitrate tags/information when viewing the files with Rhythmbox or Nautilus. Though not often, but it happens. But this is a good workaround to the default behaviour, where every mp3 file in Rhythmbox has a totally crazy length information, e.g. a 3 minute track has 15 minutes etc.)

By the way, sometimes when using VBR mp3/lame bitrates are often shown wrong exactly as 32kb/s.

In comparision this bug (which is somehow related to the other ones mentioned) is quite annoying, though it affects standard apps like rhythmbox and sound-juicer and with the wrong length information you will also get into trouble making a CD with Serpentine out of a rhythmbox playlist, because Serpetine also uses the wrong track length informations and you won't be able to use the space on the audio CD in a proper way.

But try it with "ffmux_mpeg" so far.