You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Searching in $XDG_DATA_DIRS would be nice. (Spec.) You don't always want to install models system-wide.
As it's not always set, it should also look through default values of /usr/share/ (as currently), /usr/local/share/, and $HOME/.local/share/.
In addition to exposing manually installed models in non-root locations, this would also allow automatic use of models installed via E.G. Flatpak or Nix, which set $XDG_DATA_DIRS.
Also, from the AUR, the share subdirectory seems to be vosk-models, not vosk/models:
What is the canonical place to put models? Do the docs give a recommendation?
nshmyrev commented on Apr 29, 2022
Like I wrote before we need to look for models in 3 places: /usr/share/vosk, /home/user/.cache/vosk, os.env('VOSK_MODEL_PATH').
…Or, actually, since it looks like class vosk.Model() already includes search path logic anyway, why does vosk-cli implement its own model_path() resolution order?
vosk-cli/voskcli/transcribe.py
Lines 249 to 252 in 81b9f1c
vosk-cli/voskcli/transcribe.py
Lines 337 to 340 in 81b9f1c
Searching in
$XDG_DATA_DIRS
would be nice. (Spec.) You don't always want to install models system-wide.As it's not always set, it should also look through default values of
/usr/share/
(as currently),/usr/local/share/
, and$HOME/.local/share/
.In addition to exposing manually installed models in non-root locations, this would also allow automatic use of models installed via E.G. Flatpak or Nix, which set
$XDG_DATA_DIRS
.Also, from the AUR, the
share
subdirectory seems to bevosk-models
, notvosk/models
:But that may be a packaging issue in the
vosk-api-bin
package, asvosk-api
does usevosk/models
.Just a thought/convenience that might be nice to have.
The text was updated successfully, but these errors were encountered: