|
|
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:
lt;coregt;
lt;inputgt;
quot;M:\Process\FELLOWSHIP\FELLOWSHIP.ac3quot;
lt;/inputgt;
lt;outputgt;
quot;M:\Process\FELLOWSHIP\FELLOWSHIP.oggquot;
lt;/outputgt;
lt;logfilegt;quot;M:\Process\FELLOWSHIP\FELLOWSHIP_BeSweet.logquot;
lt;/logfilegt;
lt;/coregt;
lt;azidgt;-s stereo
lt;/azidgt;
lt;otagt;
-norm 0.97
lt;/otagt;
lt;ogggt;
-q 0.500
lt;/ogggt;
use BeSweet's listfile feature.
two examlpes can be found here :
cli.html
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++?) |
|