Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
5th December 2016, 10:27 | #1 | Link |
Registered User
Join Date: Oct 2014
Posts: 476
|
What kind of interlacing/telecine pattern is this?
I can't make heads or tails of it. It seems to be random interlacing with the chroma off doing its own thing.
http://s000.tinyupload.com/?file_id=...31634349333299 |
5th December 2016, 19:24 | #2 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
This looks like silent film that was probably originally 16 fps.
It's six fields per frame, with a field reversal every frame. This leads to a field out of order every other frame. You can simply decimate with this code: Code:
separatefields() selectevery(6,1,2) weave() assumefps(16) If you instead use IVTC, you can easily get everything looking OK, but I couldn't come up with the right settings to avoid dropping a frame when the fields are out of order, every other frame: Code:
tfm() tdecimate(cycle=6,cycleR=4) assumefps(16) I think this is 100% fixable, but I just don't have the time to fiddle with the code. |
5th December 2016, 20:05 | #3 | Link |
Registered User
Join Date: Jul 2011
Location: Tennessee, USA
Posts: 266
|
What I get is that this has a "top layer" of 3:2 pulldown. I don't see any field reversal. The movie is bottom field first.
Code:
TFM(pp=0).TDecimate() The clip has illegal video levels and clipped brights. I'd inverse telecine with TIVTC and be done with it. Reducing contrast would help keep it from having that DV "cooked colors" look. Last edited by LemMotlow; 5th December 2016 at 22:46. |
6th December 2016, 04:25 | #4 | Link | |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
Quote:
It actually is even more complicated than that because every few frames there is a full frame that has to be extracted from this field reversal mess. This animated GIF shows what is going on. I have separated the video into fields. Pay attention to the slight up/down motion. Each time the picture moves up or down, that is a new field. If you count the number of up/downs until a new point in time is shown, that lets you count how many fields are repeated. Note the back/forward motion of the axe. That is due to the field being in the wrong moment in time. You can't simply switch it because you then get two bottom fields in a row or two top fields in a row. That is wrong. You can never have two top or two bottom fields in a row. Last edited by johnmeyer; 8th December 2016 at 02:39. Reason: Changed hosting service for GIF |
|
6th December 2016, 04:49 | #5 | Link |
Registered User
Join Date: Jul 2011
Location: Tennessee, USA
Posts: 266
|
Indeed, if I set the wrong field order (TFF) and use SeparateFields on telecined video I get the same thing (Does SeparateFields pull telecined fields apart properly? I don't recall it doing so very well). Try BFF and you won't see reverse motion. What you will see with SeparateFields on telecined video is what looks like field blending every few frames, plus duplicate frames periodically, followed by a dropped or missing field.
It's a mess. I'd find a better piece of video to work with. Last edited by LemMotlow; 6th December 2016 at 11:16. |
6th December 2016, 08:12 | #6 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
It is true that with interlaced video, setting the wrong field order will give you the "two steps forward, one step back" jitterbug when you view the video using bob() or separatefields(). However, I don't think that is what is going on here. The first thing I did was to try both AssumeTFF after I initially tried AssumeBFF. They both produced a similar problem because this is not a field dominance issue, but instead is caused by having fields weaved together in the wrong order.
If I get a few minutes tomorrow I'll take another look. As video screw ups go, this one is unusual, but I think it can actually be salvaged and made to look quite good. Of course the film transfer is pretty awful, with serious blown out highlights, but that's another story ... |
6th December 2016, 11:35 | #7 | Link |
Registered User
Join Date: Oct 2014
Posts: 476
|
I just hit it with QTGMC and it watches just fine at 60fps. There's actually 60i video segments interspersed so it certainly works well for those portions. I'm just wondering if there's a better way, since there's definitely some progressive and some telecining that it's certainly not optimal to run through deinterlacing.
The cycle seems to walk (it goes though blending phases every so often), so my guess it would be difficult to get something that would work through all the the shifts, especially with the chroma on its own cycle. |
6th December 2016, 15:40 | #9 | Link | |
Registered User
Join Date: Oct 2014
Posts: 476
|
Quote:
Deinterlacing to 60p is assured not to have lost any good fields and the bad ones go by too fast to notice. It's often the least worst choice for butchered sources. |
|
6th December 2016, 17:26 | #10 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
Having played with this clip, I really cannot agree. The last thing you want to do with this clip is to apply any sort of deinterlacing. Instead, this is almost entirely a decimation problem, with a small additional issue of the chroma on the first dup.
|
6th December 2016, 19:45 | #12 | Link | |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
Quote:
If I have time, I'll give you the decimation and field reweaving code needed to fix this. As I've said previously, this clip can be salvaged quite nicely by using both decimation (IVTC) along with something to better match the fields. There is no interlaced video in this clip. |
|
6th December 2016, 20:09 | #13 | Link | |
Registered User
Join Date: Oct 2014
Posts: 476
|
Quote:
http://s000.tinyupload.com/?file_id=...97613344818263 Last edited by kuchikirukia; 6th December 2016 at 20:27. |
|
6th December 2016, 21:00 | #15 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
I finally had a few minutes and devised a solution which works perfectly (although there are still a few minor chroma issues).
In doing this I realized something I didn't catch before: the first part of the clip and second part of the clip actually have a different cadence. For the first part, you use this code: Code:
tfm(mode=5) tdecimate(cycle=20,cycleR=14) assumefps(16) Code:
tfm(mode=5) tdecimate(cycle=20,cycleR=12) assumefps(16) Code:
ChangeFPS(60000,1001) AssumeBFF() # or BFF, as required SeparateFields() SelectEvery(4, 0, 3) Here's a link to the results of my work on the clip you posted: Recovered Video P.S. I hate posting big files like this, but I don't know what other option I should use that will preserve the original quality, make it easy to inspect individual fields, and be usable by the largest number of people who choose to download it. |
6th December 2016, 21:23 | #17 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
Did you watch what I posted?? I spent quite a bit of time on this and would be interested in whether it does what you expected.
And yes, the later part of the second clip you posted is 60i, although it too has some field issues that will need to be fixed. |
6th December 2016, 23:38 | #18 | Link | |
Registered User
Join Date: Jul 2011
Location: Tennessee, USA
Posts: 266
|
Quote:
|
|
7th December 2016, 00:07 | #19 | Link |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
I don't know whether I'd agree that it has "serious issues" with discarded frames. There is a dropped frame around frame 15 in my uploaded video. There may also be a few on the axe chopping. I was trying to do this in the few minutes I had available, and didn't tune all the TFM and TDecimate parameters. I could probably get better results by using a longer cycle, and possibly a different mode. That is the usual "trick" that solves these problems. Also, I was in a hurry when I chose the CycleR value for the script for the axe chopping. I think that changing that by one would probably fix the problem in the second half of the clip.
|
Thread Tools | Search this Thread |
Display Modes | |
|
|