{"id":20562,"date":"2025-05-01T18:54:56","date_gmt":"2025-05-01T18:54:56","guid":{"rendered":"https:\/\/surreyborder.org.uk\/?p=20562"},"modified":"2025-05-01T19:10:00","modified_gmt":"2025-05-01T19:10:00","slug":"elementor-20562","status":"publish","type":"post","link":"https:\/\/surreyborder.org.uk\/index.php\/2025\/05\/01\/elementor-20562\/","title":{"rendered":"Say hello to FlowFrames Video Interpolator!"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

A major problem for serious video makers is that of intermixed frame rates.<\/p>

Any set of videos made with a multiple of 25 frames per second (the UK Standard) will happily mix together. Typically they are 25 \u2013 50 – 100 FPS.<\/p>

Or, alternatively, any set of videos made with a multiple of 30 frames per second (a US Standard) will happily mix together. Typically they are 30 – 60 – 90 – 120 FPS.<\/p>

But woe betide the poor video editor who is confronted with mixture of both US and UK standards.
Quite simply, they don\u2019t mix. In the case of 25 and 30 frame per second footage, each 1\/5th of a second has a different number of images to cope with:<\/p>

\"\"<\/p>

Therefore, if the editing timeline is 25 fps, then mixing 30fps footage is rather like trying to put a pint into a half pint pot \u2013 it won\u2019t all fit.<\/p>


The US footage has 30 images per second, but each second of the UK timeline only has space for 25 of those images.<\/p>

\"\"<\/p>

\u00a0<\/p>

That means that in every second, 5 of those 30 frames will need to be be discarded. As shown on the right, every 1\/5th of a second caters for just 5 frames, so that one US frame has no location and is discarded.<\/p>

The eye might not always spot it, but the reality of removing 5 frames every second is that the video with show some level of jerkiness. This will almost always be most apparent when watching a panning shot.<\/p>

Although some editing software tries to compensate for it, perhaps by doubling up some of the extra frames, the fact is that is that it doesn\u2019t fix it, it simply tries its best to mask it. The error will always be present.<\/p>

The best way to \u2018fix\u2019 it currently is to slow down the 30 footage so that it closely matches 25 frames per second, and the eye can’t see any stutter. The formula to slow it down is to divide the frame rate (25) by the higher frame rate video (30). ie 5\/6 or by 0.833 – not the easiest number to work with \u2013 but it does the job. Running the video at 5\/6ths normal speed fixes the extra frame issue, plus it looks great for smooth and dreamy shots such as for wedding videos! But running the video slower might not be what is required.<\/p>

Assuming that the poor editor has been confronted with some 60 fps footage (with no chance of a reshoot), and they are using a 50 fps timeline, they had two options:<\/p>

1.Slow the 60 fps footage down by 0.833 of its normal speed so that it matches native 50 fps as previously mentioned,<\/p>

2. Simply drop the 60 fps footage on the timeline and hope for the best (letting the editing software remove or juggle the extra 10 frames every second),<\/p>

But now there is a third option – something that has only recently become available;<\/p>

3. Utilise an Ai solution such as FlowframesVideo Interpolator.<\/p>

https:\/\/nmkd.itch.io\/flowframes<\/p>

This program takes a series of adjacent frames and creates extra frames between them so that the overall number of frames per second is increased. For example, with 60 fps footage it can increase the number of frames by a factor of between x2 to x10. These interpolated frames are entirely generated using Ai so that the quality is good and the video motion becomes very smooth.<\/p>

\"\"<\/p>

The next bit is the simple maths. The lowest common frame rate that both 50 and 60 frames per second can happily work together with is 300 fps. (Their multiples are 6 and 5 respectively).
In our case, using x5 with Flowframes will change our 60 fps footage to 300 fps by interpolating the extra frames needed and creating the new images.<\/p>

This means that both the 50 fps and the 300 fps footage can now be placed together on the same 50 fps timeline without any issue. The playback is then as smooth as could be achieved natively, without stutters or jerkiness.<\/p>

Brian O\u2019Connell kindly provided some sample raw 60 fps iphone camera footage, and this video shows the three options the editor can choose.<\/p>

\"\"<\/p>