DGIndex Batcher v1.18 (17 Apr 2018)

[StainlessS]

Yes I know, as I said, the batcher does NOT touch the log at all, only DGIndex touches that file.
See my previous post 1st paragraph.

And mods I make in future will still NOT touch the log file, only DGIndex does that.

[videoh]

Yes I know, as I said, the batcher does NOT touch the log at all, only DGIndex touches that file.
You don't have to touch the log file. You just need to issue an F5 to DGIndex, wait a second, and then issue a stop.

[StainlessS]

Yes I know that F5 will start Preview, and ESC [I think] will stop it, we already do that to start preview and get Field Order
from the Preview window, to insert it into the template created AVS file. But, Danette wants it in the log file too, not the AVS file.
The DGIndex log file is only output at all if the option is set in DGIndex Menu/Option/Enable Info Log, and it would require
a significant amount more work just to insert the single missing item into the log, its just not something I'm particalarly
keen on doing [I dont really have much free time now or in the near furture].
If you [VH] do indeed add the Field Order item to the log, then both Danette and I will be very happy (and you will no doubt gain
an enormous amount of satisfaction, knowing that you made us (and probably others) quite delighted :) ]

It would not be a bad idea to have the field order in the log file, even when the batcher is not in use, I always used to wonder why
it was skipped from the log, like it had been overlooked or something.
When using DGIndex [on its own, no batcher] I always make a point of using preview first to see what Field Order says [and aspect ratio,
and Frame type]. It would not be the worst idea in the world for DGIndex to have the ability to insert additional infos into the AVS file on its own, just like it does the filenames and audio delay.
If addtional infos were indeed output to the template created AVS file, might I suggest that the same replacement key names
[or whatever they should be called, eg "__vid__", "__aud__", and "__del__"], be augmented using the existing
names used in the batcher.
The items in double quotes

DGI_Field_Order = "__Field_Order__"
DGI_Stream_Type = "__Stream_Type__"
DGI_Profile = "__Profile__"
DGI_Frame_Size = "__Frame_Size__"
DGI_Display_Size= "__Display_Size__"
DGI_Aspect_Ratio= "__Aspect_Ratio__"
DGI_Frame_Rate = "__Frame_Rate__"
DGI_Video_Type = "__Video_Type__"
DGI_Sequence = "__Sequence__"
DGI_Frame_Struct= "__Frame_Struct__"
DGI_Frame_Type = "__Frame_Type__"
DGI_Colorimetry = "__Colorimetry__"


EDIT: I deliberately used the same pre and postceding double underscore to identify the names,
the same as implemented in DGIndex. I also implemented similar double underscore ident in the
Avisynthesizer_Mod thingy, the original used '%' chars which I thought could be mistaken for something else,
eg "%f" insertion markers used in Avisynth String().

[Danette]

Yes, StainlessS, you captured, exactly, my entire issue and basis for the request. I understand, completely, your time issue and how much value you get for quite a bit more work, and the same for videoh.

As I mentioned, I can build my own macro to utilize the “Preview” function in DGIndex (Esc key does pause the preview for closing purposes) so, I hope neither of you sense any disappointment on my part. I have many such macros and they are relatively simple to do.

[StainlessS]

The Batcher is in no way a Macro, which goes around blindly clicking on the exact same area of screen and with the same timings as when it was recorded.
It has to wait for windows to appear [at whatever size and postion], after finishing whatever it is they were doing, detect error / warning dialog boxes jumping up, or not, and other stuff [eg user messing around with windows when its trying to complete its mission].
If it were just a matter of pressing record and spending a few moments clicking on stuff, before halting record, that would be a doddle.

EDIT: Incidently, AutoIt has a macro recorder amongst its tools, not sure if I've ever used it though.
Just curious, what macro recorder do you use [Maybe Autoit, or AutoHotKey macro recorders ?]
(The stuff above about it not being a macro, is for anybody else reading who might think that it was a macro,
I understand that you did not think it was a macro).

EDIT: The DGIndex and MegGUI batchers purpose, was to save me/others spending an inordinate amount of time sitting clicking through the DGIndex procedure, with long timouts between having to do something, and then having to do the same tedious routine using MeGUI,
with sometimes long pauses between stages [depending upon any kind of pre-processing in Avisynth].
With a task of converting maybe 100 MPEG2 files to MP4, using both DGIndex and MeGUI. You could be sitting there for hours and hours
before you even click on the start encode button in MeGUI. With the batchers [working together, DGIndex calling MeGUI and handing it
info on what it has to do], you could set it going by group selecting the 100 MPEG2s, click OK, then go to the pub. And some long time later it would finish the DGIndex fandango, and pass the remainder of the task to the MegGUI batcher, which would eventually
start the encoding of the MP4s and then auto shut down when all complete.
I dont really need to convert masses of mpegs to MP4 anymore, so I dont often use either batcher.
EDIT: Current versions of MeGUI are quite a bit better than earlier versions. At one time, MeGUI would reload an avisynth script about 5 times when reading a script [before the Preview window appeared]. And then about 7 reloads prior to actually adding to the encode queue. [or maybe the other way around]. So if there was some kind of pre-processing in an avisynth script, it had to be done about 12 times in all, for each script, that could lead to a real tedious task where adding lots of avisynth scripts to the encode queue.

[Danette]

Yes, I understand what you mean about a "macro" being a simple capture-type tool, such as in Word or Excel. It's a nomenclature thing. My "macro" definition is wider than that, meaning that it is a series of commands to do much, if not all, of what you described. It will, e.g.; look at how-ever-many numbers of files I choose, then perform the functions I set, with debugging, as needed, but prescribed by me if I see problems. I do suspect that autoit is more sophisticated.

The program I use is called "Macro Express".

[StainlessS]

I've just had a look at Macro Express, looks quite good, and more than just an action recorder. [$50.00 Std, $70 Pro]
AutoIt and AutoHotkey [the devs split the project] was I think quite similar to M.E. at one time,
started out for use in Operating system rollouts, and post install config.
I think that AutoHotkey is now probably more like M.E. than AutoIt, which evolved into a nearly BASIC like programming language,
with unique GUI/window manipulation abilities, and you can even create simple GUI's like the the Batcher Control dialog box.
[One of the first examples for AutoIt emulates a desktop calculator].

[videoh]

If you issue the F5 and ESC, then the field order should be in the log. I just tested and it's working for me. How long did you wait between F5 and ESC?

[Danette]

I've just had a look at Macro Express, looks quite good, and more than just an action recorder. [$50.00 Std, $70 Pro]

I can’t comment upon the current Macro Express version. My current version is about five years old and I assume that it has evolved somewhat since then. However, it still handles everything I’ve thrown at it and I’ve been using it for about twenty years.

If you issue the F5 and ESC, then the field order should be in the log. I just tested and it's working for me. How long did you wait between F5 and ESC?

Although I haven’t fully developed my own Macro Express “macro” for running just a log file, I can confirm that the F5 and ESC does set the field order with about a five-second run (haven’t tried less than that). My plan would be to allow about thirty seconds, just to increase the confidence in the data that it finds.

[videoh]

5 seconds should be enough.

[StainlessS]

Thankyou, but, I'm hittin' a dead end.

Loading DVD vob and pressing F5, wait about 20 seconds and then hit ESC, followed by closing DGIndex, I get this

Stream Type: MPEG2 Program
Profile: main@main
Frame Size: 720x576
Display Size: 720x576
Aspect Ratio: 4:3 [2]
Frame Rate: 25.000000 fps
Video Type: PAL
Frame Type: Interlaced
Coding Type: B
Colorimetry: BT.470-2 B,G
Frame Structure: Frame
Field Order: Top
Coded Number: 490
Playback Number: 490
Frame Repeats: 0
Field Repeats: 0
VOB ID: 1
Cell ID: 1
Bitrate: 4.236 Mbps
Bitrate (Avg): 4.359 Mbps
Bitrate (Max): 4.535 Mbps
Audio Stream: 80: AC3 2/0 224
Timestamp: 0:00:19
Elapsed: 0:00:19
Remain: FINISH
FPS: 24.96
Info:

which is nice.

But, Load VOB again into DGIndex, press F5, wait for about 20 seconds, hit ESC,
and then, F4 (save project), I get this

Stream Type: MPEG2 Program
Profile: main@main
Frame Size: 720x576
Display Size: 720x576
Aspect Ratio: 4:3 [2]
Frame Rate: 25.000000 fps
Video Type: PAL
Frame Type: Interlaced
Coding Type: P
Colorimetry: BT.470-2 B,G
Frame Structure: Frame
Field Order:
Coded Number: 44024
Playback Number: 480
Frame Repeats: 0
Field Repeats: 0
VOB ID: 1
Cell ID: 1
Bitrate:
Bitrate (Avg):
Bitrate (Max):
Audio Stream: 80: AC3 2/0 224
Timestamp: 0:29:19
Elapsed: 0:00:11
Remain: FINISH
FPS:
Info:

So full save project, loses the Field Order obtained from Preview.

EDIT: In 2nd code block, Coded Number seems to be full project length in frames,
and Playback Number seems to be number of frames Previewed.
EDIT: All above without the batcher thingy.
EDIT: But same results as above when doing same (with modded code) from within the batcher.

[videoh]

Hmm, save project may clear the info. Investigating...

[Danette]

I ran into the same problem when developing the macro using Macro Express. The last "Information" window / log file created, before closing, overwrites any other such file upon closing. To get around it, I ran the "Save Project" first and the "Preview" last. Of course, I'm not doing any of the more complex things that DGIndex Batcher is doing.

[videoh]

To get around it, I ran the "Save Project" first and the "Preview" last. That's very creative, congratulations! Still and all, that should be fixed. I'll get to it after the DGDemux port to linux is completed. I have a linux bug up my you-know-what. Maybe it will make people hate me less, but maybe not. ;)

[Emulgator]

Hi StainlessS, a small wish: open file extension mask for .MTS
Batcher 1.22 can not see camera files with .MTS extension.

[StainlessS]

OK, but on the back burner.

You could add it yourself, source is supplied and only have to (by memory) hit the F5 key to recompile.
[AutoIt compiler and the additional Scite editor for it]

[StainlessS]

Emulgator,
Line 142,

Global Const $FILTER = 'MPG Files (*.vob;*.mpg;*.mpeg;*.m1v;*.m2v;*.mpv;*.tp;*.ts;*.trp;*.m2t;*.m2ts;*.pva;*.vro)'

Just add your new semi-colon separated extension to the list,

ie,

Global Const $FILTER = 'MPG Files (*.vob;*.mpg;*.mpeg;*.m1v;*.m2v;*.mpv;*.tp;*.ts;*.trp;*.m2t;*.m2ts;*.pva;*.vro;*.mts)'


Rebuild is actually F7.

Well, here is just the exe,
https://www.mediafire.com/file/gc97gchevu2m27s/DGIndex_Batcher-%255BEmulgator%255D.7z/file

EDIT: Untested.

[Emulgator]

Deepest Thanks, StainlessS !
.mts are visible now.