Open GenericName123 opened 6 months ago
@GenericName123 this was originally created as a simply way to store values. I agree 100% with the idea though. I think a camera group should have the ability to associate its self with an output on a router and/or multiple outputs. Cameras could store an input value. It wouldn't the most flexible however it would work for situations like divisible rooms and be easy enough to setup. Regardless it needs to be QSYS agnostic to fit into the framework and function with other potential systems. Any thoughts on the above statement, I will probably start working on something shortly.
I think the easiest way is just adding to the documentation to be more clear that the first video route value is required when using QSC routing. Could the context of the 'video route' value header name change depending if camera router is defined, or display a red required tag if router is defined? Sort of like how other required values are in red?
Camera routing with Qsys, requires using video routing in additional page. Not intuitive and would either be better moving to analog drop down with router output select or renaming "video route 1" to be more obvious in it's requirement for use with camera router.