ClipReady Get ClipReady
Product menu

ClipReady

Camera media to MOV, without a transcode

Last updated:

Someone hands you a drive of .MXF files, or a folder of .MTS clips off an AVCHD camera, and Final Cut Pro either refuses them, imports them into a transcode queue that runs for an hour, or brings them in with timing that drifts against the audio.

As with disc-sourced MKVs, the picture is usually not the problem. Broadcast and camera MXF commonly carries MPEG-2 or H.264. AVCHD .MTS is H.264 in a transport stream. Final Cut has handled both codecs for years. What it struggles with is the wrapper and, in the case of transport streams, the timing model.

Why transport streams are awkward

MPEG transport streams were designed for broadcast, where a receiver can tune in at any moment. They are a continuous flow with timing references sprinkled through them, not a neat file with a single clean timeline. Some cameras restart their clock partway through a card. Long clips get split across multiple files.

An editor wants the opposite: one file, one timeline, timestamps starting at zero and advancing predictably. Getting from one to the other is a repackaging job, and repackaging does not require re-encoding.

Why “just transcode to ProRes” is the usual advice

Because it always works, and because it is what the ingest tools do. It is also expensive: a ProRes intermediate is several times the size of the original, takes real time to produce, and re-encodes a picture that was perfectly good.

For proxies or heavy grading work, that trade can be worth making. For getting a clip into a timeline, it is a large price for a wrapper change.

What you can expect

Single files, not whole cards. ClipReady prepares a file you point it at. It does not walk an AVCHD directory structure, reassemble spanned clips, or rebuild a card’s metadata sidecars. If your workflow depends on that, an ingest tool is the right software and this is not.

MPEG-2, H.264, HEVC and ProRes. Those are the pictures it can carry. MXF wrapping something else is refused by name instead of quietly re-encoded.

ProRes copies through. If your camera already shot ProRes in an MXF, ClipReady rewraps it into a clean MOV and still does the timing, timecode and audio work around it. It is not skipped, and it is not re-encoded—there is no ProRes encoder in the app.

PCM audio is carried. Broadcast MXF usually carries PCM, which Apple already plays, so it crosses untouched.

What ClipReady does about it

  • Rewraps .MXF, .MTS, .m2t and .ts into MOV or MP4 with the picture carried across, never decoded.
  • Repairs the frame timing onto an exact grid, which matters more on transport streams than almost anywhere else.
  • Writes a real tmcd timecode track at the output rate, so the clip lines up in Final Cut Pro, Premiere Pro and Resolve.
  • Shows the plan for every track before it runs, and validates the finished file through AVFoundation before saving it.

One limit stated plainly: Blu-ray .m2ts disc rips and AVI camera variants are untested against the reference corpus, so they are not claimed as supported. They may well work. That is not the same as tested, and this app does not market untested behavior.