A PC solution is straight forward with avisynth or vdub, but I think he captured it incorrectly, because vdub shouldn't be spitting up that error
As suggested earlier, I would try re-capturing with WinDV first, then I can provide more detailed instructions
It looks like he blend deinterlaced it (that's why ~every 3rd frame is "ghosted"), and changed the fps to 25 by decimating frames (or maybe youtube did it). A straight IVTC should return 23.976 (24000/1001 exactly), and a straight deinterlace would return 29.97 (30000/1001 exactly) with every 5th frame "ghosted" if you used blend deinterlacing
If your camera has a 24pA mode (2:3:3:2) , this is supported natively by Premiere and it will work properly without these extra steps
If you shot 24p standard (24p in 60i - or 2:3 cadence) , then you need these extra steps
As suggested earlier, I would try re-capturing with WinDV first, then I can provide more detailed instructions
It looks like he blend deinterlaced it (that's why ~every 3rd frame is "ghosted"), and changed the fps to 25 by decimating frames (or maybe youtube did it). A straight IVTC should return 23.976 (24000/1001 exactly), and a straight deinterlace would return 29.97 (30000/1001 exactly) with every 5th frame "ghosted" if you used blend deinterlacing
If your camera has a 24pA mode (2:3:3:2) , this is supported natively by Premiere and it will work properly without these extra steps
If you shot 24p standard (24p in 60i - or 2:3 cadence) , then you need these extra steps
Last edited: