BeLight 0.22 beta 8 released

[Kurtnoise]

BeSweetGUI OTA settings don't use soundtouch commands AFAIK...but I'll look into BeLight to see what's happen exactly. ;)

[OMINUS]

Originally posted by Taurus
I just tested it: Both combos,Belight/Besweet and GKnot/Besweet are reaching 100% CPU load. And what does this mean "CPU overload"?
I'm a speed freak, if it was'nt 100%, I would force it to....:D
This is pretty normal behaviour for an encoder.

Cheers

Taurus

with gknot the encoding doesnt use all the cpu resources
just a 15% of the cpu without any speed loss in the fast encoding process
this is a good thing u know

with belight/besweet combo all the cpu resources are used 100% but the speed of the process is anyway fast already
this is a bad thing-i cant use other applications while i encode with belight

anyway i am just curious what difference in the settings causes this behaviour

[Elias]

Originally posted by OMINUS
this is a bad thing-i cant use other applications while i encode with belightI don't get it. Are you using the unstable version? It works fine for me to use other applications. I even encode in VirtualDub while encoding an audio from the BeLight GUI.

[rotflol]

Originally posted by Kurtnoise13
BeSweetGUI OTA settings don't use soundtouch commands AFAIK...but I'll look into BeLight to see what's happen exactly. ;)
My point exactly. :) For some reason SoundTouch doesn't work in this respect, while OTA does.

[OMINUS]

Originally posted by Elias
I don't get it. Are you using the unstable version? It works fine for me to use other applications. I even encode in VirtualDub while encoding an audio from the BeLight GUI.

i use latest versions of belight and besweet
i encode wav to mp3 with belight's default settings
the cpu gets 100% used-the encoding speed is fast
with gknot(it uses latest besweet) i dont have this cpu overload
i encode wav to mp3 with the default advanced settigns of gk
the cpu gets 15% used-the encoding speed is fast

i use the latetest version of lame codec btw

its a mystery isnt it?

[Sakuya]

I'm getting the same problem again. I cannot find the start button. I have moved my Windows toolbar to the left and now I see the entire BeLight GUI but there's no start button. :( Here's a screenshot.

http://img.photobucket.com/albums/v117/Yakusoya/belight.jpg

[Elias]

Originally posted by OMINUS
its a mystery isnt it? seems so, yeah.

[Kurtnoise]

Originally posted by OMINUS
its a mystery isnt it?
Maybe it comes from the fact that I compress the executable file. upx is known to overload the cpu in memory...But on my PC, if I compress or not, I haven't this problem. :rolleyes:



@Sakuya : This problem occurs when we have a low resolution. Try the latest beta.

[daphy]

0.21 beta 3 is the latest beta, or is there something new I missed while skiing in Switzerland :D

[Sakuya]

I changed my screen resolution to 1024x768 and it worked. I used another thread as a guide and Kurtnoise said to use BeLight:

http://forum.doom9.org/showthread.php?s=&threadid=89722

I was originally asking help in this post about why BeLight wasn't working.I found a solution not using BeLight but am having some small problems. Since I can't delete this post, I thought I should just post a redirect message in its place. I hope that's allowed? :)

[LigH]

Dear kurtnoise,

would it be very hard for you to add another tab, which guides the user to create a *.mux file?

My "dream" would be some kind of channel figure (the square with the boxes), and the boxes are hollow at first, react on mouse clicks (maybe change the mouse pointer to the hand pointer there), allow to open a mono WAV file per channel on click, fill the box then, and finally allow to export the *.mux file for creating 5.1 audio files when all boxes have assigned their channel wave files.

[Kurtnoise]

hi,

Can you show me what you want with a picture ? :o

I'm working with a CheckListBox now to store the input files. Maybe with the multiple selection and right click, we could make something...

I remember that daphy asked me the same thing...

[LigH]

Better I show you the tool I just stippled together in a hurry.

Usage:

- Click on all the 6 channel boxes and select each wave file.
- Click on "Save as:" and enter the MUX file name.
- This enables the OK button: Click, the mux file is written, the wizard closes.

http://www.ligh.de/software/BSMUXWIZ.zip

NOTE: It is compressed with UPX 1.93 beta with "--brute" option. It might not run everywhere - if not, try to decompress.

[Kurtnoise]

Ok...It sounds really good. ;) I can try to add this...but we must think about the different channels order for the output formats. AC3/Vorbis have the same order but for AAC it's completely different. :rolleyes: BTW, I can manage something for sure.

Thanks for the tip. :)

[LigH]

Different channel orders -- well; in my opinion, BeSweet shall request always the same standardised channel order from its source (no matter if from a *.mux file, or from the decoder). If necessary, it shall remap the channels internally if a decoder DLL does not serve the channels in expected order. So it can ensure that after decoding or importing, channels are always present in a known order. And if an encoder DLL expects them in a different order, it shall remap them on-the-fly while delivering them.

But expecting different channel orders for different encoders in the *.mux file, is (in my oh-so-humble opinion) not quite a wise thing. ;)

[Kurtnoise]

In my opinion, we must specify the different channels order under BeSweet because the decoders themselves can't remap these channels correctly. But maybe I'm wrong....


BTW, what do you think about that :

http://kurtnoise.free.fr/misc/BSMUXWiz.gif

;)

[Elias]

Originally posted by Kurtnoise13
In my opinion, we must specify the different channels order under BeSweet because the decoders themselves can't remap these channels correctly. But maybe I'm wrong....


BTW, what do you think about that :

http://kurtnoise.free.fr/misc/BSMUXWiz.gif

;) Looks great!

[LigH]

@ Kurtnoise13:

As long as BeSweet won't remap channels depending on the encoder, you probably have to.
__

@ Elias:

(Full quotes are usually useless.)

[Kurtnoise]

Hi,

Finally I made a first alpha 0.22 release (http://corecodec.org/frs/?group_id=45&release_id=79). :)

What's new ?

* Drag & Drop support.
* Batch Mode.
* Append output log file option.
* BeSweet mux file Wizard (thanks to LigH for the tip).
* Preview & Edit BeSweet Command Line are 2 options independant now.
* Some improvements concerning the design.
* Bugs fixed for AAC Presets.
* Others some bugs corrected.


Some notes :
- This is an alpha version. So, there are some things not implemented. That's why, only ac3 input files work at the moment. If all it's ok and if you like it, I'll add the others input formats supported by BeSweet.
- The job list isn't finalize that's why this option is disabled. I need to fix some final bugs to have this feature. But the batch mode works fine...I hope.:rolleyes:


BTW, thanks for your support and patience. ;)

[filewalker]

Looks impressive!:) Thanks!


"Command line edition" to edit CL looks really great!:)

Btw.
If "View BeSweet commandline" is enabled, it doesn't show the whole commandline, only what is written in the one line at the bootom.

It would be nice if the whole Commandline is watchable to see the changes on the fly after changing some settings.

...and I like the "Info" under Vorbis...really newbie friendly.

Cu filewalker

[Kurtnoise]

Originally posted by filewalker
If "View BeSweet commandline" is enabled, it doesn't show the whole commandline, only what is written in the one line at the bootom.

It would be nice if the whole Commandline is watchable to see the changes on the fly after changing some settings.

Just put your mouse on the command line... ;) The whole command appears into the hint. Maybe I need to tune this part.

[LigH]

On Windows 2000 SP4 German, the mux file wizard looks to me, that the channel figure square is completely filled in black; instead, it rather shall be a hollow square.

[Palikrovol]

First of all CONGRATULATIONS and thank you very much for this great GUI.

A suggestion: Could you make the "command line edition" window resizeable.

See you.

[filewalker]

Just put your mouse on the command line... The whole command appears into the hint.
Ahh,I see...cool!:) Thanks for the hint.

Cu

[Kurtnoise]

Originally posted by LigH
On Windows 2000 SP4 German, the mux file wizard looks to me, that the channel figure square is completely filled in black; instead, it rather shall be a hollow square.
Screenshoot please...:p I'm running on winXP.

[Kurtnoise]

Originally posted by Palikrovol
A suggestion: Could you make the "command line edition" window resizeable.
sure...no problem. ;)

[LigH]

Can you see the big black square?

http://www.ligh.de/pics/BSMFW.png<= here shall appear an inline image?!
http://www.ligh.de/pics/BSMFW.png

[Kurtnoise]

ok...:( I'll try to change that.

[Kurtnoise]

A new alpha (http://corecodec.org/frs/?group_id=45&release_id=79)...:rolleyes:

Changelog:

* The window of "Edit BeSweet Command Line" option is resizable now.
* Bug fix for the shape concerning the Mux file Wizard.
* Bug fix regarding the Cancel button during the process.
* Added some goodies (icons for the Main Menu).

[LigH]

Figure box looks well now.

But the priority classes are not ordered well ("Real" between "Normal" and "High"?!): I'd recommend

- Real
- High
- Normal
- Idle

[Kurtnoise]

Originally posted by LigH
But the priority classes are not ordered well ("Real" between "Normal" and "High"?!): I'd recommend

- Real
- High
- Normal
- Idle
Why not...:D I'll change.

[DK]

first of all: great work, kurt


tried latest belight alpha a minute ago

any chance of a *save as* command / the chance to rename the input file?

imagine loading an 320mp3 and wanting to save that to 192mp3

i tried something similar two times and both times ended up with a 0kb file (the overwritten original file)

maybe this was mentioned before or maybe this is only occuring with the latest alpha - bear with me for not having read the entire thread

keep up the good work!

[Kurtnoise]

As I said before (read my previous posts) these alpha versions support only ac3 as input files. I prefer to correct some bugs before to add the others formats.


Anyway, there is already a "save as" option (File --> Save...). ;)

[lexsteele]

Is the Job Queue functional yet? If I press it, Belight does nothing.


Great interface BTW!

[Kurtnoise]

Originally posted by lexsteele
Is the Job Queue functional yet? If I press it, Belight does nothing.
Not functional yet...Please, read my posts in previous page concerning alpha versions. :rolleyes:

[Elias]

Originally posted by Kurtnoise13
As I said before (read my previous posts) these alpha versions support only ac3 as input files. I prefer to correct some bugs before to add the others formats.


Anyway, there is already a "save as" option (File --> Save...). ;) Is the 5.1 encoding safe for use? I haven't managed to get any of the 5.1 aac streams working in Quicktime. Although they work more than perfect with other players, like VLC/MPC, Quicktime is no sound as of now. It might be that Quicktime doesn't support 5.1 sound? Because they didn't work in winamp either. I use BeLight 0.21 with the latest BeSweet.

[Kurtnoise]

Originally posted by Elias
Is the 5.1 encoding safe for use?
Yes...it should. :)

BTW, why would you like to use qt whereas it works perfectly with other players ?

[Elias]

Originally posted by Kurtnoise13
Yes...it should. :)

BTW, why would you like to use qt whereas it works perfectly with other players ? I never use Quicktime :) Quicktime is very, very bad :D But it's like more of an insurance that if it works with Quicktime, then it's basically guaranteed to be a correct working MPEG-4 file :)

[JoeBG]

Originally posted by Elias
Is the 5.1 encoding safe for use? I haven't managed to get any of the 5.1 aac streams working in Quicktime. Although they work more than perfect with other players, like VLC/MPC, Quicktime is no sound as of now. It might be that Quicktime doesn't support 5.1 sound? Because they didn't work in winamp either. I use BeLight 0.21 with the latest BeSweet.

Thats a mistake in the Nero Filter. You have to export the aac from mp4 with mp4creator (-extract=1), import it again in any mp4 and it will work for you in quicktime.

[Elias]

Originally posted by JoeBG
Thats a mistake in the Nero Filter. You have to export the aac from mp4 with mp4creator (-extract=1), import it again in any mp4 and it will work for you in quicktime. Well, I don't know how to extract it from the mp4creator :D How do I even open mp4creator without a GUI?

[Sounddude]

Works great!!!

Thanks for the new gui!

[Elias]

One thing I'd like is higher bitrate than 448, especially for 5.1 audio, and a monaural encoding mode. And, make the alpha/beta versions available to more than just AC-3 :D By the way, is it possible of you to add an option of inputting six mono wavs and then an encode option of 5.1 sound from there? For AAC that is.

[Kurtnoise]

Originally posted by Elias
One thing I'd like is higher bitrate than 448, especially for 5.1 audio, and a monaural encoding mode.
:confused: what format do you talking about ?

Originally posted by Elias
make the alpha/beta versions available to more than just AC-3 :D
Yes, I'll add much more input formats for betas versions. But before, I'd like to have some feebacks concerning these alphas.

Originally posted by Elias
By the way, is it possible of you to add an option of inputting six mono wavs and then an encode option of 5.1 sound from there? For AAC that is.
This is the job of .mux file.

[Elias]

Originally posted by Kurtnoise13
:confused: what format do you talking about ?AAC :)

Originally posted by Kurtnoise13
:This is the job of .mux file. What .mux file? I have no idea what that is.

[Kurtnoise]

Originally posted by Elias
AAC :)
The question is : why would you have a bitrate higher than 448 kbps ?

Originally posted by Elias
What .mux file? I have no idea what that is.
This is a list file in which you must specify the differents mono channels. In addition, :search: and :readfaq:, especially BeSweet FAQ. ;)

[Elias]

Originally posted by Kurtnoise13
The question is : why would you have a bitrate higher than 448 kbps ? Higher quality? Less compression? :D Nero Digital supports up to 640 kbps for LC AAC, why not BeLight?

Originally posted by Kurtnoise13
This is a list file in which you must specify the differents mono channels. In addition, :search: and :readfaq:, especially BeSweet FAQ. ;) http://rj-elektronik.de/avideo/PDF/Stereoto5.1AC3.pdf this guide had a pretty good 6 mono wavs to ac3 encoding piece of software. Problem is, that it could only output to ac3. Meaning that the soundtrack would've need to go through another lossy encoding process in order to achieve 5.1 AAC. So this is really all I need from BeLight; a similar 6 mono wav to 5.1 AAC function. As for the FAQs/Search I'll get into it right now.

[Kurtnoise]

Originally posted by Elias
Higher quality? Less compression? :D Nero Digital supports up to 640 kbps for LC AAC, why not BeLight?
I guess your input files are wav files, right ?? If not (like ac3 files by example), it's completely insane. You will not have a higher quality by increasing the bitrate if the bitrate of your source file is smaller than the target bitrate.

Originally posted by Elias
http://rj-elektronik.de/avideo/PDF/Stereoto5.1AC3.pdf this guide had a pretty good 6 mono wavs to ac3 encoding piece of software. Problem is, that it could only output to ac3. Meaning that the soundtrack would've need to go through another lossy encoding process in order to achieve 5.1 AAC. So this is really all I need from BeLight; a similar 6 mono wav to 5.1 AAC function. As for the FAQs/Search I'll get into it right now.
Dead link but .mux files are supported with the 0.21 releases...

[Elias]

I just checked up the mux file option in the BeSweet FAQ. It seems really good. I'll definitely try it out. But it would be cool with a more user friendly alternative in BeLight :D

[Kurtnoise]

Like "File --> Create .mux file" in 0.22 alpha 2...:p

[Elias]

Originally posted by Kurtnoise13
Like "File --> Create .mux file" in 0.22 alpha 2...:p Aaaah :) Cool :) I haven't tried out that alpha release though. I'm waiting for stable releases.