Remove fixtures from fader

[martin-144]

Hi,
I am happy to say that we are in-game again. We are having our first youth-theatre production since two years of corona pause.

Said that, I am having some problems because I recorded an effect on a moving head, which is working fine. However, I recorded some other lights with it which shouldn't be there.
Can anyone tell me how I can remove these lights from the effect which I stored on a faders cue? I can set the lamps to zero intensity, but I want to remove them completely from the fader to not interfere with other cues. Any hints would be appreciated.

Thanks, Martin

[kgallen]

I always struggle with this, but your friend is the HOME key since this tags all parameters of a fixture.

So select the fixtures you want to remove. Press HOME.

Press and hold UPDATE to get the options box up and enable REMOVE.

Press the playback you want to remove this stuff from.

[martin-144]

Thanks Kevin for the quick reply,

Will try this tomorrow evening.

[kgallen]

I just looked in the manual. Also you need SmartTag *disabled*.

Somewhere on this forum you'll find me endlessly asking the same question, and Edward patiently answering.

https://zero88.com/manuals/zeros/cues-playbacks/updating-cues/update-options#remove

[Davidmk]

Just to expand on that a bit...

My variation on this is to record only the fixtures I want but surplus attributes (typically intensity). In this case, instead of Home, you can just select the fixtures and the unwanted attributes then update/remove.

[kgallen]

My extra 2p worth too, if the issue is with an Effects palette, then I've found it easier to delete the darn thing and start again. I think the last time I had that issue Edward agreed that is often the easiest approach! Above should be good though for a normal cue or single cue playback.

Let us know if it worked!

[martin-144]

Starting over from scratch would be my next option. But lets try what I can achieve tomrorrow.

[martin-144]

Hi all,

to finally give some feedback, I ended up programming the effects from scratch because there was no remove option in the record menu.
I guess this may be due to the fact that my desk is in "cue only" mode at the moment. I thought it would be easier for me to handle in a theatre environment, but now it seems it brings some limitations with it.

The second thing I noticed is that I cannot run two effects in parallel. Whichever effect I start later will interrupt the effect started before and stop it. Is this another limitation of "cue only" mode or am I doing something wrong here? I am quite sure that I only tagged the parameters needed for the particular effect.

Cheers,
Martin

[droiddk]

1 hour ago, martin-144 said:

To finally give some feedback, I ended up programming the effects from scratch because there was no remove option in the record menu.

Remove option is in the update window.

Regards

[Edward Z88]

Hi Martin,

1 hour ago, martin-144 said:

I ended up programming the effects from scratch because there was no remove option in the record menu.
I guess this may be due to the fact that my desk is in "cue only" mode at the moment.

That is correct - if you are in global Cue Only mode, this essentially means the console is in "basic" mode". More advanced programming options such as Remove will be unavailable.

Don't forget - when you have your Tracking Options enabled, you can then use the Tracking Options to set the console to Cue Only anyway.

1 hour ago, martin-144 said:

I cannot run two effects in parallel. Whichever effect I start later will interrupt the effect started before and stop it. Is this another limitation of "cue only" mode or am I doing something wrong here? I am quite sure that I only tagged the parameters needed for the particular effect.

If the console is in global Cue Only mode, it will decide what does and what doesn't get included. This can bring limitations when it comes to mixing playbacks. See the link below for more information on mixing playbacks...

I hope this helps. If you have any questions, please let me know.

Edward

[kgallen]

8 hours ago, martin-144 said:

I guess this may be due to the fact that my desk is in "cue only" mode at the moment. I thought it would be easier for me to handle in a theatre environment, but now it seems it brings some limitations with it.

The second thing I noticed is that I cannot run two effects in parallel. Whichever effect I start later will interrupt the effect started before and stop it. Is this another limitation of "cue only" mode or am I doing something wrong here? I am quite sure that I only tagged the parameters needed for the particular effect.

Yea I can see Cue Only is a big limitation here, particularly stopping you overlaying operations since "all data is recorded in all cues" (or at least that's how the desk plays them back regardless of how the information is represented in the internal datastructure) - so you lose the ability of another cue taking control over a parameter.

I came to FLX from Fat Frog. On Fat Frog the few times I used Partial mode I ran back to Full mode because I lost control of what Partial was doing. I've not had the same experience with FLX. I'm always in Tracking On mode and never have I felt the need or even the inclination to go to Cue Only mode. Compared to really advanced users, I don't do anything "that fancy" although I do have a reasonable number of LED and mover fixtures (although surprisingly on my last show, conventional fixtures did outnumber LEDs 2:1 which was unusual, usually it's closer to 1:1).

So, even as a "low-to-medium complexity" user myself, I'd encourage you away from Cue Only to Tracking. It really isn't at all scary, and SmartTag pretty much makes Tracking work the same way as Cue Only for 95% of cases and move on dark works beautifully in the background [1]. It's only when you want some finer grained control (or Remove!) do you need to start fiddling with SmartTag in my experience (which is theatre). I've had my FLX since 2015, so have done quite a few shows with it.

Go on, you know you want to!

Kevin

[1] Tip: Programme a blackout with "1 THRU @ ."

[martin-144]

Ok, so for this production time I can live with the "cue only" setting. Next time I will go back to "tracking", as it seems to bring more advantages than I thought.
Kevin, I will definitely try your tip with "1 THRU @ .", it seems kind of awkward right now but I will try it for sure.

Thanks, Martin

[kgallen]

12 hours ago, martin-144 said:

I will definitely try your tip with "1 THRU @ .", it seems kind of awkward right now but I will try it for sure.

You can programme a keys macro and assign to a UDK if you want. 

I did this last show but I never used it, I’ve got used to typing the key sequence!

If you use the macro you can automatically get the cue named at the same time (e.g. DBO or Blackout to your pref).

The other option is ENTER ENTER @. But I think this has the downside if you edit earlier cues and those changes track forwards you will no longer have a blackout.

@Edward Z88 to advise!

Kevin

[Edward Z88]

Hi Martin & Kevin,

13 hours ago, martin-144 said:

I will definitely try your tip with "1 THRU @ .", it seems kind of awkward right now but I will try it for sure.

58 minutes ago, kgallen said:

The other option is ENTER ENTER @. But I think this has the downside if you edit earlier cues and those changes track forwards you will no longer have a blackout.

"1 THRU @ ." tells every single fixture to go to 0%. If you then record a cue, this cue therefore tells every light to go to 0%. This means even if you make tracked changes further up the stack, you know you'll never end up with lights on in your blackout.

"ENTER ENTER @ ." tells the fixtures that are currently on to go to 0%. If you then record a cue, this tells only these fixtures to go to 0%. That will of course give you a blackout initially, however, if you add a new light in to an earlier cue with tracking, this fixture will need to be manually turned off again in your blackout.

1 hour ago, kgallen said:

You can programme a keys macro and assign to a UDK if you want. 

The "1 THRU @ ." macro is actually used as an example in the manual. Please see the link below for more information...

https://zero88.com/manuals/print?manual=zeros&type=section&content=user-macros

Hope this helps,

Edward