Bug Reports

SummaryIn Premiere Pro (Beta) 27.0.0 Build 57, a MogrtText value can initially be read successfully through the public UXP API. However, after writing the text back once through a transaction, the same parameter can no longer be read with getStartValue().Environment- Adobe Premiere Pro (Beta): 27.0.0 BETA StaticLib (Build 57)- Premiere UXP: uxp-9.4.0-local- After Effects: 26.5.0 (Build 89)- Adobe UXP Developer Tools: 2.3.0.5- Windows 11 Home, Version 25H2 (OS Build 26200.9457)MOGRT configurationThe MOGRT was created in After Effects 26.5.0.It contains one non-animated text layer with uniform styling.Exposed text parameter:ShizukuTextInitial text:字幕テストSteps to reproduce1. Place the AE-created MOGRT on V1.2. Retrieve the exposed ShizukuText parameter through the UXP API.3. Call getStartValue().4. The returned value is successfully recognized as MogrtText.5. getText() successfully returns "字幕テスト".6. Call setText("字幕テスト成功！") on the MogrtText value.7. Create a keyframe and a set-value actio

When adding a vignette in new color mode, the preview video in multicamera mode moves halfway off screen

I have a 12 minute clip on a sequence and for some reason, the program did not generate a transcript for almost half of the clip.  The audio is clear and recognizable, but it did not generate a transcript.  

See regular forum: I’m posting this bug report in the Beta forum to focus what I believe are the underlying issues. At least 2 changes have been made to the fields in the caption/graphics txt/csv exports during the 25.x and 26.x cycles. What I believe are the correct fields were present in the 24.6.5 version. I am unsure whether any of the changes are by design, since I thought the reasoning that led to the 24.6.5 fields should be the same. My comment in that forum thread included the problem in 25.6.4 with the exports there: “In 25.6.4, the fields became the same for caption export and graphics export: Speaker name, Start Time, End Time, and Text. Perhaps there was a plan to export speaker information to captions, but a) the Video Track and Layer ID fields should not have been removed and b) a further change was made the time of update to 26.2.2, now making the fields for caption and graphics export the same as the caption export in 24.6.5: Start Time, End Time, Text, and Layer ID.” S

Edit 12/18/25: I corrected the original post to say that this change occurred AFTER 25.5.0. I downgraded and checked this today. As of today, there is no change in Beta 26.1.1.4.   Original post: Sometime after release 25.5.0, the text panel csv and txt imports changed, mostly to mimic transcript export. This has been partly corrected by Beta 26.1.0.2. Build 10 is messed up, and I do not have access to Build 12 yet, where those issues are fixed.   See this regular forum report: https://community.adobe.com/t5/premiere-pro-discussions/there-is-a-problem-with-the-text-tab-export-to-csv/td-p/15613541   I tested in 24.6.5, 25.6.3, and Beta 26.1.0.2. I looked at captions, graphics text, and captions upgraded to graphics. I can provide the detailed results.   My summary conclusions are:   25.6.3 csv caption export header adds Speaker as field 1 and removes Layer ID as last field. This has been corrected in Beta 26.1.0.2 or before.25.6.3 csv caption export content give

i downloaded the beta version of premier and the HEVC codec inst installed 

Quando prova a fare una maschera nel pannello color continua a darmi errori e a dirmi che non trova un oggetto selezionabile 

Using Premier v27.1.0 Beta on MacOS 27.1 When I enhance audio on some of my 1920x1080 (24fps) clips that were generated with Seedance 2.5, the video clip seems to shift the start point of the clip back 14 frames! So sudenly the audio is out of sync.Workaround is I delete the video clip on th etimeline, leaving the enhanced audio, then shift the start point back to the correct frame and then lign it up with the audio. but this is a very weird bug and only happens on some clips.

Product: Adobe Premiere Pro (Beta) (Build 21)Version: 27.1 BetaOperating System: macOSSeverity: Functionality regression affecting editing workflow1. SummaryThe two-up frame preview in the Program Monitor no longer appears when moving Time Remapping speed-transition keyframes in Premiere Pro Beta 27.1.Instead of displaying the frames associated with the speed transition, the Program Monitor continues to display the frame at the current playhead position. This makes it difficult to visually identify and position the frames at which speed transitions begin and end.2. Steps to ReproduceOpen Premiere Pro Beta 27.1.Create a new sequence.Add a video clip to the timeline.Right-click the clip and select Show Clip Keyframes → Time Remapping → Speed.Create a speed keyframe on the Time Remapping speed line.Split the speed keyframe to create the two halves of a speed transition.Click and drag one half of the speed keyframe.3. Expected BehaviourWhen dragging either half of the speed-transition keyf

I'm experiencing an issue with the AI Assistant in Adobe Premiere Pro Beta.When I open the AI Assistant and click on the "Skills" section, there is no option available to add, upload, or create a new custom skill.I would expect to see an option to add custom skills, but the interface doesn't provide any way to do so.Could you please confirm whether this functionality is currently supported in Premiere Pro Beta or if this is a known bug?Thank you for your assistance.

I can only change a color if I add a hex number after this mornings update. 

I suddenly can no longer open most of my projects. It seems like saving them is actually corrupting the project files, and I get the “An unknown error occurred while opening the project.”I can retrieve a working copy from the auto-save, which is horrible cause every time I lose some work and need to redo it, but then I can’t open it again after I save it.This is an urgent issue, please fix, specially that now beta is at 27 so I can no longer revert my projects to Premiere.System info    Application: Premiere Pro (Beta) v27.1.0.18    OS: Windows v10.0.26300, RAM: 255.69 GB GB, CPUs (logical): 20

My sequence is set up properly to do a Synchronization, but “Synchronize” is grayed out. I just updated to the most recent version, but it started happening on the immediate prior version. I am going to use the regular version for now, but please report when this has been fixed. 

Olá! Estou com um problema nos créditos do meu assistente de IA. O sistema está informando que atingi o limite semanal, mas os créditos não foram renovados desde ontem. Pelo que entendi, os créditos deveriam ser diários. Poderiam me ajudar a resolver isso e restaurar meus créditos?

Specifically, every time I would use the rectangle tool to create a background for text, the app would crash completely. Then, the same thing happened with the text tool.

I made a brand new file in Premiere Beta. Now it crashes every time I try doing anything. It just started today. I already cleared the cache and used Sift+Alt. Version 27.1.0 Build 16

Running latest build but this has been happening for some time. I recently started using a feature that essentially allows Premiere to auto apply a LUT according to the clips color space (most are S-log3 but some are rec 709) and when ever there is a overlay warning banner, such as what you see when applying effects like warp stabilizer, The footage either changes color or is completely scrambled (as seen in the screen capture) until the banner disappears. Seems like a bug to me but maybe I am doing something wrong? I have been experimenting with my RAW footage workflow and started running into this issue. Thank you for your time! 

HILFE BITTE!SEHR WICHTIG FÜR CAPTIONS:Wenn ich ein MOGRT für meine Captions bearbeiten will und dann im Reiter "Eigenschaften" auf das Textfeld klicke um Text Änderungen vorzunehmen, dann wird automatisch beim anklicken des Textfeldes der gesamte Text markiert. Ich kann also keine einzelnen Worte blau markieren oder mit dem Cursor in Worte oder zwischen Sätze rein klicken, es wird immer der ganze TExt angewählt, egal was ich anklicke. Erst wenn ich die Pfeiltasten nutze hebt sich die Markierung auf und ich kann den TExt bearbeiten, das bedeutet aber ich muss alles mit den Pfeiltasten machen und im Text navigieren und löschen und das kostet unnötig Zeit, denn den Maus Cursor kann ich komplett nicht nutzen

I don’t know if this is a bug or an intentional change. If it’s intentional please don’t. The standalone crop effect is way better than built in one and also you can change it’s order. Thanks to Excalibur I was able to apply it to a clip and It’s named ‘Crop (Legacy’ but it’s not in the legacy folder either.

Anyone experiencing Media Encoder 26.0 running extremely slow and only using a small percentage of their GPUs?

Hi,The same Sony Burano X-OCN LT clip (.mxf, S-Log3 / S-Gamut3.Cine) looks noticeably flatter in Premiere (Beta) than in Premiere Pro 2026: lifted blacks, lower contrast and less saturation. All the color management settings are identical in both versions.VersionsPremiere Pro 2026: Premiere (Beta) macOS Settings (identical in both)Color Manage Auto Detected Log and Raw Media: ON Source Clip: Use Media Color Space → Sony S-Log3/S-Gamut3.Cine Input LUT: None, Preserve RGB: OFF Sequence Color Setup: Direct Rec. 709 (SDR), Output: Rec. 709 Sequence Clip: S-Log3/S-Gamut3.Cine → Rec. 709, Luminance Preserving gamut compression, Hue Preservation tone mapping, Highlight Saturation 0.5 Display Color Management: OFF in both No effects applied, Source Settings unavailable (greyed out) in bothSteps to reproduceCreate a new project in both versions. Import the same X-OCN LT clip. Create a sequence from the clip. Compare the Program Monitor.Expected: same result as Premiere Pro 2026.Actual: the Beta

Applications quits during initializing stage.

At the moment of export media, you click on files, export, but do not export, I mean, it does nothing. 

On the area that is highlighted with red box, all of them both can go above 255 or can go negative value.

everything  is gone. WTF?!?