Virtualdub (vcf) file problem?

[rojmiller]

All the vcf file that Comskip (79_137) produces start with the following 3 lines:
VirtualDub.video.SetMode(0);
VirtualDub.subset.Clear();
VirtualDub.subset.AddRange(0,2);

When I used the vcf file to delete commercials (using both Virtualdub 1.7.8 with mpeg2 plug-in, and VirtualDubMod), it leaves the first 2 frames intact. So I believe this (3rd line) vcf file output is unnecessary and incorrect, and should not be included...

All the subsequent cut points also seem to be increased by a value of 2, i.e.:
VirtualDub.subset.AddRange(9709,28091);
should be:
VirtualDub.subset.AddRange(9707,28091);
e.g., the corresponding txt file reads:
1 9708
for the first cut

Note, I'm not actually using the vcf file for Virtualdub editing. I am using it in Avidemux, because of a similar cut file system. In Avidemux I used the txt file to manually delete the frames specified, and saved the Avidemux job file. Using what appears to be the same descriptors, all the cut points seemed to be out by a value or 2...

Edit: I just tried loading the file in VDub, and manually deleted frames 0 through 9707 (corresponding to 1 through 9708 of the txt file). I saved the resulting vcf file which included the following line:
VirtualDub.subset.AddRange(9707,267150);
This confirms that the first number in all lines past line 3 should be reduced by 2... (and line 3 should not be included at all)

[erik]

The line
VirtualDub.subset.AddRange(0,2);
is supposed to disappear in the next build.
The +2 frames shift is more difficult to find.

[rojmiller]

The line
VirtualDub.subset.AddRange(0,2);
is supposed to disappear in the next build.
The +2 frames shift is more difficult to find.

VDub starts frame numbers at zero, while the txt file starts frame numbering at frame 1. Probably you added 1 instead of subtracted one, from the cutpoint frame number in the txt file?

[erik]

OK, its clear now.
Build 139 is out and should solve it.

[rojmiller]

OK, its clear now.
Build 139 is out and should solve it.

Yes, it appears to be correct now.

Thank you!

[erik]

OK, good to hear