Jump to content
Vari-Lite Controls Support Forum

kgallen

Regulars
  • Posts

    1,802
  • Joined

  • Last visited

  • Days Won

    69

Posts posted by kgallen

  1. Doesn't sound like the console, sounds like an electrical noise coupling issue between your dimmers or control wires to those dimmers

    What are your dimmers? Where are 14 and 26 in respect of the dimmers - same dimmer box, or different dimmer boxes on the same phase of the electrical supply? Are they analogue control input (with a DMX demux)? If you swap control cables (DMX/analogue) around does the problem stay on 26 or does it move around?

    If you go into the Z key there is a tab for DMX Outputs. Do you see what you expect under address 14 (whatever) and circuit 26 (0 presumably).

    (This assumes your dimmers are patched at addresses 1-<whatever>, adjust above numbers if they don't start at 1).

  2. The Zero88 YouTube channel I think is "mothballed" in preference to now using the Vari-lite YouTube channel.

    https://www.youtube.com/@zero88/videos -> https://www.youtube.com/@VariLite/videos

    Is it worth, if you can, putting something on the Zero88 channel to direct users to the Vari-lite channel plus referencing that channel in the About and Channels tabs?

    Probably a 30 second video would be the best way to get a notification in front of users looking for information beyond (e.g.) ZerOS 7.12 because for example the 7.14 stuff is on Vari-lite rather than Zero88 (which of course I realise you know, but users possibly don't!)

     

    Ta.

  3. Yea Edward is right, since both of your fades are 15 seconds then you don't need the Auto cue in my explanation.

    If you wanted different fade times then you would need the Auto method in my post (say you wanted 15 secs to 0% and 20 secs to 25%).

    Sorry for over-complicating it!

    • Like 1
  4. 11 hours ago, LLuk said:

    But i still dont understand why there are again some blocked values after update every single cue with no changes but SmartTag enabled.

    I think we'd need a little more information to find an explanation for this. Maybe if you upload the showfile this will be enough for Edward to try "unblock" and give you an explanation if the unblocking doesn't work for a specific fixture.

  5. 11 hours ago, LLuk said:

    I didn't realised that copy cues blockes values. But after your explainations it seems logic to me.

    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!).

  6. 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

  7. 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.

    • Like 1
  8. 4 hours ago, discover said:

    How do I import the *.ift file?
    In the (german) user manual I cannot see it.

    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!

    • Like 1
  9. 45 minutes ago, delfine said:

    Yes, I'll wait for Edward before going any further. However, I don't understand, when I went back to 7.13, I had the question of updating the cprocessor when I went back to 7.13, I said yes... Is this really what you are talking about ? he will also want to regress.” 

    The French <= > English translation is not always very clear. 

     

    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!

  10. 10 hours ago, delfine said:

    OK thanks. 
    I'm waiting for what @kgallen says. 
    🤞

    I'm a little panicked. 

    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.

  11. 21 hours ago, Amy Worrall said:

    If I go to a cue, make a few edits, untag something, then do Update… in the newly updated cue, does the thing I untagged remain at whatever it was set to before the update (e.g. in eos just not including it in the parameters to update), or does it get removed from the cue entirely (e.g. in eos doing @<enter>)?

    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.

  12. 2 hours ago, Davidmk said:

    I love threads like this, I always learn something. In this case, more than I contributed 😀. Thanks all.

    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!

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.