Bug Reports

SPECSIntel Core i9-14900HXNVIDIA GeForce RTX 406064GB DDR5 RAM1TB SSDAll latest Adobe/Win11Pro/and video driversDELL SE2419HR 24" I made a detailed post about this issue before - which I was asked to make into a bug report.So I followed the instructions and made a very detailed bug report.That bug report then got merged into a megathread of some sort, omitting my original details and post - I have it in my email, but it links to someone else's report. MOGRTS with text boxes set to be capitalized decide to ignore some characters at random. I am still experiencing this issue, and I cannot keep explaining, uploading source files to drive to recreate - only to have an Adobe member stuggle to recreate it and then it goes cold - only to have it happen again and again. So I'm not making yet another bug report because my original already covers every detail incl uploaded files and fonts and mogrts and ppro files. Unfortuntately that bug report has been deleted and leads to this: https://commun

Wondering if anyone could suggest anything I can do to get my Premiere Pro working again. I was successfully using Premiere Pro 2024 until Friday. On Friday I used PP 2025 on another machine and subsequently installed Premiere Pro 2025 on this machine. I could successfully edit a video for about 10-60 seconds. Then the video, nor any of the imported media would play back - no video or audio will play. The footage remains frozen on whatever I was editing. If I leave it and some back to it, I don't get playback. I have to fully quit the app and reload to be able to edit for another little burst of time. I think I've watched every YouTube video with suggestions of what to try to fix this - I've emptied the cache, looked at audio settings etc. Reset all preferences. I've also downloaded the 2024 version again, but I'm getting the same problem with 2024 now too. I'm on Mac and not running the most recent Operating System, but that was the case too before Friday when I was suc

Hi there,Apologies if this is a repeat post but I have a couple of conditions and really struggle with information sometimes. I have gone back into a program file I did in 2024 as I wanted to make some changes.  Unfortunately, the Lumetri Presets that I used have stopped working and turned everything grey! I don't know if an update knocked everything out?   Can anyone help?  I was using "Canon C500 Clean Punch NDR", I made some changes to my liking and then - it's just stopped working.  I'm trying to avoid having to spend time doing colour grading again!  Can anyone help?  (Please explain as if you're speaking to an old granpa cos honestly, that's not far from the truth...)

I'm trying to export a film in 4k proress422 that has a 3840 x 2304 aspect ratio, 5:3 resolution. Adobe randomly displayed the film in the timeline as 16:9, but is still listed as 3840x2304. The black bars on the sides are missing and if I scale down the clips they just become smaller 16:9 clips. If I change the aspect ratio to 16:9 then the picture becomes slightly bigger and cuts off the areas around the border of the clips. When I export it, the film is in the 16:9 ratio even though the settings are still listed as 3840x2304. QuickTime also changed all my previous 5:3 sample videos into this 16:9 look, but has 3840x2304 as its aspect ratio in its settings. I don't know what the hell is going on where it even changed the aspect ratios look with clips and videos I exported a long time ago when this glitch randomly happened yesterday. I was wondering if anyone else has dealt with this problem.

ESTE É O MEU SISTEMA:GPU: NVIDIA GeForce RTX 4070 SUPER 12 GBCPU: 13th Gen Intel(R) Core(TM) i9 - 13900KFRAM: 128 GBE o sistem está travando simplesmente a cada 10 minutos me impedindo de continuar a editar o meu projeto. Eu tenho que fechar e reiniciar o mesmo o tempo todo. Comecei a trabalhar hoje às 8h e até agora eu contei 23 vezes em que tive que fazer isso. ESTÁ UMA MERDA TRABALHAR ASSIM. Resolvam isso, rápido.

25.6.2 build 1Video shows it all. These apps continue to degrade in quality. 

- have had the issue since 21st of nov, - program monitor stuck in full screen mode and unable to edit pictures and txt at all,- unabel to use it in general at all, cant click on the program monitor with mouse, non responsive.  

Hello Community! After 5 months of fighting with Premiere Pro I finally discovered what caused error code -1609629695. I believe that many people have been affected with it. I have a lot of people texting me about this problem cause I have made 3 posts about it in the past.SIMPLE ANSWER - DISABLE CREATIVE TAB INSIDE LUMETRI COLORI finally found the root of the problem and what is causing it. It's the CREATIVE pannel in Lumetri Color. Disabling it makes the error go away.  Issue – While exporting a video on versions 25.2, 25.3, 25.4, 25.5, 25.6 in random timestamps we get a GPU error code -1609629695Steps to reproduce:1. Add any .look file to the lumetri color CREATIVE pannel (I tried both - avaiable with premiere pro and made by myself/downloaded) 2. Export a videoExpected result – Video exported without any problems and bugsActual result – Error code selector 9, error code: -1609629695Adobe Premiere Pro version&nbsp

In Premiere Pro version 25.6.2, when I rename my video files, the name changes in the Files section, but the original file name still appears in the header of the Source Panel.This isn't a very new bug. I estimate this problem has been around for a few months. 

So I went through the long and difficult process of importing LUTs "definietly" in Premiere. Thank you to all your contribution, it helped me a lot. Here's the necessary informationComputer : MacBookPro M1 ProOS: Tahoe 26.1Premiere Version : 25.6.2The problem is : if you plan to put a LUT to a video, everything works fine. But I work so : I put LUTs on effect Layers to avoid editing each video and putting a LUT of each (maybe I should do so, but when I don't have time, I skip what I can) So i tried to apply a LUT from the ones I imported on an effect layer, but it just doesn't work, it takes the ones from the technical list and replaces them with the position of the original.Here's where my LUTs are : and the proof that my LUTs folder in the premiere app is empty: Here's an example: I try to select a LUT to put on an effect layer Premiere selects the eighth of the list (the last one from the originally provided LUTs) I try to select a LUT to apply on a clipPremiere has selected the rig

Latest Premiere Pro, 25.6.2, is freezing in a way it never has before. No crash dialogue box or grey screen no matter how long I wait, cursor still moves around but the program is completely non-responsive, just frozen in place, will not even close. Only solution is to "End Task" using Task Manager. Windows 11 24H2AMD Ryzen 7 5800H with Radeon Graphics (3.20 GHz)32.0 GB RAMNVIDIA GeForce RTX 3060 6GB

The timeline keeps freezing in several different ways, especially when it gets filled up with heavy projects like weddings or long multi-layer edits.When the timeline gets busy, the program starts lagging heavily, then completely freezes, and sometimes it even crashes and causes the entire system to hang.This issue makes it very difficult to work on large projects.Please investigate this problem urgently, as it seems specific to the 2025 version and wasn’t happening on previous releases.

In just the past few days, Premiere Pro has become basically unusable. Any time I try to click Export, Import, or even the Home icon, none of the buttons respond. I try installing an older version, but Creative Cloud just keeps them in an infinite loop of downloading. I try to uninstall Premiere and reinstall it but Creative Cloud doesn't let me uninstall Premiere. Incredibly frustrating, hope there's a fix. This has only been since Tuesday.

When trying to add adobe stock to a timline in premiere pro you get an error message to upgrade to the newest version of premiere pro. When running verion 25.6.2. You cannot add the stock to your timeline.

Mac Sequoia 15.7.2 Premiere v25.6.1 Closed captions not visible and there is not control in the Viewer wrench for toggling them on and off.Closed captions are required for broadcast tv. 

The "Slip Tool" or Y button on a Mac is laggy and does not perform as it should. I can not get an accurate slip of the footage when I drag it left and right. 

Premiere 25.6.2, Mac OS Scenario: I'm playing a timeline with a multicam clip in multicam mode. I see a place I want to cut. Without stopping playback, I key "add edit," then I hit spacebar to stop, press a key to change the camera angle (so it changes without making a cut), and then hit spacebar again to resume playback. All in very rapid succession. Unexpected outcome: even though the timeline resumes playing and I see what I'd expect to see in the viewer, the playhead in the timeline stays stuck to the place where I last stopped. And if I press spacebar again, instead of stopping playback, Premiere instantly starts playing again from where the playhead is stuck, this time with the playhead moving forward as expected. Nothing about this makes sense! To emphasize, I'm pressing this sequence of keys very quickly, almost like a piano arpeggio, so you'll need to do this to recreate it. I do this about 900 times a day, the bug happens quite often. Sometimes many times in a

when i export -> send to media encoder instead of exporting from premiere it strips the BAKED color on 1 out of 3 cameras and makes it log flat.  full context: i brought in clips from a hard drive and when i brought them into premiere i can see the full color. i didnt add color or anything. and when i hit export from premiere it maintains the color. i had a long rip that i didnt want to export through premiere because it would lock up the program from doing anything else so i sent the timeline to media encoder and i could see in the preview window as it was exporting through media encoder that it had stripped one camera of color and made it log flat. which is wild because i didnt add any color to it. the fact that media encoder is exporting something that isnt representative of what my timeline is tells me thats a huge bug. mac os tahoe 26.1 (apple m2 ultra). premiere version: 25.6.1 (build 2). (please send me a private message if you want to see a screenshot. i dont want

If I move a file in the finder, and then reconnect it in premiere, the media path of that item is sometimes weird, which means that premiere won't recognize it as a duplicate item if it's being reimported. And then, if the item does get imported again, it won't consolidate because premiere thinks it's two different items because they have two different media paths. By weird, I mean that the media path shown in premiere will for some reason add on an additional folder that doesn't actually exist. File Path: /Volumes/ZZZZZZ/ZZZZZZ/_ALBUMS/_TENSION/ATMOSPHERE TENSION FLUTTERING/ATMOSPHERE TENSION FLUTTERING/FTMX_LOCKDOWN__FULL-MIX.wav In that file path, that bolded section does not actually exist. Below is a screenshot of two project items, both of which are exactly the same file at the same finder location. Using the getMediaPath method in extendscript returns this: /Volumes/ZZZZZZ/ZZZZZZ/_ALBUMS/_TENSION/ATMOSPHERE TENSION FLUTTERING/./FTMX_LOCKDOWN__FULL-MIX.wav I can't reliably reprod

Même avec le correctif de ce matin (25.6.2 build 1) les fichiers récents enregistrés avec la v25.5 ne s'ouvre plus (message d'erreur). Ce qui est étonnant c'est que j'arrive à ouvrir des fichiers plus anciens voire très anciens (24.x) !!!!

FrameIO v4 updated panel in 25.6.1 is a little better but still doesn't export and shows incorrect frame rates on export profiles which seem to be unchangeable. H264 presets are either stuck at 29.97 (or 30 for Vimeo preset) despite your sequence settings. There's no option to create custom presets that I can see in the extension (custom just shows a list of one you may have created in the past. Mine had a VOB preset which I don't recall ever creating so maybe it's baked in there. ) still having to break out to browser use and not able to use markers in the timeline. FrameIO is truly broken, anyone know any decent alternatives I need to carry on working somehow! 

Product: Adobe Premiere Pro Version: 25.6.1 Platform: macOS (Apple Silicon) Summary In the latest update, the Frame.io v4 integration blocks exports unless the user toggles “Save as Separate Asset”. Only after enabling that option does Premiere show the folder selection dialog. After selecting a folder, the user can disable “Save as Separate Asset” again and export normally. This behaviour is confusing and inconsistent with previous versions. Problem The Export button remains greyed out even when inside a Frame.io project. The UI shows no way to select a Frame.io folder unless “Save as Separate Asset” is turned on first. The folder-selection dialog should appear automatically when exporting a new version, but it does not. There is no visible warning that a folder must be selected for versioning workflows. The workflow forces a setting change that is not related to versioning, which suggests a UI logic bug. Steps to Reproduce Open any Premiere Pro project linked to Fra

Made a ton of new custom presets with test names. When I finished up and decided to change their names everything was fine until I closed PP for the day and started a new session the next day. All my custom effects name reverted back to their old names. No matter how many times I change and save it, the names keep changing back.Im on windows 10, latest version of PP

Premiere Pro 25.6.1 sucks!My Premiere Pro just updated automatically, and it's causing me a lot of problems. It even happened on the day the client made the edit before it was actually used. The client blamed me for my inability to work, even though I didn't know what was going on. That's why I blamed myself.If this continues, I'll be permanently switching to Davinci and canceling my Adobe Cloud subscription, which I've been a customer of since my student days (15 years).And now, I still can't recover the backlog, I can only wait..which makes me very, very disappointed.

I am so tired of this HECV codec cannot be installed issue.  (premiere Pro)Hundreds of people have been complainging about it for SEVERAL YEARS now.They cant fix it though.  I know you need another PC for the workaround.  I dont have one.  Should not need one.Considering unsubscribing to adobe completely fix your product already!!and no I am not going to reinstall anything I have spent literal days on this issue time and time again over the years.  It's on their end but they wont find a fix for it