Bug Reports

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)    

If you're using the text box feature and your premier keeps crashing, this might be the post for you.   I'll keep this very simple. When you create a new textbox and type the letters "f" and "I" in your text box (in my case, I was trying to type the word "first"), it will crash Premiere Pro. I was adding a subtitle to a video in the middle of a sentence, which stopped my progress for a solid hour! I couldn't figure out what was happening. I tried typing all different types of sentences and using profanity to see if I had triggered some hidden language blocker, but nope!   I can't find a workaround, so I'll have to create an image file for just one line of subtitles. Hoping this is an easy fix on Adobe's end.   Let me know if this is a me-only issue! Thanks in advance for the help.   Mod note: The title was changed from The Most Infuriating Text Box Crash of All Time to a title that describes the issue.

In File 1 only the first track of audio plays.In File 2 (an ProRes export from PP), all audio tracks play correctly.There are likely some .mov container flags missing from File 1 that are preventing PP from parsing the audio tracks correctly. Could an Adobe Audio Engineer, take a look at the files and let me know which flags are missing so they can be included. Version: Premiere Pro 23.1, Windows 10 Version 10.0.19044 Build 19044 (issue persists in every version FILE1: OBS Mac Hardware Encoded ProRes File (only 1st audio track plays)------NOTE1: if all audio tracks initially play, click away from Premiere Pro to lose it's Windows focus and leave PP for 30s and only the first audio track will play.------NOTE2: File recorded using OBS on Mac using Apples Hardware ProRes recorder. ------NOTE3: PP testing done on Windows and Machttps://www.dropbox.com/s/xke6wis4l7r2ht5/OBS%20Mac%20Hardware%20ProRes%20with%20Missing%20Flags%20%... FILE 2: PP 23.1

On Premiere Pro 24.2.1, my project folders naming with "0" at the start, the "0" is always deleted after relaunch.  As I use only digits of date to name my folders, say Feb 27th is "0227", Jan 15th is "0115" the folder name after relaunch becomes "227", "115". It happens everytime I relaunch the project. I also tested with different digits and naming, only when folders with "0" at the start and using only digits in the naming, the "0" will be deleted. If I use digits out of "0" at the start, or add other characters instead of only digits. For example, "20240119" for Jan 19th 2024, or "0225A" for Feb 25th Version A, or even with a hiphen "0221-2" for Feb 21st Version 2. These combinations won't affect any names after a relaunch, the screenshot is the examples.  My current solution is to add a underline at the end of the folder name to avoid being deleted. And it never happened on 24.1 or previous version. Hoping for a fix.  Spec: Premiere Pro 24.2.1, M

Currently, the online documentation includes this dialog at the bottom of web page entries: The "not really" button leads to this dialog:   This dialog is inadequate for addressing problems in documentation: 1. Entries are limited to 235 characters. 2. No images can be included. 3. No additional dialog with Adobe employees or other users is possible to clarify the issue. 4. If the problem is that no documentation exists for a feature, then its not possible to leave a comment on a page that doesn't exist.   A better means of documenting, discussing, and resolving documentation issues is necessary.   Current means of addressing documentation issues are completely inadequate. This is demonstrably true. Recent example (stretching back to reports in February 2023).   R.  

Tech Specs: AMD Ryzen 3800x | 64GB (4x16 - DDR 3200) RAM | RTX 2060 Super | Windows 11 | Premiere Pro 23.2.0 Premiere installed on NVME Media Cache stored on different internal NVME Production/Project Files/Scratch Disks/Media stored on QNAP TVS-h1688X (8x16tb Seagate Iron Wolf Pro) | Configured in RAID 6 | Blackmagic Speed Test puts read/write speeds on average around 800 MB/s | Connects via 10gbe card on PC | All media is 4K Pro Res 422 HQ   I am working on editing a documentary with a director in another state and we are using productions to edit it (using the decentralized method as laid out in the PDF Adobe released recently).   The thing is that Premiere is lagging with everything but playback. When I playback the media it doesn't freeze or playback choppy at all. Playback is the only thing that is actually working without any problem right now. When I want to do anything outside of playback it lags terribly. If I want to right-click on something in the project folder i

Issue - Dragging-and-dropping multi-cams into a timeline behaves inconsistently depending on if its a single multi-cam clip or if you drag several at once.Adobe Premiere Pro version number: 24.2.1 (build 2)Operating system - Windows 11 Pro 10.0.22631 Build 22631System Info: CPU, GPU, RAM, HD:CPU - AMD Ryzen 7 5800XGPU - NVIDIA GeForce RTX 3060 Ti (Driver version: 31.0.15.5123)RAM - 64 GBHard Drive - 1TB SSDVideo format: Quicktimes from Canon 5D, 6D, & 7DWorkflow details: Dragging a Multicam sequence into a standard timeline that already has other media in it.Steps to reproduce - (Very important!) See attached video. But basically:Set toggle on timeline to Insert or overwrite sequences as individual clips.Drag a single multi-cam into the timeline.Drag several multi-cams into the timeline.Expected result - I would expect both instances to create a checkerboard of individual video and audio clips.Actual result -  If you drag in a single multi-ca

For years I've had this issue. I create a custom workspace layout that's suitible for my workflow, and EVERYTIME I open premiere, not only are my windows in a broken state, if I hit "reset to saved layout", it does nothing because it was overwritten. In the past 2 weeks alone I've had to fix it a whooping 14 times. Once for each day. It doesn't matter if I open premiere normally, open a project file directly, or even one of those options again later that same day. This happens with every CC version of premiere that I've used (never had this with cs6), and even moreso with each new update. This is what it should be And this is what I open the app to each time It takes only a few seconds to fix it and resave my layout, but that's still a lot of of time wasted when you add up this happens evertime the app is opened. Is there a fix for this?

We use a dated folder name for many of our assets, ie 031224 would be today. If I create this folder in a PP project, or drag a folder like this into the project, PP displays the name without the leading zero - 31224. Previous versions did not do this. V 24.2.1 build 2MacStudio running 14.2.1 (23C71)

That bug has been there for years now, on Mac and PC, and it's driving me crazy : everytime I create a new project, the project panel loses its position and goes on the upper left... AND the workspace metadata display profile goes back to default. If only the "reset workspace" function worked but nooooo, I have to manually move the project panel, go back to the metadata display to chose my custom profile, and save the workspace again... until the next time I create a project.   I teach editing with Premiere Pro. It's a big part of my job, I've had more than 300 students over the last three years. And every freaking time I have to explain that saving a workspace is not enough, it will be destroyed next time we create a project. And in my class we need to create a new project every day.   I'm sorry but it's not a temporary bug. Many of my students ask me if Resolve is a faster, better performing and more reliable software and I hate to admit it but it's true in many ways. Don't

Since updating to Premiere v 23.1, I'm experiencing serious delays when performing standard actions on the timeline (scrubbing, trimming, playback, etc). Restarting the application seems to provide temporary relief, but performance quickly gets sluggish the longer I edit.   The lag occurs regardless of: whether the playback resolution is 1/4 or high whether High Quality Playback is checked whether I've rendered clips on the timeline the type of media (compressed video, proxies, just audio)   I've also tried: updating macOS setting my audio input to none clearing the media cache resetting the workspace   I use Productions and am working on the same projects (now upgraded to the new version) that had no performance problems before the last update. If anyone can help me troubleshoot or provide insight, I'd really appreciate it. Thanks, y'all.   System specs macOS Monterey Version 12.6.2 Mac Pro (Late 2013) Processor 3.7 GHz Quad-Core Intel Xeon E5 Memory 64 GB 186

I run the most recent version of Premiere Pro on Mac and I noticed the feedback menu entry in the help menu doesn't link to community.adobe.com but instead still takes me to the now defunct user voice link. This only happens in Premiere Pro, I tested AE and AME, both have updated community links in their help menu, it's just Premiere.

Hi,I am having a consistent bug in which optical flow on clips renders improperly on my M1 Max Macbook Pro. This occurs on both .mp4 and ProRes clips during timeline renders and exports. This bug appears to have been around for some time. Unless fixed, I cannot use my M1 machine on commercial projects. M1 Max, 64GB memory Version 22.0.0 (Build 169) Thanks!