Bug Reports

I've tried updating to 25.5 multiple times to see if the bug has been resolved, but I currently have to revert back to 25.4.1 (build 3).This happens very often when I change the layout or move the windows around, but not exclusive to that. Premiere freezes not just the software but also all of windows. Every action is incredibly slow to the point that I have to force restart the computer.I'm using a laptop windows 11, Nvidia 4070 driver 581.57 (although I tried other drivers as well).I had this issue before in a previous version of premiere a few months ago and the last update fixed it, but now it's happening again.I already tried clearing all the cache and fully resetting all the settings and the problem still happens.

Timeline/audio still playing but the Program Monitor is frezeeI have issue constantly, one time every hour, so it's 4-5 times per dayI tried the methods I found on Youtube/reddit but nothing works.My hardware info is also atteched, but I think they're good enought to run the software.How to prevent this?FYI, I never have this problem using other video editing software, only Premiere Pro. 

Since the latest update 25.5 I have been facing stuttered playback. it is so extreme that even after rebooting Premiere several times it still persists

Premiere Pro 25.4.0 on Win11. Today I discovered that my recent auto save files got stored in the wrong place. As long as just one project is opened, everything seems to be OK. But if you open a second project from a different folder, Premiere Pro starts putting the auto save files from the first project in the second project's folder. Even after closing the second project, premiere continues to store in that wrong folder.Luckily I was able to find the location of an auto safe file after my PC crashed. But it took me a while to figure out where they went. I sometimes open multiple projects to move clip preferences, effects or other things from one to another. Now I have auto save folders with mutliple states of up to four different projects. What a mess!

Just started getting this error window today while working on a very simple project that only has a couple After Effects motion graphics clips, and three tracks of audio: VO, music, and light SFX:   Event Details: Can't access audio the audio for _____.wav can't be read quickly enough from storage. Please check your storage and try again.   Build: Windows 11 Pro 26100.3624 12th Gen Intel i7-12700K 3.60 GHz 32 GB of RAM NVIDIA GeForce RTX 3060    The local C drive is an NVME SSD, but the file in question is stored on a Synology NAS with IronWolf HDDs. Both the computer and the NAS were built from new parts this year.   Premiere: 25.2, installed this week.   The same error happened on a second computer (same build, also connect to the NAS).

Essentially whenever I minimize premiere pro and bring it back up my program monitor goes full screen for a couple seconds before returning to normal and allowing me to see the whole program again. I have no idea what could be causing this. I have attached a video showcasing the problem. Anyone have any ideas?Issue: https://youtu.be/4FrVGP8cELU Premiere Pro 25.5Windows 11 24H2 

Hi There, Mac OS 15.7.1Premiere 25.0.0 I've had a consistent issue for many versions of Premiere. When I batch export to media encoder, and select a file path to render to, the path is not maintained once Media Encoder imports the sequences. I have to re-select the file path. This is a bit of an annoyance that adds steps and time to any batch exports I do. Thanks!Randy

Don't know if this has happend to anyone else, but ever since I updated Premiere and Media Encoder I keep getting errors saying "Returned Bad Result" This mostly seems to happen when rendering sequences that are 23.976 FPS. I rolled back to the previous version and everything works again so I'm guessing this is just a bug in the latest version of PR or ME

I've submitted this bug several times now.  2 things: how do we know if adobe has acknowledged a bug? do they respond to let you know? 2nd thing, the bug itself:   take a nested sequence, insert it onto timeline.  Add another layer in the nested sequence, apply time remmapping.  Sequence will go black before it reaches the end of the sequence. This vid below demonstrates that it is not the normal behavior of a time remmapped clip.  Most of the time when I encounter this bug it is when the original footage is not the same res as the final sequnce.   [hyper link removed by author request]   [Typo removed from title. — Mod.]

I noticed recently, that when using H.265 footage, that Premiere will work fine for a while then suddenly start having memory issues, and eventually lock up and black screen my entire computer. Sometimes I catch it before It does, and close the program, but then when I try to reopen it, it just hangs in the background and never opens.  I tried using Encoder to convert the footage to H.264 for the problem persists. I reset preferences, cleaned cache, did a clean install, everything. The only (Temporary) fix, is to completely restart my rig, and this only helps for about about 10 min of editing. Currently, I have noticed the issue when I download AI footage from Higgsfield, and it doesn't matter if its just using the upscalers or the direct footage, the problem maintains, and it only started happening after the update. This issue is bad, as I use AI footage pretty regulary for mapping out the visuals of projects, upscaling, etc. Please Advise. System: Win 11 Pro v 10.0.261

Export renders all audio clips in work area / timeline when exporting between in to out which takes forever, even for an audio only export.My export was saying twenty mins - clipped out the two clips into a new sequence on their own and it was so fast it didn't give a time. Will this be fixed soon? v25.5 build 13Mac studio M2 Max 96Gb. Sonoma 14.7.3 (23H417)

Premiere ahora selecciona otra fuente cuando cliqueo en otra variante de fuente desde el panel de texto.Premiere pro v25.5 Osx Tahoe 26Después de la última actualización a la versión 25.5, si quiero seleccionar un fragmento del texto para poner una variante de fuente por ejemplo de normal a black, en lugar de cambiar la variante, cambia la fuente completa por otra (la que está inmediatamente arriba en la lista) 

Let me try to explain the issue the best way that i can, i like coloring my scenes individually (i color a clip, copy the lumetri color settings, paste on the next clip, and change whatever is necessary while mantaining the coloring style, i'm not a fan of adjustment layes for color grading since each clip can have different lighting and such)I started to notice if i color grade a clip, sometimes the lumetri color will get "stuck inside" the clip and i cannot remove it. My main work is videos for parties and weddings, I always make a first sequence just for selecting the clips that i will use on a video, then a second sequence for the actual video with the selected clips, music, effects and color grading, so if i accidentaly delete a clip i have my first sequence as a backup.Here's an example, i finished the main video on the second sequence, i got back to the first sequence (again, the first sequence is just the clips i selected to use, no color grading or anything) and it alread

Hey y'all, long time user, first time poster. I am having an issue with FI: Grow FX and FI: Shrink FX. Upon rendering a preview, Grow FX will be zoomed in unreasonably far, so far that all you can make out is a solid color. The inverse happens with Shrink FX, wherein the clip will become so small it does not even show. This issue can be corrected by changing any of the parameters in the Grow or Shrink effect controls, but it's a coin flip whether or not the issue returns when rendering previews. I've experimented several times and have not found any patterns - sometimes it works, sometimes it doesn't.  Thankfully, the issue has not persisted through to exporting, but I attribute that to the fact that I've chosen to export with software encoding. I don't appear to have a software encoding option for previews though, so this bug is a huge pain for reviewing videos before export.  Knowing that, I've tried reinstalling my nvidia drivers, to no avail. I've also trie

I continue having issues in PP2025 when using LUTs that on R3D footage. When using the Media Browser to import clips with In-and-out points, the preview is displayed in a very strange way. It takes forever to load, and is a very frustrating process to import footage. How can this be fixed? Attached is a screenshot of the issue and how it appears, along with a screenshot of the R3D file settings. 

Hi there!MAYDAY MAYDAY..Is anybody can tell me how to fix this probleme ? Thanks in advance

Match framing subclips back to master clips does not work if they are in separate projects in a production. Steps to recreate1. Import master clip to master clip project in a production 2. Create subclips and move to a subclips project in the production3. Create an edit in an edits project in the production & add the subclips made above4. Match frame from sequence X2  Expected behaviour:Sequence should first match to subclip, then to master clip. Observed behaviour:Subclip does not match frame to masterclip (like it does where everything is in one project). Added bonus:Make one of the subclips NOT be restricted to trim region - now the 2nd match frame matches to the start of this sub clip, regardless of actual match point.

Hi all, It's one of those days I wish Adobe had a hotline for pro users... grrrrr... So I've been working on a Premiere Productions for a long time. It has several projects and I normally have 5 or six of them simultaneously opened.  Most of them have media files and only one has the assembly cuts, which is where I spend most of my time. About 40 minutes ago I noticed that, out of the blue, the undo command was no longer working. As I had auto-save on and I was able to (apparently) "save all", I pushed through for more 10 minutes till I decided I had enough of it, saved all once again, quit the application and restarted.  I was able to reopen the Productions and all looked fine WITH THE EXCEPTION that the project with the assemblies simply didn't save AT ALL! None of the work I've done in it for the past 3 hours was saved! Strangely, all the other projects were saved normally. To make matters worse, that project wasn't autosaved either, while the others we

In Premiere Pro 24.3, the Warp Stabilizer effect is extremely slow when processing log footage with the "Auto Detect Log Video Color Space" option (ADVLCS) enabled in the Lumetro Color > Settings panel. I'm defining slow as 1/12 the speed observed when applying a fresh instance of Warp Stabilizer to the same clip with ADVLCS disabled. The log footage was shot on a Panasonic S5ii (4:2:2 10-bit LongGOP, 150Mbps) and I am actively using Quicktime ProRes proxy files (quarter frame size) when applying the Warp Stabilizer effect in both scenarios. A few quick computer specs in case they are relevant: Primary drive is 512GB SSDProject and source footage drive is external SSD connected through Thunderbolt 3 port (Crucial X9 Pro, 4TB)Cache files stored on secondary SATA platter HDIntel(R) Core(TM) i7-7820X CPU @ 3.60GHz 3.60 GHzRAM: 32.0 GB (I know... more would be good!)Windows 10 Pro Education, Version 22H2 (OS build 19045.4046)Experience Windows Feature Experience Pack 1000

I'm just working on a project and for no reason this error appears and I tried all the solutions exists. Audio Hardware, Media Cache. etc...... Error Code: -1609891835 (NOT) (1609891836)

I recently upgraded to Apple Silicon (on an M1 Mac Studio) thinking that most of the kinks have hopefully been worked out, but here's a new one for me. I'm testing with a flat (Log C) ProRes MXF from an Alexa. I place that in a timeline based on the source res, and export out a ProRes 4444 at max bit-depth with 16 selected. I bring it back into Premiere. I overlay it on top of the flat MXF... and there is a significant green tint visible. Lumetri scopes indicate the same. Thinking it might be the way Premiere is interpreting the MXF, I also tested taking an H264 clip, exporting out a ProRes 4444 of a section, and bringing that back in - lo and behold, a green shift. Now for the most interesting part - I brought the ProRes 4444 that premiere created, and the flat Alexa clip, into Davinci Resolve. I put them next to each other in a timeline and toggle between the two clips while looking at the scopes - and wouldn't you know it - no green shift. So, it looks like for some reason, Pre

Summary: The Extract function in text-based editing does not work when initiated from the Program Monitor transcript. When attempting to extract (') a selected range with in/out points marked, nothing happens except the playhead moves to the in point. The Lift function (;) works normally in the same workflow.Steps to Reproduce:Open a sequence in Premiere Pro 2025 with transcribed audioEnable "Show Program monitor transcript" in the Text panel Enable "automatically set in/out points"Select a range of text in the Program Monitor transcript (in/out points are marked)Ensure all video and audio tracks are targetedClick the Extract button (or use ' shortcut)Expected Behavior: The selected range should be removed from the timeline and the gap should close automatically (ripple delete), matching the standard Extract operation behavior in Premiere Pro.Actual Behavior: The playhead jumps to the in point, but no content is removed from the timeline. The Extract operation does not execute.Wor

I have run into a pretty concerning bug that causes my entire computer to crash randomly (Event ID:41(63)) while using either Premiere Pro/After Effects. I know it is not a problem with my computer as while running other highly intensive programs such as blender, and even multiple at a time, I do not get crashes. Nor does my computer seem to be overheating, as my temperatures (I dont know if it spikes before it crashes or something to be clear) seem to be normal. My drivers are also fully updated. It ONLY happens when using premiere pro/after effects. I am not sure as to which program is causing the issue or if its a mix of both. The steps to replicate it are unclear as everytime it has happened it has been different and unexpected but I believe it has something to do with the fact I use an AMD GPU over a NVIDIA GPU, and I understand support for AMD cards will be lesser, but this is an unacceptable bug. I am using Premiere Pro: 25.5After Effects: 25.5OS: Windows PC My mo

I found out that Adobe Premiere is not utilizing the Newly installed RTX 5060.CPU- AMD 5700XRAM- 64GBGPU- RTX 5060SSD- 2X 1TB1. There are times that Adobe Premiere 2025 use the GPU for preview and playback, when i start and stop, it will stop utilizing the GPU and shift to CPU which cause stuttering in playback.2. This Issue happen everytime, So my workflow slowsdown.3. I am Editing 4K 422 10 Bit footage at 100mbps from Sony A7siii and FX30https://drive.google.com/drive/folders/18107UBikIlNZKeHNaLHsHQsOk9uH17ct?usp=sharing Can someone help me with this?All my OS, Drivers are up to date. I attached here a video file for you to see it.