I’m using beam with 8 astera luna bulbs. DMX profile 90. Tag 10 controls all lights. They are blue. Tag 11 controls one light. The moment I add tag 11 to a new generic fixture it turns that light green. Even when I have midi info sending to tag 10, the single tag 11 light’s green is always merged with tag 10’s info. Setting tag 11 values to 0 has no effect. Having no midi info on tag 11’s track also has no effect. How can I make the active hue color midi information in tag 10 always take priority? Thank you.
When a fixture is controlled by multiple devices, either via a single tag or multiple different tags, the values of its modulation parameters are merged according to the merge modes specified for its parameters.
As you can see if you open the profile for your fixture in the fixture editor, weighted average is used for the hue modulation:
You can read about different merge modes here.
However, using another merge mode is probably not the solution here.
You can make parameter values for a given device/tag take priority whenever they are playing a note by placing multiple Beam devices controlling the same set of fixtures into a Drum Rack - as explained here.
However, you will need to re-map the Drum Rack according to the Trigger Notes defined in the Fixture Patch. Also, this approach only applies when working with notes, static parameters will still be merged as usual.
Alternatively, you can also control hue of each your 8 fixtures within a tag individually by setting 8 of the Generic’s parameter slots to hue - then each parameter will address 1 of the 8 fixtures:
You can read about this Generic feature here.
Thank you for the quick reply! This is incredibly helpful and I’ll explore all of it. I’m also finding that automating the volume parameter is a primitive work around. IE fade down the 8 lights channel, fade up the single light channel.
1 Like