If the footage is made at different frame rates, do they need to be specially converted?

Hello everyone.
Often videos from the Internet have different frame rates. How to deal with this? Do videos with different rates need to be converted separately or will the program automatically do everything that is needed?

Are there any training materials on this topic?

Shotcut does not require all your source material to be the same frame rate. Shotcut will skip/duplicate frames in your source files to match the project frame rate.

The key is to set a Video Mode with the final frame rate that you want when you start your project.

For some frame rate conversions, the simple skip/repeat capabilities in Shotcut can result in jerky motion (for example, 25fps to 30fps). In that case, some people choose to use the Motion Compensation conversion in the Convert-to-edit-friendly tool.

Further reading here:

2 Likes

Thank you. This is what I wanted to see, I didn’t know about this tool. I understand that this tool should be chosen based on personal preference. Are there any more precise recommendations, a table?

I don’t think anyone has made a table. I think the general advice is to use the motion compensation if the frame rates are not multiples of each other. For example:
60fps → 30fps - MC not necessary
24fps → 30fps - MC recommended.

But it also depends on your source material and how much motion it has.

1 Like

29,97fps → 30fps? How is it here?

Movements can be fast and slow. Is this necessary for fast movements?
My computer is not designed for editing at all. It takes a lot of time to convert and see how best. If there are any other recommendations, please write.

Most people will say no.

Some people will say yes, some people will say no. Unfortunately, you will have to decide for yourself.

Fortunately, Shotcut makes it easy to convert later. My advice is to NOT convert anything, and then preview the result. If the conversion does not look good to you, then you can perform the conversion on clips that you think do not look good.

2 Likes

This is good advice. I’ve heard it before in the context of programming – “don’t optimize ahead of time.”