Jump to content
Vari-Lite Controls Support Forum

Edward Z88

Vari-Lite Admin
  • Posts

    3,281
  • Joined

  • Last visited

  • Days Won

    81

Posts posted by Edward Z88

  1. Hi Franco,

    As each software update is independent from one another, you can install ZerOS 7.9.7 directly from ZerOS 7.8.2.39. ZerOS 7.9.7 can be downloaded from our website below...

    https://zero88.com/zeros#download

    For instructions on how to perform the software update, see below...

    http://support.zero88.com/1518909581

    Once you have ZerOS 7.9.7 installed, the Solution will operate very differently to how it does on ZerOS 7.8.2.39. For information on the changes, see below...

    http://support.zero88.com/988876191

    Hope this helps, if you have any questions let us know.

    Edward

  2. Hi Martin,

    13 hours ago, martin-144 said:

    Does FLX (or ZerOS) start Artnet numbering at universe 0 or universe 1?

    From a Factory Reset ZerOS, when ArtNet is enabled, it is routed 1:1, meaning desk universe 1 is routed to ArtNet universe 1 and so on.

    If you press SETUP -> Universes -> ArtNet 4 -> Reset to Defaults, you can choose to route desk universe 1 to ArtNet universe 1 and so on, or route desk universe 1 to ArtNet universe 0 and so on. We will never rename ArtNet universe 0 to be 1, which sounds like what Realizzer may have done.

    Edward

  3. Hello,

    1 minute ago, bungeefield said:

    Ah yes i think that must've been it, in realizzer you can change the universe, i had it set to universe 1, but it was coming through on universe 2 (i assume becuase realizzer universe 1 is artnet universe 0, etc..)

    Ah excellent. glad to hear you solved the problem.

    1 minute ago, bungeefield said:

    Thank you so much for all your help, greatly appreciated.

    No worries, any questions just let me know.

    Edward

  4. Hello,

    All looks good in the show file - thanks for posting.

    I'm not familiar with Realizzer - is the connection to an ArtNet input automatic, or do you have to configure it? Is it looking to receive ArtNet starting at universe 0, or universe 1? Is this something you can configure within Realizzer? Is it also seeing FLX, however just not responding? FLX will not transmit ArtDMX, until a node subscribes to a universe. 

    I know it sounds like a cliche, however have you rebooted the PC since configuring IP settings? I have known Windows 10 to disable a NIC without asking it to in the past!

    Edward

  5. Hello,

    Thanks very much for the screen shot. 

    Hmm that's odd, can't remember seeing that before.

    What fixtures have you got patched on FLX? How many universes have you patched on? Would you be able to save your show file, and post it here so I can take a look?

    Edward

  6. Hello,

    1 minute ago, bungeefield said:

    They are connected over a network with an ethernet switch and a dhcp server.

    I'm guessing the console and computer are configured to DHCP IP addresses?

    In the DMX Workshop node list, does the FLX have a green tick? If you are seeing a question mark, it means DMX Workshop can see FLX, however there is a network error.

    On FLX, if you press Z -> System Information -> Network Overview, at the top of the screen the DHCP address will be displayed. Can you confirm FLX is using this for ArtNet?

    If you have any questions let me know.

    Edward

  7. Hello,

    Welcome to the Zero 88 Forum. 

    What ArtNet device are you trying to control?

    5 hours ago, bungeefield said:

    i am trying to output all the universes over artnet,

    Are these routed 1:1? Meaning is desk universe 1 router to ArtNet universe 1 and so on?

    What is the network setup? Are you going via an Ethernet switch; or directly from console to node?

    Edward

  8. Hi Peter,

    On 2/15/2020 at 11:33 PM, Howartp said:

    We have RDM turned off

    Even if RDM was enabled, this wouldn't unpatch a fixture.

    On 2/15/2020 at 11:33 PM, Howartp said:

    Fixture 35 is a dimmer channel on a Chilli 2410 pack (we've two making 48 channels) so no RDM either.

    As a side note, the newer Chilli dimmers are RDM enabled.

    On 2/15/2020 at 11:33 PM, Howartp said:

    We haven't added any fixtures since 35 (36 was going to be smoke but we abandoned that) and all other fixtures were already patched and set.

    I don't see any reason why this fixture would unpatch itself. If it happens again, please save and send the show file again with the fixture still unpatched.

    Edward

  9. Hi Mil,

    There are a few options to do this. 

    The simplest, is recording an effect to a playback, and in the playback settings enabling Fader Controls Effect. With fader controls effect, the fader will scale the fixture’s intensity, and the speed and size of the effect. If you wished, you could have the intensity of the fixtures controlled with a separate fader, so this fader is just the speed and size. 

    If you wish to adjust the speed of the effect separately, you can do this with speed override. Speed override can be found on the second encoder wheel when you press Z/Shift, and can be used to speed up/slow down effects running on the currently viewed playback. To view a playback, press and hold VIEW and tap the playback button. 

    Hope this helps,

    Edward

  10. Hi Peter,

    The only thing I could think happened, is that you patched fixture 35 in the Fixture Schedule, focused whilst still in the Fixture Schedule, and then switched the console off. Setup settings and patch will not be saved continuously whilst you're in Setup, hence why you see the save text when you exit Setup as all your changes are saved. Could this be what you did?

    Could you have edited another fixture's address to conflict with fixture 35? If so you will have received a warning, where if you had pressed "Patch Anyway", the console will have removed fixture 35's DMX address. I noticed fixture 36 is also unpatched, so perhaps the same happened to this fixture?

    Edward

  11. Hi Oliver,

    Thanks for the information and for testing this. We have received your email to support. We will reply with the best steps to make next.

    If you have any question let us know.

    Edward

  12. Hi Oliver,

    I'd recommend getting a can of air duster, and squirting this in the problem fader, and running it up and down with normal pressure applied.

    If you then boot the console with SETUP held down, you will then be able to see the fader behaviour on screen. If this fader is still registering incorrect values as you move it, the console may need a replacement fader. 

    Feel free to send us an email to support@zero88.com, and we can advise on replacement.

    If you have any questions let us know.

    Edward

     

    (I saw your personal message to me, but figured it would make sense to keep this all in one thread).

  13. Hi Rob,

    2 hours ago, robhurt said:

    Hi Edward, 

    Any idea what release these updates will make? 

    Thanks

    Rob

    I’m not sure off the top of my head, will have to check when I’m next in the office. Unfortunately we haven’t had many requests for these, so other enhancements have taken priority.

    The best way of achieving this behaviour currently, is to manually program colour, beam and position information in dark, to manually prep them. Therefore if you need a fixture to have timings different to the Move On Dark timing of the playback, record a cue with manual colour, beam and position information in with the fixture dark. To do this you will need to disable SmartTag in the Record Options window, to allow you to store a fixture with 0% intensity. You can then define your own custom fade times for the cue. You can also do this for the cue with the “Next” command in it. In this cue, prep your fixtures manually for the cue you’re jumping to - again with SmartTag disabled to store the colour, beam and position values with the fixture at 0%.

    Hope this helps, if you have any questions let me know.  

    Edward

  14. Hi Rob,

    As far as the console is concerned, it will be treating the CTO parameter just like any other, and it will be using the colour fade time at the same rate as the other colour parameters. As Kevin suggests, you may be seeing the CTO parameter fade from cooler colours into the warmer colours, and therefore go via blues. 

    The very basic description of how CTO typically works, is depending on the level of the CTO parameter, the fixture will essentially add a “max level” in for the RGBW parameters, and as the CTO is raised, the blue chips will be lowered, hence warming the colour temperature. This allows you to therefore mix a colour using the colour picker, and then warm it up by increasing the CTO.

    If you are getting some odd colour fades through doing this, I’d recommend programming second cue after the RGBW fade, and then change the CTO. This could automatically follow afterwards, and have its own custom fades to get the colour path you need.

    Hope this helps,

    Edward

     

×
×
  • 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.