Bug Reports

I recently got a new mac mini m4 pro and downloaded Premiere Pro to it. I like to use the metadata ratings for reviewing clips and this new UI (version 25.1.0) has them too large to fit in the default row height. I have to increase the height of the rows significantly before they'll fit. This wasn't an issue with my previous version of Premiere.  I didn't import workspace settings, I created it from scratch. Brand new Premiere Pro download so no chance of old files causing issues.  I tried quitting Premiere and restarting - didn't fix it.I tried turning off ratings in metadata settings – the column disappeared but the stars remained. Then when I re-enabled the rating display, it showed the stars duplicated on top of each other but offset.... what a mess. Any ideas on how to fix it or is this just Adobe's bad QA... adding issues that weren't there before?

When importing Phantom footage encoded at 25fps (we double checked this was correct in Davinci Resolve & GlueTools cine player) Premiere 2025 imports the footage at 24fps. We noticed this as we had created attached proxies in Premiere via AME. The Proxies although were also made at 24fps incorrectly they showed sync problems when toggling between proxies & cine files. 

Dear Adobe Team, I am using Adobe Premiere Pro 2025 and experiencing performance issues: Problem description:The software frequently displays the error message "Sorry, an error occurred", which severely disrupts my workflow.Additionally, it is impossible to use the software offline. Whenever I disconnect from the internet, the application automatically closes. Steps taken: Issues with Scripts and Extensions: While working with new features like scripts and extensions, I face significant malfunctions, which are impacting my productivity. Following your support pages and suggestions, I have tried the following: Checked all settings in the Preferences menu. Reviewed options under General and other sections. Inspected application files thoroughly using Finder. Executed several commands in the Terminal. Unfortunately, none of these attempts resolved the issues, and the problems persist. Outcome:These issues are wasting my time and causing unnecessary frustration. As the software i

Premiere Pro 25.1 does not relay the duration attributes (stretch\remix) from one audio track to another.Steps to reproduce:1) Place an audio on the timeline2) Change its duration via the Stretch or Remix tool, or in the duration menu of the Essential Sound tab(also note that the +- 5 seconds is always 5 even if you change it by 10 seconds or more) 3) Copy and paste the duration property on a new audio track The new audio track remains unchanged  

Premiere Pro Audio Track mixer jumping to TOUCH on AUdio 1 and Master Track when switching back to Premiere Premiere Pro 24.3.0 (Build 59)Operating system - macOS Monterey 12.7.3System Info: CPU, GPU, RAM, HD:CPU: 3.6GHz 10-Core Intel Core i9GPU: AMD Radeon Pro 5700 XT 16GBRAM: 64GB8TB External Hard Drive USB 3 Connections Video Codec Type: MP4/MOV H.264 4:2:0Regular rec.709 HD Sequence, 23.796fpsOpen Premiere Pro, switch to a browser, or any other program, Audio track Mixer switches Audio 1 and Master Mix to Touch by itself. 

Hey Folks This is probably a niche problem, but I've been having issues with the metadata & timecode effect, where the burnin in premiere wouldn't match an export via media encoder.And I think I've narrowed the issue down.Let's say I have a clip with a start timecode of 00:00:20:00I import, then set the start timecode to 00:00:25:00 using item.setStartTime(startTime); where item is app.project.rootItem.children[numItems]; Adding the metadata effect, in premiere it reads 00:00:25:00. If I export directly from the timeline, the burnin on the resulting mov reads 00:00:25:00. But if I send it to Media Encoder, the burnin will read 00:00:20:00, both in the preview window and in the resulting mov. My question is, is this expected behaviour? Is there a way to burn in the modified TC when using ME?I've tested this on both 2024 and 2025. Thanks!

So I've been having this terrible issue recently where a whole bunch of clips have been flashing in the timeline. CPU usage starts to go up and Premiere becomes unresponsive, requiring a force close. As you can see in the GIF below, a certain subset of clips will sit there and flash (this recording is in realtime). Flashing thumbnails in the timeline The issues started with a multicam sequence. Whenever I would trim or edit the embedded multicam sequence, it would cause all the corresponding clips to start flashing like this. My last resort was to attempt to flatten the multicam sequence into the individual clips, but as you can see they're still stuck flashing even as non-nested clips. I'm running the latest version of Premiere (23.6.0), I have the latest version of Windows 10 (22H2) and NVIDIA Studio drivers (536.99), I've tried:resetting Premiere preferencesclearing media/disk cachecopying sequence into a new timelineimporting the existing project into a brand ne

I had been having issues for over a week with Adobe Premiere 24.6.1. Every time I would play video that I had in my timeline, it would go for about 2-3 seconds, and then Premiere would completely crash. It didn't matter what kind of file I would put into my timeline, how big the file was, etc. No matter what would be in my timeline, if I would try to play it, Premiere would crash.I tried every possible suggested fix online for this, and nothing worked. I deleted my Media Cache, Uninstalled and Reinstalled Premiere, reset my preferences, and so on and so forth. FINALLY, I figured out that I could re-install old versions of Premiere. So, I re-installed version 24.6, and now my program isn't crashing anymore. I don't know if there's a bug with 24.6.1, but it should probably get looked into. This is the first time ever I have had problems with my application crashing after a software update. 

Hey - I'm hoping someone can help with a Premiere issue that I've been dealing with for close to a year now. Basically, Premiere just freezes up randomly: UI panels go black, the save dialog turns into a blank white box, playback stops working entirely etc... Only way to fix it is to restart Premiere, which is obviously a pain, especially since this has been happening every few hours, sometimes even more frequently.I kept hoping an update would solve it. Unfortunately, it's still a problem, and it's become so distruptive that I figured I finally decided it would be worth posting. Here’s a quick rundown of my setup and everything I’ve tried to fix it.Specs & Setup:OS: Windows 11 [23H2]Premiere Pro Version: 24.6.3 (but issue has persisted through past versions too)Hardware: Intel i9-13900K, NVIDIA 3070Ti, 96GB RAM What's Happening:UI glitches/ locks up (panels freeze or go black etc...)Error message: "Unable to create image buffer"Not easily repeatable (seems to happen rand

Hello all, I'm wondering if it's just me having this problem, or if anyone else is experiencing the same issues. I have had an Adobe account for a long time, and only earlier this year had the need to start using Premiere Pro for a YouTube channel I'm building (Secrets Of The Trails). I have:1) a Dell 27" AIO with 13th Gen Intel Core i7-1355U 1.70 GHz, 32 GB RAM, 1 TB SDD, NVIDIA GeForce MX550, running latest Windows 11 and all drivers updated.2) a Dell XPS 16 9640 with Intel Core Ultra 9 185H (2.50 GHz), 32 GB RAM, 1 TB SDD, NVIDIA GeForce RTX 4060, running latest Windows 11 and all drivers updated.3) a brand-new MacBook Pro M4 16", 42 GB RAM and 500 GB SDD. I run all of my images, video, and music files, as well as the Premiere Pro project files off of a 12 TB Western Digital NAS. I have had no problem running the last PP24 on either Windows device.  But once PP25 came out, I've had nothing but trouble.  I originally thought that the problem was my

Bonjour, Depuis la version 24, Adobe pro ne se lance plus. Je vois l'écran d'ouverture s'afficher puis se fermer rapidement sans aucun message d'erreur.- PC compatible- Utilisation de l'outil de diagnostic => tout est ok- Désinstallation / installation / reboot plusieurs fois toujours le même PB- Passage à la version 25 toujours le même pb.- Retour à la 23 tjrs le même problème.- Ouvrir l'app avec CTRL + MAJ ou MAJ ne fait rienJ'ai ce problème depuis des mois maintenant, je suis obligé de passer par un laptop moins puissant pour pouvoir utiliser Premiere.Comment puis-je régler mon pb? Cela commence à devenir très gênant, et les différents bots/contact n'ont servi à rien + aucun agent dispo.Merci pour votre aide!

When exporting a Quicktime .mov file with video disabled (so audio only), the embedded timecode track is always 29,97 DF regardless of sequence framerate settings.   Steps to reproduce: Create a multichannel sequence at any framerate other than 29.97, so for example 25fps Export to Quicktime with the 'video' option disabled The resulting file will have 29,97 DF timecode rather than 25fps as expected

[Moderator: we have tweaked the subject line for clarity]   I'm getting constant pop ups saying 'Premiere Pro would like to access data from other apps' which I have to approve, every few minutes while working! Also the first crashes I've experienced in months, since upgrading to macOS 15.0. Using Mac Studio, M1 Ultra, 64GB RAM. Premiere version 24.6.1 v2 Please fix, thanks.  

Updated to the latest Premiere Pro, however with the Insta360 Premiere Plugin installed, Premiere crashes everytime you try to import an insta360 video file format. Tried reinstalling everything and still the case!  

I have Adobe Premire 25.0.0 on MacOS. When editing the text and set it as RTL, it's not save in the track level, and I need to set up for each and every new subtitle clip.Here you see the RTL is selected, but it's never saved. 

If I try to adjust any setting with my R3D file the program crashes. White balance, exposure, tint, ISO, etc. My computer can easily handle the processing of these files and doesn't use more than 30% processing power unless I'm rendering or exporting something. I'm not seeing any driver failure, packet loss/corruption, or any other form of system failure when I troubleshoot on my end.  Seems like the program just doesn't like me adjusting certain settings at certain points in time. One thing I find interesting is when I let Premiere do it's "system analysis" it will tell me Premiere is not up to date & that my drivers are out of date. Both of which are untrue. Just wondering if anyone else has experienced this problem and found a solution? I've done all of the recommended troubleshooting and more that's usually prescribed for these situations.

I have a MOGRT that has an image replacement in it. Media Encoder 24.6.1 (Build 2) doesn't do the image replacement. When I preview the image replacement in Premiere Pro, the image replacement is made just fine.When I export it directly from Premiere Pro itself, the image replacement is made just fine.When I test the MOGRT image replacement in After Effects it works just fine. When I "export to media encoder" the image replacement fails, and the box is empty. Happens with both .JPG and .PNG images. Mac OS Sonoma 14.6.1 on an M1 Mac StudioPremiere Pro 24.6.1 (Build 2)After Effects 24.6.1 (Build 2)Media Encoder 24.6.1 (Build 2)

Currently any footage shot above 99 fps shows a timecode of 00:00:00:000 which is ridiculous. Premiere Pro should be able to read timecodes that are formatted with 3 trailing zeros properly so we can organize footage by timecode.

I am using the latest versions of Adobe Premiere Pro (2025) and Lightroom on a PC with the following specs:GPU: Nvidia 4070 (12 GB VRAM)CPU: AMD Ryzen 9 5900XDrivers: Latest Nvidia Studio drivers installedOS: Windows 11 (fully updated)Despite having GPU acceleration enabled in both applications, all tasks that should use the GPU (e.g., rendering, export, playback) are instead being handled by the CPU. I have already tried the following steps to troubleshoot:Ensured Mercury Playback Engine GPU Acceleration (CUDA) is selected in Premiere Pro.Enabled Use GPU for Performance with the Advanced option in Lightroom's Preferences.Verified the GPU is set to high performance in both the Nvidia Control Panel and Windows Graphics Settings.Installed the latest Nvidia Studio drivers.Reset preferences in both applications.Monitored GPU usage in Task Manager during tasks, but Premiere and Lightroom barely use it.The GPU performs wel

Premiere Pro 25.1 (Latest)Windows 10 - Desktop Hey everyone, This has been an ongoing issue but I have always figured it was a computer issue as these crashes always BSOD my computer rather than simply closing the app, however, as I've fixed the majority of my PC issues, it's now been Premiere Pro that has been crashing. I'm not running any plugins or using effects. The crash is caused by simply opening up a project with a moderate amount of files (roughly 30). These files are originally mp4 but I've converted them to proxies but still crash or the playback is horrible enough to see a crash is about to happen (roughly 2-3 second delay before playback begins). ******************************************************************************* * * * Exception Analysis * *

Premiere Pro has decided it wants to take a vacation. Today of all days, it has crashed 9 times without input from me. The first few times were while I was in-project. Nothing more than deleting or importing folders, and it would crash. After the first 3 crashes I decided to do nothing and time it.1) I initialised the app2) App goes through the standard splash screen3) Once the app reaches the home screen, the timer begins4) App spontaneously crashes without extra input (no opening projects, no clicking buttons, nothing) after 5-47 seconds (interval is always random) This has happened only today. The last "productive" session I had with Premiere Pro was 2 days from posting this (Saturday, 21st of December 2024, at around 6pm AEDT), and on that day it never crashed once. Previous instances I've had the app crash on me was when I was exporting videos (they technically don't count as the entire PC crashed during then, so it was more a GPU overload than anything else). And I

Hi, Mac Studio 12.6.2 Apple M1 Max - Blackmagic Extreme 3 - Thunderbolt 3.0 Premiere Pro timeline/source window playback freezes after a certain amount of pause/plays. You can still move the play head across the timeline/source window, but with no updated/live playback through the reference monitor. The picture will be frozen on the frame when the bug has occurred. The only way to resolve this is to restart Premiere Pro. If you press the space bar to pause/play repeatedly, you can enact this bug in around 2/3 minutes. I have rolled Premiere Pro back to v22 and Blackmagic Video Desktop back a full version with the same bug being present. Blackmagic Support have replicated the issue on their end - although they are unsure if the issue is Blackmagic or Adobe specific. I would add - this bug is not present on our PC editing station running the same software and hardware.   

I've imported a .mogrt file in premiere macOS, Premiere 24.2.1 (build 2) and 24.3.0 (build 59) It displays ok. The computer was left idle (turned on) for 1 day. There are missing files inside mogrt. If I open mogrt source in after effects, everything is ok. The behavior was reproduced on multiple mac computers. There are no special characters in the names. As far as I know mac does not have a path limit. The important part is the file displays normal after import and becomes invalid by itself later. It is a massive issue. Any advice? Funny enough I cannot attach .mogrt file here because it is not support. Here is the file https://drive.google.com/file/d/14A7QCiaP5_x28B111tes-wKlohvYIawM/view?usp=sharing

Hi,   Is it normal for certain black gaps to appear when zoomed out ?     They do not appear with the 2024 version (below)   Thank you !

Version 23 installed today, and a basic bug is still not fixed;I'm working with UHD footage on a FHD project, and when I export a static .TIFF 'freeze-frame' for Photoshop editing, I get a low quality pixelated image. Months ago I discovered that if I detach my proxy files first, I get a true quality export image.Note; I am not in proxy preview when exporting, Premiere simply exports from the proxy by default!