Edward Z88

Hello, That's correct. The behaviour of the Grand Master changed in ZerOS 7.9.3, so that now on boot the Grand Master level will be at full, irrespective of fader level. This allows you to then grab control, by level matching the Grand Master fader. This allows for any Playback fader to be configured as a Grand Master, and also means that if you're not someone who ever uses a Grand Master, you don't need to touch it. It also means that if you were in a lighting state, turn the console off, when you reboot FLX will recover the lighting state, even if the Grand Master has been adjusted since. If you have any queries please let me know. Edward

Hello, Currently there isn't the ability to prevent an individual playback from being stored into cues. You do however have a couple of options, depending on your current setup. One option is to disable SmartTag. With SmartTag disabled, only programmer values will be recorded. Programmer values are indicated by red intensity values in the Output window, and highlighted parameters on the encoder wheels. Therefore information from playbacks wouldn't get recorded into your cues when SmartTag is disabled. You can disable SmartTag by pressing and holding RECORD or UPDATE, and tap SmartTag from the Options menu. Your other option is to use an Inhibit playback. For this, program all of your cues with your working light playback at full, therefore adding them to every cue. Then go into the settings of your Working light playback. This is done by holding SETUP and tapping your working light playback's button. From the Intensity mixing options. choose "Inhibit". This playback fader now works a little bit like a Grand Master but just for the channels recorded in the playback. You can therefore go into any of your cues, and the working lights will only come on when you raise their inhibit fader. More information on Inhibt playbacks can be found here... http://support.zero88.com/1077997011 Hope that helps, if you have any queries just let me know. Edward

Hi Richard, Many thanks for your comments. Thank you for confirming. Yes this is the latest version of ZerOS software. That's correct- currently the default "Automatic" DMX out means if nothing is patched on a universe, that respective DMX port will be disabled. I have logged your comments as ZOS-8852; we will consider changing this behaviour to avoid confusion. After patching fixtures, whilst viewing the Fixture Schedule you may select those channels you want to edit (eg type 101 THRU 106 ENTER), and then tap the "Address" column header to adjust all of their addresses. Or your other option is to use the syntax 101 THRU 106 @ 201, which will address channels 101 THRU 106 to DMX address 201 through sequentially. In future we are going to allow for the use of AND whilst configuring the DMX address, to assign channels multiple DMX addresses via syntax. OK thank you for letting me know. I haven't come across this before, so will keep an eye on this one. We have seen this a couple of times with the current iOS app. This issue is due to be fixed in the next version of the apps. We'll investigate further how this should behave. Logged as ZOS-8858. Thank you for your thoughts, we'll bear this in mind. The right hand side of the touchscreen are your attribute keys. The left hand side are your function keys, providing extra features and user tools. I do appreciate all of these touchscreen buttons apart from SHIFT and HOME change the screens. OK thanks for letting me know. This feature is on our road map to be implemented in a future software update, logged on our software tracking system as ZOS-7984. We agree, this is logged as ZOS-8223, to be included in a future update. This is due to a feature called "SmartTag". When SmartTag is enabled, FLX will automatically include programmed values from other cues as well as programmer (red) values at the point of recording or updating. This can be disabled at any point in the Record or Update window, by tapping the "SmartTag" button- with SmartTag disabled only programmer (red) values will be included. You should find if you select a fixture that wasn't included when recording the palette, and isn't of the same fixture type as those included in the palette, then it will be greyed out rather than highlighted in the palettes window. Were you experiencing different behaviour to this? Yes currently decimal points are required to know where to break the time. I have noted your comment as ZOS-8859. When using shorcuts such as @@ or @., ENTER is not required to complete the command. Completed commands are ended with a comma and change to a slightly darker yellow, rather than the brighter yellow of the command currently being typed. We should maybe look to make this a more obvious colour change. There are a couple of different options for this. One of which is to use Knockout, which is available to configure as one of the special UDK functions. These can be configured by holding SETUP and tapping an empty UDK, and choose Knockout from the drop down. Now when in a cue you can select a fixture and tap knockout, and it will be snapped out of the cue this once. Next time the fixture is used in a cue it will come back on. To bring the fixture into the programmer the other option is to use syntax in conjunction with a fade time. To do this go into your cue, and enable Programmer Time. Programmer Time can be found by tapping Z, situated on the last encoder wheel. Tap the middle encoder button to enable Programmer Time, and now all syntax and palettes will use this time. You can therefore type your fixture's channel number, @. to turn it off, and it will fade out over the defined Programmer Time. You can then clear your programmer so the fixture can be used again by future cues, either by double tapping the CLEAR key, or to only remove that specific fixture from the programmer, you can customise an empty UDK to be "Clear Fixture". You can then select your fixture and tap your Clear Fixture UDK, and only this fixture will be removed from the programmer. The parameter table can be opened for a fixture simply by selecting it. This will then open at the bottom of the Output window, giving a breakdown of the fixture's parameters. They are indeed very useful! Thank you very much for the comprehensive comments. Hope my comments are helpful. If you have any further queries on FLX, please don't hesitate to contact us. Feel free to email me directly too, if that's easier. Edward

Hi Alan, As Kevin says above, for Move on Dark to occur, you’ll need a cue where the fixture is off before it is on in its new Colour, Beam and Position. If you are going directly from a cue in one colour to a cue in a different colour, some fixtures have a control channel that allows you to shut the shutter when colour/beam/position is changing. This is specific to the fixture. If your fixture doesn’t have this functionality then you’ll be able to insert a cue that turns the fixture off, and then the next cue can automatically follow on to turn the fixture on again. If you have any queries let me know. Edward

Hi Richard, Sorry to hear your first experience with FLX wasn't quite what it should have been. As Kevin asks, could you please confirm the software version running on your FLX? You can find out by tapping Z -> System Information, and in here will be a line of text displaying "Software Version". ZerOS 7.9.4 is the latest, which depending on the age of your console may not be installed. I'll work through your comments below... Hmm that's an odd one, I haven't come across this before. The "Auto" option should be exactly the same as enabling that output's respective universe if something is patched on it. I have logged this on our software tracking system as ZOS-8852 for the software team to do further investigations. Currently when patching, a fixture must be given a DMX address. This can then be removed if you wish, by tapping "Address" -> Unpatch. When working through the second page of Add Fixtures, the cursor/ENTER keys may be used. ENTER will move you on to the next field to fill in. If you type in a DMX address that is in use in Add Fixtures, and then click Finish, you will get an error message. If you enter a DMX address that is already in use and then move onto a different field, it will revert back to the suggested next available address. Could you elaborate a little on where you find this is an issue? In the Fixture Schedule, using arrow keys you can see what cell is highlighted by the blue cell. Added as a feature request. Logged as ZOS-8853 In the Fixture Schedule, if you hold SHIFT and tap a column header, the list will be sorted by the column information. Therefore to sort by DMX address hold SHIFT + tap "Address". Unpatching a fixture can only be done in the Edit DMX Address window, or by confirming a DMX address conflict. Hmm haven't come across this before. Assigning a fixture multiple DMX addresses is done in the fixture's Edit DMX Address window, rather than in Add Fixtures. Could you elaborate a little on this? When doing this you will simply need to move the faders to the level the playbacks are currently at (shown in the MFF window), and the faders will then re-gain control of the playbacks. We call this level-matching. Currently attribute keys will turn off when a new command is typed in the command line. I have logged a review into this behaviour as ZOS-8854. I'm not sure I understand what you mean here, could you expand a little? There is a new version of the iOS apps coming soon which greatly improves connectivity, and provides support for Apple Watch. Logged as ZOS-8855. The thought behind the Remote is that any time you try to connect to the console from any device you will require the password. You can disable the password in SETUP -> Remote, if you wish, which in most cases still provides sufficient security as the wireless network password is required to connect your device in the first place. Hmm ok thanks for letting us know. Again, as I said the new apps will be on their way soon, which should solve this. Pressing SETUP will take you out of Setup, as long as you aren't in a separate window within the console Setup. The HOME key is purely used to Home fixtures or program defaults and max levels, rather than being used to access a "Home screen". Do you remember whether any front panel buttons were lit, or did it just seem that the buttons were unresponsive? If this happens again, please let me know. To skip through Next/Previous fixtures use SHIFT + LEFT or RIGHT arrow (You can actually also use SHIFT + AND or EXCEPT). There is currently no way of controlling raw DMX data on FLX. This is something we get few requests for, but may look to implement in future. Is the Avolites PowerCube RDM enabled? It doesn't seem to be advertised on Avo's website. If it is and RDM is enabled, it should be discovered by the console if you are going directly into the PowerCube, or via RDM enabled DMX splitters. It will probably be patched as an individual fixture as FLX will see it as one device. Under the Beam attribute for the fixture will then contain each of the dimmer channels. If RigSync support for the PowerCube is something you're interested in let me know, and we will look to add full support for this device, so that it is patched correctly as separate dimmers, in the same way it would if connecting to Betapack 3 or new Chilli dimmers. Again thank you for your comments. We always value customer feedback to improve our products. If you have any queries please don't hesitate to let me know. Edward

Hi Mac, Great, no problem at all. If you have any queries configuring Tracking Backup just let me know. Edward

Hi Dave, Great, really glad to hear it. Edward

Hello, Currently you cannot use the playback GO button when the Fader Function is set to Manual Fader 2-way. Cue transitions are changed by the fader's movement. We have only had a couple of requests for this so we may look to add this functionality in future. Edward

Hi Chris, It's fairly rare we have customers reporting touchscreens not working with FLX. Is the Monitor you're looking at from one of the manufacturers listed on our article here... http://support.zero88.com/Consoles/ORB-XF/975056031/Compatible-touchscreen-monitors-with-ZerOS-consoles.htm If possible I think it would be worth trying before you buy. Any queries let me know. Edward

Hi Mac, As you have both Capture and Remote using DHCP it means these different protocols are on the same IP address. I would recommend setting Capture to 192.168.0.10 rather than DHCP. You should find your laptop will now listen to FLX. You will still be able to connect directly into your laptop if you don't wish to use the Remote. You may find you'll need to disable/re-enable Capture after unplugging network cabling. Any queries let me know. Edward

Hi Mac, Hope you're well. So I'm guessing your network setup is FLX plugged into one Ethernet port of your wireless router, and your PC plugged into another running Capture? On FLX is Capture set to use a static IP address? Is the Remote on FLX set to DHCP? If so you can confirm the status of these settings outside of Setup, by tapping Z -> System Information -> Network Overview. At the top you should see a line of text displaying "DHCP address", and then list the IP you have been assigned. Can you confirm this is in the same range as your iPad, and that it is reporting no errors? You can find out your iPad's IP address in iOS by tapping the Settings app -> WiFi -> Tap your router's network. Your IP and subnet will be listed. In a simple network like this, as long as the first 3 values of the IP address are the same, and the last value is different on all devices connected, you should be fine. After changing configurations such as changing IP addresses or swapping out Ethernet cabling, make sure you disable and re-enable the remote connection, otherwise you may experience a socket error. If you have any queries as always just let me know, Edward

Hi Erics, There are many improvements we wish to make to PhantomZerOS including GUI improvements and keyboard shortcuts. Hopefully you'll find ZerOS 7.9.5 improves this too, adding many GUI improvements to Setup and other settings windows. Any queries let me know, Edward

Hi Chris, The parameter table shown at the bottom of the Output Window in your screenshot, should show you whether an effect is running or not. You will see the effect palette number written instead of a value percentage for the parameters included in the effect. In your screenshot, cue 1 in playback 6 is displayed as yellow, meaning it hasn't yet been triggered. If you would like to preview this cue, make sure that you are viewing its playback, and then tap "Preview" at the bottom of the Output window. Selecting the fixtures included in this cue will then open the parameter table to show you what levels parameters are at, and whether any effects are included. Any queries let me know, Edward

Hi Chris, This is scheduled to be included in ZerOS 7.9.5, which should be released before Christmas. Any queries let me know. Edward

Hi Chris, Yes this is something we’re looking to implement on FLX. This functionality is already on Solution consoles so we will continue to unify functionality across ZerOS. Any queries let me know. Edward

Hi Matt, Thank you for the information. The behaviour of the Grand Master you describe is correct, therefore I don't believe this is the cause of the flashing fixtures. After rebooting the Grand Master level will always be at full, irrespective of what the fader is currently set to. As you have found you can then level match the fader to grab control of the Grand Master level. Edward

Hello, After Loading in a Jester show file, you'll then have to leave the console's Super User/Setup mode. You can do this by going back to the main Super User/Setup menu. Therefore press OK on the Load Show success dialogue, and then cursor down to OK in the Load/Save options to take you back to the main menu. You'll then be able to press and hold the MODE button, which will take you into the mode you were last in. If you are taken to Preset mode, press and hold MODE again to enter Program/Run mode. If you are in Program mode tap MODE once to flip to Run mode. You'll then be able to run your programmed submasters and memories. Your safest bet is to only unplug/plug in USB sticks whilst outside of Super User/Setup. That way there's no risk of the console trying to read or write to it whilst unplugging. Even if you were to do this and the console did freeze, you would likely be able to power cycle and be where you left off. Hope that helps, any queries let me know, Edward

Hi Dave, OK great thanks for letting me know. If you have any queries don't hesitate to contact me. Edward

Hi Phil, Different view options are available by tapping the SPECIAL key. To layout your palettes in quadrants, firstly view Desktop 2 using the desktop selection in the bottom left corner. You can name the currently viewed Desktop by tapping NAME and then tap the desktop select button. Now open the first palette window you'd like for the top left quadrant. To open different windows hold SHIFT + tap the relevant key. Therefore for Colour Palettes hold SHIFT + COLOUR. If it doesn't appear, under the Selected Window Options row of the MFKs, tap "Screen" until it opens. Then tap "Size", which will loop through the different sizing options. Repeat this until you have the 4 quadrants filled. This configuration will then be saved in the show file. Hope that helps, any queries let me know. Edward

Hi Matt, Hmm that's odd that the fixtures are still flickering despite RigSync being disabled. How is this system cabled? Is there one long DMX daisy-chain around all the fixtures, or does this run via a splitter/buffer? If so what make/model is the splitter? If you try addressing your fixtures in the range of DMX address 300+ do they continue to flicker? Edward

Hi Both, FLX has rugged power management, meaning if you try to draw too much current from a USB port it will be automatically switched off, rather than start to pull the voltage rail down. FLX S consoles however don't have this sort of management, so I would recommend routing through an active/powered USB hub before connecting more power-hungry USB devices. Any queries let me know. Edward

Hi Dave, Glad that solved the issue for you. Have you tested the fader button LED in test mode? If not that would be worth double checking. To do this switch your FLX S on with the SETUP key held down. The console will then boot into Test mode, and you’ll see an image of the front panel in the touchscreen. Every button you now tap should light, as shown on the touchscreen. Test button 2 and see if it lights. If not unfortunately there is a hardware fault with your console. Your best bet will be to contact your distributor you bought the console from, who should be able to arrange a replacement for you if you can show it’s an out the box problem. If you have any queries let me know. Edward

Hi Dave, Ah I see the issue. If you tap SETUP -> System Settings, and scroll down to the Operational Settings section, it sounds like the "Show Record and Update Window" setting is set to Internally. The default option is When Held, which means in most cases you can access the num pad in the Quick Access functions, but if you require access to the Record/Update options you can press and hold RECORD or UPDATE. Therefore set this to "When held", exit Setup, and now you'll be able to tap RECORD -> Z/SHIFT -> type your cue number -> tap your playback to store this to. Hope that helps, any queries let me know. Edward

Hello, Great thanks for letting me know, keep me posted. Edward

Hi Matt, RigSync was introduced in ZerOS 7.9.3, which probably explains why this has only recently just started to become apparent. Thank you for attaching your show file. I have taken a look, and there's nothing obvious there that may be causing this. As this show file doesn't have movers patched, I haven't been able to recreate the position issue you described. You can try reinstalling the software if you wish, but I don't believe this will solve your issue. When you say the playback didn't work, did values appear in the Output Window when you raised it, or did it seem completely "dead"? At the point of recording that playback, was the fader at the bottom of its travel? Robe are top of the range fixtures and Pointes are RDM enabled, so you would expect them to receive RDM data correctly. It is only fixtures with poor RS485 implementation and are not RDM enabled, that mistake RDM packets for DMX data, resulting in a fixture flickering. If RigSync is enabled, the console is still sending the DMX data to the fixture correctly, which is why parking your fixture doesn't make any difference. Unfortunately the issue is caused by the fixture incorrectly interpreting the data it receives. You should find disabling RigSync solves this, as only DMX data will then sent from the console. You may also find that addressing the problem fixtures to a DMX address greater than 255 also solves the flickering, due to data rate. Any queries let me know. Edward