Bug Reports

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

It snaps to center of the frame and other elements as well. (25.5)It still snaps to centers but ignores other elements on the frame. (26.2.2)

Every time I press the windows panel in premiere pro to change from editing to something else, premiere pro suddenly crashes and keeps loading for few minutes without resolving until I restart the app.I have the 26.2.2 version and no new update is currently present.

Nenhum dos selects, nem Premiere pro nem a versão beta funcionam os selects.

When I first open a project everything is fine, however after a couple of minutes the program monitor no longer shows the blue wireframe around objects to adjust their size, move their anchor point etc. This is also true for masks in the program monitor. Working fineNot working a few minutes later 

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  

[Premiere Pro / MOGRT Bug Report]■ Issue DescriptionWhen inserting Motion Graphics Templates (MOGRTs) in Premiere Pro, the loading process frequently freezes at exactly 15%.Light/simple MOGRTs usually work correctly, while more complex/heavy MOGRTs often fail.In some cases, already placed MOGRTs inside existing projects become stuck in a “Media Pending” state and fail to render.■ System EnvironmentOS:Windows 11Premiere Pro:Version 26.2.2After Effects:Version 26.2.2GPU:NVIDIA GeForce RTX 4070 Ti SUPERGPU Driver:NVIDIA Studio Driver (clean installation performed)Creative Cloud Desktop:Running normally and logged in■ Symptoms Heavy MOGRTs freeze at 15% during loading CPU usage remains low No GPU spike/crash occurs Premiere Pro itself does not fully crash Dynamic Link Manager process exists Existing MOGRTs may become stuck as “Media Pending” Lightweight MOGRTs may work correctly Issue occurs with both Adobe stock/preset MOGRTs and third-party MOGRTs (Motion Elements, etc.) ■

I am running into a very frustrating problem where the new version of Premiere Pro doesn't recognize After Effects. I gave both programs full disk access on Mac and ensured the versions were compatible (up to date no betas). Any solutions?

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

Avec la version 26.2.2 Première Pro buggue dès que je souhaite effectuer une sauvegarde manuelle. Que faire ?! J'ai vidé le cache. Nous sommes sous Mac séquoia 15.3.2

Since I cannot find my previous bugreport after the redesign of Adobe community, not even in my profile > recent posts I have to start another one. This time it concerns the fresh 26.0 version of Premiere Pro.Render and Replace feature is glitchy in v. 26.0. It fails with timeremapping. Steps to reproduce:start an empty project, import media, cut it on your timeline take one clip and timeremap it. Try to render and replace. Result: Render and replace fails in vertical sequences. Steps to reproduce:from the previously created horizontal sequence copy and paste a clip in a newly created vertical sequence.  Fill the screen with it using the context command. Render and replace. Sometimes you get an error like above, sometimes you get this one: Render and replace fails with the new object mask. Steps to reproduce:in the horizontal sequence select a non-timeremapped clip, select it with an object mask, track it, place the unassigned mask on the opacity Render and replace the masked clip.

From time to time, practically with every project I'm still getting these video artifacts in the programm monitor. I know there was an issue with NVidia drivers, but so much time passed, and there were bugfixes confirmed in the drivers release notes, but I'm still having this issue in Premiere Pro 24.6.1 build 2.With any footage at random moments. I'm on Nvidia Studio driver 561.09 from Sep 7.Is that NVidia again or is it still Premiere Pro to blame? I know I can reset my video drivers with the Ctrl+Shift+Windows+B combination, but in the last project I had to use it 12 times, because the adtifacts reappeared.Will this ever be fixed? Look here, people are still having this issue: https://www.reddit.com/r/premiere/comments/1fre1mk/clip_thumbnail_preview_glitching_on_monitor/

I can no longer use Premiere to work. I'm paying for a service that bugs out constantly, and I have a great laptop to run it on. Can someone from Adobe explain to me why this is happening?There's no M4A footage that would cause this, and even if there were, that's no excuse for software this expensive to have the problem. I need to know how to eliminate it.I'm on the latest Premiere update as well as the latest macOS update. I've already tried lowering the playback resolution, even though the footage is only 1080p. I won't use proxies for a 1080p video, and for software this expensive, that's not an acceptable solution either.I need to understand why this keeps happening while I'm editing simple videos with no effects. I'm only doing the rough cut.Frankly, this is ridiculous, especially on a machine as powerful as mine. So one of three things needs to happen: either Adobe gives me free years of service, lowers the price, or finally fixes these problems for good. As it stands, I'm payin

The compatibility dialog needs to be updated to include all the Film Impact effects now that they are bundled in Premiere. When exporting Premiere Pro graphics to .mogrt with the command “Export to Motion Graphics Template...”, this is the compatibility warning that shows. It should not show, because the Film Impact effects are now “standard” as they are included in all versions of 2026+.  

26.2 had freezes. I upgraded to 26.2.2 as the promise was that the freezing problem was solved. (official mention on Updates). Instead, I can’t even hit the report button, without Premiere freezing. Since we have to maintain a proper language in messages, I will just say that it’s not only dissapointing but most importantly costing time and money having to once more revert to two versions before, in order to get the job done. Since 26.0.2 is perfectly working, but 26.2 and 26.2.2 freeze, it’s 100% proof that things are messed up in the two latest versions! I mention that so you don’t just ask what the problem is, i clearly stated it.

Special characters, notably å, ä and ö break when named markers are exported as HTML.Works fine when exporting to CSV or TXT however (see attached images).This has been an issue since 25.6, and is forcing me through work requirements to run legacy 25.5 version.

latest version of premier pro hanging frequently on my latest high-end PC, when I downgrade to old version there is no problem. please fix it 

Say there’s a marker on the timeline where a portion of it is limited by the in and out points like this:If you try to change the marker length by alt+dragging it like you would normally do, Premiere won’t let you, it will move the In and out point to where you move the marker, like this:So unless you clear the in and out points you won’t be able to change the length of the marker with alt.It’s a small bug and I suppose it’s easy to fix. I suppose alt”dragging is a default command for moving the in and out zone so it should just be changed to like ctrl+drag because this command is not used

Bonjour,Depuis ce matin, Premiere Pro 26 ne respecte plus la disposition de mon espace de travail enregistrée et n'arrive pas à repositionner correctement les panneaux tels qu'ils ont été configurés d'une session à l'autre.De plus, je rencontre un problème d'affichage lors du playback : la fenêtre ne se positionne pas correctement sur l'écran désigné. J’ai effecuté des test sur des versions antérieurs (Pr25) et version Beta et le probleme n’est pas present.

I didn’t take any special steps but it did choose to send some of these brightened clips to Media Coder. ISt doesn’t always require that. Can I ignore that choice when the red exclamation point shows? 

Desde hace 1 mes, noté que tanto Premiere Pro cómo Media Encoder, no me permiten seleccionar la opción de Codificación por Hardware, ya sea tanto H.264 cómo H.265, que son los formatos que más utilizo y que llevo usando por años.Ya modifiqué los settings, ya sean los de perfil, el nivel 5.2 o superior, CBR o VBR, 4K o 1080pNo pasa únicamente con videos editados en premiere, pasa con cualquier video que quiera ingresar a premiere o directamente a Media Encoder. Entonces, la opción de que fuera algún efecto que no use GPU, queda descartado.Mis Specs sonRyzen 9 9950X3DRTX 5080128GB RAMWin 11 ProYa desinstalé y reinstalé los drivers de Nvidia StudioYa borré las preferencias de ambos programas y utilicé la herramienta de limpieza de Adobe con ambos.Esto no me pasa con Davinci ni con Handbreak, dónde si puedo utilizar la codificación por Hardware.¿Saben si es un problema común o reciente?¿Existe solución?Si no, para saber si tendré que reinstalar Windows.Gracias por su atención

I have been using Premiere Pro 2025 since it released, and I've been having issues with the program freezing up my entire computer (spinning wheel, unable to click anything including outside of the program). I'm able to move the mouse for a minute or two before the entire computer seizes up and I have to hard reset the entire machine. 1. Premiere Pro 2025 25.2.3 (but this has occured with previous versions of 2025)2. MacBook Pro 2019 (i9 Intel) with 32GB RAM and 5500M GPU running MacOS 15.53. Open project. Edit for an indeterminite amount of time. It usually happens while clicking around on the timeline, either moving clips or copy+pasting something, but I've yet to determine the exact trigger. Project freezes sometimes as soon as the first click on the timeline, and sometimes after a couple hours of editing. Cannot regain control of the computer once this starts. Have to reset via holding power button for 10 seconds to force a shutdown.4. Expected result: no freezes at all.&

I’m experiencing an audio channel bug in Adobe Premiere Pro, and the same issue also occurs in the Premiere Pro Beta version.Issue:When I import a downloaded clip from the Project Panel into an existing sequence, audio only plays from one side/channel. However, when I create a new sequence using the exact same clip, audio works correctly on both sides.What I checked: The source clip is not corrupted Audio works properly outside Premiere Pro Audio hardware settings are correct Channel mapping and sequence settings were checked No export/download issue Speakers/headphones are functioning correctly Observation:The issue only happens in certain existing sequences. Creating a fresh sequence from the same clip temporarily fixes the problem, which suggests a possible sequence audio mapping or internal software bug rather than a media or hardware issue.Additional Information: The same behavior is also present in the Premiere Pro Beta version This suggests the issue may be related t