Bug Reports

System info    Application: Premiere Pro (Beta) v26.3.0.71    OS: macOS v15.7.4, RAM: 96.00 GB GB, CPUs (logical): 24Canon R6 HEVC files are clipping blacks with Hardware Decoding enabled on Thunderbolt Displays

It’s very simple and is reproduceable every time.  I upgraded to 26.3 today, and everytime I click file, export, media encoder… media encoder does not start, and premiere just closes. When I open it back up, it says ‘it unexpectedly shut down’, and ask if I want to open the file.  Every time I try, this happens. Restarting does nothing. When i go back to using the non-beta version, everything works perfectly as expected. It’s only a problem in the newest beta. 

In the 26.3.0 BETA Build 69 and previous versions I found it impossieble to have an object tracking mask on a person and then something behind them.The preview in Premiere Pro would show the mask correctly (after tracking).Then upon export, the preview would not show the clip at all (same for export). It appeared as if the clip with the mask on opacity was completely gone.But it turns out it was not gone, but a problem of having a Scale / Motion effect changes ont he same clip applied. So opacity masks appear not to correctly handle clip level motion as well as the “Transform” effect. Workaround:At this time, the only workaround I have found is to apply the opacity mask, then nest the clip, and then scale / move / keyframe the nested sequence (in the parent sequence).Then the export includes the mask correctly. I hope future versions can make it so that the opacity masks are correctly applied to the clip without needing to nest the clip.

I'm on a Mac 26.4.1 and when I click on the Color mode controls the window is large & blocks my viewer. I cannot change this because the window blocks everything.

When I am in the colour tab and I click on the tools like masking, pen tool, or the text tool, none of them work on the program monitor, they work in edit mode but that means switching back and forth between both modes constantly to see the effects of changes

Toggeling the grid lines button on the program area does nothing.

Just installed Beta 26.3.0 and switched to the Color window. Touching any of the controls in the color window causes a crash. I can adjust the parameters in the properties panel with no issue. I've tried updating my GPU driver and turning off the color HUD display. It still crashes everytime I touch a control. Applying a Style preset crashes the application about 50% of the time.Windows 11 Enterprise13th Gen Intel(R) Core(TM) i9-13900K (3.00 GHz)128 GB (128 GB usable)NVIDIA GeForce RTX 4090NVIDIA Studio Driver 595.79

Last few builds have been difficult to operate the mask feature (any mask type)Can do one mask and then the second mask does not want to show its outline or color overlay.Have to restart the project to be able to continue.W11pro 26.3 B 43, RTX5060.

bugs in color mode:if sort is set to anything but the sequence (default), solo mode is not available and no masks are editable pressing ctrl + \ does not hide the top menu bar (in order to get this to work you first need to press ctrl + \ in edit mode, then switch back to color mode)sort is set to “clip timecode” and my masks are no longer available to manipulate. This is fixed when defaulting to “sequence timecode” sort 

I've been trying to update my Public Beta installation, but I keep getting the error that it cannot extract files. I've been updating all other CC apps, and have run public beta installs since they started. Here's the event log: Exit Code: 127 -------------------------------------- Summary -------------------------------------- - 1 fatal error(s), 17 error(s), 4 warnings(s) FATAL: Error occurred in extract of package (Name: AdobePremierePro14AllTrial Version: 26.0.0.28). Error code: '127' ERROR: Path:C:\adobeTemp already exists ERROR: Failed to allocate buffer for file C:\adobeTemp\ETRC988.tmp\1\universal\App\Adobe Premiere Pro (Beta).exe of size 951391240 ERROR: Failed memory allocation after sleep also ERROR: Failed to allocate buffer for file C:\adobeTemp\ETRC988.tmp\1\universal\App\Adobe Premiere Pro (Beta).exe of size 951391240 ERROR: Failed memory allocation after sleep also ERROR: Path:C:\adobeTemp already exists ERROR: Failed to allocate buffer for file C:\adobeTe

Premiere beta always crash in color tab

After I apply the voice enhance to my voice over, if I try to reposition the audio clip, the program freezes. This happens repeatedly and it happens in both beta and the public version.

Using the latest update available, Trying to use a isolated mask. The masks or selection does not show. The cursor does not change to a reticle to draw the mask, and the pen tool does not change to the pen tip. Tried in other projects and sequences. Also tried on a new clip operation and an existing one, and the same on a sequence operation.

Premiere Beta v26.3.0.66macOS 26.4.1 The transition between audio clips will pop and then the audio drops out for about 4 seconds.

When I’m editing in the new Color mode, the HUD is big and completely covers the program monitor. I want to change the size and position, but when I click the wrench and then click “color heads up display options”, nothing happens. The window never opens. Premiere 26.3.0, Sonoma 14.8.3

Dear Adobe Premiere Pro Team,I would like to report a behavior observed in the current Beta version of Adobe Premiere Pro within the Color workspace, specifically in the Analysis panel and its interaction with the Properties panel.When applying multiple “Adjust” instances within a single clip (e.g., Adjust 1, Adjust 2, Adjust 3), only the first adjustment is exposed in the Properties panel. The remaining adjustments remain active and visually affect the clip, but are not displayed or accessible within Properties unless the first adjustment is removed.Observed behavior:Multiple Adjustments can be applied and are all active in the clip. The Properties panel only displays the first applied adjustment. Subsequent adjustments are not listed, inspected, or made available in the UI. Removing the first adjustment causes the next adjustment in the stack to become visible in Properties.Expected behavior:The Properties panel should reflect all active adjustments applied within the clip. Alternati

I am on Premiere Beta 26.3. I am using MacOS Tahoe 26.4. I am on the latest update as of Tuesday May 5th 12:00 PM EST. When using Lumetri Color on a video in the effects control panel I can not adjust anything in the basic correction dropdown. When I use auto it sets the color but if I try and adjust anything in the basic color with the mouse it sets back to the auto level. Normally you can click the number and drag left or right to change the amount. If you type a number in it will work but the moment you try and drag a number it re-sets all the numbers back to auto amount.

I’m using the timecode feature for a countdown timer. I was working with another video earlier before an update. It worked just fine and I was able to encode and publish. Updated to 26.3.0 and the timecode is now tuck at a random time and doesn’t respond to any changes. My computer at home was updated to 26.3.0 with the same problem. To dupe:Create a Transparent Video layer In the Project panel, go to File > New > Transparent Video (or right-click > New Item > Transparent Video). Match your sequence settings and set the duration to your desired countdown length (e.g., 30 seconds). Drag it to a track above your main footage on the timeline. Apply the Timecode effect Go to the Effects panel and search for "Timecode" or "Metadata & Timecode Burn-in". Drag the effect onto your transparent video clip. In Effect Controls: Set Timecode Source to Generate Timecode Adjust Position, Size, and Opacity to place and style the numbers *** At this time: Scrubbing should show

edit for about 5 min and then program is unresponsive. I can click on things, but no response or playback

I cannot find the WB selector or the White Balance eyedropper in Adobe Premiere Pro Beta

Premiere Beta v26.3.0.061macOS Tahoe 26.4.1 In Color Mode, when I paste a mask from one clip to another, the footage disappears in the program monitor. If I delete that clip adjustment the video reappears in the program monitor. But if I try to create a new mask it turns black again. This creates two problems. First, I have to manually recreate vignettes and power windows for every single clip because I can’t copy and paste. Second, the clips that I have pasted a mask to (even if I delete it afterward or Undo) will no longer be able to receive a mask without going black in the program monitor. Is this a bug, or is this user error? I’ve tried offlining and relinking the clip, duplicating the footage in finder and relinking to the duplicate, clearing media cache, and duplicating the clip in the timeline.Thanks for the help and insights!

I have a repeatable bug where Premiere will crash from the new Color panel if you select a clip and choose “Reveal in Project”.

After generating captions, when I go to export to srt or text file the app crashes. I am on the latest version. 

Hello Premiere Pro Team,Video: Bug showcasePremiere Pro currently does not handle large selections well. As you can see in the video, It takes roughly 2-3 seconds to move Adjustment Layers that don’t have any effects on them and that effectively don’t render anything (there is no video anywhere below them). Unfortunately the Effect Controls panel wasn’t captured correctly but indeed none of those layers contain any effects or keyframes.This slow down will be amplified as soon as effects are applied on the Adjustment Layers.Copying a selection like this also take a few seconds.Using the latest Premiere Pro Beta version (b58).Thanks,will

Hello Premiere Team,when you create a Graphic Layer, set custom in and out handles (by dragging them from the effect controls panel), place *any* Sapphire effect on it and keyframe it, and then paste that Graphic Layer into another Sequence, Premiere Pro will crash.I’ve attached a video here showcasing this bug:Graphic Layers Custom Fades Sapphire Paste CrashThis will only happen if you have these custom in and out fades for the graphic layer. It won’t crash otherwise. And it also only happens for Sapphire effects.I am using the latest Premiere Pro Beta version (b58).Thank you for your hard work,will