In order to be able to use a kdenlive-23.08.x-x86_64.AppImage, which I couldn’t up until recently (see Kdenlive 23.08.2 released - #5 by ludo0565 and others there as well), I finally installed the latest version of the OS - Debian 12 Bookworm.
As it were, as far as I am concerned, an improvement (newest versions of the Kdenlive appimage do start and are apparently normally usable [still having a project started under the old “22” versions]) doesn’t come alone: it brings … other … improvements, which are, to me … a break in my usual practice.
In this case it is Python, which under Debian 12 seems to me largeley overhauled: compulsory virtual environment (with specific directory, among other things), no clue where VOSK (which I already had working under Debian 11) is supposed to be positioned and situated, and so on and so forth… (despite searching, but I’ll search on)
Up to the last and main question: how and where do I tell the Kdenlive appimage to look for VOSK and SRT ?
(Apparently, it still seems to know where the language packages are)
Thanks a lot for your answers on the last/main question (and any contributions on the earlier questions).
If I click on “Install mssing dependencies”, I get this:
I can do nothing else. (Anyway the information displayed in that window is not quite correct, because Python is alrady installed, and everything I need works: now I can operate VOSK and let it transcribe text)
Once installed in the path it should be able to find them.
A quick Google search leads to this article as the first hit listed on using them perhaps a clue to the manual install required step shown in it might get them done for you.
Yes, indeed, I found this page, too.
It’s one of those I found between my first and my second post, which caused me to say that I was “seeing light at the end of the tunnel”.
This page (and one two other ones) allowed me to understand how Python and in particular VOSK are organised in Debian 12 (and in a particular user’s directory).
But all this did not tell me anything about the status/place/position of VOSK data in a Kdenlive’s appimage environment, and how and where it’s got to be declared, in order that Kdenlive should find it.
Whereas in Debian 11, Kdenlive’s appimage seemed to find the data it needed, in Debian 12 it’s not the case… So I was thinking, there ought to be in Kdenlive settings a window that allows me to select the directory where “vosk” (by the way, now there is a “vosk-transcriber” programme) and “srt”. I know where they are; but there is no way I can tell the Kdenlive appimage.
You are welcome but unfortunately I have no clue on that problem you have. Other than it is obviously a path or permission perhaps problem. As if the 11 found it the 12 should too. Does the vosk-transcriber location show up in your PATH if you use the echo $PATH.
I checked as you rightly suggested:
user@debian-12:~/nerd-dictation$ echo $PATH
I have installed - following the Debian advice of setting up a virtual python environment - the python programme data only locally, i.e. only for “user” in his own directory…
So I might have to declare the directory where “vosk-transcriber” and “srt” are so that it appears in the $PATH , right?
Yes if it cannot see it in the path then programs looking for it will not find it. An article below on adding to the path in Linux.
How to check where it is at according to the system.
zeus@9600k:~$ which vosk-transcriber
zeus@9600k:~$ which backup_home.sh
There you can see it does not find it on my system because it is not installed or if installed is not in a directory in the PATH line. My home directory backup script is shown is in my ~/bin directory which I know is in my path.
Just as a proof that it worked earlier on (and without declaring anything in PATH or anywhere else for that matter), these two screen shots, under Debian 11 Bullseye, with kdenlive-22.12.2-x86_64.AppImage:
Well, looking for solutions, I found the light of day at the end of the tunnel!
Wondering why I had noticed nothing new for a while here, I decided to look closer.
I found this notice: Kdenlive 24.02.0 RC ready for testing
And apparently this latest release candidate solves my problem:
I just had to make a copy of my already installed and standing (and under regular use) “python_virtual_env” directory right where kdenlive settings were telling they’re expecting it, renaming it as shown - and there it went: kdenlive found it, and all is ready for use, just like I knew it!
A first test gave a speech recognition as I knew it from previous versions.
I mark this thread as solved.
Cheers to all!
P.S. I can’t wait till kdenlive-24-02-0-rc is effectively released