BeLight 0.22 beta 8 released

[Palikrovol]

is the progress bar disabled?

When transcoding an AC3 to AAC there is nothing that indicates BeSweet is properly working (except 100% CPU and increasing file :)

And another Question.

The progress bar also increases when BeSweet is calculating the Gain? because in this moment the only way to know BeSweet is working is the 100% CPU (There is no file increase).

BTW thanks for the reziable window :)

[Kurtnoise]

Originally posted by Palikrovol
is the progress bar disabled?

When transcoding an AC3 to AAC there is nothing that indicates BeSweet is properly working (except 100% CPU and increasing file :)
The progessbar indicates the transcoding time. I parse the elapsed time of the BeSweet CLI. And it's not disabled...

Originally posted by Palikrovol
The progress bar also increases when BeSweet is calculating the Gain? because in this moment the only way to know BeSweet is working is the 100% CPU (There is no file increase).
because, by default BeLight uses PreGain Mode for the transcoding AC3 to AAC. And like I said, I parse the elapsed time from the CLI. So, if you look this window, you can see that the PreGain is made first. And then the transcoding progress. That's why you have two progession for the ProgressBar. If use hybridgain mode by example, you will have only one Progress.

[Elias]

Originally posted by Kurtnoise13
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.The source could be 768 kbit/s DTS or 1536 kbit/s DTS :D

[Kurtnoise]

Originally posted by Elias
The source could be 768 kbit/s DTS or 1536 kbit/s DTS :D
Yes but BeSweet doesn't support dts files. ;)

[Elias]

Originally posted by Kurtnoise13
Yes but BeSweet doesn't support dts files. ;) True, BUT, suppose I encode a DTS file into a 5.1 Wav and then to AAC? That's mainly why I want higher bitrate support.

[LigH]

448 kbps is the maximum bitrate for AC-3 which is supported on DVD (although, for other occasions, up to 640 kbps is supported, but not on DVD). Do you think that 448 kbps sound bad?

AAC is an even more advanced audio compression algorithm than AC-3. Why do you think you need more bitrate for AAC than for AC-3?

Do you really think you can actually hear the difference between dts and AC-3? (And don't answer before you did an ABX test!)

[Elias]

Originally posted by LigH
448 kbps is the maximum bitrate for AC-3 which is supported on DVD (although, for other occasions, up to 640 kbps is supported, but not on DVD). Do you think that 448 kbps sound bad?

AAC is an even more advanced audio compression algorithm than AC-3. Why do you think you need more bitrate for AAC than for AC-3?

Do you really think you can actually hear the difference between dts and AC-3? (And don't answer before you did an ABX test!) No, I don't think that 448 kbps AC-3 sounds bad. I just happen to like high bitrates. The higher the better.

[LigH]

Then use 24b/96kHz PCM! :D

[mazzo]

BeSweet will not open the source files when I drop them to BeLight. If I open the with Ctrl-O, it's ok.

[Kurtnoise]

BeSweet is just a CLI...:rolleyes: You can't open/save files with it. It works with different commands.


And alpha versions support only ac3 files.

[mazzo]

Oh, I'm only quoting the log file in BeLight

BeSweet v1.5b29 by DSPguru.
--------------------------
Error 57: Error opening " test.wav".

[Kurtnoise]

How do you create this file ?

Could you provide a sample of your file ?

[Kurtnoise]

So, anybody have tested the last alpha ?





I forgot to mention before that the Total ProgressBar doesn't work properly...:o I'm trying to fix this issue.

[Elias]

Originally posted by Kurtnoise13
So, anybody have tested the last alpha ?





I forgot to mention before that the Total ProgressBar doesn't work properly...:o I'm trying to fix this issue. Well, not yet. I may try it later though. I don't understand what the improvements are? Do I get fully Quicktime compatible 5.1 AAC now? Or do I still have to extract it with some MPEG-4 tools and then mux it to an *.mp4 container in order to get the 5.1 AAC audio working in Quicktime? This is my only problem, other than this, I don't see any reason to upgrade because it works pretty good here with the 0.21 stable release :)

[Kurtnoise]

Please, don't speak about mp4 container in this thread...:D :D


The main improvements in the last alpha concern the batch mode (i.e xxx ac3 files as input to xxx aac/mp2/m3/vorbis/wav...). I tested some input ac3 files and all seems to be ok. But I would like to have some feedbacks from other users. ;)

[Elias]

Originally posted by Kurtnoise13
Please, don't speak about mp4 container in this thread...:D :D


The main improvements in the last alpha concern the batch mode (i.e xxx ac3 files as input to xxx aac/mp2/m3/vorbis/wav...). I tested some input ac3 files and all seems to be ok. But I would like to have some feedbacks from other users. ;) Well it's not really the *.mp4 container I was talking about. My point was, that the 5.1 encoded AAC ain't working in Quicktime/Winamp and I wondered if it's fixed? Someone said that it's because of the Nero dll filters, or something. I don't know to be sure.

[mazzo]

The new alpha works very fine with drag and drop on wav files, but it's difficult to watch the progression since the status bar is dead.

[Elias]

Hey, just tried it out with 5.1 and stereo AC3, and it worked great. Sounds even better than 0.21 release. I'll use this one as standard from now on until you've released newer builds.

[Kurtnoise]

Originally posted by mazzo
The new alpha works very fine with drag and drop on wav files, but it's difficult to watch the progression since the status bar is dead.
because the alpha versions support *only* ac3 files as input, like I said before. I plan to add other formats this week-end. :)


@Elias : thanks for your tests. ;)

[mazzo]

Very good. I've always found the old BeSweet GUI very difficult, so BeLight seems to be just THE thing for me.

[Elias]

http://img215.exs.cx/img215/4359/belight06qk.png

I don't know what's up, but I created a 6 mono wav from an mp3 file with BeLight v0.22 Alpha 2, then I closed BeLight, and re-opened it, and this is the error message I get. After I click OK I can use BeLight... weird :)

[Kurtnoise]

Originally posted by Elias
I don't know what's up, but I created a 6 mono wav from an mp3 file
Not possible... :rolleyes:

[Elias]

Originally posted by Kurtnoise13
Not possible... :rolleyes: Believe it or not, I did. Although, out of 6, I got 4 empty wav files :)

[Palikrovol]

Found some bugs

In "Command Line editor".

- When opening file "F:\_TMP_\Heavenly Creatures.ac3" the resulting command line in the "command line editor window" is

BeSweet.exe -core( -input "F:\_TMP_\F:\_TMP_\Heavenly Creatures.ac3" -output "F:\_TMP_\F:\_TMP_\Heavenly Creatures.ogg" -logfile "F:\_TMP_\F:\_TMP_\Heavenly Creatures.log" ) -azid( -c normal ) -ota( -hybridgain ) -ogg( -q 0.400 )

If i press "Run" it works perfectly and get the file from the correct path. It just shows it incorrectly.

It is solved when unchecking the audio track and opening again the "Command line editor". From that moment is always correct (even if you check and uncheck the audio track mny times).

Another way to solve it is to "start the process", abort it and openig the "Command line editor" again.

- If you close the file (clear list) and then open the "Command line editor", there is still the command line for the closed file. The "Command line editor" has to be closed and opened again to clear the trace of the closed file. (A good thing is that if you press "Run" with the closed file command line, a window appears telling you that there is no input file).


- A cosmetic issue. In the context menu in the files list, i think is better not to show cheching marks when pressing the different options, because you can press the same option two consecutive times and when you press a checked option you feel like you are unchecking it, not running it.


It is all :). I hope it is useful.

[Palikrovol]

More about the "path" issue.

If the first opened file is opened in a "Drag and Drop" way, it will be correctly displayed. Any other file opened in the way "Drag and Drop" next, will be correctly displayed. If then a file is opened by "File -> Open" it will be incorrectly displayed and any other file will be incorrectly displayed if opened in any way.

If the first file is opened by "File -> Open" it will be incorrectly displayed and the next files also will be displayed incorrectly any way they were opened.

If a file is correctly displayed ("F:\_TMP_\Heavenly Creatures.ac3") and then you uncheck the file, the path information ("F:\_TMP_\") is erased from the command line. And when pressing "Run", BeLight starts
and ends and does nothing.


BeLight does nothing with the first opened files in the "Drag and Drop" way (even if you don't uncheck it).


I think one of the bugs is when unchecking for the first time the files.

Regards

[Kurtnoise]

Originally posted by Elias
Believe it or not, I did. Although, out og 6, I got 4 empty wav files :)
Please, read once again what I said concerning alpha versions. And why I said "not possible" ? because it's completely useless. Why do you want to extract 6 mono waves from a stereo file huh ??

[Elias]

Originally posted by Kurtnoise13
Please, read once again what I said concerning alpha versions. And why I said "not possible" ? because it's completely useless. Why do you want to extract 6 mono waves from a stereo file huh ?? I was just playing around a bit :D Testing some functions, checking if they worked properly.

[Kurtnoise]

Originally posted by Palikrovol
More about the "path" issue.

Sometimes the file is correctly displayed the first time you open it ("F:\_TMP_\Heavenly Creatures.ac3"). But if then you uncheck the file the path information ("F:\_TMP_\") is erased from the command line and when pressing "Run", BeLight starts and ends and does nothing.

I think one of the bugs is when unchecking for the first time the files.

Ok I see...I'll try to fix it.

Originally posted by Palikrovol
- A cosmetic issue. In the context menu in the files list, i think is better not to show cheching marks when pressing the different options, because you can press the same option two consecutive times and when you press a checked option you feel like you are unchecking it, not running it.
Not really an issue but I can change it for sure. I had not thought about that.

[Palikrovol]

ReRead my Second post, i have edited it. I have found new information :).

[Palikrovol]

Some things i forgot.

- In the files list, if the file's name is too long, it is not displayed complete (appears truncated).

- The options '-L -3db' (-azid) are not displayed in the "Command Line", but are checked in the advanced options. I have to unckeck and recheck this options in the advanced options to make them appear in the command line.

[planet1]

Kurtnoise13 first of all thx for this great GUI.

1. could you add a drag&drop feature to BeLight (speeds up things)

Belight 0.21 final:

2. when picking a wav as input and choosing 16bit Stereo Wave as output kind of adds useless switches [ -azid( -s stereo -L -3db )]


3. when inputting a .mux list and output is WAV there are also some "useless" azid switches:

5.1 WAVE: -azid( -c normal )

Stereo WAVE: -azid( -s stereo -c normal -L -3db )

16bit (Six) Mono WAVEs: -azid( -c normal )

32bit (Six) Mono WAVEs: -azid( -c normal )

[Kurtnoise]

Originally posted by planet1
1. could you add a drag&drop feature to BeLight (speeds up things)
This feature is added with 0.22 alphas...;)

Originally posted by planet1
Belight 0.21 final:

2. when picking a wav as input and choosing 16bit Stereo Wave as output kind of adds useless switches [ -azid( -s stereo -L -3db )]


3. when inputting a .mux list and output is WAV there are also some "useless" azid switches:

5.1 WAVE: -azid( -c normal )

Stereo WAVE: -azid( -s stereo -c normal -L -3db )

16bit (Six) Mono WAVEs: -azid( -c normal )

32bit (Six) Mono WAVEs: -azid( -c normal )
It's corrected with 0.22 alpha versions. But for the moment, wav files are not supported. So, just wait a next version or edit the command line...:)


@Palikrovol : yeah, I saw the problem. Thanks for the bugs report.

[Kurtnoise]

The 0.22 beta 1 is out (http://corecodec.org/frs/?group_id=45&release_id=80).

changelog:

* Added some other input formats (mpa, mp2, mp3, vorbis, wav[**]) compatible with the Batch Mode.
* Bugs fixed concerning Opening & Checking input files.
* Edit window for BeSweet Command Line is now updated then we decide to change settings.
* Several internal tweakings.

[**]only stereo files for the moment.



In addition, a screenshot to show you the transcoding CD-Audio wav files to vorbis with BeSweet by example....;)

http://www.unite-video.com/phpbb/files/belight-0.22b1_437.gif

[Bluedan]

Great, I'll have a glimpse....

[guada 2]

Good continuation " Kurt " ;)

[Elias]

Why isn't 29.970>23.976 working? In the latest Beta release, the file became slooooow. I mean, it's much slower than usual. In the previous versions, it doesn't even work to encode with NTSC>NTSC Film.

[Kurtnoise]

Hi,

Your input file is an AC3 ? If yes, 2.0 or 5.1 ?

Did you use soundtouch function ?

Could you test also with BeSweetGUI 0.7b8, please ?

[Elias]

Originally posted by Kurtnoise13
Hi,

Your input file is an AC3 ? If yes, 2.0 or 5.1 ?

Did you use soundtouch function ?

Could you test also with BeSweetGUI 0.7b8, please ? Where can I get that GUI? Yes, it's AC3. 2.0 and 5.1, all the same. Also, it says Transcoding aborted when the encoding is done :S By the way, could you add azidts support? I'd like to encode *.dts files :) I don't know what soundtouch is :)

[Boulder]

By the way, the SoundTouch library has been updated some time ago, it fixes a nasty rounding bug which affected framerate conversions. If someone could compile it for using with BeSweet, it would be great;)

[Kurtnoise]

Originally posted by Elias
Where can I get that GUI?
http://www.dspguru.doom9.net (beta section)

Originally posted by Elias
Yes, it's AC3. 2.0 and 5.1, all the same. I don't know what soundtouch is :)
If you don't know what it is, so how did you enable the trick ? (i.e 29.970>23.976). BeLight supports only soundtouch functions for those changes. Note also that soundtouch doesn't support multichannel files, only mono & stereo.

Originally posted by Elias
Also, it says Transcoding aborted when the encoding is done :S
yeah, stupid bug which is corrected. :)

Originally posted by Elias
By the way, could you add azidts support? I'd like to encode *.dts files :)
No because BeSweet doesn't support dts files...

[Elias]

Originally posted by Kurtnoise13
http://www.dspguru.doom9.net (beta section)


If you don't know what it is, so how did you enable the trick ? (i.e 29.970>23.976). BeLight supports only soundtouch functions for those changes. Note also that soundtouch doesn't support multichannel files, only mono & stereo.


yeah, stupid bug which is corrected. :)


No because BeSweet doesn't support dts files... I guess it's called soundtouch, didn't know what it was called. But hey, is it really necessary to decrease the FPS from NTSC>NTSC film? I mean, I just added the delay settings DGIndex gave me, and when muxing the audio streams with the video stream, it all seemed perfect sync. How am I able to encode *.dts files then? I'll try the beta version of BeSweetGUI in a while.

[mazzo]

I get this error message in french every time I start the beta 1:

[mazzo]

Seems that my attachment didn't show. Well the error message is:

Violation d'accès à l'adresse 004A4DFC dans le module 'BeLight.exe'. Lecture de l'adresse 000002FC.

[Elias]

Originally posted by mazzo
Seems that my attachment didn't show. Well the error message is:

Violation d'accès à l'adresse 004A4DFC dans le module 'BeLight.exe'. Lecture de l'adresse 000002FC. I used to get it. Can't remember how I solved it :S

[Kurtnoise]

Originally posted by Elias
I guess it's called soundtouch, didn't know what it was called. But hey, is it really necessary to decrease the FPS from NTSC>NTSC film? I mean, I just added the delay settings DGIndex gave me, and when muxing the audio streams with the video stream, it all seemed perfect sync.
ooo well...it's not necessary if you keep the same FPS for video and audio. But if you change the FPS when you transcode your audio file and not for the video, you can have some desync issues for sure.



@mazzo : very strange...:confused: Are you overwrite all the old files when you install this beta ?

[Elias]

Originally posted by Kurtnoise13
ooo well...it's not necessary if you keep the same FPS for video and audio. But if you change the FPS when you transcode your audio file and not for the video, you can have some desync issues for sure.I chose 29.970>23.976 for the Video, encoded the audio with the correct delay settings, muxed, and the sync was picture perfect. Couldn't change the FPS with soundtouch from 29.970>23.976... but still, there's no sync problems of what I can hear/see. Should I just go with that? I mean, after all, if it ain't broken, don't fix it?

Originally posted by Kurtnoise13
@mazzo : very strange...:confused: Are you overwrite all the old files when you install this beta ? I always do this, in fact, did it a couple of times today, and didn't get that issue, I've stopped getting it.

[mazzo]

Kurtnoise: Try to make something with the settings, for instance set the mp3 slider to 160 Kbps CBR. Close BeLight. Whan I do that, and try to reopen, the message comes back.

[Kurtnoise]

I'll try to fix that as soon as I'm back home...;)

[rotflol]

Originally posted by Elias
I chose 29.970>23.976 for the Video, encoded the audio with the correct delay settings, muxed, and the sync was picture perfect. Couldn't change the FPS with soundtouch from 29.970>23.976... but still, there's no sync problems of what I can hear/see. Should I just go with that? I mean, after all, if it ain't broken, don't fix it?
Short answer: yes. You don't need to "change fps" of an audio track when converting a movie from NTSC to "film" (29.97 > 23.976 fps).

[Elias]

Originally posted by rotflol
Short answer: yes. You don't need to "change fps" of an audio track when converting a movie from NTSC to "film" (29.97 > 23.976 fps). Thanks, that cleared it up for me :) One question though, why is there such a feature if there's no need for it?