On firmware version in between, I remember different behaviour, but don't have any documentation to refer to. Effectively on version 4.8 your software appears to have a higher priority than the SDK / TCP. On firmware 4.8, if I lock an output using your software from one workstation, the SDK / TCP connection cannot unlock it, and so it must be unlocked with another instance of your software. My experience goes like this: On 4.3 firmware, you could lock any output from any workstation connection, but any client could route anyway using the SDK or TCP/IP connection. Thanks for taking the time to respond to one of my comments, your contact is highly appreciated as always. Please contact support if your system doesn't behave like this. The same destination can be unlocked on other Videohub Master Controls but not on a Videohub Smart Control. To Unlock double click on the same same destination. ![]() A locked padlock will appear in the top right hand corner. Select the destination and double mouse click. To unlock on the software, press the shift key and all locked outputs willl become highlighted and can then be unlocked by double clicking on the destination. To Unlock select the same destination and hold the key for three seconds. Select the destination then hold down key for 3 seconds. To unlock on the software, press the shift key and all locked outputs will become highlighted and can then be unlocked by double clicking on the destination. ![]() To Unlock select the same destination and hold the Dest key for three seconds. A locked padlock will appear in the LCD display. Select the destination and hold down the Dest key for 3 seconds. Please let me know under what conditions locking does not work as we have tested this extensively in the QA lab and locking does work as expected.
0 Comments
Leave a Reply. |