Thank you for all the help everyone. These last two examples really helped by moving the abuf or aos, whatever is needed from the interface side to the room side of the x-point. Previously I had it in the interface side and sent the out of the abuf to the x-point which is where my problem was. It works great now. Really solved my problem. I am still mastering x-points.
toggle quoted message
Show quoted text
--- In Crestron@..., "olly_penguin" <oliver.hall@...> wrote:
Hi Jason,
My solution to this (it's buried deep inside our framework, but it's used in lots of places) is to pass each analog value (from the user interaction side) into an AOS, with say a 1 second pulse width. The output of each AOS then goes into a digital on the x-point.
On the x-point destination ("equipment"), the digital enables an analog buffer for each "managed" signal.
Since AOS's are retriggerable, any *changing* analog value will propagate, but switching x-points doesn't propagate a new value (unless you happen to switch the x-point while the AOS is still high.)
The AOS/buffer stuff is all encapsulated within the x-point framework wrappers, so you don't even notice it's there. We use the technique for anything that has a slider/analog control - lights, treble/bass/balance, heating dials, etc.
Hope that helps,
Ol
--- In Crestron@..., "Jason Andersen" <jandersen@> wrote:
When I switch crosspoints the slider input value which ends up sitting on the output side of the abuf gets sent to the set volume input of my room module.
Thanks Heath. That is actually an idea I came up with last night and when I compiled I forgot to save the changes to the room module. I'm going to finish it now.
