It's quite annoying to have to go into the settings tab just to specify the transcription language. A shortcut for this would be very handy.
For a simple toggle, there should be a way to select the languages the user is interested in—similar to how keyboard layouts can be switched.
However, not all languages are well supported by all models. Latvian, for example, has limited support. To address this, I see two possible approaches:
-
a) When toggling languages, automatically switch to the appropriate model as well.
The downside is that this would make it harder to switch between small and large models for languages that support multiple options.
-
b) Add a separate shortcut to toggle the model, and allow the user to specify, per model, which languages it should support.
This requires more configuration and multiple shortcuts, but it gives fine-grained control—allowing the user to switch models based on language.
Example Use Case
The user configures for example three languages: EN, LV, PL
And some models: small, big, big-lv (amount of models not tied to configured languages)
For small and big, the user enables only EN and PL
For big-lv, they enable only LV (assuming it doesn't perform well with other languages)
When toggling between EN or PL, the user can switch between small and big models depending on whether they prioritize speed or accuracy.
When LV is selected, big-lv model is automatically selected and toggling the model would have no effect, since only one model supports that language.
It's quite annoying to have to go into the settings tab just to specify the transcription language. A shortcut for this would be very handy.
For a simple toggle, there should be a way to select the languages the user is interested in—similar to how keyboard layouts can be switched.
However, not all languages are well supported by all models. Latvian, for example, has limited support. To address this, I see two possible approaches:
a) When toggling languages, automatically switch to the appropriate model as well.
The downside is that this would make it harder to switch between small and large models for languages that support multiple options.
b) Add a separate shortcut to toggle the model, and allow the user to specify, per model, which languages it should support.
This requires more configuration and multiple shortcuts, but it gives fine-grained control—allowing the user to switch models based on language.
Example Use Case
The user configures for example three languages: EN, LV, PL
And some models: small, big, big-lv (amount of models not tied to configured languages)
For small and big, the user enables only EN and PL
For big-lv, they enable only LV (assuming it doesn't perform well with other languages)
When toggling between EN or PL, the user can switch between small and big models depending on whether they prioritize speed or accuracy.
When LV is selected, big-lv model is automatically selected and toggling the model would have no effect, since only one model supports that language.