Now in beta: hardware acceleration for more video formats

[Fergus H]

Update: This feature was released with version v24.4 of Adobe's video products. If you have questions or comments, please post them in the main Premiere Pro forum. Thank you for your feedback during the beta! 

Beta versions of Premiere Pro, After Effects, and Media Encoder now include hardware acceleration for playback of more video formats:

• AVC LongGOP in MXF
• HEVC LongGOP in MXF
• HEVC Intra in MXF

Knowing which format is used in what camea can be a little confusing! While the list below isn't exhaustive, it covers some of the more common options. 

Sony 

Cameras: ILME-FX6, PXW-FS5, PXW-FS7, PXW-FX9, PXW-Z190, PXW-Z280, PXW-Z450, PXW-Z750, BURANO

Formats: XAVC-L, XAVC H Intra, XAVC H Long, 

Canon

Cameras: C300 Mark III, C70, XF605, XF705

Formats: XF-AVC LongGOP

Panasonic 

Cameras: CX series, P2HD series

Formats: AVC-LongG50, AVC-LongG25, AVC-LongG12

Currently, hardware acceleration is available on Apple silicon computers. Support for Windows computers is coming soon. 

Update 3/15: Support for Window is now in beta. 

We’d love your feedback on this new feature! Are you seeing better playback performance - particularly with multiple tracks? Better scrubbing? Are you seeing any quality issues with playback? Let us know!

Thanks,

Fergus

[MisterAdvent]

Yay! But I'm on Windows.  I cut a project last week and had no problems, so I doubt if that helps if acceleration isn't there yet.

[Warren Heaton]

I am thinking that it would be great to have something in the user interface that indicates hardware accelerated formats - probably on the Thumbnail in the Project and Bin tab and on the Clip Boundary in the Timeline with pop-up menu options to show/hide the indicator.

[Tranquil_Cosmos157F]

This would be such an easy and intuitive way to understand why the system is struggling - or not.👍

[Kaboon2310759829rv]

I have been using Premiere Pro for our weekly podcast show, which involves seven recording sessions per week utilizing Sony NXCams with AVC LongGOP in MXF format. Previously, we encountered numerous challenges during Multicam Editing, such as a runaway timeline, audio drops, black video, sync issues, stuttering playback, and freezing GUI. However, since the latest version update, we have not experienced any of these issues.

The stability improvements have been truly commendable, making our editing process significantly smoother and more efficient. I must commend the Adobe team for addressing these concerns, as it has positively impacted our workflow and overall experience.

In addition to stability, the enhanced performance with the AVC MXF hardware acceleration is eagerly awaited, and I am confident that it will further elevate our editing capabilities.

I did encounter a crash on one occasion while using NewBlue Titler and Dynamic Linking Audition for audio edits. While infrequent, I thought it was important to bring it to your attention for continued refinement and optimization.

[theaveragedave]

I'm having excellent performance with this beta on my Canon C70 and M1 Max with XF-AVC Long Gop. However on an existing project I noticed a color shift on my C70 footage with Lumetri applied. The footage was noticeably more magenta than in 24.1.0. HEVC footage from the Canon R7 looked normal on the same sequence.

[Fergus H]

@theaveragedave Thanks for the information; that's very useful! Would you be able to share a sample project and related media that show this issue? We will test with our own C70 too but it would be useful to have your data. If you're able to do this, please send me a private message with information about where to download your files. 

Regards,

Fergus

[Khyati Gupta]

@theaveragedave Can you please share your project, we are willing to fix this issue asap. 

Regards,

Khyati Gupta

[theaveragedave]

Hi all,

I'm sorry I think I turned off email notifications because I was getting pinged constantly from other threads. I have since updated Premiere beta and it now is not giving me this issue anymore. I don't think I have revisted that same project again so I'll let you know if I discover it in that project when I do get around to testing again. Too busy at the moment.

[R Neil Haugen]

I'm with Warren.

We REALLY need a listing available in every build of Pr, with what formats it can manage. There's too many, and as your post shows, it's constantly changing.

So a top-menu item ... "Supported and Color Managed Formats This Build" would be a HUGE help. Someplace we could easily, quickly check.

NO WAY we users can mentally track which build does what.

I posted an Idea  on the regular forum for this ...

Supported formats ...

[J-TIZZO]

Is there any chance of adding support for VP9 compression videos and for MKV container videos?

[Fergus H]

@J-TIZZO We are working on adding MKV support. We do not plan on supporting VP9. 

Regards,

Fergus

[R Neil Haugen]

Thanks for the clarification, Fergus.

[Fergus H]

As an update, our Windows beta products now also include hardware acceleration for the video formats listed in my first post. We'd love to get your feedback!

Regards,

Fergus 

[R Neil Haugen]

Ahh, re-reading I see we needed to read the struck-out section of your post to see what you were talking about here ... ok ... 

[Shebbe]

Thanks for the update. Out of curiosity I checked the performance of a project of ours shot with the FX9. The performance is actually 'unacceptably slow' compared to our current version 24.0.3. Eyeballing it sets me at around 3-5x smoother scrubbing vs Beta. Our material is AVC Intra though so I don't know if this is related or it's another issue in the Beta 24.4b28

[Fergus H]

@Shebbe That's very interesting! We would not expect performance to ever be slower. There are some cases where it might not be faster (i.e., you're using Windows hardware that doesn't have support for 10-bit 4:2:2 and that's the media type you're using) but what you're seeing sounds unusual. I will send you a DM for more info. 

Fergus

[Fergus H]

As an update to the forum readers, Shebbe and I spoke offline and it turned out the issue was a local system issue, now resolved.