Bug Reports

Search box Film Impact Dashboard does not have a X to clear the box like other panel search boxes in the program have.W11, 26.5.0.77 

There are 2 critical issues with exporting.Loudness normalization effect always returns ‘Unkown Export Failure’ (happens with every codec.) Exporting MP4 exports video and audio separately and doesn’t merge them when export’s finished. (Very critical bug.) (happens with every mp4 codec)also there seems to be a bug on forum. Even when we choose ‘report a bug’ on top right menu it gives us categories to choose a question. I can’t report a bug if I don’t choose something else and select the bug report category again. You guys even bugged the bug reporting system as well as not being able to export mp4’s properly. congrats.

 System info     Application: Premiere Pro (Beta) v27.0.0.32     OS: Windows v10.0.26200, RAM: 63,77 GB GB, CPUs (logical): 32Exporting MP4 exports video and audio separately and doesn’t merge them when export’s finished. n the latest version, 27.0.0 build 32, this no longer happens when exporting from Premiere, but it still happens when exporting from the encoder. I'm also having this other problem Summary: Final program export loses one audio channel (stereo collapses to mono/single-channel) in Premiere Pro Beta, regardless of export format.Description: When exporting the sequence "Final multicam" directly from the Timeline, the resulting video file only contains audio in one channel. This happens consistently across multiple export formats (tested with H.264/MP4 and MOV/QuickTime), ruling out a codec- or preset-specific cause.Verified NOT the cause:Sequence audio track (Audio 1, 4 clips) was inspected: Volume levels are correct and identical across all clips, no clips are muted. Cha

Latest Beta from August 27th…Can’t “edit in Photoshop” RAW files from LR.It gets stuck on Opening in Photoshop but it never does. I tried converting the RAW file in LR to a DNG and it opens just fine.Seems to be a problem with the Camera RAW engine or something…I am downgrading until it’s fixed.

No audio when trying to export a MP4 using High Quality 1080p HD, H.264, audio format AAC, sample rate 48000 Hz Stereo, and bitrate 320. After export I get a video only, no audio. I do get audio if I export in a mov format.

Device Name DESKTOP-BL6AF56Processor 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz (3.50 GHz)RAM Installed 64.0 GB (63.7 GB usable)Graphics NVIDIA GeForce RTX 3070 (8 GB)Intel(R) UHD Graphics 750 (128 MB)Storage 550 GB of 954 GB usedDevice ID 91A1AF7B-F643-4B3F-9072-7040DF647206Product ID 00330-54058-88985-AAOEMSystem Type 64-bit OS, x64-based processorPen and Touch 2-point touch support Edition Windows 11 ProVersion 25H2Installed 08/12/2024OS Build 26200.9168Experience Windows Feature Experience Pack 1000.26100.344.0

As the description states, the export of media fails for an unknown reason when the loudness normalization effect is applied during media export. I was able to isolated the effect in loudness normalization. When the effect is disabled, the export runs perfectly. Attached is the error and the effect Loudness normalization effect Error when trying to export 

I’m posting this because I feel I have come across a pretty niche issue in the last few versions/updates of Premiere Beta 27.0, and I have found the solution. I hope the Adobe team fixes this, and perhaps my findings can help anyone else experiencing this. I could not find anybody else talking about this, so apologies if it has been discussed before.Issue:Entire program shows unresponsive UI redraws and visual lockups while audio and video continue to play. Lockups are only fixed in a single instance by clicking any menu dropdown at the top of the program, then continues the lockup behavior.Also wanted to note, I have been having more and more playback issues as new updates come along in both Premiere and Premiere Beta, and that was NOT the reason I was troubleshooting. I’ve long accepted that the program is sluggish and gets worse over time. But the solution seems to have helped in that regard, unexpectedly. I didn’t include this in the title because I didn’t want to misguide anyone d

I was trying to enlarge my video to 200% scale, but accidentally typed 200% into the Opacity field and hit enter. Seeing as there is no such thing as 200% opacity, Premiere apparently decided the only reasonable response was to crash. Version 27.0.0 BETA StaticLib (Build 18)MackBook Pro 16-inch, 202364GB MemoryApple M2 MaxTahoe 26.5.2

When I apply the Gaussian Blur effect and create multiple masks, the blur is applied only to the first mask. The other masks do not show any blur effect.Steps to reproduce: Add a clip to the timeline. Apply the Gaussian Blur effect. Create a mask under the Gaussian Blur effect. Create one or more additional masks under the same effect. Adjust the blur amount. Expected result:Gaussian Blur should be applied to every mask created under the effect.Actual result:Gaussian Blur is applied only to the first mask. The additional masks have no blur applied.Premiere version: 27.0(Beta)Operating system: MacOS Tahoe

Todas as legendas no adobe premiere pro estão sendo geradas apenas em inglês, mesmo que eu faça  a mudança no campo de preferências, o programa não está gerando as legendas em português!

I have been editing in premiere for 10+ years and this might be the worst update ive seen. Keyframes for the  mask tool dont work at all. The AI mask tool doesnt work at all and it broke the whole tool. I cant even do a simple hand animated mask. Adobe is way too big of a company for there to be problems like this with essential tools that we've had for decades. These are the things that make me want to abandon these programs. It is my fault I started this project in the beta version though i guess. Cant even revert to another version.

In Premiere 2026 you can copy / paste clips into AE comps. This copy /paste feature isnt working in beta. 

Quando vou para a tela de exportação do premiere, em qualquer projeto, a minha tela simplesmente carrega pra sempre, já cheguei a deixar horas parada pra ver se mudava algo mas não mudaPreciso de ajuda com urgência, isso pausou 100% da minha produtividade

Mask positioned outside adjustments. When try to move or paste to adjusment premiere broke.

When Premiere Beta runs on a second monitor both in clip LUT and sequence LUT the options are greyed out and I can not select anything. I have to move the premiere window to the main macbook monitor to be able to see the selection of LUTs

It is slow. the menu is slow. I cant use this program. Its annoying and costing me money and my reputation

The program monitor freezes completely on a single frame during playback when encountering sections with subtitles, shapes, gradients, or custom effect presets. Audio continues to play normally, but the video preview remains stuck. This issue arose immediately after updating to Premiere Pro Beta 27.0.0.20.System specifications:CPU: AMD Ryzen 9 9950XGPU: NVIDIA GeForce RTX 5070 Ti 16 GBRAM: 64 GB DDR5OS: Windows 11Here you can watch a video that shows the error.https://drive.google.com/file/d/1NrTozF6I3BnzEYklB7KkatWbtg-nK9ar/view?usp=drive_link

Title: Audio Plug-In Manager scan hangs and returns no plugins (VST3 + AU) — 27.0.0.17 and 26.0 beta, macOS 26.5.2. Release Premiere scans the same folders correctly.Environment: Premiere Pro (Beta) 27.0.0.17 and the prior 26.0 beta build. macOS 26.5.2 (25F84), Mac17,6, Apple Silicon, 64 GB. Audition (Beta) exhibits the same. Premiere Pro 2026 release and Audition release on the same machine are unaffected.Symptom: Preferences > Audio > Audio Plug-In Manager, folder list contains only /Library/Audio/Plug-Ins/VST3 (VST2 paths removed). Click Scan for Plug-Ins with Rescan existing plug-ins checked. Beach ball, then the Available Plug-Ins list is empty — no VST3, no AU. Effects > Audio Effects shows only Adobe built-ins. ~/Library/Preferences/Adobe/DVAAudioFilterScan is never created after the scan.Control: On the same machine, Premiere Pro 2026 release launched after DVAAudioFilterScan was deleted, rebuilt it on its own, and loads every third-party plugin (iZotope Ozone/Neutron/

Steps to reproduce:1. Fresh install of Premiere (Beta) v27.0.0.16 on macOS 26.5.22. Open Effects > Audio Plug-In Manager3. Confirm /Library/Audio/Plug-Ins/VST is in the VST folder list4. Click Scan for Plug-InsResult: Scan completes with 0 third-party plugins found. Opening a.prproj referencing iZotope Ozone (VST) and Insight 2 (VST) throws"Audio Filter missing" for both.Expected: Scan detects installed VST2/VST3 plugins. Release & Beta Auditionon the same machine scans the identical folders successfully andopens the same project with both effects intact.Audio Filter missing: 3:5653545a 6e4f5a4f 7a6f6e65 2050726fAudio Filter missing: 3:56535449 4e533049 6e736967 68742032

When I create a new project and drag my first clip into the timeline to create the timeline it does in as it should. however any other clips do not. please fix.

when I stop the play head over one of my clips, I can see the clip, but when I play the video the clip is not showing.  Chatting with the AI assistant - this error appears to be with Film Impacts Bokeh effect on the clip.  It seems it can't render the frames in real time so they are being dropped

I’ve recorded a Loom video to show the issue. Essentially, when I’m editing using a transcript - every clip starts too late and often in the middle of a word. So I have to go into every clip and start it earlier so you can hear the full word. 

This build of the Beta (it happened even on the previous one) has Control Surface completely broken. An ‘unexpected error’ prevents Premiere to initialize any Productions and Projects, resulting in a warning window telling me the error - I attached the warning window.The issue doesn't present itself in the regular release - altough I'm some version behind as the latest stable build has a known issue with RTX 50 series cards when it comes to graphics properties, which funny enough was fixed in the Beta builds.My PC is as follows:Windows 11 Pro Intel Ultra 9 285K NVIDIA 5070Ti 16GB (latest Studio Drivers) 64GB DDR5I use the Logi MX Creative Pad. 

I had no problems Friday- now today on Monday I can hardly use any command in Premiere Pro Beta without it is crashing. All my Adobe apps is up to date. Hope you can fix this issue, what ever is causing it.