* BeSweet + GUI: a few problems

[LigH]

Dear pals,

now that BeSweet (by DSPguru) and the corresponding GUI (by DanniDin) are released, I had to try - and found a few problems. I hope that most of them can be fixed quickly:

@DSPguru: When ripping a DVD with SmartRipper and writing separate AC3 files during this process, these AC3 files get rather verbose names - with parentheses. But BeSweet also uses parentheses to determine where a parameter group ends. It shall be possible to ignore parentheses inside double quotes of filenames. Else BeSweet immediately stops before starting the conversion with a default systax printout.

@DanniDin: When I save a LAME preset with ABR (e.g. as default), the minimum bitrate immediately gets lost. But the minimum bitrate is allowed to limit the bitrate range. Furthermore, the parameters "-t" (no Xing header) and "--nohist" (no VBR histogram) are allowed for both ABR and VBR: They both use a variable bitrate, the only difference is that the one uses a constant quality, the other a target average bitrate.

I wish you success - and DSPguru: If you calculate the average power during the first decoding (while finding the maximum gain), you could use this information for supporting the "automatic mode" of WaveBooster (with a target average power) - due to the logarithmic presentation, it is a simple addition and subtraction of dB values. Maybe you could even disable the normalisation when boosting is used, just add the normalisation gain into the boost gain. Or am I wrong here?!

[DanniDin]

Thanks for the Info LigH !

I'll Look into it Tomorrow...

Danni.

[DSPguru]

Hi man !
It shall be possible to ignore parentheses inside double quotes of filenames

please give a specifiec example, 'cause all my tests showed no problem.

I wish you success - and DSPguru: If you calculate the average power during the first decoding (while finding the maximum gain), you could use this information for supporting the "automatic mode" of WaveBooster (with a target average power) - due to the logarithmic presentation, it is a simple addition and subtraction of dB values.
ATM, only manual Boosting algorithm is supported. (mayB we should discuss a little-bit about your Automatic algorithm ;)).
anyway, when working with list, the configuration stays the same, unless noted differently. that means, if you run :
BeSweet -core( -input list.lst -output out.mp3 -substream 0x80 ) -azid( -g max )

and the list would be :
-core( -input 01.vob )
:
-core( -input 09.vob )

so, substream of all vobs would be 0x80, and the gain for all files would be the Maximum-gain found for the first vob (01.vob).

this attitude is also true for Boosting.

if a user wants to set different params to the list, he should :
-core( -input 01.vob ) -azid( -g max )
-core( -input 02.vob ) -azid( -g max ) -boost( /b=3 )
-core( -input 03.vob ) -azid( -g 3db ) -boost( /disable )
:

Maybe you could even disable the normalisation when boosting is used, just add the normalisation gain into the boost gain. Or am I wrong here?!
probably right ;) but i'm not sure if the azid process would be faster..

[LigH]

Originally posted by DSPguru
please give a specifiec example, 'cause all my tests showed no problem.

-core( -input "j:\VIDEO_TS\vts_17_([0x83]_Audio_Deutsch_AC3(6Ch)_48kHz___)_Delay_0ms.ac3" ...
does not work

-core( -input "j:\VIDEO_TS\stream0x83.ac3" ...
works fine

Therefore I thought the parentheses in the filename could be the reason. I'll send you the complete string by PM.

Originally posted by DSPguru
so, substream of all vobs would be 0x80, and the gain for all files would be the Maximum-gain found for the first vob (01.vob).

So if the audio in the first VOB is weak and gets stronger later (usually the final showdown is the loudest part), but the maximum gain is only calculated over the first VOB, then the audio could clip after the first VOB - dangerous...

And if one sets a -azid( -g max ) into each line of the list file, is the maximum gain calculated for each VOB separately? Then you will hear loudness differences between each part - annoying...

[DSPguru]

-core( -input " j:\VIDEO
mayB the problem is with the space after the quote. try removing it.

So if the audio in the first VOB is weak ........ Then you will hear loudness differences between each part - annoying...

man, i'm not going to tell my users what to do. i gave them maximum flexabilty to set manual&automatic gain for all vobs, or for each vob.

It seems that the dialog normalisation and the back channel filtering are unsupported by BeSweet
not a problem, i will support it on v0.9 :).

[LigH]

Originally posted by DSPguru
mayB the problem is with the space after the quote. try removing it.

There is no space between the first quote and the drive in my original command string. This must be a mistake while quoting in this forum.

[DarkAvenger]

Hey Ligh and DSPGuru, if you discuss the automatic booster stuuf, don't forget me! :)

[DSPguru]

@LigH
ok, so i'll check that out.

@DarkAvenger
NP :)

[DanniDin]

@DSPguru
The Problem in the File Name is the "(" and ")"

Danni.

[DSPguru]

10x DD. helpful as always :)
btw, -f & -n are supported now.

LigH,DD,
what was BeSweet's error message you got ?
again, all my tested showed that it do get the whole filename.

[DanniDin]

:)

[LigH]

No error message, just the "Usage:" display. (BTW: I run it under Win98SE)

[DSPguru]

so it's probably because you forget to set the "-output" switch.

[DanniDin]

@DSPguru
Try Copying a File and You'll See that "Copy (2) of stream0x80.ac3" Doesn't Work.

It's Because of the () You Use in Order to Seperate the Programs

It Happens to Me All the Time.

Danni.

[DSPguru]

damn right !

fixed :).