Bug Reports

I've posted this in the other thread about the timeline issues, but maybe it's better suited as a new bug report.Since the latest build (25.2.0 Build 50) I'm having a lot of timeline and other issues since this build. For example:- GUI isn't loading properly on start (some black panels) unless I resize those panels.- Timeline preview rendering start takes around 60-70 seconds, then goes at normal speed- Timeline freezes frequently (stops updating the program monitor)- External tools like Premiere Handy Tools and Excalibur are not working properly (very long delays of 60s+ until they apply the settings)- Timeline often stops accepting input, I have to alt-tab away from Premiere and back again to be able to click on clips or start playback.- Clicking a clip on the timeline does not update the data in for exampleEffect Controls. It only updates the data once I move the playhead. - sometimes most of the GUI stops responding to clicks unless I move the playhead or resize the correspond

I have a timeline (1080x1920 25fps) with 3 layers of video (one of which is a Lumetri adjustment layer) and, seemingly importantly, 3 tracks of subtitles. In PPro Beta (25.2.0x127), if I reposition/rescale one of the layers, when I start play back (or scrub), it jumps to a random position and scale. When I stop playback, it snaps back to its previous position. This does not happen in the release version 25.1.0 (Build 73). This renders the Beta version unusable for my current project. If I render the sequence, the problem goes away - ie. the actual rendered video is fine - UNTIL a subtitle appears on screen (even if just 1 subtitle track is active), and then one of the video layers jumps to a random position and scale. If I turn off all subtitles, the problem goes away. As far as I can tell.

Trying to grade a clip in premiere pro beta but the lag time between making an adjustment and the program monitor updating is about 3-5 seconds. It used to be basically instantaneous. Enabling and disabling the adjustment layer also takes 5+ seconds for the pogram monitor to display.  Clip has basic lumetri adjustment (exposure / shadow / etc) And above it is a adjustment layer with a lut (slog3 to 709 v2 provided by sony) and a creative effect lut from speed looks. So in node speak, that would be three adjustments or layers. It plays back the clip in real-time but making an adjustment is arduous with or without proxies turned on.  Sometimes after awhile it will become more responsive but it still won't "live update" it will only update once you release the mouse button. Tried clearing cache and prefs, but problem remains.  Tech details:  Windows 11Windows v.10.0.26100.1 PrPro 25.2.0 build 57 NVIDIA GeForce RTX 2080 Ti v.32.0.15.66

I'm in the most current Beta of Premiere Pro and Auto -Save will interrupt like two minutes after having just auto-saved even thought my settings are at 12 minutes.

Premiere Pro Beta 25.2 (Build 117), 50 clips, total lenght of the sequence is 08 mins, 4k, SSD, preview 1/8, good hardware.When I do trim a clip (at the beginning of the sequence), it lags up to 10-20 seconds for the preview to update. There is no such lag in the end of the sequence, it works much faster. So, I have to create nested sequences to make editing possible.No such lag in Premiere Pro 25.1.0 stable, it works smooth.Tried:1. Switching color spaces (currently, using Wide Gamut and ACEScct).2. Proxies.3. Turned off Visual Analysis, Transcription, etc.4. All of the other settings are equal to the stable version.

When manually typing in a font in the source text field, the cursor deselects from the text field after typing one letter. You have to reclick into the text field to continue typing. After which typing one letter makes it exit the text field again - and so on.

Premiere won't show fonts for mogrt assets so it is impossible to change fonts... This beta program is useless like this.

I can't Join Through Edits in captions in PP 25.2.0 Build 123, and PP 25.1 on Windows 11, 23H2. Right-click shows the option but doesn't do anything. Neither does a shortcut for "Join All Through Edits".    

Updated to the latest Beta of PP this morning and the timeline does not start playing when hitting the Spacebar; well; sometimes it does, 98% it does not start playback  

Can not export captions.The button is greyed out. Try to push it several tims but not effect. Restarted Premiere, but nothing changes... button is still greyed out. 

Hello, I'm having trouble opening Premiere Pro Beta projects when my Audio plugins are enabled (example: Clear, iZotope, etc). The project stalls 40% and I have to force quit Premiere. Then I have to open Premiere and disable my audio plugins to then open the project (and then I can re-enable audio plugins and they work). This is very cumbersome and I'd love to simply use the audio plugins I've purchased. I have Premiere Pro Beta 25.2 on a Mac Studio (M1 Ultra) Any solutions? Thank you Remy 

No fonts at all are shown on the text properties on Premiere Pro Beta

Make a new layer of text but can only see the red bounding box. There are no characters on screen but the text shows in the graphics panel.

Unable to extend clip, getting a check connection error

While selecting a bunch of clips in the timeline by shift-clicking them one by one, if I inadvertently shift-click on a cut point, PPro deselects everything and then selects only that cut point/transition. This, in my opinion, should not happen. If, during the shifty-clicky-selecty process, I do click on a transition, PPro should either ignore that click, or select the clip closest to the mouse pointer - even if it's only by one pixel. It should never just deselect everything.

I am absolutely infuriated beyond words. Without any speed changes or modifications, Warp Stabilizer has suddenly decided to stop analyzing clips altogether. These are plain, simple, normal clips that worked perfectly fine until today. Now, this completely ridiculous and mind-numbingly frustrating issue is threatening my entire project. This bug is so incredibly stupid that it’s putting me at risk of missing deadlines and losing work. I cannot believe I'm losing time and potentially money over such a senseless problem. Adobe, I expect better from software that professionals depend on for their livelihood. Fix this ASAP before it costs people like me our jobs!

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