Bug Reports

I just tried using it in Premiere and got a strange glitch that I can’t troubleshoot.I’m running Premiere 26.0.2 on a Mac.Screenshot attached illustrates the issue. The color fields stay regardless of rendering, timeline size, and frame rate.btw, it works fine in Premiere Pro 2025 and older versions. The issue is only with the 2026 version.Here is a link for the file: https://we.tl/t-QuN48F454DVPj6dm

Title: TrackItem.createSetInPointAction does not persist across save/reopen for video tracks (UXP API, Premiere Pro 26.2)Affected API: ppro.TrackItem.createSetInPointAction(tickTime) and likely createSetOutPointAction(tickTime)Description:Calling trackItem.createSetInPointAction(newInPoint) from UXP on a video TrackItem and executing the resulting action via project.executeTransaction() successfully changes the in-point in-session. After saving the project, closing, and reopening, the in-point reverts to the source clip's original in-point.Scope:Reproduces on all video TrackItems — confirmed on both regular source clips and multicam nested sequences Does not reproduce on audio TrackItems — createSetInPointAction on audio persists correctly Does not reproduce via native razor — manual razor (C key) and Option+Up move both persist on video Track locking (🔒) does not change the behavior — in-points still revertOther persistence behavior on video (for reference):createMoveAction — persist

I am having trouble with the Adobe font "Museo Sans Rounded" on two different Macs in two different locations in Adobe Premiere. Only 300 weight shows up OR every weight EXCEPT 300. I often need more than one weight in projects. Any ideas?

Spell Checker in Premiere Pro not working at all when reviewing captions in the text function. Despite newer versions in both premier and macOS coming out the problem continues. Help?Premeir Version 26.0.1 (Build 3)Apple M2 Max 96GB MemorymacOS Tahoe Version 26.3 

I have just upgraded to v26 of Windows 11, but I can't use the new object mask function on it. I also can't use the other mask. Expected ResultI can see the selected result by using the object mask . Actual ResultNo result has been detected or selected.

Hello,I have made several Team Projects for my employees to work on several different projects. However, whenever I try to invite my employees, Premiere is no longer sending the invitation. It does not even show the dialog box for invitation email progress.  They can send me an invite to projects they create, but I am unable to send them an invite on projects I create.

When expanding window to full size it creates a blurry render of the clip in program monitor

qeSeq.razor() silently fails in Premiere Pro 26.0.2Environment:  Premiere Pro 26.0.2  Windows 11  ExtendScript via VS Code ExtendScript DebuggerSteps to reproduce:  1. Open any project with a sequence containing video clips  2. Enable QE DOM: app.enableQE()  3. Get active sequence: var qeSeq = qe.project.getActiveSequence()  4. Target all tracks: seq.videoTracks[i].setTargeted(true)  5. Call: qeSeq.razor(String(Math.round(60 * 254016000000)))Expected: Razor cut applied at 60s on all targeted tracksActual: No cut applied, no error thrownAdditional context:  - clip.razor(), seq.razor(), seq.razorAll(),     app.executeCommand(2368) all unavailable in Premiere 26  - qeSeq.razor() is the only method that accepts input without     throwing an error, but produces no result

Two bugs: Project bin will randomly (after various periods of time) no longer accept any drag and drop movement or additions of assets. I receive the mouse icon for "unable to complete". A second bug, that also seems to occur at random, is that my source window video will become pixelated and oversaturated. It happens across multiple projects and no matter which footage is loaded into the Source window. Restarting Premiere seems to fix both, until the next time they occur. Neither bug occurred prior to 5/15. v 26.2.2 (Build 3) running on a M4 Max MacBook Pro, Tahoe 26.5

HI,I have reported an issue with Premiere Pro and Audition, but now I am encounter a problem with Premiere and Media Encoder. There doesn’t seem to be a way for me to easily view the clips I am sending to Encoder from source point in to source point out. I have used ai to try and resolve the problem to no avail. This is all very frustrating, but I know that I have had a lot of expectations met with Adobe products in the past. Even so, I must report this, as it is consuming way too much of my time to do simple things which are now complicated. I am not a big-time user of Encoder, but I have learned about it and it appears to be a very good tool for doing some of the things that would be helpful to me. The problem is as stated above, the specs are:I set in/out source points on a project in Premiere, went to export, sent the file to Media Encoder and made sure it was set to source in/out, but the whole project shows up in the source player, and there is no way to view the video in the out

Updated to v26.2.2 yesterday after it crashing in previous version - now I'm getting error code that: Adobe Premiere Pro 2026” is damaged and can’t be opened. You should move it to the Trash. This file was downloaded on an unknown date." I don't want to uninstall all my presets and reinstall for this annoying error that I've never encountered before after 10 years. Even clicking the messages uninstall doesn’t do anything so it’d have to be an uninstall from the applications. Please advise so I can move client projects forward

IssueWhen I change the default keys for zooming in the timeline to someone else, the program monitor will not follow that change.Steps to reproduceChange the keyboard shortcut for zoom in/out timeline from +/- to arrow up/downExpected result vs actual resultI press up in the timeline and the the timeline zooms in, I press up in the source monitor and the timeline/time bar zooms in, I press up in the effect controls and it zooms in… all as expectedI press up in the program monitor and the playhead jumps to the previous edit point.This is the expected behavior for the default shortcuts where up is used for the navigation between edit points but I changed that shortcut to something else:“+” is not set to any zooming, so it doesn’t zoom in the program monitor as expected.I call this a bug because the behavior is inconsistent between the different panels and the panel itself (one key follows the new setting, the other one doesn’t/is “hard coded”). It doesn’t follow any logic.Adobe Premiere

For bins with lots of clips in them, Set Poster Frame can be invaluable in quickly seeing which clips are which, as many of the clips I work with start with black, so the default Poster Frame of the first frame of the clip isn’t useful. I used to have no problem using Set Poster Frame. However, now, whenever I try to use it, nothing happens. I upgraded to PP 2026.0.0 and it still doesn’t work. I’m on a MacBook Pro M2 Max 2023 OS 26.3.

See the video. Steps to reproduce: add a 1920x1080 imageonto a 1920x1080 project timeline, reduce the scale. At 49% the image jumps and becomes much smaller. Premiere Pro v.25, all the settings reset, caches cleaned. It's on CUDA and OpenCL in 14700K+4080 On Mercury all is OK

En el panel de Texto > pestaña Transcripción, selecciono en el menú de 3 puntos “Generar transcripción automática”, eligiendo la pista de audio donde tengo los diálogos.Se ve aparecer la barra durante medio segundo y entonces se corta y desaparece, simplemente no ocurre nada y no se generan los diálogos.Con la versión anterior funcionaba a la perfección, pero desde la última versión no me transcribe en absoluto. El programa está recién instalado y con caché y configuración nueva.La secuencia no tiene nada más.

Hi, I wanted to ask about something. I created my own MOGRT file in After Effects where I'd like to be able to replace media within the template. However, when I import it into Premiere, the option doesn't show up at all in the Properties panel (see photo). In After Effects, I tried dragging both a standalone PNG and a precomposition into the Essential Graphics panel — neither worked. Am I doing something wrong in After Effects, or is this a bug in Premiere? If I use a MOGRT file from someone else, it works fine — just mine doesn't. Thanks for any response.

I remember in the recent years when I drag-n-dropped a file or a folder into the same folder or subfolder in Premiere, if the folder name or the file name matched Premiere did not duplicate them but added the new files that missed. It was very convenient to update growing folders - when you are sent additional videos for the air and you don’t have to think where to import them to, you just drop them into the same folder the other similar vids are in and update the folder structure by simply dragging it on itself in the Project bin in Premiere thus getting the old files with the new, added ones.It does not work anymore. Why? Was it broken? Now when you drop a file or a folder you get duplicates of everything even though the names match exactly:  Can you guys fix it already, please. 

As far as I know, this is a fairly old problem that has not  been solved yet. I have re-read all the forums, reviewed dozens of videos on YouTube, but I am not even one step closer to solving or at least understanding the problem.   The system configuration:Windows 10/11 AMD Ryzen 5600x AMD Radeon 6650xt   It is noteworthy that prores raw managed to run on the same system with a twelve-year-old graphic card AMD Radeon HD7950. RAW 5.8k was added to the Timeline and worked perfectly

Hello, This seems to be a consistent issue with most windows users and no solution has been found from what i have seen. I'm hoping adobe sees this and releases some kind of decoder or fix for this. Everytime i try to import prores raw footage into premiere, media encoder and after effects I get the same error code. "cannot be decoded"SYSTEMCPU: I9 13980HXRAM: 32 gbGPU: nvidia 4070 Windows 11 I have triple checked settings in premiere, updated drivers and tried using older ones, downloaded the apple decoder, turned off integrated graphics in device manager. I ve tried all the things but nothing works. Please if someone could help me find a solution for this id greatly appreciate it.  

Been having issues with the latest version of Premiere - using CUDA render results in ProRes RAW footage stuttering. Since the problem is only with the Pro Res RAW clips, I've found that the issue seems to lie in the sequence settings being a different frame size - as my output is going to be 1080p, I've been working in this space and scaling down within the edit. I've tired exporting the single clip in matching sequence settings timeline to then import and use that way but for some reason, one frame from the other pro res shot (despite not being on that timeline) came out with the export. PC SpecsCPU: Intel Core i7-14700KFRAM: G.Skill Trident Z5 - 32GB 6800MHz CL34 DDR5EDIT DRIVE: WD Black 4TB SSD Gen4GPU: RTX 4060 Ti 16GB 2X What I've triedRolling back driversI was on the game drivers - I tried the latest studio driver but no luck, so I rolled back to this version:Driver Version:555.85 - WHQLRelease Date:Tue May 21, 2024 Premiere Pro BetaStill the same issue&

Hello, with my camera I used an Atomos Ninja V+ to record videos in Prores RawI use a PC with Windows 11, I downloaded "Apple ProRes RAW for Windows 1.3". I downloaded the latest NVIDIA Studio 531.41 driver and unfortunately when I put a video in ProRes Raw on Premiere Pro it sends me an error message saying "impossible to decode the ProRes Raw video". I have a black screen on the preview screen of première pro and just the sound I have a recent laptop from this year :Intel Core i9NVIDIA GeForce RTX 4090 Laptop GPUAmount of video memory: 16 GB can you help me to use première pro with video in ProRes Raw Thanks a lot Sincerely

Hey all, I've got a really annoying bug that I'd like to have looked at. The process is as follows: - Open Premiere Pro, and load in ProRes RAW video. The program complains it doesn't have the codec.- Disable the iGPU (Radeon 890M) but leave the discrete GPU active (RTX A6000).- Restart Premiere Pro, load the ProRes RAW video, and it works. Premiere Pro is set to use the A6000 and not the iGPU, but the presence of the iGPU in the system prevents the proper assignment of the ProRes RAW codec from Apple. Software and codec are current versions. When I disable the iGPU, screen resolutions / UI scaling gets all wonky. The discrete GPU is also connected via USB4 as an eGPU on a laptop, so permanently disabling the iGPU is not a viable option. Happy to provide any data to help get this bug resolved. Thanks!

I am attempting to view, decode, and edit with ProRes RAW footage taken on an Atomos Ninja V in Premiere Pro. and I cannot get it to decode even after installing the decoder from Apple. I have tested different drivers, different Windows updates and versions, and I am beginning to think, especially after research, that it is an issue with AMD GPUs. I am using an RX 6800 with Ryzen 5 5600, 32GB DDR4-3600, and Windows 11.  Please help!   [Mod: updated the title to make the issue easier to find when searching]

After opening a new project, next to the media browser and library panels, project panel doesn’t show up anymore, and it’s not possible to add it from the window panel neither.

I usually edit from stringout sequences in my Source monitor in to cut sequences in my Program monitor. I set ins and outs on the source side, set an in point on the program side, then patch the track I want to edit across, hit period, and bam, the media appears in my sequence. I’ve been cutting this way every day for over ten years professionally. Except this week it stopped working.I’ve tried resetting all my settings and preferences. I’ve started a new project. Insert/Overwrite work fine when I’m cutting from a raw clip on the source side. But when I put a sequence in the source, enable, say, Audio 2, and try to just cut that one track across… nothing. Weirdly, if I enable ALL the audio tracks, it works. But sometimes I don’t want that. I want to, for example, go back to a version of something I had a month ago, and just take the music track, line up the two sequences and ONLY cut track 14 or 16 or whatever, over the newer track 14. Except, now that no longer works.It’s a real bumme