Bug Reports

I’m using Premiere Pro Beta in the new Color workspace/mode.When I create one mask, it works normally. But as soon as I add a second mask, Premiere creates black vignette-like artifacts/black blocks on the image. Also, the mask appears to shift or affect a different area than where I placed it.In the Program Monitor, the mask outline is in the correct place, but the actual masked effect seems offset/misaligned. It looks like the mask position and the rendered result don’t match.This happens when adding a second mask in the Color panel. I’m not sure if it’s a GPU/rendering issue or a bug with multiple masks in the new Color Mode.Has anyone else experienced this?

Auto object masking gets caught on tracking - it simply says tracking. The frame rate of the footage is 29.97 filmed on my Canon R5. A previous update resolved this issue, but it is now back. 

When I go to use the object mask tool feature isntead of the red outline you are supposed to get when hovering, all I see is a clock icon and it will not work.

heic files crash when imported and re crash when re opened?..when converting image file on mac from hif ti heic premiere does dont like file and crashes>?..then crashes on re opening with file in progect bin?.. used early sved file to continue progect mike d oakland ca.

object mask wont track 

Mogrts aren’t visible after inserting them on the timeline. Did everything possible, clearing cache, restarting the app. They aren’t visible and the app doesn’t throw any error either. But they’re working fine on the regular app. 

Transcribing is currently not working on Beta. Just stops and doesn't give any error codes or anything   System info    Application: Premiere Pro (Beta) v26.1.0.12    OS: Windows v10.0.26200, RAM: 63.93 GB GB, CPUs (logical): 16

I ran a backup of my drive array yesterday and saw a ton of folders with a long ID and “Masks.”  In this multicam project I have about a 15 minute segment for one camera that required a tracked mask (which worked very well, though it took forever to plot). Anyway, after 3 days of editing I now have 22GB of Auto Save files with Masks. Each folder is 651MB. (However the Masks folder in the project root folder is over 900MB. What’s up with that?)This is the first time I’ve seen a Masks folder, I guess this is part of the new masking scheme. Aside from slowing the frequency of updates, is there any way to cut down on mask bloat? System info    Application: Premiere Pro (Beta) v26.3.0.53    OS: Windows v10.0.26200, RAM: 63.79 GB GB, CPUs (logical): 16

After the new Object tool update. I am unable to manually animate the Masks by adding manual path keyframes.  

Who was the genius who designed this disaster…? There’s way less precision for selecting exact values compared to Lumetri Color. One wrong mouse movement and you instantly lose the value you had before… it’s simply a disaster. And don’t even get me started on what happens if you organize your workspace for editing vertical videos. What the hell does it mean that the moment you start editing, you can’t even see your clip anymore? Someone explain that to me… Extremely disappointed.  

Audio meters sometimes just stop displaying the levels. Can’t tell if there’s a reason for why they go out and come back.

After a short period of making color adjustments in the color panel memory consumption quickly balloons to the point of causing macOS to have to suspend all programs.

"Apply Inverse Tone Mapping” was added with the beta release of color mode, and it solved my previous issues when adding text to a Wide Gamut project, in the last two updates from this week, this stopped working, tried it on older  projects, and making a new one with the same behaviour on either instance.  Fully white text looks gray. It's worse when trying to use a specific color. 

26.3.0 BETA (Build 44) contains this error: if a sequence contains a scaled MOGRT clip with Motion → Scale set to 50% or less, the Program Monitor preview scales incorrectly unless High Quality Playback is enabled.

Problem: In Color Mode the Comparison View icons remain visible even after switching it off. The Reference, Current, and the Swap Sides icons and text remain on screen. MacBook Pro 2021 15.4.1Pr Beta 26.5.0 (Build 9) 

All video playback is pixelated and blurry.  Playback setting are set to full and high quality playback is enabled. It looks this way in the color workspace and in the normal editing timeline. Export is clear and normal

None of the HUD scopes are clear enough to read. They all pop up pixelated. When adjusting the HUD options, the sample HUD looks normal.

Mask tracker will not track if clip has Color effects on it. It will drop keyframe on the current frame and not move. Rebooting and uninstall and reinstall Premiere Beta allows tracking but will crash when you click 'Stop' on tracker. This is repeatable even after reboot and uninstall+reinstall of Premiere

 This bug also exists in version 26.2.2 System info    Application: Premiere Pro (Beta) v26.5.0.8    OS: Windows v10.0.26200, RAM: 31.82 GB GB, CPUs (logical): 24

Steps to reproduce:    1. ... Result: ...Expected: ... System info    Application: Premiere Pro (Beta) v26.5.0.4    OS: macOS v26.5.0, RAM: 64.00 GB GB, CPUs (logical): 18

Clips wont long snap to the edges of another clips anymore.It will only snap to the red center guides or when using the blue guides Works in 2025 but not in 26.2.2 either. 

No workspaces in headerDoes not let you use the New item icon button for new sequences.Have to use the New Sequence window.26.5.0.2

I have installed the beta version of your new Premiere Pro 2026 recently, where your audio remix tool is not working; it's behaving like a normal arrow tool. Can you please fix this issue, as it's causing me issues? 

I recently upgraded to Premiere Pro Beta 26.5. Instantly, I noticed I’m unable to play back the timeline/program monitor at full resolution. No matter what I select, it only plays at a low resolution. I’m not sure what resolution it is exactly, but I’m guessing it’s 1/8 based on what I’m seeing. It freaked me out because I thought there was something wrong with my footage , but when I checked the source it was fine. I reverted back to 26.3.0 BETA (Build 71) and it’s fine now. I’m wondering if anyone else sees this issue. I’m hesitant to upgrade until I know this has been fixed. I realize this is the risk in using the Beta version, but the normal version of Premiere has stopped opening - it crashes every time I try to open it - I think it is related to a plugin issue because it will start if plugins are disabled. Long story, short, I started using the Beta version almost exclusively becasue I’m not having the crashing issue.Apple M3 Max64GB RAMTahoe 26.5