Text-Based Editing pause detection has regressed between Premiere Pro 26.0.2 build 2 and 26.3

Hi Adobe team,

I’m reporting what appears to be a regression in Text-Based Editing, specifically in how Premiere Pro detects short pauses in the Transcript panel.

The version that works correctly for me is:

Premiere Pro 26.0.2, build 2

The version where I am facing the issue is:

Premiere Pro 26.3

In Premiere Pro 26.0.2 build 2, I could use the Pauses filter in the Transcript panel and adjust the Set pause length / Minimum pause length setting to detect very short pauses in spoken dialogue. This was extremely useful for dialogue-heavy editing, because Premiere would correctly identify even small pauses, including pauses around 0.1–0.11 seconds.

However, in Premiere Pro 26.3, the same workflow no longer behaves correctly. The pause-length slider still allows the minimum pause length to be set very low, but Premiere now appears to ignore many short pauses that were previously detected in version 26.0.2.

For example, on the exact same video clip:

• Premiere Pro 26.0.2 build 2: approximately 200 pauses detected

• Premiere Pro 26.3: only around 40 pauses detected

This is with the same clip, the same spoken dialogue, and the same type of Text-Based Editing workflow.

This does not feel like improved or refined pause detection. It feels like the pause-detection threshold is no longer being applied correctly in version 26.3, especially for very short pauses around 0.1–0.11 seconds.

This regression has seriously affected my editing workflow. I rely on Text-Based Editing to quickly identify and clean up pauses in dialogue-heavy videos, and because of this issue, I have had to continue using Premiere Pro 26.0.2 build 2 instead of the latest version.

Could the Premiere Pro team please investigate whether the Pauses filter or Minimum pause length / Set pause length behavior has changed or regressed between version 26.0.2 build 2 and version 26.3?

It would be very helpful if the pause-detection sensitivity from 26.0.2 could be restored, or if users could be given a more precise and reliable way to detect short pauses in the Transcript panel.

Thank you. Text-Based Editing is a genuinely valuable feature, and I hope this regression can be fixed in an upcoming update.