Bug Reports

I have a video in Spanish. If I input the transcription in Spanish, Premiere generates the transcription correctly in Spanish. However, if I want to translate it into English, it generates random text that doesn't exist.Here, I’m sharing the screenshot of the Spanish audio transcription and what happens when I ask it to translate it into English. I already uninstalled Premiere and reinstalled it, but the same thing keeps happening.

Premier Pro Beta, is not showing the option to translate to other languages Normally, a new option for translation should be there

Hi, The main exciting feature for me to test out is the new tranlastion ability in Beta.However the tranlate button isn't on any of the Text panel pages (transcript, caption, graphics). Best,Fiona

Every alteration i make it takes forever to show on the program monitor

Version: 25.2Windows 10 I understand that this a brand new feature, but I want to get an answer maybe about what is going on. While using the new media intelligence feature, after all my footage has been analysed, I get a report saying "Complete with errors" and a lot of my footage seems to be stuck at 89% complete. The media that is marked with this 89% complete mark does not show up in the search window (as one would expect). Luckaly, this feature is in beta and can be looked at. So Adobe, what is this, and is it something you can fix? This is a game changer when it comes to culling through the hundreds of hours of footage I have and I'd like to see this preform as efficent as possible. Thanks! I have some pictures below to give you all a better sence what im talking about.

I have my scratch disks set to a very specific place where my media lives, which is separate from my project file.   Every time I launch Premiere, it writes an Adobe Premiere Pro (Beta) Audio Previews folder to the same directory as my project file, NOT the project set in my scratch disks. Being the project file lives on cloud storage, I absolutely 100% do not want any preview media written to that location.    Could this be checked out and possibly fixed as it's been ongoing for a long time? It happens in the regular version of Premiere too, but it feels like it may have more chance of getting fixed if it's pointed out in the beta. 

Bonjourne fonctionne pas, surtout pour les clips DJI (caméra Osmo)Savez vous pourquoi? 

I filed this as a bug: hope its not buy design. W11 build 108 (and some previous builds) When turning on the Reverse button, the button itself get highlighted. Turn Reverse button off and button is still highlighted. Now press play/spacebar and Reverse button is turned back on instead of the playing the timeline. Expected result is to play the timeline and not turning the effect back on.  

Steps to reproduce:    1. ...Turn on snap Result: ... nothingExpected: ...  snapping System info    Application: Premiere Pro (Beta) v24.3.0.16    OS: macOS v14.2.1, RAM: 18.00 GB GB, CPUs (logical): 12

Every time I launch the latest version of Premiere Pro beta, the In and Out points of my project are reset to different places. I can set them correctly, quit PP and reopen, and they will be reset to different (seemingly) arbitrary places on the timeline. This is repeatable and happens every time so far with the newest version.

Two days ago I set up a multicam project and it was working fine, even after saving, reboots and restarts. With today's build nothing is playing on the program monitor, even after reloads and restarts. Audio plays but there's no picture in the program monitor.  No static picture either when skipping around with the playhead. If I double click  the multicam clip, it renders black in the preview monitor.  (I should see the sources). If I go into multicam edit mode, everything is black except for an outline of the camera that's supposed to be playing.  If I go into the multicam source sequence and double click a clip, it shows in the preview monitor,  but even there scrubbing the timeline shows nothing in the program monitor. I tested 3 other non-multicam projects and they work OK. To be sure I updated the nVidia driver. That made no difference. Did something break in multicamland in this build???System info    Applicat

Steps to reproduce:1. Set up a multicam sequence. Reserve one track for static images (still JPGs)2. Cut to the still image JPG for a short time3. After setting start/end points and having the cut section of the multicam track on the timeline, adjust motion in the clip to start with a closeup on an element of the JPG and then scaling it out to full frame4. Observe that it plays perfectly from the timeline5. Render to h.264 Result: ... The motion effect does not play. The full frame graphic appears without movingExpected: ... For the motion effect to play in the rendered output. System info    Application: Premiere Pro (Beta) v25.2.0.106    OS: Windows v10.0.22631, RAM: 63.82 GB GB, CPUs (logical): 16

Scrolling inside Program monitor does not zoom in or out anymore. It makes use of the scrolling bars instead. Image goes up or down. Zoom level is stuck. W11, 25.2.0.104

File>Productions Settings >    will not open any menu

I already have a sequence with many audio and video file clips that are working just fine. I then put another audio clip in wiht the same exat file type and it gives me a screeching loud white noise over the audio. It almost blows my speakers out for how loud of a waveform it is. I have tried deleting cache, restarting, copy and pasting to a new sequence and nothing will work. Any help or suggestions? 

Problem in the beta version of Premiere Pro 24.1.0 (build 64)When using Nobe Omniscope software from Timeinpixels. If Mercury Transmit is enabled and Nobe Omniscope Transmitter is checked, the Premiere Pro application closes when the Project Timeline is displayed. Simply deactivate Mercury Transmit in production before launching the project, and all is well. You can then activate Mercury Transmit and launch the Nobe Omniscope application.This problem does not exist in the official PP Version 2024.0.0 (build 58).There is simply an error message that does not close the application: "21/10/2023 low-level exception occurred in: Nobe OmniScope Transmitter (Transmit::QueryVideoMode)". Another problem with the beta version is that the Mercury Transmit function is no longer visible in Lumetri/Settings. There are only checkboxes for the various links, whereas this line is visible in the official version! Best regardsChristian Goubier

Estou relatando um problema que encontrei no Adobe Premiere Pro ao usar uma segunda tela. Percebi que os vídeos não podiam ser arrastados na linha do tempo, o que impactou meu fluxo de edição.Meu Ambiente de Trabalho:Software: Adobe Premiere ProHardware: GPU NVIDIA RTX 4050Sistema Operacional: WindowsConfiguração de Múltiplas Telas: SimDescrição do Problema:Ao tentar mover os vídeos na linha do tempo usando a segunda tela, percebi que eles simplesmente não se deslocavam. Para solucionar isso, testei várias configurações no Premiere e no sistema, mas nada parecia resolver.Tentativas de Solução que Realizei:Verifiquei a configuração da GPU no PremiereConfirmei que estava usando Mercury Playback Engine GPU Acceleration (CUDA).Atualizei os drivers da minha GPU (RTX 4050)Fiz isso pelo GeForce Experience.Ajustei as configurações no Painel de Controle da NVIDIAConfigurei para Máximo Desempenho e selecionei a RTX 4050 como GPU principal.Redefini as preferências do PremiereRestaurei as configur

When adding a lut (in this case Universal day for night) from the default preset bin it works as expected. If I want to add a lut preset from a custom bin it does not work. Input lut is not added. This works in 25.1.73 but not in 25.2.0.101. W11

Steps to reproduce:- Right click inside the clip you want to edit its speed- Make sure that the speed and duration option is disabled. Result:  The speed and duration option seems to be disabled, it seems to be the same bug that had the option of nesting sequences within a projectExpected: ... System info    Application: Premiere Pro (Beta) v25.2.0.100    OS: macOS v14.5.0, RAM: 16,00 GB GB, CPUs (logical): 8

Nesting is impossible in PP beta 25.2.0 build 87 and in PP 25.1 (both German language) on Mac Mini 2018 with MacOS 15.1.1 (24B91) and external GPU AMD Radeon Pro 580.The menu item Nest ("Verschachteln") is greyed out.It does not even work with the official trial file from https://learndownload.adobe.com/pub/learn/premiere/premiere-pro-nesting-sequence-cc.zipHave I missed a required setting? or is it a bug?

Lumetri takes about 15 seconds to update its edits in the Program monitor/scopes Build 90 and earlier. W11, gtx1070ti source clips canon mxf intraframe. preview codec Prores LT. Playback in FULL is smooth.   It looks like I am not the only one: https://community.adobe.com/t5/premiere-pro-beta-bugs/lumetri-effect-huge-input-lag-in-prpro-25-2-0-build-57/idi-p/15046909

Steps to reproduce:    1. Load project and place playhead somewhere.2. Tap arrow up (Prev Edit)  Result: ... Play head goes to start of timeline.3. Tap arrow down (Next Edit) Result:... Playhead goes nowhere Expected: ... KB shortcuts to be standard System info    Application: Premiere Pro (Beta) v25.2.0.99    OS: Windows v10.0.22631, RAM: 63.82 GB GB, CPUs (logical): 16

When the home panel opens it would never let me open any project clicked from the first try, instead I'd have to click several 3+ clicks frantically -- then it will initialize the opening... This is happening from the very beginning of the appearance of the renewed Home panel long ago.

Hi, I updated Premiere Beta from version 25.1x63 to version 25.2x31. I open the project and see this "This project contains masks or generative AI features that are not supported with this version of Premiere Pro. To view and edit with these effects, update to the latest version of the app.". What does this mean? Very strange 😞 

Steps to reproduce:While I usually drag & drop footage into the project bin, I decided to try the Import function.1. Started new project, Import screen came up2. Selected files from the folder on my drive array (all silent AVI clips)3. Import Result: 1. Nearly all the files on the drive appeared in the bin and on the timeline, including audio files from another project.2. In the Program window the bit of the screen that was in the Import window (showing the file thunbnails) stayed in the program window.3. Program becamse unresponsive and crashed when closingExpected: ... To work! System info    Application: Premiere Pro (Beta) v25.2.0.99    OS: Windows v10.0.22631, RAM: 63.82 GB GB, CPUs (logical): 16