Premiere Pro 26.0 fails to transcribe audible dialogue and displays “No dialogue found”

All,

When Sumeet says “investigating a similar issue & have made improvements in the latest Beta,” that means 2 things to me. 1) Staff have probably been unable to replicate the issue. 2) They have fixes for other transcription/text editing issues in the Beta version, which might have fixed the problem. That makes Sumeet’s request for users who are affected to consider testing in the Beta very important. If the problem is present, then they can focus replication attempts there, which is where they must fix the problem anyway. If the problem is not present, that will emphasize the importance of trying to get “similar issue” fixes in the next release version rather than one farther down the line. And no, I have no idea when/what that means, except that the current release is 26.2.2, and the Beta jumped from 26.3 to 26.5.

For the few of you who reported that the Beta version showed the problem, this is as easy as updating the Beta and giving it a go. (​@bonebj, ​@Visuales_FVST, ​@wombatant111) See my cautions below regarding updating the Beta. For those of you who do not have the Beta installed, you can install it independently from your production/release version(s). You can reset its preferences without affecting your release version.

The link Sumeet provides is to the “Adobe Creative Cloud Beta FAQ.” It provides important information, particularly if you have not used an Adobe beta version previously. Here's the link again:

https://helpx.adobe.com/in/x-productkb/global/creative-cloud-beta.html

But I’d like to emphasize or clarify some things, and add a few others.

Here, we are testing for a bug. And sometimes, the problem will persist to a new version via preferences or the media cache. So it is important to do what I always do when updating the Beta: hold down the shift key when you first launch it and Reset preferences, Clear the cache, and Reset the plugin loading cache. Also, create a NEW project for testing.

I do not recommend using the Beta version for deadline-sensitive work, but many users use it successfully. The recommendation here is to install it for testing, not to move your project there for your regular work. As new builds are released (usually every day), there are regular bugs, some of which make the version unusable until the next build, or less commonly, more than one build.

Because the build is changing frequently, it is very important to report the build with the version. It is not enough to say “the latest,” to give the date you updated, or to just give the version (currently 26.5.0). Report the version with the build number: so I currently have PR Beta 26.5.0 Build 3 installed. Today, I see that the latest is Build 15. In the cloud desktop, it shows the date as 5/27/26. But in the PR Beta using Help -> About Premiere, it will only show the Build. So I prefer reporting the build number, not the date.

You can only install the latest version of the Beta, and cannot roll back to a previous version. I sometimes create a clone of my system drive if I have an important need to roll back.

Be certain that you have auto-update turned OFF. In the Creative Cloud Desktop, click on your avatar/account -> Preferences -> Apps. You'll see Auto-update.

When you open the Beta and there is a new build of the Beta, an invitation to update appears. Do NOT click on it. As I said, you cannot roll back and may discover stop-your-work-dead-in-its-tracks bugs.

Stan

Hi everyone,

We’re investigating a similar issue & have made improvements in the latest Beta. Would you mind trying the latest Beta version to see if it’s working properly? You may refer to this link to learn more about the Creative Cloud Beta Program.

Thanks,
Sumeet