Bug Reports

ProblemMotion and Transform Position keyframes do not update correctly when editing Nikon Z6 III HEVC footage.Steps to reproduce1. Open Adobe Premiere Pro 26.2.2 (Build 3).2. Import a Nikon Z6 III clip recorded as HEVC (H.265), 10-bit, 4:2:0, 3840 × 2160, 100 fps, Rec.709, Full Range.3. Create a new sequence and place the clip on the timeline.4. Select the clip and open Effect Controls.5. Enable Position keyframes under Motion.6. Create several Position keyframes and change the Position values at different points.7. Move the playhead back to previous keyframes.Expected resultEach Position keyframe should preserve its own value and the image should update correctly at every keyframe.Actual resultAfter creating several Position keyframes, the image becomes stuck on a previous position or displays a different position from the selected keyframe.Changing the numerical Position values no longer updates the image correctly.The same issue also occurs when using the Transform effect instead of

I have imported a picture and turned on scale to frame size. When I try to scale the image up slightly it only scales on the Y axis not x. When I turn off uniform scaling it does the same thing until a certain point and it snaps into place. On Mac newest version of premiere. Freshly installed day before.Youtube link with footage of bugImage is jpeg, size 3024x4032(1.0)I was unable to reproduce the bug with different images, but reimporting the image into the project the same bug was affecting it. -import image to timeline with a smaller sequence size-turn on scale to frame size-scale image

Hey all!   Weird thing going on here with the relink media window in premiere, it shows up as a small section in a larger window that doesn't allow scaling to the full window size. Was wondering if anyone had a similar issue, it's been this way for a while now! Would be nice if I could use the full size of the window to search media easier.   Using Premiere Pro 22.2  

I selected a few clips as ambient, and now I want to use the ducking feature in Premiere Pro. And I am talking against dialogue. As you can see, there is a huge pause between dialogue. Doubtful in this moment should be boost of audio, but it works only in the moment when sensitivity is high when I lower sensitivity it's works random. The moment when the audio should get quiet , there is no keyframes from ducking and it is creating key frames in random places.You can see clearly that in video I attached to this post.The ducking should work like it works in music tab. When there's no dialogue because I'm ducking against dialogue, you should work normal and when dialogue appears audio should get quieter.

O problema esta na hora da exportaçao onde o arquivo exportado está vindo sem a cor que foi editada no projeto. 

Pr 26.2.2, 10 images put into a nest, inside the nest all the images are duplicated multiple times. The task is to make a gradually speeding-up sequence of images.32 minutes of images, 5 seconds eachSo I switched on the time-remapping graph and made this curve and it turns out in this scenario Premiere shows only half of the images:Your normal reaction would be - ok, it sped up so much (it’s only a 500% speed curve) that the images just ended before the sequence ended, right? Well, first of all, when you pull up this speed up curve the sequence gets shorter accordingly. Second - I went inside the nest and tripled the amount of pictures there afterwards (the purple ones are the original quantity):… and guess what, nothing changed - the images just go black at this timestamp:Steps to reproduce:Create a sequence, put the needed amount of images in it Select all the images and nest them Open the Time-remapping curve, place the keyframe somewhere at the beginning of the nest and drag the cu

Bug : la transcription de modification basée sur le texte est générée en anglais alors que la transcription de la séquence est en françaisVersionAdobe Premiere Pro 26.3.0 Windows 11Description du problèmeBonjour,Je rencontre un problème reproductible avec la fonction Montage basé sur le texte.Mon interview est entièrement en français.J'ai correctement configuré la langue de transcription en Français (France).La transcription de la séquence est parfaitement reconnue et affichée en français.En revanche, lorsque je sélectionne « Générer une transcription de modification basée sur le texte », Premiere Pro génère une nouvelle transcription en anglais (ou parfois dans une autre langue) au lieu de réutiliser la transcription française existante.

First of all, Apologies I recently made a post about this before but i thought it was rushed and i feel i can explain this issue at a lot more detail. As there is multiple issues i shall split this post into several sections (Please Check Last Section For Technical Specifications And Other Notes On My Tests)   Premiere Pro 2024 has Some Severe UI Issues. (Beta Included)READ THIS :THIS IS A MASTER THREAD FOR THIS ISSUE. WHERE I WILL BE POSTING EVERY SINGLE FINDING I POSSIBLY CAN. IF YOU SEE THIS POST AND ARE SUFFERING FROM THIS ISSUE PLEASE HIT UPVOTE. AND COMMENT YOUR PC SPECS AND SPECIFICS ON YOUR EXPERIENCES. EVEN IF YOU HAVE NOTHING TO ADD JUST A COMMENT SAYING THAT YOU ARE EXPERIENCING THIS BUG IS ENOUGH TO PUSH MORE TOWARDS A FIX. IF YOU FIND ANYONE EXPERIENCING THIS BUG ALSO IN ANOTHER FORM PLEASE REDIRECT THEM HERE SO THEY CAN COMMENT AND WE CAN HAVE ONE SPACE FOR THIS ISSUE AND EVERYONE EXPEIRIENCING IT. REGULAR UPDATES ON MY FINDINGS ON THIS

I'm working on a documentary. Our team is using Productions with the Production files and all media stored on a local NAS (Avid NEXIS). We are in Premiere 25.2.1. I am cacheing to the default folder (Users/[user name]/Library/Application Support/Adobe/Common) on a 2023 M2 Ultra Mac Studio with 192 GB of RAM and 1 TB of internal storage. My media cache is set to "not delete files automatically." And, under audio settings, I have "Generate audio waveforms automatically during import," de-selected.  Everyday when I open any project in the production, I notice my visible waveforms, created the day prior, are gone. When I look into my cache folder at the corresponding .PEK file, I can see it there, in the dated folder from the day prior, along with all the other .PEK files—all mixed media sources—that are also not showing visible waveforms in Premiere where they were yesterday. If I select these clips and "Generate Audio Waveforms," new .PEK files will be creatd in a new folder in

Hi all, looking for help and information on an issue I am having.To preface this, Apple has agreed to buy back my M4 Pro and M4 Max MacBooks, but they have asked me to reach out to Adobe to get more information on this for better understanding of the issue.I'm experiencing playback issues (very choppy and stutter, skipped frames) on Quicktime (Native Metal) on the M4 chips, but this issue is not replicated at all on the M5 chips we used to test. We used the same exported file to test (Apple support verified the checksums).Apple has benchmarked the M4 MacBooks and found no technical faults, they have ruled out performance issues on their end. They believe it is a software issue with Adobe and M4 chips, as it works fine on M5.We use Premiere Pro and Media Encoder for work frequently and have never encountered this issue, only first noticed it a week ago.Does anyone know who we can talk to get documentation/logs, a sort of paper trail running to talk to Adobe Technical Support, that we ca

 Bug descriptionIn the latest version of Adobe Media Encoder 2026 on Windows 11, newly added export jobs appear in the queue in reverse order. For example, when I add a second job, it is placed above the first job instead of below it.The actual encoding order is also inconsistent. Sometimes Media Encoder processes the queue from the bottom upward.Manually dragging jobs into a different order does not reliably fix the problem. Media Encoder may still process them according to the order in which they were originally added rather than their visible position in the queue.Steps to reproduceOpen Adobe Media Encoder 2026. Add one export job to the queue. Add a second export job. Notice that the newer job may appear above the previous job. Add several more jobs and manually rearrange them. Start the queue. Observe that the jobs may encode from top to bottom, bottom to top, or according to their original insertion order rather than the visible queue order.Expected resultJobs should be added to

These BWF WAV files were created and exported from Pro Tools with the followingexact source timecodes:• 2997DF_1h00m.wav → 01:00:00;00• 2997DF_1h10m.wav → 01:10:00;00• 2997DF_1h20m.wav → 01:20:00;00• 2997DF_1h30m.wav → 01:30:00;00However, after importing them into Premiere Pro and setting the Time DisplayFormat to 29.97 fps Drop-Frame Timecode, Premiere displays:• 2997DF_1h00m.wav → 00:59:59;29• 2997DF_1h10m.wav → 01:09:59;29• 2997DF_1h20m.wav → 01:20:00;00• 2997DF_1h30m.wav → 01:30:00;00Requested behavior:Please preserve and display the original source timecodes assigned when theBWF WAV files were created:• 2997DF_1h00m.wav → 01:00:00;00• 2997DF_1h10m.wav → 01:10:00;00• 2997DF_1h20m.wav → 01:20:00;00• 2997DF_1h30m.wav → 01:30:00;00The attached ZIP contains the original 1 kHz BWF WAV test files exported fromPro Tools. A screenshot showing the Media Start values in Premiere Pro is alsoattached.Premiere Pro: 25.6.5 (Build 4)Operating system: macOS Tahoe 26.5.2Hardware: MacBook Pro 16-inc

So i bought a new laptop like 3 weeks ago and i downloaded and started using Adobe softwares like photoshop and premiere last week. But now premiere is really bugging and tweaking out. While i was editing a 58 minute video 3 days ago premiere suddenly crashed and made my entire screen including my 2nd monitor black. And after resetting my laptop and stuff, i tried opening premiere again, still crashed everything. So i decided to ask chatgpt for help (idk if thats good, i was desperate and was really shy of using reddit). And with Chatgpt we did multiple things too see if it can help. I tried erasing cache, switching my driver to Nvidia studios, change the path to a separate folder, etc.While doing those attempts (still failed), i went to see what actually crashed, apparently it was a "LiveKernelEvent 141". After doing similar stuff, I found out that my Adobe and its software was in Onedrive, and i thought that was the issue, and after making a backup of my proj i deleted adobe and its

Je suis un utilisateur de la suite Premiere depuis des années Et je n'ai jamais pris le temps de faire un poste ou de remonter un problème. Mais là il faut que ça cesse.C'est quasiment devenu impossible de travailler sur la suite. J'ai un légion avec 32 gigas de RAM et faire des montages de 2 caméras avec des osmo Pocket 3 (pas des caméras de fou) est juste invivable. Vous ne pouvez même pas savoir à quel point c'est une déception quand on paye un logiciel aussi cher tous les mois de ne même pas pouvoir faire quelque chose d'aussi simple que de faire un montage que je pourrais faire sur mon téléphone sans que ça bug.Je vais dans les prochains mois faire l'effort de migrer l'intégralité de mes process sur un autre logiciel de type Da Vinci Resolve car c'est juste insupportable de perdre autant de temps en tant que professionnel quand on paye un logiciel professionnel. Le logiciel freeze toutes les 2 minutes, quand on commence à lui donner des ressources (RAM en plus ou qu’on mets les fi

System:Premiere Pro 26.3.0macOS Tahoe 26.5.2Mac mini M4 Pro (48 GB) HEVC footage from an iPhone 15 Pro Max glitches in the Program Monitor when Scale is above 100% and playback resolution is set to 1/2, 1/4, or 1/8. Full resolution works correctly. Exported videos are normal. Screen recording attached.

I tried using premiere 2026 and it won’t open without closing or crashing. I’m not even trying to open a specific project but it closes on the home page. I’ve updated my graphics driver and even tried re-installing the app but neither of those worked. Any suggestions?Running on a windows with a Intel Core Ultra 9 and GeForce RTX 5080 and a z890 Aorus Pro Ice Motherboard. I’ve included a video in case it provides clarity.

My transcript tool is not working, I updated premiere like 2 weeks ago and this just happened today. Needless to say, this is not what the audio is saying, it’s the reading of a script. I tried both the Text Based Editing Transcript and the Static Transcript, none of them works 

Bug: Premiere Pro 26.3 playback issue with DJI HEVC D-Log M.Mac: MacBook Pro 14" M5 Pro, 24 GB RAM.OS: macOS Tahoe 26.4.Camera: DJI Mini 5 Pro.Media: 4K 60fps HEVC (H.265) D-Log M.Problem: Files play perfectly in QuickTime, but in Premiere Pro 26.3 the playhead moves while the image updates only every few seconds. Playback is extremely choppy.Test performed: The exact same files play perfectly in Premiere Pro 25.6.6 on the same Mac.

Hello Adobe Support,I am experiencing a persistent and severe crashing issue with Adobe Premiere Pro on my MacBook Pro M4 Pro with 24 GB RAM and macOS 26.5.2.Premiere Pro repeatedly crashes shortly after opening or working inside a project. The issue has occurred across multiple projects, different clients, and footage from different cameras and sources. At different points, Premiere has also crashed with brand-new projects and with little or no active editing.I have already completed extensive troubleshooting:- Cleared the Media Cache.- Reset/trash Premiere preferences on startup.- Launched Premiere with third-party plugins disabled.- Disabled hardware-accelerated decoding.- Tested different import methods, including File > Import instead of Media Browser.- Closed the Media Browser panel.- Tested multiple projects.- Tested footage from different cameras, clients, and sources.- Created completely new Premiere projects.- Completely uninstalled and reinstalled Premiere Pro.- Tested Pr

Premiere Pro v26.2.2 no me transcribe nada, literalmente nada. Se queda cargando para luego quedarse ahí quieto. Mi única solución después de perder horas fue volver a reeditar todo en la versión 2024 ya que ahí la transcripción me funciona PERFECTO. Enserio, tengo todo descargado en la v26.2.2, el paquete de idioma, el enhance speech, pero aun así nada de nada. Y no es un tema de archivo ni nada de eso ya que, como menciono, la versión del 2024 me funciona mucho mejor.

I can no longer drag layers, change numerical values, or trim a layer.It's becoming impossible to edit.It freezes up constantly, and the audio also cuts in and out. It might randomly start working again, but only for 1 click, then it won’t allow you to move or change anything. Version: Premiere Pro version: 26.3Chip: MacBook M5 MaxmacOS: Tahoe Version 26.4Memory: 128GB Becoming more and more concerned with Adobe. This has been reported several times with 0 help.Many others are experiencing the same thing.    

after opening premiere create a sequence and upload a media then premiere crashes, does it every-time 

Hi,I'm experiencing a strange issue in Premiere Pro.In my timeline, I intentionally left a gap of about 3 seconds between two clips to create a hard cut to black before the video continues.Inside Premiere, everything works as expected. During playback, the screen goes black for the duration of the gap and then the next clip starts normally.However, after exporting the video, the last frame of the previous clip stays frozen during the entire gap instead of showing black. Once the gap is over, the next clip plays normally.I've already tried several things: Leaving the gap empty. Replacing the gap with a black video layer. Adding a fade transition. Deleting and recreating the cuts. Clearing render files and exporting again. The issue only appears in the exported file, not inside Premiere.Has anyone encountered this bug before or found a solution?Thanks!

After updating to Adobe Premiere Pro 26.3 on Windows 11, several projects that had previously opened without any issues began displaying an “outdated or damaged” error and would not open properly.At the same time, my Logitech MX Creative Console also stopped functioning correctly with Premiere Pro.I initially thought the issue might be related to Windows, so I completed an in-place reinstall of Windows 11 and reinstalled the affected applications. However, the Premiere project errors and MX Creative Console issue continued.I then reverted to Premiere Pro 26.2 through the Creative Cloud application. Immediately after installing version 26.2:• All of my Premiere projects opened normally.• The “outdated or damaged” project errors disappeared.• My Logitech MX Creative Console began working correctly again.Since both issues occur in Premiere Pro 26.3 and are resolved by reverting to 26.2, this appears to be a bug or compatibility issue introduced in version 26.3.System: Windows 11Problem ve

Premiere Pro version: v26.3OS: Windows 11Summary:The Limiter within the Dynamics effect (and the standalone Hard Limiter) does not correctly enforce the threshold I set. When I set the limiter threshold to -6 dB, the output does not limit to -6 dB as expected — the metered level shows around -10 to -15 dB instead, and the limiter appears to either over-attenuate the entire signal or not respond to the threshold value correctly.Steps to reproduce:Create a new project and import an audio/video clip with dialogue. Apply the Dynamics effect (or Hard Limiter) to the clip. Enable the Limiter section and set the threshold to -6 dB. Play back the timeline and observe the audio meters.Expected result:Audio peaks should be limited to the set threshold (-6 dB) and not exceed it, while the rest of the signal remains unaffected.Actual result:The output level does not correspond to the threshold. Peaks read significantly lower than expected (around -10 to -15 dB), as if the entire signal is being at