Edward Z88
-
Posts
3,247 -
Joined
-
Last visited
-
Days Won
77
Posts posted by Edward Z88
-
-
Hi Sven,
The App Store version is actually different to the Build version number found in the About screen.
You are running the latest release apps.
Hope that helps,
Edward
-
Hi Sven,
I can confirm the current version of the ZerOS Remote and ZerOS Monitor apps (v3.3) are compatible with devices running iOS 12.
If you have any queries let me know.
Edward
-
Hi Sandy,
OK thanks for trying that.
If you’re happy to, please send me an email to EdwardSmith@Eaton.com, and I’ll be able to arrange getting you access to the latest beta software. This should solve the problem, and greatly improve the performance of your Leapfrog 96.
Alternatively you can of course wait until ZerOS 7.9.5 is released.
Any queries let me know.
Edward
-
Hi Sandy,
OK thanks for letting me know. Did you try Jon’s suggestion...
On 8/3/2018 at 6:16 PM, Jon Hole said:Try doing a Factory Restore, save the empty showfile to the USB stick, unplug the USB stick, plug it back in, and then try loading that "empty" showfile back into the console.
Now try loading something else. Does that work?
Neil tried out our latest beta version, which I believe solved the problem. I haven’t heard from him recently though.
Just to confirm, are you finding if you Factory Reset the console, you can read USB storage devices ok, but as soon as you start programming the console USB devices don’t appear?
Any queries let me know.
Edward
-
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.
4 hours ago, RichardWilliamson said:- I was using 7.9.4 (Which I think is latest version)
Thank you for confirming. Yes this is the latest version of ZerOS software.
4 hours ago, RichardWilliamson said:- Re. outputs, I was getting no data received on the dimmers until I set an output to universe 1, however I hadn't patched anything at this time so maybe the output wasn't initialised? It was slightly confusing behavior though
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.
4 hours ago, RichardWilliamson said:I am used to working in command line, so patching with the keyboard as far as possible. I found the workflow on FLX which seemed best for me was:
- Open to the patch window (after creating all the fixtures I want)
- Tap on the address column, this might cause a window to open but I clear that
- Type the channel I want to patch, press enter - the patch detail window for that channel appears
- Add the DMX address etc
- Press enter
- Confirm over-patching if necessary
- This returns me to the normal patch view, I now have to press clear, as if I type a second channel number without pressing clear I will edit two channels (however the window doesn't tell me this so i can make lots of mistakes!)
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.
4 hours ago, RichardWilliamson said:It seemed to me that when I changed between the two the output would jump to the current fader positions in a non-nice way (level matching is what I would expect to happen), I would need to get back to the desk to check I wasn't imagining things
OK thank you for letting me know. I haven't come across this before, so will keep an eye on this one.
4 hours ago, RichardWilliamson said:When you press a key, the button is rendered as down (highlighted) and when you remove your finger it should re-render to the normal state. What I found happening regularly (maybe due to bad wifi?) was that my release of the button was missed, so the button would remain pressed. If I wanted to use that button again I would need to press it so it logged a key-up before I could use it again
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.
4 hours ago, RichardWilliamson said:This is just annoying though - once I know the password then I should be able to save it so I can quickly re-connect to the desk. I see no benefit to forcing it to be typed every time.
We'll investigate further how this should behave. Logged as ZOS-8858.
4 hours ago, RichardWilliamson said:So this is where I think the physical button layout is confusing - to me, the buttons surrounding the screen appear to be buttons that change the view - which some of them do (and their light lights up to reflect the view, hence the weirdness when the lights go out) - I would expect the home button to be near the programming keys. Obviously these buttons are now rather set in stone and I'm sure I would get used to them in time!
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.
4 hours ago, RichardWilliamson said:Has been fine since - all the buttons were off, although the 8 segment button for fader pages did its cycle on power up so was connected to something
OK thanks for letting me know.
4 hours ago, RichardWilliamson said:- It would be great to have a list of used fixtures/favorite fixtures when adding new ones - I found it very boring to have to search for a fixture every time I wanted to add one. Ideally the "show" fixtures and maybe bookmarked fixtures would be in a list
This feature is on our road map to be implemented in a future software update, logged on our software tracking system as ZOS-7984.
4 hours ago, RichardWilliamson said:- Similarly, it would be great to be able to search all fixtures (from all manufacturers) in the middle column when you haven't specified a manufacturer - that way if you know the model name you can miss a step of having to find the manufacturer first
We agree, this is logged as ZOS-8223, to be included in a future update.
4 hours ago, RichardWilliamson said:- I found update annoying. In my mind update should only put the captured (red) channels into the target, however it seems to take the console output. This meant that in my use (an exhibition whit a playback for each area) I had to take other areas to blackout in order to record or update a specific playback
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.
4 hours ago, RichardWilliamson said:- I found it a little confusing when selecting a colour palette for a unit that wasn't in that palette (as there was no error to see when it wasn't a relevant palette) - maybe this is just me
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?
4 hours ago, RichardWilliamson said:- I found entering real time confusing in that I am used to being about to type 220000 and a console automatically formatting it to 22:00:00 - Jon Hole kindly pointed me in the right direction of adding decimal points to format appropriately
Yes currently decimal points are required to know where to break the time. I have noted your comment as ZOS-8859.
4 hours ago, RichardWilliamson said:- I'm not a massive fan of the long command line - I found it hard to tell what I had just typed, and I feel at the least the "enter" command (or assumed enter after commands such as @@) should insert a more obvious block than just a comma.
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.
4 hours ago, RichardWilliamson said:I also would like a way of sneaking/releasing a single channel out of the programmer in both live and also in blind, I couldn't see how to remove a channel from a cue..
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.
4 hours ago, RichardWilliamson said:- Also, in blind or in live, is there a way to see the colour/other information for a channel. I usually worked in the Strand 520-esq channel view (using shift-view)
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.
4 hours ago, RichardWilliamson said:Hope these thoughts are useful! I've finished on that job now but will try and find an excuse to use an FLX again soon
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...
17 hours ago, RichardWilliamson said:- initially I had universe set to ‘auto’, however using DMX output 1 I got bad signal when checking with a swisson (dimmers didn’t recognise anything) - changing to universe 1 fixed it
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.
17 hours ago, RichardWilliamson said:- patching is laborious. There seems no way to add a fixture without giving it an address, and far too much tapping on the touch screen. It’s not very clear which column you are editing, when you try to patch an address that’s in use for a new channel you don’t get a warning, the number just reverts.
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.
17 hours ago, RichardWilliamson said:You seem to have to make lots of use of clear/enter and check which Column is selected meaning it is stupidly easy to make mistakes without noticing
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.
17 hours ago, RichardWilliamson said:- also when patching, the menu when addressing doesn’t display the channel number you are working on, neither do any of the confirmation alerts. So if you accidentally edit the wrong channel there is no way to know
17 hours ago, RichardWilliamson said:- similarly if trying to patch an in use channel the alert should tell you where you are currently using the address
Added as a feature request. Logged as ZOS-8853
17 hours ago, RichardWilliamson said:- is there a way to view patch in address order?
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".
17 hours ago, RichardWilliamson said:- I somehow managed to unpatch channels twice. And I’ve no idea why. This could have been a bug. Or just me - either way it’s not good as there was no alert that gave me enough information to know it was happening.
Unpatching a fixture can only be done in the Edit DMX Address window, or by confirming a DMX address conflict.
17 hours ago, RichardWilliamson said:- at one point patching one 8 bit dimmer would patch two addresses. I have no idea why. This stopped after a while
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.
17 hours ago, RichardWilliamson said:- in live, when you switch faders from channel to playback mode with faders up ugly things happen
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.
17 hours ago, RichardWilliamson said:- when you select ‘colour’ on the right, the led above the colour button lights up as expected, but as soon as you move an encoder it goes out
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.
18 hours ago, RichardWilliamson said:- the remote (iOS) regularly doesn’t read key up’s meaning you can end up with a load of buttons seemingly pressed
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.
18 hours ago, RichardWilliamson said:- the remote is confusing if you leave the desk in setup and try and use it
Logged as ZOS-8855.
18 hours ago, RichardWilliamson said:- the remote should remember the console password
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.
18 hours ago, RichardWilliamson said:- the remote seems to flash ‘incorrect password’ when making a successful connection.
Hmm ok thanks for letting us know. Again, as I said the new apps will be on their way soon, which should solve this.
18 hours ago, RichardWilliamson said:- I feel pressing home should take you out of the setup area
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".
18 hours ago, RichardWilliamson said:- at one point the entire face panel (other than touch screen) became unresponsive across power cycles. Maybe this was a hardware issue
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.
18 hours ago, RichardWilliamson said:- no way I can see to go next/last through channels.
To skip through Next/Previous fixtures use SHIFT + LEFT or RIGHT arrow (You can actually also use SHIFT + AND or EXCEPT).
18 hours ago, RichardWilliamson said:- no way I can see to call up channels by address.
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.
18 hours ago, RichardWilliamson said:I couldn’t get rig sync to work with a power cube but they may not work with it?
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...
If possible I think it would be worth trying before you buy.
Any queries let me know.
Edward
-
Hi Mac,
13 hours ago, Uriahdemon said:The Network Overview info is as following:
DHCP - IP Address - 192.168.0.102
Capture - Transmitting on - 192.168.0.102
Remote - Listening on - 192.168.0.102 - 1 connection active
Capture is Enabled and 'Use DHCP Address' is enabled.
On FLX - Remote is Enabled as is DHCP
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.
13 hours ago, Uriahdemon said:When programming use Capture for visualisation so just the FLX console into the router and router connected to laptop.
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.
16 minutes ago, mattyiench said:I've noticed something really weird with the Grand master; i've switch on the desk with grand master at zero, i didn't see it was at zero actually but all the faders works fine with it at zero. the black out button was not flashing red..to make the grand master works i've to up and down it..
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
Use of Playbacks with random access during a cue stack playback
in Solution & Solution XL
Posted
Hi wildswan,
Could you expand a little on what you are trying to achieve?
I'm guessing you have some playbacks containing single cues acting as your random access playbacks, that whilst playing back your Master Playback at full you wish to flash over the top? By default, you should be able to raise your playback faders or flash them, and intensity will be mixed with your Master Playback with HTP (Highest Takes Precedence) behaviour, and any other attributes will mix LTP (Latest Takes Precedence). If you are seeing nothing happening on stage when you raise the fader or flash the playback and its settings haven't been changed, this may be because the lighting state contained in your playbacks is already on stage coming from your Master Playback.
Feel free to send me a copy of your show file, along with a description of which cues and playbacks aren't working as expected for you, and I'll take a look to see what's going on.
Any queries let me know,
Edward