> CL-Interface:
> [Options] <Sourcefile 1>...[<Sourcefile x>]

> comment:
> CL loads all GUI components without showing them (except [-g]).
> Input via CL-I is used as 1 job.

> no options
> starts the GUI
> an existing ini-file in the current working directory is read and overwritten on close.

> options:
> -c <ini_file>
> if a different ini-file is given it must be provided with the full path to load correctly. this option overwrites all standard settings.
> not all settings must be given, missing settings are set to the standard.
> all options for the GUI including the post-commands are directly controllable via the ini-file, except the user variables like [-n,p,i]/Sourcefile.

> -dvx1
> sets the 1st option for createing a .d2v projectfile

> -dvx2
> sets the 2nd option for createing a .d2v projectfile
> sets the options for appending a RIFF Wave Header for AC3 files

> -dvx3
> sets the 3rd option for createing a .d2v projectfile
> sets the options for appending a RIFF Wave Header for MPEG audio files

> -dvx4
> sets the 4th option for createing a .d2v projectfile
> sets the options for appending a RIFF Wave Header for AC3 files
> sets the options for appending a RIFF Wave Header for MPEG audio files

> these options can't be used together!
> the next options are independant but must be given after the first options (if used) or directly after the programname.

> -o <outputpath>
> overwrites the current settings for the <outputpath>, this must be a full path.

> -n <filename>
> forces this <filename> as a basename for all output files (without path).
> (option not available for the GUI)

> -p <cut-file>
> the given <cut-file> has to be provided with the full path and. it contains the cut-points (text, lineoriented).
> parsing is done based on the current cut-mode -> ini-file, std = bytepos. cut

> -i <token1,token2,..>
> provides (P)IDs for selected editing, several separated by comma. These are then used exclusively.

> -l
> creates a standard logfile

> -g
> starts the GUI with all given parameters instead of starting the job at the command line.
> changes in the GUI settings and are not written to the ini-file.

> <sourcefile 1..x>
> the sourcefiles inlcuding the full path for this job must be provided at the end of the command line in the correct order.

> To create a special ini-file, run the GUI, set all options accordingly, exit the GUI and save the ini-file under a different name.