[wishlist] add support for LAME presets on CD ripping

[Mario Abarca]

Binary package hint: banshee

LAME defines four MP3 encoding presets: medium, standard, extreme and insane. As documented in LAME man page, this presets are meant to be future-safe and transparent to the end user (no need for "AVR" or "kbps" technobable). This presets should appear in the LAME configuration dialog of Banshee. Also, the "Standard" preset should be set to default: it is designed to be both high quality and small sized.

[Victor Vargas (kamus)]

maybe this requirement is related to bug https://bugzilla.gnome.org/show_bug.cgi?id=633859

[Mario Abarca (knkillname)]

@Kamus I think this bugs are not related. The one you are referring to appeals to the experienced users who already encode mp3 comand-line style (and know AVB, CBR, ABR, ID3, ID3V2, KBPS, "lowpass filter", "replay gain" and other tech-words). On the other hand, this one appeals more to "human beings" by simplifying the UI with four well-tested presets (see http://wiki.hydrogenaudio.org/index.php?title=LAME ).

The presets description are well written in plain understandable English:
Medium: "This preset should provide near transparency to most people on most music."
Standard: "This preset should generally be transparent to most people on most music and is already quite high in quality."
Extreme: "If you have extremely good hearing and similar equipment, this preset will generally provide slightly higher quality than the standard mode."
Insane: "This preset will usually be overkill for most people and most situations, but if you must have the absolute highest quality with no regard to filesize, this is the way to go."

Also, just let me point out that this requirement is easy to implement:
Medium, Standard and Extreme presets are aliases for 5, 7 and 9 in the Banshees VBR quality setting.
The Insane preset is obtained by a constant bit rate of 320Kbps.

[Victor Vargas (kamus)]

I see, by the way, I have sent this requirement to upstream tracker so you can track and follow status of this issue at https://bugzilla.gnome.org/show_bug.cgi?id=651177