Premiere (Beta)

See this thread in the regular forum:  Users report transcription failure resulting in “No dialogue found” for files that appear to have dialogue and that work in earlier versions. Some users report this as early as 26.0.0. More users report this coinciding with upgrading to 26.2.2. I have wondered if some of the users with problems are using non-English installations or non-English files. I took special note of ​​@mattchristensen1’s post that raised the question of the large downloads involved in the extensive updates to transcription in 26.2.0. The user I link to reports that this also occurs in the Beta 26.3.0, build unspecified. I am posting this bug report for him, because I realized that the new forum makes posting a Beta bug report with the system information less straight-forward than previously. I believe the results reported are not in themselves diagnostic. Transcriptions may fail after starting for multiple reasons, and when they do, they often show no transcription and a N

System Information:Hardware: Apple Mac Studio OS: macOS Display: ASUS XG49V (Ultrawide 32:9 Aspect Ratio / Native Resolution 3840x1080) Application: Premiere Pro Beta (New Color Mode Workspace)Description of the Issue:While utilizing the brand-new Color Mode workspace, the real-time scope overlays (both the Transient HUD scopes that appear when dragging/holding the Color & Contrast dials, as well as the new permanent "Video Scopes" panel) are rendered with heavy, blocky pixelation. The pixel-precision is so low that the waveform information is entirely unreadable for fine color adjustments.Steps Taken to Troubleshoot (Unsuccessful):Verified that the Program Monitor playback and paused resolutions are explicitly set to "Full." (Note: Lowering the resolution selection to 1/2 or 1/4 results in no discernable difference in the monitor preview canvas quality, indicating a potential UI texture-buffer refresh mismatch). Enabled "High Quality Playback" via the Program Monitor settings. Att

Bug: Color Mode HUD waveform scope renders at extremely low point density — M5 MacBook ProSystem: M5 MacBook Pro, macOS Tahoe 26.4.1, Premiere (beta) 26.5.0 build 3, Metal GPU rendererWhat's happening: The HUD waveform scope that appears when clicking a Color Mode control (e.g. Contrast) renders at roughly 2–5% of expected point density. Instead of continuous waveform traces, the scope displays a sparse scatter of individual pixels — the underlying data appears correct (sky at ~60–75%, shadows near 0–20%) but the rendering is so low-density the scope is unreadable as a grading tool. The scope background and panel dimensions render at full resolution; only the waveform trace points are affected.Expected behavior: Dense, continuous waveform traces as shown in Adobe's own Color Mode tutorial videos and documentation screenshots.Reproduction: Open any clip in Color Mode → click any control that triggers the HUD waveform (Contrast, Exposure, etc.) → HUD appears with sparse pixelated trace i

Bug: Color Mode HUD waveform scope renders at extremely low point density — M5 MacBook ProSystem: M5 MacBook Pro, macOS Tahoe 26.4.1, Premiere (beta) 26.5.0 build 3, Metal GPU rendererWhat's happening: The HUD waveform scope that appears when clicking a Color Mode control (e.g. Contrast) renders at roughly 2–5% of expected point density. Instead of continuous waveform traces, the scope displays a sparse scatter of individual pixels — the underlying data appears correct (sky at ~60–75%, shadows near 0–20%) but the rendering is so low-density the scope is unreadable as a grading tool. The scope background and panel dimensions render at full resolution; only the waveform trace points are affected.Expected behavior: Dense, continuous waveform traces as shown in Adobe's own Color Mode tutorial videos and documentation screenshots.Reproduction: Open any clip in Color Mode → click any control that triggers the HUD waveform (Contrast, Exposure, etc.) → HUD appears with sparse pixelated trace i

How many cycles is it going to take to finally fix this bug.Broken since 2025Moving the WAB in the source monitor on a 2160P clip opened from the timeline in a 1080p setting26.5.0.3 

PP 26.3.0 Beta Build 71Was switching around color spaces (to Rec2100 PQ)As I push up the exposure the HUD scope changes but the Window | Video Scope (waveform & vector scope), that was formerly responsive, remains unchanged Quit & restart results in no scopes at all visible in that pane.

Clicking the comparison button in color mode (under program monitor) hard crashes PP 26.3 BETA build 71. Repeatable.Had to access the comparison button by clicking the + button and then removing items until it appeared. 

I was working in color mode just fine yesterday on version 26.2. Now after updating to 26.3  every time i move a setting in the new color panel, inside the color mode tab, it just crashes. Note: it doesn't crash in the edit tab, when selecting a clip and adjusting color through the sliders.

In the beta version of Premiere Pro, while using the new Color Mode, I noticed that the color shifts / changes when the clip is playing. When it’s paused, I grade the clip to where I want it to be. Then when it starts playing, it shifts. Watching the scopes, I see it change. The clip is relatively static where the background doesn’t change. But the scope shows it changing. And the color temperature and or tint shifts which is noticeable. This is a bug in my opinion as the clip’s grading should not change between being paused and playing. 

when I select clips to edit that have lumetri effects on them, the program shuts down 

Steps to reproduce:    1.Create a project WITHOUT captions.Export project to AME with Captions turned off in settings  Open settings for the export within AMEResult: ...New “Captions” checkbox at top of list is turned on.Expected: ...Captions to NOT be turned on in AME since they were not enabled in Premier. System info    Application: Premiere Pro (Beta) v26.3.0.71    OS: Windows v10.0.26200, RAM: 63.79 GB GB, CPUs (logical): 16

Just when I thought i was going to be able to complete a project with no bugs, one turned up.Writing the mix on an audio track is not being recorded. At least it’s not playing back.  I can’t find where to switch the viewport to track keyframes instead of clip keyframes.Enable Track Mixer Put it in Write mode Start the timeline and adjust levels (fade in or out) Stop and play backResult:Track fader stays where it was last left Track fader does not move  during playback No difference if you try to Touch the volume.  System info     Application: Premiere Pro (Beta) v26.3.0.71     OS: Windows v10.0.26200, RAM: 63.79 GB GB, CPUs (logical): 16

I applied the audio remix in the beta version, but nothing happened; only the normal audio remained, and visually it showed that it had been remixed, but it hadn't expanded the audio, it sent the original audio.

v26.3.0 BETA Build 71Mark in and out points - programme monitor does not update to new duration immediately. This is intermittent and update usually occurs after timeline is moved (but not always).

System info    Application: Premiere Pro (Beta) v26.3.0.71    OS: macOS v15.7.4, RAM: 96.00 GB GB, CPUs (logical): 24Canon R6 HEVC files are clipping blacks with Hardware Decoding enabled on Thunderbolt Displays

It’s very simple and is reproduceable every time.  I upgraded to 26.3 today, and everytime I click file, export, media encoder… media encoder does not start, and premiere just closes. When I open it back up, it says ‘it unexpectedly shut down’, and ask if I want to open the file.  Every time I try, this happens. Restarting does nothing. When i go back to using the non-beta version, everything works perfectly as expected. It’s only a problem in the newest beta.