(1222-014) BUG/IMPROVEMENT - MIDI mappings inheritance

[PolDavril]

Hi,

This is not really a bug, rather an inconvenience and a possible improvement.

When two (or more) fixtures of the same model (same ssl2) are not added together at the same time but in separate patch actions, the new fixtures do not inherite the defined MIDI mappings.

In this example, a first fixture is patched and MIDI mappings are set.
Afterwards, a second unit is patched.

In the fixture tab (led-par64), the MIDI indicators are lit for all fixtures (thus for the 2nd also, as shown in the screenshot below), although the mapping works for the first fixture only.

Daslight-1222-014-1.jpg (29.12 KiB) Viewed 3897 times

In the General tab, there is no automatic mapping for the 2nd fixture.

Daslight-1222-014-2.jpg (41.17 KiB) Viewed 3897 times

The MIDI dialog displays channels for both fixtures, though.

Daslight-1222-014-3.jpg (23.9 KiB) Viewed 3897 times

The drawback of this issue is that the MIDI dialog must be reopened for each fader, for just pressing enter to update the list of channels.

[TomHat]

Hello Pol,

As you said, this is not a bug. The important thing to understand is that mappings are always made on the channels, not on the faders. If you map channels through family fader, it'll apply this mapping to the chosen channels.
If then you add a new fixture to the same family, you cannot expect this new fixture to take the mapping as family faders don't really keep track of channel mapping.

For the midi dialog, I think it helps better as it works now than it would is it only showed current state. In the situation you mentionned here, the dialog could show :
- everything disabled (because all beams don't have the same state)
- Midi enabled, but only channel 1 written (because fixture 1 only is already mapped)

What I can do though is to only show in the dialog channels belonging to selected beams.

Regards,