Edward Z88

Hi Kevin, Macros are only required if you want a single Note command to emulate a Go button press. In most uses of MIDI Notes as the article describes, the Note number you send to the console, will trigger that cue number on the viewed playback. I will however add this information as a tip under the Note's Cues section. Edward

Hi All, Apologies for the lengthy delay on this. Due to the delay in getting the manual out, we have taken the decision to release the manual alongside ZerOS 7.9.6, to help future proof it. ZerOS 7.9.6 has been in release candidate stage since mid-July. We are planning to release this month. If you have any questions let us know. All the best, Edward

Hi Simon, With MIDI Notes, each individual Note command triggers each individual cue. For example when the console is set to Notes triggering Cues, and it receives a MIDI Note On 10 command, the console will trigger cue 10 in the currently viewed playback. If you wanted to simply emulate a Go button press with the same MIDI Note command, you could do this, however via programming a Macro. Firstly, program a macro that presses your Go button. You can do this by tapping RECORD MACRO x ENTER (where x is an empty macro number) -> Keys -> Press your Playback's Go button -> MACRO. Now, view an empty playback, and program an empty cue. Go into this cue's settings -> Macros... -> Macro Add -> Choose your Macro -> OK -> OK. Now, whenever you send a MIDI Note 1 command and you are viewing this single cue macro playback, it will emulate a Go button press of your main cue stack. Hope this helps, if you have any questions let me know. Edward

Hi Neil, No problem - just send us a copy of your show file when you get a chance and we'll take a look. Edward

Hi Simon, There are 3 different MIDI Protocols FLX supports. These are MIDI Timecode (MTC), MIDI Show Control (MSC) and MIDI Notes. All three can be used to trigger cues on the Master Playback. The article below goes through each of these, and how they can be configured on FLX... http://support.zero88.com/990063141 Hope this helps, if you have any questions just let me know. Edward

Hi Joe, Hope you're well. No date on Stage Sizing yet. We require a new fixture library for this, to gain more information such as Pan and Tilt ranges. The current plan for the road-map is the new fixture library will be released as ZerOS 7.9.7, and so Stage Sizing will then be able to be released after ZerOS 8. Edward

Hello, Yes, for this I'd program a new playback. Record 50 cues, each one turning each pixel from your chosen blue, to your chosen orange. I'd recommend using palettes for this, so that if you wish to change your night time blue, or your sunrise orange, you can update the colour palettes and all 50 cues update automatically. As you step through each fixture and change it from blue to orange, you may find the SHIFT + Right Arrow key shortcut helpful, for selecting the Next fixture. Then for each cue set a colour fade of 30 seconds, and an Auto With trigger, with a wait of 6 seconds. I'd recommend temporarily changing the console fade time defaults, to save you having to change 50 cue's fade times. To do this tap SETUP -> Defaults -> Cue Colour Fade. You can then trigger this playback from a cue in your Master Playback if you wish, whenever you need to use this sunrise effect. Hope this helps, Edward

Hello, Thank you for the request. As you say, FLX has 4 physical UDK buttons, however 40 in total across 10 playback pages. They are page locked by default. There are no plans to add UDKs to FLX S consoles, as this is a more advanced feature. Edward

No problem, just let me know if there's anything else we can help with. Edward

Hi Mac, There's currently no way of preventing a playback from being inhibited by another playback that is soloed. However, UDKs won't be inhibited by a playback being soloed. You could therefore have an intensity programmed for your FOH on a UDK that can be latched on before you solo a playback. Hope this helps, Edward

Hello, Sorry to hear this. Have you created a show file from a fresh install, or have you loaded an existing show file into the new software? Please could you send us a copy of this show file to support@zero88.com, and we’ll take a look to see if there’s anything causing the issue. Has the console offered to dump a debug file to USB? If so could you send these across? It is possible to roll back the software to ZerOS 7.9.4 if you wish, however we haven’t come across this issue before. ZerOS 7.9.4 can be downloaded here... For information on setting Default values, see below... http://support.zero88.com/1011707631 The colour picker will use RGBW chips for colour mixing if present. Other chips will be available via the encoders. Hope this helps, if you have any questions just let us know. Edward

Hello, See if there is a “Shutter” parameter or similar under the Beam attribute. What value is this set to? Most fixtures personalities should be configured so that when intensity is raised, you will achieve White light output. Therefore parameters such as RGBW or Shutter are preset at values specified in the fixture’s manual to allow this. Edward

Hi Eric, Apologies for the delay. We have seen your emails. The console is with us, and we have had it switched on to see if we can recreate the issues. We will continue investigating on Tuesday after the UK Bank Holiday weekend. If you have any queries just let us know. Edward

Hi Steve, Just to confirm, what console is this on? What software version were you running previously before updating? I would recommend doing a fresh install of ZerOS 7.9.5, using the instructions available here... http://support.zero88.com/1518910761 Once ZerOS 7.9.5 is freshly installed, you should find new effects are available when you press the "Auto Create Effects" button. If loading in the show file into the freshly installed software is still causing issues, please send us a copy of your show file to support@zero88.com, and one of the team will take a look to see what may be causing the issues. Hope this helps, Edward

Hi Steve, For information on setting Max Level and fixture Defaults, see the article below... http://support.zero88.com/1011707631 Hope this helps, if you have any questions let us know. Edward

Hi Marco, We have received your support email regarding this, so will continue over email. If you have any questions just let us know. Edward

Hi Marco, Please email support@zero88.com with this description, and we'll be able to advise on what the cause of the issue is. Edward

Hi Paul, No problem - let us know if there's anything else we can help with. Edward

Hi Paul, Just to double check, the software installation application to be loaded into the console is "ZerOS OS Creator USB - v7.9.5 17-5-2019 MD.exe". If you are running ZerOS 7.9.4 you will be able to tap SETUP -> Load File, and choose this file and load it in. Also available with the ZerOS 7.9.5 download is Phantom ZerOS 7.9.5. This is not the console software - this is the offline editor. If you try loading this into the console you will receive the error you described. Hope this helps and solves the issue. Edward

Hi Thibault, Hope you're well, really glad to hear you have a FLX S48 on the way. Yes your best option for this is to use different show files for each venue. You could build each show file using a standard file if you wish - and simply change your fixtures for each venue. Edward

Hi Walid, If you wish to communicate with Light Converse, you'll need to route your lighting data to the PC's loopback IP address, which is 127.0.0.1. It will be one of the IP options on Phantom for each protocol. I believe Light Converse will be listening on this IP, however you may need to manually change this in Light Converse. Only use one of the protocols to communicate with Light Converse, and disable the rest. It doesn't matter which protocol you use from Phantom's point of view - I'm not sure whether Light Converse recommend a protocol in particular. Hope this helps, if you have any questions just let us know. Edward

Hi Kevin, EFFECT + HOME is the same as the No Effect palette - it simply stops any effects running (the syntax EFFECT 0 ENTER also does the same). In the same way COLOUR + HOME will just home the colour of the selected fixture. It would only give hard values for that cue, therefore only fixtures that needed to Move On Dark for the next cue wouldn't be prepped. When you go into the cue after the block, fixtures could then move on dark for when they're next used. Edward

OK thanks for the information. Will keep an eye on this to see if I can recreate. Edward

Hi Kevin, A quicker way around this would be to go into the cue where you want the movers to stop the effect, select the fixtures, EFFECT + HOME -> SHIFT + RECORD -> type the cue number -> Playback Button -> Merge. Doing this will also turn it into a block cue. Edward

Hello, SmartTag will register a fixture as "off" when at 0%. Therefore if a fixture is at 1% SmartTag will include it. If this is causing you problems, you can simply hold RECORD, tap SmartTag so that it has a blue stripe meaning disabled, and then press RECORD to close the window. Now all tagged fixtures will be recorded, including those at 0%. For more information on tagging including SmartTag, see below... http://support.zero88.com/1014189311 Fixtures can't be created with a minimum parameter level. Hope this helps, Edward