Jump to content
Vari-Lite Controls Support Forum

MD1125

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by MD1125

  1. Well yeah, under 2.3 of the Monitor EULA it states: "Licensee will not, nor will it permit others to, modify, adapt, translate, reverse engineer, decompile, or disassemble the Software or any component thereof (including the Documentation), or create derivative works based on the Software (including the Documentation), except to the extent such foregoing restriction is prohibited by applicable law." and under 5.12: "Licensee acknowledges that confidential aspects of the Software (including any proprietary source code) are a trade secret of Cooper Lighting Solutions UK Ltd., the disclosure of which would cause substantial harm to Cooper Lighting Solutions UK Ltd. that could not be remedied by the payment of damages alone. Accordingly, Cooper Lighting Solutions UK Ltd. will be entitled to preliminary and permanent injunctive and other equitable relief for any breach of this Section 5.12." In this case for example, sharing where this is: Would be allowed, because it kinda falls under intended use, but I think sharing real source code or "trade secrets" wouldn't.
  2. I was just in general interested in how all of it works I guess. No direct purpose, just pure interest. Oh and regarding the theoretical direct string input: I was actually able, after some playing around, to fully emulate the traffic between the Monitor and FLX S24 by opening my own TCP connection to the FLX and then send the same strings it does from the Monitor App. From what I've looked at in the traffic it first sends a string to initialize, then one carrying the Password, and then you have (in theory) full control over the Keyboard. By sending these strings: "5a 38 38 52 01 00 00 00 1d 00 00 00 44 4b 65 79 00 00 00 00 00 0a 00 00 00 00 00 00 00", "5a 38 38 52 01 00 00 00 1d 00 00 00 44 4b 65 79 00 00 00 00 03 61 00 00 00 00 00 00 00", "5a 38 38 52 01 00 00 00 1d 00 00 00 44 4b 65 79 00 00 00 00 01 0a 00 00 00 00 00 00 00", You can emulate you typing an "@" on your keyboard, same goes for any other keys you might press, so by expanding this system you could (theoretically) make your own API I guess, just not directly for colour, although that would also work if you kinda pre-record where the mouse has to press. And as far as "debugging" these strings goes, they seem to be actually rather structured, example: First string for @ -> "5a 38 38 52 01 00 00 00 1d 00 00 00 44 4b 65 79 00 00 00 00 00 0a 00 00 00 00 00 00 00" Z 8 8 R D k e y Presumably key data "5a 38 38 52 01 00 00 00 1d 00 00 00 44 4b 65 79 00 00 00 00 03 61 00 00 00 00 00 00 00"
  3. Well the problem with OSC is, from the commands provided in this documentation file it appears to me as if it can only receive these: Cues Playbacks Macros, Grandmaster & Blackout It could be that I just overlooked the file but on the FLX S24 OSC does not seem to have individual colour control that is not pre-programmed
  4. Hi, I was just in general interested how the whole ZerOS and the remote apps etc. work together and wether I could remotely for example via my own "code" send data / packets to change colours, intensity etc. So I looked into that a bit but I was wondering if there is a easier method to do so. I thought maybe the Monitor App has an easy API to reverse Engineer but from what I’ve observed when inspecting network traffic between the ZerOS Monitor App and the FLX: The Monitor app doesn’t appear to have it's own UI, as it's just displaying the raw image stream sent from the console (please correct me if I’m mistaken). The FLX sends this UI as raw image data, and in return, the app sends mouse coordinates (x, y) and state changes (down, up, move) back to the console, which then updates the display. In theory, it looks like I could send raw hex strings (e.g. "1 enter @100 enter") but I really hope theres an easier way I overlooked. So my main question is: Is there an easier or officially supported way to remotely control the FLX (S24) to change colours or intensity via the standard DMX universe — ideally by sending packets directly over Ethernet from custom code? I’ve checked out a few options, but they don’t seem to fit: Triggers: Only seem to fire cues/playbacks, not direct channel control. KiNET: Doesn’t appear compatible with my setup. Philips Hue: Works only with Hue devices, as far as I can tell. Any advice or insight would be really appreciated! Thanks in advance!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.