kgallen

Maybe this was the thread, but I don't know how directly relevant it is. Might have a few things for you to check/compare or to trigger some thoughts of your own on settings etc. Sorry I don't have a direct answer.

I've had good success with Art-Net on my FLX. There was some thread a while back about some external tools not picking up the packets. Something to do with polling or broadcast or unicast or something like. I can't find the thread now of course and anyway it might not be relevant... I assume you've been through the relevant manual pages? Here it is before someone more knowledgeable comes along! https://www.zero88.com/manuals/zeros/setup/universes/art-net

These pages do specifically mention FLX, but as Solution runs "the same" ZerOS maybe worth giving them a try. Sorry if you already know about these! https://www.zero88.com/manuals/zeros/shortcuts/keyboard-shortcuts

I would email this to support@zero88.com as they will want to do some diagnostics with you.

You can set the intensity of a fixture then RECORD HOME will allow you to reprogramme the Home or Default values. https://www.zero88.com/manuals/zeros/controlling-fixtures/defaults

You should be able to use the on-desk Fixture Creator to do this (although I never have!). Let me see if I can find a manual reference… https://www.zero88.com/manuals/zeros/patching/add-fixtures/fixture-creator

Hi. Yes, use SHIFT+COPY for a MOVE. See this page in the manual ("MOVING CUES IN A PLAYBACK"): https://www.zero88.com/manuals/zeros/cues-playbacks/moving

I have the same and did query the Copy function on this Forum a few months back. Update with SmartTag on in this instance should be a clean way to prune out the data that is not needed in the cue as a result of the Copy which copies in "blocked" values to achieve the Copy. Edward explained this to me in that thread and the behaviour of Copy does make sense but my inner OCD makes me want to tidy up with the Update step. I'll see if I can link the thread later. Remove is a very specific operation. In your example above you talk about turning off their intensity. In the case of intensity, using Update with SmartTag is the easiest thing to do, and that the intensity is now being recorded at zero, the action of Update with SmartTag will be to prune any other attribute data (colour, position etc) for that fixture. (That is my understanding, @Edward Z88 to correct me if I'm wrong). Remove is a very specific operation that will prune from the recorded data, the specified parameters for that fixture. I often have this scenario when I'm experimenting with my next cue, trying some colours or moving position and then concluding that I didn't actually want to change those fixtures at all. In the case of those changes being in the programmer then I can use the backspace key and CLEAR to purge those changes. However once those changes are committed to a cue with a RECORD operation, then Remove is the mechanism to get the scissors out and to go back and to snip that data out of the cue as if the change was never there in the first place. This is of course different to the situation where I changed the colour but then decided I didn't want the fixture lit when I've recorded a change (to colour) that I can't see (because intensity is off) but has actually entered some data for that fixture in the recorded database. The key thing here is that using Remove to snip out those unintended, or unrequired changes, is that what happened before and what happens next is wholly unaffected, including any impact on Move on Dark. I've probably made a real meal of explaining that above and while I understand the principles and operation I wouldn't claim to be as adept at performing these edit operations on the console as I should be. So your queries do gain my sympathy. Maybe in some of these cases you should be selecting Track Backwards or Track Forwards with these changes. But I would expect if you are doing a Remove operation on cue #n then the tidy-up in that cue should directly benefit cue #(n-1) and cue #(n+1) implicitly because the fixture changes that were not required are now purged from the programme. Again, easy on my part to say this and I confess that I go through the same stressful period as you're conveying. I think that's because we probably don't do these operations very often and are a little apprehensive that they'll have an impact that we didn't expect. Then, because the console doesn't have any real Undo type function (once the command line has been committed), we're in a position where we can't Undo to recover what we had (even though it was "wrong") in order to attempt another approach. So I realise I might not have helped much there. Maybe some words of comfort if nothing else, that you aren't going mad and several aspects also cause similar consternation to other users! I'm not sure if Edward is about at the moment, I'm sure once he frees up, he'll have some calming words for us both on these topics! Kevin

Rob, I'm sure Edward will make this for you. I did check the latest 4.5 library and I couldn't see that "740" type listed in the Ignite section. Regarding the Fixture Request link, it seemed to work ok for me. The page it takes you to, you do have to scroll to the bottom after all of the other options to " Click here to email us with your fixture request". Then I get an email template as follow which sends to the email address "FixtureSupport@Zero88.com" *** REMEMBER TO ATTACH (OR LINK TO) THE FIXTURE'S OFFICIAL MANUAL *** Direct link to Fixture's manual (if not attached): If the fixture has modes, which mode do you require: Which Zero 88 console is this for: What is your ideal required date*: *Although we will endeavour to achieve your ideal required date, we cannot guarantee completion by this date. If you require a quick turnaround, please consider using Fixture Tools to create this personality yourself - available to download, for free, from zero88.com/library *** Fixtures will be created as per the fixture manufacture’s manual and our database syntax. Requests to divert from this will be declined. ***

Off topic. I thought I'd be my usual pain and "stress test" the website. I went to the above link. I went to "VISIT OUR A-Z OF LEGACY PRODUCT MANUALS" I clicked "Entertainment Controls" I selected Product Sub Type=Lighting Consoles, I left Product Type at Entertainment Controls, I left Product Familty at All, I set Status=Discontinued I got "The filter criteria you have selected did not deliver any results" So where are my Frog, Jester, Orb, Solution, Level series, Alcora, Elara, Sirius manuals? Yes I'm sure you could give me a link - that's not the point, why doesn't this search, having followed the route given by the website, yield all of these juicy manuals for discontinued product? Yes I know I'm a PITA, but you've known that for years... 😁

Is there a battery in Solution? That would be my first check if so. CR2032 or similar is typical in Z88 products (at least those from this century!).

Not that I know of. I think this is due to the software needing to detect press-and-release versus press-and-hold so it uses the ‘falling edge’ to detect a press-and-release event. Of course I don’t actually know but this would be a typical approach in software (or hardware) where the button has multiple functions. Does the master go behave like this? Compared to the other playbacks. I rarely use the Go of other playbacks so maybe the master go works on the downward press? Sorry, a little off topic…

I think your settings are correct for what you want to do. Hopefully @Edward Z88 will confirm!

Recent example. The respondent has replied to my post quoting a Vari-lite page but still hasn't recognised in respect of the OP being suggested an "FLX-24" that FLX-S range is NOT discontinued as he continues to assert ambiguously. What's worse is kitlane is a UK operator and posts on Blue Room too. To be frank this is partly down to Zero88 continuing to use unclear/subtly similar product names for quite different products. (I won't mention "Leap Frog"!).

Note to Z88 folks ( @Edward Z88, @Jon Hole ) and other active members: It seems on other forums, misinformation is being spread that suggests or states (incorrectly) that all FLX - including FLX S- production has been stopped. Prospective buyers are being dissuaded from FLX S series consoles because they are "discontinued". I'm rebuffing this where I can, including a link to Jon's original statement at the top of this thread. Please be aware of this misinformation being propagated and do your bit to correct the statements where required.

No I wouldn’t switch off SmartTag. The only time SmartTag is a ‘pain’ is when needing to record ‘Effect Off’ going into a blackout. Unless you are a hyper-advanced user, or creating lots of overlayable busking playbacks, SmartTag will be your friend (so I’m not sure it creates ‘more problems than it solves’). What SmartTag does is stop you worrying about what fixture attributes are tagged in order to get them recorded into a cue, there isn’t anything really to ‘understand’ about it. If you turn it off, then you need to be on top of your game with what you want recording. If what you observe is truly a desk issue then @Edward Z88 needs to be able to reproduce it. I’ve never seen anything like this though in 9 years of having my FLX.

I’m not sure what in the fixture definition could cause this. Is this fixture well behaved (I guess I’m asking is it a cheap and nasty one!) - if you use it manually will it fade nicely to zero without doing silly colour things? If you record cue 1 freshly to a clean playback (say PB6), then use the fader to fade up then down, do you get the same bad behaviour? What if you assign another playback ad a Grand Master. If you light your fixture with PB6 and then use the GM to fade out is it still badly behaved? Did you record cue 2 with SmartTag off and change the colour as well as setting intensity to 0 when programming that cue? Is there a cue 3 with a different colour and did you set the move on dark delay to 0? just some ideas to try or confirm.

WTF??????!!!!! Oh no! I've known Ian since 1996 when he joined CTS. I bought my Alcora and FLX from him when he was there plus countless other theatre items as I'd hang about his "sweet shop" on a Saturday morning waiting for him to open up. He obviously contributed on this Forum regularly and we were loosely in contact over the years; I gave him my "spares" and he got me a Line Backer. I had no idea he was ill, or maybe he wasn't and this was a shock event. I'm speechless. I would also like to convey my sadness and condolences to his family. Kevin

Thank you for the updates and roadmap. The FLX S fixture and universe upgrades are interesting and welcome. I’m working on my local hall moving to FLX S. However I can’t help but feel a little scared for my own FLX. I hope you are genuinely able to keep supporting and developing for this platform as there is a lot a capability under the hood. Are you developing a replacement high-end console to supersede FLX or is the Neo-X now that offering? I’ve never seen Neo mentioned outside of Vari-lite - no one on any of the forums I contribute on ever mentions or recommends the product (and neither do I as I know nothing about it). FLX and FLX S do, despite their undoubted reduced market share compared to the ETC offerings. Thanks, Kevin

Oh no! Keith that is such a shame. But we have to all thank you for your many years of tireless support and answering all of our stupid questions. We will remember you with the ‘KR’ stickers inside of our equipment. With best wishes for whatever you are moving on to. If it’s still inside the entertainments industry then maybe we’ll see you around. If not, then good escape! Kevin

Looks like there is a Test Mode within Setup (SHIFT+MODE): Setup Mode JesterML Operating Manual 73-406-00 Issue 3.0 59 of 85 Test Mode This option is provided primarily for factory and dealer servicing only. It allows the hardware of the JesterML to be tested in isolation from setup options or programming in the show data, which can be useful in diagnosing some problems. Pressing a button will display it‟s name on the Main LCD, optionally toggle nearby LEDs, and optionally display the level of a nearby fader. The 7-segment displays will show a count pattern Wheel levels will be displayed on the wheel LCD. The DMX Input and Output ports will be tested (this test may fail if a DMX-Input source is present). Shaded colour bar patterns are displayed on the monitor output. MIDI test messages are transmitted if MIDI is enabled. Press ENTER to leave test mode and return to the Setup menu. Manual: https://www.vari-lite.com/b-dam/vari-lite/discontinued-products/jester/english/jesterml-manual-3-0.pdf See also this thread:

Marco I'm sure it will be something simple - but might be a ribbon cable come loose inside the desk. I expect it will be readily fixable, so don't worry. I can't find a Service Manual - there will be a test mode that can be enabled from boot that will allow testing of all buttons and faders. Hopefully Keith @KWR88 will be along shortly to help you diagnose the issue.

I don’t think you can directly with a UDK (*) What you need is an Inhibit playback. Record the same lights to another playback (probably you could copy) and then SETUP and set playback as an inhibit. But then I think you’ll have to drag the fader down for the ‘out’ which is not as snappy as just pressing a button. (*) There might be a convoluted way: create a macro to trigger the above inhibit playback and then set a UDK to trigger the macro. I’m sure Edward will have a better idea! ETA: On FLX you can now reconfigure the Blackout fader/button. Probably you could reprogram the Blackout fader/button as an Inhibit for just your above lights then hopefully the Blackout button is your "UDK". (Blackout is usually an Inhibit for the whole lighting rig).

Adding updated links for Alcora: https://www.vari-lite.com/global/products/alcora and Elara: https://www.vari-lite.com/global/products/elara

That all sounds in order. If your trigger cue only has the macro trigger and no other lights recorded then I’d expect fade times all to be blank. The next (or maybe a later) cue in your main stack will be a Release of PB1 to stop the effect. I’m not sure why your trigger is not happening. I’m assuming you are viewing and GO on your main cue stack. Maybe there are some other playback settings that are not default. I’ll have to defer to Edward for what other settings you should check.