Green frame on second frame of d2v?

[Adub]

Hey, neuron2, I just noticed this recently.

I am using the version of DGindex that ships with MeGUI's autoupdate (1.5.2)

When I load the m2v file from this thread:
http://forum.doom9.org/showthread.php?p=1174310#post1174310

And load a simple script like this:
DGDecode_mpeg2source("C:\Documents and Settings\****\Desktop\VTS_01_1.demuxed.d2v",info=3)

If I load that script into virtual dub and step through the first couple frames, I get a green frame with a black dot in the right hand corner. Can you replicate this?

The rest of the clip is fine, but the 2nd frame is just...green.

[HymnToLife]

The M2V seems corrupted, DGIndex throws me a warning near the end of the process (and I have the green franme too).

[Adub]

Yes, I get that to. However, is that what is causing the green frame? I wish I knew where the field order transition took place.

[Guest]

It's a bad stream. What's to explain?

When you correct the field order transition it shows you the location.

[Adub]

Ah, okay. I thought that was the case, it's just that I had seen this somewhere else recently, but that was a corrupted stream as well.

But is this okay? Chances are that he created that stream using the cutting mechanism of DGindex and demux. Shouldn't this produce a valid file? Or am I wrong?

[Guest]

Chances are?!

If you can produce a problem doing it, please make a thread about it. You're right, cutting with DGIndex should not produce a stream like that.

Don't get me wrong, I really appreciate your trouble reports and the useful feedback you've given me in the past!

[Adub]

Okay, I will try and make some tests of my own. I haven't seen any problems except for other peoples files, so it could be just their fault.

Edit:

Okay, I can confirm the green frame bug. At least, for what I understand it to be.

To reproduce, take a vob. Any will do, I used the same vob available in my "Really messed up Anime source. CHALLENGE!!" thread.

Use the selectors to create a region in the middle somewhere, doesn't matter.

Save and demux. Now, the d2v created here works fine. So delete this.

Load the newly created example.demuxed.m2v into dgindex and save a new d2v.

Load using just this:
DGDecode_Mpeg2source("example.demuxed.d2v")

Drop the script into Vdub, and you should encounter a green frame on one of the first couple frames.

[Adub]

Okay, i just encountered this again today. neuron2, can you confirm?

[Guest]

I just ran into it myself today. I'll try to figure out what's happening this evening.

My workaround: freezeframe(1,1,0) :)

[Adub]

Great! I am glad that it at least has been confirmed.

[Guest]

I never doubted you. :)

I had a copy of the source laying around at work, so I had a look. I found and fixed the problem and will release the fix tonight. I want to add a few other things as well as long as I'm making a release.

The problem was that I start processing the file once to count the number of leading B frames and then again to start the main indexing. But I started demuxing at the start of the first processing, so I ended up demuxing an extra partial copy of the first GOP. Now I start the demuxing before the main indexing pass begins.

Thank you for pointing this out.

[Adub]

Good to know that you were able to pinpoint the bug so fast! I look forward to the next version with eagerness then!

[Guest]

See here:

http://forum.doom9.org/showthread.php?p=1207367#post1207367

[Adub]

Great, thank you very much. I am updating as we speak.