Bug Reports

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

My configuration is as follows:System: Windows 11 Professional 64-bit, Version 26100.4652 (24H2)Processor: Intel Core Ultra 7 265K, 20 cores (8P+12E), 20 threads (8P+12E), TSMC N3 processGraphics: NVIDIA GeForce RTX 5080, Intel Graphics, Intel NPUMotherboard: MPG Z890 EDGE TI WIFI (MS-7E19), Micro-Star International Co., Ltd., Intel Z890 chipsetGraphics card driver: Geforce Game Ready 576.80Hard Drive:aigo NVMe SSD P7000Z 2TB (actual capacity 1.86TB, SSD type)Predator SSD GM9000 2TB (actual capacity 1.86TB, SSD type)KINGSTON SNV3S 2000G 2TB (actual capacity 1.82TB, SSD type)Monitor: P2710V MAX, Resolution 3840*2160, Refresh Rate 160Hz, Screen Size 27.2 inchesMemory:Acer DDR5-8400 (4200 MHz) 24GBAcer DDR5-8400 (4200 MHz) 24GBTotal Capacity: 48GB, 4 channels, 8398 MHz, Timing: 40-52-52-1262TSoftware: Adobe Premiere Pro 2025, Adobe After Effects 2025Issues encountered:After exporting the video, there are encoding errors, and some frames display green stripes. For example, in a 5-minute vi

Hello I've experienced the following issue a lot which is the cause f A part of my project has  colour flickering in playback monitor. This issue has occured repeatedly over time. As I said, None of these issues occured when playing tne source file on VLC.My PC is pefectlty equipped to let everything run smoothly, I've cleaned my media cache, reset my workspace tp default, tried it after creating a new project, my graphics card is up-to-date but to no avail. I've seen that over the various installments on forums this issue kept being present. I honestly can't comprehend that after so much time and an apparently widespread occurence it's still not fixed through a patch/update. especially as Premiere Pro presents itself as leading software in it"s domain  I'd like tp think that part of that includes reliability and stability.   Your team developed the software, so I'd like to think that at somr point, you can provide a definite solution Y

I'm on the latest version of premiere pro on mac (25.2.3), all is up-to-date and I'm not using things like iCloud drive for my documents folder. Everything is local. I've had this problem for other versions of premiere pro as well.   I'm having a bug with premiere pro where I try to make a preset of the settings on the source. All works well when I keep premiere pro open. But when i restart premiere the (test) preset is gone. It is a preset that can only be applied to the source of the video file, but it all works when i drag and drop it on top of a clip.   I've already tried and delete the 'Effect Presets and Custom Items.prfpset' located in my documents folder. When I try to open the file with a text editor and i search for 'RED' i can see the preset in there. I then proceed to reboot premiere pro and i see the custom preset for a couple of seconds. After that everything disappears and basically resets to the default.I'm not sure what to do since I've already tried quite a

I create multicam sequences, and then cut those into the main timeline.If I update the Gain on audio tracks within the multicam, the waveform adjusts as expected.However, the waveform does not update in the main timeline. It used to do this, and now does not.The audio meters correctly report the audio volume. For instance:1. Add 6dB of gain to clips within multicam sequence. The waveform updates to show increased gain as expected.2. Go over to main sequence and cut in this multicam sequence. The waveform shows the audio volume as it was before the gain was adjusted. Even if I completely zero out the gain in the multicam to -96dB, the waveforms in the main sequence stay as-is. Again, the audio meters are correct and do not show any audio volume. I've noticed this (I believe) Premiere 25. Earlier versions of Premiere did not have this issue.Premiere 25.1, MacOS 15.3.2

 The marker name and/or comment is cut away when clip starts behind marker start.As you see in the screenshot above from Version 24 you always see the whole information of the marker.In Version 25.1 the information is incomplete.Additionally when zooming into the timeline you see even less of the infos. 

9:16の縦長動画のプロジェクトにおいて、プロパティパネルで設定したテキストの位置情報が、テキストスタイルに保存されない。• 既存のテキストスタイルを修正し、「スタイルの再定義」を行っても、位置情報が更新されない。• このため、複数のテキストクリップの位置を一括で変更することができず、手動で1つずつ調整する必要がある。 再現手順:①9:16の縦長シーケンスで新しいプロジェクトを作成する。②タイムライン上に新しいテキストクリップを作成する。③プロパティパネル（エッセンシャルグラフィックスパネル）で、テキストのフォント、サイズ、色、および「整列と変形」セクション内の位置を調整する。④調整が完了したテキストクリップを選択した状態で、「スタイルを作成」し、名前を付けて保存する。⑤次に、別のテキストクリップを選択し、作成したスタイルを適用する。⑥スタイルが適用されたにもかかわらず、位置情報が反映されない。⑦ さらに、元のクリップで位置情報を再度変更し、「スタイルの再定義」を試みるが、他のクリップの位置は更新されない。 作業環境:• Adobe Premiere Pro バージョン: 25.3.0• OS: macOS 15.6（24G84）

Dear Adobe Support,When using Adobe Premiere Pro 2025 with ATOK set as the default Japanese IME on Windows 11 24H2, the application consistently crashes when attempting to create a new project. This issue does not occur when Microsoft IME is used instead. The faulting module is textinputframework.dll (part of Windows' Text Services Framework).Environment:- OS: Windows 11 Pro 24H2 (Build 26100.4770)- Faulting DLL: textinputframework.dll 10.0.26100.4768- Application: Adobe Premiere Pro 2025 v25.3.0 (Build 84)- CPU: Intel Core i9-12900K- IME: ATOK (issue occurs) / Microsoft IME (no issue)- Reproducibility: High (almost every attempt)Steps to Reproduce:1. Set ATOK as the default Japanese input method.2. Launch Adobe Premiere Pro 2025.3. Select "New Project".4. Premiere Pro crashes immediately.Error log excerpt (Event Viewer):Faulting module name: textinputframework.dllVersion: 10.0.26100.4768Exception code: 0x00000675Fault offset: 0x00000000000107baWorkaround:Switch the IME to Microsoft IM

Detailed steps, specs, and screen recording of issue are here: https://community.adobe.com/t5/premiere-pro-discussions/why-is-my-clip-going-into-the-timeline-fully-transparent/m-p/15457996#M568685 (I originally posted this as a "discussion" since I didn't know what the problem was. Now I'm reposting as a bug report since I think it's a bug.) Short version: In Windows 11, Pr 25.3, selecting a clip in the timeline and then alt+dragging another clip from the project panel onto it, to replace it, sometimes makes the replacement clip completely transparent in the program monitor. Please see link above for details.

For years about 60% of the time I duplicate a sequence auto save stops and I have to restart Premier to keep working.

Am I doing something wrong, or is this a bug? Thanks in advance! Windows 11Premiere Pro/After Effects/Media Player versions 25.3 All clips involved are Prores 30fps, in a 3840x2160 30fps timeline. *Note: yes, I'm aware that I'm bypassing the Render and Replace feature. I've had trouble with it being unreliable before and I just prefer now to do the same operation manually by importing the render and placing it in the timeline.* Screen recording of issue: https://vimeo.com/1109147208/fbc7fb6d9b 1. Duplicate timeline. (This is so I can use "Replace with After Effects Composition" in the first timeline, render the roto'd clip from Ae, and then place it in the duplicated timeline. At the end I'll have one timeline with Ae comps intact and another timeline with all the renders. Just for safekeeping.) 2. Right click clip (prores 422 LT) in first timeline, choose Replace with After Effects Composition, apply roto brush, render as Prores 4444 with alpha. No p

When I assign the "3" key to a zoom shortcut, it doesn't work. For example: fit, zoom to fit, zoom in, zoom out, in all iterations -- ie program monitor, source monitor, or system-wide in the case of "fit." In previous versions of Premiere (2021-2024), I have assigned 1 to zoom in on source/program monitors, 2 to zoom out, and 3 to zoom to fit. Yet in 2025, while other keys will perform the function when I assign them to that shortcut, the "3" key will not do anything.  My workflow uses this a lot, and I've had to modify it, but would love to be able to use that "3" key to zoom to fit again.  Steps:1. Premiere Pro-> Keyboard shortcuts2. Assign the "3" key to View->Magnification->Fit (or Zoom Program Monitor to Fit, or Zoom Source Monitor to Fit, or Program Monitor Panel-> Zoom in/out, or Source Monitor Panel-> Zoom Monitor In/out.3. Return to program or source monitor, use my assigned shortcuts to zoom in ("1") and out ("2"), which work. Expected resu

I am struggling to move captions from one track to another for different styling. I began being able to freely move one speakers captions onto their own track, then all of a sudden I was not able to move them, only for when I tried to drag an drop the caption, it would open a new track and place the caption on there. Then I found that some would be able to be moved around. I then restarted PP as this is usually a way to make it behave. Didn't work. I then restarted the machine. Didn't do anything. Checked I have the latest PP, didn't, updated and this hasn't fixed the issue.  Please see the attached video for reference.  

Issue:When using fullscreen playback (via Mercury Transmit) on a secondary monitor, Premiere Pro shows a white outline around any scaled-down or masked video/graphic layer. This white outline also appears on the Program Monitor during real-time playback. The white edges do not appear in the final export.System:Mac Studio M2 Ultra with dual Apple Studio Displays + mirrored client monitor (4K Samsung OLED TV)macOS Sonoma (latest OS, issue present across all OS updates in the last year+)Premiere Pro (latest version, issue present across all versions in the last year+)Renderer: Metal (cannot be changed)Steps to Reproduce:Create a sequence (any resolution)Add a video or graphicScale it or apply a mask (with or without feathering)Enable fullscreen playback on an external monitorObserve white edges appearing in real-time playback on the external monitor and on the Program MonitorNote the white edges do not appear in the final exported videoAdditional Details:Rendering the timeline removes the

Hello. I think this is a question for @mattchristensen We're making the jump from Premiere 2023 to Premiere 2025. A two minute, ProRes 4444XQ file takes 27 seconds to scene edit detect in 2023. It takes over five minutes to complete in Premiere 2025.These are Windows machines running Premiere 25.3.NVIDIA RTX A5000 GPU Cards.I noticed GPU usage is about 15% whene scene edit detecting on Premiere 2025, and only 3% on Premiere 2023.Help!