Hello Holger,
Thursday, August 31, 2000, 2:31:48 PM, you wrote:
HD> It's hard to come up with a good option dialog for RL, given the vast
HD> amount of options LAME has to offer. I think it's a good idea to put
HD> those settings in categories, however, I agree, it can get a bit
HD> unclearly...
I think this is not good way of handling things. If there are too
much options, there are too much options. If you decide to catalog
some of them as "advanced", some as "expert" and other with another
subjective label, it only complicates things even further.
30 options in 1 screen are less complicated than 30 options scattered
over 5 screens.
What I suggest, since lame will continuously develop and new options
will be added, is to simply handle things like this:
- 1 screen (oversight & clarity)
- in top, a (greyed out or so) continuous display of current command
line. I never understood why enabling this is an option.
- only a limited set of "core" options. stereo mode, bitrate, encoder
mode, delete after, and the most common flags. Just so you have a nice oversight of
options.
- a box to add non-common command line options.
- a flag to make lame only use that box, instead of adding the content
to current selected options.
This is, basically, the way lamebatch did things. In the long run
this seems to be the only managable way of constructing a frontend
imho: You simply see what's set, and you don't need to look 3 windows
back for some setting you also might need.
then, why no multithread? it'd be nice to update the to-be-encoded
list in one window while the encoding-box is somewhere else...
I had to press abort too often :(
just some suggestions ...
--
Best regards,
Roel mailto:[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
