Geometry Dash video, VFR (64,820 FPS) to CFR problems

[Migue12HD]

Hello, good morning.

I’ve been struggling with a serious issue in my Geometry Dash gameplay recordings.

I have several older videos recorded in VFR (Variable Frame Rate), and since these videos are very important to me, I don’t want to discard them.

Many of them were recorded at irregular frame rates (for example, 57 FPS or lower values), but the one I’ve been working with recently is especially important — it was recorded perfectly smooth at around 64.820 FPS (VFR).

I’ve been trying to convert this video from VFR to true CFR (Constant Frame Rate) using FFmpeg, and although I’ve managed to get very close, there’s always one persistent problem:

I get slight horizontal "wobble" or displacement of the screen, as if the camera shifts left and right every second. This is especially noticeable with how the level blocks move during gameplay — they don’t stay stable like they should.

What I need is a way to convert this kind of VFR video to 60.000 CFR without adding visual artifacts, stuttering, duplicated frames, or that screen wobble. I want to preserve the exact same fluidity of the original.

Alternatively, if there's any way I can upload this video to YouTube directly without it introducing these problems, I’d love to know that too.

I’m using an RTX 3050 and currently working with FFmpeg + NVENC. The best result so far came with this command, but the problem wasn't totally resolved: ffmpeg -hwaccel cuda -i "C:\Users\miguel angel\Desktop\MAGMA.mp4" -c:v h264_nvenc -preset p7 -cq 18 -colorspace bt709 -color_primaries bt709 -color_trc bt709 -color_range tv -pix_fmt yuv420p -vsync 0 -filter:v "fps=60" -c:a copy "C:\Users\miguel angel\Desktop\MAGMA_BIEN.mp4"

Thanks in advance for your help — any advice or advanced techniques are appreciated.

[ProWo]

You can use clever FFmpeg-GUI.
Load your movie, click main page, click various, click change framerate.
Insert 60 in the new fps field and click change.
Wait until is finished. The final output should have constant 60 fps as framerate.

The whole thing works without the video being re-encoded. So it is fast.

This operation naturally changes the length of the video stream.
The audio stream must be adjusted to the new length so that the video is synchronized again.

You can also use the program for this.

[Migue12HD]

The program allows me to configure the parameters to convert a video from VFR to CFR. However, I can't export the file in a format other than .mkv because there's no way for me to modify the target file. The problem with the .mkv format is that I can't properly preview the result.

[rgr]

Many of them were recorded at irregular frame rates (for example, 57 FPS or lower values), but the one I’ve been working with recently is especially important — it was recorded perfectly smooth at around 64.820 FPS (VFR).

Use Avisynth and https://github.com/Asd-g/TimecodeFPS plugin to convert to CFR.

I’ve been trying to convert this video from VFR to true CFR (Constant Frame Rate) using FFmpeg, and although I’ve managed to get very close, there’s always one persistent problem:

I get slight horizontal "wobble" or displacement of the screen, as if the camera shifts left and right every second. This is especially noticeable with how the level blocks move during gameplay — they don’t stay stable like they should.

Normal with CMOS matrices. Use CMOS Fixr plugin (Vegas, Resolve, Premiere).

What I need is a way to convert this kind of VFR video to 60.000 CFR without adding visual artifacts, stuttering, duplicated frames, or that screen wobble. I want to preserve the exact same fluidity of the original.

1. Stick to medium frame rate.
2. If you have to (which I don't think makes sense), then go to 59.94fps.
3. You can use Topaz Video AI (Chronos filter) to change to 60fps/59.94fps.

Alternatively, if there's any way I can upload this video to YouTube directly without it introducing these problems, I’d love to know that too.

I’m using an RTX 3050 and currently working with FFmpeg + NVENC. The best result so far came with this command, but the problem wasn't totally resolved: ffmpeg -hwaccel cuda -i "C:\Users\miguel angel\Desktop\MAGMA.mp4" -c:v h264_nvenc -preset p7 -cq 18 -colorspace bt709 -color_primaries bt709 -color_trc bt709 -color_range tv -pix_fmt yuv420p -vsync 0 -filter:v "fps=60" -c:a copy "C:\Users\miguel angel\Desktop\MAGMA_BIEN.mp4"

There will be duplicate frames.

[ProWo]

The program allows me to configure the parameters to convert a video from VFR to CFR. However, I can't export the file in a format other than .mkv because there's no way for me to modify the target file. The problem with the .mkv format is that I can't properly preview the result.

You haven't read my instructions.
There are no parameters to set except the desired framerate. There is also no need for a preview, as the video is the same as the source.
After the framerate adjustment and the audio track adjustment, you can mux both tracks in the app to any other compatible container, e.g. mp4, mov, avi etc.

[Migue12HD]

Use Avisynth and https://github.com/Asd-g/TimecodeFPS plugin to convert to CFR.

@rgr To use the TimecodeFPS plugin, I need to compile the files; however, despite multiple attempts, my compilation attempts have failed. In fact, I had never compiled anything before. And I can’t use the plugin without having the compiled file.

Normal with CMOS matrices. Use CMOS Fixr plugin (Vegas, Resolve, Premiere).

I could use CMOS Fixr + those video editors, but the problem is it’s paid software, and the costs are not cheap.

If you happen to have the files and can share them here, I would really appreciate it.

[Migue12HD]

The program allows me to configure the parameters to convert a video from VFR to CFR. However, I can't export the file in a format other than .mkv because there's no way for me to modify the target file. The problem with the .mkv format is that I can't properly preview the result.

You haven't read my instructions.
There are no parameters to set except the desired framerate. There is also no need for a preview, as the video is the same as the source.
After the framerate adjustment and the audio track adjustment, you can mux both tracks in the app to any other compatible container, e.g. mp4, mov, avi etc.

@ProWo, I managed to export the video with CFR and it looks good.
The problem is that I still have that slight camera shift to the right, which is like a shutter happening roughly every second. This is the same issue I had when using classic ffmpeg.
Do you know how to eliminate this error? It’s the only issue I’m experiencing.
Here is the configuration I used:

[Attachment 87038 - Click to enlarge]

[ProWo]

@ProWo, I managed to export the video with CFR and it looks good.
The problem is that I still have that slight camera shift to the right, which is like a shutter happening roughly every second. This is the same issue I had when using classic ffmpeg.
Do you know how to eliminate this error? It’s the only issue I’m experiencing.

This is the wrong way and it will recode your video.
As i said, go to main page, various, change framerate.


[Attachment 87039 - Click to enlarge]

[Migue12HD]

@ProWo

I have accessed the tab you mentioned and followed exactly what you instructed.


[Attachment 87043 - Click to enlarge]

However, my video, once converted, experiences lag and slowdown, even gaining 6 extra seconds in total duration.
You can see my original video here (recommended to watch on a good mobile player).

And here is the result after applying the configuration, which shows the issues mentioned:

[ProWo]

I have accessed the tab you mentioned and followed exactly what you instructed.
However, my video, once converted, experiences lag and slowdown, even gaining 6 extra seconds in total duration.

I don't see any lag, but the slowdown is normal, from 64.82 fps to 60fps.
If you don't want that, what do you think of this?

[Migue12HD]

@ProWo it's a very smooth video, so any loss of fluidity, no matter how small, is noticeable — especially if you look at the blocks during the movement. The camera motion becomes choppy and looks more rigid.

[pandy]

Personally i would check for smallest delta between PTS and use this or twice lower time as frame rate denominator so you can keep motion fluidity at a cost of doubled frames.