The quality of exporting from Premiere Pro using hardware encoding on the new MacBook Pro with M1 PRO chip is extremely poor. I've tried exporting with multiple different projects and footage but the quality when exporting with hardware encoding is pixelated and blurred - the file size is also significantly smaller than the estimated file size.

There is no issue with software encoding and footage is as expected.

I've tried Premiere Pro 2022 and also gone back to 2021 and tried opening with Rosetta instead, still hardware encoding into H264 is extremely poor quality with file sizes less than half the expected file size. This only happens with hardware encoding.

• Premiere Pro 2022.04
• have Intel Core i7-1165G7 (11th Gen) 16GB Ram, 475 Gb, SSD, Laptop with 2GB external graphic card

Premiere Pro Warp Stabilizer has been extremely slow ( does not even work at all in some clips longer than few seconds long) whereas DaVinci or stand-alone ProDad stabilizer (add-on Prodad no longer works fine in the recent versions of Premiere PRO - no thanks to Adobe) in my laptop

Some will say "why don't I get a more powerful processor/system"
I'd say "why doesn't Adobe get their act together and code it good enough to work properly, requiring less resources like DaVinci stabilizer or Prodad Stabilizer"

C'mon guys & girls:
please fix the stabilizer issue first before adding new features (they are mostly beta to be tested anyway)

When I hit the "L" key to fast-forward while playing on the timeline, and hit about 4x speed, the audio stops scrubbing (I think this is normal), followed by Premiere Pro locking up. There's no way to halt the playback at this point, and eventually Premiere Pro locks the entire system - even the mouse cursor won't move. If I shutdown/restart fast enough (after Premiere locks, but before the entire system locks), I can get a reboot to happen. Otherwise it's the reset switch.

It is very similar to the problem described here, except I'm running Premiere Pro 2022 on Windows 10, and the video format is XAVC S HD:

https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-cc-2020-crashes-on-fast-forward...

If I edit AVCHD footage, the problem doesn't seem to occur. I've tried turning off hardware accelerated encoding/decoding in the Media preferences, with no effect on this. I'm guessing it's a Premiere bug - suggestions?

ProRes Raw files are seeming unable to be played back on AMD GPUs using the latest PP 22.x + ProRes RAW 1.3 on Latest Windows 10 & 11.

See: https://community.adobe.com/t5/premiere-pro-discussions/issues-decoding-prores-raw/m-p/12648595

There seems to be a bug that prevents the rendering of frames using GPU Acceleration using OpenCL that produces a console Error and results in audio playing but only a black screen for video:

<12112> <Assert> <0> Debug Assert failed!
Expression: dvacore::ResultSucceeded(result)
Process: Adobe Premiere Pro.exe
Process ID: 9652
Thread ID: 12112
Thread Name: Display Thread
File: ....\Src\RenderRequest.cpp
Line: 228
Function: AdobePlayer::RenderRequest::ProduceFrame
Last Error: 6
Assert Dialog Show:false
Callstack:
xRendererEntry
xRendererEntry
dvacore::threads::CreateAsyncThreadedExecutor
dvacore::threads::GetThreadName
dvacore::threads::GetThreadName
boost::detail::win32::handle_manager::swap
configthreadlocale
BaseThreadInitThunk
RtlUserThreadStart

The new color management options in 22.x versions break the proxy color and dynamic range, when using LOG or HLG/PQ original clips that have been over-ridden to Rec.709 with an input LUT.

The original clip on the Rec.709 sequence is 'normalized' correctly. But when you then go to create proxies, the CM is not used in creating the proxy.

What you get is a blown out useless mess of an image as your "proxy".

Not a correctly viewable image in the same color space as the original clip and the sequence.

We need the proxies to follow the clip Color Management.

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)

I frequently combine text with different fonts/sizes/etc in the same layer when composing credits. For instance, one style for the role or crew position, another for the name.

In Premiere, applying a Styles preset to highlighted text changes the entire text layer, incl. unhighlighted text.

PS does this with ease using Character Styles.

If I am in need of a clue, I would appreciate some kind soul educating me about this. I've tried various approaches and I just can't get Premiere to stop changing all the text to a given Styles preset when I only want to change the highlighted text.

I have all of my source footage and audio sorted into about 12 folders. Some of the folders have multiple files, others have just one.

If I import all of these folders into Premiere, any folders that have more than one file get a BIN created automatically. Any folders with just one file don't get a BIN.

I don't see the point or benefit of not creating a bin for folders with just one file. If I'm importing folders, I think it's safe to assume I want to use that structure. I plan to add files to these bins later and having to manually create them again in the Premiere interface is a waste of time!