Issue Importing MKV File with HEVC (H.265) Codec into Adobe Premiere Pro

[AVTO.M]

Hello Adobe Support Team,

I am facing an issue with importing an MKV file encoded with the HEVC (H.265) codec into Adobe Premiere Pro (latest version). The program throws the following error:
"The file could not be imported. The source compression type is not supported."

Here’s what I’ve already tried to resolve the issue:

1. Installed HEVC Video Extensions from the Microsoft Store.
2. Cleared the Media Cache in Adobe Premiere Pro.
3. Verified that my Adobe Premiere Pro is updated to the latest version.
4. Attempted to import the same file into Adobe Media Encoder (the same error occurs).
5. Created a new sequence matching the file’s resolution and frame rate (3840x2160, 23.976 fps).

The file details are as follows:

• Format: MKV (Matroska)
• Codec: HEVC (H.265, Main 10 @ L5.0)
• Resolution: 3840x2160 (4K UHD)
• Frame Rate: 23.976 fps
• Audio: EAC3 5.1 @ 640kbps, 48kHz

I would prefer to resolve this issue without converting the file using external tools, as the file size is large (~8.77 GB), and I aim to maintain the original quality.

Could you please help me understand why this file cannot be imported and guide me on a solution?

Thank you for your assistance.

Best regards,

[Ann Bens · Accepted solution]

That is correct H.265 in a MKV wrapper is not supported. H.264 is.

https://community.adobe.com/t5/premiere-pro-beta-discussions/now-in-beta-support-for-h-264-in-mkv/m-...

You already know the solution: convert.

[Guedhami385986385rdb]

That's a Joke! I don't know why Adobe insists on not fixing that. 

[R Neil Haugen]

Because mkv is not a heavily used codec in pro editing workflows, never has been.

It's a great codec, yes. But the general use has been a very small niche market, mostly archivists.

That's why they don't have support for it at this time. Though it is in process in the public beta work, they've told us.

[paul32062743ku6s]

6 months on has this been resolved  as a forensic video unit hevc files are now becoming more frequent from security systems. Some of our workflow ends up with an option to use mkv keeping vital metadata etc which is lost in the process of rewrapping or transcoding the source file. Mostly the hevc files we get are proprietary and won't import straight into premiere.

[R Neil Haugen]

Depending on the tool used for the conversion, there should be a process to get all metadata crossed into the new container. That said, some fomats and options used have at times been less than optimal for how one can handle the file data later.

And for certain choices that have been made by someone in the past ... the only forward choice is manually transferring data. Which is a right and total pain, and yes, I did get some first hand experience with this.

Our youngest just competed his Master's in library science with emphasis on archival ... and this was something he was tasked to report on for a couple classes. With Dad being a video post dude, Dad got queried on some issues he was having. He was able to solve them successfully, but still ... I was struck by how fragile the entire 'ecosystem' is, really.

So while I always support requests to get users more options ... this is one that, I think from memory ... is finally getting some official care, as again, it's a much smaller share of the pie than most other things the app works on or with. I get that.

But it's not going to be a fast rollout ... and I do wish it were other. As I do with about 50 other things. Sigh.

[paul32062743ku6s]

Our problem is, CCTV footage is now adopting more HEVC/H265 codecs. The data we use needs to be preserved as we don't always just edit it into a compilation. There are several practices we use and and every little byte of data is important. If it was just convert a proprietary format into a useable stream then we mostly use ffmpeg to rewrap or transcode the file. Most jobs are like that, but when you have to do a forensic analysis on a file then further examination. Then we need to preserve that data. MKV using ffv1 is one such format that does not affect framerate, compression or any other from a long list of attributes that we require. If this was a brand new filestream then yes, I get it. But MKV has been around for well over a decade. It's usefulness is now becoming more apparent as it can maintain that data. Like someone else posted on an Adobe forum a while back  Davinci Resolve can handle MKV so why not Adobe who are a much bigger company and have been around for decades. 

Depending on the tool used for the conversion, there should be a process to get all metadata crossed into the new container. That said, some fomats and options used have at times been less than optimal for how one can handle the file data later.

And for certain choices that have been made by someone in the past ... the only forward choice is manually transferring data. Which is a right and total pain, and yes, I did get some first hand experience with this.

Our youngest just competed his Master's in library science with emphasis on archival ... and this was something he was tasked to report on for a couple classes. With Dad being a video post dude, Dad got queried on some issues he was having. He was able to solve them successfully, but still ... I was struck by how fragile the entire 'ecosystem' is, really.

So while I always support requests to get users more options ... this is one that, I think from memory ... is finally getting some official care, as again, it's a much smaller share of the pie than most other things the app works on or with. I get that.

But it's not going to be a fast rollout ... and I do wish it were other. As I do with about 50 other things. Sigh.

By @R Neil Haugen

s usefulness is only becoming more apparent now the HEVC videos are around. Like someone else posted on an Adobe forum Davinci Resolve can handle it, so why not Adobe.

[R Neil Haugen]

We users never know the specifics for any decision no matter the company. None of us can answer specifics on why one does one thing another doesn't. 

While you clearly have a specific need for MKV support, it's still not a widely used codec for most workflow needs. I would guess that is still a consideration.

I wish it were otherwise. But then I have interest and need for color tools past what Premiere offers at this time. Which the devs agree would be very cool and useful. For tge 20 or 30 of us users who would actually use them.

I'm not holding my breath, mind you. Though I do hope they get better MKV support for you who need it.