Edward Z88

Hi Jean, Many thanks for attaching the show file. I have been using your show file, following your steps, trying various combinations, and have been unable to replicate the issue. I will continue to investigate this. I noticed in your show file there is a fixture that has been discovered by RigSync called "RDM:0181". What fixture is this? If you have any questions let me know. Edward

Hi Jean, That's frustrating. In this case it does seem like these splitters are not truly RDM capable. If you have any questions let me know. Edward

Hi Jean, No problem! Let me know how you get on following these tests. Edward

Hi Jean, Many thanks for the detailed description. This is a bit of a case of déjà vu for me. I seem to remember several months ago, a customer reporting exactly this issue, when daisy-chaining these splitters. I'll have to check back through our records when I'm next in front of my laptop. From memory their issue was specifically when daisy chaining the second of their splitters from an output of the first. I believe daisy-chaining the second splitter from the first splitter's Thru port rather than an output was fine. I'd have to check that though. It seemed to be an issue with how the splitter was retiming the signal. Once this had been retimed twice through both splitters, it had been thrown out of the DMX and RDM specification. If you just use the first splitter, disconnecting the second, do the fixtures connected to the first splitter respond correctly? If you have any questions let me know. Edward

Hi Jean, No problem. We will investigate this to see if we can replicate the issue. If you are able to replicate the issue, a show file and the steps you took would be very helpful. Our system is internal only, however we are always more than happy for console users to suggest features, and we can then either log the suggestion if it is a new request, or raise the priority of an existing request. Feel free to do this via the forum or email. Will take a look. Edward

Hi Peter, No problem. If you email me the console's serial number, I will be able to confirm when this console was manufactured. Please don't post it here. If you have any questions let me know. Edward

Hi Pete, If your FLX S24 is saving show files in the .isf format, and is unable to load .zos format show files, this means your console is running out of date software. The show file format changed from .isf to .zos in ZerOS 7.9.8. The latest software for FLX S24 consoles is ZerOS 7.9.9, which can be downloaded from the link below... https://zero88.com/zeros#download Release notes are also available from this link, detailing the installation instructions. Both .isf and .zos show files can be loaded into ZerOS 7.9.9. If you have any questions let me know. Edward

Hi Jean, Welcome to the Zero 88 Forum. Really glad to hear you have just received your FLX console. Sorry to hear this. This is not an issue we are aware of. Would you be able to email us a copy of the show file you were using when you experienced this? Our support address is support@zero88.com That is correct. Currently when you change a fixture, the replacement fixture will use the name of the new fixture, not the original custom name. The ability for replacement fixtures to use the original custom name is logged on our system as reference number ZOS-10745. If you have any questions please let me know. Edward

Hi Kevin, No problem. Yes good idea. We can use that as an example. Edward

Hi Kevin, ZerOS will recognise a remote switch "press" and "release". ZerOS only listens for the press, to trigger either a specific cue or a macro. Keeping the remote switch "pressed" is fine. ZerOS will not register a "repeat" instruction and do something different. Correct - potentially if we add the ability to map remote switches to front panel keys, we would listen to both the repeat and the release, but currently the release is ignored by ZerOS. Remote Switches can either trigger a cue, or a macro. Therefore your Remote Switch could always trigger a single specific cue number, or it could trigger a go button press via a macro. If you wanted the remote switch to behave like the go button, but with the remote switch disabled at certain times, you could program a macro to enable/disable the remote input. This would simply consist of a series of arrow keys and enters, which takes you into Setup, enables/disables the option, and then exits Setup. This macro could then be triggered by the cue, prior to when you want to disable/enable the remote input. Yes - as the macro to press the go button will have already been triggered, the "repeat" and "release" of the remote switch will have no effect on the go button. Hope this helps, Edward

Hello, FLX consoles currently do not support OSC commands. Available trigger methods are detailed here... https://zero88.com/manuals/zeros/setup/triggers If you have any questions let us know. Edward

Hello, ZerOS consoles, including Leapfrog 48, will only send Art-Net DMX data, to Art-Net devices that report themselves as an Art-Net receiver. ArtNetominator does not report itself as an Art-Net receiver, and as such Leapfrog 48 will not transmit Art-Net DMX to it. If you wish to test your network, you could use the demo Capture files on the link below, and use the Art-Net protocol... https://zero88.com/manuals/zeros/networking/connecting-to-capture Which Art-Net devices do you wish to control with the console? If you have any questions let us know. Edward

Hi Wosti, The Fader Function options will affect the intensity behaviour, with attributes adhering to cue fade times. Fader controls position, allows you to transfer from whatever position values your fixtures are currently at, to the position values recorded in the current cue you crossfade into. Therefore lowering the fader will send the fixtures back to their previous values. It can't be used as a method of transferring between the cues on the playback. Therefore if you want to control the time of position crossfades between cues, you may wish to configure a Speed Override control to do this. For more information see the link below... https://zero88.com/manuals/zeros/cues-playbacks/special-playback-functions Hope this helps, if you have any questions let me know. Edward

Hi Pete, Hope you’re well. This sounds like the trigger level of the playback has been changed to 20%. To access this option, open the playback’s settings by holding SETUP and tapping the playback’s button. Then choose the Raise and Lower tab from the top. You will then be able to adjust the Trigger/Release level. The default is 5%, however if you want to access the full range of dimming you could adjust this to 1%. For more information on Raise and Lower, see here... https://zero88.com/manuals/zeros/cues-playbacks/playback-settings/raise-and-lower If this doesn’t solve the issue, it sounds like there may be a custom dimmer curve set on those fixtures. This will be due to the cue colour fade. To edit, view the playback the cue is programmed on by holding VIEW and tapping the playback’s button. Then tap on the colour time, which by default is 3 seconds. You can use the encoders to dial this to 0. Hope this helps, if you have any questions let me know. Edward

Hi Lloyd, Welcome to the Zero 88 Forum. Please see the link below, containing information on using the Windows Remote application with FLX S24... https://zero88.com/manuals/zeros/networking/using-the-remote-apps If you wish to connect a laptop running ZerOS Monitor to the FLX S24, you will be able to use a single Ethernet cable between the two. Using this method, you will need to configure static IP addresses in range of one another, for both the FLX S24 and laptop running ZerOS Monitor. For more information on IP addressing, see the link below... https://zero88.com/manuals/zeros/networking/ip-addressing If you have any questions please let me know. Edward

This is logged as reference number ZOS-10640 on our system. Edward

Hi Peter, This is an issue we are aware of. In ZerOS 7.9.9, if you select a dimmer, and an LED RGB fixture together, RGB controls are unnecessarily duplicated on the encoders. Our software team have fixed this issue ready for the next release. If you would like access to this fix prior to the next software version is released, please drop me an email and I can share the beta software with you. If you have any questions let me know. Edward

Hi Romec, This will be coming in a future update, and is already logged on our system. Currently you can only copy and then delete the original. You can do this using Speed Override. For more information see below... https://zero88.com/manuals/zeros/cues-playbacks/special-playback-functions#override Although there is no dedicated “executor” window, you can record snapshot palettes, to record whole lighting states. You could then view the palettes window and use this to recall lighting states for selected fixtures. For more information see here... https://zero88.com/manuals/zeros/palettes/recording-palettes Hope this helps, if you have any questions let us know. Edward

The amazing thing about it, is no power is required at all. An excellent idea. Logged as ZOS-0104. Edward

Hi Daniel, Welcome to the Zero 88 Forum. As Kevin mentions, after selecting your fixtures, go to the Effects window, and you will have a button to automatically create effects. Pressing this button will generate 45 effects for your fixtures. How many effects do you see after doing this? If you have any questions let us know. Edward

Dear All, ZerOS Library 2.1 has now been released. This is available for ZerOS consoles running ZerOS 7.9.8 and later. This release contains 23,831 fixtures. ZerOS Library 2.1, along with further information, can be downloaded from the Library page below... https://zero88.com/library For installation instructions, see the link below... https://zero88.com/manuals/zeros/patching/zeros-library Legacy Consoles If your console cannot run ZerOS 7.9.8 software or later, individual fixture files that you require can be downloaded from the link below... https://zero88.com/fixtures/legacy-consoles/ Additional Fixtures If the fixture you wish to control is missing from the latest library, see the link below... https://zero88.com/library#support If you have any questions, please let us know. Edward

Hi Peter, That is correct. This is because by default, the playback will release when its fader is lowered, and will then trigger again when it is raised. As colour information by default mixes LTP between playbacks (latest takes precedence), raising your colour mix intensity playback, which has colour information at 0, becomes the most recent instruction to the fixture. The fixtures therefore go black. To avoid this, you can disable release on lower on your colour mix intensity playback. To do this hold SETUP, and tap the playback's button. From the playback settings choose Raise & Lower at the top, and then disable Release on Lower, and click OK. For more information see the link below... https://zero88.com/manuals/zeros/cues-playbacks/playback-settings/raise-and-lower It doesn't have to. As per my point above, if you have disabled release on lower, it won't "retrigger" when you raise its fader, allowing you to set a colour, and then raise the intensity over the top. Hope this helps, if you have any questions let me know. Edward

I have added a message to this page to help avoid confusion... https://zero88.com/manuals/zeros/cues-playbacks/record-options Edward

Hi Peter, If you cannot see a SmartTag button in the Record Options window, this means that the console is in global Cue Only mode. See the link below for more information... https://zero88.com/manuals/zeros/cues-playbacks/record-options/tracking#GlobalOptions I hope this helps, if you have any questions let me know. Edward

Hi Peter, The additional universe can be unlocked on FLX S48 consoles by loading in an unlock code. For more information see the link below... https://zero88.com/manuals/zeros/setup/upgrade I hope this helps, if you have any questions let me know. Edward