Jon Hole

Hi Theo12, Is it this fixture you require? http://www.chauvetlighting.com/colorado1-tri-tour.html Many thanks Jon Edit to add: If so, here's the profiles you need: COLORado 1 Tri Tour.ift

Hi Andre, Here's the Expolite TourLED Pro 28 Zoom in all modes. TourLED Pro 28 Zoom.ift Regards Jon

Do you mean some form of display above the faders? We're keeping this in mind for any future product we made, but unfortunately there was just no way we could do something like this without a dramatic price increase. ZerOS in general doesn't support true undo functionality currently. We have a "backspace" button which will undo the last commands on the command line one at a time. However, this won't update a record/delete/update at the moment. It will updo any updates to the programmer. I'm not sure what you mean by this? Maybe you could expand on this please? Yes, of course. And "Record 5.55 Enter" - we go up to two decimal places. Yes, but it only works for the stack you are currently viewing (the cue itself is actually stored at the point of typing "name", not when you press "enter"). I've added ZOS-6179 to delay the recording of the cue until after typing in the name, so you can select a stack. We know - and we're working on making it much much better. When you press RECORD, the four encoders will change to: - Fade Up - Fade Down - Delay Up - Delay Down You'll be able to use the wheels to change the time, and then choose where to record it, or you'll be able to tap the middle button of the encoder and then type the time you want. I guess everyone expects it to be in different places. Most people think the Solution is weird having Intensity within Position! Intensity doesn't really live in any of these attributes, and doing so adds confusion as Intensity doesn't use that attribute's fade time, and doesn't get stored in that attribute. Also, if there are several parameters in that attribute, it means you have to cycle around the pages to find it, whereas here you can get to it instantly, no matter where you are. Yes... you can set one of the User Definable Keys to be "Rem Dim". Choose an empty UDK, and hold SETUP + press the UDK. You can now choose Rem Dim from the drop down. Yes - you can use "Highlight" which takes the selected fixture's intensity to full, and any other parameter to it's default. This can also be put onto a UDK (like Rem Dim) or you can use the shortcut SHIFT+HOME together. When you have highlight active, the left and right arrows will select the next and previous fixture. However, we're doing a little work on this as we've been made aware that in some situations the next / previous doesn't always work like this. When you load the image in, the console asks you to put all the fixtures into one of the corners (that we mark on the image) and then record them there. You then do this to each of the other three corners. It takes a little while to set that up, but once done it's then a really really quick way to control position. We also record focus and zoom onto this image, which you can use if you wish.

Hi Emily, If you're in Program mode, you should just tap "Mode" and it switches to Run. If you press and hold "Mode" it should go to Preset. Are you saying that's not happening? Can you get into Setup by pressing and holding SHIFT and MODE together? If so, go into Setup, press the Up arrow to get to <Test Mode>. Is the middle line of the LCD blank, like the first image, or does it have something written in it, like the second image. If it has something written in it, what does it say? The keyboard just makes it quicker to type in letters or numbers (rather than using the 10 Multi-Functional Keys). You can also use the left/right/up/down/enter keys. Do you mean this product? You would use this *instead* of the Jester console, not as well as. It might be worth contacting them directly about that product to give you some more information.

Holding clear and moving the encoder should work, but you can also just "tap" the parameter on the touch screen to tag and untag it:

Hi Mathias, If you do exactly what you've written, you'll get B - the fixture will become blue. However, if you'd prefer A, this page shows you how to make RGB Submasters on our other ZerOS consoles. http://www.zero88.com/support/index.php?/Knowledgebase/Article/View/585/ Doing it on FLX is very similar... the only slight difference is you go into the Stack Setting and change the "Fader Controls" there:

Hi mathias, No, not at the moment - it's RGB / CMY / HSV only.

Hi Lufferov, Really glad you liked the console. Yes - please post your questions here and we'll answer them. Also, we can arrange a demo for you if that's helpful - drop me an email, and I'll put you in touch with one of the team.

Frustratingly, we missed Prolight & Sound for this, but I'm pushing hard to get something on the Beta forum this week. I was given a version on Friday, and they are now working on the feedback I gave them from that.

Hi Jack, For the chase issue, please can you send me a showfile, with instructions on how to recreate it using your showfile. For the fader issue, this might be a problem with the faders themselves. Try going to "Other Windows" in the Output Window, choose "System Info", and then choose "Event Monitor" on the window that appears. Now, push one of those faders right to the top. You'll see a lot of text appear, and the bottom line should include "New Level 0xFF". Now, pull that fader right to the bottom. The bottom line should now include "New Level 0x00". If you see anything other than 0x00 or 0xFF, let us know. Jon

Hi Jan, This is how the Jester 12/24 and 24/48 has always worked. In Program Mode, when you select a sub or memory, the contents is "loaded" into a kind of "programmer", ready for you to do something with it - like modifying it or storing it somewhere else. It's different than in Run Mode, when it's being played back live from the submaster / memory itself. Therefor, when you delete something, you're only deleting the sub / memory itself, not the additional info in this kind of "programmer" - that's still there incase you want to do something with it (and to stop the stage being plunged into a backout!).

Hi Sandy, You can select a new Cue Stack (STACK x ENTER) and then create several cues within this stack, each with the channel at a slightly different level. Now, click "Stack Setup" in the cue stack window, choose "Chase" in the window that opens, and then choose "Turn into Chase". You can then change "Chase Direction" to "random", and change the speeds etc within this window.

Hi Jan, Which version of software are you running? Regards Jon

Hi Ziglight, Just to confirm, this hasn't been implemented in ZerOS but the data is there so we can fix the wheel edit to the midpoint of the detail range, rather than scrolling through it.

Blind mode will definitely be added shortly. The rest, we'll have to see!

Thanks, this is useful feedback. Are there "better" ways we could do this? For example, could we have a switch in the output window to switch between patched channels and DMX. When viewing DMX, the syntax could work for DMX addresses instead of the patch. Or maybe we could show in the output window when effects etc are running, so it's very clear? Have a think and let us know! We're definitely open to suggestions... I think we've got a great implementation for launch, but when people start getting FLX in their hands, I'm sure we'll get lots of new great ideas too, which we'll look at implementing. The fader wings use USB for both data and power. However, there's no reason you couldn't use a USB - Cat 5 converter for a longer run - as long as they provided power to the wing. We're also going to implement "Art-Net In", which would allow you to plug a smaller console in - such as a Level 6 (using something like our 1 Universe box to convert from DMX to Art-Net). I think there's still a definite market for ORB XF. There's functionality on ORB XF that FLX doesn't have yet, such as part cues, individual channel times, blind mode, parking etc. ORB XF also has the 60 built in faders, 10 UDKs (which are pageable giving you 200 UDKs and have LCDs for labelling), an intensity wheel, additional I/O on the rear, 4 physical DMX outputs rather than 2, more hard-buttons for command line programmers (things like Snapshot, Cue Only etc are hard buttons on ORB XF, but soft buttons within the record window on FLX).

We're using it internally, but we're not quite ready to release it yet... less than a month though Out of interest, how/why/what for do you regularly use the DMX Output Window? This is something on my radar to update and add functionality to, so it would be good to take your comments into consideration while we do this. Unfortunately not. This is because their hardware is limited to 1024*768 output.

That's our list price for launch, yes. However, you should always talk to your local Zero 88 distributor regarding pricing. Not yet, no. Yes - we've started building the first batch already, and these have been mainly bought by our distributors for their demo stock. The second batch will be ready for shipping later this month. The Wing will be shipping in a few months. You can use the faders to control intensity, or syntax, or one of the encoders. We're also going to add the ability to use the scroll wheel on a mouse / trackball to control intensity in an upcoming software release. We've tried to include as much as possible. Obviously there are going to be things done in slightly different ways. For example, there's no "Move" button, but within the copy window, there's the option to Move rather than Copy. Eventually you'll be able to drop and drag things like palettes via the touch screen too - but that's a little further away. We've basically covered it all above already. There's no two-preset operation. Blind Mode will be added shortly, but not quite at launch. There's no SMPTE or DMX Input (These are upgrades to Solution anyway. Art-Net input is being worked on for ZerOS in general, so will also be available on FLX). Yes there is. It shows each playback, and the current cue, name and fade times of the current cue on each playback. Hold down VIEW and press the GO button of the playback you want to view the cues of. This appears in the bottom half of the external monitor, if it's plugged in, or on the internal monitor if it's not plugged in. Keep them coming!

Thanks for the email uli-s_kn - our software team are investigating what could be causing this for you. cucolino - I will reply to your personal message directly, but it's worth saying that as far as I'm aware Uli's issue is the first speed-related issue that's been reported since the new software, and so we're treating this as a one-off case at the moment while we investigate what could be causing it.

Hi Johnny - thanks for bringing this to our attention. I think this only applies to certain processors, but I will investigate further once the office reopens after Easter.

I'm guessing, as keredyelesob suggests, that this is because "0%" is in the programmer - and the "programmer always wins"! Pressing CLEAR twice will remove the 0's from the programmer, and the submaster's intensities will start working.

Hi keredyelesob and Lufferov, Let me try and answer your points.... however the best way is always going to be to get a FLX in front of you and decide for yourself. We're trying hard to get it in front of as many people as possible as quickly as possible! There's a comment on this link (a Facebook post) from someone who was shown the console today - it shows a few things that stood out to someone not working for Zero 88 !. https://www.facebook.com/Zero88/posts/947392855294293 We discussed in length where to place FLX in marketing material, and decided to place it where it is mainly based on size, speed and ease of use. The main issue with trying to "place" FLX either before / between / above Solution and ORB XF is that ORB / Solution work in very different ways to each other. They use different control methods (channel faders vs syntax), different programming methods (one you press RECORD in the middle of the syntax, the other you press Record at the end) and are aimed at different marketplaces. So to try and place FLX in relation to two products which don't really relate to each other in the first place, is quite hard! When looking at the specs... There are 240 of each palette, which is technically lower than Solution, but I have never seen a showfile with even half of the Solution palettes filled up. FLX also includes a fourth attribute (splitting Beam and Shape), so there's kind of the equivalent of 480 palettes in comparison to the 400 Beamshape palettes on Solution - which is easily the attribute which usually has the most palettes recorded. Recording palettes is also much quicker and easier (if using something like the colour picker, the tab automatically changes to "Palettes" when you press record, and then automatically switches back afterwards. We've also built auto-palettes directly within the window, rather than via setup etc). You can recall them using the touch screen (equivalent of the MFFs on Solution) or via syntax (equivalent of ORB XF). Things like this can't be highlighted on a simple comparision table. There are 241 playbacks on the FLX- that's significantly more than the Solution (technically an increase of 24000%!!!). We no longer use the idea of "submasters", as this functionality (and much much more) is included with the playbacks. There are 200 submasters available on Solution and 600 on Solution XL. ORB XF has 1000 cue stacks and 1000 submasters (but again, I'm almost certain no one has ever used them all!!!). There are up to 2048 channels across four universes, without any limitations. This is the same as ORB XF. Solution has 248 (or 296 on Solution XL) available channels/fixtures. FLX has been designed to not require the external screen at all. However, if you choose to use one, for launch we've decided to limit the Window Outputs as this is an area we've seen a lot of users get confused with in the past, and an area we wanted to make really really simple and quick. Because of this, we created the two layouts we see most often, and made everything else available through the internal touch screen. Effects appear on the internal touchscreen instantly when you press "effect". We've combined the "Effects Palettes Window" and "Effects Window" into a single window with two tabs, just like the P/T Grid in position and the Picker, Faders and Filters in Colour. DMX Output window will be coming soon... Yep - we have a quad core ARM processor in FLX - it's awesome. The touch screen is multitouch, and so ZerOS has been updated to start accepting Multi Touch gestures for the first time. The memory is a lot more reliable, no longer requiring a battery to back it up. We're using Neutrik etherCON and powerCON connectors (with internal PSU) - both much more reliable and robust connectors than we've used before. We also include the MIDI and Remote inputs, which is available via an upgrade on the Solution (remote now has 8 channels rather than the 6 we used to have). We can also now output more than just 1024*768 on the external monitor - so plugging in a higher resolution monitor will allow you to see "more" stuff, rather than just everything bigger. So for example, in the "quarter" views, on higher resolution monitors it's possible to see 10 palettes per row in each of the windows, rather than just 5. You can also see more rows at a time without scrolling. Let me know your other questions and I'll have a go at answering them!

Hi Both, keredyelesob - thanks for providing the support here, everything you say is what we would have said too! cucolino - i strongly suggest not using the Beta software. We've had loads of users tell us 7.8.2 is a great improvement. One forum member has said their console is slower than they would like - but we're treating that as a one off issue and waiting to receive showfiles so we can look into it further.

Hi Jens, I'm not sure of an easy and reliable method that's going to be much cheaper than the £108 I don't think

Hi Ziglight, There's a lot of options that we don't currently use, but are there so we can include the information within the personalities if we ever decide to make use of it in the future. I believe this was included to specify if the "detail" is something like a fixed gobo (rather than rotating), but to be honest we don't include this information within any fixtures we make. I have dropped our lead Software Engineer a message to get some more clarification, as this was added before I joined Zero 88!