kgallen

Ouch. Those things - even the "budget" brands (although in my experience Showtec are pretty good) - are expensive aren't they! Glad I can (currently) stay within the two universes of DMX XLR on my FLX! Good luck Mac! ETA: I bought the Brad Schiller book a while back. It's ok, but if you've been doing this stuff for more than a couple of months I don't think it will take you anywhere new. I'm certainly no expert on using movers - but I got one decent idea from the book - to lay out my palettes akin to the physical placement of the fixtures!

Maybe I miss something - and sorry if I'm stating the obvious! My assumption here is that the other end of that RJ45 is plugged into the back of the FLX. The RJ45 is carrying ArtNet or sACN. So to extract the DMX needs some "fancy" kit - it's not just DMX over the wires of the RJ45 cable that need breaking out from RJ45 to XLR. That Stairville FX4 is just that - an RJ45 to XLR breakout box (just some wires and connectors), it's not an ArtNet/sACN decoder. For ArtNet decode, you're into a lot more bucks than the £21 for that FX4. Zero's own offering for example include this, and you're in to many hundred of pounds. This one for example is a couple of grand! https://www.zero88.com/products/control/ethern8/index.shtml

When programming I find the cue stack listing and current/next bar behaviour really annoying - because by definition I'm at the end of the cue stack I'm always working at the bottom of the cue stack list on screen. When playing back then the "next" cue is in the centre of the screen cue list. This is fine. It's when programming it drives me batty... There are some screens provided on Orb that I've seen you chaps using the get more detailed information on cues/fixtures etc when debugging stuff. As you don't sell Orb anymore (so don't need feature-differentiation to FLX) can you port these screens to FLX? Of course now I want one, I can't find an example where you've done this on the forum to show here even though I've been looking for about an hour... 😣 Debugging RDM fixture setup is impossible. Like Erics above, "RDM controls to see RDM parameter from devices" please. I know you have some internal debug screens you use. Looking back there are a lot of ZOS enhancement requests that us early-adopters have raised. Would be good to see some of those make it into the software finally, or at least get some sort of roadmap so we can "reliably" know when to expect them. I'm including the ones from 2015-2016 that have "gone quiet"...

Can you share the symptoms for the rest of us? What ZerOS version?

Not on the console. The Fixture Tools can be used on a Windows PC to create new fixture definitions: http://support.zero88.com/Fixture-Library/975405071/Fixture-Tools.htm

I believe so. Even with the "old" Frog range I made that mistake, having the mind-set a colour palette needed to be "red" or "rosy pink" when in actual fact it could be any set of colours across the fixtures it was programmed for. Something I too should exploit more often but one does get artificially stuck in "this is my red palette", "this is my blue palette"! Same with beamshape and position. Beamshape could be whatever selection of gobos you wanted across a set of fixtures and you could easily have a position palette "jumbled about" as much as "line across"!

Select fixture. Beamshape. Press Beamshape until you get the gobo spin channel above one of the encoders. Wind encoder or maybe press encoder to see if there are any predefined settings. Please try to give a little more information in your posts (and give it a meaningful title) - one-liners really don't help us understand your issue or help us answer your question. We also like it when you pay attention to your spelling and grammar. Remember we're not sitting in front of the desk with you.

When you say "scroller" are you meaning a traditional colour scroller on a conventional (tungsten) fixture? If so, for Move on Dark to work, you need to use the composite dimmer+scroller fixture so the desk knows what intensity channel the scroller is associated with, then it can wait on dark before moving the scroll. Also, did you program the next cue as a Record All (Snapshot)? If so, Move On Dark can't work.

Shhhhhhhhhh. Jon will be writing the upgrade Invoice for you as we speak...

Good advice as ever from Edward, but do be aware you are going to eat through the supported fixture count on your desk with this multi-patching - although with an S48 you do have 96 to play with. More of a trade-off for those with a base S24 with a 48 limit. But as ever, you pays your money and makes your choice. Kevin

I’m not sure how the 3 channel ‘RGB’ fixture works because if they are colour channels then I don’t know where the desk gets the intensity information from. Hence recommending the RGB plus virtual intensity fixture. This is of course only 3 real DMX channels going out to your controller for R/G/B tape and the desk is using the so-called virtual intensity to scale the RGB values on those channels. This has the benefit that the colour picker will work, you can set the overall brightness with one fader, SmartTag will work and move-on-dark will work. Also you’ll be able to use any Effects with a colour component on your tape. These comments are applicable for any of the Zero88 desks with some or all of these features, from the Frog range through to all of the ZerOS-based consoles not just the FLX family. (I make this clarification for wider reference as we’re in the Fixture Library forum not an FLX-specific forum). Good luck! Kevin

There is nothing unusual about RGB LED tape from the lighting desk's point of view. It's just a number of DMX addresses. What you have to decide is whether you will control R/G/B elements as colour channels or intensity channels. I would suggest the RGB+Virtual-dimmer profile, this will allow you to use colour palettes with RGB tape. You should of course patch the "fixture" to a suitable DMX base address on the FLX-S that is also configured on the decoder using the DIP switches. I have FLX and have used RGB tape using this method. 3 pin or 5 pin should make no difference assuming it is wired correctly and your electronics at the decoder, tape and power supply end is sound.

Tapani - are you really solved with this issue because of the Release on Lower setting or do you still have a query related to the lime emitter ‘misbehaving’? With so many emitters in these ETC fixtures you’ll find the other colours on subsequent pages by pressing the Colour button multiple times. If not it would suggest the fixture definition is deficient Sorry if you’re an experienced user and already know this.

The quickest way is to write it yourself using the Fixture Tools: http://support.zero88.com/Fixture-Library/975405071/Fixture-Tools.htm The second way is to email Zero88 with a link to the pdf for the manual - and if the fixture has many DMX modes, if there is a particular one you need urgently: To requests new fixtures, please email us, ensuring you supply full details of the fixture (Make, Model, Mode) and a download link to the Operating Manual. FixtureSupport@Zero88.com Contacting the fixture manufacturer is likely to result in a deafening silence... Kevin

http://support.zero88.com/Legacy-Products/Legacy-Consoles/Legacy-ZerOS/ORB-XF/1011707591/What-does-the-Output-Window-show.htm Red – Programmer DataYellow– Highlight/RemDim, UDK Channel Data, Intensity defaulted to above 0%.Blue – Playback dataGreen – Value faded down in a cuePurple – Tracked ValueWhite - Blocked ValueRed Background – ParkedGrey Background – Moved On DarkLine above value – A Topset/Max Level is active

Another nugget of applications information that needs capturing somewhere safe...

Hi Edward, Can you please update the KB article with this - or at least equivalent - detailed information. I was interested in the process so had a read of the KB you quoted. The article really is lightweight in this respect as clearly from your replies on this thread there is more to setting up MIDI triggers than the article implies. The article simply says "MIDI Notes cause a Go to the cue corresponding to the Note-On message on the currently viewed/selected playback. Programmed Fade times are used, and velocity information is ignored." From your explanation above, it's quite clear the process is much more involved and requires MACROs - MACRO is not mentioned anywhere in the KB. Thanks, Kevin

Do you really need to delete them? Have you patched them to channels? In which case just unpatch them. So it depends what you mean by 'delete' them. If you really want to remove any trace of them from the desk then use Clear User or Factory Reset. Reset Desk won't remove user fixtures.

Requesting new fixture profiles To requests new fixtures, please email us, ensuring you supply full details of the fixture (Make, Model, Mode) and a download link to the Operating Manual. FixtureSupport@Zero88.com

If I remember correctly I think that came in 7.9.4. 🤔

Thanks for the clarification and tips Edward (as always!). Apologies to the OP for the slight thread steal but hopefully the information is relevant and useful!

Thanks Edward - is this the same a No Effect or would it HOME the fixtures C/B/P too (which is probably undesirable). Also creating the block cue would disrupt move-on-dark for other fixtures. If this understanding is right and hence there are implications, how else could this be achieved? Thanks, Kevin

I'm sure it's extremely bad practice and unnecessary if (a) I could use the desk properly (b) the desk was an incy-wincy bit better at handling this, but yes I do this too just to make sure the fixture is recorded. A common case is to ensure an Effect is removed from a fixture, by ensuring the "No Effect" is recorded into the cue - otherwise your heads keep moving about running the effect even though they are now dark. Given that some LEDs will light at 1% (which will be a DMX value of 2 or 3 typically) this doesn't always give you a "dark" fixture, so it depends on the fixture if you can get away with this fudge. I guess the proper way is to manually tag the fixtures for No Effect in the cue where the fixture is DBO (because SmartTag won't do it for you), but that is such a faff as you've already recorded the bulk of your cue with SmartTag then you have to go in again to deal with the fixtures with Effect to tag them and Update the cue. If there is more usable way then Edward or Jon will tell us in the next post... 😁

Hi. I benefit from move on dark all the time now and usually it works in the background without me even knowing or worrying. One mistake I made early days was in doing a record-all/snapshot cue which will stop MOD working, and understandably. Hopefully Jon’s instructions give you a starting point - subsequently just beware of the record-all trap! Kevin

Sorry guys I'm not sure I can reconcile these new "explanations", this is a plain bug surely. Other users have reported similar issues/confusion in other threads, that I've linked to this one to see if there is a common problem. Jon (apologies if you have followed the thread but:) - I'm recording an Effect palette. I can understand that if I was recording a Colour palette the desk would want to record just the colour attribute. Edward already confirmed early on that what I'm trying to do (which is not anything fancy) is reasonable and the desk should do as expected. Are you saying this is not the case and it's not a bug but some "unreasonable expectation" of what should happen given what the GUI is presenting as options? I select the required attributes for recording on Record Options then I press OK. It's not doing what I ask regards which attributes to record. Why have these Record Option buttons if the desk doesn't follow what options are enabled? I don't see what syntax or touch has got to do with it - the information required in the palette is there selected by buttons on the Record Options form. As stated above, I even follow your KB "Tagging" article and the desk does not behave in the way the KB article says - they KB says it in plain English "These tagging options allow you during the Record process to choose which attributes to include:", "Under Attributes, you can then go in and choose which attributes to include or ignore. ", "You can choose to include an attribute by tapping the Attribute soft button to include it and it will go red.". Is palette recording not following this same schema? Please be straight with us - if it's a bug, let's log it, fix it and move on, not dancing around some "legalese" language about "advanced" usage. If it's not a bug and expected behaviour then please clarify the KB and add it as an enhancement request so we can do it. Thanks as always, Kevin