BeLight 0.22 beta 8 released

[Kurtnoise]

@video_magic : hehe, good to know. ;)

@vlad : I'll check it but by manually I'd say : with the mouse you can modify the width & heigth of BeLight.

[Vlad74]

@vlad : I'll check it but by manually I'd say : with the mouse you can modify the width & heigth of BeLight.

Unfortunately, no! The size of BL window I get on my monitor is unalterable with mouse - it is a problem!

[Kurtnoise]

Like I said I'll check it...Thanks for the bug report.

[aliumalik]

Hey Kurt would it be possible to add an option regarding the encoding thread's priority?

[Kurtnoise]

Check the options --> Priority in the Menu...;)

[Backflip]

Bit of a strange one, but anywho. I recently upgraded to the latest BeSweet, but now every time I close then reopen BeLight my language is set to Spanish, instead of English which I chose.

Also, just something I was wondering, but should I be able to select Variable bitrate mode - Normal and HE (High Efficeincy) AAC with Quality set to High and expect a Normal quality HE-aac file, or will it be LC-aac (auto-switch to LC?).

Foobar says the file is:
bitrate = 192
samplerate = 48000
channels = 6
aac_profile = HE AAC
codec = AAC
tool = Nero AAC Codec 3.2.0.15
----------
350754048 samples @ 48000Hz
File size: 176 273 088 bytes

Media Info says:
Format : MPEG4 at 193 Kbps
Length : 168 MiB for 2h 1mn 47s 450ms

Audio #0 : MPEG-4 AAC LC at 192 Kbps
Infos : channel(s), 48 KHz

Hhmm, I was just wondering about that because I've noticed in the Nero AAC encoder itself that you can only use a Variable bit rate setting of Normal :: High and only the LC profile.

[Kurtnoise]

Bit of a strange one, but anywho. I recently upgraded to the latest BeSweet, but now every time I close then reopen BeLight my language is set to Spanish, instead of English which I chose.
Works like a charm here..try to reinstall the last BeLight beta version.

Also, just something I was wondering, but should I be able to select Variable bitrate mode - Normal and HE (High Efficeincy) AAC with Quality set to High and expect a Normal quality HE-aac file, or will it be LC-aac (auto-switch to LC?).
Media Info doesn't detect the SBR flag (aka High Efficiency) in mp4 files. So there is no problem here. ;)

[tjdavis1138]

Trying to use the create mux file option. I have 6 wav's that I want to convert to a 5.1 ac3 file. Belight creates the mux file fine and the command line looks good, but when I try to start the process it obviously has a problem so I checked the log and this is what I have: Error 32: No input-data was found (wrong substream?)

Not sure what to do here. I created the wav's in vegas so I assume they are ok.

Thanks for any help or suggestions. :)

[LigH]

Not sure what to do here.
As usual:

Post the whole command line, and the content of the mux file.

[Kurtnoise]

In addition, mux input file is not supported as input file for the last betas.

[Backflip]

Think I know the reason why the language was reverting to Spanish. It was because I was closing the program after encoding had finished instead of clicking the green/white arrow. Think it only happens after the Transcoidng aborted error occurs.

[Paulcat]

I have some VCD's that I am converting to DVD's, and as my authoring software takes a long time to resample the audio from 44,100HZ to 48,000HZ so I wanted to do it with BeSweet/BeLight (I have BeSweet 1.5b30 and BeLight 0.22b4). However, when I select my file to alter (e.g. Audio.mp2) I cannot change the destination filename (e.g. NewAudio.mp2).

This is not an issue when changing filetype (e.g. to encode as AC3, the original file is re-encoded as Audio.ac3).

Is there a way around this? I tried to encode my audio as ac3 initially, but the final file was full of static for some reason, and as I was in a hurry, ended up letting my authoring program do the work, instead of finding the solution.

Is there a solution?

[Paulcat]

I tried again to convert mp2 to ac3 and again ended up with a file rife with static, like a poorly tuned radio. I then converted the mp2 to a stereo wav file, and then converted the wav file to ac3, which worked like a charm, AND it was louder than the first ac3 file (same volume as the mp2 and wav files)

I have had no trouble converting mp3 to ac3...

I am using BeSweet 1.5b30 and BeLight .22b4

Paul

[Kurtnoise]

when I select my file to alter (e.g. Audio.mp2) I cannot change the destination filename (e.g. NewAudio.mp2).
indeed... :o my fault. It's fixed now...


For your mp2 to ac3 trouble : well...first, I don't think it's a good idea to transcode a lossy to a lossy. Second, could you upload somewhere a short sample of your mp2 stream ? You can also send it to me by mail to kurtnoise at free dot fr

[ron spencer]

do I smell a new beta coming? Hope hope!!!!!

[Kurtnoise]

I hope to release a new beta as soon as possible (before the end of July).

[CiNcH]

Hi,

I'd like to transcode to Vorbis with a negative quality value. Guess that it is not possible and that it is a BeSeet limitation as it returns an error when using a negative quality value in command line (using latest BeSweet + SSE optimized Vorbis 1.1.1 + aoTuVb4 library).

I am currently outputting wave and further convert it to Vorbis with latest oggdropXP (based on Vorbis 1.1.1 + auTuVb4) which displays nominal bitrate much more accurate (finer steps) in Quality Mode than BeLight and supports negative values (down to -2 which equals to 32 kbps).

[Kurtnoise]

Yep... look my next post. :)

[Brother John]

But BeSweet actually CAN have negative Vorbis quality numbers. Range is from -0.1 to 1.0 and corresponds to oggencs -1 to 10. Maybe your vorbis dlls don't support that?

[Kurtnoise]

Indeed... :o I had some old dlls. I tested with the latest libvorbis (1.1.1 aoTuVb4).

With q=-0.1 :
BeSweet v1.5b30 by DSPguru.
--------------------------
Using libVorbis.dll v1.0 ( Jul 9 2005 ) by John33 (www.inf.ufpr.br/~rja00).

Logging start : 07/20/05 , 14:19:31.

d:\Audio\BeSweet1.5b30\BeSweet.exe -core( -input d:\Samples\DaFunk.wav -output d:\Samples\DaFunk.ogg -logfile D:\Audio\BeSweet.log ) -ogg( -q -0.1 )

[00:00:00:000] +------- BeSweet -----
[00:00:00:000] | Input : d:\Samples\DaFunk.wav
[00:00:00:000] | Output: d:\Samples\DaFunk.ogg
[00:00:00:000] | Floating-Point Process: Yes
[00:00:00:000] | Source Sample-Rate: 44.1KHz
[00:00:00:000] +-------- OGG --------
[00:00:00:000] | Average Bitrate : 160
[00:00:00:000] +---------------------
[00:00:20:578] Conversion Completed !
[00:00:20:578] Actual Avg. Bitrate : 49kbps
[00:00:05:000] <-- Transcoding Duration

Logging ends : 07/20/05 , 14:19:36.


With q=-0.2 :

BeSweet v1.5b30 by DSPguru.
--------------------------
Using libVorbis.dll v1.0 ( Jul 9 2005 ) by John33 (www.inf.ufpr.br/~rja00).

Logging start : 07/20/05 , 14:17:09.

d:\Audio\BeSweet1.5b30\BeSweet.exe -core( -input d:\Samples\DaFunk.wav -output d:\Samples\DaFunk.ogg -logfile D:\Audio\BeSweet.log ) -ogg( -q -0.2 )

[00:00:00:000] +------- BeSweet -----
[00:00:00:000] | Input : d:\Samples\DaFunk.wav
[00:00:00:000] | Output: d:\Samples\DaFunk.ogg
[00:00:00:000] | Floating-Point Process: Yes
[00:00:00:000] | Source Sample-Rate: 44.1KHz
[00:00:00:000] +-------- OGG --------
[00:00:00:000] | Average Bitrate : 160
[00:00:00:000] +---------------------
[00:00:20:578] Conversion Completed !
[00:00:20:578] Actual Avg. Bitrate : 35kbps
[00:00:04:000] <-- Transcoding Duration

Logging ends : 07/20/05 , 14:17:13.

Some issue with average bitrate values in the log...but the average bitrate is ok when I checked my files with fb2k.

Ok, I'll include this in the next release... :p Sorry for my bad answer previously.

[CiNcH]

Ah, I see, so -0.2 in BeSweet equals to -2.0 in oggdropXP. Thanks.

Would be nice if you added it to BeLight, Kurt.

[Kurtnoise]

Would be nice if you added it to BeLight, Kurt.
Done...;)

http://kurtnoise.free.fr/vorbis_negval.gif

I'm thinking about something now : added a flag to prevent people to have libvorbis.dll updated if you want to use these negative values. What do think about that ? An other way could be to update directly my package with this dll...

[Palikrovol]

I'm thinking about something now : added a flag to prevent people to have libvorbis.dll updated if you want to use these negative values. What do think about that ? An other way could be to update directly my package with this dll...

I think there is no problem at all with libvorbis.dll versions. I think all version suport negative values.

CiNcH had problems (correct me if i'm wrong) because he/she used -2.0 instead of -0.2.

Anyway it could be a great idea if you (Kurt) has the latest versions of the libvorbis.dll in the download site.

Go on with the great Belight. Thanks a lot.

[Kurtnoise]

The problem is that DSPGuru doesn't provide libvorbis.dll in his BeSweet package. In addition, some people have OggDSF installed. Thus, BeSweet uses this filter for the Vorbis transcoding when there isn't libvorbis.dll into BeSweet folder. In this case AFAIK, we can't use negative values with OggDSF. That's why, all in all, I think the best thing for all will be to include directly libvorbis.dll in BeLight package.

[Palikrovol]

The problem is that DSPGuru doesn't provide libvorbis.dll in his BeSweet package. In addition, some people have OggDSF installed. Thus, BeSweet uses this filter for the Vorbis transcoding when there isn't libvorbis.dll into BeSweet folder. In this case AFAIK, we can't use negative values with OggDSF. That's why, all in all, I think the best thing for all will be to include directly libvorbis.dll in BeLight package.

OK. But remember that there are optimazied versions of libvorbis.dll for pentium4, AMD and of course the general ones.

Are you going to make different builds or just include the general (not optimazied) libvorbis.dll?

[Kurtnoise]

Yep...

Are you going to make different builds or just include the general (not optimazied) libvorbis.dll?
There are lot of place in CC.org you know... :D So I can release different builds w/o problem.

[CiNcH]

OK. But remember that there are optimazied versions of libvorbis.dll for pentium4, AMD and of course the general ones.

You mean the lancer builds? I guess that those builds are just based on SSE which is also supported by AMD Athlon processors from XP onwards, probably SSE2 (don't think so), which means that those builds will work on AMD Athlon 64 and onwards.

But the optimized lancer builds (latest build based on Vorbis 1.1.1 + aoTuVb4) are indeed great. Almost doubled encoding speed...

[Kurtnoise]

Hi,

Finally, 0.22 beta 5 (http://corecodec.org/frs/?group_id=45&release_id=132#r132) is out. :)


changelog :

- Add q negative settings for Vorbis Encoding (libvorbis.dll needed).
- Add some info in the Hint when we select the file in the Input File List.
- Add Polish & Russian Languages.
- Update the AAC presets by introducing the Fast Quality Mode.
- Fix the transcoding aborted flag.
- Fix the mono CBR Mode for MP3 Setting at 96 kbps.
- Fix the ProgressBar Position for MPEG and Vorbis files during the transcoding.

[Vlad74]

Hi Kurt!

I tested the 0.22b5 version and found the same problem with main program window: it is stably shrinked in the right-bottom corner and cannot be streched by mouse. In attempt to stretch it the program window stretches only in its left -top directions... :(
http://img94.imageshack.us/img94/6262/belight022b58ol.jpg

All the same as it was with the version 0.22b4.
I am using Win XP Pro SP2, CPU - AMD Duron, nVidia card...

And it is still OK when I use 0.21 and it was OK when I used version 0.22b1 and b2. Can I get them?

[Kurtnoise]

Too bad for you...Did you use a large font with your PC (i.e 120 dpi) ? You can check this by a right click on your desktop then Properties --> Settings tab --> Advanced button.

Anyway, could you check with this version (http://kurtnoise.free.fr/BeLight-0.22_beta5.zip)...Thanks.

[MrX]

I'm working on a german translation. In the next days I will finish it.
But please leave for the next version more place for the "terms" and buttons. Because in other languages the "terms" are longer usually.
For example:
Options = Einstellungen

[neo_anderson]

hey, i have a question, for ac3 to aac encoding, can i use both pregain and normalize to 100%, or should just one of them be used? which is the optimized way for ac3 to aac encoding in belight, i mean which all options?

[Kurtnoise]

I'm working on a german translation. In the next days I will finish it.
But please leave for the next version more place for the "terms" and buttons. Because in other languages the "terms" are longer usually.

I know...I try to make my best with terms and buttons but this is the main problem with translation.

If you want some help, I found in my old HD an old german translation created by Brother John. I can post it...

[Kurtnoise]

hey, i have a question, for ac3 to aac encoding, can i use both pregain and normalize to 100%, or should just one of them be used? which is the optimized way for ac3 to aac encoding in belight, i mean which all options?
Just one of them...is enough. By default, it's PreGain in BeLight.

[neo_anderson]

kurt, dude, one more thing, should i use 44100 khz or 48000 khz for encoding ac3 to aac in belight?

[Kurtnoise]

It depends of your input file...but the aac compressor from Nero try to find the best and the optimized setting for you. So, let's the Sampling-Rate disabled....at least if you haven't some restrictions for your following tasks.

[Vlad74]

Too bad for you...Did you use a large font with your PC (i.e 120 dpi) ? You can check this by a right click on your desktop then Properties --> Settings tab --> Advanced button.

Anyway, could you check with this version (http://kurtnoise.free.fr/BeLight-0.22_beta5.zip)...Thanks.

Hi, Kurt!

You are genius! You have guessed absolutely right! I did had 120dpi fonts, because Normal fonts were a little bit small for my LCD monitor. When I had changed settings of video card to Normal, both versions of your program - the one you asked me to test and that one I downloaded before - both of them started to work without any shrinkage of windows.

Thank you very much for your help!

However, I think that shrinkage evidences of some gaps in your program, because neither version 0.21 nor other used programs do not depend on settings of video card. It would be great if this problem could be solved in the final version, that I await with impatience!

All the best for you
And good luck!

[2COOL]

BTW if your VOB contains only one audio stream and you have VOBInput.dll in BeLight folder, all should work fine by choosing "All Files" from the input list normally...I think this tidbit should be mentioned on your first post. It took me awhile to read through this big thread and it was post #173.

Also, I find myself manually opening and reading the log if any errors occur. Request for a view log function and option to save?

[2COOL]

@Kurtnoise13

I forgot one more request. It's fine that you are using one thread for new BeLight announcements and discussions, but I would wish that there was some bookmarking table of contents in the first post to jump to versions when they have been released.

e.g.
http://forum.doom9.org/showthread.php?t=90960
http://forum.doom9.org/showthread.php?t=92481

In case, someone might want to easily peruse through the archives. ;)

[Kurtnoise]

I think this tidbit should be mentioned on your first post. It took me awhile to read through this big thread and it was post #173.
Well...you're right. I need to update my first post with some clues. btw, concerning this :

if your VOB contains only one audio stream and you have VOBInput.dll in BeLight folder, all should work fine by choosing "All Files" from the input list normally...
It's not neccessary anymore because there is VOB Files in drop menu List Entry now.

Also, I find myself manually opening and reading the log if any errors occur. Request for a view log function and option to save?
The logfile is saved in your input folder....if you have checked "output log" of course in the settings. ;)

[2COOL]

It's not neccessary anymore because there is VOB Files in drop menu List Entry now.Yes, I knew about that but is it just me that the VOBInput.dll is not included in latest versions of BeLight and BeSweet?

The logfile is saved in your input folder....if you have checked "output log" of course in the settings. ;)Again, I know it saves it because I have checked it but I have to manually check it for any unforseen error. It would be nice if a separate logfile dialog would pop up like DVD Decrypter logfile and view the status in real time. Then, we could opt to save it need be.

But, if you choose to retain the save log option setup, then how about a button/option to view the logfile instead of going into the File Manager and manually opening it?

[Kurtnoise]

Yes, I knew about that but is it just me that the VOBInput.dll is not included in latest versions of BeLight and BeSweet?
Indeed...I forgot this dll in the last package. (but vob input files isn't supported yet in the 0.22 branches...only 0.21. Yeah, I need to update my first post. :D I finish this answer and I add some infos.)


Again, I know it saves it because I have checked it but I have to manually check it for any unforseen error. It would be nice if a separate logfile dialog would pop up like DVD Decrypter logfile and view the status in real time. Then, we could opt to save it need be.
mmmh why not...:) but my question is : why would you like to have this info in real time ? :D

[2COOL]

why would you like to have this info in real time ? :D Well, at the time when I did have my VOBInput.dll in my folder, my process indicated that everything went well. But, when I went to check the folder to see my new files, there were some missing. It was because of the logfile that has shown me the error.

Also, about the logfile saving option you mentioned...where is it? I just looked in latest version and I can't find it. It must be saving by default.

But, why not having a logfile dialog on the side in real time? It gives the user a better understanding of what events are occuring and the results are. It gives us a sense of security.

[Kurtnoise]

Also, about the logfile saving option you mentioned...where is it? I just looked in latest version and I can't find it. It must be saving by default.
It is saved as soon as the BeSweet process is running. There is not saving option concerning the logfile.

But, why not having a logfile dialog on the side in real time? It gives the user a better understanding of what events are occuring and the results are. It gives us a sense of security.
Ok...I'll add it. Anyway, if you try BeLight 0.22 beta xxx you can see already some infos during the process.




PS : first post updated. Tell me if it's enough...

[Paulcat]

I was tinkering with beta5, converting an mp3 file to a stereo ac3 file...the progress bar showed completion in about 5 seconds, while the actual conversion process took 4 minutes...

[Kurtnoise]

It's because BeLight doesn't like that you transcode a lossy file to an other lossy file.... :sly: :D

More seriously. The extension of your input file is in capital letter, right ? If yes rename it in lower case. I just fixed this issue...



btw, try to describe the bugs more precisely in the future...Copy here the logfile at least. Thanks.

[MrX]

If you want some help, I found in my old HD an old german translation created by Brother John. I can post it...

That would be nice.

[Kurtnoise]

http://kurtnoise.free.fr/BeLight/Deutsch_by_BrotherJohn.txt

Hope this helps.

[2COOL]

It is saved as soon as the BeSweet process is running. There is not saving option concerning the logfile. Yes, but it contradicts what you previously posted.

The logfile is saved in your input folder....if you have checked "output log" of course in the settings. ;)

_______________

Ok...I'll add it. Anyway, if you try BeLight 0.22 beta xxx you can see already some infos during the process. Thanks!

PS : first post updated. Tell me if it's enough...Much better! :D BTW, I see you have updated the image. I kinda like the green interface since it made it look so fresh and not so default. That's what I'm using right now.

[EDIT] I think you should mention this important disclaimer in your first post too if it's still valid while using VOBInput.dll. I haven't tried it yet with a multiple audio VOB but I assume it won't work properly?

if your VOB contains only one audio stream and you have VOBInput.dll in BeLight folder ...

[Kurtnoise]

Yes, but it contradicts what you previously posted.
Not at all...by option saving I would say something like that : File --> Save as. In other words, using some manually interaction. ;)



I see you have updated the image. I kinda like the green interface since it made it look so fresh and not so default. That's what I'm using right now.
You mean the winXP Theme ?


I think you should mention this important disclaimer in your first post too if it's still valid while using VOBInput.dll. I haven't tried it yet with a multiple audio VOB but I assume it won't work properly?
It's not valid anymore with BeLight 0.21...