Effect recorded into default is hard to get rid of

[Davidmk]

Just in from a gig providing lights for live music at a fireworks display. Not my usual rig so no TouchOSC/go-cue set up as it would take too long to program. I quickly thew together some colour mixing PBs and a few effects PBs and relied on the programmer for other bits & bobs.

Part way through the gig I must have accidentally recorded the warm rainbow into default (I was probably intending to only change default tilt to 0 instead of the normal 50%)

All my LEDs get stuck on a version of white, my colour mixing faders don't work but I can still override the colour in the programmer. Tried the obvious update/remove but it had no effect. Eventually I tried setting the default to red and then

I don't suppose we are supposed to record effects as default, it dosn't make sense

Anyway,to  cut to the chase...

What's the right to get to get effects out of  defaults if you accidentally put them in?

 

[kgallen]

I’m not sure what you mean by ‘recorded into default’ - which ‘default’ is this?

The only ‘default’ I know of is under HOME and you DELETE HOME. But you can’t record an effect there so you must mean something else?

[Davidmk]

6 hours ago, kgallen said:

The only ‘default’ I know of is under HOME

That's the one. It was a colour effect. Selecting one of the affected fixtures showed the name of the effect under colour and source showed D under colour. Hence me thinking it was recorded under default.

I'm prepared to accept that this is supposed (and maybe is) impossible but, if it was something else then I love to know what.

The fix, ultimately, was to record an actual colour into default and then to delete it.

Don't know how I managed to record it, don't know if I can repeat it. Or, indeed, how to avoid repeating it.

[kgallen]

Interesting. I guess I never really thought about default holding colour but I guess it does, just the default is usually white!

So what you’re saying seems perfectly sensible!

I guess this us fairly easy to do - you’d set some fixtures and done RECORD HOME. It would have asked, I think, home or default, which might have rung some alarm bells, but certainly not hard it do. 

Tomorrow, Edward comes along and tells us we’re both talking nonsense!

[Davidmk]

Default (and home) holds a value for everything.  It can even hold an intensity. I was trying to change pan & tilt to zero in this case but I frequently change colour to black.

1 hour ago, kgallen said:

It would have asked, I think, home or default, which might have rung some alarm bells, but certainly not hard it do.

It most certainly would have but I wanted to change default so it didn't alarm me and I meant to only select position and nothing else.

Generally though, I have an MFK where I keep my pseudo defaults for a gig. Values I want when I'm not doing something else with them. Where I want moving heads to be, stair edge lights at 50%, MH washes white (it's black in the real default). Anything that just applies to that show rather than to that fixture.

[Edward Z88]

On 11/12/2023 at 3:01 AM, Davidmk said:

I must have accidentally recorded the warm rainbow into default

Effect data (Speed, Size, etc) cannot be stored as a fixture's default values. However, if a fixture's parameters were referencing the values stored in an effect palette, these values would get stored in the fixtures Defaults, as per any other parameter referencing a palette. So if you apply a [Rainbow - Warm] effect, and then RECORD > HOME > Default, RGB will store a reference to E23 (effect palette 23).

On 11/12/2023 at 3:01 AM, Davidmk said:

What's the right to get to get effects out of  defaults if you accidentally put them in?

19 hours ago, Davidmk said:

The fix, ultimately, was to record an actual colour into default and then to delete it.

Yep, that is the best solution: select the fixtures, set the desired colour values, such as applying colour palette 1 [White], and then RECORD > HOME > Default.

[Davidmk]

Thank you @Edward Z88. So, just down to careless recording. Not surprised. Did expect update remove to get rid of colour values for the affected fixtures though.

 

Mention to @kgallen so he sees your response.

[Edward Z88]

16 minutes ago, Davidmk said:

Did expect update remove to get rid of colour values for the affected fixtures though.

Fixtures must have default values. It is therefore not possible to remove parameters, because they must have a default value assigned.

You are therefore essentially always "updating" when recording to the Home key. DELETE HOME is a special operation, that reverts the values to the library defaults (but of course does not remove parameter data).

Hope this makes sense.

[Davidmk]

Aha, OK, so it isn't possible to have null values in defaults. That would seem to be the crucial thing missing from my understanding of them.

Many thanks for that.