Until very recently, changing the frame rate from 25 to 24 was an easy thing.
I simply selected DnxHD and went for it. Since things have changed with DnxHD and ProRes in Premiere, the conversion process seems to have become all but impossible as I get a really irritating little stutter - almost as if a frame has been dropped somewhere, and it is making the process next to impossible.
There are 3 modes: Frame Sampling, Frame Blending & Optical Flow and each has their problems on this particular footage. FB causes some of the people to appear as if they have 4 legs each. The ghosting is all over the place & unacceptable. Optical Flow is exactly the opposite of what it claims - it looks terrible, and Frame Sampling is causing not only the stuttering effect vbut has an almost complete image break-up on one particular scene.
So the BIG question is - how can I get this frame rate conversion done without changing the run time duration? Yes, I can interpret the footage as 24 instead of 25, and create a new sequence & yes I understand this is how it is normally done - but that adds 4% to the run time and alters the audio speed & pitch, which is unacceptable.
I have also tried Topaz Labs Video tool, using the Cronos AI which is designed for the job and it looks fantastic - but the result plays out either 18 seconds too quickly (converting to 24 fps) or 8 seconds too quickly (converting to 23.976 fps) so that's no use either.
I feel a lot like Edison when he was trying to make an incandescant light bulb and famously said he had found 'thousands of ways not to make one' (or something along those lines, anyway) and have put so far last week 100 hours & $800 cash and still all I have done is found ways not to do this.
What irks me more than almost anything though is that this process used to work right up until very recently, so what has changed to cause this to start happening, please?
Finally - does anyone have any suggestions? FS looks the best apart from this seemingly 'dropped' frame every so often and at least it maintains the correct run time. I wonder if running a Topaz Repair, or a slo-mo would fix the issue?
... View more