Jon Hole

Ed's correct, this is available on ORB Series and FROG2, but not currently FLX. One way you can get around it is to record palettes of the fixture you want to copy, and then apply that palette to the new fixture - but this is a little bit long winded.

I've been wearing the 38mm watch for a week now, and I'm convinced more than ever that these things are too small for any form of keypad. To unlock the Watch you need a PIN and the buttons feel just about big enough - we'd need to fit additional buttons onto the screen to be able to access basic syntax, and so I don't think would be nice to use.

A quick update: App development was put on pause for a couple of days, but has restarted and is progressing well. ZerOS now fully supports the messages and flags required for the Apple Watch app We've built a development emulator within ZerOS to test these messages and flags

It's a little like Christmas in the office...

Maybe this style interface would work better? One for individual channels, one for groups.

Thanks for the feedback - keep it coming. I think the real advantage here is as a focus tool. I struggle to see the need to have playback functionality from your wrist (although, potentially the current cue, and any fade / wait times and progress bars could be useful for crew backstage?). Rather than using the digital crown to fade up / fade down, what do you think about just using the programmer time on the console, and then Rem Dim / Highlight would use this time - meaning you can still just press "next" rather than having to fade down the previous channel, select the next channel, and then fade it back up. To change selection, if there are difficulties in using the Digital Crown (need to investigate this) how about press and hold the next / previous buttons to scroll through the channel numbers, and the when you let go, we action the Highlight / RemDim (with the programmer time if enabled). Lastly, I think Next / Previous would only select static fixtures, not Moving Lights. If a selection has already been made, Next / Previous would cycle through that selection in the order they were selected (so if you knew you were focusing channel 7, then 10, then 12, then 15 you could just select those fixtures on the desk / phone app, and then using the Watch to cycle through those four channels). Thoughts?

Hi Matthew - can you send us your show file, and let us know which playback numbers you're referring to, and we'll take a look for you!

1 @@ will go to full (or 1 @ 100 Enter) 1 @ . will go to 0% (or 1 @ 0 Enter)

Hi Karleaton, The ORB Series manual will be coming up for a renewal yes, probably later in the year. We're going through our product range updating the manuals, with the Solution manual updated last month. Jon

Hi Matt, There's not a list no... however we have requests logged to expand our support for keyboard shortcuts, so this might be a good thread for people to request what they think we should include! One useful shortcut - SHIFT + F10 opens SETUP

Kevin got there first - I was going to write exactly the same! Also, check you're running the latest software (ZerOS 7.9.2)

There are a few options, it's best to discuss with Keith on email keithrogers@eaton.com In short, we might be able to do a firmware update, but this requires sending back the keypad and one of the internal 3 phase PCBs to us. However, depending on the age of the PCB, there's a possibility the new firmware won't install. The alternative is an "upgrade kit" which includes a new keypad and 3 phase PBC. Keith will be able to discuss the various options with you

Appears that it's pre-populated if the last cue that was recorded is the last cue in the list. If you record a point cue, the next Record Name is left blank. Added as ZOS-7572 Added as ZOS-7573

However it's happened, the setting will be saved into the show. However, I'm guessing you're running old software as the latest software will force it back to percentages, so the best option is to save the show, update the firmware and then load the show back in

Yep, as Mike says it's all within the .zip file. That can be downloaded by clicking "Download ZerOS" on this page: http://zero88.com/software/zeros/

Send over the showfile with details on which fixtures should be doing what in which cue and I'll take a look I end up with all sorts of odd versions of ZerOS only laptop... I think this was an old early beta

Yep, should do :-)

You can only have either Snapshot or Smart Tag enabled at any one time. Enabling one will disable the other. SHIFT+RECORD only temporarily enables Snapshot for that one Record, and then reverts the settings back to how they were previously. SHIFT+RECORD / Snapshot doesn't affect the tracking setting - this setting is left as whatever it was before (Tracking forwards / backwards / both / cue only). Already is :-) It's a "macro". If you enable both "Smart Tag" and "Cue Only", you shouldn't get any future blocked values.

This is the problem. Shift + Record is "Snapshot" not "Cue Only". In Snap Shot, every parameter gets recorded, no matter what. The other thing to remember is just because the intensity of a fixture is tracking / not tracking, doesn't matter that the individual parameters are / aren't. Move on Dark only works if the fixture is at 0% (or another parameter is set to a value that "is dark", such as "Shutter Closed") AND the parameters that are "moving" do not have programmed values within that cue. Because you've been using Snapshot, every cue has parameters programmed within it, and therefor the lights are not moving in dark. I've opened your show on an ORB XF, which shows this a little more clearly, essentially the red values are "bad" (in this situation, not always): The easiest way to solve this will be to go into the Playback settings (SETUP + GO together), go to "Advanced" along the top, and then choose "Unblock". This will remove all the red values shown above. To stop this happening in the future, in the Record Window enable "Smart Tag" - this does lots of the cleaverness for you, and 90% of the time means you can ignore tagging, tracking, cue only etc.

I'll try and explain where we stand on this... We now support RGBW fixtures within the colour picker and filter lookups. To do this, we make a very crude assumption that "white" LEDs are always the same (that being "all frequencies"). This is clearly not true, and therefor it's up to the Lighting Designer to choose a fixture with "white" LEDs that they like / are most suitable for the performance. That being said, we've had great feedback on our implementation, not just from users but from multiple fixture manufactures too. Amber (or any other colour) becomes a little more difficult because there's no definition of what "Amber" (or any other colour) is, or exactly where it lies within the frequencies / hues. Trying to solve this, some organisations take real life measurements of each fixture type and use these to try to calibrate control consoles. However, we believe there are multiple reasons why this doesn't give us a full solution: For the calibration to work efficiently, you need 100% of the fixtures in your rig to have had their measurements taken. No one has (or can) take measurements of every fixture type that's released into the market place, and therefor the likelihood you'll have a rig made up of 100% measured fixtures is minimal. Even once a fixture type has been measured, there are too many external variables. Try getting the same colour (and intensity) out of two discharge lamps, when one is brand new and the other is towards the end of it's life. Even if the lamps are replaced at the same time, the measurements are only accurate at the point your fixture has the same lamp hours as the fixture that was measured. LEDs can change over time too, and even more frustratingly between batches. Therefor, two identical fixtures, both used for the same number of hours, can show a difference in colour. Especially at the lower end of the market. Even if you solve all of the above, we're assuming you're projecting onto a white surface. As soon as the surface changes colour, the operator is required to counteract this colour shift anyway (if they can). So, is there a solution? Maybe. Have a look at this: http://www.mikewoodconsulting.com/articles/Protocol%20Fall%202014%20-%20Color%20Communication.pdf

There's no guarantee on this - for now we want to find out how much interest there is, and exactly what the App needs to do, so if we do it, we get it right first time. So, do we need anything else? Display the current cue? If so, of which Playback - the currently viewed playback or only the Master Playback? Do we need a way to press "GO"? With next/previous, do we skip fixtures with Pan/Tilt and assume you won't be focusing those? Do we add the ability to next/previous within a group, so from the console you can select all the fixtures on a truss / bar / stand, and then next/previous only cycles through those? Throw ideas around...

What would a ZerOS Smart Watch do? What would be it's purpose? Here's my idea for a focus tool. The channel in the middle (15) is the currently selected fixture. Next and Previous buttons allow you to select different fixtures. The digital crown on the side allows you to adjust the intensity in steps of 5%. RD = RemDim, HL = Highlight.

The Colour Picker will only affect the RGB values. Amber can then be added in / removed using the dedicated encoder wheel. I'd ensure that Amber is defaulted to 0% rather than 100% (if this isn't already the case, this can be altered in SETUP > Edit Fixtures > Defaults)

Thanks for sending that over. If you select fixture 113, press "colour" and then along the bottom of the touch screen tap "Red", "Green" and "Blue" so they all go light blue rather than dark blue. Now, press and hold UPDATE. When the Update Window appears, tap "Smart Tag" to turn it off. Now type "1" (for Cue 1) and press the {Playback 1 button} to update Cue 1 on that Playback. This should solve this problem. We've logged this as ZOS-7535 so this doesn't happen in the future

As I said before: Last week we released ZerOS 7.9.2 which was the second of these two updates, so no - these two haven't been implemented yet.