Bug Reports

I'm putting together an editing demo reel, and I noticed the color was off for some RED/R3D 6K footage when rendering it for smoother playback. Long story short, when I render the R3D footage within the timeline or export it using Quicktime Prores 422 HQ (or 4444 or 4444 XQ), the grade looks much more contrasty, with blown-out whites and crushed blacks (see attached screenshots for example, including scopes). Prores 422 vanilla and 422 LT are both rendering the grade correctly. No other types of footage in the timeline exhibit this problem when rendered, including Fuji X-T3 4K LOG mov, H.264 mp4, older Prores 422 HQ mov exports of this same R3D footage, etc. I have hunted down numerous settings and tested them, and none of them seem to be the culprits (see below for details). It looks like a new problem with the codecs themselves, at least when it comes to R3D footage. Prores 422 HQ has always been my go-to for archival copies of my work, and I've used it numerous times over the years

IssueAfter updating to Premiere Pro 26.3.0 (Build 93), the Proxy → Reconnect Full Resolution Media command hangs indefinitely on "Locating media...".The exact same project reconnects correctly in Premiere Pro 26.2.2.EnvironmentPremiere Pro 26.3.0 (Build 93) macOS Mac Studio UGREEN NAS SMB over dedicated 10 GbE Proxies created using Premiere Pro + Adobe Media Encoder (Create Proxies)Steps to ReproduceCreate proxies using Premiere Pro and Adobe Media Encoder. Open a project with attached proxies. Make the original media unavailable. Choose Proxy → Reconnect Full Resolution Media. Browse to the folder containing the original media.Expected ResultPremiere should reconnect all original media within a few seconds while preserving the attached proxies.Actual ResultPremiere displays "Locating media..." indefinitely and never completes the reconnect.The application does not crash, but reconnect never finishes.ComparisonThe identical project, media, NAS, and proxy files reconnect immediately in

Hi. I’ve seen this reported multiple times in 26.0 and 26.0.2 but now I’m having this memory leak issue in 26.2.2 myself.Memory leak with a half of RAM freeImportant: I have 64 Gb of ram. Every time this issue happens I check the ram usage and it’s never above 36-38  Gb in total, coupled with all the other system apps. I also checked it with HWInfo which records parameters over time and when the issue happens the RAM is still half free. It happened several times all of a sudden while I was scrubbing the timeline. I normally work with 2 timelines so it might be the cause:My two-timelines workflowI should also mention that I updated to Win 11 26h1 from 25h2 recently so it might be a cause too because I had never had memory leaks before.My PC: 14700K, 4080, 64 Gb of Ram, half free SSDs. I have some media on my HDD too, like overlays and my sound library but I use them quite seldom and like 3-5 pieces a project.My media used is different, mainly my channel’s MXFs and MP4s and MOVs from dif

We are aware of an issue in Premiere version 26.2 and 26.3 that causes the transcription feature to detect pauses and fillers with less consistency than in version 26.0, resulting in fewer pauses and fillers filtered in text-based editing. Additionally, sometimes the range of the pause is not accurate enough, leaving too much silence outside of the pause range.While the new models are better at transcribing multiple languages within a single transcript, the language detection model may occasionally select a suboptimal model, leading to poor quality transcripts. When poor transcription quality is observed, try to manually select the correct language in the transcription dialog, many make corrections if there are not too many, or revert back to version 26.0. Workarounds and recommendations:Workaround #1 – manually set the transcription languageDouble click the offending clip on the timeline or in the project panel to load into the source monitor From the Transcript tab of the Text panel,

Suddenly the individual parameters in Studio Reverb has a large space when twirled down. 

After install of 26.2 the Home screen with previous files freezes for about 30 sek.During this time the profile image is missing.When the freeze is gone, the previous projects becomes clickable and the profile image appears.See images for example.  

There is a long-standing bug with the faux-style ALL-CAPS (TT) option in Font Properties for text layers. This bug affects both Premiere Pro graphic Text Layers and text inside MOGRTs.   When user applies ALL-CAPS, the text randomly displays upper/lowercase characters instead of all-caps characters.    The fix is to manually type the capital characters (a -> A) instead of using the all-caps button.   Sometimes, these also work as a temp fix for the bug: Uninstall/reinstall font Manually clear all Media Cache files Restart Premiere Pro   This bug disproportionately affects plugins that use MOGRTs for text templates (such as Mr Horse Animation Composer, Captioneer, etc)   Here are many user reports of this issue: https://www.reddit.com/r/premiere/comments/134pyqe/random_letters_are_lowercase_when_all_caps_is/ https://community.adobe.com/t5/premiere-pro-discussions/mogrt-titles-render-uppercase-lowercase-randomly/m-p/15399924 https://community.ado

to show me my projects and I have to click like 15 times for the project to actually open. Does it happen to others? I’ve cleaned cache.

Hi everyone, I have a Mac M2 Pro, the latest version is Premiere 2026. I import files from a GoPro, edit them, don't apply any effects, export, and get a rendering error: Error receiving frame 959 at time 01:00:33:13 from file F:\BM\GX010240.MP4 with replacement of frame 958.I have the same error on my second Windows PC.I searched the forums, but nothing helped.I imported into Davi@chi and Ka@cat, and the rendering ran without errors. How come?

When I import a sequence from an adobe premiere project into after effects, or when I copy layers from premiere and paste into after effects, opacity keyframes come into after effects. But audio volume level keyframes do not.  According to this page they should: https://helpx.adobe.com/premiere/desktop/use-premiere-with-other-apps/working-with-o[…]e-applications/copy-clips-from-premiere-to-after-effects.html But, I am unable to get the audio level information into AE.  In the past, the audio levels would come into After Effects in the form of the Stereo Mixer effect. I am using Premiere 26.3 and After Effects 26.3, having just updated from the previous version of AE26 and PR26 to see if an update would help, but it did not.

I always need to make small adjustments to the transitions via effect controls panel so it causes me extra clicks every single time. I don't know if it is a bug or intentional by Adobe. Please watch the footage included.(It has nothing to do with OS or system specs i tested it on 2 different computers you can easily reproduce the problem yourself so i don't see meaning to include them here.)

Got this today. My sequence pixel aspect ration is 1.0, the footage I use has 1,7. Normally Premiere has no problems with that and define pixel aspect ration correctly. No the interpret footage says the PAR is unknown and brings the clip into the project in this state: A fix is manual interpreting. Version 26.0.2 had no problem with the same file.

I've done some audio repair on a video clip that has already been edited into multiple sequences. I could open up each sequence 1 by 1 and select the clip, hit in point, copy the in point and paste it into the revised copy of the audio and then alt drag it or hit replace with clip, however, that would take forever with how many cuts there are from the source.So instead, I made a sequence that has the original video with the revised audio paired to it. All settings match the original source clip, timecode most importantly. I hit the Replace With Clip > From Source Monitor - Match Frame, and to my surprise, it does not match frame. Sometimes it shoots out an error, "The source clip lacks sufficient head material to match to the desired frame." And other times it does replace the media, but totally ignoring the match frame part and just replaces it at the first frame of the video.I've tried multiple different work arounds such as making it into a mutlicam sequence, experimenting w

Premiere 26.3MacOS 14.8.4 Intel RED footage now displays incorrectly on the source monitor, if that footage is part of a Multicam sequence. The base video file displays correctly, and the Multicam sequence displays correctly on the program monitor. A sample of the distorted video is attached. 

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

After updating to version 2026, the option to remove pauses after transcription is malfunctioning. I'm having to use third-party programs, even though it worked fine in version 2025. 

Premiere Pro 25.6-26.3 CUDA/R3D Issue (RTX 3090)Up to Premiere Pro 25.5 (version that introduced film impact plugins), RED Komodo and RED V-Raptor footage worked flawlessly on my system.Starting with Premiere Pro 25.6, projects containing RED R3D footage frequently crash or fail to open properly when Mercury Playback Engine is set to CUDA GPU Acceleration.The issue occurs consistently during project loading. The only reliable workaround is to launch Premiere using Mercury Playback Engine Software Only, open the project successfully, and then switch back to CUDA GPU Acceleration. Or open the project, experience the big, switch to Software only, the timeline loads, then use Cuda.After switching back to CUDA, Premiere usually works normally for a period of time.However, during longer editing sessions, Premiere can become unstable again. Symptoms include:Black Program Monitor.Playback becoming choppy, stuttering, or freezing.RED footage no longer displaying correctly.General GPU-related in

Subject: Timeline Clips Become Unresponsive After EditingI am facing an issue in Adobe Premiere Pro. After adding clips to the timeline and making one or two edits, the remaining clips stop responding properly. I am unable to move, select, or edit them on the timeline.At that point, I can work on only one clip at a time. To continue editing, I have to close the project/tab and reopen it again. This issue happens repeatedly and is affecting my workflow.Please help me resolve this issue. I have attached screenshots for reference.Premiere Pro Version: 26.0Operating System: Windows

The 26 version of premiere has no Mask on BLUR and it is irritating. It was a great tool and now is not there. Please put it again in the version.

I cannot open few options like film impact dashboard and even the basic options like speed duration etc

Mac Studio M2 Ultra - Premiere Pro 2026.3 .0 (build93) Tahoe 26.5.1When exporting timeline from Premiere Pro in Prores 4444 (no sound) and send it to Media Encoder the resulting file is black frames.If I export the same setup but directly from Premieres export window it turns out correct.I am exporting to local desktopMedia Encoder 26.2.2 (build3).

Premiere Pro 2026 displays a false "insufficient GPU memory" warning in the System Compatibility Report.System specifications:Premiere Pro 26.3.0 (Build 93)AMD Ryzen 9 7950XAMD Radeon RX 7900 XTX (24GB VRAM)64GB DDR5 RAMWindows 11GPU acceleration is enabled and set to Mercury Playback Engine GPU Acceleration (OpenCL).Steps to reproduce: Launch Premiere Pro 2026. Open any project. Open the System Compatibility Report. Premiere displays a warning stating that the system has less than the minimum required GPU memory. Expected result:No GPU memory warning should be displayed, as the system exceeds Premiere Pro's GPU memory requirements.Actual result:Premiere reports insufficient GPU memory despite detecting and using the RX 7900 XTX correctly. Playback, rendering, and exporting function normally, and GPU acceleration remains active.Additional information:The issue appears to be limited to the compatibility checker. No performance issues, crashes, rendering failures, or GPU detection

Ever since the last update (26.2.2 Build 3) , I get the "Transform cannot allocate a buffer larger than 30000 pixels" error, mostly when I add images of any size. Sometimes nothing happens, but usually the second I try to move or scale the image, apply any effect (or even just move the image clip in the timeline), I get the error, and the playback window just turns black permanently until I restart Premiere.

'Link media...' doesn't function the way it should when linking more than one clip at a time.  When I need to re-link the media for multiple clips in the same folder, I'll navigate to the correct folder, select the first clip and then Premiere takes over and rediscovers the rest. The problem is, Premiere starts looking for those clip names OUTSIDE the folder I've specified. The clips are IN the folder I've specified! But Premiere keeps looking elsewhere until it finds other clips on the harddrive with the same file name, albeit it in drastically different parts of the file directory, and then links them instead.   I've had similar problems in the past when bringing projects from one computer to another and allowing Premiere to discover the media. It looks outside the directory I pick the first clip from, and links to outside clips with the same file name (Sony's in-camera file-naming resets to zero after every 10,000 instances, so every year or so I end up with a new clip cal

Hi - I upgraded to 26.5.2 sometime last week and during the last few days, returning to projects that had been tweaked with it since, the project files were just not in their expected location. For years I've had this workflow :  Launch Premiere  Select the project from the recent projects panel or navigate to it if it's not within the recent projects list (which is always a "0_PremierePro_Scratch" sub-folder under the overall project's name on my drives)  Once in the project, "Save As" and tweak the suffix of the project's name to today's date  Edit away. "Save".   Rince and repeat.   The default location where the software always opens the "Save As" dialog box has always been the folder from which the project was open in step 2. above.    Always. Except since version 26.5.2 After fearing the loss of 3 or 4 of my projects edited since the update, I just found them scattered in various folders. I'm not sure what the trigger is, but it