Mass MIDI mapping and Virtual Console colour palette.
Posted: Thu Oct 24, 2019 3:29 am
Hi all!
I recently used QLC+ 4 on my first gig in conjunction with my school. Overall it's a great piece of software, but here are two things that I would have liked that would have made my life a whole lot easier:
A easy to use colour palette option.
My show file was set up in such a way that I could press a button in a row on my MIDI controller (Novation Launchpad Mini), and have the group of lights corresponding to that row, change to that colour. Pretty much like Christian Jackson's colour picker on grandMA2.
Christian Jackson's colour picker on MA2.
I had my version setup using coloured buttons and solo frames in the virtual console, each button mapped to the corresponding MIDI input note, but for only three fixture groups, with about 5 colours each, took me hours to get working. Having to create a scene function for every colour, then assign to the button etc. So I propose this:
A simple button grid function, like what's already available, but with the option to assign each row (or column for that matter) to a group of fixtures, and either set each row (again, or column) to any colour, or to have a gradient of colours applied across the entire pad. This would have been an amazing time saver if I had it.
Into my second idea/suggestion:
Mass MIDI control mapping.
This one is really simple. For every button on my colour setup, I had to open each buttons preferences, click "Auto Detect" on the Input section, press my MIDI button, turn off auto-detect, and exit the window, moving onto the next button. I propose an option, that when you select a bunch of elements in the Virtual Console (that's another thing actually, we need drag and drop selection in the virtual console), the setting would one by one, ask for a MIDI note to be pressed, and once a note is pressed, it simply asks for the next note, for the next element. If you don't want to assign a MIDI input, just hit the escape key, and it will continue on.
Those are my suggestions.
I tried my best to not make this sound like a rant, I absolutely love the software, but these are just some ideas I had while sitting there programming on a time-sensitive schedule.
I would love to hear any ideas about this that the community has.
Thanks!
- Alex
I recently used QLC+ 4 on my first gig in conjunction with my school. Overall it's a great piece of software, but here are two things that I would have liked that would have made my life a whole lot easier:
A easy to use colour palette option.
My show file was set up in such a way that I could press a button in a row on my MIDI controller (Novation Launchpad Mini), and have the group of lights corresponding to that row, change to that colour. Pretty much like Christian Jackson's colour picker on grandMA2.
Christian Jackson's colour picker on MA2.
I had my version setup using coloured buttons and solo frames in the virtual console, each button mapped to the corresponding MIDI input note, but for only three fixture groups, with about 5 colours each, took me hours to get working. Having to create a scene function for every colour, then assign to the button etc. So I propose this:
A simple button grid function, like what's already available, but with the option to assign each row (or column for that matter) to a group of fixtures, and either set each row (again, or column) to any colour, or to have a gradient of colours applied across the entire pad. This would have been an amazing time saver if I had it.
Into my second idea/suggestion:
Mass MIDI control mapping.
This one is really simple. For every button on my colour setup, I had to open each buttons preferences, click "Auto Detect" on the Input section, press my MIDI button, turn off auto-detect, and exit the window, moving onto the next button. I propose an option, that when you select a bunch of elements in the Virtual Console (that's another thing actually, we need drag and drop selection in the virtual console), the setting would one by one, ask for a MIDI note to be pressed, and once a note is pressed, it simply asks for the next note, for the next element. If you don't want to assign a MIDI input, just hit the escape key, and it will continue on.
Those are my suggestions.
I tried my best to not make this sound like a rant, I absolutely love the software, but these are just some ideas I had while sitting there programming on a time-sensitive schedule.
I would love to hear any ideas about this that the community has.
Thanks!
- Alex