-
Notifications
You must be signed in to change notification settings - Fork 344
Processing default Siri reaction after catching any speech input #544
Comments
SiriProxy works on the basis of matching the text of converted voice |
... packets. If siriproxy does not find a match based on the regex expressions you define, sirproxy simply passes on the default Siri response. Does that not meet your needs? |
Yes, so far so good. But I'm catching all voice inputs (see the regex I use above). I afterwards send the input, whatever it is, to some other, more advanced engine which is going to analyze the speech string. Though, it can be that the voice input does not make any sense particularly for that engine. So at this point I'm stuck, because the SiriProxy plugin has matched anyway the voice input, but still it seems not to be the thing I could work with, so maybe there is a default routine for that input. Concrete example: "What time is it?" would be perfectly answered by Siri by default. I catch that input, analyse it and notice that I have no use for this input. So I want to return (or forward) back to the default action. |
The reason you match all speech is because your regex expression is too generic. You have two options:
|
Yes, the Regex is pretty much as generic as possible. It is in fact my intention to match everything with the regex. Because I want to analyze the speech not in the Siri-Proxy Plugin but externally (so I consciously don't want to go with 1. or 2.). That's why I'm asking if I can hook somehow into the default routine again. |
Not that I am aware of. |
I'm wondering, if one can process default behavior of Siri after having matched up with a speech input.
This is especially interesting when You try to dynamically catch voice inputs, like with
listen_for /\A(.*)\z/i do |speech|
to analyze the input with some algorithm or other software component. So if nothing is being found, it would be great to tell the proxy plugin that it should proceed with the default Siri reaction (e.g. creating a contact or something).Is that possible somehow?
The text was updated successfully, but these errors were encountered: