Some time age I experienced strange UI issues when running MagicQ on Ubuntu Linux. The UI was displayed very big and did not scale correctly. This made the whole software unusable as you can see in the following example of the programmer window.
It seemed like the issue was linked to the introduction of high DPI support in MagicQ. Lowering the screen resolution solved the problem, but was no serious long term solution. After a frustrating time of troubleshooting I finally found the root of the problem. It looks like the scaling feature of Qt messes up the UI scaling when using small displays with high resolutions (like my 12,5″ display with 1920x1080px). After reading through some bug reports on github I found out, that deactivating the scaling by using the environment variable QT_AUTO_SCREEN_SCALE_FACTOR=0 fixes the issue.
To solve the issues permanently, I added the line export QT_AUTO_SCREEN_SCALE_FACTOR=0 to the ./runmagicq.sh file in the /opt/magicq folder. You can also use the solution non permanently by starting MagicQ from the linux console with the command QT_SCREEN_SCALE_FACTOR=0 /opt/magicq/runmagicq.sh
Note: I reported the bug to Chamsys. As I found the solution, I also reported my solution.
Update (5th October 2018): With version 126.96.36.199, high DPI scaling is turned off by default on MagicQ versions of Ubuntu. See the Change Log on the official Chamsys page for details.
Since my AKAI pad linked to a Chamsys MQ60 console received some attention on tour, I decided to write down a detailed description. In this blog post I specify my Chamsys extension setup which consists of an AKAI MPD26 and a Raspberry Pi 3 model B. This guide hopefully helps other interested people to build a similar setup.
The most apparent part in my setup is the AKAI MPD with it’s pads, faders and knobs which can all be used to trigger playbacks or executers on the console. The Pi is used to convert the AKAIs MIDI output to DMX signals which are relayed to the console via Art-Net. The “converting” is done by the free software QLC+ by Massimo Callegari. QLC+ is configured to take the AKAIs MIDI input to control dimmer channels which are played out via Art-Net. The consoles Art-Net in feature is used to trigger the wing playbacks on the console.
How it all started
The whole thing stared, when I used the consoles Art-Net in feature to link the good old Lightcommander 12/2 to the console via an enttec open DMX Ethernet interface. My intention was to get some more faders for stuff like front lights, fog, haze, fans etc. Even though the setup lacked the play/pause/select buttons of the Chamsys wing, it worked out pretty good. The workflow was nice: program things, click the record button, press the flash button of the destination fader on the LC and that’s it.
Choosing the AKAI MPD26
The Lightcommander with it’s good build quality was a nice extension, but it did not exactly fit my needs. I really like to trigger effects like strobes, blinders and ACLs etc. using hardware buttons. This is why the LCs ratio between faders and flash buttons did not suit me well. Another downside was the size of the LC. I really like the compact size of the MQ60 console which is why putting a second “desk” with almost the same width next to the Chamsys only to get some more faders and flash buttons did not align with my concept of a compact and minimal setup. While digging through the huge amount of MIDI interfaces, AKAIs APC40 came to my mind which then led me to the MPD series. I finally choose the discontinued MDP26 due to it’s compact size and the nice amount of 16 pads, 6 faders and 6 knobs. The fact that the MPD is a MIDI device and such devices can’t easily be used to control Chamsys playbacks didn’t bother me. The idea of converting MIDI to Art-Net was in my mind for some time and therefore, buying the MPD26 would be a nice point to start.
For a simple proof of concept, I installed QLC+ on my Linux laptop computer, connected the MPD26 via USB and configured QLC+ to accept the MIDI signals as controls. To forward the Art-Net packages to the console, I connected laptop and console via network. Art-Net in was already configured due to my prior LC12/2 + enttec ODE setup. After configuring QLC+ to use the right Art-Net universe and channels the setup surprisingly worked straightforward. I have to admit, that I didn’t expect the the whole thing to work out after such a short time 😉 After this success, I decided to take it to the next level by porting the MIDI/Art-Net part to the very handy Raspberry Pi 3. In the following sections, I will give a detailed description of the Pi and Chamsys configuration.
Raspberry Pi setup and installation
For my setup I use a Raspberry Pi 3 model B with the Raspbian operating system installed. At this point, I won’t describe the setup of Raspbian any further since it’s already well documented. After the operating system is installed, QLC+ needs to be installed on the Pi. This can be done the easy way by using the QLC+ Raspberry installation files which can be obtained on the official page for a donation of 15€. I went the free, but more complex way and built the software from source. I won’t document the building process at this point since this would go beyond the scope of this article. After QLC+ is installed, the IP address of the Pi needs to be configured. In my case, I used 188.8.131.52 as address for the Pi. As you might already imagine, I won’t document the IP configuration here since it’s also already well documented.
Now that the system is installed and so far configured, QLC+ needs to be configured. We start with the Art-Net configuration. This can be done in the Inputs/Outputs tab. At first, one of the QLC+ internal universes needs to be selected. This can be done in the left column of the window. I used universe 1. After the universe is selected, the right column is used to configure the Input and Output mapping. To configure the universe to be played out via Art-Net the “Output” checkbox of the Device with IP address 184.108.40.206 needs to be checked on the right window column. After that, the outputs Art-Net universe can be configured by clicking the tool button on the right side. In my case, I choose Art-Net universe 42.
At this point, the Pi and the console can be liked with a CAT cable and QLC+ should be visible as a node on the Chamsys (Setup → DMX I/O → Net manager→ View Art-Net).
Now, the AKAI pad needs to be configured as an input device. After the pad is connected to the Pi via USB, QLC+ should list the MIDI device in the right column of the Inputs/Outputs window. I experienced that QLC+ doesn’t recognize new devices while running. So the MIDI device needs to be connected before QLC+ starts up (otherwise, a restart of QLC+ is necessary). After the MIDI pad is selected as an input device, a small joystick icon should be displayed in the corresponding universe row in the left column of the Inputs/Outputs windows whenever a pad/fader/knob on the MIDI device is pressed. The icon indicates an incoming MIDI signal.
In the next step, QLC+ will be configured to control dimmer channels via MIDI. First of all, the dimmer channels need to be added in the fixture tab of QLC+. Using the green plus button in the menu bar I patched a generic dimmer at universe 1, address 1 with 28 channels (6 faders + 6 knobs + 16 pads = 28 channels). Now that the channels are patched, the controllers of the MPD can be assigned to a dimmer channel. I used the virtual console tab and created 12 faders, one for each knob and fader of the MPD. The virtual faders of QLC can be configured in the widget properties window (right click on the fader → Widget Properties). In the general tab, the MIDI input can be configured by using the auto detect button in the external input area. After the activation of auto detect, the fader/knob on the MPD needs to be moved from min to max to be assigned. The Input universe and channel values will be filled immediately after the MIDI input is recognized.
Now the corresponding dimmer channel can be configured in the level tab by checking the box of the channel number.
This needs to be done once for each fader/knob. For the pads I created buttons in the virtual console tab. Unfortunately, QLC+ only allows the buttons to act like flash buttons when they are configured to use scenes. This means, that for each channel controlled by a pad, a scene with the corresponding channel set to 255 needs to be created. The creation of scenes is documented here. At this point, the configuration of QLC+ is completed. I strongly recommend to create a backup of the configuration (in QLC+ it’s called workspace). Please remember that the the green play button in the upper right corner of the QLC+ windows must be activated in order to use the software to control the Art-Net universes.
Configuration of the Chamsys console
In the last step, the consoles Art-Net in feature is configured. The Setup → DMX I/O menu needs to be configured as follows.
Output on universe 1 is disabled, only input via Art-Net is enabled. The nodes IP is configured as unicast IP (but as QLC+ broadcasts the Art-Net packages, it’s strictly speaking not required). It’s necessary to use universe 1 of the console for Art-Net in since controlling Playbacks is only possible using universe 1. That’s also why I moved the consoles four physical DMX Outputs to the internal universes 2-5. Now that the basic DMX I/O configuration is done, the inputs configuration for the wing playbacks are next in line. The wing configuration can be entered by clicking Setup → View System → View Wings. In this window, PB Wing 1 and 2 need to be changed to DMX Input. Furthermore the channels have to be configured regarding the following screenshot in order to be linked with the playbacks.
After that, the setup should finally work. This can be tested by arranging channels in the programmer, hitting the record key and then hitting a pad or moving a fader up to full on the MIDI Controller. At this point, the yellow light on the consoles record button should turn off which indicates that the cue is recorded. The recorded playback should also be visible in the playback window (by hitting the Playback button on the console). This is how my playback window with some cues assigned to the MIDI controller looks like.
Improvements on the Pi
Since I run the Pi completely headless (without monitor, mouse and keyboard), QLC+ has to start up automatically after the system has booted. On Linux systems, this can be achieved using init scripts. Calling QLC+ with the -p parameter starts the application straight into the operation mode (remember the green play icon in the upper right corner) and the -o parameter helps to load the workspace file with the configuration and patching done before.
Avoiding Art-Net conflicts
Since Every Art-Net universe on the Chamsys console can only be used for input OR output, I choose universe 42 for the Art-Net coming from the Pi. I did this because Art-Net universes with lower numbers are more likely to be used on venues and festivals to control fixtures. Using Art-Net universe 1 for the MIDI controllers Art-Net in signal would make it impossible to play out a DMX signal on the same Art-Net universe. Controlling fixtures attached to a node which uses Art-Net universe 1 would therefore not be possible.
Famous last words
Hopefully, this article is helpful for some of you lighting and Chamsys-loving people. I’m just a human, so forgive me if there is anything missing or unclear (or just leave me a comment and I will have a look…). Until today, I used the my setup on about 30 shows and it always worked like a charm. But this is my experience and I can’t guarantee anything. Oh, and please consider a donation to the QLC+ project if your setup works and you like it. QLC+ is the reason this whole thing is possible!
Future posts regarding this MIDI setup could be about reliability measurements and backups for the whole setup itself. I also have not used the after touch features of the MPDs pads to control the fade out behavior, this might also be interesting.