kgallen

Oh right… the 7.13 update video is on the Varilite YouTube channel, not the Zero88 one - explains why I couldn’t find it. Some cross linking required if this is a permanent change of clothes?

Hi Jon, It's quite likely the current Auto Effects library will have what I need - once I've worked out how to tweak them to my needs. The additions you made a couple of ZerOS back were very useful, I was just curious if you'd had more ideas/requests and were building more options in. I'll ask in a new/separate thread how you guys might suggest I build a certain effect (with LED movers). Thanks! Kevin

Of course we're forever ungrateful and are intrigued what is being worked on for 7.14 (or beyond)! 😀 Possibly the wrong thread to ask in but I'm interested if there is anything upcoming for the (FLX) Effects Engine or it you might add more preset effects to the library (I'm not sure if you can add these via a library update or if it would require a new ZerOS release). My next show in October will require me to us a lot more movement and colour effects (I realise there won't be a new ZerOS before then!).

Great work guys (and gals)! Good also that you're consistently flagging these releases on blue-room.org.uk 👍

You’re pretty experienced so I guess you’ve tried Setup+Button ?

A conventional fixture is a very simple electrical device. If they ‘fail PAT’ then the fix to make them ‘pass PAT’ should be very straightforward. If they fail earth bond replace the earth bonding inside the lantern and the main flex with 180 C silicone. If they fail insulation then just the main flex should do it. I think you came here from BlueRoom. If so I’m glad to hear you are going to keep you conventionals (for now at least!).

Hi Edward, thanks! - But there are some "limitations" with staying with the "red" fixtures though aren't there - like not being able to do fixture swap-out/morphing? Of course any fixtures designed by the user using the Fixture Tools will always be "red" and carry these limitations.

I think that happened with 7.11 due to the underlying library format change to support multi-cell fixtures. I'm in a similar place with mine and went through an exercise of trying to find the "updated" library fixtures for the many fixtures I have. I didn't find it a particularly quick process, in part because of the manufacturer versus brand partitioning. I think the desk could be much more helpful here in finding the equivalent and supporting a better search. I did question and document my experience on this forum, I'm not just complaining now, and it seemed in accordance with what the software does, but I don't think the situation is particularly good. Some enhancements were filed or promoted as a result of feedback, so it's worth you also having a play and noting your thoughts as Z88 are generally very receptive to user comments. (The linked thread is in the Beta Test forum, some users might not be able to access it).

On FLX , tracking is not scary. With SmartTag enabled tracking will seem to you as Cue Only, but will give you some behind the scenes benefit as you move to more non-conventional fixtures. Move on dark just works in the background for any fixture that needs to do some ‘prep’, but your programming style can stop MOD working when you need it to. Cue Only mode is the main Achilles Heel. My rigs are between 50% and 75% conventional too. It’s worth getting into the habit of using the ‘more advanced’ style to future proof your learning. Take a look at the excellent videos Edward has put on YouTube. At least one of these will also help you debug the scenario you raise here.

From your screenshots what I think is happening is the default trigger threshold is 5%. As you move up the fader the LEDs intensity raises but the colour trigger doesn’t happen until 5%. You should set the playback button to GO function (Setup+Playback) and press that button before raising the fader to ‘prep’ your LEDs. You could try reducing the trigger threshold and/or disabling release on lower if that would work in the context of your other playbacks. The latter could cause issues though if you want to overlay playbacks.

...and as a bonus we get Edward to remind us all again how to use "Remove" 😝

If they are all the same type in the same mode (ie identical patch and parameters) then yes I believe that should work…

Re-inspect your handy-work carefully. Did you create a solder bridge? Did you damage a pad? Did you take antistatic precautions? Did you dislodge a cable when reassembling? Did you accidentally change any DIP switches? Did you use the correct fader part? (i.e. did you buy from Z88 or a service centre - if you're used to repairing sound equipment I'm assuming you know how to identify the correct component, value and curve type...) Maybe @KWR88 can tell you how to get into test mode to test all of the faders and buttons.

You can programme a keys macro and assign to a UDK if you want. I did this last show but I never used it, I’ve got used to typing the key sequence! If you use the macro you can automatically get the cue named at the same time (e.g. DBO or Blackout to your pref). The other option is ENTER ENTER @. But I think this has the downside if you edit earlier cues and those changes track forwards you will no longer have a blackout. @Edward Z88 to advise! Kevin

Here-here / hear-hear (whatever the heck it is).

Jon - none of us can keep up with your email address changes! 🤣 eaton.com signify.com zero88.com varilite.com?

🤣😜👍

https://plsn.com/featured/featured-slider/signify-rebranding-strategy-covering-strand-vari-lite-and-zero-88/ Discuss...

Fantastic 🙂👍 Save Setup & Palettes: This options saves everything EXCEPT cues and UDKs. So as a tester: this would include user MACRO definitions? 🙃

Side topic - Edward could you improve the document to explain Save Setup Only and Save Setup & Palettes. They are mentioned but there is no description of what "Setup" information is - of course I could guess but the documentation needs to be explicit and say what is (and isn't included). Palettes is hopefully more obvious but I think the documentation should still be more explicit, if nothing else, to mention anything in this scope that is excluded. For example are the picture images included in Colour Palettes? A contrived example I admit, but this is exactly why the documentation does actually need to say and not assume.

Yea I can see Cue Only is a big limitation here, particularly stopping you overlaying operations since "all data is recorded in all cues" (or at least that's how the desk plays them back regardless of how the information is represented in the internal datastructure) - so you lose the ability of another cue taking control over a parameter. I came to FLX from Fat Frog. On Fat Frog the few times I used Partial mode I ran back to Full mode because I lost control of what Partial was doing. I've not had the same experience with FLX. I'm always in Tracking On mode and never have I felt the need or even the inclination to go to Cue Only mode. Compared to really advanced users, I don't do anything "that fancy" although I do have a reasonable number of LED and mover fixtures (although surprisingly on my last show, conventional fixtures did outnumber LEDs 2:1 which was unusual, usually it's closer to 1:1). So, even as a "low-to-medium complexity" user myself, I'd encourage you away from Cue Only to Tracking. It really isn't at all scary, and SmartTag pretty much makes Tracking work the same way as Cue Only for 95% of cases and move on dark works beautifully in the background [1]. It's only when you want some finer grained control (or Remove!) do you need to start fiddling with SmartTag in my experience (which is theatre). I've had my FLX since 2015, so have done quite a few shows with it. Go on, you know you want to! Kevin [1] Tip: Programme a blackout with "1 THRU @ ."

Eric, Coming back to your initial question: I agree I would not use a USB stick for "long term" storage. I copy the show files from the USB stick onto my PC which as a RAID NAS attached. The USB stick is purely a mechanism to get data to and from the FLX and my main computer. In this respect, it's adequate. Maybe I interpreted your initial question wrong. USB sticks are of course a portable medium. SSD (in terms of the solid-state HDD replacement) is more usually semi-permanently attached inside a computer - they usually have some version of SATA interface. This isn't hot-pluggable in the way that USB memory sticks are, so "SSD" wouldn't be a replacement for USB on the FLX. Kevin

When plugged into FLX front panel or via a USB hub in rear port I haven't had an issue with USB sticks (Zero88 or other branded) becoming unusable or corrupted. Aside: The issue I do have, is since the USB sockets are not labelled on the FLX, is knowing which of the USB keys is associated with the port name provided by the GUI. I have had issues with USB sticks (including a Zero88 one) being corrupted and becoming unusable when connected to a Windows10 machine, but not when connected to FLX. I don't believe an SSD card would be any more reliable. The underlying Flash memory technology is the same, only the interface is different, and I don't have any reason to trust SSD over USB.

I was just reading a reddit article and it made me think about the issue many of us have with non-premium LED fixtures and their inability to dim nicely at the bottom end. The suggestion in this thread is to add a delay to the dimming instructions to LED fixtures to help them blend with traditional fixture dimming. Maybe this is something that could be added to a fixture in patch - a delay to the dim value being output. (This would be analogous in sound to applying a delay to an audio output for particular physical outputs).

My extra 2p worth too, if the issue is with an Effects palette, then I've found it easier to delete the darn thing and start again. I think the last time I had that issue Edward agreed that is often the easiest approach! Above should be good though for a normal cue or single cue playback. Let us know if it worked!