Bug Reports

When importing gopro mission 1 video files that are using the new wmedia mod, if the file has been broken into multiple pieces by the camera (long), the first file shows as video in premiere, but subsequent files show as audio files.  When placing on the timeline they only show as audio.  The files when opened from the windows desktop are in fact video files with 2 audio tracks.  The files marked in yellow in the screenshot should show as video files like all the others.   

created a text layer over video text is 2 short lines added Effects > Text > Typewriter to text layer works fine On the text layer: Effects control > text > drop shadow checkbox activated the typewriter effect now comes out in chunks.Apparently the same thing happens when i add a Backgroundto my text

I get these errors when I import drone content into Premiere 26.5.2. The video files are playable in windows explorer and MacOs. However they fail to import into Premiere. If I do ever manage to get them to import the videos show the first frame but are unplayable even with a high spec machine. They will not even move one frame. Again like the issue I had with the GoPro files that showed only as audio I had to roundtrip my DJI videos through windows clipchamp to make them viewable by premiere. This causes a degradation in quality. Again if I re-export with encoder it doesnt seem to resolve the issue.  

I just newly installed premiere pro on my macbook air m5 and it is not supporting any type of audio clip in the timeline, shows error when importing them into project, some get blank audio and some can't even be added into the timeline. I have already tried solutions like Audio Hardware changing, Clearing cache, Creating a new blank file, Using different audio files, installing a year old version of Premiere, but nothing seems to be helping me, plss guyzzzz help me! 1 of 2 things happens with the file:it imports with error, can add into timeline, has no audio.It imports without erro, has no audio and can’t be added into the timeline.pls anyone, solution? Blank AudioError 

Hi, I'm running Premiere and Media Encoder Version 24.3.0 on Windows 11. I'm having a strange issue where if a Sequence in Premiere has been renamed at any point (for example 'Amazing_Edit_V001' to 'Amazing_Edit_V002', whenever I go to export that sequence using Media Encoder, it sets the default Output Filename to the previous sequence name,  'Amazing_Edit_V001'. Regardless of whether or not I shut down all the programs or even restart my computer after renaming the sequence. It was always inherit the original sequence name. This will also happen if then rename the sequence again to 'Amazing_Edit_V003', it will still maintain the original 'V001' filename when sent to Media Encoder. I should specify that this only applies to the 'Output File' filename. It correctly recognises the the sequence name as the source name on the left.

Hello, I have the current Version of premiere pro.The object mask tool is very helpful.Unfortunately it is working really slow. When opening a project the timeline has red zones.When using the preview it stops to play or it is not possible to play it after edition at a random time.The mouse is still moving but I am not able to use the program. I have to restart then it is working again.Anybody with same issue or is it a known bug?

I've submitted this bug several times now.  2 things: how do we know if adobe has acknowledged a bug? do they respond to let you know? 2nd thing, the bug itself:   take a nested sequence, insert it onto timeline.  Add another layer in the nested sequence, apply time remmapping.  Sequence will go black before it reaches the end of the sequence. This vid below demonstrates that it is not the normal behavior of a time remmapped clip.  Most of the time when I encounter this bug it is when the original footage is not the same res as the final sequnce.   [hyper link removed by author request]   [Typo removed from title. — Mod.]

TEST IN PROJECTSIn the video linked I try to show when this bug happens and when not it seems to me that is something to do with the masks folders there created or with the new rotoscopie system. I’ve tested previously the ruler and box out preview but it dind’t solve either. Premiere is updated 26.0.1. @Ann Bens ​@Ron Rigler ​@Dani_V. Processador    Intel(R) Core(TM) i7-9700KF CPU @ 3.60GHz   3.60 GHzRAM instalada    16,0 GBArmazenamento    447 GB SSD SSD 480GB, 1.82 TB SSD WD Green 2.5 2TB, 932 GB SSD KINGSTON SNV2S1000GPlaca de vídeo    NVIDIA GeForce GTX 1660 (6 GB)ID do dispositivo    78351133-11F7-4BE0-905C-26A65D630A79ID do Produto    00330-80000-00000-AA527Tipo de sistema    Sistema operacional de 64 bits, processador baseado em x64Edição    Windows 10 ProVersão    22H2Instalado em    ‎27/‎04/‎2021Build SO    19045.6466

Issue: The Premiere version 26.3 is causing issues with scale and position when exporting and rendering videos, but everything looks fine when I'm in the project and timeline, so the only way I can check for errors is to export a whole video. This only happens with some file types such as images animated using Film Impact Dashboard or vertical images that I have scaled to fit the landscape frame. I have since rolled back to 26.2.2 and everything works fine. So I'll wait to see if the next version also has these issues.Steps to Reproduce: I have a feeling it is a compatibility issue with my PC.Below are the details of my system:Processor    AMD Ryzen 7 9700X 8-Core Processor (3.80 GHz)Installed RAM    32.0 GB (31.6 GB usable)Graphics card    AMD Radeon RX 7900 XT (20 GB)System type    64-bit operating system, x64-based processorI have a timeline for an 8 minute YouTube video and export in YouTube 4k. Then I watch the exported video back to see if the error has occurred.I did try renderi

I am experiencing severe freezing issues with Adobe Premiere Pro 26.5.2 on my MacBook Pro with an M4 Pro chip and 24 GB of RAM, running macOS Golden Gate 27.01. The application frequently freezes and becomes almost completely unresponsive.Today, I downgraded to macOS Tahoe 26.7.1 and tested Adobe Premiere Pro 26.5.2 again, but the problem remains unchanged. Even when I simply move text around in a video project, make cuts, and press Play to preview the footage, Premiere Pro freezes.This issue is seriously affecting my workflow and making video editing extremely difficult. I would appreciate it if your team could investigate this issue and provide a fix as soon as possible.Thank you for your attention and support.

I assigned the “Q” key as a shortcut for "Reveal in Finder" for the selected item in the Project panel.However, when I rename an item in the Project panel and the name contains the letter Q, Premiere stops the renaming process at that letter and triggers the "Reveal in Finder" command instead.On top of that, "Reveal in Finder" doesn't work correctly either. It simply brings Finder to the foreground without opening any windows, and that's it.OS: MacOs 26.6.2 (25G83)Chip: Apple M3Premiere 26.5 Build 99

I am trying to crop the images and sometimes videos, just my usual workflow, but lately this bug show. Whenever I am cropping something, there are times like this one that it always goes back to previous version (uncropped) when I am clicking something.This is really frustrating as sometimes some cropped images are okay but when i am editing along the way, I reverts to uncropped version without my knowledge and I will just see it after rendering it.ps: i cant upload my screen recording.

Premiere Pro 2026 v 26.0Multicam functionality is gone. Using the number keys or mouse to select a camera does not work.

Bug Report: H.264 Export Fails on All Projects (Selector 9, Error Code 3)SummaryH.264 export fails consistently and immediately (within the first 1-2 seconds of encoding) on every project tested, including a brand-new project with a single random clip and no effects. QuickTime/ProRes export from the identical source completes successfully every time. This isolates the failure to the H.264 exporter component itself rather than any project, sequence, or media content.EnvironmentMac model/chip: Apple M2 macOS version: [fill in — Apple menu > About This Mac] Premiere Pro version/build: [fill in — Help > About Premiere Pro] After Effects version/build: [fill in, if relevant] GPU acceleration setting: Video Rendering and Playback renderer selector is grayed out/locked in Project Settings > General Storage involved: Local internal SSD (issue persists even with no external/network drives involved)Steps to ReproduceOpen Premiere Pro. Create a brand-new, empty project. Import a single v

 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

Pixel aspect ratio gets wrongly interpreted on some footage after 26.2 version, i don’t know what triggers but it happens. Please test it with Pr 2025 and Pr 2026 (after 26.2 because 26.0 doesn’t have this bug.) Pixel aspect ratio gets wrongly interpreted as 1.778 and footage looks streched. Premiere 2025 correctly interprets pixel aspect ratio as 1.0 and footage looks exactly how it’s playing on a media player. If you still want to make sure the problem is not the footage, also play the footage on your media player.I will provide the footage so you can test it yourself.Note: If we transcode footage into a prores 422 or h265. This bug doesn’t occur. So it’d be a good starting point to know it has to do with h264. I hope it helps identifying the bug! also i saw similar posts about pixel aspect ratio bug. Just you know that it’s not only spesific to this footage.System info    Application: Premiere v26.3    GPU: RTX 3060 Ti with Nvidia Studio Driver ver. 610.47    OS: Windows v10.0.26200

When I scrub through a video on a Full HD timeline for more than 15 seconds continuously, the Program Monitor and output screen go black. My system configuration is: i7-11700 processor, RTX 5060 GPU, 32GB of RAM, and an NVMe 2.0 SSD.

Mouse click-and-drag randomly stops working in Premiere Pro and After Effects on MacI’m experiencing an intermittent click-and-drag bug in Premiere Pro and After Effects on my MacBook Pro M5.The problem started in Premiere Pro and recently began happening in After Effects as well. When I click and hold the left mouse button to drag something, the drag sometimes fails, requiring multiple attempts.This happens with timeline clips, playhead, timeline zoom, controls, and other drag operations.I tested the trackpad, two different mice, a wired mouse, and different USB ports, with the same result. Outside Adobe applications, everything works normally.When Premiere and After Effects are open together, the problem happens more frequently. Closing After Effects often makes Premiere work normally again.Both Adobe applications and macOS are fully updated.Please investigate this as a possible Adobe/macOS input or click-and-drag bug. It is significantly affecting my editing workflow.

Hi,Had a frustrating issue with Premiere this morning and thought it was worth reporting, as I eventually found a workaround.Yesterday afternoon I added a short voice recording made on my Pixel 10a using Google’s Recorder app. First time using it, so I hadn’t changed any settings. Everything seemed fine until I came back to the project this morning.One of the music tracks would play for a few seconds and then go silent. Pressing the spacebar to pause and play brought it back briefly, then it would disappear again. Eventually the whole sequence stopped playing or previewing.Strangely, I could still save the project, but trying to close it froze Premiere and I had to force-quit.I restarted the Mac a couple of times and reverted Premiere from 26.5.2 to 26.5.1, but the problem was still there.I used ChatGPT to help troubleshoot and read through the crash reports, which helped narrow the suspect down to the phone recording. I tried converting it in Media Encoder, but that froze too and need

Adobe Premiere 2026.2.2 (Build 3). I have been roundtripping (export > reimport) .mov ProRes exports from my timeline and noticed a contrast/gamma shift on my ProRes exports. Image is noticeably darker.Seems to only be affecting exports from .R3D source material.This is new and should NOT be happening.Funny thing is...this change only seems to occurs in 422 HQ, 4444, and 4444 XQ - not in 422.- Color Management is off.- Same exporting from Premiere or Media Encoder.------I’m pretty sure this has to do with exporting R3D footage to ProRes.Dynamic-linked clips to AE and exported. It does NOT have this problem.Ladies and Gentlemen - we have a Premiere Bug.***** I am at a full standstill right now and this is ruining my deliverables timeline. Someone - please help. *****

EnvironmentPremiere Pro 26.5.2 macOS 27.0.1 Mac Studio (2026), M5 Max, 64 GB unified memory Footage: ProRes 422 LT, 4K, on an Apple RAID (Mac OS Extended, Journaled); also tested with media on the internal SSD Sequence: vertical 2160×3840 (9:16) Media Analysis and Automatic Transcription are both off Hardware-accelerated decoding: off   SummaryAfter applying Auto Reframe to a sequence, Premiere's memory footprint climbs to several hundred GB (I saw 355 GB and 386 GB in Activity Monitor) on a 64 GB machine. macOS then terminates Premiere. The windows just disappear: no crash dialog and no crash report. It happens during playback and also when Premiere is idle. Any project containing the Auto Reframed sequence then spikes and gets killed right after opening.Steps to reproduceCreate a vertical 2160×3840 sequence with ProRes 422 LT 4K footage. Apply Auto Reframe to the sequence or a section of it. Leave Premiere idle or play back, and watch Premiere's memory in Activity Monitor. Quit, then

i do it from crt, lut , c1, c2 , skin , curves but it will get reversed when i copy from top side​​​​​​1 more the keyframes are not automatically marking in when i use masking tool 

As the title states. This morning after updating I was simply trying to cut a video file over top to stay at it’s preferred frame. Once I cut the layer at the preferred point I right clicked to Add Frame Hold, yet no matter what I did the frame would not hold. It would either create another cut and not frame hold, or it would do nothing and not frame hold. Other users in the past recommended right clicking and Clicking Ok once you click on Hold Frame Options, but that did not work as intended either. Obviously an easy work around is to just take a snapshot of the preferred layer at the preferred time and reimport it, but the frame hold saves me several clicks and is easier for project hand off.  

Issue: Object mask became extremely slow after update from 26.3.2 premiere Steps to Reproduce: Try object mask on every shot or image Expected Result: it should work like it worked in 26.3.2 Actual Result: It doesnt work or it works extremely slow Premiere Version: 26.5.2 Operating System: AMac Sequoia Or Sonoma Chip (Mac Only): M1 pro Video Format: all formats Project Size: It doesn’t matter It affects all projects and in began after update from 26.3.2 to 26.5.2

Changing the timeline (sequence) resolution updates the displayed image correctly, but the Direct Manipulation overlay (transform bounding box) remains at the previous resolution, resulting in an incorrect frame position and size.Steps to ReproduceHave sequence with some footage. Change the sequence/timeline resolution (either upscale or downscale). Select a clip and enable Direct Manipulation. Observe the Direct Manipulation overlay.Expected ResultThe Direct Manipulation overlay should immediately update to match the new timeline resolution and remain correctly aligned with the displayed footage.Actual ResultThe displayed image updates to the new timeline resolution, but the Direct Manipulation overlay retains its previous dimensions and position.When the timeline resolution is increased (upscaled), the overlay appears much farther away from the footage. When the timeline resolution is decreased (downscaled), the overlay appears smaller and is positioned inside the footage instead of