dnmeid
commented
1 year ago Both features have been implemented now. Unfortunately I don't have a modular matrix at hand and so I don't know what happens if there are some slots unused. I assume that switching unavailable ports might give an error message but the module won't crash.
Describe the feature Up to now companion only supports symmetrical matrices (I=O). Since companion seems to get its default values for the "switch I to O" commands from the number of outputs of the matrix, matrices with a lower number of outputs than inputs can't be controlled. Only the first n inputs can be switched (n=O).
In LW3 this is the following (e.g): CALL /MEDIA/VIDEO/XP:onClick(Ox,Iy)
So if we could just enter x=Input and y=Output we can control any Lightware Matrix no mater of I/O relation.
Further it would be amazingly practical to have the output lock for each and every output. If the output is live it is sometimes necessary to lock it. So unintentional switching by e.g. presets is avoided.
In LW3 the lock is: CALL /MEDIA/VIDEO/XP:lockDestination(Ox)
the unlock: CALL /MEDIA/VIDEO/XP:unlockDestination(Ox)
Is this platform dependent (windows, mac, ..)? NO
If documentation is required to implement, do you know where to find it? LW3 is universal for all LW3 devices - ask if you need something!
Usecases Especially Lightwares HDbaseT matrices are asymmetrical but also the modular types can be of that type. The lock is an operating feature which I use for setups where the matrix is shared with other operators. I lock what I want to have safe on program.