First decide whether the climb is slow or the player is struggling
A clip that feels too slow after editing does not always need a speed increase. The exported file may contain deliberate slow motion, the player may be set below normal speed, or playback may pause while the file loads. Those are different problems. Start with the unchanged original and the exact saved copy that looks wrong, rather than another copy downloaded from a chat.
This is a general troubleshooting workflow. It does not establish a CruxCut bug, promise a specific export frame rate, or claim that CruxCut offers manual speed controls.
Compare one recognizable movement, not only total duration
Choose a short sequence with clear endpoints, such as leaving the start holds and reaching the next hold. Watch that same sequence in the original and saved file at each player's normal-speed setting. If the saved movement takes visibly longer and the whole sequence remains smooth, investigate a speed change. If movement freezes and then jumps ahead, investigate playback or loading first.
Use total file duration as a clue only when both files cover the same start and end. A shorter trimmed export cannot be compared directly with a long session recording. For example, an untrimmed ten-second sequence that becomes twenty seconds is consistent with slower playback, but duration alone cannot tell you which app or setting caused it. This example is illustrative, not a measured product result.
Check the player's speed before changing the edit
If your player has a playback-speed control, confirm it is at its normal setting, often labeled 1×. Open the saved file in another available player without editing it again. If the problem happens in only one player, that narrows the affected path; it does not prove the saved file itself is correct everywhere. A slow network preview is also not the same thing as a local saved file playing slowly. Wait for an available download to finish and compare locally.
Keep the audio as another clue when the recording has useful original sound. A change in sound timing can help you notice a speed difference, but silent footage, replaced music, or audio processing makes this inconclusive. Do not infer the exact speed multiplier from audio alone.
High frame rate is not the same as slow playback
Frame rate describes how many video frames are represented per second. Playback speed describes how quickly the recorded action unfolds. A high-frame-rate recording can play at normal speed; it does not automatically need to be slowed down. Some recording and editing workflows also preserve a selected slow-motion region or interpret timing information differently. Check the recording mode and the source's slow-motion selection where the device exposes it.
A file labeled 60 fps or 120 fps does not, by itself, tell you how long a reach should take. Likewise, choosing a different export frame rate is not a reliable substitute for correcting an unintended speed setting. If the original itself already plays slowly in your gallery, investigate the source before blaming the export.
Run one short test from the original
- Keep the original unchanged and make a separate test project or copy.
- Choose one complete, recognizable movement with a little setup and follow-through.
- In an editor that provides speed controls, check for speed changes, ramps, or slow-motion sections. Disable only the unintended change for this test.
- Save the test once, then open the actual saved file outside the editor.
- Compare that movement with the same source segment at normal player speed.
Do not change speed, crop, resolution, and audio all at once. A controlled test is easier to interpret. Avoid repeatedly speeding up already-exported copies: return to the original when testing a new correction. If the source format is not supported, follow the editor's current support guidance rather than guessing a conversion setting.
Use slow motion where it answers a climbing question
For beta review, normal-speed playback helps preserve the rhythm of an attempt, while a separate slowed section can make a foot slip or hand transition easier to inspect. Label the slowed section so viewers do not mistake it for the real pace. Video cannot reveal grip force or prove why a move failed just because it is slowed down.
For a sharing edit, check the start and finish after any timing change. Keep enough context to read the action. If the actual issue is missing feet rather than slow movement, use the framing checklist; if it is loss of detail, use the sharing-quality checks.
What to send support if the speed still looks wrong
Record the source device and recording mode, the original and saved durations for the same segment, the players compared, and whether the problem affects the whole clip or only a section. Separate what you observed from your explanation of the cause. A screen recording of playback may help demonstrate the symptom, but it is not a substitute for the actual source and output when file timing needs investigation.
- Keep original, test, and final copies clearly named using a simple attempt log.
- Share only a short sample you are permitted to share, with consent for identifiable people.
- Do not include passwords, private links, or unrelated bystander footage.
- Check the final destination copy once more before calling the problem resolved.