Jump to content
Vari-Lite Controls Support Forum

kgallen

Regulars
  • Posts

    2,049
  • Joined

  • Last visited

  • Days Won

    105

kgallen last won the day on August 6

kgallen had the most liked content!

2 Followers

About kgallen

  • Birthday July 28

Recent Profile Visitors

129,325 profile views

kgallen's Achievements

  1. @Davidmk unless the desk is continually rebooting due to intermittent power I doubt such a fault would only affect the LCDs. Happy to be proven wrong!
  2. If you have no luck elsewhere, it's probably worth posting on the Blue Room too as there will be a lot of these desks (and the others I list) out in the wild. https://www.blue-room.org.uk/forum/2-lighting/
  3. You were possibly referring to a post on here or the Blue Room by our good friend Ian Knight @iank99. Unfortunately Ian is no longer with us and I don't know what happened to what would have been an extensive stock of new and used Zero88 spare parts. If anyone reading this knows if that stock was salvaged and can be purchased, then it would be useful to make this community aware.
  4. There's a non-gen one here. Can't vouch for it though (one user commented "don't work"): https://ultralightsound.co.uk/product/replacement-power-supplies-for-zero-88-desks/ I find this thread but the other two supplier links (10-out-of-10 and Stage Gear don't work any more). This page has the part number, which might be useful in searches as the same PSU is used by: Illusion, Jester, Juggler, Leap Frog 48/98, Solution in addition to the Frog series: https://www.vari-lite.com/global/products/frog-series#_spareparts There is this non-gen (maybe a ULS one): https://www.ebay.co.uk/itm/316738459895 There's a Jester thread here: https://www.blue-room.org.uk/topic/75786-zero88-jester-power-supply/ The OEM model number seems to be SPU41-13D-1 but having a google, other output connectors can be used. I suspect the Frog only uses the +5V with +12V only for the lamp; I suspect -12V isn't used.
  5. Ok good stuff. If I have a few spare moments some time (when it’s not sunny!) I might have a bash at building fixture definitions. I’ll post here if/when I do. Feel free to remind me if you need them!
  6. I’ve been having a look around the manuals/forum (without much success/clarity). This post seems to essentially confirm what you observed earlier - 16-bit dimming was added for ZerOS. I assumed, but not it seems, that my Fat Frog would support 16 bit dimming as I have fixtures defined as such. Seems I must be wrong as this thread was about Frog range. I would have thought however that Jester TL would do full 8-bit dimming rather than percentage, but again this seems maybe contrary to your earlier observations. This does bemuse me, because of course the processor is working in binary (and I very much doubt they went to the pain of using BCD!).
  7. I’m not sure if this would help but might be worth a play, if Jester supports Virtual Dimmer. Define a beamshape or position (something that will support 16 bit parameters) onto the channels that the fixture uses for MSB:LSB intensity, then a define a Virtual Dimmer then scale that 16 bit parameter with Virtual Dimmer. I wonder if that might be a method to get you better control at the bottom end. Might not work as a scale on a 16 bit value but as you seem up for a few wacky trials, might be worth a play.
  8. I don't see the ETC Colorsource V Zoom PAR listed either here: https://vari-lite.s3.eu-west-1.amazonaws.com/software-firmware/ZerOS-Library-4.5-RigSync-Support.csv or here: https://vari-lite.s3.eu-west-1.amazonaws.com/software-firmware/ZerOS-Library-4.5-List-of-Fixtures.csv which must mean it's not in the library and one reason why RigSync has not been able to patch the fixture, and has thus made a "bad stab" at creating one. Probably the RDM data just identifies intensity and non-intensity (I don't know) so the console has put most things as a Beam parameter (we historically put arbitrary control channels under Beam(shape) when there wasn't a better attribute, i.e. not colour or position). What would I do... I'd write my own fixture profile, and I can do that for you (if you're not otherwise au-fait with the Fixture Tools) if you can point me at the pdf for the fixture and tell me which modes are your priority.
  9. Hi Do you know the fixture will actually dim to/from zero smoothly? I have lots of different LED fixtures and only the most expensive (some Philips/Selecon fixtures) even remotely dim ‘smoothly’ to/from zero, and even then not as good as tungsten. Try patching the two intensity channels onto two faders patched as dimmers and see if the LSB fader gives you a smooth fade to/from zero. Commercial manufacturers are never going to release the source code of their products. It’s their IP and they wouldn’t want the bad press or support burden of scores of amateur hacked branches of code being out in the wild. The Fixture Software giving a warning about intensity being a WORD is normal and is a useful confirmation.
  10. Hi @alg A fixture listed in red in the Fixture Schedule means "not a library fixture" which usually means a fixture created by the user in the Fixture Tools (so I have a lot of fixtures listed in red as I write pretty much all of my own fixture definitions). But possibly it means a fixture created by the user on the on-console fixture create utility. Possibly, and more likely in your case, is the fixture identified by RigSync is not defined in the library and the console has put together a fixture definition based on the information it has obtained from the fixture using RDM (=RigSync). This information is possibly incomplete, erroneous or RigSync has interpreted it incorrectly. For whatever reason, the fixture has become patched with a profile that does not correctly define it. Can you unpatch them and patch them manually using a fixture profile from the on-console library? Or find a fixture definition for a similar ETC fixture? This may or may not be your long-term solution, but at this point it's really to help debug what's going on. I don't know if you have physical access to the fixtures to play with DMX addresses and modes.
  11. Hi @invisible It sounds like you’ve defined the fixture correctly. Are you testing this by pushing a fader? You will probably find that the fader has 8 bit resolution. However if you programme a cue with a fade you should find that the console fades with 16 bit resolution. That is what happens on my FLX - 8 bit on the fader, 16 bit from a memory. Here’s a thread where we were talking about this (FLX-S in this case):
  12. @Phil Kiernan are these your words of from Vari-lite? ie is this the firmest suggestion yet there will be at least one more ZerOS release?
  13. Hi @Davidmk Of course you’re right - I just wanted to note that the use mode might be restricting what @ATC Tech might be trying to do if they’d opted for Cue Only thinking it would be ‘simpler’ but might be hampering them.
  14. Are you in Cue Only mode? You seem to need to record-all (snapshots) using Shift+Record. This is rarely a good thing - it effectively nulls many desk features like playback overlaying, tracking, move on dark. You are effectively using the desk in a very basic mode.
×
×
  • 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.