Edward Z88

Salut Ben, Bienvenue sur le forum Zero 88. D'après votre description, il semble que "Programmer Time" soit activé pendant très longtemps. Cela signifie que les modifications manuelles que vous apportez prendront un certain temps à disparaître. Pour trouver l'option de temps du programmateur, appuyez sur Z / Shift, et sur la quatrième roue codeuse, vous verrez l'heure du programmeur. Est-ce que cela a un fond bleu clair? Si c'est le cas, appuyez sur le bouton au milieu de l'encodeur Programmer Time pour le désactiver, indiqué par un fond bleu foncé. J'espère que cela t'aides, Edward Hi Ben, Welcome to the Zero 88 forum. From your description, it sounds as though "Programmer Time" may be enabled, to a very long time. This means manual changes you make will take a while to fade. To find the programmer time option, tap Z/Shift, and on the fourth encoder wheel you will see programmer time. Does this have a light blue background? If so tap the button in the middle of the Programmer Time encoder to disable it, indicated with a dark blue background. Hope this helps, Edward

Hi Kevin, Definitely an interesting feature to investigate. It would mean you could leave a default home position of 50% pan 50% tilt, and ensure your fixtures tilted upstage/down stage for example, even if they have been rigged with a slight offset. This is on the system as reference number ZOS-5911. Certainly another interesting feature to investigate. For now, you would have to manually give your fixtures some low intensity, in the cue prior to snapping them on to full. Edward

Hello @PSchermer Welcome to the Zero 88 Forum. @kgallen nicely covers all the basis here in the post above. The main reason that just raw DMX is shown, is to show you the true resolution of control you have over that parameter. In most cases, no matter what the value was you were seeing, you are probably going to need to be looking at the stage, or visualiser, to actually get the lights where you need them. See this section of the online manual for more information... https://zero88.com/manuals/zeros/controlling-fixtures/parameters This is something that is being reviewed. If you have any questions please let us know. Edward

Hi Niko, We have received your fixture request email. We will get this fixture added to a future library release. Please could you email me a copy of your fixture file that is failing to load? I will then take a look to see what may be preventing it from loading in. If you have any questions let me know. Edward

Hi Niko, No problem, really glad to hear you are now up to date. Edward

Hi Niko, Welcome to the Zero 88 Forum. I have not seen this error message before. Please could you email me a picture of the error message you are receiving? The latest ZerOS Library file can be downloaded from the link here, with the .zlbr file extension... https://zero88.com/storage/downloads/bb511d50-baf0-4ace-8a09-c89b3a0adcdb/ZerOS-Library-2.zlbr You must be running ZerOS 7.9.8 software or later on your console to load in the ZerOS Library file. If you have any questions let me know. Edward

No problem - if you have any questions let us know. Edward

Hi Pascal, Welcome to the Zero 88 Forum. That's great, really glad to hear you have a new FLX S48. Yes it is - if you have an active DVI-D to VGA adapter you will be able to use your VGA monitor. The passive DVI to VGA adapters will not work. For more information see the link below... https://zero88.com/manuals/zeros/desktops-windows/external-display Once connected, as it isn't a touchscreen you will be able to connect a mouse to navigate the external monitor. I hope this helps, if there's anything else we can help with just let us know. Edward

Hi Neil, No problem! Yes definitely helps typing in commands rather than using the UI when it comes to needing lots of macros in a cue. The Auto (with first cue) idea is logged on our software tracking system, as reference number ZOS-10724. If you have any questions let us know. Edward

Hi Don, There is no Zoom invert option available on the console. By default the zoom parameter will be controlled how the fixture manufacturer design it - whether that be wide at 100%, or spot at 100%. You can however choose the "Invert Output" check box in the Fixture Editor software for any parameter. You could therefore do this for the Zoom parameter of your fixture. Choosing a special of "Zoom" for a parameter, allows the console to apply it to the Zoom automatic effects. Hope this helps, Edward

Hi Don, As @kgallen explains, the Image Manager is part of the Fixture Editor, not a stand alone program. It can be used to show you all the images used by fixtures in the current fixture file. To edit the gobo images of a gobo parameter, go to the properties of the gobo parameter of a fixture, and then go to the details tab at the top. You can then edit the details, including loading images to a detail. Hope this helps, Edward

Hi Neil, No problem at all! You could do this, by triggering a cue using a macro, and then have a delay time on the cue you are triggering. See the Advanced section below... https://zero88.com/manuals/zeros/cues-playbacks/cue-settings/cue-macros Hope this helps, if you have any questions let me know. Edward

Hi Mac, Connecting a laptop to the console running the ZerOS Monitor app for windows, is done in exactly the same way as connecting an iPad running the ZerOS Monitor app. For more information see the link below... https://zero88.com/manuals/zeros/networking/using-the-remote-apps For more information on auto palettes, as opposed to palettes you record manually, see here... https://zero88.com/manuals/zeros/palettes/automatic-palettes Hope this helps, Edward

Hi Mac, No problem, look forward to seeing you on the training. Edward

Hi Mac, This is a bit of a spoiler for the training 😆 Firstly, as a prerequisite to most of this, I am assuming SmartTag is off. For most of this you're going to want to be pretty picky with what gets recorded where. For more information on SmartTag, see below... https://zero88.com/manuals/zeros/cues-playbacks/record-options/snapshot-smarttag If I have a completely fresh console, and have an event I need to light in very limited time, first thing I would do is get the rigged patch, preferably by RigSync if it is decent RDM kit. Otherwise, get all the info you can, and start patching. If you have a small Windows laptop (touchscreen even better!), get this connected to the console over Wi-Fi, and walk round the venue with it patching. Once patched, create all your auto palettes and groups as a base. I would then start to program my own custom groups, based on where the fixtures are in the rig, and how you wish to use them for your design. With these key groups, I would then aim to program 12 intensity masters. By this, I mean record just the intensity for 12 groups of lights onto separate playbacks, with nothing else. The reason 12, is I like to fill the first row of faders on page 1. As a general rule when operating, I try to avoid having manual intensity values, and have intensity controlled by playbacks only. If I have time, and know that when the event is running it will involve very quick changes, I will then program myself some macros. I will record a macro for each intensity master I have created, which selects their respective groups of fixtures. I will then trigger each macro with each playback, so that when I raise the playback of my "back light" for example, backlight are automatically selected, allowing me to then use my palettes desktop on the external monitor to apply my palettes. If you don't have time for this, I would probably live with my groups on the internal touchscreen, and then jump between other desktops on the external touchscreen. You may then want to have a think about custom defaults and home values - are there positions or colours that you are using more than any others, that could be used as the default for the fixtures? Rather than using the Home button as a way of "resetting" all your parameter adjustments, could the Home button instead just take the selected fixtures to a nice default lighting state? Custom default information here... https://zero88.com/manuals/zeros/controlling-fixtures/defaults Custom home information here... https://zero88.com/manuals/zeros/controlling-fixtures/home After groups, position palettes are by far the most important set of custom palettes to create. Remember - as a general rule always include all fixtures in all position palettes - it then doesn't matter which ones you select, they will work with your palettes. Start with the usual palettes; down stage, centre stage etc, but then create some "general" position palettes, which are more interesting looks. Then, I create some "all" palettes, using snapshot recording. This gives me some lighting states I can fade to with programmer time manually. I tend to store these in the Beam attribute, as I find I have the least palettes in this attribute. For more information on snapshot palettes see below... https://zero88.com/manuals/zeros/palettes/recording-palettes For more information on Programmer Time see below... https://zero88.com/manuals/zeros/cues-playbacks/special-playback-functions#programmer Then, create yourself a few lighting states, that will just work for most things. I would program 6, to fill another bank of faders. Raising these faders, and double tapping CLEAR, will then always guarantee to get you somewhere suitable. For UDKs, I like to have blinders on one for live events, house lights on another, and a "Clear Fixture" UDK, to allow you to clear manual values for the currently selected fixtures. If there is a group or position you are regularly using, stick this on a UDK too. For more on UDKs see below... https://zero88.com/manuals/zeros/user-definable-keys Always important to never forget - emergency lighting. If you aren't using the Master Playback for anything else, program house lights/ general light there. If something happens, bring that in. I hope this helps, and gives you some further pointers. Edward

Hi Joel, The way ZerOS works, is that a playback will always have its own physical fader. There is therefore no central pool these playbacks live in, prior to being assigned a fader, in the way that some consoles work. This ensures that playback number 2, will always live on playback fader number 2, for example. On FLX S24 you have 48 (plus the master) playbacks to play with. I don't know your exact configuration, but as a generalisation let's say the first 12 playbacks are general lighting, and the next 12 are for your intro songs. This leaves playbacks 25-48 on page two free, where the playbacks you are currently not using could live. When you need them, you could then copy them back across onto page 1, replacing a playback you no longer need. As @kgallen mentions, on FLX you have 10 pages of playbacks, so this gives you the flexibility to have "operation" pages that you use to run the show, and then "storage" playbacks you use to hold spares/extras of all the playbacks you may need for the show. You can then use copy to transfer these from one place to the other. Your other option, is to actually segregate the configuration completely, and only have the playbacks you need at any one time in a show file. You can then have multiple show files saved to a USB stick, each for a different application. You can then give the instructions to the operator to load in file "xxxx" when required, and this will give them all the lighting states they need, all labelled of course. I hope this helps, if you have any questions let me know. Edward

Hi Mac, The most time consuming part of these situations, is simply getting the fixtures patched, let alone thinking about starting to program them. If the fixtures are RDM, RigSync will sort this out, otherwise it will be a case of working out what fixtures you have, and if they are in an existing suitable address and mode, getting them patched in. Fixture swap-out/change/morph/replace is ultimately all the same thing - the ability for the console to replace an existing fixture in the show, with a different fixture, applying all information such as programming to the new fixture. With the addition of the new fixture library in ZerOS 7.9.8 and later, fixture changes are now far more detailed, due to the extra information in the fixture database. This will help ensure the new fixture uses the same positions, colours, intensities etc in all your cues and palettes. If you have existing fixtures in your show, which are not used in a venue, you can therefore use these as templates, and perform a change profiles to replace the existing fixture with the venue's fixtures. If you have more fixtures in a venue than you had programmed in an existing show, you have a couple of options. Either add the additional fixtures manually into key cues, or add additional addresses to the existing fixtures - you can then start to have pairs of fixtures doing the same thing. In some lighting designs this works really well. This is a great place to start. If you do at least know what fixtures the venue has, pop them into a visualiser, and then replace the existing fixtures in the show file with the venue's fixtures. Address them to match the visualiser, and see how your programming looks. On 3rd March, I'll be running a session dedicated to using the console with limited programming time. If you're free, see the link below... https://zoom.us/meeting/register/tJ0lceuhqz4iGtzxQIwfa5oaM0qzWOTRg67a If you have any questions let me know. Edward

Hello, No news on this unfortunately. The ZerOS Remote watch app currently remains incompatible with watchOS 7, due to the changes Apple introduced in watchOS 7. If you have any questions let me know. Edward

No problem at all. Edward

Couldn’t agree more. Fundamentally it is down to your particular system, and if there are benefits to powering the console after the devices you’re controlling then that makes sense. The only “rule” we would advise is to ensure the console is earthed prior to connecting other devices to it. If you get into more complex network systems, you can easily get into the situations where you may have multiple controllers, and so of course the order the system is powered will be down to the system design. If you are using DMX relays to power the fixtures in the rig, such as our RigSwitch cabinets, then these allow you to remotely power the rig on and off from the console. Edward

Hello, Thanks for you email, I will reply shortly. If you have any questions let me know. Edward

Hi Kevin, This list is no longer required. Any touchscreens which are plug and play with Windows 10, will be compatible with ZerOS. More information below... https://zero88.com/manuals/zeros/desktops-windows/external-display/external-touchscreen Hope this helps, Edward

Hi Rob, As best practice, it is usually best to power the FLX console first, and then the fixtures. If you have fixtures that without the presence of DMX will go into an auto mode, having the FLX powered first will mean they will boot straight into DMX receive mode, as there will already be DMX present when they boot up. From a safety point of view, connecting the console first prior to powering the system, will ensure that the console is earthed. This doesn't require for the console to be switched on though. For more information see below... https://zero88.com/manuals/zeros/quick-start Hope this helps, if you have any questions let me know. Edward

Hello, Thanks very much for emailing me your show file. I will reply to your email. If you have any questions let me know. Edward

Hello, Has this touchscreen worked with the console previously, or is this the first time trying it? Please plug in the touchscreen via USB, power the touchscreen, and then boot the FLX S48. Then tap Z/Shift -> System Information -> System Info. In this window is a "Input Devices..." list. Can you see whether the Acer touchscreen is listed? Feel free to email me a picture of this window. The Acer website seems to have fairly limited information... https://www.acer.com/ac/en/GB/content/model/UM.VT2EE.A01 I am struggling to see whether this states it works with Windows 10. If it needs special drivers to work and is not just plug and play with Windows 10, then unfortunately it sounds like it won't be compatible with FLX S. If you have any questions let me know. Edward