ClipReady Get ClipReady
Product menu

ClipReady

How to get an MKV into Final Cut Pro

Last updated:

You drag an .mkv into Final Cut Pro’s media import window and it sits there grayed out. Or the import runs, and the clip lands with no audio, or with a frame rate the timeline argues with. Nothing explains why, and the file plays perfectly in VLC, which makes it look like Final Cut is the one being difficult.

Final Cut Pro does not read Matroska. That is the whole story on the import side, and it is worth being precise about what it means, because the fix follows directly from it.

The container is not the video

An .mkv file is a wrapper. Inside it, on a disc-sourced file, is almost always H.264 or HEVC video: exactly the formats Final Cut Pro edits natively and has for years. The picture is not the problem. Apple’s media stack simply does not have a reader for the box it arrived in.

So the job is to take the encoded video out of the Matroska box and put it in a QuickTime one. That is called remuxing, or rewrapping, and it does not decode or re-compress anything. The picture that comes out was never decoded and rebuilt, and the operation runs at roughly the speed your disk can copy the file rather than the speed an encoder can rebuild it.

This is why “just transcode it to ProRes” is the wrong first move. A 10 GB MKV becomes an 80 GB ProRes file after an hour of your machine’s time, and you paid for that with a generation of quality you did not need to spend.

What a plain rewrap still leaves broken

Here is the part most instructions stop before. Change the container and nothing else, and three things follow you into the timeline.

The frame rate reads wrong. Matroska stores timestamps in milliseconds, and 23.976 fps is 41.7083… ms per frame, which does not fit. Frames land 41 and 42 ms apart. Final Cut measures the real spacing rather than believing a header, averages the jitter, and reports something around 23.81 fps. A stream copy copies those timestamps too, so the new file reads exactly the same. The long version, with the arithmetic.

The audio may not arrive. Disc-sourced MKVs commonly carry DTS-HD Master Audio or TrueHD. Apple’s media stack does not decode either, so the track either goes missing or plays silent. The video was always fine. Why the sound disappears.

Surround comes out of the wrong speakers. A MOV needs a named channel layout. Write six channels without one and Final Cut guesses at the order, which is how dialogue ends up in the left speaker. What the layout tag does.

None of the three is a container problem, which is why swapping the container does not fix them.

The steps

  1. Rewrap, do not transcode. You want the video stream copied, not re-encoded. If a tool offers you a quality slider for the picture, it is about to re-encode.
  2. Choose MOV for editing. Final Cut and Compressor both prefer it, and MOV can hold things MP4 cannot. Choose MP4 if the file is for playback or sharing rather than a timeline.
  3. Deal with the audio deliberately. Anything Apple’s stack already plays should be copied as it is. Anything it cannot should be converted to 24-bit PCM, which keeps every bit, rather than to a compressed format you did not ask for.
  4. Make sure the timing is repaired, not just carried. This is the step that separates a file that works from a file that imports.
  5. Check the result before you build a timeline on it. Frame rate in the inspector, audio channels playing where they should, duration matching the source.

What ClipReady does

ClipReady is a Mac app built for exactly this sequence. Drop the MKV in and it reads the file first, then shows you a plan: every track labeled Preserve, Convert, or Incompatible, with the reason, before anything runs.

The video bitstream is copied across untouched. The timestamps are snapped back onto the exact frame grid, so 23.976 reads as 23.976. Audio Apple’s stack can play is copied; audio it cannot is converted to 24-bit PCM with the channel layout verified against Apple’s own decoder rather than assumed from the source tags. Chapters ride along, and a SMPTE timecode track is written at the output rate, which an MKV has nowhere to store.

Then the finished file is loaded back through AVFoundation and VideoToolbox and checked before it is reported as done. If a check fails, nothing is saved.

It also declines work it cannot do honestly. VC-1 and AV1 have no path into Apple’s media stack without re-encoding the picture, so ClipReady says so and names the stream instead of quietly transcoding around it. Bitmap subtitles, PGS on Blu-ray and VobSub on DVD, stay in the original file: they are pictures, and MOV has nowhere to put them.

ClipReady works on files that are already on your Mac. It does not read discs, and it does not remove copy protection.