Bug Reports

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!

After updating to 2025 25.0 Premiere I noticed that after exporting 25fps timeline XMLs for grade, colourist receive 50fps timeline in davinci.After opening same timeline in the premiere 2025 24.6.3 it appears that 2025 premiere exported it as interlaced sequence.  Premiere 25.0 Sequence settings   Davinci Project Import ScreenPremiere 24.6.3 same XML import  

Whenever I try to open a project in Adobe Premier Pro 25, my OS crashes with no warning, no blue screen, nothing—just a hard restart. The behavior started two days ago. Since then, I've updated my video driver and ensured all other Windows updates and system BIOS have been updated.  I'm running on Windows 11 Pro build 26100. The processor is an AMD Ryzen 5 5600G, 3900 Mhz, 6 Cores, 12 Logical Processors, 64 GB of RAM. Radeon RX 6500XT with 512 MB RAM.  Here are the errors get thrown in the Windows log: 12/17/2024 9:52 PM Application Error Faulting application name: AdobeCollabSync.exe, version: 24.5.20320.0, time stamp: 0x6751fa64
Faulting module name: AdobeCollabSync.exe, version: 24.5.20320.0, time stamp: 0x6751fa64
Exception code: 0xc0000409
Fault offset: 0x0000000000524371
Faulting process id: 0x5A38
Faulting application start time: 0x1DB5

Dear Adobe Community, I regularly create scrolling text inside a graphics item for our quarterly graduation videos.  The graphics item/box usually handles around 300 names for a six-minute scroll just fine; rendering and exporting took a few minutes on my office Windows desktop. On my new MacBook Pro, just rendering the six-minute scroll is taking 9 hours, let alone how long it will take to export.   Steps I have taken to speed up the process:cleared media cacheensured that my sequence settings match best practicesswept my computer with CCleaner Attached below are my MacBook specs.  I am using Premiere Pro 2024 and it is up to date.  MacOS Sonoma 14.3.1. Your help would be most appreciated! 

If you have a search bin of items, and you've opened that search bin in a separate tab, you are unable to change the label of items in that search bin. It appears greyed on on the right click menu, and shortcut doesn't work. You can, however, change the label color on items in a search bin if that is just twirled open from within the project panel. To reproduce:1. Create a search bin with parameters that allow it to populate with at least one item.2. Open the search bin in a separate tab.3. Try to change the label color.  Expected Behavior would be label color changes the same as if you had simply opened a regular bin, but in this case, nothing happens. Running 25.1.0 on a Mac Studio 2023 running 13.6.6, but I've noticed this behavior in previous Premiere versions and other rigs.

[Premiere Pro 25.0, Media Encoder 25.0, After Effects 25.1 | Windows 11, i9-12900K, RTX 4080-S, 128 GB RAM]When using Productions with Premiere Pro on our larger projects with multiple editors, and exporting the final compilation sequence with all scenes through Media Encoder, there's a step before the actual video encoding that says "processing audio source...[filename]", and this seems to take a weirdly long amount of time, and I can't figure out why or what ME is even doing at that time. It'll perform this "processing audio source" task on both compressed and uncompressed tracks, and even rather short clips seem to take way longer for this "processing" to happen than it would normally take to export these as standalone files multiple times. It'll perform this "processing" for clips on muted tracks or submixes, and I've even duplicated a sequence, moved it to a fresh sub-project within productions, deleted all video tracks and half of the audio tracks...and exporting that stripp

Pretty simple problem that i dont have an answer for and could use some help. ive graded my timeline in davinci and have exported such as an xml timeline, now when trying to import it gets stuck at 0% forever . any ideas what could be going on?

Experiencing this issue on Premiere Pro v25.1.0 (Build 73) in Windows 10, as well as the same build on MacOS Sequoia v15.2. When selecting multiple Video effects in the Effect Controls panel (just through mouse clicks, with no keyboard modifiers), it automatically deselects the previously selected effect (this is the expected behavior). But when selecting Audio effects with a mouse click (again, just with the mouse and no keyboard modifiers), it will add subsequent Audio effects to a multi-selection. This behavior is identical to Ctrl-Clicking on multiple effects in the Video section of the panel. Once selected, Audio effects can only be deselected by Ctrl-Clicking on them, or by clicking on any open area of the Effect Controls panel, which deselects everything.  Furthermore, when using non-modified clicks on multiple Audio effects, and then selecting a Video effect in the same panel (if controlling a clip with Audio and Video components), the first&n

Hello I am using Premiere Pro v24.6.1 (Built 2) on a Windows Laptop. Windows 11 Home.I imported a 6K stereoscopic video mp4 (6400 x 6400) h264 which was filmed on Insta360 Pro 2 and is already stitched on Insta360 Stitcher app.I tried to export a short part of it in 4K (3480 x 3480) on PP. When played back on Quest 2, the video has a double black line where the stitch line is.When I export a 4K video directly from the Insta360 Stitcher, and play it back on Quest 2 there is no black line.Which means that the problem occurs in Premiere Pro.Please see the attached screenshot from Quest and the settings on Premiere Pro. Actually what I see on Quest is a double thin black line. The screenshot shows one thick line. If you view the screenshot as flat, you can see the line on the right hand side. Any advice how to solve this?Also, are there any tutorials for editing stereoscopic 360 video? The only official Adobe video is from 2018, 7 years old and obsolete stuff! It is very frustrat