DGIndex 1.0.12 Command Line Usage

[mohn]

How do I use the "Pre-Scale Decision" in the shell?
Either I'm too dumb to use the command line parameters properly, or it isn't implemented.
I've read the FAQ and used the forum's search function, but I couldn't find anything helpful regarding this matter.

[neuron2]

That's not currently implemented in the CLI.

[mohn]

Hi Donald,

is it on your development list?

I'm doing a series (26 episodes) backup, and for each episode two audio tracks are decoded using prescale decision.
So there are 4 passes needed for each episode.
Each pass takes 2 minutes to finish.
2*4*26 = 208 minutes.
Its annoyingly monotonous to push for over 3 hours every 2 minutes the same buttons again and again.
If prescale decision were implemented for the cli, the pc could do the job without any further user input needed,
after writing a batch file, which takes about 5 minutes.

[neuron2]

Help me out here. I've seen the prescale decision stuff in the code but never looked at it or used it. What is it for and how do you use it? Tell me the exact workflow if you did it manually through the menus.

[mohn]

Process for each episode:

1) Open VOB file

2) Check options: Audio-Output Method: Decode to WAV, Audio-Dolby Digital Decode-Dynamic Range Control-Heavy,
Audio-Digital Decode-Dolby Surround Mix Off

3) Choose audio track number

4) Choosing menu item Audio-Dolby Digital Decode-Prescale Decision starts decoding the audio track without any file output.
After this pass in the Status Info there's a number (e.g. 5.51) for audio amplifying used by the second pass.
After clicking the Play Preview requester the information window closes.
The Audio-Dolby Digital Decode-Prescale Decision menu item is now checked (on).

5) After choosing menu File-Save Project the second pass is executed decoding the chosen audio track and writing
the WAV audio file and the .d2v file. When finished, the Information-Status-Info field says 1.00.

6) Uncheck Audio-Dolby Digital Decode-Prescale Decision.

7) Choose another audio track.

8) repeat 4).

9) repeat 5). The Project file is overwritten. End of process.

[neuron2]

How would you see this working in the CLI?

[len0x]

Wouldn't it be simpler to just demux AC3 and run Azid on it to produce WAV file? (normalization can be done during azid step or after on WAV file itself via normalize?)

[neuron2]

I agree. We're planning to remove all that decoding stuff anyway.

[mohn]

@ Donald:

> How would you see this working in the CLI?

Another cli parameter, say -PD=1 (default: 0 no pre-scale decision).
This should trigger for one specific audiotrack a two pass processing, which combines steps 1) to 5).
And for each audio track one cli command call. For example:

DGIndex -IF=[I:\test.vob] -IA=3 -FO=0 -YR=1 -TN=1 -OM=3 -DRC=3 -PD=1 -DSD=0 -DSA=0 -OF [F:\testa1] -Exit


> I agree. We're planning to remove all that decoding stuff anyway.

Oh no! Imagine, the author of one of your most highly estimated programs tells you that he will drop a feature,
which is essential for you. I know of quite a few people, who use DGIndex the same way I do.
To drop audio decoding at all is asking for program spin offs, IMHO.

[mohn]

@len0x

Why should the usage of two different programs be simpler than the usage of just one?
Of course, I could demux and later use azid. But then the audio delay wouldn't be
autocorrected, as it is done now for decoded WAV audio files. Sure, the audio delay is part
of the generated AC-3 audio file names, but then you have to correct the audio delay manually
in VirtualDub(Mod).

DGIndex, the way it is now, is almost perfect for me as a GUI Tool.
All I'm asking for is to use its DRC two pass auto gain feature from the cli.

[len0x]

Originally posted by mohn

Why should the usage of two different programs be simpler than the usage of just one?


If you're using GUI then its obviosuly not simpler, but from CLI it makes no difference whatsoever (you only have to write a batch file once). I do believe that different tools should focus on different things that they do the best. To be honest its the first time I see someone decoding DD audio from DGIndex (we have such fantastic tools like BeSweet - is it not useful anymore?). But that's just IMHO...

[mohn]

Originally posted by len0x
If you're using GUI then its obviosuly not simpler, but from CLI it makes no difference whatsoever (you only have to write a batch file once).

But what about the audio delay I have to fix afterwards (cli batch file) manually in VirtualDub/Mod?
I always thought, DGIndex doesn't touch the demuxed AC-3 files at all.

The audio delay autocorrection for decoded WAV audio files has always been one my favorite
features in DVD2AVI/DVD2AVIdg/DGIndex.

[len0x]

Originally posted by mohn
But what about the audio delay I have to fix afterwards manually in VirtualDub/Mod?

the option to correct delay in audio file on the fly is available in BeSweet...

[mohn]

Originally posted by len0x
this option is available in BeSweet...

Sorry, I meant after running a cli batch file.
I don't want to use another GUI program for 2*(26 episodes).

[len0x]

Besweet is a CLI application, so design a script that extracts delay from the file name and puts it as BeSweet parameter.

[mohn]

Originally posted by len0x
Besweet is a CLI application, so design a script that extracts delay from the file name and puts it as BeSweet parameter.

Ouch! I totally forgot that. Your're right, and thank you very much! This solves my cli problem.
I still would have preferred an integrated prescale decision feature for DGIndex's cli usage, though.

Looking at the GUI side, I still hope Donald doesn't drop the AC-3 audio decoding completely in future DGIndex versions.