LXSeries Lighting Software

is there a function in midi preference to avoid that a midi fader used to control a submaster take precedence on sub level?
I mean that if the sub level on lx console is not 0 a midi fader take control of dmx level only when is value is higher than apps's fader level.

tank you!

Perhaps the way to do this would be with two identical subs, one controlled by fader and the other controlled by MIDI. The highest level of either would get added to the current output.

but when you go back to zero with midi fader the level will remain at the level of the second sub..
there's no way to grab app's level with midi fader?

So, what you want is a MIDI action that controls a sub, but not until the percentage value is the same or greater than the sub's level?

When does this MIDI action release control?

Is it a one-shot thing? So, the MIDI action is not controlling the sub when a file is opened and then as soon as the level condition is met, it remains in control of that sub forever?

i think the english translation of this is "pickup mode", i mean to avoid that if midi fader is not motorized, if a sub is reaised on the app and after the corresponding midi fader is moved levels don't jump down to midi level but stays on app level until midi reach the same level and take control of the sub as usually does.

The principal is clear, it is the details. How about if a MIDI control is higher than the sub level. A similar thing would happen, when the MIDI control moved, the sub level would jump up to the MIDI level.

It may not be feasible for the levels to match exactly for the MIDI to "pick up" the control of the sub. It may need to be just close.

But there's also the question of when and how the initial condition is established. Is this when MIDI is first enabled?

And, is there a condition, other than LXConsole quitting when the control is released?

Finally Faders control subs and could be thought of as subs. But there is a difference between faders being controlled by MIDI and control of a sub that is defined in the MIDI actions of the setup window. Which of these are you asking about?