Bug Reports

when Open the Beta version of Premiere pro i received the Problem Report 

When trying to toggle between the different blending modes under the Effects Control panel, it stays stuck on Normal

always freezes and have to close program if I touch hue or sat in color mode. can't isolate any colors at all.  

As I was editing through the mic phone indicator started to lit in my m4 max macbook. when I checked what is using the mic it showed premiere beta. I did not record or do anything that is related to mic.

I'm running Adobe Premiere Pro 2026 (v26.3.0) on the macOS 27 Golden Gate Public Beta, and Premiere keeps crashing randomly while editing.I checked the crash log, and here's what stands out:Exception: EXC_BAD_ACCESS (SIGABRT) KERN_INVALID_ADDRESS at 0x0000000000000000 Premiere calls abort() The crash is triggered by a thread named:CML_AdobeOneVisualB16-20250709It doesn't look like a GPU, codec, or memory issue. From what I can tell, it seems more related to Adobe's background AI/Creative Cloud components ("Adobe One Visual") or an incompatibility with the macOS 27 beta version.

I'm running Adobe Premiere Pro 2026 (v26.3.0) on the macOS 27 Golden Gate Public Beta, and Premiere keeps crashing randomly while editing.I checked the crash log, and here's what stands out:Exception: EXC_BAD_ACCESS (SIGABRT) KERN_INVALID_ADDRESS at 0x0000000000000000 Premiere calls abort() The crash is triggered by a thread named:CML_AdobeOneVisualB16-20250709It doesn't look like a GPU, codec, or memory issue. From what I can tell, it seems more related to Adobe's background AI/Creative Cloud components ("Adobe One Visual") or an incompatibility with the macOS 27 beta.

The transcription/text feature works with the source footage, but once the production timeline is assembled, it becomes buggy. Sometimes it provides the transcription with properly labeled speakers; other times it provides an unlabeled version with incorrectly timed text; but mostly it indicates that no dialogue is found.

I have been editing my projects with the official release (26.3) and opening them on Premiere Beta to do the color grade using the new Color mode (saving the project with a new name so I can still open the ungraded project on the official release if something happens). The color mode recently became unusable. It is very very very slow. Every click on a tool takes seconds to open the scope and then it takes a few seconds to show any change when I move the mouse. I noticed I was using the 26.5 version. I tried for hours but got very frustrated and installed the previous beta version (26.3) and I’m once again able to grade my footage. It’s slow but workable. I don’t know what happened with the 26.5 version but I hope it gets fixed so I can use the latest version. 

Save as or Save a copy does not open the corresponding folder containing the project files. etc.It opens some random? folder.This behaviour can cause serious mistakes in managing ones project.This has been going on for a while and also present in 26.3Beta 26.5 B64 W11

New (in beta) color grading tools still don’t work properly with Wacom tablet. It’s imprecise, even after modiying sensitivity and nudge in setting and then holdng Alt key. It’s impredictive, runs to extremes (up or down).Also the pivot concept is wrong, in my opinion. It would be beter if it all worked as eyedropper in ACR - you click specific area and drag. Or maybe there should be an option to operate by draging particular areas on HUD. Just Click on the HUD and drag it up or down, with possibility to modify the area height / falloff strenght by eg. pressing keyboard arrows.

Keyframing beim Ducking funktioniert nicht.

This is an annoying behavior that did not happen before and is still present even in the Premiere Pro Beta. When you modify the value of an existing keyframe, its interpolation resets from Bezier to Linear.For example, if a Scale keyframe is set to 50 with a custom Bezier speed curve, and I later change that same keyframe value to 60, the keyframe immediately becomes Linear. This forces me to manually recreate the Bezier speed curve every time I need to adjust a value, which significantly slows down the workflow and breaks fine motion adjustments.The expected behavior is that modifying a keyframe’s value should preserve its interpolation type and Bezier curve unless the user explicitly changes it. 

Object mask and warp stabilizer don't go together. Even with nesting the mask will go offset. Does not matter if you nest the mask or WS first. It wont follow WS.   Render and Replace wont work at all as the are 4K clip in a 1080p timeline.   26.1.1 B30 W11pro   nesting Render and replace      

The new color mode has a bug when using a fade/dissolve in a clip and also having the detail module turned on at the sequence level. Here is how the clip looks mid dissolve with the detail module turned on: And here is the same frame with the detail module turned off: 

Update crashes midway with an error code 146 and says “Unable to move the file. Rename the file and try again. ”Has full admin access too.  Error log:  Exit Code: 146-------------------------------------- Summary -------------------------------------- - 2 fatal error(s), 0 error(s), 1 warnings(s) FATAL: Error (Code = 146) executing in command 'MoveFileCommand' for package: 'AdobePremiereProBeta14AllTrial_arm64', version:26.3.0.71FATAL: Error occurred in install of package (Name: AdobePremiereProBeta14AllTrial_arm64 Version: 26.3.0.71). Error code: '146'WARN: Unable to move file at "/System/Volumes/Data/.adobeTemp/2839B7E5-E6DB-432B-B40E-ACC155371D44/1/arm64/App/Adobe Premiere Pro (Beta).app/Contents/CodeResources" to "/Applications/Adobe Premiere Pro (Beta)/Adobe Premiere Pro (Beta).app/Contents/CodeResources" . Try setting correct permissions to the specified file/folder or parent folder, so that admin has rights to modify it.-----------------------------------------------------------

Steps to reproduce:1. Edit a short section on a timeline that you want to export (3 or 4 clips)Tap the UP arrow on keyboard to select the first frame of the section Tap “I” to set the in point Tap the DOWN arrow on keyboard to select the last frame of the section Tap O to set the out point Export In to Out    Result: ...An extra blank frame is added to the export.  Looking closely at the timeline, it’s apparent that an extra frame has been added to the selection. As these are for a video loop, the black flash frame is apparent. Expected: ...In previous versions no extra blank frame was selected. Workaround: Step back one frame and tap O. Last frame is selected and no more.   System info     Application: Premiere Pro (Beta) v26.5.0.51     OS: Windows v10.0.26200, RAM: 63.79 GB GB, CPUs (logical): 16

When render-and-replacing multiple MOGRTs simultaneously, Premiere appears to check via their parameter configuration alone whether or not those MOGRTs are unique. However, duration does not appear to be considered, and this causes a problem if you render responsive design-time MOGRTs simultaneously with different durations but otherwise identical parameters. For example, in the sequence in the screenshot below, I have two instances of the same MOGRT for a ‘progress bar’ animation on V2. They have identical parameters, but different durations. After selecting both and rendering to ProRes 4444 simultaneously, you can see that only a single render file has been created ending in _24, and both instances have been linked to that. In this case, the render has been performed from the first instance of the MOGRT, and since it is longer than the second instance, the second instance ends its animation prematurely and holds on the last frame. Meanwhile on V3, there are two instances of the same

When applying in adjustment in the colour panel to the sequence and let's say click on any other adjustments for example contrast the panel disappears! See images:Adjustment in the SequencePanel Options visableThen when adjustingThen what I have to do is go back click on the adjustment in the sequence and try and do it again. This doesn't happen if the adjustment is at clip level. This is extremely annoying and with some of the features impossible to use.

I'm currently running macOS 27 Golden Gate Beta 3, and things have been really bad since updating.First, I found out I had to run this command:defaults write com.adobe.PremierePro "EnableFireflyFeatures" -bool NOThis fixed an issue where Premiere Pro would crash every time I placed anything on the timeline. After that, I discovered another bug: copying attributes from one clip to another causes the app to crash again. I haven't found a workaround for that one yet.I know some of these issues may need to be fixed by Apple, but since the first problem was resolved by disabling Firefly features, it seems like at least some of the crashes could be Adobe-related.At this point, Premiere Pro is extremely unstable on Golden Gate Beta 3, and I honestly don't know what to do. After Effects has also been crashing, even though I haven't changed anything besides updating the OS.

When in the new color mode, the comparison view does not allow me to select shots - and therefore I cannot use this feature. I briefly get a “from selection” box pop up top left, after using the thumnail view to select two bottom right,  but these quickly disappear. Tested across a Mac Pro and MacBook Pro with the same issue on both. 

When Premier 26.5.0 launches, I get an error “The shortcut ke “Adobe Premier Pro Defaults V6.keys is invalid.”When I select Keyboard Shortcuts… from the menu, Premier crashes every time.Crash logs attached.

The scopes in color mode often don't render. It's just a black box instead of the actual scopes. Happens more with larger projects, or when it's been open for awhile.PS, an opacity slider for the scopes would be nice, because they cover up a lot of the image.

En el modo de color, cada vez que quiero empezar a realizar un ajuste la ventana se cierra y no me deja modificar, tengo que seleccionar de nuevo la capa de ajuste y ajustar 

Description: I’m experiencing a bug in the current Premiere Pro Beta (version 25.6.0) related to manual masking and keyframe animation.When I draw a mask using the Pen tool or shape tools and attempt to animate it using Mask Path keyframes, the mask does not respond to changes. Even after enabling the stopwatch and adjusting the mask on different frames, the animation does not register—both keyframes remain identical, and the mask stays static.I’ve confirmed this behavior in multiple projects and tried the following workarounds:Toggling the Mask Path stopwatchManually adjusting the mask shape on different framesUsing different effects (Gaussian Blur, Lumetri Color)Resetting workspaces and preferencesNone of these resolved the issue. It seems the new masking system in the Beta is not properly linking manual mask adjustments to keyframe animation.System Info:Premiere Pro Beta v25.6.0Windows 11 Pro 64GPU: Nvidia GeForce RTX 3080 LaptopThis bug is blocking my workflow, especially for subtl