Ambiguous Field Order

bsmith1593 · 20th February 2011, 21:51

I have a video that has an ambiguous field order, and I do not know what to do. DGIndex reports the field order as TFF, and when I tested the field order in VirtualDub, the video flowed perfectly. However, it also flowed perfectly as BFF. When I plug the video into my main script [with Telecine(post=0) and TFM(slow=2,cthresh=255)] with both orders, I see no difference. Does this video not really have a field order? I am highly confused. Thank you for your help.

55-second clip: http://eva.adriels.com/miscellaneous/VTS_03_1.m2v

Field Order script:

Code:

mpeg2source("C:\PROGRA~1\GORDIA~1\D2Vs\Who Said.d2v")

AssumeTFF().SeparateFields()

Main script:

Code:

mpeg2source("C:\PROGRA~1\GORDIA~1\D2Vs\Who Said.d2v")

AssumeTFF()
Telecide(post=0)
TFM(slow=2,cthresh=255)
# vinverse()
# TDecimate()
# UnDot()

# T-?, B-?, L-?, R-?

NOTE: For those who will comment about it, I have a reason for having two field matchers. I tried both Telecide() and TFM() separately. Telecide() found some better matches than TFM(), and TFM() found some better matches than Telecide(), so I use them both. In other words, Telecide() might have found good matches for frames 2 and 4 but not for frames 6 and 8, while TFM() might have found good matches for frames 6 and 8 but not for frames 2 and 4. Also, I am sorry if this is in the wrong section. It concerned AviSynth, so I put it in this section.

TheSkiller · 21st February 2011, 19:03

The field order does not matter because that video in fact is not interlaced (anymore).
Also it has never been telecined (which is totally typical for a TV recording and makes sense). That means decimate is redundant and will kill the last bit of temporal quality that is left.

It seems like it has been (very badly) blend-deinterlaced (for example at frame 1342 look at the fingers, that was blend-deinterlaced).
What you probably see as interlacing are the remains of the original interlacing, they are there due to the poor deinterlacing.
I wonder why it has been deinterlaced at all, TV engineers these days.

You should try QTGMC with inputtype=1 or 2 or 3 to improve the quality.

bsmith1593 · 21st February 2011, 21:54

I'll have to download and try. Thank you. Also, this is a DVD source, not TV. Disney has some MAJOR explaining to do!

20th February 2011, 21:51	#1 \| Link
bsmith1593 Registered User Join Date: May 2009 Posts: 24	Ambiguous Field Order I have a video that has an ambiguous field order, and I do not know what to do. DGIndex reports the field order as TFF, and when I tested the field order in VirtualDub, the video flowed perfectly. However, it also flowed perfectly as BFF. When I plug the video into my main script [with Telecine(post=0) and TFM(slow=2,cthresh=255)] with both orders, I see no difference. Does this video not really have a field order? I am highly confused. Thank you for your help. 55-second clip: http://eva.adriels.com/miscellaneous/VTS_03_1.m2v Field Order script: Code: mpeg2source("C:\PROGRA~1\GORDIA~1\D2Vs\Who Said.d2v") AssumeTFF().SeparateFields() Main script: Code: mpeg2source("C:\PROGRA~1\GORDIA~1\D2Vs\Who Said.d2v") AssumeTFF() Telecide(post=0) TFM(slow=2,cthresh=255) # vinverse() # TDecimate() # UnDot() # T-?, B-?, L-?, R-? NOTE: For those who will comment about it, I have a reason for having two field matchers. I tried both Telecide() and TFM() separately. Telecide() found some better matches than TFM(), and TFM() found some better matches than Telecide(), so I use them both. In other words, Telecide() might have found good matches for frames 2 and 4 but not for frames 6 and 8, while TFM() might have found good matches for frames 6 and 8 but not for frames 2 and 4. Also, I am sorry if this is in the wrong section. It concerned AviSynth, so I put it in this section. Last edited by bsmith1593; 20th February 2011 at 22:37.

21st February 2011, 19:03	#2 \| Link
TheSkiller Registered User Join Date: Dec 2007 Location: Germany Posts: 632	The field order does not matter because that video in fact is not interlaced (anymore). Also it has never been telecined (which is totally typical for a TV recording and makes sense). That means decimate is redundant and will kill the last bit of temporal quality that is left. It seems like it has been (very badly) blend-deinterlaced (for example at frame 1342 look at the fingers, that was blend-deinterlaced). What you probably see as interlacing are the remains of the original interlacing, they are there due to the poor deinterlacing. I wonder why it has been deinterlaced at all, TV engineers these days. You should try QTGMC with inputtype=1 or 2 or 3 to improve the quality. Last edited by TheSkiller; 21st February 2011 at 19:06.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

21st February 2011, 21:54	#3 \| Link
bsmith1593 Registered User Join Date: May 2009 Posts: 24	I'll have to download and try. Thank you. Also, this is a DVD source, not TV. Disney has some MAJOR explaining to do!