Bug report: After upgrading to Premiere v15, exporting an H264 file from either Premiere or Media Encoder to my NAS creates a file which the program claims exported successfully, but actually creates a glitched file. At some point in the file, the audio will drop out, and the video will freeze on a single frame, which will remain on screen for the rest of the duration.

Exporting a quicktime file to my NAS doesn't cause this problem, and exporting an H264 file to my internal harddrive doesn't cause this problem, so there's only an issue with the combination of encoding to the H264 export setting to a NAS location that is causing a problem.

This is hugely disruptive to my workflow, and I really need it fixed...

I'm on the new version of Premiere, and I have a 608 track that can be enabled and edited as designed. However, rendering OVER that in the Program Monitor are the same titles again in the style of 608 captions of Premiere 14.x. There seems to be no way to toggle these titles off, and they do not respond to editing the caption text. However, if I edit the text, save the project, close it and reopen it, the old style 608 titles will reflect whatever changes I had made before reopening the project.

If it helps, I notice the old style 608s disappear whenever I go into caption text edit mode directly in the program monitor. They reappear back over top of everything as soon as I leave the text box.

Multiple users report problem with HLG and SLOG footage that gets overexposed in Premiere Pro v22 after importing it into the project. In my case dealing with overexposed H.264 4:2:2 SLOG3.cine none of the fixes mentioned in groups and forums do the trick to fix the exposure. Interpreting footage to Rec. 709, making sure sequence is Rec. 709, ticking ''colour management'' in general preferences - nothing. The footage is also behaving normal on my windows laptop and issues occur on M1 Pro machine (same files, same versions of Premiere, same settings, I attach pictures of waveform from both computers). Please improve this bug in next update.

Premiere Pro CC 15.2 running on 2020 Mac Mini with 8GB RAM - MacOS Big Sur 11.4

Memory leak starts immediately and skyrockets after any edit, making editing impossible after just minutes. What this means is I have to restart Premiere after nearly every edit. Massive hit to productivity.

You can see in the attached screen recording, at one point tonight Premiere maxed out the 8GB memory and then used upwards of 12GB of Swap Memory, which also negatively affects the lifespan of the non-replaceable SSD in this computer.

Fix this ASAP.

Linking to video since the screen recording was apparently too large to attach.

https://youtu.be/EtPMZmaw_4c

Since the update to 14.5.0, all panels that are on a secondary monitor (connected to a DisplayPort) are unresponsive to the keyboard, and items cannot be dragged and dropped.

For example, I have a workspace that has the source and program monitor panels, plus the productions and media browser panels on my primary monitor. The rest are arranged on my secondary monitor.

I can use key strokes in any of the panels on the primary monitor, for example, hitting the spacebar will toggle playback in the source and program panels. I can also drag and drop clips from the media browser to the source or program panel.

But, I cannot drag and drop from the media browser to the project panel or a sequence, because those panels are on the secondary monitor. I also cannot drag clips from the project panel to a sequence, nor can I drag an effect from the effects panel (also on the secondary monitor) to a clip in a sequence.

There is however, a workaround. If I change the workspace to one of the default schemes that only occupy the primary monitor, then switch back to my dual monitor scheme, all the issues disappear until the next time I launch Premiere.

Has anyone else experienced this bug?

Greetings! Like many other folks, we are remote shooting with camera crews and need to quickly get proxies from set that our editors can access quickly and start editing with. A common usecase is the proxies that the Canon C300 MK2 camera generates internally and records to an SD card. The camera originals are 3840x2160 and 400 MBS (23.98 fps, with 4 channels of audio). The proxies are 1920x1080. matching audio channels and framerate and 24 MBS, quite a bit smaller! We want to download these small proxies from set and have Premiere treat them as “attached proxies” even though we don’t have the originals yet. We would like to have the option to have Premiere interpret them as 3840 x 2160 as if they were proxies attached to masters of that framesize. Then later, when the camera crew gets back from location, downloads the originals and uploads them, our editor might download them the next day or even later. But we would like to have the proxy workflow where they point the Premiere project to the camera originals and Premiere recognizes them as the “attached masters” to the proxies they’ve been editing with. Now, when we finish an edit that has been edited with the 1080P proxies, often we’ve done a lot of resizing and reframing in the 1080P sequence and so when we reconnect to the 3840 x 2160 files it’s complicated to go back to resize and reframe. Also, we are wanting to be able to make very tiny 1280 x 720 MP4 proxies on location and have those map back to our raw files. A similar usecase requiring the same features in Premiere. We’ve been able to do this in After Effects since 1999 or so by bringing in offline clips and attaching proxies while waiting for the full rez clips to be available. Maybe this feature could be developed from code that the After Effects team has already developed? This would be an enormous timesaver and we would be very appreciative if you could help us develop this workflow!

Hi!
I've heard I am not the only one to have this issue. Preview window in Premiere Pro 22.0 is terribly tearing. Like some kind of V-sync bug. It's not there on ver. 15.1.0. Though it's still has bugs.
I have read everything. I turned on/off/what ever else V-sync in my Nvidia control panel for Premiere. Turned on/off GPU for previews in proj settings. Forced the system to use different video adapters for Premiere. Nothing. Tearing. Even on pre-rendered clips. Even without any effects applied. On Full resolution, "High quality" preview settings. No matter if it's Low-res HD footage or heavy 4K vids.
If I open the same preview file from Adobe previews folder it runs OK. Exported video is OK. But it terrible to work. I can't say, if footage is OK, until I export it. And I normally add some glitches to my video transitions. How do I know, is it my glitch or a bug?
Definitely needs to be fixed. Check out attached file for an example please.

BR, Anton.
Gigabyte Aero 2021, 11th gen i7, 64 Gb RAM, RTX 3060. Latest drivers. Nvidia Studio driver.