Keyboard Shortcuts
Likes
- Crestron
- Messages
Search
|
Re: Biamp Control Subnet
I forwarded ports 5353, 12003 and 61451 in the crestron router config.? When I connect to the IP address of my CP3N using the Tesira software, Tesira will take about 45 seconds then complain and say device discovery failed.? Once I click OK, it gives me the options I usually get when biamp is directly connected to the network.? I also get live feedback when? connected to the system.
|
|
Re: Yamaha AVRs
I don't know if anyone else has notice this, but the last two Yamaha receivers that I did a firmware update to, it broke some of the RS232 commands.? If you look at the RS232 response from the Yamaha receiver, it says "Restricted" after doing the firmware update. In particular, the menu/cursor commands stop working.
|
|
Re: TSR-310 voice recognition
I've played around with the TSR-310 voice recognition and actually have been pretty impressed with it.? I have offered it to a few clients but for the most part, clients have not been that interested it. They just want a remote to control their AV system and the TSR-310 does that well with or without voice. So I haven't done any in field installations yet.
I found it is not necessary to link to a google or amazon account.? Just registering with is enough.? Other report better voice recognition with a link Amazon/Google account.? But for most things I have used it for, I found that is not necessary. I found that when you pair the TSR-310 with the processor, only the first one will pair.? When you try to pair the others, they will fail.? But no big deal because after you pair the first, all the other will work too even though they say they failed the pairing.? Like Tony mention, the big advantage is the serial string youvcan send to a SIO symbol and create any type of custom voice prompt you want. Steve |
|
Re: TSR-310 voice recognition
The prompt works fairly well, but it is way easier to integrate with Josh.ai since you can assume multiple phrases for something like wakeup, makeup, etc on the serial string.? If you haven't heard of Josh.ai yet.? Go look now.
-- Ryan Baldwin CEO | XS Design Studios rbaldwin@... 760.712.2240 |
|
Re: TSR-310 voice recognition
Oh, let me add:
toggle quoted message
Show quoted text
As described, even with just the "Voice control" extender, the remote seems to communicate with a Google server according to my firewall logs. -----Urspr¨¹ngliche Nachricht----- Von: [email protected] <[email protected]> Im Auftrag von Tony Golden Gesendet: Donnerstag, 29. April 2021 16:45 An: [email protected] Betreff: Re: [crestron] TSR-310 voice recognition After begrudgingly having to do a few of these, here's my take on how it works. There are two TSR-310 Device Extenders for voice processing... The first, "Voice Control", is basically the raw speech-to-text data from the microphone. It can be used alone, without relying on "the cloud", but then programming must account for every possible interpretation, as Jeremy described below. The second, "Dialog Client", takes the raw speech text and sends it to EITHER Amazon or Google's servers for processing. It basically figures out not only what was said, but what was intended, such as "too", "to", or "two" - then either acts on it using the Alexa or Google Assistant cloud service. The remote essentially becomes another Amazon Echo or Google Hub device, and the processor and/or remote must be registered for the appropriate service. I say "and/or" because it's been a year or two since I last did one, and can't remember. Although I'm still not a fan, the few I did worked reasonably well for what was required. The key is setting client expecations :-) One cool by-product is the processed commands (what Amazon or Google determines was said) are EXPOSED in the Simpl program as a serial string, allowing you to do things with a simple SIO that couldn't be done with Alexa alone. --- On Thursday, April 29, 2021 at 7:52 AM, Jeremy Weatherford wrote: |
|
Re: TSR-310 voice recognition
Ah, thanks for clarification, Tony.
toggle quoted message
Show quoted text
I was indeed only experimenting with the " raw speech-to-text data from the microphone", hence the "Voice Control" extender. Indeed, you need to do the parsing and processing yourself, but for just some short one-word commands, it seemed to be pretty reliable, even with German language (after switching to "de"). -----Urspr¨¹ngliche Nachricht----- Von: [email protected] <[email protected]> Im Auftrag von Tony Golden Gesendet: Donnerstag, 29. April 2021 16:45 An: [email protected] Betreff: Re: [crestron] TSR-310 voice recognition After begrudgingly having to do a few of these, here's my take on how it works. There are two TSR-310 Device Extenders for voice processing... The first, "Voice Control", is basically the raw speech-to-text data from the microphone. It can be used alone, without relying on "the cloud", but then programming must account for every possible interpretation, as Jeremy described below. The second, "Dialog Client", takes the raw speech text and sends it to EITHER Amazon or Google's servers for processing. It basically figures out not only what was said, but what was intended, such as "too", "to", or "two" - then either acts on it using the Alexa or Google Assistant cloud service. The remote essentially becomes another Amazon Echo or Google Hub device, and the processor and/or remote must be registered for the appropriate service. I say "and/or" because it's been a year or two since I last did one, and can't remember. Although I'm still not a fan, the few I did worked reasonably well for what was required. The key is setting client expecations :-) One cool by-product is the processed commands (what Amazon or Google determines was said) are EXPOSED in the Simpl program as a serial string, allowing you to do things with a simple SIO that couldn't be done with Alexa alone. --- On Thursday, April 29, 2021 at 7:52 AM, Jeremy Weatherford wrote: |
|
Re: TSR-310 voice recognition
After begrudgingly having to do a few of these, here's my take on how it works. There are two TSR-310 Device Extenders for voice processing...
toggle quoted message
Show quoted text
The first, "Voice Control", is basically the raw speech-to-text data from the microphone. It can be used alone, without relying on "the cloud", but then programming must account for every possible interpretation, as Jeremy described below. The second, "Dialog Client", takes the raw speech text and sends it to EITHER Amazon or Google's servers for processing. It basically figures out not only what was said, but what was intended, such as "too", "to", or "two" - then either acts on it using the Alexa or Google Assistant cloud service. The remote essentially becomes another Amazon Echo or Google Hub device, and the processor and/or remote must be registered for the appropriate service. I say "and/or" because it's been a year or two since I last did one, and can't remember. Although I'm still not a fan, the few I did worked reasonably well for what was required. The key is setting client expecations :-) One cool by-product is the processed commands (what Amazon or Google determines was said) are EXPOSED in the Simpl program as a serial string, allowing you to do things with a simple SIO that couldn't be done with Alexa alone. --- On Thursday, April 29, 2021 at 7:52 AM, Jeremy Weatherford wrote: |
|
Re: TSR-310 voice recognition
¿ªÔÆÌåÓýCan?t confirm this. I tried with an empty program with just the TSR-310 and then added the ¡°Voice Control¡± device extender. Compiled, uploaded and then voice recognition worked out-of-the-box without any service setup. ? ? ? Von: [email protected] <[email protected]> Im Auftrag von johnh via groups.io ? It does require the voice services setup on the processor and last I messed with it you had to have an Alexa account linked as you would with regular Alexa integration. I had many issues with it actually working correctly though. I could speak the exact same command to the remote as I would to the Alexa device, and the Alexa commands worked 100% while the remote commands would almost always fail. I opened a case with Support and they were able to reproduce, and it just never went anywhere. Dont know if they fixed any of it but we gave up on the voice remote finctionality and instead direct clients to just use Alexa devices as its a much more reliable experience.? |
|
Re: TSR-310 voice recognition
¿ªÔÆÌåÓýI am using the amazon service with mine.? It works not well enough to deploy at a client site, but it is cool when it works. ? From: <[email protected]> on behalf of Jeremy Weatherford <jweather@...> ? It's basically the "OK Google" cloud service.? The trick is that it's in free-form/dictation mode, so if you have a scene called "wakeup" it may come through as "wakeup", "wake up", or "makeup"? :)? It doesn't know what the valid commands are, so you could get anything back. ? On Thu, Apr 29, 2021 at 5:36 AM Thorsten K?hler <thorsten.koehler@...> wrote:
|
|
Re: TSR-310 voice recognition
It does require the voice services setup on the processor and last I messed with it you had to have an Alexa account linked as you would with regular Alexa integration. I had many issues with it actually working correctly though. I could speak the exact same command to the remote as I would to the Alexa device, and the Alexa commands worked 100% while the remote commands would almost always fail. I opened a case with Support and they were able to reproduce, and it just never went anywhere. Dont know if they fixed any of it but we gave up on the voice remote finctionality and instead direct clients to just use Alexa devices as its a much more reliable experience.?
|
|
Re: TSR-310 voice recognition
¿ªÔÆÌåÓýAh ¨C thanks for the information. ? Cheers, Thorsten ? Von: [email protected] <[email protected]> Im Auftrag von Jeremy Weatherford ? It's basically the "OK Google" cloud service.? The trick is that it's in free-form/dictation mode, so if you have a scene called "wakeup" it may come through as "wakeup", "wake up", or "makeup"? :)? It doesn't know what the valid commands are, so you could get anything back. ? On Thu, Apr 29, 2021 at 5:36 AM Thorsten K?hler <thorsten.koehler@...> wrote:
|
|
Re: TSR-310 voice recognition
It's basically the "OK Google" cloud service.? The trick is that it's in free-form/dictation mode, so if you have a scene called "wakeup" it may come through as "wakeup", "wake up", or "makeup"? :)? It doesn't know what the valid commands are, so you could get anything back. On Thu, Apr 29, 2021 at 5:36 AM Thorsten K?hler <thorsten.koehler@...> wrote:
|
|
Re: Looking for a 10-12" Touch Screen for DGE100/200
¿ªÔÆÌåÓýAh, i see ¨C i had the TS-1542-C in mind that has a DM-input, but of course you?re right, the TSW-10xx doesn?t have this option. ? ? ? Von: [email protected] <[email protected]> Im Auftrag von zac.sparrow@... ? On Thu, Apr 29, 2021 at 02:50 AM, Thorsten K?hler wrote:
For the HDMI video ingest. This application requires live video and streaming adds close to 1? second delay. The panels cannot be larger than 12" due to physical constraints.? |
|
Re: Looking for a 10-12" Touch Screen for DGE100/200
On Thu, Apr 29, 2021 at 02:50 AM, Thorsten K?hler wrote:
But anyway, i?m wondering why you don?t go with a standard TSW-10xx for 10¡± size requirements.For the HDMI video ingest. This application requires live video and streaming adds close to 1? second delay. The panels cannot be larger than 12" due to physical constraints.? Looks like there are a few opitons in the $350 range - Elo and Mimo. |
|
TSR-310 voice recognition
¿ªÔÆÌåÓýHi, i?m just experimenting with the built-in voice recognition feature of the TSR-310. I?m talking about using the ¡°Voice Control¡± device extender for the TSR-310. Does anybody know what service is behind that? ? Does anybody have more insight into that? ? Cheers, Thorsten |
Dave H - Crestron True Blue Tech Support Engineer Since 2014