Edward Z88

Hi John, Mandy will be visiting PLASA Glasgow so you will be able to chat with her, however we have chosen not to have a stand there this year. Edward

Hi Jason, We have enhanced the Remote connection to ZerOS consoles which has required an update to the apps to be compatible with ZerOS 7.9.3. The iOS version has already been released, however we are still waiting for the GooglePlay store ZerOS Apps to be updated. Edward

Hi Simon, Hope you're well. I have replied to your email, but this issue seemed to have been caused by the Master Playback being set to LTP (Latest Takes Precedence) Intensity Mixing in it's Settings. Setting this back to HTP resolved the issue. Hope that helps, any queries let me know. Kind regards Edward

Hi Kevin, Yes ZOS-8389 is to do with Allow Stomping not working correctly, LTP Intensity Mixing is correct. Stomping is used to automatically release a Playback once all of the parameters it is currently controlling are given a new command from a different Playback. For example if Playback 1 is controlling fixtures 1-6 at 50%, and Playback 2 is controlling fixtures 1-6 @ 75%, when I put Playback 1 to full the fixtures would go to 50%, and when I add in Playback 2 the fixtures would go to 75%. If I took Playback 2 down the fixtures would drop to 50% as Playback 1 has them at that level still. However if Playback 2 has “Allow Stomping” enabled it is allowed to “Stomp” over Playback 1, and therefore as soon as it goes above 50% Playback 1 actually releases. This is useful for example if you have a different dance on each Playback that you want to work your way through. Hope that makes sense! There are a few FLX T-Shirts left! Kind regards Edward

Hi Kevin, Again apologies for our delays on this one! Yes using LTP is the correct way to do this. Allow Stomping is a method of allowing Playbacks to automatically released once every parameter has been given a later command from a new playback. This however appears to not be functioning as expected, so I have logged this as ZOS-8389. How I woukd do this is setting Playback 1s fader to control Colour under it's Settings. That way to snap the Colour in, you can snap the Playback up over the top of the Master Playback, but then to release you can fade out the Playback where the colour will fade into the Master Playback's colours. There is no way of setting some Playbacks to ignore LTP rules for attributes. Therefore the only way to prevent the colour changing when you advance to cue 2 is to remove the colour data. This can be done by selecting the fixtures whose colour want to remove, tag colour, tap UPDATE and choose "Remove" from the Update Options. Then tap the Playback's GO button to finish the command. Hope that helps and all makes sense! Kind regards Edward

Hi Kevin, Apologies for our delay in replying. We're looking into this still at the moment, but yes this is a bug affecting Intensity effects when updating them. This is logged as ZOS-8368. The best way to avoid this issue is after editing your effect speed, rather than tapping UPDATE tap RECORD, and save it as an effect palette. Then use this palette to update the cue with the edited intensity effect. Alternatively if you are viewing the Playback containing this Effect, you can use Speed Override to change the speed of the effect live. Will feedback when we find out more information. Kind regards Edward

Ah ok well thanks for letting us know! Edward

Hi Peachy, Thanks for letting us know. We haven’t come across anyone else with this issue. However it sounds as if your SunStrips are not truly DMX compliant, and are receiving the RDM protocol used by RigSync and trying to interpret it as DMX data, which you’re seeing as a flicker. If you wish to use the SunStrips on the same DMX Output that has RigSync enabled, try addressing them to a DMX address in the second half of the universe (for example DMX 256-512) as this may stop the flickering. Kind regards Edward

Hello, Yes as suggested tap “Create Effects Palettes” again. This can be done on Solution by tapping EFFECT, and then page down on the MFKs to get to the last page, and you should find the Create Palettes MFK. These effect palettes are then compatible with your new fixtures. Hope that helps Edward

Hi Fred, What you can do is add a Virtual Intensity channel to the fixture using the Fixture Editor software with a default of 255. Then set the Shutter/Strobe to be scaled by virtual intensity with its default set to intensity at maximum. This then allows the fixture’s channel fader to scale intensity, and you can then use the encoder wheel to access strobe. Hope that helps Edward

Hi Thomas, On Solution, the display in the bottom right corner is the 2-Preset Time (the same time palettes take when TIME is held) set under Special, not the Programmer Time. To see the Programmer Time tap SUBMASTERS and you'll be able to see the Programmer Time playback's position in seconds or minutes. To activate programmer time you'll need to tap the Playback's button. You will then see it go from dark to light blue in the MFF Window. Again on ORB Series, check that you've tapped the Programmer Time Playback's button to activate it. This is indicated in the bottom right monitor display which will go red, and also shown in the MFF Window on ORB XF. You can open the MFF window by holding SHIFT + FADER FUNC. Hope that helps, Edward

Hi Chris, Glad you like the videos! How did you know about what video is lined up for Christmas Day?! Edward

Hi Thomas, Yes Programmer Time is available on all consoles running ZerOS 7.9.3. Solution & ORB therefore have 2 methods of fading palettes, using a Playback to set the Programmer Time, or if you don't want to use a Playback holding TIME and tapping the palette you want to fade into. As you say this time for Solution consoles is set under SPECIAL, which is the same time the 2 preset cross fade uses. Hope that helps Edward

Hi John, Yes try Ian’s suggestion. I haven’t come across Security Essentials popping up saying there’s an issue, so maybe try giving it a go again. Kind regards Edward

What issues are you finding with the encoders? We spent quite a bit of time for ZerOS 7.9.3 getting the sensitivity right for all consoles, are you finding they aren't as you'd expect? Edward

Hi James, In ZerOS 7.9.3 you are able to adjust wheel sensitivity per attribute by holding SETUP + tapping the attribute you wish to setup. Edward

Hi Tom, Have you got a Phantom Unlock Dongle plugged in to the laptop running Phantom and ensured that the ArtNet settings match those on Capture? (for example a matching Universe for each port). What are the IP addresses and subnets of the 2 laptops? I would set one to be: 2.1.1.10 (subnet of 255.0.0.0). and the other to be: 2.1.1.20 (subnet of 255.0.0.0). Have you tried plugging both laptops into an Ethernet switch, rather than directly into the other laptop? On Phantom, in Setup (SHIFT + F10) under "Network Devices" do you see the Capture Laptop appear? Kind regards Edward

Hello, To change the direction of an effect dial the "Speed" wheel down, and you will find it goes into negative values, which means the effect direction is reversed. Hope that helps, Edward

Haha yes we did notice that at the time of recording and were thinking about doing it again, but we figured people would understand what he meant! Edward

Hello, It sounds like for this you need to use Speed Override. This allows to speed up or slow down the cue transition using the Speed Override pot. Therefore set an estimated time you think it will take to transition from one cue to the next, then press GO to advance into the cue, and during the fade you can use the Speed Override pot to adjust the speed live. You can assign Speed Override to a fader if you wish by holding SETUP and tapping a blank Playback (submaster) button, and then choosing Speed Override. This will then work in exactly the same way the pot does, and 50% fader travel will be no override. The latest software is ZerOS 7.9.3, not 7.9.2.50, which is available to download here... https://eatonfilesharing.app.box.com/v/ZerOS/folder/42009315015 Hope that helps, any queries let me know Kind regards Edward

Hello, What software version are you running? If you are running ZerOS 7.9.2 or later the operation of the console is very different to how the original manual describes, as outlined in this document... http://nr1.s3.amazonaws.com/kb/2AD62C9/3879A76B/3AF10D9F/1/changes to operation of solution consoles within zeros 7.9.2 and later.pdf The latest manual can be found here... http://zero88.com/manuals/IM9210 - Solution Manual Issue 2.0.pdf The software version can be found by clicking "Other Windows" in the top left of the Output Window, and then clicking "System Information" from the drop down. When you say transfer I presume you mean Copying cues? If you are running ZerOS 7.9.2 or later copying cues is done in the Copy window you have been seeing. If you are viewing the cue list containing the cue you wish to copy, tap COPY, type the cue number you want to copy from, press ENTER, then type the cue number you want the copy to be numbered as, and then tap ENTER. You will then have made an exact copy of the cue. Hope that helps, any queries let me know. Kind regards Edward

Hello, Yes that would be great, please send to: EdwardSmith@Eaton.com Kind regards Edward

Hello, Really glad you like the features of your FLX S48. We have just released a new software version for FLX S which I highly recommend you installing. We have found a couple of issues with patching that I guess is what you described as the "teething problems"! These issues are fixed in this version which you can download from our website here... https://eatonfilesharing.app.box.com/v/ZerOS/folder/42009315015 Download the ZerOS - 7.9.3 (USB).zip file, and extract it to the root of a USB stick. Then on the FLX S tap SETUP -> Load File, and select the software file and the console will perform the software update. Software updates wipe the console's memory, so make sure you save the current show first to USB before updating. The new software also changes the way the console behaves so that by default you have the cue list in the internal touchscreen. You can change this in SETUP -> System Settings -> Monitor Enable/Disable - this option changes which monitor the VIEW key effects. When you say "lines" on the screen, could you give a little more description or even take a photo and send it over? We haven't come across this before and so it would be good to know what's going on there. Is this still happening after updating the software? In the next software update we will be moving over to a new fixture library that will prevent the duplication you have described. Hope that helps, any queries please don't hesitate to get in contact. Kind regards Edward

Hi Joe, Speed Override only effects the Playback you are currently viewing (by default this is the Master Playback). To View different Playbacks hold the VIEW key and press the button of the Playback you wish to view. The Speed Override will then effect this Playback. Hope that helps, Edward

Hi Ziglight, Just to clarify, SmartTag is still tracking, and will Record the changes of fixtures, however will also automatically tag parameters that have changed from the previous cue, or intensities that are above 0% from a different source. It will also ignore parameters of a fixture with an intensity of 0%. Therefore in your example, with SmartTag enabled you could update the first cue and all subsequent cues will have changed colour, until there was another colour change. The way you described was non-tracking/ Cue Only. Tracking can be enabled/disabled from SETUP -> System Settings Juste pour clarifier, SmartTag est toujours suivi, et enregistrera les changements d'appareils, mais marquera aussi automatiquement les paramètres qui ont changé de la cue précédente. Il ignorera également les paramètres d'un appareil avec une intensité de 0%. Par conséquent, dans votre exemple, avec SmartTag activé, vous pouvez mettre à jour le premier repère et tous les repères suivants auront changé de couleur, jusqu'à ce qu'il y ait un autre changement de couleur. La façon dont vous avez décrit était non-suivi. Le suivi peut être activé / désactivé depuis SETUP -> Paramètres système Hope that helps, Edward