Originally Posted by sneals2000
The 24p slow-downs yes, the 50i to 59.94i conversions no.
The 50i to 59.94i conversions will be using high-end frame vector-tracked motion-compensating interpolation process (likely to be Snell's Alchemist Phase Correlation technology) which would be pretty close to impossible to unpick.
The Doom9 thread that I started is: http://forum.doom9.org/showthread.php?t=163769
It seems that the 25 fps was slowed down to 24.975 fps and them converted using the 2:3:2:2:3 conversion pulldown. There is a response noting the pulldown if 25 -> 29.97 was used,.
Why do I think that slowdown was done first? I took a 10 minute sample of the program and did "tdecimate(cycle=30, cycleR=5)" in the AVS script and the whole 10 minutes was converted without issue.
I'm not going to attempt to speed it back up to 25 fps, as I don't really want to tear apart the AC32.0 audio and speed it up as well. As long as the program is, there is a good chance that it will be out-of-sync at the end.
I think my Blu-ray player will play it from a MKV file. Don't know what would happen if I try and author it at 24.975p, since that is an illegal frame rate.
The program looks so much nicer watching it at 24.975p, vs the 2:3:2:2:3 pulldown conversion. The judder is kind-of annoying. VLC even has issues trying to match it to the 60 Hz display rate of the monitor connection, where split screen issues can be seen. At 24.975, the motion is smooth and there are no display issues.