Created attachment 139451 [details] script not found error message in 21.04.2 SUMMARY I did use the speech recognition successfully on the same machine with 21.04.1. After uninstalling and updating to 21.04.2, this stopped working. The configuration screen now has an orange error message at the bottom that reads "The speech script was not found, check your install." I would like to emphasize that it _did_ in fact work before, and that I _do_ have vosk and srt installed. I also saw #438306 but this seems to be a different error. I also tried installing various versions of vosk (including the previously working 0.3.27, the latest version 0.3.30 and the one mentioned in the other ticket 0.3.22). STEPS TO REPRODUCE 1. Install kdenlive 21.04.2 2. Install vosk and srt via pip3 3. Open kdenlive 4. Go to configuration screen / speech to text 5. Add a speech model 6. click "check configuration" OBSERVED RESULT There's an error telling me > The speech script was not found, check your install. but no information which script this might be. Also starting any recognition (of course) yields a note that I'd need to firstly configure speech to text. EXPECTED RESULT Speech recognition should work as in the previous release. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION As pointed out before, this setup used to work in 21.04.1. Downgrading to 21.04.1 immediately fixes this problem (even with vosk 0.3.30).
I can confirm that speech to text with 21.04.2 is not working. I tested with the nightly build and it works. Please try with the nightly build https://binary-factory.kde.org/job/Kdenlive_Nightly_mingw64/. The 7zip is the standalone version.
I tried `kdenlive-master-797-windows-mingw_64-gcc.7z` (build on 2021-06-20) and it also gives me the "script was not found" message.
Thanks for your report! As this seems to be the same as or at least closely related to BUG 438306 (the one you already know :) ), I am going to mark this one as duplicate to have everything neat and tidy. Please continue to comment there… *** This bug has been marked as a duplicate of bug 438306 ***