kgallen

😂

Use SETUP+PB button and set the shifted option to Pause. Then button=GO, shift+button=Pause/Back

See here: http://support.zero88.com/Legacy-products/Legacy-Consoles/Legacy-ZerOS/ORB-XF/975056031/Compatible-touchscreen-monitors-with-ZerOS-consoles.htm I think I've got the Iiyama 1731SR-B which is the one that Zero88 use for their training and demos etc.

On my FLX (not FLX S), I connect the touch screen to one (rear) USB port, then in the other (rear) USB port I have a 4-way Belkin unpowered hub with keyboard, mouse and sometimes USB stick (usually I use the USB port on the top of the FLX for the USB stick). Zero88 would recommend a powered hub, but if you're sensible with what you attach I think you're ok for an unpowered one in the keyboard/mouse application. Jon/Edward may disagree. It's possible the different USB ports can support different power requirements, but certainly on FLX I know Jon said they did lots of USB power load testing... Mileage may vary slightly on FLX S - I don't know how many USB ports are on the S24 or S48.

I recon this is RDM data that is not handled by the fixture. If you want to use RDM (RigSync) I think you can work around this by addressing the non-tolerant fixtures higher up the DMX address range. Jon mentioned this in some post a while back, something like above address 200. I'll see if I can find the post. Lots of my "cheapo/£200-range" fixtures are not tolerant to RDM packets. ETA: My post crossed with Edward's above. His is, as usual, a much better answer!

If you're logged in to the Forum, see if you have a "Software Testing and Beta Releases" section under "PRODUCT SUPPORT - SOFTWARE". The 7.9.4.7 Beta is listed under there. If not, worth dropping Jon an email: JonHole@eaton.com

Yes do the same I guess!

Hi Matt, You can find 7.9.3 here:

Depending on the DMX details of the SunStrip, you need to identify the "unique" bit and the bit that is repeated per segment. The per-segment bit is probably just RGB, so just patch "n" consecutive generic RGB fixtures from the first DMX address of the first degment. For the "unique" bit - which will have some control channels specific to the model of SunStrip - you need a fixture definition just for this bit. This might already be in the library, if not then send a link to the manual to FixtureSupport@Zero88.com explaining what you want to do, and they'll make up the fixture definition parts you need. If you search the forum for sunstrip there have been a few queries related to yours, so these might help or point you in the right direction. Kevin

Your monitor needs to support DVI-D because the desk doesn't output DVI-A or VGA. Most half-decent computer monitors should support DVI-D. The NEC LCD2170NX I'm using now on this PC is about 10 years old and it has DVI-D. It doesn't need to be touch screen. Datasheet: https://www.zero88.com/datasheets/FLX_S48_Datasheet_UK_Rev2_0418.pdf

Did you plug the USB cable back in as well as the DVI-D?

I recently had an issue with one of our Betapack 1's where there was some instability/flicker on channels 3 and 4. Tonight I've tracked that down to loose nuts on the mains inlet - not the ones on top of the phase joining bar, but the ones *underneath* that clamp the M6 bolts to the metal phase plates on the PCB. You will only find this by removing the phase joining bar which otherwise holds the three bolts locked together (assuming the top nuts are tight which are the easy ones to check!). Pair of 10mm spanners to tighten. Check all three phases and the neutral too, as whilst phase 2 was distinctly loose on mine, phase 3 and the neutral also needed a tweak. There should be spring washers in place too under the nuts. Diagnosed by having some lamps plugged in and tapping around the case with the rubber handle end of a screwdriver and seeing some flicker and hearing a little buzzing/crackling every now and again! Recording for the reference of others competent to remove the rear panel - danger, mains voltages, unplug/isolate before doing so!

Hi Edward, You are right, certainly from "cold" this works correctly on 7.9.4. At the time I had the "issue" I had been programming other playbacks, and had then gone back to PB0 to add the trigger macros into the main cue stack. I'll try to keep a watchful eye next time I'm doing this! Thanks, Kevin

Page 23 in the User Manual: https://zero88.com/manuals/FLX S User Manual v1.pdf "Deleting Cues To delete a cue, press the Delete button, press Ⓩ , and then type the cue number you wish to delete (for example 15 ), and then press the Playback button which contains the cue you wish to delete (for example, the Master Playback). To delete multiple cues, the “thru” button can be used (for example 15 Thru 20 ). To delete all cues within a playback, see “Deleting playbacks” on page 16. Deleting a cue cannot be undone." Cues are not renumbered, so yes, you will have a "hole" between cue 5 and cue 7.

Might be some defaults have changed and the old programming set those defaults to "the old method" rather than what we'd expect from a "fresh" desk. Good stuff!

(Edward will give you a clearer answer in a moment I'm sure!) Yes that should do exactly what you want. If you clear the programmer then you should just be able to push up that playback fader and get all of those lights to fade up, and likewise fade down when you pull down the fader.

Hi Edward, Thanks for your quick replies. OK, I'll check this, thanks. Yes, in the end I used Clear+F/F. I did try some "SmartTag off" but I think I'm still a bit of a novice on this one! (Yes I agree there should be nothing to worry about, just tag the stuff you want, but I'm not sure I always get quite what I expect!). I think my mistake was I *selected" the fixtures I wanted to remove, and missed out the "(Untag [Intensity])" step. I need to practice the Remove process at home I think as I never get it to work when I need it (user error not desk error!). Yes now I've had a good play with it I understand it more now - I can see it's powerful, I'm just not always sure which "base effect" to start with and what then to adjust. Your detail earlier in this thread was a great help. I've not needed to use it recently but the Waveforms tab is the worst for me - the touch boxes are just way too small for me to use reliably. Looking forward to seeing what you guys have come up with - I'd like to use the Effects feature a lot more... Aha... I'm not going mad then! Regards, Kevin

One (ok maybe more than one it seems...) other question from my plotting. So I have a stack on PB0 and I also have some chases on other PBs that I trigger from PB0 (as discussed above). So with some fictional cue/PB numbers for ease: PB0/1 triggers chase on PB7 PB0/2 adds some conventionals in When I've GO on PB0/2 I decide I want to tweak the level of the conventionals, so I select them and tweak the levels. I now want to update PB0/2, but of course I don't want to capture the current state of the chase running on the "unrelated" PB7 into PB0/2. How do I do this? -> When I was plotting I had an "issue" where I was RECORDing this cue, and it captured not only the fixtures I'd added in but also the current state of the chase that was "running in the background". This captured a "freeze" of the chase into the new cue. Try as I might, I could not use "Remove" to get rid of those chase fixtures. In the end I had to delete the cue, release the chase manually (Clear+Chan/PB), then record the state changes for that cue (without the triggered PB7 chase running), then go back to the trigger cue and run through from there to check. Now I guess this kind of makes sense, but I wasn't expecting it and I wondered if there was a "better" way. Other than that the show is looking good and I'm very much appreciative of your help... and I've learnt a lot more about the desk and especially the Effects engine. I would like to note (as others have) that the documentation is very weak here - I ended up going through a lot of the (colour) effects and with the insight you gave me earlier (on Blue Rainbow etc), work out what e.g. "Red Step On" actually did - how the base colour was formed and what the effect waveform modulated on top. So I understand a bit more now how I can e.g. get a red base and swoosh a yellow through it... One other thing - I think I noted it a while back: I set up a number of Groups, with the selection order carefully defined. So 1 THRU 5 and another 5 THRU 1. I expected 1 THRU 5 and "Forward Individually" to go 1,2,3,4,5 but it always seemed to go 5.4.3.2.1. Likewise "Backwards" did 1,2,3,4,5. Random did what I expected! Thanks, Kevin

My comments relate to PB0 - I'm not sure about the others. It gets me every time! I press GO and nothing happens and I scratch my head wondering why the lights aren't coming on... then I remember... However hold the thought, we have a Dress Rehearsal tonight, so I will do a cold boot and see if PB0 GO will get the house lights/stage preset up without me needing to cycle the PB0 fader...

Hi Edward, Thank you for your replies! (Hope term has started ok too!) Tomorrow we are doing the LX plot, so I'll be filling in the gaps of cue 1 etc - but this detail is useful, because I think some of those earlier cues are going to be busked, so I might well need to do the encoder business you detail above - thanks! Thanks for the explanation. I must find that console cue fade default you identify above! Ok - thanks for confirming, I suspected this might be the case! I will have been whizzing between all sorts of windows - at the time I didn't have an external monitor, so doing everything on the internal screen. At least with View or Z or with my usual show setup with Mouse and Keyboard this should be less of an issue! It's a known "issue" - actually it's probably not a bug as such as PB0 behaves the same as other PBs in that you need to raise the PB fader from 0 to trigger the PB - pressing the Go button with the PB0 fader at full (from power up) is not enough. My FLX usually has the PB0 fader left up at full as I'm generally using a cue stack on PB0 (and effectively it's just like the Frog Playback X fader to me, although I know it is "so much more" on FLX). What this means is when I start playing around I get no output then scratch my head for a while until I realise I need to drop and re-raise the PB0 fader to actually get some output. There is a ZOS for it and I do tease Jon every now again that it's not "fixed". I probably understand why that is ("not a bug") but it is a bit annoying nontheless! Much appreciating your help this week or so. Within a couple of days I should stop asking dumb questions (for a couple of weeks anyway!). Cheers! (Not sure how to send you a real or virtual pint, so that will have to do for now! I've been rigging all day, I could do with some refreshment too!) Kevin

Hi Perry, I'm not sure the ZerOS Release Notes come bundled for all releases. Probably best if you email Jon/Edward or the generic Zero88 email address (support@zero88.com) and ask for them. I don't think there is much back-catalogue on the Download site, I can only find 7.9.4 and 7.9.3. Kevin

Hi Edward, In the attached showfile, I am using playback triggering from the master playback. [1] In cues 7 through 10 I am triggering playback 3 or playback 4 (and releasing the other). I am observing a 3s fade for each of these cues: Why is this? None of the playbacks have a fade time other than zero, and I've also disabled MOD, which is the only other anything I can find with a non-zero time. You can see this on the Outputs Screen on fixtures 59 thru 63: they drop intensity to 0 and fade up to 100% over about 3s. [2] Also when I step between pb3 and pb4 I get a brief 100% flash, like the cue briefly snapped to full. [3] In this show file, I now use pb3 to release pb4 and vise-versa. This is because when I did this in stack 0 in the cues, e.g. cue 8 triggers pb4 and releases pb3, I saw a delay again of about 3s between pressing GO and pb4 taking effect - this is not ok! This is all a little confusing... [4] Also I find with pb3 and pb4, which are rainbow effects using Fan-V (as we've been discussing), I can't get Global Tap Tempo or Tap Tempo button to make any difference - can't set the Effect speed. Should I be able to? I can get Speed Override to work. You can see in this showfile that I've assigned PB13 to this function. Change the function to Global Tempo and it doesn't do anything. Same under the Z key - speed override works, Global Tempo encoder changes nothing. [5] I'm also having lots of occasions where the cursor keys have no control over the Next bar or "Spreadsheet" cue edit boxes: I think the console has locked up (it hasn't). I find I need to press the Z key twice to get them working again. [6] Of course having to initially drop and raise the fader on PB0 tripped me up yet again... 🤬 Thanks, Kevin MMCsetup2.isf

Hi Dan, I don't think you can on FLX... at the moment it doesn't have configurable screens 😞 I would like some reassignment flexibility too, like the groups screen, so hopefully this will come along sometime soon... Kevin

Good work - sounds like you are in business now! Enjoy 😊

Thanks Edward - yes, this is what I did in the end (see "Bug?" report in the Software Test forum!).