Log in

View Full Version : DGIndex interlaced content reported as progressive or dgdecode issue


dwrbudr
18th December 2009, 12:19
Hi

I'm trying to rip Lost Season 5 episodic PAL DVD to H264.
Here's a screenshot from DGIndex:

http://i.imagehost.org/0349/Snap1.png (http://i.imagehost.org/view/0349/Snap1)

Then I load this simple script into MPC:

LoadPlugin("C:\Tools\filters\DGDecode.dll")
Mpeg2Source("c:\disc4\vts_11_1.d2v")


Here's a screenshot from MPC:
http://i.imagehost.org/0171/snapshot20091218131000.jpg (http://i.imagehost.org/view/0171/snapshot20091218131000)

MeGUI "analyze" tool reports that the AVS is interlaced, bottom field first.

How from progressive PAL DVD it ends up to interlaced source with such a simple script?! :devil:

What am I doing wrong?

When I later try to encode this with x264 (1500kbps, preset slower), I get occasionaly such output:

http://i.imagehost.org/0079/snapshot20091218131708.jpg (http://i.imagehost.org/view/0079/snapshot20091218131708)

Thanks in advance!

Guest
18th December 2009, 15:14
Post a link to an unprocessed source sample.

If you read the documentation you will understand that the "progressive" indication in DGIndex does not mean what you think it means.

dwrbudr
18th December 2009, 20:01
Ok, I'll post VOB sample tomorrow. But how happens that the picture in DGIndex window is not interlaced?

Guest
18th December 2009, 20:05
The two screenshots you posted are not the same frame. So, e.g., if you have hard telecine, you'll have 3 progressive frames followed by two interlaced one. You can also see things like that with blended fields. That's why I asked for a sample.

scharfis_brain
18th December 2009, 20:12
also it might be the rare occasion of rff-flags within a PAL-Source. (which should be perfectly fine)

but most probably it is telecined/field-blended stuff (which is interlaced) encoded in progressive mode.
that means you chroma will be b0rked all the way.

Anyways a sample is necessary for further investigation.

dwrbudr
19th December 2009, 09:45
I think I've got what's causing this and that's it because I've clicked Yes on the message "Field Order Transition Detected".
Anyway here's is a VOB sample for you:

http://hotfile.com/dl/21136743/7255d17/VTS_11_1.VOB.html

Guest
19th December 2009, 16:06
Correct. If you look at the first few lines of the D2V, you see this:

d00 5 0 2048 0 1 1 90 a0 a0 a0 a0 a0 a0 a0 a0 a0
d00 5 0 34816 0 2 1 d2 f2 e2 f2 f2 e2 f2 f2 e2 f2 f2 e2
900 5 0 61440 0 2 1 72 72 d2 f2 f2 e2
900 5 0 73728 0 2 1 72 72 d2 f2 f2 e2 e2

You can see that the initial black portion is BFF while the video itself is TFF. If you choose to correct field order, it will insert a field that will make all the frames interlaced when served.

Since field order doesn't matter for black video the right thing to do is to *not* correct the field order transition.