Bug Reports

The new mask feature’s keyframing functionality is broken. Sometimes, changing the position value and adding a keyframe doesn’t animate the mask. It just moves it for the entire clip duration.I can’t reproduce when it does or doesn’t work.

Out of nowhere my clip became black. It’s still showing the preview in the timeline, but the source clip in the bin, in the source monitor and the playback monitor are all pitch black. I have tried relinking the clip, adding effects, removing effects, and nothing works.  

Issue: In Adobe Premiere Pro 2026, audio waveform generation after importing clips into the timeline is extremely slow. Even on high‑performance systems, it takes a long time before the waveform appears, delaying the start of editing.Impact: This causes workflow interruptions, especially when working with multiple audio files or compressed formats like MP3.Tried Fixes: Clearing media cache, converting audio to WAV, enabling multithreaded waveform generation, and updating drivers — but the delay persists.Request: Looking for a reliable way to speed up waveform display or confirmation if this is a known bug in Premiere Pro 2026.

I just updated to 2026 Premiere and every single time I open my project it crashes before it can open. Switching back to 2025

Hey everyone!I’m hoping someone can help me figure this out because it’s absolutely killing me.Up until recently, I’ve always been able to hold down the Shift key while clicking and dragging a track's edge in the timeline header to dynamically resize all video or audio tracks at once.Ever since updating my Mac to Tahoe, this has completely stopped working in both Premiere 26.2 and the 26.5 Beta. As you can see in the video I attached: I hover over the track edge until I get the vertical adjustment cursor. I hold down Shift and drag. Instead of moving all the audio tracks together, it completely ignores the Shift modifier and only resizes that one single track. My System Specs: Machine: MacBook Pro 16-Inch (Nov 2023) Chip: Apple M3 Max OS: macOS Tahoe 26.5 Premiere Versions tested: 26.2 and 26.5 Beta What I have already tried that didn't work: Resetting Premiere's UI preferences and workspaces completely. Toggling Mac Accessibility permissions off and back on for Premiere Pr

Issue: Holding the Shift key while dragging track dividers in the timeline header fails to adjust all track heights simultaneously. Instead, Premiere completely ignores the Shift modifier key and only resizes the single hovered track.Steps to Reproduce: Open any sequence containing multiple audio or video tracks in the timeline panel. Hover the mouse cursor over a track divider within the track header zone (next to track names/locks) until the vertical resize arrow cursor appears. Hold down the Shift key on the keyboard. Click and drag vertically to change the track height. Expected Result: All corresponding video or audio tracks should resize concurrently to match the height of the track being dragged.Actual Result: Only the single track under the mouse pointer changes height. The Shift modifier is completely ignored.Screen Recording: https://drive.google.com/file/d/1MXTTV74yZD1vIpy4q9dX3JdMTPH0zwpG/view?usp=sharingPremiere Version: 26.2 (Release) and 26.5 (Beta)Operating System

As you can see from the screenshots, I’ve set the target bitrate for 15Mbps.  When I actually render/export the video, the resulting file is 30Mbps.  I’m on version 26.2.2 (Build 3).  I got a new computer a few days ago.  On my old computer, I was using an older version which did not have this problem. When I set it by hand for 14Mbps, the resulting file is 25Mbps. What gives? 

５月の中旬までは重いファイルはフリーズしていたのですが、この頃は重くナイファイルを開いてもフリーズします。特定の行動をしたとかではなく、フリーズするようになりました。プレミアプロはいいドアンインストロールして再ダウンロードしています。パソコンの容量も１TB中、246MB空いています。何が原因なのでしょうか？

RGB curves within the Lumetri Colour panel aren’t displaying accurate colours or light adjustments. Making the slightest adjustment causes footage to look washed out. It doesn’t appear to remove all the grading, as it appears brighter than the raw footage. Image below These washed out colours occur within the Red, Green, Blue, and B&W channels. Making any slight adjustment causes the same error. In testing other footage from the same camera, RGB curves works as usual. No change in settings (4K 3840x2160, 50fps, 10-bit colour), and the same LUTs applied, which makes me curious as to why some shots work and others don’t.  More details:Occurs in this latest version 26.2.2 (build 3) and previous versions too.Occurs with footage from different cameras (Sony a7siii, DJI Air 3 etc)

I've dealt with this error before but it now seems to be on steroids - Frame Substitution Recursion attempt aborting after multiple attempts on file... Mac Mini M4 Pro64G memorySequoia 15.1Media Hard Drive - WD_BLACK 4TB SN850X NVMe SSDGen4 PCIe, M.2 2280, Up to 7,300 MB/s1.9TB available of 4TBPremiere Pro 24.?, 25.2 and 25.3 (beta) I'm editing multiple footage files that I've used consistently since 2022. They are h.264 mp4 files - basically B-Roll masterfiles for work that have never given me any issue. Some of the footage is 59.97fps, some are 29.97. None are variable framerate, all have been exported into these file formats from their original sources and used without issue for some time, including on a much less powerful machine.At the beginning of January I was using Premiere Pro (beta) - not sure which version - and every footage clip in the library started giving me the "Error retrieving frame" error. I couldn't get it to stop so I switched to the non-beta versio

I imported shots with double-system audio recorded 32-bit float having jammed an FX6 from a MixPre6ii.  I can sync camera (with guide track) and audio clips in the timeline via TC with no problem.  Here's the oddity: Suddenly the TC overlay in the Program window displays incorrect TC for only the audio clips (up to a minute off), but PPro seems to read the proper TC because I can still sync clips using TC in the timeline.  Also, I had TC properly displayed in a couple of timelines, but when I went to another timeline and then back to the timelines that had correctly displayed the TC, they now also displayed incorrect TC, i.e. the display went bad in seconds.  I had correct TC displayed in these timelines for weeks until this anomaly occurred.  I know because I did a test shot shooting the display of the MixPre, which displayed the same TC as the PPro Program overlay.   I uninstalled and reinstalled PPro: same problem.  On another computer: same p

On May 19th, Google added a new model, Omni Flash, to their Video AI generator, Flow. The latest versions of Premiere Pro (26.2.2 Build 3) and After Effects (26.2.1 Build 2) as of 05/22/26 are not properly decoding the codec used for the video outputs from this latest model. Obvious but randomly placed video artifacting is being displayed in both the preview and outputs from Premiere Pro and After Effects that are not being displayed in other applications or programs such as VLC Player, DaVinci Resolve, etc. I tried both the latest Game Ready as well as a clean install of the latest Studio Driver from NVidia for my 4080S but had the same results.

The outline of the mask not showing at all when creating a mask in any situation in premiere 2026

As title says when you have multi-cam view open any time you execute a ripple delete, where the playhead would follow the delete to the edit point, it instead just sits in place at the same timestamp, leaving you at some useless point randomly in the footage ahead.   A big workflow thorn when in multi-cam. Easy to replicate, create mcam, enter into view, and then try to ripple a clip section with your playhead in the middle of the clip.  It will stay in. place when it should snap left to the rippled edit point as usual for continuitySee attached screencap for extremely clear demo of issue.,25.3 Mac

after a certain amount of time, my premiere pro stops me using the timeline scroll, selecting multiple channels and also shortening/lengthening a clip via dragging. Makes it practically unusable at times! Please help.I used to think it was harddrive related but i started new projects without it connect to the harddrive and it’s still happening.It also doesn;t allow me to move the motion effect from left to right or up to down either, making edits VERY difficult  

IssueI’ve experienced some problems with the new Mosaic effect. It’s not only adds the mosaic but also adds a blur that will get the image softer, the bigger the tiles are.The legacy Mosaic in comparison adds no blur at all.The reason why I added this as a bug, even when comparing two different effects is because I don’t expect a Mosaic effect to soften the image in the first place, just to pixelate it (the blur is done before the pixelation. That’s my problem with it).There is a feather amount in the new effect but it only adds more blur and can’t be adjusted to the negative.Why don’t I just use the legacy version of the effect? As it’s legacy I don’t know for how long it will be supported and the new one has more settings that I would like to use. But the softening that I can’t change is a problem for me.Steps to reproduceI did test it with different settings, matching the tile size of both effects roughly.I also did a test with the tile size really high to show that a blur is added

I’ve had this bug since 26.2 and thought it would be fixed in v. 26.2.2 but it wasn’t. I have a huge project with several K media clips in different formats, mainly mxf, mp4 and mov. They all were given to me by a TV company, so they now how to shoot, trasncode and do other stuff with videos.The problem is that after I had imported all the videos I was to work with into the project, Premiere started to generate peaks to all of them and for several files it failed to do that. Now every time I launch this project Premiere does this:The process of generating peaks never starts, always hanging on that 0%. You cannot cancel it. And I would never pay attention to it if my CPU wasn’t roaring:Premiere certainly does - or rather tries to do - something but it never starts and never finishes. Yes certainly I can try and transcode these two MXFs to something else and it will solve the problem, this is not what I need help with. The problem is that YOU CANNOT CANCEL this process. You can see in th

Premiere Pro 2026 v 26.0Multicam functionality is gone. Using the number keys or mouse to select a camera does not work.

Dear Adobe Support Team,I am facing a major issue while importing subtitle files into the Premiere Pro timeline in the newer versions.In the previous versions of Premiere Pro, when I imported a subtitle file, it appeared as a single file/track on the timeline. This made it very easy to sync the subtitles with the entire video timeline.However, in the newer versions, the same subtitle file is being split into multiple subtitle clips on the timeline. Because of this, syncing the subtitles with the full timeline has become extremely difficult and time-consuming. It is almost impossible to move or adjust all the subtitle parts together smoothly.This change has reduced usability and accessibility compared to the previous versions. The earlier workflow was much better and more practical for editors. I would like to understand why this change was implemented, as it feels like the testing or product team may not have considered real user workflow properly.Please confirm whether this is a bug,

Using the latest Premiere pro (V26.2.2). Just created a simple logo animation in AE and exported it with Quicktime (.mov) using ProRes 4444 with an alpha channel (RGB + Alpha).When I import the file into Premiere Pro, I instantly get a ton of red error messages that say ‘Error retrieving frame’ and then it lists a bunch of frame numbers and mentions the clip I imported.I’m working on a commercial for a large client with a tight deadline. I’ve never experienced this before. Been working in Premiere and AE using this workflow for 15+ years.I also tried the animation codec with Alpha and got the same error.I don’t have time to troubleshoot Premiere bugs.

After installing the latest SoundQ update (May 2026), Premiere Pro became almost unusable on Windows.Symptoms:Playback takes several seconds to start Playhead freezes or updates very slowly Timeline becomes extremely laggy UI still responds, but playback engine appears stuckI completely uninstalled SoundQ and the problem still remained.What fixed it immediately:Preferences→ Audio→ Manage Audio Plugins→ Click “Rescan existing plug-ins”Playback instantly returned to normal after that.Looks like SoundQ may corrupt or confuse Premiere’s audio/VST plugin cache or scanning state.

Issue – The last 2 versions of Premiere (at least) have had issues with WAV files playing, and after trying many different things to fix it, I’m sure it must be a bug in the software introduced with the updates. When importing WAV files into the timeline they will play for a while, and then after short period, or a few moves of the playhead, they will stop. In text based editing, transcribing does not recognise that there is any audio there at all. Opening old files that had perfectly functioning audio previously, now plays no audio despite the files still being there. Adobe can find the files on my PC (I checked through reveal in explorer), and clearing the media cache and resetting to default settings has not changed this. The files do not work when using render and replace, or if opened in Audition from Premiere.MP4 and MP3 sound work fine. To begin with the clips have a waveform in Premiere but this disappears when the file is saved and then reopened.    Steps to reproduce –  1) Im

When attempting to stream with SRT protocol as a caller it seems like Premiere is not correctly using the passphrase that I enter and instead its starting the stream unsecured. On my server I get these errors from the SRT protocol. !-->:10:15.122626/SRT:RcvQ:w2!W:SRT.cn: processConnectRequest: rsp(REJECT): 1011 - Password required or unexpected14:10:15.214513/SRT:RcvQ:w2*E:SRT.cn: @566080749: HS EXT: Agent declares encryption, but Peer does not - rejecting connection per enforced encryption.14:10:15.214592/SRT:RcvQ:w2!W:SRT.cn: @566080749:newConnection: connection rejected due to: INTERNAL REJECTION - ERROR:UNSECURE The exact same settings work fine when using Premiere 25.0. Streaming also works if I turn off the passphrase requirement in the server and send it unencrypted from Premiere.  So seems like passphrase is not added properly in Premiere 26.2.2. 

Issue: Mercury Transmit would not send playback to a specific external monitor on Display Port after a Premiere crash. The monitor was recognized and selectable in Preferences -- Playback, but no video output was delivered. Other monitors (including another one using a Display Port) could receive Transmit output without issue. The problem persisted across two major versions (v25 and v26), full system restarts, GPU driver reinstalls, and monitor resets.Ultimately resolved by switching Monitor 1 from Display Port to HDMI. Mercury Transmit appears unable to output via DisplayPort after a crash, despite the monitor being fully functional for desktop UI over DP.Steps to Reproduce:Was working in Premiere Pro with Mercury Transmit enabled, outputting video to an external monitor (Adobe Monitor 1) — functioning normally Premiere froze during editing — forced close Reopened Premiere No video output appeared on Monitor 1 Went to Preferences — Playback Confirmed Mercury Transmit was enabled and A

No Modo Edição cada pasta do projecto não estão a abrir individualmente. Cada vez que abro uma pasta de um determinado tema do video a editar não consigo voltar atrás e abrir novas pastas com outros temas.