Skip to content
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.

stt configuration inconsistently shared #62

Open
mikejgray opened this issue Jun 1, 2023 · 2 comments
Open

stt configuration inconsistently shared #62

mikejgray opened this issue Jun 1, 2023 · 2 comments

Comments

@mikejgray
Copy link

mikejgray commented Jun 1, 2023

My backend STT configuration is:

{
  "stt": {
    "module": "ovos-stt-plugin-server",
    "ovos-stt-plugin-server": {
      "url": "http://192.168.86.58:9090/stt"
    },
    "fallback_module": "ovos-stt-plugin-selene",
    "ovos-stt-plugin-selene": {
      "url": "https://api.mycroft.ai",
      "version": "v1",
      "identity_file": "/root/.local/share/ovos_backend/identity2.json"
    }
  }
}

However, what got passed to my OVOS device was:

  "stt": {
    "module": "ovos-stt-plugin-selene",
    "ovos-stt-plugin-server": {
      "url": "http://192.168.86.58:9090/stt"
    }
  },
@emphasize
Copy link
Member

emphasize commented Jun 5, 2023

Had some similar expirience while setting up my local whisper docker, but didn't dig deeper.
There was no request to whisper but i got a transcription (from somewhere), so i think the second definition was chosen.

BTW i use selene plugin on ovos side pointed at the personal backend stt endpoint. That way the transcription gets saved in the database. (just fyi)

@JarbasAl
Copy link
Member

JarbasAl commented Jun 5, 2023

STT configuration isnt passed from backend to device, the backend simply uses the same config format but this wont be sent to devices, its just for the stt endpoint

there is no fallback_stt in backend either

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants