Bug Reports

Subject: Intermittent Voice-over Recording Failure in Premiere Pro (Version 24 and above)Hello,I am experiencing a critical issue with voice-over recording in Premiere Pro.The issue:The voice-over recording intermittently fails. It sometimes records audio normally, and other times, the recorded audio file has a duration of 0 seconds.This occurs regardless of the audio device used (including professional audio interfaces, webcam microphones, and USB microphones).The problem persists consistently in Premiere Pro versions higher than 24.Troubleshooting performed:Reinstalled Premiere Pro completely.Tested various audio hardware including Steinberg UR22C audio interface, webcam microphone, and USB microphones.Changed USB connection methods (direct connection, USB hubs, etc.).Verified settings including sample rate (48000Hz), buffer size (512 samples), and audio latency.Temporary solution:Downgrading Premiere Pro to version 24 completely resolves the issue, confirming it is a software-relate

Ik keep getting this error whilst scrubbing through timeline after 25.2 update"Can't render audio Premiere Pro can't render your audio due to high CPU usage. Try using fewer audio effects, simplifying your timeline, or increasing the 1/0 buffer size in Audio Hardware Preferences"Tried all options mentioned. After a while the audio stops coming throughThanks!

I'm having the issue of not being able to see the screen, not the whole screen, but the screen where it allows you to view the footage you're editing. I've tried reopening the app, and restarting my pc. Yet both failed. I don't know what to do or what is wrong with it. I'm going to keep trying to fix it, but if anyone has any solutions, please tell me them.

I wanted to have an iris transition via a circular mask to have better control over the feathering and accelleration, but when the mask touched the screen, the feather completely disappeared for that little bit. I can't imagine why it would be this way other than a glitch. Creating a dynamic link to after effects completely fixed the issue, so I am reporting it here as a bug. Here are some screenshots I took of the issue. Please fix this. It is extremely aggervating to have to resort to going to another software to fix an issue that shouldn't be here in the first place. Premiere Version 25.0.02019 MacBook Pro 2.4 GHz 8-Core Intel Core i9 

Nach dem Update auf die neuste Adobe Premiere Version wird bei einem aktuellen Projekt das Drohnen-Footage nicht mehr richtig gerendert. Seit dem Update stockt das Material beim Export, das Video-Footage im gleichen Projekt ist nicht betroffen. Auch wenn wir das Drohnen Footage in einem separaten Projekt Rendern, erfolgt der Export mit stockendem Bild. Betriebssystem Windows:Version: 25.2.3

I notice that my timeline is having a serious performance issue during playback. The video preview is played with full quality without issue. Already update GPU driver. Already reset everything back to default. I notice this happen after the new update. 

Screen Frozen everytime when I drag some items from Project Window have to End the Premiere from Task manager to run it again. 

The time keeps running for several frames, when the space bar is hit.That makes editing to audio quite a hazzle. Note: this happens when Mercury Transmit is active. (I use it to view my edit via Blackmagic Ultrastudio Monitor 3G).

For many many years now, in Mac OS, there has been an issue in Premiere (and apparently some other Creative Cloud suite of applications) where, in any of the File Export or Save As dialog boxes, when one brings up the "Create New Folder" dialog box, one cannot paste text into text field.  This is something encountered many many times daily for some of us.  In the Illustrator forums, this same issue has been upvoted many many places.  An Adobe employee acknowledged that this was a known issue YEARS AGO, and suggested upvoting the initial complaint.   Some relevant posts:https://community.adobe.com/t5/illustrator-discussions/unable-to-copy-amp-paste-in-save-as-dialog-box-in-illustrator-2020-on-macos-catalina/m-p/13286899/page/3#M340274https://illustrator.uservoice.com/forums/601447-illustrator-bugs/suggestions/39374122-still-not-able-to-paste-cmd-v-text-when-creati

Ok, the title makes clear this is part rant, but I also am legitimately hoping there's a fix to the latest (for me) of the unending bugs and issues working with captions. Premiere just keeps falling further and further behind free options like CapCut.  When changing size of captions, the I (first person singular) is gigantic, about 50% larger than all other captions. That is, I've uniformly applied a font and size to all captions, but the I is much much bigger when it's standalone. This doesn't happen when the letter I is in a word.   

Normalmente exporto haciendo Source In | Out en la línea de tiempo, y desde que pasé al 2025 me está dejando un frame en el inicio del video cuando estoy en Windows y en la oficina que usamos Mac, lo deja al final. Me toca correr dos cuadros al final de cada nota para no dejar los negros.Eso es un error de la selección de In y Out de esta versión?Gracias

Looks like the ZXP sign process is broken both on macOS and Windows.macOS: Signing process ends with: [1] 21894 segmentation fault ./ZXPSignCmd -sign mypassword -tsaWindow: just fails with no error Command that fails:  ./ZXPSignCmd -sign "/Users/admin/Desktop/extension/dist/cep" "/Users/admin/Desktop/extension/dist/zxp/com.my.extension.cep.zxp" "/Users/admin/Desktop/extension/lib/.tmp/com.my.extension.cep-cert.p12" mypassword -tsa http://timestamp.digicert.com/None of the environments nor macOS nor Windows has changed. It just worked yesterday and today it's not.ZXPSignCmd has proper executable rightsTried changing timestamp serversTried using different network connectionVerified with different repos/toolsTested on ARM/x64 macOS, ARM/x64 Windows. All fail to signConfirmed the same behavior by many devs

Everyone, please help me. I edited the videos and everything was okay until this morning. I definitely saved the project. But when I reopen it, the timeline was like that, the video clips with parallel lines can't be seen and video orders were all messed up. Do you know how can I fix this problem? 

  i have a problem with the ligature in premiere pro when writing arabic.the problem is, when i write "lam alif", the ligature doesn't work properly. even though i have turned on the ligature feature.i tried it in adobe illustrator and it turns out there is no problem.but what i wonder is, this doesn't happen in all fonts. there are fonts that have the ligature "lam alif" correct and some have problems. coincidentally the font i want to use has problems.the font name is LPMQ Isep Misbah

Dear Adobe Support Team,I am writing to report a recurring issue in Adobe Premiere Pro version 25 that affects the export process. When working on a 1920x1080 HD sequence containing video clips with a resolution of 1440x1080 pixels, the export process frequently freezes, especially when certain transition effects are applied like clock wipe. This issue persists despite various troubleshooting steps, including updating the software, clearing media cache, and adjusting export settings.I have consulted the official list of fixed issues for versions 25.x and 24.x, but I did not find any mention of this specific problem. Additionally, I have explored community forums where similar issues have been discussed, but no definitive solution has been provided.Could you please confirm if this is a known issue and if there is a planned fix in an upcoming update? Any guidance or workaround you can provide would be greatly appreciated.Thank you for your attention to this matter.Best regardsDariusz Ksi

Has anyone experienced this kind of distortion? One solution is to reformat the video in HandBrake, but I'm looking for a simpler solution within Adobe. I've only experienced this with Getac body-worn camera footage recently. I know the company has updated its technologies within the last several months, and that's when I noticed the issue started. Premiere is updated. Any ideas?Video Properties:Type: MPEG MovieFile Size: 1.26 GBImage Size: 1912 x 1088Frame Rate: 30.07Source Audio Format: 44100 Hz - Compressed - MonoProject Audio Format: 44100 Hz - 32 bit floating point - MonoTotal Duration: 00:25:28:04Pixel Aspect Ratio: 1.0Alpha: NoneColor Space: Rec. 709Color Space Override: OffInput LUT: NoneVideo Codec Type: MP4/MOV H.264 4:2:0Variable Frame Rate Detected

Bug en todos los paneles de premier pro luego de la ultima actualizacion ! cambia de colores o simplemente no se ven los sub menu, tambien se buguea el monitor no puedo visualizar, en terminos simples no se puede editar con ese bug. no funciona al 100%. necesito una solucion rapida porfavor para continuar con mi trabajo.   Bug in all premier pro panels after the latest update ! It changes colors or you just don't see the sub menu, it also bugs the monitor I can't visualize, in simple terms you can't edit with that bug. it doesn't work 100%. I need a quick solution please to continue with my work.

Issue Summary:After updating to Premiere Pro version 25.2.3 (Build 4), I noticed an intermittent issue where the timeline cursor does not move when using the left or right arrow keys.The playhead stays in place instead of moving one frame as expected.Steps to Reproduce:Open an existing project with H.264 footage.Place a clip on the timeline.Attempt to move the timeline cursor using the ← or → arrow keys.Occasionally, the cursor will remain stationary despite repeated key presses. Temporary Workaround:Copying the contents of the sequence into a new sequence resolves the issue. Footage Specs:Format: H.264Frame rate: 50 fpsBitrate: 50 MbpsColor: 4:2:0System Configuration:CPU: Intel Core i9-13900KRAM: 64GB DDR5 6000MHzGPU: NVIDIA RTX 4070 TiStorage: Samsung 990 Pro NVMe 4TBOS: Windows 11 24H2 Expected Behavior:The timeline cursor should move one frame forward or backward with each press of the arrow keys.Actual Behavior:The cursor sometimes gets stuck and doesn't move, makin

Hi there,Here are two annoying bugs that appeared recently with Premiere Pro 25.2 and are still here on 25.2.3. Essential Graphics sortingThe Essentiel Graphics panel fails to sort MOGRTs on an alphabetical basis. They're always sorted by most recent. Properties panel showing wrong MOGRT propertiesRandomly, the Properties panel displays properties related to another MOGRT on the timeline, not the selected one. The Effect options panel displays the right properties. Thanks for investigating these issues.Best regards, Adobe Premiere Pro 25.2.3Apple Mac Studio 2023 - M2 Max - 32 GB RAM - 512 GB SSDMacOS Sequoia 15.4.1

Ever since I downloaded Adobe Premiere Pro, I’ve been experiencing the same recurring issue: the first time I launch Premiere, the “play” button to start the video I'm editing works correctly. However, as soon as I make any changes to the video (for example, adding audio, adding or editing subtitles, inserting a clip, etc.), I can no longer use the “play” button to play the video and continue editing. The only workaround is to close Premiere Pro after every single change I make and then reopen it, just to be able to play the video (but only once). I’m working on a Mac with a decent amount of free storage space, and both my Mac and Premiere Pro are updated to the latest available version. How can I fix this issue? Thank you to anyone who can help!

I have a problem with my version 25.2.3 (build 4) of Premiere Pro: basically it doesn't track the mask when I have to blur a detail like a face or a car license plate. That is, it does the tracking but it doesn't let me scroll the clip at that moment to check if the mask is centered or not. Since this problem has never happened to me, I wonder if it's a bug in this version or not. Thanks

Hi Adobe Team,I’m encountering a recurring issue in Premiere Pro related to font rendering. Upon reloading a project, certain text layers that are set in ALL CAPS display incorrectly—with inconsistent capitalization (see attached screenshot). This occurs even when:The ALL CAPS formatting toggle is enabled or disabled in the Essential Graphics panel.The original font style was correctly saved and previewed before closing the project.It seems Premiere is misinterpreting the character casing upon reloading, despite the font settings not being altered. This affects the appearance of animated titles and static text, making the text look broken or unprofessional.Would love to know if there's a workaround or if this is a known bug that’s being addressed.

Have a movie.  Create a freeze frame.  Everything to left of the new cut has the opacity line (moving movie portion).  To the right of the cut (freeze frame) the opacity line has dissapeared.  Tried switching to 'motion' and 'speed' but still no line on the track in the timeline where i can drag up and down for opacity / keyframe changes. 

The core of Premiere Pro, "comfortable cutting and editing," is sacrificed with each new version.The most important thing is that editing "runs smoothly." Professional tools like Premiere Pro should prioritize the following above all else:- "comfortable operation"- "fast editing response"- "UI that responds to the user's intuition." However, in recent years, since v24,- the drawing of the timeline playhead becomes heavy- tracking during shuttle movement becomes sluggish- scrolling and zooming get stuck- captions and AI transcription continue to run in the background these elements are affecting the user's editing rhythm to a level that "breaks the rhythm of editing."I think Adobe is actively adding AI and automation features, but at the same time, it seems that "UI drawing and core engine optimization" are being put on the back burner. Could you please reconsider the priorities?

The below is a fix that is working for some users.   Update: To fix the issue described below, upgrade your Mac’s OS to the latest version: Sequoia (15.0).Go to Settings -> General -> Software UpdateMore information about Sequoia available here.   This issue effected some users with Mac Intel computers using AMD Radeon GPUs. The bug involved a crash when using Enhance Speech, particularly with longer audio clips. We do not see evidence that this was effecting other configurations.We are continuing to work on a fix for remaining users still experiencing this issue. Thank you for your patience.