OK, so I have things working now. And it actually seems to work really well!!
Unfortunately for me, it wasn't a real problem but red herrings that I would say are at the feet of Crestron (I should be used to this...)
?
Part of the issue is the Generic CCD file that by nature has universal I/Os that may/may not be used with specific hardware, and thus the help file does not offer specific help notes about how said specific hardware works, or what signals are used/not used or how they behave....? ?Have I said how much I hate these CCD files...?
If they would just publish help notes and idiosyncrasies in dedicated documents instead of some 'creepy' output into the console (which probably doesn't have all that we need anyway), we would be miles ahead of the game, IMHO!!!
?
Here's the take-aways for those who haven't tried it yet:
- The CCD help file (Typical PDF doc with the demo program) has not been updated for notes about the Voice I/Os. Thus, your only hope is trying to look at the demo program and divine the secret knowledge of the application which creates red herring #1.
- The 'VoiceReady_F' output NEVER goes HIGH.? My suspicion is that the cable box doesn't tell us this so thus, red herring #2, as the Demo program has a signal that tells the user ready/not ready.??
- Maybe this one is obvious to others but not me. When you press the MIC button, you literally start getting PAGES and PAGES of unreadable hex data coming thru the RawVoiceData. Even without speaking. This was particularly confusing because in trouble-shooting this (because no VoiceReady_F) my tests with just the basic Voice extender, I received beautiful, readable text coming into the program. The Hex blather seemed very not right, especially since it wasn't based on my speaking...Red herring #3
?
At the base, It seems to work well. I would love to not have the pages of hex vs actual readable text (which perhaps this is security stuff), and would love to see Crestron actually help us deploy these kinds of things efficiently, unless of course they would like to write fat checks for us as a community T/S'ing and fixing stuff...? Fat chance, not fat checks!...:(
?
?
