BeSweet CLI Parameters

moonwatcher · 27th January 2003, 04:03

DSPGuru,
Do you suppose its possible to make Besweet process script files in addition to the CLI interface, for those of us who prefer to use scripts over GUI's

Something like a -f switch that will process a special script file (say .BSI files) that will have an XML style that is more comfortable. For now I simply write dos .bat files with the correct CLI, but it’s a bitch to look at as it is all in one text block, Something like:

<core>
<input>
"M:\Process\FELLOWSHIP\FELLOWSHIP.ac3"
</input>

<output>
"M:\Process\FELLOWSHIP\FELLOWSHIP.ogg"
</output>

<logfile>
"M:\Process\FELLOWSHIP\FELLOWSHIP_BeSweet.log"
</logfile>
</core>

<azid>
-s stereo
</azid>

<ota>
-norm 0.97
</ota>

<ogg>
-q 0.500
</ogg>

DSPguru · 27th January 2003, 18:19

use BeSweet's listfile feature.
two examlpes can be found here :
http://DSPguru.doom9.org/cli.html

moonwatcher · 27th January 2003, 18:29

yes, well the fact of the matter is that the file addresses are much longer in my case, and I get a 4 line CLI, and I cant put a new line character because BeSweet doesn't like it, and I end up with a very very long CLI...

I don't like GUIs and I like to keep all the scripts I used for past encodings, this way if I have a movie that has the same qualities as something I did in the past, I can reuse the scripts with minor changes.

Don't get me wrong, BeSweet is great for use with CLI, but I wish the scripts would be more readable.

If I implement the parser, will you consider including it? (Is BeSweet C++?)

27th January 2003, 04:03	#1 \| Link
moonwatcher a cat nurse Join Date: Apr 2002 Location: Haifa.Israel. Posts: 24	BeSweet CLI Parameters DSPGuru, Do you suppose its possible to make Besweet process script files in addition to the CLI interface, for those of us who prefer to use scripts over GUI's Something like a -f switch that will process a special script file (say .BSI files) that will have an XML style that is more comfortable. For now I simply write dos .bat files with the correct CLI, but it’s a bitch to look at as it is all in one text block, Something like: <core> <input> "M:\Process\FELLOWSHIP\FELLOWSHIP.ac3" </input> <output> "M:\Process\FELLOWSHIP\FELLOWSHIP.ogg" </output> <logfile> "M:\Process\FELLOWSHIP\FELLOWSHIP_BeSweet.log" </logfile> </core> <azid> -s stereo </azid> <ota> -norm 0.97 </ota> <ogg> -q 0.500 </ogg>

27th January 2003, 18:19	#2 \| Link
DSPguru BeSweet Author Join Date: Oct 2001 Location: On top of a supercompact cardinal Posts: 3,506	no xml use BeSweet's listfile feature. two examlpes can be found here : http://DSPguru.doom9.org/cli.html __________________ FAQs : BeSweet, Audio :readfaq: Homepage : DSPguru's Webpage http://dspguru.notrace.dk/cs.gif Guides : Multilingual Guides of my tools http://dspguru.notrace.dk/1zhelp.gif

27th January 2003, 18:29	#3 \| Link
moonwatcher a cat nurse Join Date: Apr 2002 Location: Haifa.Israel. Posts: 24	yes, well the fact of the matter is that the file addresses are much longer in my case, and I get a 4 line CLI, and I cant put a new line character because BeSweet doesn't like it, and I end up with a very very long CLI... I don't like GUIs and I like to keep all the scripts I used for past encodings, this way if I have a movie that has the same qualities as something I did in the past, I can reuse the scripts with minor changes. Don't get me wrong, BeSweet is great for use with CLI, but I wish the scripts would be more readable. If I implement the parser, will you consider including it? (Is BeSweet C++?) Last edited by moonwatcher; 27th January 2003 at 18:32.