Skip to main content
October 20, 2025

HEVC 4:2:2 10-bit 6.2K Video Not Using Hardware Decoding (Works Fine on 4K)

  • October 20, 2025
  • 13 replies
  • 830 views

Hello Adobe Community,
I'm experiencing an issue with hardware-accelerated decoding in Adobe Premiere Pro on my NVIDIA RTX 5070 Ti GPU. Specifically, HEVC (H.265) videos in 4:2:2 chroma subsampling, 10-bit depth work perfectly with hardware decoding at 4K resolution, but the same format at 6.2K (5240x2700) falls back to software decoding (CPU). This leads to poor performance during playback and editing.


System Specs:

GPU: NVIDIA RTX 5070 Ti (latest Studio Driver installed, 581.57)
CPU: AMD Ryzen 9 9900X
RAM: 64GB DDR5
OS: Windows 11 (fully updated)
Premiere Pro Version: 25.5
Preferences > Media: Hardware-accelerated decoding enabled, set to NVIDIA.

 

Issue Description:

For 4K videos (4096x2160 or 3840x2160), hardware decoding works as expected. In the Debug Monitor (Alt+Ctrl+F12 > Importer.MPEG), the "Hardware Decompressed" counter increases while playing, and "SW Frames Decompressed" stays at 0. GPU usage is visible in Task Manager/GPU-Z.
For 6.2K videos (5240x2700 from Fujifilm X-S20 camera), it switches to software decoding: "SW Frames Decompressed" increases, but "Hardware Decompressed" remains at 0. No GPU decode activity.

Both videos have very similar properties (HEVC High Profile, Level 6.1, 10-bit, 4:2:2, YUV). The only major differences are resolution and frame rate (6.2K at 25fps, 4K at ~60fps). I've tried:

Clearing media cache.
Restarting Premiere after enabling hardware decoding.
Testing with different sequences and clean projects.
Updating drivers and Premiere to the latest versions.

This seems like a limitation or bug in the Mercury Playback Engine's integration with RTX 50-series NVDEC for higher resolutions in 4:2:2. Encoding works fine for both resolutions.


Has anyone else encountered this with RTX 50-series cards and high-res HEVC 4:2:2? Is this a known limitation, or could it be fixed in a future update? Any workarounds besides proxies or transcoding to ProRes?
Thanks in advance for any help!

13 replies

Adobe Employee
May 13, 2026

Hi All,

Sorry for the inconvenience caused. This issue has been fixed in the latest Beta builds (26.3.67 onwards). Please try it with the latest Beta build and let us know how it behaves there.

We sincerely appreciate everyone for highlighting and helping us investigate this issue.

Thanks,
Mayjain

Victor5CD3
Known Participant
March 7, 2026

It's good to know that a fix has already been released in beta 26.2. Here at the production company, we have new machines with the RTX 5070 and we're having the same problems, in addition to the low performance. I'll wait for the official version to be released to update to this new version 26 when these fixes come. I'd like to remind the Adobe team that the lower-end RTX 5060 is also having these same problems. I don't know the dynamics of the tests before releasing an official version after user testers have tested the beta, but I suggest that the Adobe team test it on the weaker card. If it works well on that card, it will work on the top-of-the-line model. If these fixes that will come in the official version work well on the RTX 5060, they will work well on the top-of-the-line RTX 5000 series models.

Build CPU Ryzen 5700X,64 GB ram,Nvidia geforce 5060 Ti 16 Gb,SSD nvme 1tb + ssd sata 2Tb HD Disc 2Tb Win11 24h2
IanB_360
Community Manager
Community Manager
March 6, 2026

Hi ​@triovid 
This issue has been fixed in Premiere beta version 26.2. Feel free to test the 6k files in beta; you will find they're now using the GPU for decoding instead of the CPU. 
Here to help.

Ian

Participant
November 21, 2025

Update! I tried to disable "H264/HEVC hardware accelerated decoding" and "H264/HEVC hardware accelerated encoding" in Prefecences > Media. After that I created a new project and then imported sequence from my old project file and it worked!

 

For sure this ain't long-term solution, but helped me to finish my project so I was able to deliver final version to my client.

Participant
November 21, 2025

Hi!

 

Still having the same problem with Fuji 6.2K HEVC 4:2:2 10bit. In the last message I wrote that I have a old project that works fine, but now even that doesn't work and Premiere Pro crashes when I try to open it. When using 4:2:0 everything works just fine with both LongGop and All-I.

 

I'm running latest versions of both Premiere Pro, Nvidia Studio Driver and Windows 11.

 

Adobe: Have you figured out any solution for this and is there a fix coming in Premiere Pro 26.0??

IanB_360
Community Manager
Community Manager
November 6, 2025

Hi @triovid 
Have you seen this community post regarding the HEVC 422 10-bit files? support-for-nvidia-blackwell-architecture
I am sharing the footage you sent with my team so they can take a closer look. Do you happen to have any 60FPS files that are also spiking the CPU usage?
Here to help
Ian





 

Inspiring
October 24, 2025

I am having this SAME issue and I have to keep rolling back to old versions of premiere to get certain projects to load and to work at all, I also cant export without error codes using both Hardward AND Software encoding options. 

October 23, 2025

As I said, it's really frustrating. I upgraded my graphics card to an RTX 5070Ti because of the new H265-422-10 Bit-supported Encoder-Decoders that come with the Nvidia RTX 5000 series, but now I can't use their Decoders in Premiere 🙂

Participant
October 23, 2025

Hi! I tried to create a new project > Created 4K sequence> Then added 6.2K 4:2:0 footage > Dragged footage in to the sequence and "Fit to frame" = No problems. Then I imported 6.2K 4:2:2 footage and dragged it in to my 4K sequence = Playback doesn't work and Program Monitor freezes, and when I try to close Premiere Pro it doesn't respond and I have to force close it. Very frustrating!

 

But still the project I created in September with older version of Premiere works just fine with almost 200 clips of 6.2K 4:2:2 footage. It's like new projects that I create with 25.5. are broken at first place.

 

I'm totally fine using 4:2:0 LongGOP but still it would be great to hear what is causing these problems. I usually delivery both horizontal and vertical video for my customers, so 6.2K 3:2 footage suit my needs very well.

October 22, 2025

Hello, yes, I'm experiencing the same issues you mentioned. I noticed something: if I import H265-422-10 Bit 4K files and H265-422-10 Bit 6.2K files into Premiere Pro at the same time, it crashes. If I import only 4K or only 6.2K files, it doesn't crash. You can try it too 🙂 This situation is really frustrating. I'm not a software engineer, but I think this problem stems from the fact that 6.2K videos can't use the graphics card's decoders. I think Adobe could easily fix this issue with an update. I hope they do, because working with these files without using the graphics card's decoders seems practically impossible...