CREATOR WORKFLOW
How to test variable-frame-rate clips before editing
Check a phone or screen capture before cutting, then compare an edit-ready constant-frame-rate copy if playback or timing is off.
By Colquhoun Studio editorial
Know when a conversion is worth testing
Variable frame rate means a file does not present frames at a uniform interval. That is not automatically a problem. If the clip plays and exports correctly from your editor, leave it alone. Test a conversion if a source file plays normally on its own but becomes choppy, hard to trim, or poorly synchronized in a new timeline. Those symptoms can have other causes, so they are a reason to test, not proof.
Make a short baseline in your editor
Copy the original into a work folder and keep the original untouched. Import the source into an empty test project and check the editor’s clip properties for a variable frame rate indication, if it provides one. Try a short export that includes an obvious motion, such as the cursor clicking a button. If the file also contains sound, check a visible action with a clear sound near both the beginning and the end.
Make one constant-frame-rate comparison
Use a copy of the same source. In HandBrake, choose Constant Frame Rate in the video settings for this test. Its documentation distinguishes that mode from Peak Frame Rate, which can still preserve variation below the chosen limit. Use the intended project rate if you know it, such as 30 frames per second for a 30 fps project. Do not overwrite the original or assume that changing an editor’s playback interpretation does the same thing. Reference: https://handbrake.fr/docs/en/latest/technical/frame-rates.html
Compare timing, detail, and duration
Put both versions in separate test timelines with the same settings. Watch the same action, check the sound against the picture, and compare durations before taking the copy into your main edit. Look at small lettering and cursor movement too; a transcode can change clarity or motion. If both versions have the same problem, investigate another cause rather than converting the rest of the files.
Label the version that actually worked
When the comparison copy solves the problem, name it clearly, for example, demo-take03-cfr30. Keep the original alongside it. If you already cut portions of the source, test replacing it in a duplicate project and check each cut before relying on the replacement. For a new project, test one representative clip first and only batch-convert if the result is consistently better.