OVOS offer many "types" of plugins, each can be replaced at any point with a different version, this allows you to endlessly customize OVOS!
- Case Study 1: Offline OpenVoiceOS
- Case Study 2: Cloud Services + OpenVoiceOS
- Case Study 3: Home Server
- Case Study 4: Your own interface
Compromises can be made to run on low end hardware, or if you have the juice and want to run the State of the Art on all fronts, you can make a plugin for it!
There are 4 main types of plugins in OVOS:
- "essential" plugins - the user selects which plugin to use, only 1 is in use at any time (eg, Microphone, VAD, TTS, STT)
- "sequential" plugins - these plugins are used in a specific order in the pipeline (eg, transformers)
- "parallel" plugins - these plugins are run side by side doing their own thing (eg, wake words, PHAL)
- "app" plugins - the user installs as many of these as desired, we can think of these as "apps" for OVOS, can often be run standalone or dynamically loaded as part of a ovos-service (eg, Skills)
For some plugins it is possible to configure a secondary one to handle failures of the primary plugin
Everything runs on the same device, internet not required
Cloud services can be plugins integrating with 3rd party services, or a collection of publicly hosted ovos servers
There are many reasons to use a cloud service, such as accuracy, but a device should remain functional even on internet outages
It might be benefitial to run the "brain" of OVOS in a machine, and then spread voice satellites around the house
Demo video MacOS voice satellite - https://www.youtube.com/watch?v=yRe0wcok4LA
Demo video - Local vs Satellite comparison
Demo video Raspberrypi 0 - satellite
Split your OVOS components as you want between server and devices
A bot in your chatroom
Accessing OVOS on mobile
