Simple Desk questions

Patrick Rea · Sun Jan 04, 2015 5:15 am

Couple of quick questions regarding the use of the simple desk in comparison to a standard theatre console. Most of these questions relate to the last desk that I used, a Strand Lightboard M.

1) Is there any way to have direct access to a fader and it's level from the keyboard? On the Lightboard M, you could press a dedicated key to put a selection box on the screen. You then keyed in the channel you wanted to control and put a "+" between multiple channel numbers or use "-" to select a range. You could then directly enter a percentage value (0-100) for the selected channel(s) using the keypad and then press enter for the channels to react. This allowed for much quicker entry for large numbers of channels and meant that you could program the basics of an entire show without touching a single fader. As we had 72 channels of dimming but only a 24 fader desk, it meant you didn't have to flip pages on the faders.

2) A "Go To" shortcut combination, ie."CTRL+G" followed by the cue number to bring a cue up without waiting for fade times to run. This would just put your selected levels up on the screen for editing purposes. If you want to see how a cue runs you would "GoTo" the cue before.

3) Shortcuts combinations. Maybe CTRL-SHIFT-R to reset all channels to zero. CTRL-SHIFT-P to switch from design to playback and vice versa. In playback mode, assign the number keys across the top to allow you to switch cue stacks or to solo/flash a channel grou.

If I knew enough about coding I might try to do these on my own. But I don't so I thought I might throw these out for anyone else.

Thanks

Jano Svitok · Mon Jan 05, 2015 8:12 am

This pull request contains some of the functionality: https://github.com/mcallegari/qlcplus/pull/280, but there was no time yet to integrate it to main branch. You are welcome to try it if you can compile from sources. If you do, please report feedback (here is a good place).

Patrick Rea · Mon Jan 05, 2015 3:10 pm

I wish I could compile easily. The machine I have to dedicate to QLC+ is an old Thinkpad R40 with only 512mb of ram. Compiling the first time took a few hours on it. I'll see if I can't kick loose another machine which is a dual core Dell desktop. Unfortunately, it's currently my database server for Digikam and a few other apps.

Jano Svitok · Mon Jan 05, 2015 3:24 pm

Patrick, what's your OS (linux?) distribution & version?

Patrick Rea · Wed Jan 07, 2015 3:38 pm

Ubuntu 14.04LTS. This is a clean OS, no extraneous stuff on it except for the packages required to build QLC+.

Jano Svitok · Wed Jan 07, 2015 4:05 pm

Patrick,

do you have 32bit or 64bit distro? For 64bit I can compile the debs for you, for 32bit I don't think so...

Patrick Rea · Thu Jan 08, 2015 3:34 pm

32bit version. I'll see if I can't figure out a way to grab and compile your version. First step will be to grab GIT.

Thanks!

Patrick Rea · Fri Jan 16, 2015 4:40 pm

Okay. Stupid question time. I installed git and pulled in the source for QLC+. How do I get the specific version above?

david garyga · Mon Jan 19, 2015 9:50 am

First, add the remote containing the wanted branch:

> git remote add kripton git@github.com:kripton/qlcplus

Then fetch the remote:

> git fetch kripton

And then you can try to merge the remote branch and resolve conflicts (git merge kripton/dmxkeypad), or (more simple) checkout the remote branch to test it (git checkout -b dmxkeypad kripton/dmxkeypad)