Weird behaviour in override buttons

[Civette]

Hi all,

I noticed a weird behaviour in my override buttons. When I activate some ( not all ) some others are deactivated. Always the same button, whatever the sequence behind is.

The "disable all others buttons" option is properly disable ( as I can see with my eyes )

Any idea what can cause this ?

Thx,

[Spirit]

hi

this isnt strange, i think for about 99.9% you did something wrong on the SEQ you created..

look at the SEQ that causes this issue.
to see if you by accidentally added a Channel to the SEQ that should not be there..

/spirit

[jdmyers]

Right - I think if you have 2 different fixtures in the buttons - one for each button, you are OK. Pressing button 1/fixture 1 and then pressing a button 2 controlling a fixture 2 will allow both to stay on. But if anything is active within both buttons (same fixtures & channels) then HTP (highest takes precedence) takes over and cancels the previous button because its fixture has been over-ridden. If you are controlling the same fixture but NOT the same channel(s), you should also be OK.

As an example, you have an LED can that (seq 1 / button 1) sets the intensity to 255 and the RGB values to "purple" (channels 1-4, for example). You create another sequence (seq 2 / button 2) that only sets the "FX" channel (channel 5) on the same fixture to "stroby colors", while leaving all other channels unchanged ("off" in sequence editor). Now you can have the purple light on, then press button 2 to make the purple light go to stroby colors mode.

The 1st button will stay on because you didn't change any of the other channels (intensity or RGB, 1-4) but it will now be doing its internal effect. You can then turn OFF the second button and the 1st button will take its place back as the purple light.

Now you create a 3rd seq/button and make it be a intensity=255/RBG = "Cyan-ish". You can turn this one on, and it will cancel button 1 but *shouldn't* cancel button 2 (if engaged), however button 2 will still work over the top of button 3.

Hope that makes sense?

[Spirit]

pff no i dont understand it but for me they allways work perfect..

but i will add a example, as i never use Ledpars on Overridebuttons..i will use a MH with Iris.

i will make the gobo Seq like this.
GOBO OPEN = 1Step , Gobo open , Focus Gobo, Iris Open
GOBO1 = 1Step , Gobo1 , Focus Gobo, Iris Open
Iris small = 1step, Gobo Open, Focus Iris, Iris small
but as you see i did not add the Color channel to it so i can change the colors without strange results.
and with a correct light update.

as you see for the gobo Seq and Iris seq i add the same channels otherwise i can get trange result and the light doesnt turn on/off correcly.

But can you tell me whay you like to have so i can explain how to achive this..

/spirit

[Civette]

Hi chaps,

Well till now i haven't found the reason, I'll clean all sequences and restart from scratch.... and I'll see

Thx all

[buttza]

I think it is because your override button is 3 may not have a Value for the intensity channel. Strode won't work without an intensity value. If your override is missing that from the submasters then it won't work. Check the intensity slider on that submaster is up.

I too like 'Spirit' create everything with no colour values then create colour palettes in the submasters or as overrides.

I think I do understand what you are talking about. You are using stacking to build or remove your effects.

[Spirit]

hi i dont add everything to the GOBO, IRIS, Focus..
i do this otherwise the Gobo will not be sharp, or iris will also not be sharp and Gobo Should be open otherwise the Iris will not work Correct.
but these channels are somehow related to each other...

but colors (RGB/CMY/colorwheel)..can alllways be changed..same as Frost, Prism, Prism Rot, GoboRot.

/spirit

[jdmyers]

Sometimes functions on a fixture might share the same address or channel. If you are trying to control something such as shutter on one button, and strobes on another button, but strobes are sharing the same channel as shutter / intensity / other similarly grouped functions, this could be your problem as well, since you would be overriding a channel from one button with another button using the same channel - even though they might not be on the same fixture control panel... if that makes any sense?