Bug Reports

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. 

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 

When switching modes from edit to color, my default window setting get changed, even after setting and resetting custom saved workspaces. I use 3 monitors, and windows will be hidden behind one another, leaving 1 monitor completely empty, and I have to manually find the window and bring it back to the correct monitor every time I switch.

AI assistant feedback on audio effect to a clip (for later copy and paste to other clips audio)**Status on your request:** I can't add the audio processing effects right now. Every audio effect I tried — Parametric Equalizer, Dynamics, Mastering, Hard Limiter, Multiband/Single-band Compressor, even the basic Internal Highpass/Bass filters — is listed as available but gets rejected by the effect-add tool as "unknown." I confirmed the tool itself works (added and then zeroed out a test video effect on the same clip's video component to prove it, no visible change left behind), so this is a current limitation specific to audio effects in this environment, not something I can work around by retrying or picking a different effect name.**What that means for the EBU R128 pass:**- EQ (Parametric Equalizer / highpass cleanup) — blocked- Compression (Dynamics / Single-band Compressor) — blocked- Loudness normalization to -23 LUFS integrated / -1 dBTP true peak — blockedYou'll need to apply this

Couldn’t ******It bounces back every time I try to add a shape on the programme, making it almost impossible to add graphic on it.On way I figured out is to go to Properties, then add new layer, and choose Rectangle.

Steps to reproduce: 1. ...  Result: ... Expected: ...  System info Application: Premiere Pro (Beta) v26.5.0.50 OS: macOS v15.7.2, RAM: 24.00 GB GB, CPUs (logical): 14"The Premiere Al agent APl's getAppliedEffects and addEffects tools donot return componentid values for effect components, makingsetEffectParameters non-functional. This prevents the Al fromprogrammatically setting any effect parameter values on timeline clips."

No me deja editar, no sale la barra de la cronología en la opción de edición 

Gestion de couleur avec un mac book pro M3 latence pour le rendu des réglages 

I have been using Beta 26.3 for the color mode to color grade my videos (I still edit them with the latest official release) but when I upgraded the beta to 26.5 it became unusable. It’s so slow I can’t do anything. I have tried all the 26.5 versions that have been released, including the one released today on the 25th of June and all of them are sow slow I have to uninstall and go back to installing the 26.3 version to be able to work. I’m getting really worried something important changed with 26.5 and that will continue with each new beta version and I won’t be able to work with the latest versions. And even worse, that the same bug continues to the latest official release when the Color Mode get’s released there. Am I the only one having this problem with the 26.5 versions? When I click any of the color tools it takes a few seconds to show the HUD and when I move the mouse it fakes a few seconds to show any change. It’s too slow. 

Masks won’t track. They just get get hung up after trying to start the track. Mac M1 Ultra. Tahoe 26.3. Premiere Beta 26.5

I’m using a 2 screen setup. When I open new panels, they open with their control bar behind the menu bar. It’s impossible to move or control the panel window

Steps to reproduce:    1. Tried to get AI to resize a 16:9 sequence to 9:16 - it created a new sequence, but then said it couldn’t change the sequence settings.Then asked it to resize the clips to the new sequence size, so as they filled the frame proportionally.   Result: As reported by the AI tool itself:I don't have a tool to file a bug report directly — that's something you'd need to raise through Adobe's feedback channels yourself. But if you do, the specific issue worth flagging is that `setEffectParameters` returns a success response (`{}`) even when the write is silently rejected (e.g. an out-of-range value), making it impossible for an agent to distinguish a successful write from a no-op. That's the core reliability problem here.And yes — you're absolutely right, and I should have seen it earlier. `copyTrackItemAttributes` with `motion: true, videoEffects: false` would have been the correct approach from the start:1. Set Scale to 88.89 on one clip correctly2. Use that clip as

The newest Beta (26.5.0 Build 36) is crashing with motion array transitions.  Worked on the previous build until I updated today (June 18)slicer AND shifter both fail

Pretty self-explanatory… Command+\ no longer hides the header bar in the latest beta.Working on a 14” MacBook I need all the screen real estate I can get. Please fix!

Cuando activo el comparison view desde el click derecho en la pantalla, al desactivarlo seleccionando "Composite Video" , no se van los boton de "Original", "Curren" y "Swap Sides". Tambien me ha pasado que selecciono un highlight zone, pero al mover la exposición, este no se afecta de ninguna manera

Hi all,This version definitely has too many display problems: the menu and interface freeze, and the software is slow. Sometimes I have to force-quit the program…Fabrice Laptop HP Omen 16CPU intel I9_14900HXRAM 32 GOGPU Nvidia Geforce TRX 4080 Laptop and DRIVER Studio Nvidia 596.36iGPU intel disableHD 1To Microsoft Windows 11 Famille (64 bits)25H2 (10.0.26200)   

Hello!I’m not sure if this is the right forum for a bug report on the beta release of Premiere, but it seems that the latest build (build 30) crashes much more often in the color panel than the earlier builds did.  This could be due to my getting more comfortable, and therefore ambitious, with the new toolset.  Now when I apply a mask (rectangle or oval) and try to track it, the program locks up almost every time.  If this needs to go to another fourm, please let me know.Thanks!System:Windows 11Core I964gig RAMRTX4060TI

Some transitions in Production Crate’s LaForge Suite cause instant crash when applied. I thought it was a “me” problem till i saw someone else’s post saying also motion array’s transitions cause insta-crash:I concluded that it’s a bug by testing the same transitions on the latest stable release (26.3) crash doesn’t happen there. Sapphire and BCC transitions seem to be working fine as well, but there is definitely something going on and needs to be looked into.System info    Application: Premiere Pro (Beta) v26.5.0.37    OS: Windows v10.0.26200, RAM: 31.82 GB GB, CPUs (logical): 24

I am testing out the new Assistant. I have a bunch of text layers in my sequence with two different text assets in them. The first text asset that appears in the list in the Properties panel needs to be moved upwards on the Y axis, from the current value of 2032 to a new value of 2005. I asked Assistant to do this for me on a selection of four clips before running it across my entire sequence. It says it ran, but when it was done the values of the Y position had not changed, and now my text is just blank. My convo with Assistant: Results: 

Issue:Premiere Pro incorrectly detects silences in Transcript / Text Based Editing. The detected silence regions are visibly offset from the real audio waveform, so the silence markers do not line up with the actual pauses. Because of this, removing pauses is unreliable and sometimes cuts into spoken dialogue instead of only removing real silence.This happens in both Premiere Pro Beta and the regular Premiere Pro release, so it does not appear to be limited to one version branch.Steps to reproduce:1. Import a video clip with spoken dialogue and natural pauses.2. Create a sequence from that clip.3. Open the Text panel and create a transcript using Text Based Editing.4. Let Premiere detect pauses / silences in the transcript.5. Compare the detected silence block positions against the actual waveform in the timeline.6. Notice that the detected silence regions are offset and do not match the real silent areas correctly.7. If you use the remove pauses function, Premiere may remove the wrong

  When Direct Manipulation is manually disabled, the setting does not persist when selecting clips that contain linked audio and video. reselecting a linked A/V clip or selecting a different A/V clip, Direct Manipulation re-enables itself without user input.   This behavior appears to be specific to linked audio/video clips. I cannot reproduce it with unlinked video-only clips or still images, where Direct Manipulation remains disabled once you disable them while selected as expected.Import a video file that has audio linked. Add the clip to a sequence as a linked audio/video clip. Enable Direct Manipulation. Disable Direct Manipulation. Reselect the linked audio/video clip. (or any other linked video)   Expected Result:Direct Manipulation remains disabled until it is manually re-enabled by the user.Actual Result:Direct Manipulation re-enables itself after reselecting the linked video or any other linked video on the timeline. Additional Testing:Unlinked video-only clips: Cannot reprod