You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Crestron Programmers
I want to know how many other programmers have really embraced the power of cross point routing. If you have, what are some limitations on connections etc... Thanks Nate
Blacktee
unread,
Nov 30, 2012, 12:50:10 AM11/30/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to crestron-p...@googlegroups.com
I use them in almost every program. They are very handy and can keep you organized if you use them correctly. A great example is multiple transports: why tie up all of those join numbers and make your vtp file unnecessarily larger?
Here are few quick tips I have learned over the years to make them more successful:
Do not use them for sliders, use a serial buffer if you need to change the path of a slider in your program
For serial strings make sure they come from a MSP
Disconnect_All is your enemy if you use multiple connect symbols, try to stick to just the connect and disconnect inputs and make the control id or equip id fixed to an init
You can use a sawpulse to control it, you only need 1 logic wave to change routs. Tie the out to the disconnect and the out* to the connect.
They can be used inside of a module
Use the analog values through an equate for your interlocked buttons, it saves a symbol and is a nice double check.
With a little planning you can develop a system that saves you time in every program, copy paste gets easier. Like everything in life, they are not for everyone but I have found them extremely useful