Updating the mainwindow.

Johan SÃ¶derberg · Post by **Johan SÃ¶derberg** » Mon Sep 03, 2012 5:05 am

I made a little experiment:

Since LXConsole has no built in ability to fade in and out chase effects I decided to build some looped chase effects in Qlab. These loops keep repeating a midi controlchange and the midi velocity is controlled over time according to a drawn curve showing its waveshape.

It works just great if LXConsole is set to run submasters triggered according to the very fast changing midi signals coming from Qlab.

But if I let the same note control only one channel it quickly chokes LXConsole and in the mainwindow I dont see the channelvalue changing rapidly in accordance to the sent waveshape. Instead I soon see nothing but a spinning colourful umbrella and LXConsole will need some time to catch up before its usable again.

But in both scenarios: submaster or channel, It works fine to the DMX output. The chase loops can be seen running live perfectly.
Only not in the "Mainwindow" when set to trigger a certain channel.

What might cause this behaviour?
It shows a whole group of fast changing channels and has no problem updating the window with them all, but when its only one channel and its rapid changes to show, then it chokes up after a few seconds!

Johan SÃ¶derberg · Post by **Johan SÃ¶derberg** » Mon Sep 03, 2012 7:43 am

Heres a picture of that loop done in Qlab.

Post by **admin** » Tue Sep 04, 2012 11:03 pm

Connecting a MIDI message to a command is exactly like typing the command into the command line. Imagine sending a whole bunch of these messages to a fast typist. Even the best would get overwhelmed.

The use of the SUB- form of the MIDI/OSC action connects directly to the output and that does not require the interface to keep up.

This is mentioned in the help but the reason for it is not explained.