PDA

View Full Version : BeSweet GUI : Windows XP ?


user
10th January 2002, 23:22
Hi all,

this is my first post to this very interesting forum.

Let me introduce first:

Perhaps some people know me already from german www.dvdboard.de as Grundig-moderator or by test report of TYT 2000 & clones at www.dv-rec.org, from Scan-TYT&clones-Yahoo-group or from MP3 groups, user as originator of "List of actual recommended Lame settings" at www.hydrogenaudio.org and www.r3mix.net forum.


Since some time I was using azid, toolame for converting audio of my SVCDs. I stayed at 48 kHZ, because TYT&clones could play 48 kHZ mp2's very well.


Then I found here BeSweet. Wonderful GUI !

So it was easy to convert ac3 2 wav@48 2 wav@44.1 2 mp2 in one step with best freeware programs available !!!

Here are my first wishes:
Using besweet, you can only use green marked options. At ssrc there is missing 2pass to avoid clipping.
In future some more green options would be welcome !


So all worked well with Win98SE.

But then I tried Win XP.
And now I get some errors if I select the *.exe files in GUI or in GUI selecting the files I want to convert.

Then GUI crashes.

Could the reason be that after installing new windows I have to delete all in directory of BS and have to install BS complete new ?

Or is this problem (Besweet & XP) known and worked on ?

UHT
11th January 2002, 01:54
im packing xp with the same setup, works fine

MaTTeR
11th January 2002, 02:56
Welcome to the forum bro.

Yep, I can verify the GUI works fine on XP. Did you upgrade your 98SE to XP? If so that's always a bad idea. When using M$ software, always do a clean install.

user
11th January 2002, 08:15
I did a clean install. I kept only my own files, documents, program installation files.
Then deleted everything related to MS, windows etc.
Good to know that BeSeetw runs well on your XP. So I am going to try on.

Doom9
11th January 2002, 10:56
xp here too.. works on both of my boxes. And.. since internally besweet works in 32bit floating point mode I don't think there's a need for 2 pass.. you shouldn't get any clipping when staying in the float space.. especially not if you have 32bits to work with

ChristianHJW
11th January 2002, 12:26
in fact SSRC 2 pass is
- impossible to implement for BeSweet. Remember ther are no intermediate WAV files with BeSweet and thats were SSRC is doing its 2 passes on
- not necessary. Normalizing is done in BeSweet by defining an suitable amplification factor for Azid in 1st pass and apllying this on 2nd pass. Best possible method to do normalizing.
Special BeSweet feature : No clipping when higher DRC values are used like with standard Azid ( azid.exe ), as DSPguru did it his own way, he isnot using -g in Azid ...

Only wishes remaining for BeSweet is maybe

- 16 bits output switch for SSRC output. Thus resampling could be done in floating point ( 24 or 32 bits ) with high precision and output be written to 16 bit WAV file. SSRC.exe can do this as standard.
- a few more lame options, as supported by lame 3.91
- toolame.dll instead of mp2enc.dll for Mpeg 1 Layer II . Better quality ?
- 0.5 - 1 dB attentuation in SSRC on downsampling to avoid overflows ( almost impossible, but may happen in worst case )
- Speed like HeadAC3He :D .... at least if being used on Raid 0 !

Regards Christian

DSPguru
11th January 2002, 12:59
Hi Christian, my man !

2-pass ssrc iZ possible to implement. i just didn't think it was needed.

you can create 16bit output wav. here's the command :
-core( -input in.ac3 out.wav -2ch ) -ssrc( --rate 44100 )

1) a few more lame options, as supported by lame 3.91
2) toolame.dll instead of mp2enc.dll for Mpeg 1 Layer II . Better quality ?
3) 0.5 - 1 dB attentuation in SSRC on downsampling to avoid overflows ( almost impossible, but may happen in worst case )
4) Speed like HeadAC3He .... at least if being used on Raid 0 !
1. already an action item.
2. i guesss toolame Iz better. but didn't find toolame.dll, and pretty tired of creating dlls all day ;)
3. it's possible. use -ota( -g -0.5bd ) .
4. hehe, i prefer to focus on signal-processing, not on copmuter programming :D.