BeLight 0.22 beta 8 released

[nexus]

Originally posted by Palikrovol
Why not both? I mean "Radio (40/50 kbps)", "Streaming (50/70", and so on.

And i think all the presets for all the speakers config. would be better (tape, radio, internet and streaming for 2.0 and 5.1 in HE)

Anyway it looks great.

Go on with the GUI Kurtnoise13

DITO

Bug: Encoding priority is not saved.

[Kurtnoise]

Originally posted by Longinus
Just one small bug I found...
The LAME alt-preset for 128 CBR is not right, it's using ABR instead..
lame( --alt-preset 128 ) instead of lame( --alt-preset cbr 128 ).

Yep...thanks for the bug report.

Originally posted by dOpiate
where is the option to turn on the two-pass for SSRC in your prog???

Sorry, BeLight haven't SSRC 2-pass option...But you can check "View & Edit BeSweet command line", then delete the lines and copy & paste you own command. It should work great.

Originally posted by Palikrovol
Why not both? I mean "Radio (40/50 kbps)", "Streaming (50/70", and so on.

And i think all the presets for all the speakers config. would be better (tape, radio, internet and streaming for 2.0 and 5.1 in HE)

Ok for both but I'm not sure about bitrate range for VBR/5.1. If someone could be tested the different presets quality...could be interesting.

Originally posted by nexus
Bug: Encoding priority is not saved.

not a bug yet...it's not implemented. BTW, the different priorities encoding work well ??

[nexus]

Originally posted by Kurtnoise13
not a bug yet...it's not implemented. BTW, the different priorities encoding work well ?? [/B]

I think "normal" should work (because it's standard), I'll test with "idle" and "High" and post the result later.

Another bug (?) postet in the german Doom9 forum: You can't change normalization method, it's always PostGain (only AAC).

Edit: Encoding priority: It seems that it doesn't work correctly. I started BeSweet (idle) and VDub (normal), BeSweet uses 20% CPU, VDub the rest. It should be 0% for BeSweet, I think.

Edit2: Same with "normal, BeSweet: 20%, VDub rest.
I guess priority only affect on BeLight, not on besweet.exe

[Kurtnoise]

Thanks for the tests.

Originally posted by nexus
Another bug (?) postet in the german Doom9 forum: You can't change normalization method, it's always PostGain (only AAC).

It's not a bug...Read the AAC FAQ (n°15). That's why I choose PostGain.

[nexus]

Originally posted by Kurtnoise13
It's not a bug...Read the AAC FAQ (n°15). That's why I choose PostGain. [/B]

But HybridGain is not recommended at the moment, so why can't I choose PreGain?

[JoeBG]

Originally posted by Kurtnoise13
It's not a bug...Read the AAC FAQ (n°15). That's why I choose PostGain. [/B]

You mean PreGain

"15. What gain setting should I use to encode AAC with BSN/Oagmachine?

Eventhough BeSweet/Bsn has implemented Hybrid gain, there are no Directshow filters capable of using the hybrid gain information at this time. So it is not recommended at the moment. Instead use normalization or pregain"

Pregain works fine with the normal GUI and I´m really looking at every release of your GUI if it works wit AAC. In the moment it does not ;(

[Kurtnoise]

PostGain ( -G 1) is equivalent to Normalization ( --maximize)...but I can manage to switch between PreGain & Normalization if you want.

[JoeBG]

Originally posted by Kurtnoise13
PostGain ( -G 1) is equivalent to Normalization ( --maximize)...but I can manage to switch between PreGain & Normalization if you want.

This would be great, thank you very much. Most people prefer Pre Gain for AAC Encoding and not the Azid method.

[OMINUS]

there seems to be a bug when i try to encode from .ac3 to .mp3
when i click start ,using the belight's default settings,an error message appears sayin that i must have the aacenc32.dll and aac.dll in the belight directory in order to transcode my file in aac!!
(i have put the belight in the besweet folder)

[therealjoeblow]

Originally posted by Kurtnoise13


BTW, I need you to have your point of view. I'm preparing some Presets for transcode processing. That's why I would like to have some feedbacks or suggestions for these things.

I post 2 pictures :
snip)...

to see how we can manage the different presets. So, what do you think about that ? Is it ok or not ?? Thanks guys ....

I prefer the kb/s descriptions - 'radio' and 'tape' just seem too subjective to me to mean anything.

[nFury8]

Originally posted by OMINUS
there seems to be a bug when i try to encode from .ac3 to .mp3
when i click start ,using the belight's default settings,an error message appears sayin that i must have the aacenc32.dll and aac.dll in the belight directory in order to transcode my file in aac!!
(i have put the belight in the besweet folder)

I got the same error message when i tried to encode AC3 to 6 wavs for this latest version 0.20b2.

[Kurtnoise]

@ nFury8 & OMINUS : yes...sorry for this stupid bug. I had forgotten to uncheck something in my code...

[Kurtnoise]

Originally posted by therealjoeblow
I prefer the kb/s descriptions - 'radio' and 'tape' just seem too subjective to me to mean anything.

Yes...that's why I chose to put both information. Everyone will be happy..

[Brother John]

Originally posted by Kurtnoise13
PostGain ( -G 1) is equivalent to Normalization ( --maximize)

That's not correct. In fact PreGain is equivalent to --maximize.

PreGain and maximize use a 2-pass approach. First the file is scanned for the peak sample, then the appropriate gain value is calculated and applied to the file while transcoding.

PostGain looks for the peak value while transcoding and afterwards applies a gain tag to the file. The actual normalizing is done by the decoder, that needs to read the gain tag.

HybridGain uses both gain methods depending on source material. First a fixed pregain value is added to the file (0db for 2.0 sources, 10db for 5.1 sources). While transcoding the still missing rest gain value ist looked for using PostGain and stored in the gain tag.

Unfortunately aac decoders can't read gain tags, so an aac file encoded with post gain or hybrid gain will have a too low volume. For that reason PreGain "-ota( -g max )" or --mazimize should be used for aac.

edit: wrong command line for pregain corrected

[Taurus]

Originally posted by Brother John
Unfortunately aac decoders can't read gain tags, so an aac file encoded with post gain or hybrid gain will have a too low volume. For that reason PreGain "-ota( -g max )" or --mazimize should be used for aac.

Thank you for clearing up the sky for me. Always wondered why hybrid and post gain do not show the desired effect on aac's.

Cheers

Taurus

[rondo]

Hope this bug (at least I think it's one) hasn't already been corrected, as I can't test it in v20 cos of the Ominus issue.

I'm coding to MP2.

If you check the VBR Mode box & then uncheck it again, the option remains set at VBR, & the program needs to be restarted to unset it again.

Regards

[Kurtnoise]

It has been corrected with the latest beta.


I'll post a new build tonight...

[Kurtnoise]

Finally...I've got a free time this afternoon. So, 0.20 beta 3 is out.

changelog :

- Enhancements for Presets.
- If AAC output format is chosen, then PreGain or normalization is available. In other word, Hybrid Mode is not present for this format.
- if "-- BeSweet List File --" is chosen, then *.lst and *.mux files can be loaded.
- bug correction if the dll from Nero aren't available in the BeLight directory.

[JoeBG]

@ Kurtnoise

It works, thank you very much. Now a lot of manuels have to get changed

[Kurtnoise]

Hi guys,

Before to add new things, I managed the 0.20 Final.



Changes from 0.19 to 0.20 :

- Added : Presets.
- Added : Bitrate equivalence for Vorbis Q Mode.
- Added : Possibility to select either lst or mux files in the input list.
- Fixed : PreGain available for normalization if AAC is chosen.
- Fixed : Languages can be saved now.
- Fixed : Plugins part when it's saved.
- Fixed : Some problems with LFE and Output Mode in Azid Settings.