First I'm happy that development is going on. I try to describe a bit my user expierences qlc and my needs, maybe its of interest.
I used to work with qlc since a while mostly for smaller theatre or dance performances. Like most Software Controllers QLC(+) follows "rock'n'roll" logic in lighting. This workflow differs from working in theatre.
The problem of QLC was, that the Virtual Console was useless for my case of use, because there was no possiblity to record the output which I created in the Virtual Console by pushing faders into a scene. Creating a Scene with the Functions Editor by having 48 or more channels was totally time consuming. It cost me 5 to 10 times more to create a Scene or doing corrections than using a physical lighting desk. If you have a guest performance and limited time its a absolut no go. So I patched qlc and added a button for that in the Virtual Console [record current output into new scene]. I know, it breaks the internal logic of qlc(+) but made my life a lot easier.
I normally "rebuild" a conventional lighting desk with 48 hardware faders and a bunch submasters (groups) in the virtual console to make my scene presets there and put them into a cuelist (boring theatre workflow
). The only thing what's left to make me really happy is the ability to capture channels through the Virtual Console, if I have to lower the intensity of a lamp in a scene during a show or a runthrough or while doing corrections.It would be cool if the further development could consider also the conventional light needs. The most important thing or need is to keep on schedule or beeing faster, but you all know that
The channel grouping I discovered today will help a lot for that.Anyway it's a great piece of software.
offtools.