Premiere Pro incorrectly detects silences in Transcript and Text Based Editing

Issue:

Premiere Pro incorrectly detects silences in Transcript / Text Based Editing. The detected silence regions are visibly offset from the real audio waveform, so the silence markers do not line up with the actual pauses. Because of this, removing pauses is unreliable and sometimes cuts into spoken dialogue instead of only removing real silence.

This happens in both Premiere Pro Beta and the regular Premiere Pro release, so it does not appear to be limited to one version branch.

Steps to reproduce:

1. Import a video clip with spoken dialogue and natural pauses.
2. Create a sequence from that clip.
3. Open the Text panel and create a transcript using Text Based Editing.
4. Let Premiere detect pauses / silences in the transcript.
5. Compare the detected silence block positions against the actual waveform in the timeline.
6. Notice that the detected silence regions are offset and do not match the real silent areas correctly.
7. If you use the remove pauses function, Premiere may remove the wrong section, miss real silence, or cut into parts where speech is clearly present.

Expected result:

Detected silence regions should align correctly with the real silent sections of the waveform, and removing pauses should only remove actual silence without affecting spoken dialogue.

Actual result:

The detected silence regions are misaligned with the actual waveform. In some cases, Premiere marks silence too early or too late, and in other cases the detected silence extends into sections where speech is clearly present. As a result, removing pauses is not reliable and can cut spoken audio.

Adobe Premiere Pro version:

Premiere Pro Beta: Version 26.3.0 BETA
 

Operating system:

macOS Tahoe 26.3

Hardware:

MacBook Pro M4 16 inch
24 GB RAM

Video format: 1080x1920

Comparative information:

This issue occurs in both Premiere Pro Beta and the regular Premiere Pro version.

I already tried the usual troubleshooting steps and none of them fixed the problem:

1. Confirmed that I am using Text Based Editing and not a static transcript
2. Recreated the transcript from scratch
3. Forced the correct language manually
4. Tested different minimum pause length settings
5. Created a fresh sequence and tested again
6. Tested in both Beta and regular Premiere Pro

None of these solutions changed the behavior.

Does it affect all projects or only some projects?

I have reproduced it outside the original sequence as well, including fresh test sequences.

Does it affect new projects?

Yes. I tested it again in a fresh sequence and the issue still occurs.

When did the problem begin?

I noticed it recently, with this last release version of the Beta