Post #493566

Darth Mallwalker said:

Using the VOBs directly would give you PGC_2 first (15 frames) followed by PGC_1 (main feature.) So I would have thought the total frame count would be higher by fifteen. Yet you say it's the same when you use the VOB method? That's very weird indeed.

Darth Mallwalker said:

Not sure you've missed anything, but emphatically I say No it's not normal, even for NTSC.
I'm glad you're asking these questions, and not simply accepting it, because it shouldn't be that way.
Hope I can help to figure out the anomally. So far I'm stumped...

Can you try turning on PGCDemux Logfile, and also "Include end time" in CellTimes.txt, then post both files here or somewhere.

Darth Mallwalker said:

This statement befuddles me because I've never seen frame counts listed whenever I run PGCDemux (except in the Logfile, but you had that turned off.)
Where in PGCDemux are you seeing the frame count?
Can you make a snapshot of PGCDemux, where "174262" is displayed on-screen? That might help to give me a sense of context.

Finally if I can be so bold to list what I believe are the correct answers for STAR WARS:
PGC_1 contains 174261 frames.
Both AviSynth and VirtualDub call the first frame 0, so the last frame will be called 174260.
(Other programs might start with 1, as Chewtobacca already mentioned.)

Skipping PGCDemux, and DGIndexing the VOB files directly ought to yield 174276 frames. That's 15 from PGC_2 + PGC_1's 174261.
Again VirtualDub and AviSynth both count from zero, so
last frame of PGC_2 is called 14
first frame of PGC_1 is called 15
last frame of PGC_1 is called 174275