Bug Reports

This has been an ongoing issue with Adobe Premiere. It's not consistent but when it strikes it consistently does not open the window to start exporting media. Even if I reboot several times. I use the menu to open the Export Media functionality. Or I use Ctrl + M and no window is presented to create media. I can wait more than 10 minutes and a window never opens.

Bonjour, Depuis ce matin, lorsque j'ouvre mon projet Adobe premiere (qui marchait encore hier soir), dans la fenêtre programme apparaît le message "media en attente", et il ne se passe rien : aucun media n'apparaît. Pour voir si le pb était lié à ce projet là (qui marchait hier soir je le précise encore), j'ai fait le test de créer un nouveau projet Première : le projet se crée, mais dès que je cherche à importer un fichier dans le projet, la barre "importer le projet" reste vide, il ne se passe rien, l'importation n'a pas lieu. Je suis en plein milieu d'un projet important, pourriez vous me dire ce qu'il se passe ? Merci d'avance

Curious if this is happening to anyone else. I have a project that refuses to load. When I try to open it normally, it stops at the same spot, about 2/3 of the way loaded:  This is verson 3 of the project. I was able to successfully load v1 and v2. I've browsed a number of conversations with similar issues, and I've tried many of the methods that others say worked for them, including importing the project into another blank project. When I do that, it hangs at 69%. Sometimes it will move to 70% and hang for hours.Ihave tried this process on 3 different PC's. Here's other things I've tried:Restarting PremiereRestarting the computerLaunching Premiere as AdministratorHolding Ctrl+Shift while launching Premiere to reset plugin cachesHolding Alt while launching Premiere to reset preferences I have a number of projects that use the same camera type footage and are built the exact same way, with very little use (if any) of VST or other plugins. This is the only project tha

When I am batch exporting files (usually audio), I will include the option to create a Sidecar SRT file. For the workflow we use, a seperate program Storyline 360 will auto import captions along with the audio if the file has the same name, just a different extension (ex. Introduction.mp3 and Introduction.srt) . Unfortunately Premiere spits out the SRT files with the extension of the original audio or video included (Introduction.mp3.srt). This means I will have to manually go in and rename each file. For my work, this can end up being 40-50 per day.  I spoke with someone briefly at NAB Conference 2024 who assured me this was a bug and not a feature. If there were a way to remove this in preferences or another place, it would help immensely. Thanks, Thomas

I'm creating a new metadata property using addPropertyToProjectMetadataSchema and Premiere will create the property just fine, but it won't add any data into that property.  Below is code lifted straight from the Premiere Pro github sample page.  I've tested the same exact code in 23.6.5 and it works as expected where it both creates the property and adds data to that property, but in 24.3.0 it just creates the property and won't add data to it. Maybe I just have a setting wrong in 24.3.0, but I can't think what it would be!  modifyProjectMetadata : function () { var kPProPrivateProjectMetadataURI = "http://ns.adobe.com/premierePrivateProjectMetaData/1.0/"; var namefield = "Column.Intrinsic.Name"; var tapename = "Column.Intrinsic.TapeName"; var desc = "Column.PropertyText.Description"; var logNote = "Column.Intrinsic.LogNote"; var newField = "ExampleFieldName"; if (app.isDocumentOpen()) { var projectItem = app.project.root

Documentation is here. This is part of that post:“Since the optical flow library cannot sustain real-time playback, as it happens with the existing Frame Blend function, Premiere Pro uses the time-consuming Optical Flow only for Time Remapping for high quality renders” 1. What, as a user, do I need to know about the “optical flow library”?2. “as it happens with the existing” should probably be “as with” … but there’s probably better grammatical options for this whole sentence. This reads as very convoluted text.3. The meaning that seems to be attempted here is that Optical Flow clips probably need to be rendered for real time playback (and as a side note, this is less and less true in 2024, in my experience, though I would be interested to be corrected). This should be much clearer and presented in less convoluted language. R.

I am setting up a metadata display preset.In the Bin panel I have 2 fields labeled "Media File Path" and "File Path" - see attachedIn the Metadata Display panel when I search the word "path" I only see File Path and not Media File Path - see attached.When I deselect File Path (and save that preset) Media File Path disappears. There is a disconnect for me with these fields, with thier naming and behavior.I also do not understand why Media File Path is populated and File Path is not.  What is the difference between these two fields? Why is one populated and the other is not.Ideally I would like to remove the unpopulated field from the display but that is not possible at the time of this writing.  I like the ability to create my own metadata display in the bin panel to the way I work and manage the assets in my project. An additional question/request regarding the presets for the metadata display - I would love to have the preset bake in the display order as well.&nbsp

Hi everyone, I'm wanting to re-edit a project I did so i can edit it down into small clips for my Youtube Channel. When I load the latest file of the video, first off, it just reloads it into my media browser without putting it onto the timeline. I then have to go through multiple different auto-save iterations of the file that will open on the timeline. Once I found one that loads onto the timeline, I got greeted with the message saying i need to locate files (yes i have moved the files around which i know is the reason why). I locate where the files have been moved to. Now, all the music works fine except my voiceover, with the red bar and green stripes appearing. This is very frustrating and would appreciate some guidance. There is no option for me to right click and hit "find and connect" which i've seen others put forward as a solution. Please help

I have the latest version of premiere pro installed (24.3). in the editing timeline everything is perfect and nothing crashes, but when i render and export, drone takes (4k 60fps) crash/freeze. i've tried every way to fix it, i've changed sequences but to no avail. i installed the previous version (24.2.1) and it exported correctly. i use windows 11 and my video card is an RTX 3060

Hi, When I make cuts on a multi-camera sequence, the name of the selected camera isn't displayed anymore. Just the file name from the selected camera is displayed. It worked fine on previous versions. I used to get the [MC1], [MC2], etc. indicator at each cut I made, which was super useful, and now it's not there anymore. I've tried creating a new project, and it does the same thing. I'm using Premiere Pro 24.3.0 on Windows 10, and 24.2.1 on MacOS, and I have the same issue on both operating systems, using different projects. I just installed the Beta version on Windows and the problem is still there. This makes me think that this feature was dropped / forgotten during the last updates, but it was really useful, and I hope we can have it back.Any help is appreciated. Thank you. 

Hi I’ve noticed an ongoing issue with Premiere Pro for the last 2 days where while playing back my project, my computer screen has these black flashes that occur at random.  It doesn’t matter what project I’m in. It still flashes everytime during the playback. This is my 1st time experiencing this type of issue and I can’t find a way online to resolve it.  Do any of you have knowledge on how to settle this matter? I've tried updating and restarting the application but nothing has worked 

I have done my color correction with Lumitri color within Premier Pro, I have set my render and noticed that the persons face is very red in the render preview, after looking for a solution, I found a forum that stated that with the final render it will look correct, this however was not the case, and the render is very red.  How do I fix this problem?  I have picked this problem up after I updated to the latest Premier Pro

Save an image with Photoshop (File > Save As) and make sure the Color Space of sRGB is checked:Import that image into Premiere Pro. Premiere Pro will not register this image as an image with a Color Space, saying that this image is "Not Color Managed," under Lumetri Color > Settings > Color Space Conversion.Workaround: Save the image in Photoshop under File > Export > Export As > PNG >  making sure these two checkboxes are checked:Click Export. Premiere Pro will register this identical image under Lumetri Color > Settings > Color Space Conversion as sRGB.  In the past, Photoshop saving as a sRGB under File > Save As > [Filename].PSD worked just fine in Premiere, but someting has changed with the latest version preventing this from working. Now it's a bunch of extra steps that forces destructive editing by saving as a PNG instead of a PSD.  

For my line of work, I need to open an old Premiere project on occasion to edit something that was originally completed anywhere from six months to three years ago. Most of the time, I save it as a new version to be compatible with the current version of Premiere and go about my merry way with no issues. However, occasionally I will open a sequence from an old project and every clip on the timeline will start at the beginning of the timecode. In other words, all the in/out points are messed up with audio and video both starting from 0:00:00 in the media file. In the most recent case of this happening, only one of four sequences in the project was affected. On my team, we store all of our projects on a network server and keep everything very well organized. Edits to any given project may be done from multiple machines but all are connected to the same server and accessing the project file from the same location. I've tried many things to try and solve/revert this issue in

The old Video Limiter (Legacy) properly held IRE levels to between 0 and 100 IRE (or however you set it).The current Premiere Pro (Ver 23.6.0) Video Limiter looks just fine on the Lumetri scopes. But after export, there are STILL pixels below 0 and above 100 IRE. And it doesn't matter whether the limiter is on the clip in the timeline, or on an adjustment layer above.Take the exported file, plunk it back into a fresh timeline, and all those out-of-range levels are still there.You're audio folks understand what a limiter is — no signal goes beyond (signal limit goes here).I understand that the YouTubers and TikTokers of the universe don't give a pixel about IRE levels. But those of us in the broadcast world — you know, your original customers — NEED to have functions that, well, function. Otherwise, our content doesn't get broadcast, and we don't get paid.We need a Video IRE Limiter that CLIPS the signal to the correct level and doesn't just fudge some compression and call it a day.(The

When I select a clip and adjust the Position / Scale values, it seems to be fairly smooth. When I click the 'Motion' tab to show the Outline + Anchor point, suddenly adjusting the position / scale values is extremely slow and unresponsive.  Version 24.1.0 (Build 85) Worth noting that adjusting the position / scale values in any timeline with a slightly more significant amount of footage becomes extremely laggy too... The files I am using:File 1 Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : Main@L4 Format settings : CABAC / 4 Ref Frames Format settings, CABAC : Yes Format settings, Reference : 4 frames Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 8 min 16 s Bit rate : 6 601 kb/s Width : 1 920 pixels Height

I feel like I've posted this before or on user voice but can't find the thread.  This bug has been around for a couple years now and it's a really knife to the old workflow. There are two ways to trigger this bug:  Option A (most common)  1. Open PrPro2. Start a project3. Add some dynamic linked files (anything, text, vfx, doesn't matter)4. Leave AE open.5. In PR. Render timeline green. 6. Close AE7. PrPro kicks open the BG AE render for dynamic link8. All render files are now set to red. You just lost whatever renders you've had even though you made 0 changes to the dynamic link file.   Option B:  1. Open premiere project with dynamic links. 2. Render entire timeline green 3. Open after effects proejct file into the foreground (CMD/CTR+E is usually what does it for me) 4. Change literally nothing.5. Close AE6. All Render files go from green to Red, wasting a lot of time here! Workaround: Don't open or clos

Hey everyone! I have some shaky clips I need to fix but I haven't had to do that for a few months now. Anyway, I was shocked to see that I have to wait 30 minutes for my clip to be analyzed?! For context the clip is 14 seconds long with 342 frames. I don't remember ever having to wait more than about 5-6 minutes for a clip to be analyzed before... Did something change with PP again? Is there anything I can toggle or fiddle around with to figure out why this is so? Any and all help/info is appreciated, thank you!

This one really grinds my gears.  SpecsWindows 11Latest Nvidia Studio Driver2080ti RTX24 core 3960 PrPro 23.5 Steps to reproduce  1.Create timeline with 10+ audio tracks and 3+ video tracks. 2. Lock all of your audio tracks. (shift + lock)3. Try to scrub4. Slideshow ensues5. Try to re-size audio video/break6. Slideshow 7. Unlock all video tracks8. Normal performance returns.  Theory: Something about how premiere draws that hash pattern is very 1993 and is not drawing properly causes the whole interface to drag even the program monitor. Will post video shortly.   

Hello,yesterday night I started getting a new problem with the newest version of Premiere.I was working on a project (Full-HD sequence with 25fps) and when I wanted to export I got a very weird notification for the first time. Every time I tried changing this weird resolution showing up here I automatically received this message saying something like "Invalid frame size or frame rate for this level. Reduce frame size or frame rate or increase settings for the profil / the level". I then tried both but nothing worked. I don't know why it gives me this weird resolution 720x576 in the first place.Today, I started working on a completely different project. Again, 1920x1080 sequence and 25 fps and the same error pops up. I should mention I have ALWAYS worked with these kinds of videofiles and never had I stumbled upon this, so it's not possible it's a corrupt raw video or something.The work-around is using the 2023 version of Premiere. I don't get the problem there. But this means I ca

The video attached explains it best - simply put, I'm experiencing behavior with my masking handles in Premiere Pro that are unexpected. When I drag click my mouse in previous versions of premiere pro with the masking tool (hovering my mouse over the preview window with the pen tool, left clicking and holding left click while dragging does not create long bezier handles, which it used to in older versions of Premiere Pro) it worked fine.Now, the bezier handles get stuck at the node that was just created, and it's infuriating. Because I can't even move the node now since there are handles that get clicked first. The nodes aren't even un-bezier, which would be better!! The Premiere Pro pen masking tool creates bezier curves that are weird/strange.

I just updated to 24.2 and suddenly my razor and rolling edit keys are not working, and not displaying. Had to roll back to 24.1 in order to get them back. I haven't had time to investigate whatever else isn't working; that was enough.

Here's how to reproduce this:(1) create a green matte and a red matte, put the red matte on a layer above the green one. It should look like this. All further operations are on the red (top) layer.  (2) create a rectangular mask on the red layer by clicking the rectangular mask. It should look like this: (3) nest the red layer and put a wipe transition at the beginning of the layer. (4) Now as I step through this video frame by frame by pressing the right arrow key repeatedly, I first see a black rectangle unexpectedly, then red color starts to wipe into this rectangle. If I stop pressing the arrow key, after a second the black part will turn green (green is what I expect), until I press the right arrow key again. Turning off GPU in project setting seems to make this go away. Can anyone reproduce this? I have an old nvidia GTX 1080 gpu with the latest driver installed by nvidia experience, and I tried both the studio and game driver with the same result. I

I have a sequence with one track of audio and I've Enhanced it.  It's a talking head "template-based" project that uses one shot of the talent delivering one line to the camera so I'm reusing the opening and graphics by just duplicating the sequence and using REPLACE EDIT with new person so my color correction and framing stays the same. When I do the a replace edit, the audio track gets replaced with the new one but the sound from the old audio track stills plays over the new one - even though there's just one audio track in the timeline. The workaround is to option-click just the audio in the timeline and choose Render and Replace.

We are aware of an issue affecting some users in Premiere Pro, After Effects and Media Encoder version 24.2.  A crash on startup may be experienced for some Windows systems with certain NVIDIA GPUs supporting CUDA.  Some user are also seeing that they cannot enable GPU acceleration for CUDA.  At this time, we do not believe an NVIDIA GPU driver update will resolve the issue since the issue is believed to be in the Adobe codebase.   While we track down the source of this crash, we have decided to pull the 24.2 releases of Premiere Pro, Media Encoder, and After Effects from the Creative Cloud Desktop application.  We plan to issue a 24.2.1 patch as soon as the issue is fixed.   This issue affects Premiere Pro, Media Encoder, and After Effects.   Workarounds and recommendations: Revert back to 24.1 or Update to 24.2.1 (once it is available)