Davidmk

The order you start things in may be significant. My guess is desk first is best but it's by no means certain.

So, @saitekx830, you seem to be doing the right things. If I was in this position I'd probably run Netscan (other network scanners are available) from the PC running your cueing software to just check that it can see itself and the desk. I'd expect that to work if the remote app is working but you never know. I use wired connections and find it helpful to disable WiFi to make sure the software isn't trying to use the wrong network. I guess, if you are using WiFi, you could disable any wired connections. Next, I'd go to the desk and after (like you) checking the network connections, I'd go to event monitor and send a few OSC commands. I do find that the first couple after switch on don't appear on the monitor (fine from about the 4th command and continues fine as long as the connection remains up) Now there are three possibilities, if you commands are not appearing then there is something wrong with the connection between your software and the desk, if they are appearing but with errors then they are just plain wrong (format, invalid commands or something) and if they appear without errors but don't do anything then they are valid but the thing (cue, playback, whatever) they should fire doesn't exist. If that didn't solve it then I guess the next step is to consult your neighbourhood witch or sorcerer. 😀

@kgallen Yep, seen it but busy ATM. @saitekx830 Settings both ends look good will give it some thought later.

I took "forum admins" to mean they sort out the forum when it dies and deal with inappropriate posts. So, yes, my assumption has been that the prompt and helpful days of Edward and Jon are over and we are, as you say, "on our own". I, for one, would be delighted to have this cynical and depressing assumption proved wrong. The newish thread - 16 bit intensity really 8 bit - is one that seems to require their attention (even though you have tried to help).

Absolutely! Also, don't forget, selection sequence matters when creating groups. Mostly for effects but for applying a spread of colours. So you may need more than one group for the same fixtures (eg start in the middle and work out 1,5,4,2,3 and the reverse 3,2,4,5,1) (Yes, I know an effect can be reversed, it's only an example 😀 )

Never tried it but you can save intensity in groups. Whether you can in pallettes I don't know, my guess is yes. Look up recording pallettes and be careful of SmartTag.

Not sure if they are available or how they work on Solution but pallettes should be your friend here. Plenty of documentation about them but look out multi-parameter (looks) pallettes. Rebuild your show from scratch using pallettes and, from then on, tweak pallettes not cues. Will require some planning but should simplify things in future.

My sentiments exactly. Keith, Edward and now you. My disappointment knows no bounds.

@kgallen Interesting video @epiclight sorry, forgot you can't use syntax (without a keyboard) on S desks. What I didn't see in the video is a way to put the same colour spread across each of the fixtures. To clarify. Say I have a number of linear fixtures, rigged horizontally but in a vertical column (one above the other rather than end to end) and I want a colour spread from red in the first pixel of every one of them to blue in the last pixel of each. How do you do that?

I'm guessing here but are you selecting them as whole fixtures (fixture no)not as heads (fixture no.1 thru fixture no.n). If so then all the heads get whatever the fixture does. You need to select the heads as described.

@Charlie Newman It's what I do with OSC. You use less PBs, you get the option to cross fade rather than snap and you don't build up a stack of active PBs.

Looking at the view of PB25 he's triggering cues within PBs. That edit window refers to the button which has triggered cue 25/3 (cue 3 in PB25). I'm more interested in the edit window itself, this doesn't look like touch OSC so, what are you using @Tomas Pokorny?

@Stan Vigurs I don't think a chase's speed can be controlled from a fader, you can set the speed to Tap Tempo and use the PB button to control it or (as @kgallen alludes) Global Tap Tempo and use an MFK or another playback's button. Speed Override simply changes the speed of a running cues transition. These options would allow the rate of speed to be varied manually but it would depend on the skill of the operator. To get something repeatable (that will always run with the same timings) I think you would have to program lots of identical cues each with an Auto After trigger and a different time on each (nightmare, especially bad as you'd need different sequences for speed up and slow down). Perhaps something clever could be done with macros @Jon Hole could advise?

@LLuk When you trigger a PB from a cue it uses the cues timings not the PB's so you still need the extra cues to get the different times. The don't have to have any fixture information just the timings and the trigger. See manual here and here. @kgallen for courtesy

@kgallen Looks good to me but don't forget auto-with can have a delay time as well (see manual here) which let's you start one cue off with, say 10s fade, and another lot 5s later with a 5s fade and have them all finish together. (Posted for completeness, not necessarily for @LLuk's specific needs.)

@kgallen If that link is his fixture then you are going to have your hands full with that. Sparx7_Manual.pdf

Is this https://saleswl.com/product/jb-lighting-sparx-7/ Your fixture?

I think the issue is that DMX values can run to a lot more digits than percentages. Allowing for all those digits in the screen layout would require less information visible and/or smaller fonts. Also if it was displaying 128 (for example) how would you know if that was 128 (50%) out of 255 or out of 65536 (20%). There is method in this particular bit of madness. The wheels show the DMX value by default. I have a feeling you can change that to % but I suspect most people change it back pretty quickly.

You're welcome. The acid test is "Does the fixture perform as expected?".

@kgallen @Charlie Newman Hmm. A DMX value of 5 (out of 255) is pretty much 2 and I think the fixture profile works in DMX value while the display works in %. If in doubt check the manual and/or the DMX output window.

I work in the same venue most of the time with the same patch for years at a time and a have a showfile for it with everything I need to busk. I just add a few bits for each show and yet this would still be so useful to me. The same acts come year after year but I can't reuse the showfile from the last time they were there because my "standard" set up evolves with time but being able to extract a few playbacks and MFKs from the last time and add them to my standard set up would be good. I also have my own rig, again with a standard setup, which Includes every fixture I own even though I don't use all of them at every gig and it is frustrating not to be able to copy in things from previous gigs with similar fixture positions. Now, I can see why there is no facility to do partial loads when the the channels are different would give rise to some unexpected results and if the channels referred to different makes/models of fixtures the results could be particularly "interesting". There'd be a few support calls from that I expect. While I'd like so see partial loads they'd probably need a health warning ("The results of this load could be spectacularly confusing. Are you sure?") What might be useful instead is the ability to load CSV showfilles. You can already save CSV files, these could be manipulated and combined in a spreadsheet, saved as CSV and then loaded to a desk. They might not work, of course, but you'd know what you'd done and the effort of doing it would mean only those with a real interest would be attempting it. It would have to be an unsupported feature but I'd be willing to give it a go. Another thing that would be handy would be a subtle change to groups making them more like pallettes so you could record a cue with a fixture group, change the fixtures in the group and the desk would apply the relevant parameters to all the fixtures in the group. Obviously things like a colour wheel parameter couldn't apply to an RGB fixture and again it might need a health warning but it would get you a better starting point. We can't hope for cues/playbacks/MFKs/pallettes to 'just work" when different fixtures are involved but getting them into the showfile would be a better starting point even if you had to step through them making corrections. What do you think @Jon Hole is there a remote possibility of helping us out here?

As @kgallen says, you will only get green if green is a component of the incoming or outgoing colour. Green is a component of white so, if you have a default of white and fade from nothing set by you to magenta you will see it. The default default is the Home colour which is, pretty much always, white (given what Home is for). I suspect the reason for this is the lack of an obvious and consistent, alternative. IMHO it should be black and I always change it to that. You can change it, it does work. Select all your colour mixing fixtures, set them all to R=G=B=0, and (on FLX) press Record (not Update), press Home and select Default on the screen. Mixing between colours works fine in a cue stack, it's only as good as you are when done manually. Either way you can get unwanted intermediate colours. Yellow to Magenta will go via a mucky White for example when the incoming Blue and Red matches the outgoing Green. and Red. In a cue stack you could fade Yellow to Red with a follow on cue going from Red to Magenta but that would be inconvenient to do manually. If you want total control of the change from one colour to another then RGB mixing on faders is probably the way to go. Really thinking about it... Fader controlling intensity and colour R=255 G=B=0, default colour R=G=B=255, trigger level 5%, fixtures not currently controlled by anything else. Fader @4% (below trigger level) gives I=10, R=10, G=B=10 (dim White) Fader @10% gives I=25, R=25, G & B are more complicated, they are reduced by 10% because you are 10% through a change from 255 to 0 but they are at 10% of that so G=B=23 that's 255 minus 10% all @10%. Sort of a dim, pale red? Fader @50% I=127, R=127, G=B=(255-(255x50%))x50%=127 (brighter pale Red) Fader @90% I=230, R=230, G=B=(255-(255x90%))=23 (bright, almost Red) Fader @100% I=255, R=255, G=B=0 With a starting colour of black, G=B=0 throughout. With a Magenta fader a.ready @100% B as above, G=0 throughout. Edit: On reflection, I'm not sure I've got the sums right above. Nevertheless the outcome is similar.

Colours will fade if... There is a colour fade time on the cue or Fader actions include colour Otherwise they should snap. You will see the previous (or default) colour when you first move the fader off zero if the trigger level is higher than the intensity level that actually produces visible light or the intensity is already at or above the visible level on another sub. Most of us buskers do not want colours to snap so the knowledge is mostly about how to avoid it. We are pointing you to the things we use to get fades and telling you to turn them off. You are also getting advice from FLX users, not Leapfrog and it's just possible ZerOS has Leapfrog specific quirks we don't know about. You could try clearing the desk and starting a new show file from scratch if you've been messing with it for a while as you might have something lurking from a previous experiment.

Last shot then. Separate intensity from colour. Use either the channel faders or a sub master with only intensity recorded on it and then one or more faders without intensity for colour. If you are using colour mixing then follow the instructions for that exactly. If you are using one sub per colour or subs with colour cues then set defaults to black (which you should only see with no subs up). Remove colour from fader actions so that the last will always take precedence and make sure the colour faders release on lower. Putting up an orange sub followed by a magenta one should result in full strength magenta as soon as that fader moves past 5% and back to orange as soon as it is lowered.

Another thing you could check out is the playback settings. (Here in the manual.) On the general tab, see if the fader action includes colour, try removing it (this is the default on FLX but maybe not on yours) and also look at the trigger level on the raise & lower tab and try setting it to 0% or 1%