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
Maybe you want to look at using two STT variants at the same time.
If an external STT service is unavailable (maintenance, no internet connection, etc.), Willow could try to recognize the command on the local Multinet.
I don't know if Willow has the resources to do these processes in parallel, but you can do them in sequence.
The text was updated successfully, but these errors were encountered:
As part of #25 we're adding health/status checks for WIS, HA, and others.
The issue with this approach (as you say) is having the model loaded, and with up to date commands that make any sense. Additionally, we would need to be careful in terms of user expectation because multinet fundamentally cannot support many of the commands of WIS so users will be caught off guard when Willow switches back to multinet for whatever reason - commands that used to work likely won't. We could of course provide status on the display but as a far-field device where you either can't see or aren't looking at the display this is of dubious value.
Additionally, we would have to look hard at how feasible this is fundamentally because the ADF framework we use currently initializes and loads multinet on boot depending on configuration. We'd have to really explore how this could work. However, on that note, post initial stable release we want to generate the multinet vocabulary on device dynamically (from WAS) so we could look at this as part of that process.
Maybe you want to look at using two STT variants at the same time.
If an external STT service is unavailable (maintenance, no internet connection, etc.), Willow could try to recognize the command on the local Multinet.
I don't know if Willow has the resources to do these processes in parallel, but you can do them in sequence.
The text was updated successfully, but these errors were encountered: