Comment 61 for bug 195483

Ok, now these opinions about differences between results or different testing tools are silmply useless.
Here we are searching for the cause of the bug and for the best solution to it.
The cause was a buggy/misused gstramer plugin "lame". Now developers rolled out "lamemp3enc", a better interface to the same library. All we need is that the sound-juicer Gstreamer pipeline is changed to use it.
So, which are the best default options? I don't know. But surely the optimal pipeline is the one i proposed above, taken from Maverick. (See gst-inspect lamemp3enc or my precedent message for reference)
There are no other questions. Let's speak about this one.