kgallen

I guess for a variable fade chase you could keep your cue stack and use Auto Trigger to cycle through the cues. In the cue list, choose the Settings button (or select the Cue Options cell and press enter).

Edward. That will be the critical ‘right click’ bit... 🤦‍♂️Doh.

Hi Edward, So these are the instructions in the KB: To set the IP address of a PC as per Windows 10: Right click Start, and choose "Network Connections", to open Control Panel Double Click on "Ethernet" Double click “Internet Protocol Version 4 (TCP/IPv4)”, and click “Use the Following IP Address” then set the IP to 2.1.1.10 and the subnet to 255.0.0.0, and click OK. The sequence is a little longer than the list above - I've finally found it. I guess if you do this every day, then you know where it is! Start, "network connections" just gets me some useless web searches. Start "Control Panel" gets me of course to control panel app, but it's not at all clear how to then get to somewhere to set a fixed IP address (rather than say DHCP). I know the form you refer to but can't for the life of me find where the darn thing is in Win 10. Of course, they try to hide this kind of low level stuff more and more - it's comparable to Jon not wanting us to be able to access DMX values on the console! 😋 So finally I've found it: So once at Control Panel, we take "Network and Internet" then "View Network status and tasks"? Then "Connections: Local Area Connection" Then "Properties". Then select "Internet Protocol Version 4", Then "Properties". Then At last "Use the following IP address". 😆 One other question - I tried to use Phanton ZerOS with Capture - is that possible, or does it only work with a real desk? Thanks, Kevin

Edward - the Windows 10 PC IP setting instructions aren't correct (certainly not as April 2018). Can you elaborate/update in the article? Thanks.

Hi Eric We really should return to the FLX forum for these usage questions. Also it would be good for you to start new topics. This is because we will create a historical reference of knowledge on FLX and other FLX users can both learn and contribute to our collective knowledge. We will not find these answers in this part of the forum after a couple of months. In addition you will find your queries are missed as they are buried with other queries and bug reports -> start separate topics for each query, it's better that way! Regards the chase speed I am no expert but I understand there are two ways: On a playback programmed with a Chase, SETUP+playback button then Chase page will allow you to select Global Tempo or set a private BPM (beats per minute) tempo for this playback - either type BPM number or tap the MFF button for tempo (maybe button has to be configured for this). For global tempo, the speed can be set by a MFF. SETUP+playback button on an unprogrammed MFF will allow you to set that MFF as the tempo adjust on the fader. These should both be in the current user manual. Regards the manual I think this will only get updated with a major software revision. My personal view is that I agree the FLX manual is quite weak for such a complex product when I compare with other Zero88 manual and other brands. Other users have voiced their concerns back on the FLX forum. You can also use the Orb XF manual, the Knowledgebase and this forum for other support, plus whatever you can glean from the Release Notes. My wish would be that a Jon were more inclined towards the FLX product documentation but I suspect this is one aspect of his job he least enjoys, but conversely he does seem to devote his time to product definition, improvements and furthering the range. Edward does seem quite adept with both his product knowledge and descriptions here on this forum so maybe he might be persuaded to work on the product manual. Having the manual in electronic rather than paper form may be one way to keep the official documentation more in step with the software releases. Anyway enough of my waffle, but I hope that answers some of your queries even if it is only from another users perspective. Kevin

Eric - Edward just wants you to disable this function to try to debug your spurious light problem. Normally it is convenient to leave this setting enabled so when you move a channel MFF the channel is selected.

Well it needs more work to smarten it up a bit - adding gobo pictures and the like (depends which console you have). Sorry if I misinterpreted some of the French manual in places, I tried to get the right "intent"! At least it has got you going. Probably worth an email to FixtureSupport@Zero88.com to point at this Forum entry to get a full and complete set of fixture definitions built and added to the next official library release. All the best, Kevin

He lives! Phew! Welcome back Edward, hope you had a nice time! 😂

Hi Eric, <ENTER><ENTER> is a shortcut to select fixtures with intensity > 0 (get orange boxes around the channel numbers in the Output Window) <ENTER><ENTER> @. (at dot) (or <ENTER><ENTER>@0<ENTER> as you've used) will select any lit fixture and black it out. It only affects the intensity, it won't move position or beamshape.. Try <CLEAR><CLEAR> first to empty the programmer to be sure your commands are being interpreted correctly. Hope that helps. It's just a little "trick", nothing magical. This is from the manual, page 9, right column about a quarter of the way down: http://www.zero88.com/manuals/flx-user-manual-version-1.pdf Kevin

Good point Martin, thanks for the clarification. Kevin

It looks like you want "Blind" mode, but this article says Blind is not provided on FLX S unfortunately:

Eric - on you ghost, can you work without the fader wing for one session and see if you get any spurious lights? I don't have a Wing, and fortunately have never experienced this problem with my "bare" FLX. (Not commenting on your new thread as I know you'd like one of the Zero88 chaps to respond... Maybe they are at PLASA this week?)

Your application for shift+record would be for example the first cue of a new dance routine. This would stop tracked values from one dance from bleeding into the next dance. Shift+record is also useful for a blackout cue to avoid an update later put into an earlier cue from resulting in a unintended light on in an intended blackout. I wouldn’t otherwise overuse shift+record because you’ll lose the benefits of tracking and overlaying playbacks will likely result in unintended fixture behaviour.

I'm conscious we will distract from your important question regards the spurious lighting, however if I understand this latest question I would suggest: For a blackout on all fixtures you could do: <ENTER> <ENTER> @. (at dot) -> all fixtures will get intensity 0 (ENTER-ENTER selects all fixtures with intensity>0) SHIFT+RECORD -> create a blocking cue - record all parameters of all fixtures (SmartTag setting does not matter)

Eric - are you saying the fixture is being selected by the desk and the channel LED in the MFF button is coming on?

Sorry Monster I only managed to achieve the same as you did. Same happens in "latch" mode. Raise/Lower settings (Setup+Playback) didn't help either. Over to Edward/Jon...

Hmmm weird. Sorry I didn't reach a conclusion. I did/looked at: - a flick through the general setup - nothing unusual, no remotes set up. DMX output 1/2 has RigSync (RDM) enabled but overall RigSync is disabled (looks like the default -> RDM is off, so that can't be the cause). - the setup/operation of the 6 playbacks on page 2 - nothing unusual there, basic submaster usage - a run through the cue list on the master playback - nothing seemed out of place, no accidental strobes - no chases I could see or tracked issues on those channels It's interesting you say you can grab the errant channels intensity and release it and it stops the issue. Also you see it on an LED unit and a dimmer channel (conventional -> spot or fresnel?) For completeness, can you confirm you have DMX terminators on the lines and only a linear DMX topology (no passive splits). It's not an issue I've experienced on my desk (currently 7.9.4) to date.

Hi Bertrand, Give this a go. It is only a quick attempt and I've not had time tonight to put all of the details in of the gobo/prism/iris channels (ch18 on), but it should be detailed enough to get you going until one of the Z88 guys can build you a fully specified definition. Regards, Kevin servospot15k.ift

Eric - I've loaded your showfile in PhantomZerOS to have a look - can you tell us which channels were affected by the spurious lighting? Which fader did you grab?

Link the manual, say which modes are a priority for you.

It's a link to the beta test forum for those that can see it. Peter, I thought you were a beta tester too? Kevin

I don't see that ZOS-8363 is fixed in 7.9.4 (Release Notes) so I'm not sure if 2-way fader is going to work?

Well done Eric! Can you upload your show file here so Edward can take a look at what might have caused your spurious light? There can be many reasons! Earlier we were talking about tagging for your effect. I found this Knowledgebase article: http://support.zero88.com/Consoles/ORB-XF/1014189311/What-is-Tagging.htm

Edward will probably give better advice but I guess (as you suggest earlier) that intensity@0 means SmartTag does not record to effect off. For that cue when you go to record, on your external monitor you should get the record options page - turn off SmartTag for that record so fixtures with changed but intensity@0 will get recorded. Great photo. I see you get ch1-24 across one monitor line. That is nice, mine are spread across 2.

Your naming question is easy, I generally do the record and name in one movement, for cue 10: record 10 name <type name> enter To stop the mover effect you will need to choose Effect->No effect. You could do this when you record your blackout or go back and use Update. You can use shift+record to put in a blocking cue if needed. That’s quite an achievement if you’ve already run a show with moving lights less than a week having a brand new console!