Cloning a colour palette/colour onto other lights (LEDs)

[kgallen]

So we know that currently on ZerOS, if we programme a (colour) palette for light type "A" we can't apply it to light type "B".

What's the easiest/most reliable way to update a (user) type "A" colour palette so it can be applied to light type "B" when doing prep offsite - i.e. all of the fixtures to be used aren't rigged/attached/operational.

So I've devised and programmed some (LED) colours using light type "A". But there will be more (LED) fixtures of a different type (several types) that I'll also want to apply the "same" colour to - accepting it could be a different shade initially - until I actually have the lights rigged and I can see how they respond to the palette, when I can tweak it for those lights and UPDATE.

Assuming the lights are in the showfile patch (albeit not attached to DMX), how can I update the palette in this prep?

The only thing I can think of is:

1. Select both type "A" and type "B" on the desk (and set non-zero intensity)
2. Apply the colour palette (that will only currently work for type "A")
3. "nudge" one of the colour encoders - will this cause the other RGBW values to snap onto the type "B" lights?
4. UPDATE the colour palette (so it now has data for type "A" and type "B" lights)

The crux is step 3. What's the best thing to do here without having to redefine the entire colour "blind" for the type "B" fixtures?

The assumption is that the (colour) palette was defined on an RGBW device (say an LED mover) and will need to be applied to other comparable RGBW devices (say LED PARs).

Thanks!

Regards, Kevin

[Edward Z88]

Hi @kgallen

21 minutes ago, kgallen said:

What's the easiest/most reliable way to update a (user) type "A" colour palette so it can be applied to light type "B" when doing prep offsite - i.e. all of the fixtures to be used aren't rigged/attached/operational.

If a palette has been recorded with one fixture type, and you need it to work for another fixture type, it is a case of tagging the new fixture type, and updating the palette, so that the palette now has information for the new fixture type too.

21 minutes ago, kgallen said:

The only thing I can think of is:

1. Select both type "A" and type "B" on the desk (and set non-zero intensity)
2. Apply the colour palette (that will only currently work for type "A")
3. "nudge" one of the colour encoders - will this cause the other RGBW values to snap onto the type "B" lights?
4. UPDATE the colour palette (so it now has data for type "A" and type "B" lights)

The crux is step 3. What's the best thing to do here without having to redefine the entire colour "blind" for the type "B" fixtures?

This process makes sense if you want to apply one fixture's colour values to another fixture type, and then update the palette.

The order of selection is important. You must select type A first. That way, when you nudge the Red encoder for example, the Red parameter of all selected fixtures will snap to the absolute value of the first selected fixture. You can then nudge Green, Blue and White too, so that if the type B fixtures have these parameters too, they will snap to match the first selected fixture's values. Once all the required fixtures have tagged colour parameters, you can then update the palette. To do this tap UPDATE, and tap the palette onscreen, or use the syntax UPDATE COLOUR x ENTER. There's no need to add intensity to the fixtures when doing this, but if you have them connected you'll probably want to so you can see what you're doing!

Hope this helps,

Edward

[kgallen]

Hi Edward,

Thanks for taking the time to reply late today, I’ll be having a play with this later.

So from your reply I’m guessing there is no easier way to tag all colour parameters than nudging every colour encoder - something like Shift+Colour or HOME which is a trick we use for REMOVE. I realise I can’t use HOME since that will not only tag all parameters but HOME them too!

Thanks again!

Kevin

[Jon Hole]

7 hours ago, kgallen said:

currently on ZerOS, if we programme a (colour) palette for light type "A" we can't apply it to light type "B".

This sounds like something that should go into the ZerOS request thread 🙂

[Davidmk]

6 hours ago, Jon Hole said:

This sounds like something that should go into the ZerOS request thread

Absolutely! Please.

[kgallen]

10 hours ago, Jon Hole said:

This sounds like something that should go into the ZerOS request thread 🙂

I have asked before 😁. But you’re right it’s probably not on that list but you might find a ZOS for it already!

[Edward Z88]

 Hi Kevin,

15 hours ago, kgallen said:

So from your reply I’m guessing there is no easier way to tag all colour parameters than nudging every colour encoder

To tag all colour parameters, you can press and hold CLEAR and tap COLOUR. However, this simply tags the parameters. It will not change their current values.

17 hours ago, kgallen said:

currently on ZerOS, if we programme a (colour) palette for light type "A" we can't apply it to light type "B".

11 minutes ago, kgallen said:

I have asked before 😁. But you’re right it’s probably not on that list but you might find a ZOS for it already!

The ability to use a recorded palette for other fixture types not included in the palette, is logged on our system as reference number ZOS-3718. I have logged the thoughts from this thread.

Let us know if you have any questions.

Edward

[kgallen]

Hi Edward,

44 minutes ago, Edward Z88 said:

To tag all colour parameters, you can press and hold CLEAR and tap COLOUR. However, this simply tags the parameters. It will not change their current values.

From how you word this above I'm concluding that tagging is not enough to get the data onto the type "B" fixtures, it really is necessary to nudge each colour to make the absolute values snap onto all selected fixtures?

Thanks! Kevin

[Edward Z88]

Hi Kevin,

6 minutes ago, kgallen said:

From how you word this above I'm concluding that tagging is not enough to get the data onto the type "B" fixtures, it really is necessary to nudge each colour to make the absolute values snap onto all selected fixtures?

If you "Tag" an attribute (CLEAR + COLOUR), this simply means the attribute's parameters will get recorded in their current values.

To apply the first selected fixture's parameter values to the rest of the selected fixtures, you then need to nudge the encoders. This process automatically tags the colour parameters.

Edward