Log in

View Full Version : Besweet 1.5b23 AAC encoding cap?


K-Dash
27th November 2003, 02:52
This used to work so well for the previous couple weeks untill now, and what I thought this could be is the 50 encode cap on standard NERO ver where you have to buy for the unlimited AAC encoding as an additional offer. But I'm not 100% sure so I'll just post the error msg here:

e:\besweetv1.5b23\BeSweet -core( -input 1 AC3 T01 3_2ch 384Kbps DELAY 0ms.ac3 -output 1.mp4 -logfilea e:\BeSweet.log ) -ssrc( --rate 44100 ) -bsn( -config -2ch )

[00:00:00:000] +------- BeSweet -----
[00:00:00:000] | Input : 1 AC3 T01 3_2ch 384Kbps DELAY 0ms.ac3
[00:00:00:000] | Output: 1.mp4
[00:00:00:000] | Floating-Point Process: No
[00:00:00:000] +-------- AZID -------
[00:00:00:000] | Input Channels Mode: 3/2, Bitrate: 384kbps
[00:00:00:000] | Output Stereo mode: Dolby surround compatible
[00:00:00:000] | Total Gain: 0.000dB, Compression: None
[00:00:00:000] | LFE levels: To LR -INF, To LFE 0.0dB
[00:00:00:000] | Center mix level: BSI
[00:00:00:000] | Surround mix level: BSI
[00:00:00:000] | Dialog normalization: No
[00:00:00:000] | Rear channels filtering: No
[00:00:00:000] +------ Shibatch -----
[00:00:00:000] | Source Sample-Rate: 48.0KHz
[00:00:00:000] | Dest. Sample-Rate: 44.1KHz
[00:00:00:000] | Attenuation : 0.0db
[00:00:00:000] +---------------------


And right before the "Finalizing" file a crash msg pops up saying:
"Besweet.exe has generated errors and will be closed by Windows
You need to restart the program."

tiki4
27th November 2003, 09:22
You have to give a fully qualified path for the output file.
On my system BeSweet doesn't produce any output if I don't give the full path.

tiki4

P.S. ... and also remember to give some -azid() section to your command line. I'm not sure what BeSweet does if you omit this. Try to use OagMachine to get a feeling for the command line you need to specify.

K-Dash
27th November 2003, 09:41
Interesting, thanks. So this is why it didnt spit out some other times as well.