[RESOLVED] Interlaced or not?

Support forum for DGDecNV
Post Reply
User avatar
tormento
Distinguished Member
Distinguished Member
Posts: 233
Joined: Mon Sep 20, 2010 2:18 pm

[RESOLVED] Interlaced or not?

Post by tormento » Thu Mar 07, 2019 5:26 am

I have just sent you a small fragment from The pillars of the Earth.

Sometimes it happens to me that a file is recognized as 25 fps from MediaInfo and DGIndexNV (which gives me a TFF warning in info side bar) and as 50i from eac3to.

Which is which? Are those the two faces of the same medal? IMHO if really interlaced, it should be 50fps in info panel.

Or not?

What is the real format of the chunk I sent you?

User avatar
gonca
Distinguished Member
Distinguished Member
Posts: 698
Joined: Sun Apr 08, 2012 6:12 pm

Re: Interlaced or not?

Post by gonca » Thu Mar 07, 2019 6:01 am


User avatar
tormento
Distinguished Member
Distinguished Member
Posts: 233
Joined: Mon Sep 20, 2010 2:18 pm

Re: Interlaced or not?

Post by tormento » Thu Mar 07, 2019 6:15 am

gonca wrote:
Thu Mar 07, 2019 6:01 am
Try this
Yup, I know. As we are talking in different threads about same aspect, i.e. parsing, I am just throwing some more meat on fire. ;)

User avatar
tormento
Distinguished Member
Distinguished Member
Posts: 233
Joined: Mon Sep 20, 2010 2:18 pm

Re: Interlaced or not?

Post by tormento » Thu Mar 07, 2019 7:34 am

gonca wrote:
Thu Mar 07, 2019 6:01 am
Try this
I have applied the

AssumeTFF()
SeparateFields()

trick and despite the frame are half the size, the progression is aabbccdd but from a to the second a there is a vertical shift of 1 pixel.

So is it progressive? :mrgreen:

User avatar
admin
Site Admin
Posts: 4382
Joined: Thu Sep 09, 2010 3:08 pm

Re: Interlaced or not?

Post by admin » Thu Mar 07, 2019 1:01 pm

It's progressive content. The shift with separatefields() is normal. Think about it and you'll understand why the bottom field appears shifted. If you don't like that effect then step through bobbed fields this way:

DGSource()
DGBob()

User avatar
tormento
Distinguished Member
Distinguished Member
Posts: 233
Joined: Mon Sep 20, 2010 2:18 pm

Re: Interlaced or not?

Post by tormento » Fri Mar 08, 2019 3:55 am

admin wrote:
Thu Mar 07, 2019 1:01 pm
It's progressive content. The shift with separatefields() is normal. Think about it and you'll understand why the bottom field appears shifted. If you don't like that effect then step through bobbed fields this way:
Thanks I will do ;)

My question was about the parsing and TTF showed in the info lateral bar even for progressive material.

It simply reports what the stream tells. True?

P.S: Just picture that eac3to reports it as 50i :shock:

User avatar
admin
Site Admin
Posts: 4382
Joined: Thu Sep 09, 2010 3:08 pm

Re: [RESOLVED] Interlaced or not?

Post by admin » Fri Mar 08, 2019 11:14 am

It's progressive content encoded as interlaced. What is the big deal? That's very common.

Yes, the stream parameters are reported; there is no attempt to determine if the content is actually progressive/interlaced.

Sharc
Distinguished Member
Distinguished Member
Posts: 206
Joined: Thu Sep 23, 2010 1:53 pm

Re: [RESOLVED] Interlaced or not?

Post by Sharc » Fri Mar 08, 2019 11:24 am

25 fps (frames per second) footage must be encoded (or at least flagged as) interlaced for Blu-ray or DVD standards compliance, even when the original content is progressive. DGDecNV reports these streams always as interlaced.
Unfortunately some tools report 25 interlaced frames per second as "25i" while other tools report it as "50i" according to the 50 fields per seconds. This ambiguity is omnipresent, unfortunately.

Post Reply