Open Deanbau opened 6 years ago
First version of the chamsys module is done with the playback Actions, I will make more actions after this have been tested.
Where/how can we test it? I am willing to test and review this, can test on laptop and on MQ100 console. Edit: Found it, I can test it tomorrow evening because it seems like you have to go out demo mode and I don't have my dongle/consoles with me as the moment :( It doesn't work in magicQ demo mode.
Also any command on this, i see it stops at PB10, can't you make it go on? On my console with wings i go above PB40 and i know from other software that it works, if you could remove this limit i can test it. Other commands requesting triggering execute windows, triggering macro's. Ooh and a special request, this one is going to be harder, don't know if it's possible. Triggering a flat button as long as i press the stream deck button and when i release the button releasing the flash, is that possible in the future (no pressure for this).
I can’t get the magicq module to work? It is out of demo, tried local and remote. Checked firewall ip adres, subnet ranges, i could ping the remote device, chamsys accepts network packages, ip adress in chamsys was correct, port was set up correct in chamsys and bitfocus, and chamsys is out of demo mode. I think i tried and checked everything to get it to work. When i open widget designer on the computer i am able to trigger magicq (only this time widget designer runs on parallels).
We see nothing wrong in the msg sendt, but I must admit that my knowledge of Chamsys is limited at best, we have a sales guy here at the company which is a a chamsys user i will get him to have a look at it :-)
Chamsys does have a good helpdesk, send them a mail, chances are big they want to help you.
I just had an idea, packages send with companion can they be read with wireshark on the receiving computer (with chamsys)? If this is the case i can try to see the difference in the package when received by companion or by W.D. so we can compare the code or doesn't it work like that? Probably it is not that simple i guess, but if you think it could work i can spend some time on this.
https://m.youtube.com/watch?feature=youtu.be&v=2OSmBFcCCik Maybe this can be helpfull?
Which port are you using for the osc on the magicQ
I will make another module for the Chamsys desks using TCP or UDP but i think we should get this working as well as this can be used in multidesk environments as well. I'll borrow a dongle so i can activate the Software and find out what is going on. Be aware that the companion server uses port 8000 as default, and the default RX OSC port on chamsys is also 8000 so if they are running on the same machine you need to change the port on one of them (i Suggest Changing the Chamsys).
Ok good news, i can confirm it does work on a mq100 and on my macbook (no demo mode). I think there must have be a poblems with the ports indeed, don’t remember the exact set-up i tested it with. 2 small bugs, bdo on/off are switched. And when releasing a fader and then triggering the flash i first have to set the flash to off before i can set it to activate.
OK I will swap the DBO actions when it comes to the Flash function We really need an Up action handler for the buttons before that will work as expected, I know it's on list of enhancements but unsure of when it will be done
These are the commands to trigger execute buttons/faders in magicq.
https://secure.chamsys.co.uk/help/documentation/magicq/ch40.html
exec/
/exec/
(optional) one of following
no arguments = activate button/fader
0 = relase button/fader; lower encoder
1 = activate button/fader; raise encoder
float between 0.0 and 1.0 = set fader level
int between 0 and 100 = set fader level
Control button, fader or encoder in execute window
Is support for execute window items planned or are you thinking to only support playback triggering?
Per this is great. Thx. To make it super flexible, it would be interesting to integrate MACRO triggering. One could program the macros on the MagicQ platform as required and launch them via companion.
Hello, I'm not sure if this is exactly the correct place to post this. But the Chamsys QuickQ is now controllable via UDP as of 5.1 firmware that just came out. @PerRoine would you be willing to put together a module for companion? Manual for the QuickQ can be found here: https://chamsyslighting.com/pages/quickq-downloads but I also pulled the important page out and pasted it here:
3.11 Ethernet Remote Control QuickQ consoles feature a simple remote control protocol allowing them to be controlled from 3rd party control systems over a network. When Ethernet Remote Control is switched on in the Network Settings window of the console will listen for UDP messages on port 6553. The port number is fixed and cannot be changed. The Ethernet Remote Control messages do not require any heading. Each command is an ASCII string with a number followed by a letter. The supported commands are: A Activate Playback R Release Playback T Activate Playback at 100% U Release Playback X Toggle 10Scene button A number is pre-fixed before the command to denote the item that the command will control. For example sending "10A" will activate Playback 10, while sending "2X" will toggle the second button of the 10Scene panel.
Thanks for all the amazing job. Now with new StreamDeck + and rotational encoders, and plus MagicQ has updated with more functions, is there any chance we can see mode stuff added into the module. Like I want to control rotation encoder in Exec which I cannot find in companion. Thanks in advance. @PerRoine and whoever contributed to that module - thanks a lot.
Describe the feature Control of Chamsys consoles via - thankfully - OSC!
Is this platform dependent (windows, mac, ..)? No
If documentation is required to implement, do you know where to find it? https://secure.chamsys.co.uk/help/documentation/magicq/ch40.html
Usecases Chamsys desk control!