Q Light Controller+

Hi all.
Already in another place in the forum was commented on a feature similar or equal to the one I propose.
I think that if we could assign external midi controls to the dmx channels of the fixtures, we would get much better performance and faster a show could be created ... (in many cases the time is very limited)

The form that I understand would be the correct would be that these external controls affect all fixtures selected by "groups of fixtures" or manual selection .....

I do not know very well how this feature could fit in qlc + 5, in qlc + 4 a non ideal form but if interesting to do so would be having external control over a group of channels and assign it as a scene in a VC slider ... (the serious flaw that always affects the same fixtures with no possibility to select / deselect live fixture)

The use case would be similar to that of large lighting consoles:

-I call a group of fixtures "group 1"
-I turn on light with an external slider
-move pan / tilt with a trackball, or wheels or slider ....
-recorrect the positions individually by selecting / deselecting the fixtures that interest you
- Record a scene and assign it to an external slider or just save it.

I guess it would be to create the way to assign midi controls to attributes that affect "everything called pan" or "tilt" or Dimmer ... only to the selected fixtures ....

I hope to have explained myself well and that google help me with the translation .....

Well seen, at the moment of having to create a lot of scenes with this method it would be very quick to create them and it would be a lot of time in general ....

What do you think?
a greeting

I already thought about this like 3 years ago. I've got a spreadsheet for QLC+ 5 features too
The idea is to automap a connected external controller to various controls of the UI.
There is one problem though.
QLC+ 5 contexts can be detached. So you can have editing on one monitor/window and the Virtual Console (with sliders and everything) on another monitor/window.
In that situation, when you move a fader, what should QLC+ do ?
I'm pretty sure some people would like to control editing, while other will say VC has precedence.
Discussion open.

i'Ve already done this question some day ago. i don't understand very well where problem is.Widget for pan tilt in the programmer(and so on)simply trigger a variable value i think. an external controller should trigger this value too.when i've done i save my scene and link it into a VC plugin, that will be triggered with another note from the midi device , or, if is that the problem by another input device

mcallegari wrote: ↑Thu Dec 13, 2018 9:50 pm QLC+ 5 contexts can be detached. So you can have editing on one monitor/window and the Virtual Console (with sliders and everything) on another monitor/window.
In that situation, when you move a fader, what should QLC+ do ?

I understand that if you assign an external control to a parameter in edition, only and always must affect this parameter to the fixtures or group selected.
External VC controls will only affect VC, always,

Who to give priority to? I understand that changes in editing take precedence over VC .....
As each use case is very unique, Some consoles have 2 ways of operating, a normal mode (only spears scenes, there is no access to live programming) and a very useful "take over" mode, you can modify live parameters using palettes and groups of fixtures .......

If you want to share an external controller to control editing parameters and control VC,
At the moment of having two monitors, the normal use would be:
There is no fixture or selected fixture group:
The external control controls VC.

Select a fixture or group of fixture that contains the parameter that is assigned an external control, this switches from VC to Window of edition .... And only acts on the edition .....

Is my thought......

Anyway, I think it would be a great addition ...