Jon Hole

Hi Vincent, Ah yes, I see. However, this does seem to work for Playbacks, so this will sort itself out in the next release because of this thread. Jon

Yes, you're correct - as long as you go in numerical order, tracking and move on dark (which are two different things, independant of each other for the most part) will work. Any "missing" cues will just be ignored

Hi All, As we've had such valuable feedback from our previous proposal, here's another! We're always looking for new ways to support our end users. 2015 saw our highest social media engagement via Facebook, Twitter AND YouTube. This forum was also the most active it has been for several years. We obviously also offer telephone and email support, run several training courses every month, and provide onsite support for events such as the Edinburgh Festival. So, what else? One idea is to run occasional live chat sessions, where users could bring questions and ideas into a "chat room" with Zero 88 staff. These would last for an hour or so at a time, and maybe run once a week (for example). It would also be an opportunity for us to ask you questions (just like this proposal and the previous one) so we can discuss them within a live "chat room" environment. Would this be of interest to you? If so, how often would you realistically want to take part in a session like this? And what times / days would work best for you? This is just one idea - if you have any others, please let us know! Many thanks Jon & the team

DVI-D is, kind of, a more modern digital version of VGA (that said, DVI's still not particularly modern but that was a deliberate choice during the development process!). Touch Screens require a second cable (USB) for the touch element. So you can have VGA Touch Screens or DVI Touch Screens. So, in short, no there's not VGA on the FLX - but DVI can be used for non-touch screens too.

The only advantage is that you use one less DMX channel but have exactly the same control of the fixture. The problem is that it's the last channel of the fixture, which means the console will think it's only a 7 channel fixture, which can get confusing as the console will allow DMX addresses to be "overlapped" on this 8th channel. To get around this, double click the "DMX Allocate" (which in the image below is "3", but for you should be "7". That will open the small popup, where you can change it to "8". Again, I'd just ignore it if you don't need it. Alternatively, just put it as a "beamshape" parameter called ID, and ignore the "special" drop down box.

What I've described above is exactly the same as physically pushing the other fader up over the fade up time, and then brining it back down over the fade down time. So as long as the main cues run when you do that, they will when you add the chase in as described above. (The reason I'm not definitely saying yes, is there are all sorts of options you could select that will make all sorts of strange things happen!)

It's very easy to do, a little harder to explain!

Thought it might have been! Do you understand what happened, or would you like me to explain?

Hi Tim, Have you got an external monitor plugged in? Half way down, by the FLX logo, what Playback does it say you're viewing? If it's anything other than "Playback 0", that will be the reason!

Not sure why that is, sorry. If you email Stan Bulan (stanbulan@yandex.ru) he should be able to help you.

Hi Rob, You create the chase on a separate playback, and then use a "macro" to trigger and release it during your cues. On the cue you want to trigger the chase, go to the "Cue Settings" cell and press Enter. Now choose "Macros", choose "Add" next to trigger, and select the chase. Click OK on both windows. On the cue you want to release the chase (it might be the next cue, or several cues later), do exactly the same, but choose "Add" next to release instead, and select the same chase.

It depends on two things really - how many requests we get and/or if we're already working on Move on Dark, in which case this can get added in. I think they both make perfect sense, so I'd like to try and push them through. However, I don't think it's going to be in the next two software updates, as they are both pretty well defined already I'm afraid.

Have you tried different USB sockets? Try the two on the back of the console for example. Also, do you have a powered USB hub? If you do, please could you try plugging that into the console, and the two devices into the hub, and see if that works? Thanks

All our distributor information is available by clicking "distributors" along the top of the page. Here you go: http://zero88.com/distributors/easterneurope/russia-diamond.shtml Regarding the faders, this might be helpful to you too: http://zero88.com/support/index.php?/Knowledgebase/Article/View/512/210/replacement-faders--sliders

If you email us your showfile, we can have a look at it for you :-)

There are two apps, here you go: https://play.google.com/store/apps/details?id=com.eaton.ZerOSMonitor.Rigger https://play.google.com/store/apps/details?id=com.eaton.ZerOSRemote.Rigger

Hi Rob, Thanks for taking the time to post here, glad you're getting on with the basics "with ease"! I've added these two requests as new software issues and below I've included our reference for each of these: ZOS-6982 ZOS-6983 All the best, Jon

At least the battery in FLX is only used for the clock, not showfile information :-)

That one's up for discussion. Currently we're on ZerOS 7.8.5 (FLX) and ZerOS 7.8.2.36 (X86 consoles). The current plan is for this to become ZerOS 7.9, because we've already publically defined ZerOS 8 as including a Matrix Engine / Pixel Mapper and RDM functionality. Yes, definitely.

It will indeed!

Hi Andy, Certainly sounds like the battery to me. All the infromation you should need is here: http://zero88.com/support/index.php?/Knowledgebase/Article/View/546/31/replacement-battery-information

A few duplicated ideas here: - Try trying different USB ports. If a USB device tries pulling too much power, FLX cuts off that USB port for protection. However, it does this in pairs. So it might be that the keyboard is causing FLX to cut off a pair of USB ports, which is why the monitor stops working. - Your post doesn't specifically say you've had the keyboard working on it's own without the touch screen... does it? - What USB Keyboard are you using? Is it super basic and simple, or does it have things like lots of extra Media Keys, a built in trackpad, backlit keys, extra USB ports on the back/side to plug other devices in etc etc?

Hi All, We're continuously working to make ZerOS more intuitive and quicker to programme, yet even more powerful, with regular new features and updates. In the next release of ZerOS, we're proposing retiring "Submasters" so that everything becomes a "Playback", just like on FLX. We'd like your feedback on this idea! Why would we want to do that?! Well, ZerOS is a bit of a mess at the moment! Each console has different terminology and slightly different features: ORB & ORB XF: Submasters, Cues, Cue Stacks, Playbacks (Cue Stacks can be chases, Submasters can't be) Solution, Solution XL, LF48 & LF96: Submasters, Memories, Memory Stack (Submasters and Memories can have chases directly within them) FLX: Cus, Playbacks (Playbacks can be chases) FROG 2: User Definable Faders, Cue Stacks, Playbacks (Cue Stacks can be chases, User Definable Faders can't be) There are many reasons this isn't good. For you, it means that you're probably missing basic functionality which is already available on another ZerOS consoles, it means there's a significant learning curve when moving from one ZerOS console to another, and it means that showfiles aren't as fully cross-compatible as they should be. For us, it means development and testing is slower and more complicated, technical support is more difficult, and training / documents are more confusing. So, what exactly are "Playbacks"? Currently, on ORB, ORB XF and FROG 2, "Playbacks" relate to the physical fader, which can then have different "Cue Stacks" on them (using pages). So, for example, ORB has 10 "Playbacks", but 1000 "Cue Stacks". This means you can access 10 of the 1000 "Cue Stacks" at any one time. ORB XF can have 20 "Playbacks", meaning you can access 20 of the 1000 "Cue Stacks" at any one time. However... on FLX we ignore all this, and "Playbacks" are the new name for a more advanced, yet simplified, "Cue Stack". These new "Playbacks" can have a single cue on them (like a Submaster), they can have multiple cues on them (like a Cue Stack), and they can have a chase on them. It are these Playbacks that we propose to roll out for all consoles. How will this affect me? It depends on which console(s) you use: ORB: All the features of Submasters and Cue Stacks get combined, so you no longer have to switch between them on the 10 faders. Any Playback can be loaded onto the "Master Playback" (but a new "Playback 0" would become available for those users who'd like the Master Playback to be completely independent). ORB XF: All 60 faders could be Playbacks, rather than just the bottom 20, meaning chases can be put anywhere. The "Fader Function" button instantly switches between "Channels" and "Playbacks" with a single button push, rather than the longer syntax currently required. Any Playback can be loaded onto the "Master Playback" (but a new "Playback 0" would become available for those users who'd like the Master Playback to be completely independent). Solution, Solution XL, LF48 & LF96: Each of the current submasters would become Playbacks, allowing you to store multiple cues to each of these faders, just like on the "Master Playback". Chases would no longer be stored directly within individual memories, but instead they'd be stored onto a separate Playback. This would then be programmed to automatically be included within whichever cues you decide (so you still only press the main GO button). This is advantageous compared to the current chase method for three main reasons: 1) Chases can very easily run on top of multiple sequential cues, rather than just one 2) It becomes very easy to update the "base" lighting state and then put the chase on top of this, rather than having to update every step of the chase 3) A Chase can be used multiple times, even when the "base" lighting state is different FLX: Nothing changes FROG 2: Both sets of 10 faders become Playbacks. These can be paged independently of each other (so the top set could be "Page 1", and the bottom set could be "Page 2"). Will old showfiles be compatible? We are working on code that will convert old showfiles to the new format automatically. However, these are significant changes, so you'd be required to carefully check through the whole showfile before you use it on a live performance (you should do this anyway when updating software!). There are also some specifics to think about on certain consoles: ORB, ORB XF and FROG2 - Submasters (UDFs on FROG2) might be renumbered. This is because there might be a "Cue Stack 1" and a "Submaster 1", and they can't both become "Playback 1". Therefor, Cue Stacks would "take precedence", and Submasters would be automatically moved if required. This could be avoided by reorganising Submasters before upgrading the software. ORB XF - Currently Playbacks 1 - 20 appear on the bottom 20 faders, but with all 60 faders being Playbacks, these would appear on the top 20 faders. How will Zero 88 communicate these changes? We are convinced there are enough significant advantages (for everyone's benefit) to make this worth while, but we also understand these are significant changes to how some consoles work. We have plans to provide written documents, updated manuals and new YouTube videos detailing the changes and training on how the new Playbacks work. Training courses will also be updated to reflect these changes. I have questions and ideas, how can I feedback to Zero 88? That's exactly what this forum post is for - please put your feedback, comments, questions and ideas below and we'll reply to each one.

Yes please!

Hi, probably a little late to answer this one (always use our official support lines - email or phone - for urgent help). I always patch sunstrips as 10 separate dimmer channels. It makes it way easier to control, and it means you can use the "offset" encoder in the effects window (hold down SHIFT whilst moving the offset encoder to "fan" the offset across the fixtures)