If it’s choppy in the export too, then the Video Mode is probably something lower than 29.97fps. Or the video clip was slowed down by a significant amount and there aren’t enough source frames to look smooth. (@Hudson555x‘s post has a link with more information about checking Video Mode.)
What is the video source? Cell phone, .MTS file, etc? If the file is variable frame rate, there can be seeking issues that cause stutter in the export. We kinda need the rest of the information Hudson requested at this point.
thanks for the answer.
one more info: videos I made by my camera works, only videos I made by my drone are choppy. Thus it depence on the imported video. When I look the source video in VLC it is not choppy.
Here are the specifications and/or answers to your questions (in German, but I hope you understand it by the units):
Computer specifications / Win10 Home / AMD Ryzen 5 3500U with Radeon Vega / 4 Cores / Mobile Gfx 2,1 GHz / RAM 8GB / 64 Bit / SSD
Could you include source video information for the camera video like you did for the DJI? Shotcut has an Automatic mode where it sets the timeline to the same settings as the first video dropped onto the timeline. I suspect differences between the camera and the drone. If true, then which one is choppy depends on which one was dropped onto the timeline first.
Also, did Shotcut ever prompt about “this video needs conversion to Edit Friendly” when adding a video?
The camera and the drone have different frame rates. The camera is 25fps and the drone is 29.97fps. They are not going to play nice on the same timeline. Either the 25fps video will have frames duplicated up to 29.97fps, or the 29.97fps video will have frames dropped down to 25fps. Both methods will create stutter. The real solution is to have both devices use the same frame rate, but that may not be an option as it appears one is PAL and the other is NTSC.
This tells me the Video Mode is set to 25fps. Frames are being dropped from the drone video to fit. One option could be setting the speed of the drone clip to 0.8333x which would slow it down enough to use all frames and restore internal timing.
The Video Mode is still 25fps. Video Mode is the native format of the timeline. It is not overridden by the Export screen. The Export screen is an interpolation of the Video Mode, with all the problems that come with interpolation, including stutter. Video Mode is set as follows:
Ideally, the Video Mode and the Export screen will have the same settings. If not, interpolation and potential problems will happen. In the case of the drone video, frames are being dropped to get it down to the 25fps timeline rate (Video Mode), then frames from the 25fps timeline are being duplicated to get back up to the 29.97fps export target. This creates stutter.
Unless the files straight out of the two devices are the same frame rate, one of the two videos will be choppy (assuming 1.0x playback speed) because one video must be interpolated to match the other. That means dropped or duplicated frames which create stutter. The files you currently have are not frame-rate compatible with each other.
A workaround is to slow down the faster video (the drone) to match the frame rate of the slower video.
ok - I created a new project with only the drone video and the project setting on 29,97 fps. The Shotcut screen is still choppy, but the export file is now good, if I view it in VLC .
Tomorrow I will slow down the drone video to 0,8333x.
Is there also another option?
There are ways to generate in-between frames artificially. The general term is Optical Flow processing. But it is error-prone and slow. There is also depth-aware processing (DAIN) to improve on it, but still error-prone and slow and requires pretty beefy GPUs. These techniques never look as good as the real thing. The best look is when devices capture at matching frame rates from the start (unless there is intention to speed up or slow down a clip of course).
There is also a technique called 3:2 pulldown (or telecine) that converts 24fps movies to 60fps interlaced for television. I’m not sure how well it would convert your 25fps camera footage to 30fps progressive, but it might work for shorter clips.
Here’s a brief analysis of optical flow along with notes on when it works and when it doesn’t. However, Shotcut does not perform optical flow processing. This would have to be done with an external program like Premiere or Resolve or slowmoVideo, then bring that new video into Shotcut for editing.
I understand now the problem and how to avoid it - best is everything with the same fps.
Today I slowed down the drone video (from 29,97 to 25 fps)
and it works
Both work - the Shotcut viewer and the exported file - genial.