kgallen

Nor did I, until Edward explained to me a while back. Likewise it makes sense once you know, and the UPDATE (SmartTag on) to get the console to recalculate tracking is the way out of it. (I think there might also be a global "unblock this cue stack" too, but I've never used it - too scared!).

Hi, Yep. easy: You will need two cues, one for each of your requirements - let's say you number them cue 2 and cue 2.5. The cue before (cue 1 in my example) will need to set those 10 fixtures to whatever intensity you want to start from. Cue 2 will be recorded for those 8 fixtures to be 0% with Fade Down of 15s, cue 2.5 will be for the 2 fixtures to fade to 25% again over Fade Down of 15s. Then on cue 2.5 you go into Cue Settings (button at the end of the line in the Cue list window) and set that cue to "Auto With". This means that cue 2.5 will be triggered at the same time as cue 2. I would recommend being in SmartTag on and Tracking to record this requirement. When you record cue 2 make sure you only change (hence tag) the 8 fixtures to go to 0. When you record cue 2.5 make sure you only change (hence tag) the 2 fixtures to go to 25%, otherwise each cue will affect more lights than you intend and your requirement won't work properly. See https://www.zero88.com/manuals/zeros/cues-playbacks/cue-settings/cue-triggers

Hi @LLuk Blocked (white) values will inhibit move on dark from operating on any fixture that is blocked in that cue. MOD can operate on the following cue if the fixture isn't blocked assuming that fixture is not used until later. COPYing cues will result in blocked values. Updating or recording with SmartTag off may result in blocked fixtures if you tagged that fixture but actually didn't change the intensity. Using UPDATE with SmartTag enabled will clear the blocking and track if possible. If you've seen other behaviour (and your opening text suggests you do), then Edward will probably need a little more info on your exact programming sequence, a showfile and which ZOS version you're using. Reading your paragraphs your understanding in each seems correct to me.

If you’re wanting to record an Effects palette that includes other attributes, you might want to refer to the recipe I documented here: (don’t torture yourself with the whole thread, I’m still in therapy!)

Hi @discover I will let you follow @Edward Z88's instructions first. If subsequently you need to load "user created" fixture definitions, you just load them with Setup->Load (with the IFT file(s) on a USB stick of course). Here is the entry in the English manual: https://www.zero88.com/manuals/zeros/setup/load/fixture-files-2 Good luck, I hope you get your lights working!

I know nothing about this stuff, but could Multiplay do what you need? https://www.blue-room.org.uk/topic/73548-multiplay-new-version-in-development/page/11/#comment-603888 https://www.da-share.com/software/multiplay/ https://da-share.com/forum/

Hi @discover If you're desperate, I've attached my own fixture profiles for these fixtures and modes. (The ones in the library might be based on these but Edward possibly rebuilt them in the GDTF editor). Regards, Kevin Showtec.ift

For Elara: Test Mode - Faders and Rotary Controls A Master - Sequence 2 button B Master - Sequence 3 button Speed Control - Memory Page button Test Mode - Internal Tests Internal EPROM test - Sequence 1 button

Posting here for reference (because I needed it today), hope the Zero88 folk don't mind! (No action required from Zero88 folk). This is certainly for the Mk1 (grey) desks, it might also work for the Mk2 (blue) desks. Alcora_Elara_Test_Mode.pdf

This just needs release on lower disabling doesn’t it? The trigger level could be set to 1 or 2% if the colour needs to snap the first time the fader is pushed Setup+Playback button then you’ll find it in there, I think under one of the page tabs.

Yes. 🙂 https://www.zero88.com/manuals/zeros/setup/universes/citp

This is really important feedback @Amy Worrall, thanks for taking the time to capture it all!

Hi @dolphins 7.13 will require an old coprocessor code. When you install 7.13 after 7.14, the installer will also move the coprocessor back to 7.13. -> your experience is expected 🙂 I hope that translates ok!

Hopefully @Edward Z88 will be here soon to give you proper advice, but it seems for now you should backdate to 7.13 for your show. If you did update coprocessor firmware then it will want to regress that too. A while back I was testing some beta releases of ZerOS and needed to regress to 7.13 for a show. I didn't (fortunately) have any issues. Note this was FLX rather than FLX S though.

Hi both! @delfine Did the console want to update the coprocessor firmware, and if so did you allow it to do it? @Flabbe With the touchscreen, did you recalibrate it after the ZerOS install? (Maybe you need to press the Update button to make calibrate work on your monitor?)

If you Untag something then that untagged change will not be recorded or updated. You need to use the REMOVE method discussed above to take a something out of a cue.

I agree! However it's embarrassing sometimes, I should have known "Clear Fixture" off the top of my head! 😏 What it reminds me is I need to keep reading the manual and focusing on some of the "advanced" sections. And to keep re-watching Edward's various FLX/ZerOS videos!

@Edward Z88 ah Clear Fixture - that's the one! I was completely wrong! Edward, would you be prepared to add that to the "Manual Tagging" section of this page - or a cross-link or one of your "lightbulb" boxes to point to that if it's documented elsewhere in the manual (seems to he here)? I'm sure you probably mention Clear Fixture in the video that is in that section, I just didn't want to watch all of that video to answer Amy's question. 🙂

Hi @Edward Z88 Could you answer this part of the original query. I'm pretty sure I'm wrong in my answer. I couldn't find anything in the manual, but I'm sure there must be something... This part of my answer I'm pretty sure is wrong, or at least missing something: Thanks, Kevin

ZerOS tags when you adjust <thing> but I guess you know that!

Sure, that's of course fine! I was just curious that Amy might think she "needs" to work with SmartTag off when doing theatre stacks. Each to their own based on their needs, experience and workflow. 🙂

Hi Amy, I guess I should've questioned this one: Why? (out of interest!) I programme theatre cue stacks and rarely turn off SmartTag. I only do if I need to do a REMOVE or something very specific for an UPDATE operation. I know that the busking folk tend to turn SmartTag off but this is because they are doing some complex overlaying of Playbacks with very specific material recorded into each playback, and generally not using a traditional stack or relying on features such as Move on Dark. But for theatre cue stack I would have thought in the main, you'd have SmartTag on.

Yes, sorry, I should have elaborated on my answer for attribute remove! Thanks for clarifying that! - I should have thought more about "thing"!

Hi Amy, "Welcome back!". I'll try to help... Since you have an FLX, the Output window has a Preview button. To see fixture details (colour, gobo etc) you'll have to select them first and then you'll get a scrollable list. (Might not be quite as good as you have on Eos). SmartTag looks for non-zero intensity then records only the attributes/parameters that are adjusted in the programmer and are thus required to be recorded to recreate that look. Whether it is attribute or parameter depends on the attribute. For example by default, Colour parameters are linked together (so you get the colour you want) whereas Shape and Beam parameters are not grouped (gobo is not linked with zoom for example). If you turn SmartTag off then tagging will be based on what you adjusted but the "linking" will be as above. You can change this in Setup. To untag a whole fixture, select it then (I think) it's CLEAR+HOME (need to check the manual!). To untag a whole attribute it's CLEAR+COLOUR (for example) Select the Fixture, hit HOME (this will tag all parameters). UPDATE and select the REMOVE option. (See David's elaboration in the following post). Palettes recorded on a fixture can be applied to another fixture of the exact same type even if that other fixture wasn't selected when recorded. There isn't currently any other "palette morphing" onto a fixture with similar capabilities but a different make/model. (This is something I/we've been asking for for some time, so I hope it will come along soon... 😉 ) No you won't do it by accident. You have to try "quite hard" to get anything but Colour in a Colour palette (but actually you can record Beam/Shape etc in there but you have to be very explicit to do that). The most (in my usage) application of this is to be very specific about which attributes are recorded into an Effect palette. I'm not sure you can do that. Using the "spreadsheet" style of the cue list one by one is the only method I know. You can however in Setup, set the default times for fades, so if during programming you need different times for a block of cues you could do this. But once you've programmed, I don't know a quicker way to update them. There is reasonable COPY (and MOVE) functionality (especially on FLX), but I don't know that you can do this. I hope that helps! I'd encourage you to put enhancement requests in on this forum for any features you have in Eos that would be beneficial on ZerOS. To record a blackout, I recommend "1 THRU *. <ENTER>" as this allows move on dark to continue to work. Similarly, avoid snapshot cues Similarly if you get white boxes in your output windows, those fixtures have "blocked" values. If this is not intended, then use UPDATE <ENTER> (with SmartTag enabled) to remove these. Note also when you're using UPDATE to ensure you've selected the tracking option you want - Cue Only, Track Forward etc (those are probably the options you're most likely to use). Tracking works well on FLX so I'd encourage you to stay in that mode, and not go back to Global Cue Only mode (in Setup). Regards, Kevin

Salut! https://www.zero88.com/manuals/zeros/cues-playbacks/recording-cues-2