The time when there was only NTSC, PAL and SECAM will one day be remembered as the time of great clarity.
Today we have perfect chaos.
As many resolutions as you want, 8bit/10bit/12bit quantization, 4:4:4 ; 4:2:0 ; 4:1:1 ; 4:2:2 …etc
And as many frame rates as you want from 23.97fps to 60fps and more.
As the number of technical possibilities increases, the education/training of media people seems to decrease.
The result is a particularly annoying phenomenon that occurs when footage is shot in 24 or 25 fps, but then somehow 30 fps is supposed to be made out of it. (or the opposite process is the case)
Then every 4th or 5th frame is doubled (or removed), resulting in a stuttering of the movie commonly known as JUDDER.
Is there a model in Topaz that recognizes and removes the doubled images so that you can then convert from e.g. 24 to 60 fps?
I think they attempted to have a resolution to judder with the ‘replace duplicate frames’ check box in the interpolation models, but it has never worked. (It dose to something, but in all the videos I have tried, it makes things worse.)
You can try it out, and maybe you will have more luck than I have.
If they were to make a new model, specifically to solve for those two situations, that would probably be better.
The solution lies not with VEAI but with AviSynth.
Usually this is treated by running detelicine filters on your source. It is non-destructive, but only works if you have access to the proper telecine’d source. Detelecine can performan decimation in multiple formats: 3:2 (29.97 to 23.976) or 25:1 (25 to 24) for instance.
If you only need to remove duplicate frames, TDecimate alone will do the trick, or you may even use SelectEvery to remove 1 frame every N.
In other cases, SRestore works great when it is needed to switch from one frame rate to another in a more complex ways.
Hello,
I tested Chronos with fake 60 fps (each frame twice) at to real 60 fps.
It worked perfectly!
You might have to play around with the sensitivity control a bit…
Greetings, Soap Chef
PS: I still have to test the fake 30 fps (24 fps footage) to footage at 60 fps…
“It seems to be as you say.
Topaz is unable to eliminate judder.”
I tried a fake 30fps (shot at 24fps – so every fourth frame is duplicated).
Topaz eliminates the duplicate frame and also converts it to the desired 60fps, but it looks completely unusable. There’s no smooth motion, just completely uneven, meaning the result is worse than the original!
They really need to develop a special model for this case, which occurs very often.
Where people who don’t know anything about anything simply convert 24 to 30, or vice versa, convert 30 to 24 fps. (also from 25 to 30, so every fifth frame is duplicated)
…that would be nice…
Is there a statement from Topaz about this?
frame interpolation is not same as inverse telecine, interpolatation produces new frames and as more blury existing are at more blury generated gets. Known on the TV as Soap-Effect when you activate interpolation, background gets more blury
To be honest I don’t wont learn Avisynth scripting for inverse telecine. If you are lazy like me, have a look at “Decomb decimate” and “Decomb telecide” which are Avidemux implement filters. I can’t say how good this works, but you can give it a try
Hi,
Thanks for this advice.
“If you only need to remove duplicate frames, TDecimate alone will do the trick, or you may even use SelectEvery to remove 1 frame every N.”
Ok, and what is than with the audio?
and the software recognizes which frame is the duplicate ?
If you encode the resulting video at the corrected framerate, the audio will stay in sync because the video duration will not change, only the framerate. So a 25 fps video where you apply for 1 in 25 decimation needs to be encoded at 24 fps.
TDecimate is your best bet, it will automatically remove all duplicated frames for you, if you use it without any paremeters. But it may then remove too many frames (especially with anime sources which naturally contains multiple duplicates that you want to keep). You can check its documentation TIVTC/TDecimate - Avisynth wiki
For a 25 to 24 fps decimation, you should use TDecimate(cycleR=1, cycle=25) which will make it aim for 1 frame to remove every 25 (TDecimate will decide for itself which frame is the best candidate for decimation in each batch of 25 frames).
