I’ve noticed what appears to be a bug in how Premiere renders H.265/HEVC footage after applying certain effects. From what I can tell, if an effect is not natively GPU accelerated, the image will be degraded by color noise/artifacting and perhaps a color shift. It essentially looks the same as if using MPE Software Only.

Effects such as Warp Stabilizer don’t cause this, as I don’t think they are in the same processing pipeline, but I have found that the following do:
Camera Blur
Neat Video
Color Balance
Flicker Free (older non-GPU acceleration version)
Luma Key
Posterize Time

Out of these, Neat Video’s noise reduction plugin is the most relevant to my workflow – but I wanted to show that this bug applies to both native and 3rd party effects. And while it’s a bummer that Neat Video for Premiere isn’t really usable with HEVC footage, I found that if I dynamic link to Ae and use Neat Video there, the issue isn’t present.

I’ve also included a couple of still frames for reference – notice the blocky color artifacts on the second image, especially in the purple areas to the left and right sides of the frame. The first image just has Lumetri applied, while the second also has Camera Blur but with the percent blur set to 0 (saturation has been boosted in both to help show the issue).

Lastly, I have observed this problem on a variety of HEVC footage (422 10-bit, 420 10-bit, and 420 8-bit) and two different workstations (specs below).

System 1
Windows 11
Premiere Pro 2022
i9-12900K
64GB DDR5 4800MHz RAM
RTX 3080
Multiple NVMe SSDs (500GB–1TB)

System 2
Windows 10
Premiere Pro 2022
i9-9900K
64GB DDR4 2666MHz RAM
GTX 1070
Multiple NVMe SSDs (500GB–1TB)

We rendered a 960x540 DNxHR LB clip in MXF OP1a container out of DaVinci Resolve.

Upon trying to import it into Premiere Pro, the Project Panel metadata wrongly shows that clip as being 1280x540, even though VLC and DaVinci Resolve show it correctly as 960x540. After importing, the clip is stuck showing the "Media Pending" graphic and won't show that actual footage.

Rendering the same clip from DaVinci Resolve as 960x540 DNxHR LB in a QuickTime MOV container allows Premiere Pro to import the clip fine, show it correctly as 960x540, and show the footage just fine.

So this appears to be some kind of nasty bug from Premiere Pro with the MXF OP1a container and DNxHR LB footage at this resolution.

HELP!!!!
When importing media from cameras with the AVCHD media folder structure using the Media Browser (as you have to, in order to get metadata such as timecode), Premiere will no longer register any audio for spanned clips (clips made up of multiple files to account for legacy systems that cannot use media files over 2GB). On the timeline, the entire video clip is present, but there is no peak file data or audio. When you look in the media folder on the hard drive, Premiere creates a peak (.pek) file for the first media file, but not for the spanned file(s), nor does it create an XMP for the clip. The only way to make it work is to import the clips independently (losing all metadata) or import all the audio independently and have to re-sync it to the timeline.

Please let me know how we can fix this or what information I can provide.
Premiere 22.3.2 (build 2) - Windows 10
Worked previously, but no longer.

I have four :30 promos on a sequence. There are six Mono Tracks with Video and Titles. I want to take the fourth spot on the timeline and speed it up from :51 to :45. I mark In and Out, Ctl-M for Export, Select the Time Tuner and set the duration to :45 (which by the way always has to be manually typed in). After export, the video is perfect but the audio cuts out half way through the spot. Silence.

The workaround was to duplicate the sequence. Remove everything I did not want Time Tuned and bring the spot to the beginning of the timeline. Mark In and Out, select Time Tuner and export. That worked.

It would be nice to have the Time Tuner work like that without the extra steps. This has happened in both 2020 and 2022 versions of Premiere Pro.

Thanks,
Rob K.

I edited the trailer for a documentary project on my old Intel iMac on Mojave this past August with no issue. The majority of the footage in the project are R3D files. I recently started editing the full-length film (same footage) with a new MacBook Pro with M1 Max, Mac OS 12.2, and Premiere 22.1.2, and I'm now getting a number of issues.

-Most importantly, I'm getting corrupted frames (see below) on export, and sometimes when just opening a sequence or pausing in the timeline.
-When loading Multicam clips in the source monitor, I see the two correct camera angles displayed while paused, but as soon as I hit play, it displays the B Cam (second video track) twice.

So far, I've tried the following:

-Opening Premiere in Rosetta (fixed issues during playback, but still had a bad export)
Transcoded all R3D footage to ProRes, changed sequence presets accordingly (no corrupted frames during playback or export, still improper angles in Multicam playback)
Opened the most problematic clip in Resolve, played it back, added some nodes, exported (worked!)
-Edited another project with different media (.braw - Blackmagic media) on the same system (worked flawlessly!).

So, from what I've been able to deduce, this seems to be a unique issue with Premiere, M1, and R3D media. Any help greatly appreciated!

On behalf of editors, I request better controls for exporting an animated GIF file from Premiere Pro. Currently, the file size of these files is often too large to post on websites and social media sites. The results are better using Photoshop > Save for Web (Legacy). Editors would rather not use Photoshop and simply need more control over the size and quality of the exported file. Is this possible?

This forum post currently has over 56,000 visits. Kindly upvote this feature request so that others may have this ability to create GIFs easily and with a lower file size. Thanks.

https://community.adobe.com/t5/premiere-pro-discussions/how-to-change-the-mb-size-of-a-gif/td-p/10786587

I am experimenting with rendering computer graphic animations in an image format called OpenEXR. Unfortunately, Premiere doesn't appear to support OpenEXR in any useful way.

While there is a 3rd-party addon that allows Photoshop to open and edit OpenEXRs, there doesn't appear to be one that does the same for Premiere. As much as I loathe learning a new video editing app, the solution for me is to switch to a 3rd-party option like DaVinci Resolve.

Unlike Premiere, DaVinci Resolve easily imports OpenEXR sequences (Premiere will import them, but they display as black frames). Please Adobe, I'd prefer to stick with Premiere. Thanks!

Premiere plays HEVC audio up to two frames too early and displays up to two frames of no audio at the end of clips. Not an issue in Resolve or Final Cut Pro

I make small H.264 proxies of HEVC footage from Canon C70 cameras so editors can download footage quickly. Sometimes clips have 4 channel audio so I have to make proxies in Compressor or EditReady. We noticed that there is a discrepancy in the audio of two frames between the original footage and the proxy footage. This is a HUGE problem and waste of time when reconnecting full res for final export. After emailing Canon they suggested I try it in a different NLE, lo and behold, it lines up perfectly in Resolve and Final Cut Pro. Canon informed me that if it lined up in other software the problem is likely a codec issue with the software I was using which is Adobe Premiere.

Originally we thought the proxies just didn't line up; that it was a sound sync issue with proxies. But it appears to be a problem with how Premiere plays back and displays audio in HEVC footage.

I'm Working on a 2019 MBP with macOS 10.15.7
This problem happens in Premiere 22.0.0 and 15.4.2
And it doesn't matter if the audio is LPCM or AAC, stereo or 4 channel, or if the codec is 35Mbps or 100 Mbps, 422 or 420, it still happens.
The length of the video also doesn't matter and it is not a drift issue.

Check out these screen grabs and take note of the waveforms at the location of the playhead in each photo. Premiere plays the HEVC audio two frames too early in this particular clip.