Edward Z88

Hi Steve, This is the correct behaviour. Pressing a playback’s go button, will go to that cue at the value of the playback’s fader. This allows you to advance through cues without intensity, so you can then raise the fader when you’re in the right cue. After triggering the playback, you will need to raise the fader manually prior to tapping the playback’s go button. Or, leave the fader up prior to triggering it. Edward

Hi Steve, What method are you using to trigger the stack - is that using the advanced cue macro trigger syntax, or simply using an Add/Release macro? If you trigger the playback manually using its Go button, it will trigger at the fader’s level. This chase functionality would have changed in ZerOS 7.9.2. If you want to manually step through lighting states, then not turning the playback into a chase and simply using Go Snap to advance through the cues is the best method. Hope this helps, Edward

Hi Steve, The syntax “Gx” can be used to trigger a whole stack. The syntax “Tx/y” can be used to trigger a specific cue within a stack. More information can be found here... https://zero88.com/manuals/zeros/cues-playbacks/cue-settings/cue-macros Could you elaborate on what you’re trying to achieve? Triggering a playback using trigger macros will trigger it at 100%, irrespective of that playback’s fader level. Hope this helps, Edward

Hi Steve, Thanks for confirming, let me know how you get on after performing the software update. Edward

Hi Steve, Sorry to hear this, thanks for letting us know. We haven’t had any other reports of this, so I am going to guess this is an issue specific to how the app is handling data from OrbXF for the screen resolution of the Galaxy S10. Can you select palettes correctly using the Z Monitor app? After updating the software, let me know whether this solves the issue. If you have any questions let us know. Edward

Hi Neil, The ability to auto trigger any cue in a stack x seconds after the very first in that stack is an interesting idea, thanks for the feedback. I guess the assumption here, is that if you are synchronising lighting to an audio track, you are likely to have MIDI connecting the two systems. Starting a time code clock at the same time as the audio source, then means you don’t even need to press GO on the FLX at the right time, and you don’t even have to program cues in the correct order - they will just run at the specified hour, min, second and frame when FLX receives it. Edward

Hi Neil, For the ultimate method of synchronising lighting cues to an audio track, Timecode triggers can be used. Unfortunately this is only available on the FLX console, not FLX S consoles. FLX consoles also have real-time triggers, so in your New Year example you could have a cue running at 11pm or midnight on the dot. See David’s link above he has helpfully posted for more information. Something you may wish to try, is programming your cues on the console, but then load the show file into Phantom ZerOS on PC, running as an OrbXF desk type. OrbXF consoles have a “Learn” function. This allows you to tell ZerOS to start learning the times of a cue stack, and as you press the Go button in real time, the console will calculate and add in the Auto timings. You could then save the show, and then load it back into your console. Hope this helps, Edward

Hello, If you want relay channels to default to on whenever your console is powered, patch your relay channels in Add Fixtures using Generic -> Non Dim -> Default On. Hope this helps, Edward

Hello, ZerOS 7.9.9 has now been released... https://zero88.com/zeros#download If you have any questions let us know. Edward

Hello, ZerOS 7.9.9 has now been released... https://zero88.com/zeros#download If you have any questions let us know. Edward

Hi Dave, No, FLX S24 and FLX S48 consoles do not have an internal battery. If you have any questions let us know. Edward

Hi Jake, No problem at all. Keep an eye on our website and social media as we'll post when ZerOS 7.9.9 is released. If you have any questions let me know. Edward

Hello, Really sorry to hear you have had difficulty recording intensity effects. We are aware of an issue in ZerOS 7.9.8 software, which results in intensity effects not recording on some fixtures. This has been fixed by our software team, and we are aiming to release ZerOS 7.9.9 next week to fix this. In the meantime, intensity effects can be recorded correctly onto UDKs. If you have any questions please let me know. Edward

Hello, When you apply a palette to some fixtures, you will see you get the palette code displayed on the encoders, such as "C20" for colour palette 20. If you then record a cue, the cue records the fact those parameters are using palette 20 - they do not record the raw parameter values. This allows you to update palettes, and any cues recorded using the palette, will have updated too. More information here... https://zero88.com/manuals/zeros/palettes/referencing-palettes If you have any questions let me know. Edward

Hi Caffrey, Welcome to the Zero 88 Forum. We are hoping to release a “Release Candidate” of ZerOS 7.9.9 next week to our forum beta testers. All being well with that, we will then be able to release ZerOS 7.9.9 officially. Therefore if you need to access the Intensity wheel for these fixtures on Monday, I’d recommend rolling your software back to ZerOS 7.9.7. ZerOS 7.9.7 can be downloaded from the link below... https://zero88.com/zeros#legacy Please drop us a link to the missing fixture’s manual to fixturesupport@zero88.com, and we’ll add the fixture to the list to be included in a future fixture library release. I hope this helps, if you have any questions let us know. Edward

Hi Sean, Welcome to the Zero 88 Forum. Have you ensured that the preheat levels, and manual control levels, are set to their defaults? Apologies for checking the obvious, but have you ensured the bypass switch hasn’t been activated for the channels at full? If you have any questions let us know. Edward

Hi @el gordo, Welcome to the Zero 88 Forum. Really sorry to hear you have come across this issue on Orb as well. To view the functionality of the Orb encoders, you can view the "Wheels" desktop on the external monitor. The latest full library that was compatible with ZerOS 7.9.7 was GFT40. We now use a new format for our fixture libraries (ZLBR), which will not be compatible with ZerOS 7.9.7 and earlier. Our software team have already fixed the issue, which will be included in ZerOS 7.9.9, currently scheduled for release by the end of the year. If you would like access to a pre-release version of software containing the fix, please send me an email. If you have any questions let me know. Edward

Hi Steve, OK thanks for confirming. Seems odd that the only change to the system is a new iPhone. The console should automatically appear in the list of consoles in the ZerOS Remote app. You shouldn't have to manually type in its IP address. If this doesn't solve it, feel free to email me a list of the devices you're using for your remote network, how they're connected, and the IP addresses they are using. Edward

Hi Mac, Thanks very much for sharing the pictures. That looks fantastic, very nice setup. Looks like a really effective way to make your life easier speeding up the setting up time, and ultimately, keep it all safe! Edward

Hi Steve, If you are running iOS 14.2 on your iPhone SE, you should have received an iOS pop-up message upon opening the ZerOS Remote app for the first time, stating that you need to grant the app access to other devices on the network. If you have not seen this message, go to the iOS Settings app, and choose "Privacy" -> "Local Network". You should see Z Remote listed. Ensure that it is switched on to give it access to the local network. I hope this helps, if you have any questions let me know. Edward

Hello, Essentially, Mood Boards are just shortcuts to colour values. Therefore if you apply a mood board, and then record this to a cue, you are just recording raw colour values, with no reference to the mood board you used. If you wish to keep track of the colours you are using in your cues, I would recommend using colour palettes. You can therefore record the mood boards you wish to use as your own colour palettes, and then these can be used to record your cues. This means you can easily update your colour palettes, and any cues that used them will be updated too. It also saves you having to keep finding the colours you need within the different moods. Hope this helps, if you have any questions let me know. Edward

Hi James, Welcome to the Zero 88 Forum. If you are using a single Ethernet cable between Capture and your Mac, you won’t need to worry about setting the Router IP on the FLX S48 CITP settings. However, your IP address of the CITP protocol on FLX S48, must be in range of the IP address of your Mac. Your FLX S48 CITP must have the same subnet as your Mac. Therefore if you wish to use the IP of 192.168.1.101 for your FLX S48 CITP settings, set the subnet to 255.255.255.0, and then change your Mac’s IP address to 192.168.1.x (x could be any number between 1-254, which doesn’t conflict with your FLX S48), also with a subnet of 255.255.255.0. After changing the IP address of your Mac, I’d recommend restarting Capture, and FLX S48 and Capture should then be talking. (I have moved the topic into the FLX S forum, rather than FLX forum). Hope this helps, if you have any questions let me know. Edward

Hi Josh, That's great, glad to hear it. If you have any questions let me know. Edward

Hi Josh, Thanks for confirming. Please email us a picture of the console's serial number to support@zero88.com, displayed at the top of the LCD when you open Super User, and we will be able to advise the next step. If you are able to, it would also be worth copying the Jester4.1 software onto a different USB stick if you have one to hand, and try booting the console with the left and right arrow keys held down again. If you have any questions let me know. Edward

Hi Josh, Thanks for the photos. When you chose <USB Host>, did you have Shift held down? If you have any questions let me know. Edward