Bug Reports

I just tried using it in Premiere and got a strange glitch that I can’t troubleshoot.I’m running Premiere 26.0.2 on a Mac.Screenshot attached illustrates the issue. The color fields stay regardless of rendering, timeline size, and frame rate.btw, it works fine in Premiere Pro 2025 and older versions. The issue is only with the 2026 version.Here is a link for the file: https://we.tl/t-QuN48F454DVPj6dm

Nell'ultima versione Pr la forma d'onda della traccia audio non corrisponde con l'audio effettivo, diventando così inutilizzabile

Hello,I would like to report what appears to be an issue with XML exported from Adobe Premiere Pro. Environment Adobe Premiere Pro 26.0.2 DaVinci Resolve 20.3.2 I found a problem related to overlap / Cross Dissolve transitions in XML exported from Premiere. When a timeline containing OL / Cross Dissolve transitions is exported from Premiere as XML and then imported into DaVinci Resolve, the transitions appear visually in the timeline, but during actual playback they are not applied correctly and behave like simple cuts. After comparing the Premiere-exported XML with a Resolve-exported XML of the same edit, I found the following transition parameters in the Premiere XML:<startratio>0</startratio><endratio>0</endratio>If I manually change the XML to:<startratio>0</startratio><endratio>1</endratio> the overlap / dissolve works correctly in Resolve. From what I understand, the original Premiere values may still be technically valid as XML d

I wasn’t gonna post this because I thought it was my system specific issue, but here’s another guy with the same problem and the same symptoms: https://www.reddit.com/r/premiere/comments/1si1vsv/premiere_pro_2026_hangs_on_initialization_when/The issue: at a certain moment Premiere freezes entirely or just the program monitor - it’s won’t play back at all. You normally restart Premiere to go on working but this is when the problem happens - Premiere won’t pass the welcoming screen having stuck on the initialization process:So you close it, launch it again and it won’t let you pass this window. The process also becomes strange, hanging there like this:Steps to fix it I tried and none helped:reset the preferences cleaned the cache I closed all Adobe processes in the process manager in Win11 reinstalled the whole suite of Adobe Apps having sweeped everything with CC cleaner too Uninstalled every third-party plugin for AE and PR one by one and tried to launch Pr after.THE ONLY solution - wh

Product: Adobe Premiere Pro 2026Category: Sequence / Nesting / Adjustment LayersType: Bug / Inconsistent behavior Summary:When moving content between sequences, Premiere Pro handles adjustment layers inconsistently depending on the method used. Dragging a nested sequence into another timeline preserves all adjustment layers, while copying and pasting the same content does not include them.

The animated glow and bright blue-ish color no longer appears as the graphics fade in from a blur. It is clear that several core effects have been discontinued, but this has only left a broken architecture. Resorting to the prior version(s) of Premiere only results in crashes and seized processes. SInce I pay handsomely for the full license every year, I am not pleased that Adobe has so thoroughly fractured a core product line.Please restore your prior effects or repair your interface. The current state of your applications are nearly zero value for the stiff price I have already paid.

I'm trying to do a rough cut of two rough cuts lol meaning I am importing.MP for files just to play around with a couple of options to show my editor and both have the following audio codec MPEG-4 AAC, 48000 Hz and when I drag and drop the MP4's into the import bin, there's no audio at all. I have tried to Transcode them as well honestly, about 100 times with various settings using Shutter Encoder and nothing works. I have the same issue every single time I don't know what I'm doing wrong and I'm losing my mind

When in the Essentials workspace, in the Lumetri Colour Panel on the rightside, there are times when I am using the Curves Graph and it just stops allowing me to make changes. My mouse can’t grab onto the graph. The only way to continue editing is to swtich to the colour workspace.

Desde hace casi un mes cambie mi computador de uno windows a una Macbook M5 PRO, desde que hice el cambio el premiere ha estado teniendo errores al momento de realizar la transcripción, ya sea que omite palabras, o simplemente las detecta como otra cosa que no tiene nada que ver con lo que dice el video, intente muchas soluciones, como borrar cache, desinstalar y volver a instalar todo, pero aun asi, nada, sigo sin solución, todo mi trabajo he tenido que hacerlo manual (el tema de la transcripcion, ya que la unica solucion que encontre fue pasarlo a mi pc windows hacer la transcripcion y luego volver a la mac, pero es un lio total, ya que compre la Macbook, por temas de viaje y ya que no siempre puedo estar en mi PC windows de escritorio, espero puedan ayudarme a solventar este problema, gracias de antemano 

Hi, I know that the title implies I should post it on BorisFX forums (which I also did), but I’d post here too since Adobe should cooperate with BorisFX in order to solve their common problem.The problem lies in insane performance drop when BorisFX plugins are used in Premiere Pro. Here’s a screenshot of a single BCC Film Glow:Just one property is animated with 3 keyframes, and the timeline shows this already:In a FHD sequence with a 8-bit 420 4K clip in h264. I can assure you that the long-gop here is not the problem. I have a 14700K-RTX-4080-64Gb PC which plays back 9 physical copies of this staff with no frame drops but a single BorisFX effect nails my system down. And it happens with any BFX effect. I have no problems with any other third-party plugins, Film Impact here can even be used in batches and no playback issues at all. But BFX are just the worst performers, any of them.And I checked the same BFX plugins in Davinci and magically there are no issues there. All the BorisFX ef

I've spent an hour searching through forums regarding this issue. It appears as though Adobe has decided that duplicate media isn't a big enough problem for their software engineers to solve. Instead, Adobe would rather spend time implementing AI and other features that lends themselves more towards marketing bylines than to fix long standing issues. I have tried every solution I have come across, and Premiere continues to import duplicate media when importing XML files. This is insanely frustrating and a massive waste of time. Plus, there's no way to consolidate the duplicates. The "Consolodate Duplicates" command does nothing. In all the advancements made to Premiere Pro, it somehow can't tell that two clips sourced from the exact same file in the exact same directory are, in fact, THE SAME. Davinci Resolve can do this. There are literally HUNDREDS of posts across many forums - both Adobe sponsored and not - asking for a solution to this issue. This post go back well over 1

When I go to the export screen, the whole editing interface goes black. The buttons are still there and I am able to export by remembering where the "Export" button is from past projects, but I have no visuals to see where it's exporting to, what quality etc. I have tried everything including uninstalling and reinstalling Premiere, with no luck so far. 

One of our editors updated a project from 2025 to 2026 and nothing using mp3s works. I've encountered this problem quite a few times over the years as well. Can't relink any MP3 files or drop new ones in - "the importer reported a generic error"  

Several transition effects are now showing a red line with the message that the effect requires GPU acceleration. It's strange that it doesn't appear in the timeline, but in the exported video, the darn red line indicates GPU acceleration. I'm using the latest Studio driver, version 595.79, for my RTX 5060ti.

The preview export screen has disappeared. It was there two versions ago, but now I get nothing on that screen. I cant even choose in and out points on that screen.

In Premiere Pro 26.0.0, several dropdown-menus are occassionally empty. Here’s a recording of the Project manager:The Dropdown-menu only populates when pressing Ctrl+Shift+Win+B to reset the Graphics driver. The populated menu only lasts for one click, then it is empty again. Empty dropdowns are found all across Premiere, Effects Panel, Options, everywhere. -------------------------------------------------------------------Windows 11 25H2, Build 26200.7462Nividia RTX 4090, Studio Driver 591.74Single 4K MonitorAMD Threadripper 3970X, 128 GB RAMPremiere Pro 26.0.0

================================================================================ADOBE PREMIERE PRO 26.0.2 — BUG REPORTScrubbing lag caused by progressive session-state degradation — page fault storm on memory-mapped proxy files================================================================================DATE: 2026-03-31SYSTEM SPECIFICATIONS---------------------OS:         Windows 11 Pro 25H2 (Build 26200)CPU:        Intel Core i9-14900K (24 cores / 32 threads)RAM:        32 GB DDR5 — 2x 16 GB Corsair @ 4800 MHz (XMP: 7000 MHz)GPU:        NVIDIA GeForce RTX 3090 — Driver 559.97System SSD: WD Black SN770 1TB NVMe (C: drive, OS + Media Cache)Proxy SSD:  Samsung 990 PRO 4TB NVMe (G: drive, proxy files)Media Cache: C:\Users\Owner\AppData\Roaming\Adobe\CommonPREMIERE PRO CONFIGURATION--------------------------Version:              26.0.2Playback Engine:      Mercury Playback Engine GPU Accelerated (CUDA)Source media:         Offline (proxies only workflow)Proxy codec:          Apple ProRes

CRITICAL Memory Leak: Premiere Pro v26.0 on macOS 26 (Tahoe) - 89GB+ VM_ALLOCATE Exhaustion Summary: I am reporting a severe memory leak in Adobe Premiere Pro 2026 (v26.0.0.72) running on macOS 26.2 (Tahoe). The application progressively consumes all available physical RAM and exhausts swap space until the system becomes unresponsive or forces a hard crash.This is not a standard "high usage" scenario. System logs confirm that Premiere is allocating untagged virtual memory without releasing it, forcing a SIGKILL or manual termination.System Specifications: Hardware: Mac mini (M4 Pro) Memory: 48 GB Unified Memory OS: macOS 26.2 (Build 25C56) Premiere Pro Version: 26.0.0 (Build 72) The Issue: While performing standard editing tasks (proxy workflow, no heavy VFX), Premiere Pro's memory footprint expands uncontrollably. In my most recent crash, the application reached 89.14 GB of memory usage on a 48GB machine, forcing the macOS kernel to create an 80 GB Swap file. Technical Analysis

Premiere Pro is the only software I've had this issue in. The issue manifests itself in slow scrolling speed in its windows and tabs. Below are video illustrations of one scroll movement up and down.- Project bin (1,5x as slow) - Graphics templates (2x as slow) - Effects (2x as slow)- Audio mixer (1,5x as slow)- Lumetri (1,5x as slow)- Metadata (2x as slow)- Export (2x as slow)In comparison After effects has the scrolling speed as it is in the Windows, and Premiere's timeline is also of the same speed:In the x1,5 tests you may think it's ok, but it's not - there still is a distinct difference between AE, Premiere Pro timeline, OS windows scrolling and those tabs seen in these tests.Surely I know I can bump up the mouse speed in the OS settings and that leads to higher speeds everywhere - the browser scrolling becomes too fast too as well as any other scrolling including AE. My OS windows scale is 100%, the mouse and everything have the default settings, so it is Premiere

En el panel de Texto > pestaña Transcripción, selecciono en el menú de 3 puntos “Generar transcripción automática”, eligiendo la pista de audio donde tengo los diálogos.Se ve aparecer la barra durante medio segundo y entonces se corta y desaparece, simplemente no ocurre nada y no se generan los diálogos.Con la versión anterior funcionaba a la perfección, pero desde la última versión no me transcribe en absoluto. El programa está recién instalado y con caché y configuración nueva.La secuencia no tiene nada más.

Prior to upgrading to v26 of Premiere Pro, Synchronize worked almost every single time. The scratch audio had to be really, really bad for it to not work. Now, with v26, it’s the complete opposite. Just about every time I try to synchronize, I get the message: Audio synchronize failure; Could not synchronize one or more clips in the current selection because a match could not be found.I literally went back to old projects that I had used Synchronize on and I get the same message for clips I know with 100% certainty worked with v25. Now, the audio track pretty much has to be identical for it to find a match. That defeats the entire point of Synchronize.What’s worse, when I transcribe the scratch track with my dedicated vocal track, it transcribes the words almost word for word, so the two tracks are good enough to be transcribed the same but yet Synchronize can’t seem to find a match. What a disappointment!

Hi Adobe Team,I’ve run into a significant performance issue with the new Premiere Pro 2026 (v26.0.1) regarding media relinking over SMB, which seems to be a clear regression compared to the 2025 (2025.6.4) version.The IssueIn Premiere Pro 2025, the initial relink/indexing of a large project (multiple TBs) takes some time, but once the metadata is cached, subsequent launches are fast, but still takes some unnecessary time. In Premiere Pro 2026, this "warm-up" benefit is gone. Every single time I open the project, Premiere spends the same full duration relinking and scanning the media. It’s as if the application is failing to commit the file-path metadata to the local cache or is forcing a deep re-scan on every launch, regardless of whether the files have moved.My SetupI’ve tested this thoroughly on a high-end setup to rule out hardware bottlenecks: Clients: New Mac Studio M4 Max (14/40-cores), 128GB RAM. Network: 10GbE to clients, 100GbE uplink to the switch. Configuration: MTU 9000

Hi,Since updating to the latest version of Premiere Pro, the Comparison View (Lumetri Color → Color Wheels & Match) is no longer functioning correctly.The reference frame slider does not navigate the timeline It is impossible to properly select a reference frame As a result, the automatic Color Match does not workI have tested this with:multiple sequences different clips and formats reference clips placed directly in the timelineThe issue persists consistently.I also tried:restarting Premiere clearing media cache switching renderer (GPU / Software Only)No change.This workflow was working correctly before the update, so it seems related to the latest version.Is anyone else experiencing this issue or found a workaround?Thanks

Mac OS Tanhoe and Premiere 2026 26.0.2 build 2. When I import RED Gemini footage the Output Transform Settings gamma curve gets changes to BT1886 from Log 3G10 meaning I can't preview a log image at all which is no good for grading. This is in the raw video settings tab. On the same shoot we used a RED Komodo shooting R3D too and it imports and the gamma curve sticks to LOG3G10 as normal. I installed Premiere 25 and imported the footage and it worked fine so it definitely seems like a problem with Pr 26