There was a report of something like this, but I can't find a link to the thread. I don't think it was consistently adding an extra space.
Tested in Release version PR 22.0.0. A very short simple sequence; and a longer more "wordy" one. I set the caption creation to single line. In each case, some, but not every, caption line has an extra space. I do not see a pattern. It may or may not occur after a period. The transcript itself appears to be correct: there a no extra spaces in the "paragraph" of text. (I was not using speaker identification in this test.)
I also tested in Beta 22.1.1 Build 59. Neither sample shows any extra spaces. In the long sample, I only checked the first dozen captions.
I exported that transcript and imported it to PR 22.0.0. Captions created from that transcript show the extra spaces. So the extra spaces are added (or probably more correctly, "left" and not stripped) in the caption creation step, not the transcription step.
A workaround for now would be to export srt file and search/replace the extra spaces.
Another workaround would be to install the Beta version - you can install it alongside regular PR versions. Note that you can only install the lastest Beta version, which this morning is now 22.2.0 Build 1. It is a Beta version, and new bugs appear and are fixed regularly. Do the transcription there, create the captions, then export captions to .srt. Import that srt to your regular project version.
Thanks for the quick response! Yes that's exactly right, I should have clarified. The spaces occur in some lines but not all.
I'm hestitant to try a workaround via any beta's because of the tendency crossing projects to a beta version has had to cause me issues in the past. I've bricked some project files this way. Or is it easier these days to switch back to the old software?
Sounds like I'll need to keep removing manually until fixed, do you know how long something like this would usually take to receive a dedicated fix?
I agree with not opening the same project in the Beta and the current Release version. The two projects can be opened in both, because the current PR project version is the same for both. But that doesn't mean that it might not create big problems when reopened in the Release version. And that project compatibility could change at any time.
You can have both versions existing on the same computer without problem - as long as you keep them straight! I was only suggesting using an export for one to the other.
We don't know how long it might take for such a bug to be fixed in the Release version.
Reason to suspect it might be soon: several of the 2022 apps were updated about a week ago. There is a fix in Beta. And while I can only say this problem is not in Beta 2.1.1 build 59, it might have been fixed many Beta versions earlier.
Reason to suspect it might not: Murphy's laws.
I agree with fixing manually for now. I love Notepad++ for exotic search and replace - and this one is pretty easy.