Edward Z88

Hello, Welcome to the Zero 88 Forum. Jester consoles have a VGA output on the rear panel for an external monitor output. Any monitor with a VGA input should work with the Jester. If you have any questions let us know. Edward

Hello, To Lamp On the Mac 550, select the fixture, and tap "Beam" to go to the Beam controls. Then dial the "Shutter, Strobe, Control" parameter until you reach "Lamp On". If you are on a FLX range console, you can tap the middle encoder button of the "Shutter, Strobe, Control" parameter, and then choose "Lamp On" from the touchscreen. If you wish you can then record a Beam palette, to give you a shortcut to the Lamp On command. Hope this helps, Edward

Hello, Yes it is. To do this, when you update the cue, you can disable the “SmartTag” option in the Update options. When SmartTag is disabled, only manual control values will get included, not values form another playback. For information on the SmartTag feature, see here… https://zero88.com/manuals/zeros/cues-playbacks/record-options/snapshot-smarttag#smarttag Hope this helps, Edward

OSC triggers are on the list, as an addition to the Triggers tab of Setup. Edward

Hi Roan, As Kevin says, FLX can receive MIDI, but not output MIDI triggers. The MIDI output is for connecting other devices on the MIDI daisy chain so they can all receive the same signal. For more information on MIDI see the link below… https://zero88.com/manuals/zeros/setup/triggers Hope this helps, Edward

Hi Jean, No problem, and many thanks for the feedback. Edward

Hi Jean, Let's see if others have any suggestions. It may also be worth a post on the Blueroom technical forum for a wider reach of product suggestions... https://www.blue-room.org.uk/index.php?showforum=2 No problem at all - just let me know if you have any questions. Edward

Hi Jean, Our Splitter 8 is RDM compliant... https://zero88.com/data/splitter8 This also has the added benefit of the Fix Switch. More information here... https://zero88.com/manuals/splitter8/fix-switch Edward

Hi Jean, I have checked, and "0181" is the ID of the S4 Lustr. Therefore RigSync has found one of these fixtures. Interestingly, RigSync seems to be detecting that the fixture is in "Mode 0", which obviously doesn't exist. This is why the fixture is appearing with its ID name, not the true text name. Were you going via your splitters at the time? If so it sounds like RigSync has managed to get some data over RDM, but not the full picture. That is correct. RDM devices will report a UID, which in theory is not shared by any other fixture - a bit like a MAC address in the world of Ethernet and Wi-Fi. If you patch fixtures manually, that are then discovered by RigSync, the console has no information to tell it that you chose to patch those fixtures manually, and therefore it sees them as new fixtures. This will likely result in the DMX address of your fixtures being changed by RigSync. This is because it will see they conflict with "other" fixtures in the console - the ones you patched manually - and so readdress them over RDM. This is where segregating your DMX network, and choosing to use or not use RDM for whole DMX lines is beneficial. This also helps with ensuring non-compliant fixtures won't be affected. When in the Fixture Schedule, it is best to change the mode of a single type of fixture at a time. For more information see the link below... https://zero88.com/manuals/zeros/patching/fixture-schedule/change-fixture If the console discovers your RDM fixtures, and you decide for those particular fixtures you wish to patch them manually, you could delete the discovered fixtures in the Fixture Schedule. Doing this, will mean despite the console knowing they are still there on the DMX line, it will ignore them, and know you don't wish to use them. Resetting the console, would allow RigSync to patch those fixtures again. For more information see the link below... https://zero88.com/manuals/zeros/setup/universes/remote-device-management We do have an internal version of ZerOS software, which has a dedicated "RDM" tab within Setup for this log. Currently the information is very "raw", and not something we'd want to baffle a user with. Adding a nice RDM sniffer is definitely something we wish to add. This feature is logged as reference number ZOS-9042 on our system. If you have any questions let me know. Edward

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