Jump to content
Vari-Lite Controls Support Forum

Jon Hole

Vari-Lite Admin
  • Posts

    2,518
  • Joined

  • Last visited

  • Days Won

    35

Posts posted by Jon Hole

  1. The technbppac,

     

    I'd be happy to send you a beta version of ZerOS closer to the end of the week, if this would be helpful?

     

    The Android Remote was released to a handful of Beta Testers, and we're now working on the issues and requests that came back from that round of testing. We'll then release a second Beta.

     

    Best Regards,

  2. Hi techbppac and lxkev,

     

    I've recently taken over the software development of ZerOS. I'd like to try and explain what's going on 'behind the scenes'.

     

    As you saw at PLASA, ZerOS 8 was a massive update (with well over 200 issues and new features), and was far from being ready for release. We've learnt that there was just too much in this single release which then had knock on affects on other areas of the operating system, and kept pushing back the release date.

     

    We are now scaling back a release, called 7.6, which is the fastest, and most stable release of ZerOS I have seen in my almost 3 years here. However, stability is THE most important thing, so we are spending longer than normal testing this release, both internally and externally on shows around the UK and Europe. We are *so* close to releasing 7.6.

     

    After that, we are going to be working on Tracking Backup, as this is an area our current customers have told us they would like us to work on further.

     

    Once these areas, which are most important to our current end users, have been completed, we are then going to revisit the new features we want to release, as 'ZerOS 8'.

     

    I hope this gives you some insight into the incredible amount of internal beta software releases that's going on here at Cooper Controls, and I really hope you're going to be as happy with 7.6 as I am.

     

    We're always looking for new Beta Testers from a variety of backgrounds, and if this is an area of interest to you, please drop me an email.

     

    If you have any questions, please don't hesitate to contact me directly - all my details are in my signature below.

     

    Best Regards,

  3. Hi,

     

    Thanks for this.

     

    We are currently trying to move server, because of these (and more) problems that we are unable to fix on the current server. It's a very annoying and frustrating situation at the moment, but in the next week or two we will be on new servers which we will have full access to, so we can fix these problems.

     

    Best,

  4. Hi,

     

    It sounds like the close contact connection is staying connected (is the pedal latching? It needs to be 'push to make'), or possibly connected until you press the pedal instead of the other way around.

     

    Are any of those possible?

     

    Regards,

  5. Hi,

     

    The ORB XF has MIDI Timecode, allowing you to trigger cues against a timecode, for example on a projection or audio track.

     

    We are looking at implementing other MIDI functions in future software updates, but I don't have a time frame for this yet. These include MIDI Show Control and MIDI Notes

     

    Regards,

  6. Hi Dan,

     

    Best way to alter a step of a chase is to 'load' it into the programmer, make the changes, and then 'Update'.

     

    It's not a glitch that we are aware of, however if you would like to send me your showfile, and which version of ZerOS you are running, I'm happy to have a look through it for you.

  7. Alternatively, would it help if we dissassociated the ChromaStrips from what's going on the cue stack; perhaps running them manually from sub-masters or chases or some othe magic function of the fixtures controls?

     

    This sounds like a good option - create a chase on a submaster which does just the colour. Once you have got to the end of the chase, record several cues all the same - this gives you time to then pull down the submaster at the end, so the chase doesn't start again (there is no way to do a one-shot chase on a Jester ML).

     

    Because colour is 'latests takes precedence' (LTP), and submasters on the Jester ML don't release, the colour will stay when you pull down the submaster. Just make sure the intensity of the LEDs are recorded into the cue itself.

  8. Hi DickM,

     

    First, I was going to suggest recording several cues (I would personally use the point cues, so your number sequence doesn't get too badly affected), all with their trigger set to 'auto', and a fade time of however long you require.

     

    However, on a Jester, the following becomes tricky...

     

    This should of course happen at the same time and over the same duration that all the other lanterns are changing their states for cue 28 too.

     

    If you know you have 10 cells, you could reduce/increase the percentage of each channel by 1/10th of the overall change on each step - however this isn't a 'nice' solution, and if you choose to make an edit of the final step, you would need to update each and every cue. It would work, however it's not an elegant, or particularly practical, solution!

  9. I'd rather be able to select which memory (or submaster) is being triggered by which note. Any chance of implementing this in future updates?

    We can definitely look further into this. I've added it as issue ZOS-5187

     

     

    Thread-starter mentioned a way of using a MIDI>DMX interface. Do you have made any experience with these?

    I've not had any experience of these, however other users on the forum might have done.

     

     

    why this feature is not present in the top desk?

    We're looking into this, to ensure features are spread across our consoles in a logical manner! However, I don't have a time frame for you at the moment, sorry.

  10. Hi Johnny,

     

    When enabled, the first note relates to memory one, second to memory two etc etc.

     

    With 'Octave' enabled, each octave will do the same thing, meaning you can only access Memories 0 - 11.

     

    With 'Octave' disabled, the second octave will start from memory 12 onwards.

     

    Hope this helps,

  11. Try going into SETUP > Desk Setup > Event Monitor

     

    Now, push one of the problem faders right to the top of the travel, and you should see a load of text appear on screen at looks like this (with the blanks filled in).

     

    Fader 0x____ (_________________), New Level 0xFF, Old Level 0x__

     

    Check that the last (bottom) line of text has 'New Level' as '0xFF'

     

    Now pull the fader to the bottom, and check that 'New Level' is at '0x00' on the last line of text.

     

    Repeat this for all the faders that are causing problems, and let us know the result.

     

    (to exit this window, you need a mouse or touchscreen to click the cross in the top right corner of the screen. If you don't have either of these, turn off the desk and turn it back on).

  12. The showfile will be absolutely compatible unless you are updating from a VERY old version of software, which it doesn't sound like you are (so long as your software is 7.x.x you'll be fine).

     

    Remember that updating the software wipes your showfile, so take a backup of the showfile onto a separate USB memory stick first, so you can load it back onto the desk

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.