Bug Reports

Hello, When i do the transcript of a clip, the application shut down where as last week, everything was fine.What happened  ? Do someone has the same problem ? I try on Premiere Pro Beta 2025 ans also Premiere Pro 2025

App: Premiere Pro (Beta) 23.3.0 (Build 20)Platform and OS: Mac mini M1 2020, 16GB, macOS Ventura 13.0 If a Sony MXF clip is added into a project and a temporal effect is applied (for example the built-in Time > Echo or Time > Posterize Time) to it,then Premiere reports retrieving frame errors and frame substitution recursion attempts (see screenshot in attach). Expected result: all clip frames should be retrieved and provided to the effect without errors. MXF file info from Premiere:Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)File generated by: Sony, Mem (2.00)AVC UnconstrainedBitstream Format: SonyGamma: S-Log3 Cine We can provide a sample video file and project on request from Adobe by e-mail (specify e-mail address).Thank you.

Hey, I have a super annoying issue with one project I'm currently working in, where preview images of sequences start to flicker. I usually sort my footage in separate sequences so I can merge separate audio tracks more easily, thus I have a lot of different bins with short sequences. Now I have one bin that gets super flacky - see video. In Premiere Pro 2025 this happens by itself and gets triggered by setting an in or out point in the sequence. Then the whole program becomes very laggy and starting any videoplayback freezes the playback handle etc.This clip is recorded in the latest Premiere Pro Beta 25.2.0 Build 12, in which similar strangeness happens, except the program still functions without restarting. I remember that this bin had the same issue in the last Premiere Pro 2024 version. I already imported everything into a new project which didn't help. For some reason it only happens in some bins and not in others. The one showing the issue has 176 sequences i

See this thread: https://community.adobe.com/t5/premiere-pro-discussions/wrong-timecodes-when-exporting-srt-files-36-sec/td-p/12753511   I am surprised there are not more reports of this issue. I did not test for drop vs non-drop frame, nor different start times.   Steps to reproduce:1. Create a one clip sequence, transcribe, and create captions. 2. Export SRT. 3. Set Sequence start time (I used 10 hours) 4. Export SRT.   Result: SRT 1 starts at 00:00:01,200. SRT 2 starts at 10:00:26,976 Expected: SRT 2 should start at 10:00:01,200.   System info    Application: Premiere Pro (Beta) v24.1.0.2    OS: Windows v10.0.19045, RAM: 63.80 GB GB, CPUs (logical): 16  

Rectangular, ellipse and polygon tool stopped working Able to draw, but they do not show in the Program Monitor W11, B117

 The option to translate captions is no longer appearing in the program. 

Hello, I tried the latest beta version of Premiere Pro but language translate option does not appear.  Could you please let me know why??

When I make on-the-fly adjustments to audio in the Clip Mixer and/or Effect Controls it writes keyframes even though write keyframes is not activated.  I also have this problem in v 25.1.0 MacOS 15.3MacBook Pro M1 

Bonjour Adobe Support,Je rencontre un problème avec le mappage de tonalité HDR → SDR (Rec. 709) lorsque j’exporte mes vidéos iPhone HDR via Adobe Media Encoder.Description du problème :Dans Premiere Pro (v. 25.2.0.117), j’ai activé l’option Auto Tone Mapping sur mes vidéos HDR (séquence / project / Lumetri settings).Lorsque j’exporte directement depuis Premiere Pro, l’image est correcte et bien convertie en Rec. 709.Cependant, lorsque j’exporte via Adobe Media Encoder (v. 25.2.0.119), le tone mapping semble être ignoré : l’image est trop lumineuse / surexposée, comme si le HDR était mal converti.Tests effectués :Vérifié les paramètres d’exportation et l’espace colorimétrique.Testé différentes options dans Media Encoder, mais l’image reste incorrecte.En appliquant manuellement un effet Lumetri pour réduire l’exposition, le problème est partiellement corrigéMa question :Y a-t-il un moyen de forcer Media Encoder à prendre en compte l’Auto Tone Mapping de Premiere Pro sans passer par une c

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