Bug Reports

"viewer gamma" settings dont act the same wether a clip color space is unchanged or not   Adobe Premiere Pro version number: 25.1.0 (build 73) Operating system : macOS sequoia 15.3.1 System Info: Apple M2 MacBook air 3,5 GHz apple GPU 10 16Go DDR5 RAM Hard Drive 1To Video format: any image media Workflow details: any project, any sequence Steps to reproduce - (Very important!) I'm french so excuse my english please. Place any image media clip with rec709 2.4 profile (video, png, jpg...) on a timeline (any settings) select the clipIn the lumetri color settings panel :Display color management is on working color space : rec709   Set the "source clip" section on "use media color space" (so rec709) "viewer gamma" on 2.4   export the clip as an h264 file (any settings) this is FILE 1Achange "viewer gamma" to 1.96then Image should look different inside Premiere's program monitorexport the clip as an h264 file (any settings) this is FILE 1BNow Set the "sou

Hi, my name is Haris Ahmed, and I’ve been working in video editing, animation, and graphic design for the past 2 years. Recently, after switching to Premiere Pro 2025, I started facing a major issue. Whenever I try to export a long project with hardware encoding, the export fails and gives an error every time. If I switch to software encoding, the export works, but it takes a lot of extra time, which slows down my workflow. I’m using a system with an 8GB dedicated GPU, so hardware encoding should normally work without a problem.As you can also see from the image I posted, my projects are usually long and heavy, so this issue is making the workflow very difficult. I’ve already tried multiple solutions and troubleshooting methods, but the problem is still there. Can anyone guide me on how to fix this, or let me know if this is a known issue in the 2025 version? Any help would be greatly appreciated.

I have Premiere Pro on 3 computes, 2 Macs and a Windows 10. Always keep software and OS up to date on all of them. For a couple of years now, I keep encountering an issue where the max output volume is always -3db until I add another "Volume" after it to bump it up to 0db, or use the audio track mixer to compensate. It's every effect, both stock and third-party. EQs, compressor, distortion, limiter, etc. Haven't been too annoying of a problem, until recently where I have to repeate the process of adding the "Volume" effect to compensate a lot in a short amount of time. I've tried making it a preset, but it doesn't add the 2nd "Volume" at the end of the effects chain, and adjusts my settings to the first "Volume" in the chain.I've looked periodically, and it seems like no one else has talked about this problem.I would prefer not to reset preferences and go directly to whatever's causing this, if possible.Any advice would be appricated.

This one keeps me buggin for quite a while now. Whenever you work with media that doesn't match the sequence framerate, the info panel will always show the sequence frame rate for selected media rather than the media's frame rate. This is incredibly annoying because you need to verify the media framerate by revealing it in the project panel every time. After doing so the info also switches to reflect the actual source media's framerate. But back to sequence framerate whenever that panel is active.   Media info as shown from Sequence (false info):   Media info as shown from Project (correct info):  

I am an editor on an animated series working remotely with one other editor using Lucidlink. All our assets and project files are stored on Lucidlink.I have been converting our edit projects to use Productions, so I can spread out our assets to various projects instead of having every asset in one bloated project per episode. It was working great until the Productions panel stopped responding to the changes I would make, like create a project/ folder, or rename a project/folder.The only way to get the Productions panel to refresh is to completely restart the Production which sometimes means closing my projects.  How do I fix this? Beyond this really disruptive and annoying bug, the system works perfectly. I saw another post from Marjorie Sacks that is supposedly the correct answer to this question but it only seems to apply to local servers (and to teams with resources like an IT department lol)https://community.adobe.com/t5/premiere-pro-discussions/production-panel

When dragging a timeline into a destination timeline, I see a preview of the clips in the timeline UI, but it never actually completes the operation and adds the clips to the timeline.  Scrubbing through the timeline, there is no video from the ghost clips.  Trying to click on or interact with them doesn't work.  Here's a screen recording of the issue:  https://youtu.be/7KVmIZiTfsQ Expected behavior:  the destination timeline should have the dragged content in it. Windows 11.  Premiere 25.3.0  (was happening on previous version, I think it was 25.2.0, but updated to see if that effected it but no change.)The screen capture is done with a Teams project.  Tried publishing.  Tried exporting as a local project and opening that and it had the same issue.  So it's not specific to teams or publishing.  Tried making a simple test case and if I make a new timeline with a handful of clips for testing,  I can not replicate

On Mac M1 machine (SEQUOIA 15.6) Steps to Reproduce:a. Updated Premiere pro version to: 25.4.0 (Build 99)b. Opened a Team projectc. Selected all media, right click and selected "Link Media" OR "Proxy-->Reconnect full resolution media"d. Selected a file and located it in a folder on SSD Expected result: All media should be automatically linked. Actual results: One few files got linked automatically, and a bunch didnt. No other option other than linking them manually.  Refer attached video for details

Hello Team!We have a 42, stereo track sequence in Premiere 2024. Audio clips all have Parametric EQ and volume keyframing applied on a clip level. We exported an AAF (embedded or otherwise) broken out to mono with effects rendered.The resulting AAF when brought into Pro Tools or even back into Premiere has all the volume keyframing in the wrong place. I've attached a screenshot. On the left is the AAF, broken out to mono and with 'include un-rendered clips' checked. On the right is the Premiere project.You can see the keyframes are completely off on the rendered clips in the AAF.We have tried every possible combination of AAF and the only thing that works is not to render the effects. When we do that, the volume keyframing is fine.Any idea why this is happening with this project?

I’m having a serious issue with Adobe Premiere Pro after upgrading my GPU.My setup:MSI B450 Pro motherboardRyzen 7 5800XT processor64GB DDR4 RAM1TB NVMe SSDPreviously using an RTX 2060 Super (everything worked fine)I recently upgraded to an RTX 5060 to stay up to date and improve my workflow. Unfortunately, it’s been the worst decision so far. Since switching GPUs, Premiere Pro has become almost unusable: I experience playback issues, dropped frames, export problems, and even playing a simple 4K iPhone video has turned into a nightmare.Things I have already tried (please don’t suggest these again):Complete reinstall of Adobe Premiere ProClearing cacheUpdating driversMaking sure Premiere Pro is set to use the GPU in the NVIDIA Control PanelSystem restart / power cycleAt this point, it feels like Premiere Pro and the RTX 5060 are simply incompatible.

Product: Premiere ProVersion: 25.4.0 (Build 99)OS: Windows 11 proBug Description:In Premiere Pro 25.4.0 Build 99, the playhead can no longer be moved by seconds.“Go to Time” command is missing from the Sequence menu and Help search.Typing a timecode in the Program Monitor (e.g. 15. to jump 15 seconds) resets the playhead to 0 instead of moving to the correct time.Keyboard shortcuts for Step Forward 1 Second and Step Backward 1 Second do not work as intended; they still move the playhead by frames, not seconds.“Display Format” options for the timeline (timecode vs frames) are no longer present in Sequence Settings.Expected Behavior:Ability to move the playhead by seconds using numeric entry or shortcuts.Proper recognition of timecode input (HH:MM:SS:FF).Restored access to “Go to Time” or equivalent functionality.Steps to Reproduce:Create a new sequence in 25.4.0 Build 99.Attempt to use “Go to Time” (command is missing).Click Program Monitor time display and type 15. → playhead rese

I’ve run several tests sending LTC timecode to my Zoom H5 audio recorder using Deity timecode generators (TC-1). I’ve tested a variety of setups: sending timecode to a single input while recording separate audio to another, and recording stereo files with LTC on the left channel and clean audio on the right.Regardless of the setup, when I import the WAV audio file into Premiere Pro, convert the LTC timecode, and sync it with other cameras that also used LTC, the WAV file is always 30 to 50 frames out of sync. I’ve followed all the proper steps—right-click, Modify > Timecode > Audio LTC—but the result is consistently inaccurate across multiple files and devices, including my Zoom H6.However, when I import the same files into Deity’s Timecode Toolkit to decode the LTC, then bring the decoded file into Premiere and sync by timecode, everything works perfectly. This clearly indicates that the issue lies within Premiere’s handling of LTC from WAV files.This seems to be a bug in Premie

I'm facing severe lag with playback and of course, dropped frames! This is not the first time this has happened, usually every 2-3 updates this problem occurs and I have deadlines just like many other people do! To give you a brief, my hardware:- 64GB RAM- RTX 4070- AMD Ryzen 9 processor- Windows 11 64bit- 4k Monitor- Changing audio hardware input to all options available- Working off a 5th generation 2TB SSD I'm using NRAW raw files transcribed using REDCINE X PRO since adobe still doesn't support Nikon raw files. they are 12 bit. I have already tried the following:1- Changing audio hardware to no input.2- Changing codecs (all of them)3- Playback quaity (all of them)4- deleted media cache files5- reinstalled studio driver (and rolled back to previous versions) NOTHING IS WORKING!! someone please help! 

A transcrição não corresponde ao video da timeline após eu ter duplicado a timeline e trocado o vídeo anterior na nova timeline, o video novo, ou trecho de vídeo, já tem transcrição criada mas não aparece no visor da transcrição então não consegui criar legendas novas, tá me deixando muito insatisfeito, só funciona e volta ao normal se fechar o programa ou criar a transcrianção estático e voltar pra de edição depois, o que é muito chato de ficar fazendo e nem sempre funciona!

my 4k video is not rendering properly.. and premier pro stopped automatically

Hi I have just updated to 25.2 and opened my current project. Playback is incredibly laggy, even with proxies and at 1/2 resolution, a MASSIVE difference from yesterday when I was working on this project in 25.1. I can't even play through a basic cross dissolve between two clips, or a keyframed opacity on a single clip. Won't play just jumps ahead once it has caught up. My Windows Task Manager shows Premiere using 30-60% of the GPU conducting "video decode" processes for the last 20-ish minutes since I opened the project, which I'm assuming has something to do with it. And like 65% of RAM. That's happening even while I the program is sitting in idle. Does this have something to do with the new content search and analyzing of clips? If so, is there a way to turn it off? This is just a guess. PP 25.2.0 Build 147Windows 10.0.19045 Build 19045 AMD Ryzen 9 5950xNVIDIA GEFORCE RTX 308064GB RAM

Je peux lancer mes projets mais les plans ne chargent plus, je ne peux pas non plus lire mes séquences ou les exporter. Je ne peux rien faire. Je suis sur Apple M4 pro version 15.6 avec la dernière version de premiere pro. 

Are there any one who facing issue while rendering in lastest version of premier pro, i was using 25.2 since 25.3 had Avchd audio peaking issue. I upgraded to 25.4 hoping they fixed the issue, along with I upgraded the encoder also then i started to face rendering issues, now i switch back to other version, its completely working - and the Playback Is very slow Even though I have powerfull desktop 

I am so sick of Adobe. I pay for the product and it continues to get worse and worse.   ISSUSE - EVERY FLIPPING TIME I TRY AND SWTICH THE WORKSPACE FROM "LEARNING" TO ANY OTHER WORK SPACE ADOBE PREMIERE CRASHES. I TRIED AN OLDER VERSION, TRIED RESTARTING, ETC .ETC. NOTHING FLIPPING WORKS!   I CANNOT WORK IF CAN'T SIMPLY SWITCH WORKSPACES!!!     [PLease do not write in capital letters: for some its difficult to read and its considered shouting which we do not do on this forum]    

Issue:When using Mercury Playback Engine GPU Acceleration (CUDA), applying blur effects such as Gaussian Blur or Directional Blur causes black clipping in dark areas, resulting in loss of shadow detail. This problem does not occur when using the Mercury Playback Engine Software Only mode.Steps to reproduce:Place a clip with shadows or grayscale gradients in the timelineApply a blur effect with GPU rendering enabledPreview or export shows clipped shadowsRequest:Improve GPU rendering precision so that tonal range matches software rendering resultsReintroduce the "Mercury Playback Engine Software Only" option removed in v25.2+, to allow users to bypass GPU rendering when necessary for quality reasons.

I've been using 2025.4 for the past 24 hours on a large LucidLink-hosted project, and am delighted to say that just about all the issues I had been having in previous versions of 2025.x seem fixed, and performance is much, much better all around. However, I've noticed one problem that was common a few releases ago seems to have resurfaced - renders for rendered MOGRTs seem to 'disappear' after some time. Details.1. MOGRT lives on LudicLink, added to Local Templates in Graphics Templates window.2. MOGRT added to approx 35min timeline (23.976fps, HD)3. MOGRTs rendered throughout show, all show as green4. Project saved5. Green renders begin slowly turning red backwards, i.e. from the end of the timeline towards the front of the timeline, over a period of maybe an hour or less.   It doesn't matter if I'm working away in Premiere, or leave it untouched in the background, they continue to disappear.6. Eventually, all MOGRTs in timeline show as unrendered red.   This also

macOS VenturaDesktop Video Setup 14/15Adobe Premiere Pro 2023/2024/2025 Mercury Transmit, via the Desktop Video SDK, does not automatically change the following setting in Blackmagic's Desktop Video Setup to properly match the timeline: SDI Output > 1080p HD and 2K > Are output as 1080p Progressive or Are output as 1080p Segmented Premiere does change the other settings, such as Resolution/Framerate, but the Progressive vs Segmented setting needs to be manually changed. I've confirmed that Resolve does change this setting as needed, so the SDK should have this functionality available.

I will tell Premiere to search in a specific location on a specific disk, but the search WILL NOT respect that, and will search literally every folder of every disk on my computer.  This has been a problem for a while on my Windows 10 workstation and my mac for several versions now. It shouldn't be this much effort to make PP search where I want it to search. 

So I started editing and bessically everytime I wanna play my footage it takes around 10 seconds to start and randomly while playing the preview window freezes and if I want to change text it also randomly freezes the preview monitor. I have a week old macbook- Macbook air m4 24gb ram- Premiere pro 25.3.0 (a week old first project I have ont this premiere pro installation- Cache is cleared- using 1/4 quality

I recently moved to an M3 Ultra Mac Studio - 96g ram When I have Premiere Running with a project open, my network connection, LAN, Internet, NAS, is throttled down to a trickle.  I went through multiple troubleshooting things and searches, thinking my NAS was an issue.  The fix i found was to disable 'Media analysis & transcription' in the preferences.  PP ver 25.3.0

Warp Stabilizer takes an unusually long amount of time to analyze a clip with Lumetri applied. In the same project, I had applied warp stabilizer to the clip in question earlier without issue. After applying Lumetri to the same clip, warp stabilizer then took much longer (over an hour vs roughly 10 min) to analyze the very same 2 minute and 40 second clip. Upon removing Lumetri, warp stablizer went back to taking about 10 minutes to analyze. It doesn't seem to be affecting anything, but in case it is relevant, in addition to Lumetri, I had applied an opacity mask to mask out the subjects in an attempt to get better stablization, and nested the clip before applying warp stabilizer. By removing Lumetri and changing nothing else, it functioned normally again. Some system/software info:i9-12900K32GB RAMRTX 3080Windows 11 HomePremiere Pro v25.3 Sequence settings:1920x108023.976fps48kHz Clip was taken from source footage with these attributes:Type: MPEG MovieFile Siz