Comment 106 for bug 602934

(In reply to comment #93)
> I totally agree that the Quality method should be used. But, I think LRN had
> it right when he used a slider. We wouldn't be able to provide an accurate
> value if we tried to assign a bitrate to a specific quality value.
Of the three apps I know about, SUPER (using FFmpeg) and iTunes both use kbps
in a dropdown. Nero (as implemented in dBPowerAmnp which is a fringe app) uses
a slider, but indicates the approximate bit rate on the slider. I have not
tested if SUPER files produce the stated values in the dropdown.

The issue though as I see it is that users do the conversion to AAC in iTunes
or elsewhere because they can't figure out what our Quality slider will give
them. Also they don't want to bother with the large number of possible quality
choices that our slider presents.

The bit rate is only an indication anyway (I do think iTunes isn't clear enough
about that). Is it possible to take a dozen or less quality settings, but have
a dropdown for those indicating the quality then the bit rate range (exactly as
we do for MP3 VBR)? My concern with the slider is that it would have to be a
lot wider (and maybe a lot of work) to carry target bit rate information.