AGK test request: mono encoding

[chilled]

I cant try new 1.87 beta from Auto GK for the moment so I ask for testing (and reporting...) on the mono encoding issue that has been recently discussed on previous betas:

-inputs AC3 2.0 (assuming original source is mono) AND 1.0 (pure mono). optionally real 2.0 surround or stereo and 5.1 (wow I hope nobody encodes this as mono...)
-outputs MP3 (mono hidden option - assistant) both CBR and VBR (specially that one). In the past I had problems with low bitrate VBR enconding (64, 80 and 96kbps -in the advanced tab- which means about 32, 40 and 48kbps in mono VBR mode reported by gspot.

thank you

[chilled]

btw Len0x, I also would like to know if output mp3 is always 44.1 (even when using low and high bitrate values) since this has been discussed recently

[len0x]

No, if bitrate goes below 48kbps per channel lame 3.96.1 will automatically resample it below 44KHz. High bitrates will still have original 48Khz...

P.S. however --resample 44.1 option always works in latest Lame (it wasn't before), so if/when AutoGK exposes audio parameters as an option then you should be able to control that manually.

[fewtch]

Originally posted by len0x
P.S. however --resample 44.1 option always works in latest Lame (it wasn't before), so if/when AutoGK exposes audio parameters as an option then you should be able to control that manually.
Oh please, if that ends up "when" instead of "if" I'll be very happy...

:thanks:

P.S. the more parameters you can expose on hidden screens for us "in between" folks (neither expert nor newbie) who prefer AutoGK is awesome... it could fill a niche for those who mostly want a quick/easy encode, yet sometimes would like to tweak lots of options...

[chilled]

as an "in-between" coder, I do totally agree with that, but I think it will definately always be better to have (more and more) hidden or advanced options (with check tabs like "force resampling to 44.1" or so -I dont ask for this one, just an example) rather than any kind of CLI-like option (that could just introduce the ability of the "in-between" coders to mess all the things up...).
So Len0x you see that AGK is not only preferred by newbies but also by us "in-betweeners" (ppl that could eventually use GK but will never get that sharpy results as experimented coders do -just because we do not want to be near-professional coders)