kgallen

..and HOW do you want the 2 consoles to control the same lights? What is the responsibility of each console? How would the DMX universe be "carved up" for each console. We've already covered that an HTP merge is not going to work unless you only have dimmers. It makes no sense to have two active consoles controlling the same "intelligent" light (unless they are a specifically designed active/backup tracking pair). This merger for example: https://www.elmvideotechnology.com/store/dmx-merger-dmg-2x1?gclid=EAIaIQobChMIwcuSlL705wIVFuDtCh0ftQdiEAAYASAAEgKev_D_BwE claims to have an LTP merge mode. But still how would this work in practice? You have two lighting consoles (who have no knowledge of the commands sent by the other) giving likely conflicting data to one light, which is going to jump about trying to service both sets of unrelated commands, depending on how the merge picks DMX channels from each console. This is my "shouting at the kids" example from earlier. HTP mergers are often used if the venue has two lighting desks, but where only one is active/powered at a time. Say a very simple desk used by groups "who just want some light" and a more complex console used by "advanced" users. Tell us what type of fixtures you have in your rig and how you want the overall control surface to work.

HTP is fine for an intensity channel (e.g. a dimmer) but is likely a disaster for any other parameter (position, colour, beamshape) which would almost always be treated LTP. Your merger will work if you use one desk at a time (and the unused one outputs 0 on all channels - unlikely if you have ‘intelligent’ fixtures patched). Using both together unless you only have dimmers makes no sense to me. Think conceptually what you want to achieve and how it would actually work. With anything but dimmers I don’t think a merger is the answer. There is nothing wrong with your FLX S.

How would a merge actually work? FLX sends out a full 512 channel DMX packet. Where does the data from the other ‘master’ fit? If the other master sends channel data to a fixture that FLX thinks it’s controlling surely the fixture is going to jump unless somehow the other master is snooping what FLX is sending and builds some sort of transition from where FLX puts the fixture and the other master wants it, and the merger gives that master control over those channels. One master has to control the parameter of a fixture to get anything sensible out. If the merger gives alternate frames to the FLX and the other master, then these are two uncorrelated data streams and I can’t see how anything other than mayhem can result. Both you and your wife shout independent instructions alternately to your son and see if anything useful results! "Get your shoes on" "Go clean your teeth" "Comb your hair" "Pack your school bag"! -> I dont really understand how this can work sensibly. Maybe I’m about to learn!

If you're suitably competent, maybe worth opening the desk up an checking for loose ribbon cables. Maybe Edward can consult the mechanical drawings and advise if this screen is directly soldered or if there is a candidate cable of some sort. Also the minimal set of screws to remove to gain access. On Fat Frog for instance (similar case design) it is just one per side, the lower one to the rear of the side panels.

...and that, you will have to pay (quite a lot) for! 😈

You don't need to pay any more money. The desks are limited by channel count (2048 on unexpanded FLX) not by Universe. When you patch a fixture you can assign the DMX address to any universe 1-64. Under Setup you might need to check that the universe is enabled and which physical output (XLR) it's assigned to. But no, I've not currently ever done this myself! 🤣 Kevin

Peter, Take some screenshots from this page and assemble yourself a couple of images that can be uploaded to the image picker. Second prize I guess... Lee Filters (Chroma Order) Lee Filters (Number Order) It's a little project someone on this thread might even pick up...

No idea really but might be worth disabling RDM (in Setup) just in case there is something coming back from the merger that is confusing the desk. Kevin

Probably. I start from the Tab at the top of the forum which takes you here: http://support.zero88.com/ Many useful articles are within "ORB XF" but that is almost impossible to find because it's only within one branch of the tree and that is either an orphan or can only be found by luck from one point. Not all of the ORB XF KBs are ported under FLX (for example). Search only works if you know what you're searching for. My usual situation is "Oh, there is KB on that somewhere, I don't know what it's called but it describes the 'X'. I'll go in the KB and have a dig around to see if I can stumble across the thing I'm looking for." -> result is always frustration and usually failure to find the information.

You did a better job. I failed to find that KB on the radical changes which I wanted to link... (KB a bigger impenetrable mess than ever now, how is the "reorg" going?)

Edward just beat me to it...! You should be able to go direct, however prior to 7.8.3 you had to use a "bootable USB" stick. This thread has some instructions: Also note the whole concept of submasters vs playbacks has changed. Do this update when you've got time to understand the new features/operation.

If this is a "multi-cell" device, then the current recommended approach is to have two fixture definitions: 1st definition has all of the "master" controls that affect all cell (e.g. master dimmer, strobe), 2nd definition has the "cell" parameters (e.g. R,G,B,W). One instance of the "master" is patched as a fixture, then one "cell" is patched for each segment of the device. In this way you are able to use the Palettes and Effects section across the whole multi-part fixture. Looking at the spec for the Elation sixbar 1000, you would have a fixture defined for RGBAW+UV and instance it 12 times. Plus one instance of the "master" section will mean that one of these units will look like 13 fixtures. You will then have full control of each segment of the fixture and can apply palettes and effects across it. Improving this user interface I understand requires ZerOS to be changed to support a different library format (Carallon library). I understand this work is well advanced but users have been waiting some time (.....) for this update.

It sounds like the fixture definition could be bad. Can you post a link to the manual here and also send to Zero88 https://zero88.com/library#support

Just got an email for your above post on this thread, but a different cause: "Prefer to stop receiving these emails? Adjust your notification preferences." So that one must have come about from one of the email prefs I changed. Oh and the bl**dy bell now! 🤣 I bet Peter is getting lots of spam now with the same settings!

It's started... just got "Patching without a monitor?" update email... However the quoted reason is "You are receiving this email because you are following Edward- Z88" rather than it being triggered by following or contributing. And just got a "bell" notification. It never rains...! (Just checked, I've not contributed to that thread, although I've been reading it.)

OK as many boxes as I can area ticked. There are 8 selections that are greyed out "Administrator has inhibited this feature". I'm the same as Peter now with the addition of a tick in "Show popup window when I receive a new personal message". Spam folder at the ready...!!!

Neither (yet). But that could be my Notification setup looking earlier, I don't think I'm enabled for quotes. I'll go and change that now. I already have the two "Automatically follow" settings like Peter has above which you would think would generate some email traffic. Last email I got was from Oli's post on his fader problem. This is an FLX Forum post, and I follow that Forum. But there are plenty more posts there than I get emails for. Before then, "ZerOS7.9.7 Release" (December). Before then a post on "Understanding Smart Tag" (also Dec), before then a post on "New firmware and global bpm" (November), before then "Programming Additional Movers" (October) and before that "ZerOS 7.9.6 Released" (September). So pretty random and about one a month then (2 in December, none in January!), and we both know there is a lot more traffic than that on the Forum that I'm likely to be interested in. If the latest Forum software is supposed to be reliable then it could be my settings (probably close to default). Certainly in the past it's been "good for nuthin'" ! ...and they aren't going into spam, I do get them when they come! ...oh but I do get "everything" in the Forum notification - the bell icon at the top gets a red dot when you quote me.

I find email notification very spurious/random and it's been this way for years. I follow/contribute to a fair number of posts and normally get no emails. On occasion I'll get an email to say there is a new post, but it seems a random event. Sometimes (though rarely) I'll get a "Weekly Digest", but it's always "old news" as I'm generally on the forum quite regularly. Conclusion -> email notification is of little practical use to me at least!

Maybe a dodgy solder joint... Sounds like it needs opening up - depends on your warranty status. Advice from Z88 incoming...!

I don’t know this fixture but I expect the CTO is implemented on a separate DMX channel to the vanilla RGB, so the RGB channels are ‘fading down’ whilst the CTO channel ‘fades up’. But the CTO channel is probably bands of DMX values giving different CTC/CTO temperatures, so what you get is RGB fading down whilst CTO steps up through a number of CTC (blue) settings until it hits the CTO range. I expect the CTO/CTC is just implemented with an appropriate mix of RGB than anything clever.

I do avoid blocking cues these days because of the impact on move on dark. If you have a ‘pre’ cue where the fixture is dark then you shouldn’t need to ‘pre-place’ the mover. Before we had move on dark functionality we had to do this and it was called a marking cue. Now with desk move on dark and tracking, marking cues should be mostly unnecessary. In my last show I had a lot of mover activity - used as wash lights and as specials and with effects. By avoiding blocking cues, using position palettes and using tracking I don’t think I had a single issue with mover position being wrong. The time it does go wrong for me and it takes me a while to recover the programming, is when I accidentally tag and record a mover when I didn’t intend to. Then I have to go back and fight with my desk to do a cue update with a remove. But that’s an old story for me much covered on this forum!... (ps I’m also the sound man so also have to wear two hats at the same time, with complex equipment on the sound side too where I have to scratch my head and try to remember which page and menu a particular setting is in! I’ve had my FLX since 2015 and I’m still learning each time!)

Sorry Rob...! Edward - Can I get the MACRO to NAME the new cue at the same time with something like: RECORD MACRO x ENTER -> Commands -> 1 THRU @ . RECORD NAME "DBO" ENTER MACRO Hold on - that will probably name the MACRO rather than the RECORDed cue???

Interesting... I've been using ENTER ENTER @. which of course "only" turns off lights that are on (but is very quick and easy to type). Edward - with your syntax I guess this records every fixture at intensity 0 so you don't get the issue I potentially have with a tracked updating causing the DBO not to be dark? Hmmm like, that. Needs a macro though as you say as that is more a mouthful of keystrokes. I really must look up how to record and use Macros for keystrokes... Thanks! Kevin

(Edward posted about a half second before me - hope I don't contradict him!) If you're in Tracking and mostly using SmartTag, then I think you should be fine adding in the movers later: playing back the cue, using syntax/palettes to set up your movers and then using Update. Use of Cue Only will depend if you want the mover as set to only be in the current cue, or if you will put it in at an early cue (then allow it to track through some cues) then take it out at a later cue. In your Monday rehearsal, being able to step back and play over a sequence of cues would be a real benefit here. Not being able to would indeed worry me too. Depends on the type of rehearsal. Sometime at our techs, if they are faffing about on stage with some prop or costume, I'll go back a few cues and quickly step though any "thorny patch" to make sure the recording plays back as I expect. Also it depends if you have snapshot blocking cues. I used to always record a blackout as a blocking cue, but since using more movers I've stopped doing this now as it breaks move-on-dark. Of course there is always the hazard that you edit a cue before the DBO and find the light is still on in the DBO. With tracking though this is generally easy to see, as you only have to run the cue before the DBO then step into the DBO to check you really are dark - and do an Update to the DBO cue if you did indeed have something on due to tracking. If you're using Effects then you have to watch out that SmartTag will not record a "No Effect" if the light went dark. There are plenty of posts on this Forum with people saying "my lights are still dancing even though they are off". So if you add a mover in to a cue to do some dancing, then in the (next) cue where you want the dancing to stop, remember to: select your light, select No Effect, select @0, then when you do the Update, turn off Smart Tag (and remember SmartTag will stay off until you enable it again!!!) to ensure the No Effect gets recorded. Also with movers - and may be tricky in your timescale - is it's essential to have your Position Palettes set up, because messing about with Pan and Tilt during a rehearsal is just impractical as it takes so long. Get yourself ready by having your movers patched into the desk with the correct mode setting. Then record and name some placeholder palettes for DSL, DSC, DSR etc, so when you rig your movers, you can step through each position palette, set the mover there (yes this takes [me] ages), then Update your palette. Actually even at your first rehersal without the movers hung, you could programme your cues with the movers at non-zero intensity and having triggered the required position palette. Of course at this stage it will be a junk position. but when you have the mover rigged, it will at least come on and you can move the position and Update the Position Palette there and then which of course will be then correct for the subsequent mover cues required at that position (Palettes are referenced not copied into the cue). When you have the movers there, you can of couse then tweak the intensity in the cue and set colour/gobo etc and Update the cue - but at least you have a starter-for-10 in place. Of course if you happen to forget at the initial programming, then just add it in at the second rehearsal, you're no worse off. I'm assuming at your first plotting rehearsal, you will have "more" time and be under less pressure so can take your time and set some groundwork in place. Then at the second rehearsal when you're getting evil stares, you minimise how many changes you need to do to integrate your movers into your show. Adding an Effect (movement etc) will always be more of a challenge, and probably will be a time consumer on the second rehearsal, but the more general use of the movers as specials or highlights can probably be done to a reasonable extent before you actually rig them. Get those Palettes drafted in would be a wise move. On Fat Frog I was a disaster in Partial mode, however on FLX I just use the tracking mode. and with Update and SmartTag (care as above) I have few problems these days. One thing to learn beforehand (and I've posted lots on this and Edward has explained), is how to properly remove from a cue a fixture you accidentally recorded in. I think this is better in later ZerOS (late 7.9.x) as I used to have real problems with this, but these days I can (generally!) get it to work! However don't ask me to explain now, I'd need to look it up again!!! Hope that helps. Sorry I've waffled on a bit, but hopefully some of those ideas will help out! Good Luck! Kevin

Shift+Encoder wheel might be what you want?