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. |
26th February 2013, 23:00 | #22 | Link |
Registered User
Join Date: Nov 2009
Posts: 50
|
Ah... here we go. It has a montage with a decent array of motion.
http://www.mediafire.com/?039o9yve05n0b5u I've DEFINITELY watched through this one all the way. *EDIT* Added a better clip... keep an eye on the log on a conveyor belt going into a chipper about halfway through. The problem gets really obvious there. Most of the other times it happens are when people are talking, which you asked me to avoid. Last edited by Monkeylord; 27th February 2013 at 00:40. |
27th February 2013, 15:33 | #23 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
I'm not seeing any residual combing with this script (except for some mouth combing that can be attributed to match failure and which postprocessing will mitigate):
dgsource("Metalocalypse S3 Sample 1.dgi") assumebff() telecide(post=0) # Use version 5.2.4 with Avisynth 2.6 decimate() I don't see anything I would attribute to incorrect field order. The animation is not completely smooth but that is due to the low animation rate, not any pathologies, as far as I can see. Please describe the problem that you see by referring to specific frame numbers in your sample. There is a field order transition at the end of the sample, but that could be due to your cutting. Last edited by Guest; 27th February 2013 at 17:07. |
27th February 2013, 16:13 | #26 | Link |
Registered User
Join Date: Nov 2009
Posts: 50
|
I managed to have a quick look on my laptop, and it seems that if I set it to TFF then there's tons of bad matches, but if I set it to BFF then there's a tiny amount of bad matches.
The bad matches in BFF mode are correct in TFF, so there seems to be field order transition error happening. Would it be an idea to set up 2 versions of the video, and where BFF produces a combed frame have avisynth replace it with the good version from a TFF file? (I have no idea if what I just typed made any sense) For example, using: AssumeTFF() Telecide(post=0) Decimate() In my sample, this causes frames 794, 798, 801, 804, 807, 811, 818, 821, 824, 827, 830 and 834 to have interlacing left behind, but: AssumeBFF() Telecide(post=0) Decimate() In the same range causes only frame 835 to have interlacing artifacts. Last edited by Monkeylord; 27th February 2013 at 16:26. |
27th February 2013, 17:21 | #30 | Link | ||
Registered User
Join Date: Nov 2009
Posts: 50
|
Quote:
Quote:
On a serious note though, you've helped me learn a lot over these past couple of days (previous clip content faux-pas, included!). What I think I'll have to look into is how to generate a list of just the frames that need switching, and then how to switch the parity on just those ones. It's as much in the learning experience as it is the "getting it right" for me, at this stage. |
||
27th February 2013, 21:41 | #31 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Don't assume the parity is wrong for one frame! That's a leap you are making without cause. I'll look again this evening as I said.
A bad match just means that the matcher is not perfect, it doesn't mean that the frame has wrong parity. Have you tried pattern guidance? |
28th February 2013, 02:04 | #33 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Frame 835 looks clean to me with this script:
dgsource("Metalocalypse S3 Sample 1.dgi") assumebff() telecide(post=0) decimate() and with this one: mpeg2source("Metalocalypse S3 Sample 1.d2v") assumebff() telecide(post=0) decimate() What source filter are you using? |
28th February 2013, 02:07 | #34 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
In some cases Telecide() does better and in some cases TFM() does better.
TFM/TDecimate have more features than Telecide/Decimate, but for what we do here they should be close in results. Last edited by Guest; 28th February 2013 at 02:16. |
28th February 2013, 02:44 | #35 | Link | |
Registered User
Join Date: Nov 2009
Posts: 50
|
Quote:
Here's my exact script Code:
mpeg2source("C:\Temp\Split\Metalocalypse S3 Sample 1.d2v") AssumeBFF() Telecide(post=0, show=true) decimate() The interlacing is on the log. It's the only thing moving in the frame. I used separatefields() earlier, and navigated to the fields for that frame and it gives the telltale forward/backward jerking of the wrong field order, wheras all the frames leading up to it show the log progressing smoothly along. Last edited by Monkeylord; 28th February 2013 at 02:54. |
|
28th February 2013, 05:27 | #36 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
That frame for me is 959 after decimation, so I don't know how you get 834. And that frame is clean for me. Are you using the exact same sample you uploaded?
Anyway, I can't duplicate your result. The only differences I see is that you have Decomb 5.2.3 and you use VirtualDubMod. Can you try Telecide 5.2.4 and use plain vanilla VirtualDub? Last edited by Guest; 28th February 2013 at 05:35. |
28th February 2013, 13:16 | #37 | Link | |
Registered User
Join Date: Nov 2009
Posts: 50
|
Quote:
Thanks so much for all the help. I've learned a lot through all this turmoil. |
|
28th February 2013, 17:53 | #40 | Link | |
Registered User
Join Date: Feb 2002
Location: California
Posts: 2,695
|
Quote:
Last edited by johnmeyer; 28th February 2013 at 17:55. Reason: added link to my third post |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|