Davidmk

I've got "form" for crashing FLX across more than one version of ZerOS. Not been able to find a way to force it to crash and neither have support so my ticket (ZOS-12410) is still outstanding. I updated one of my desks to v8 a few weeks back to create a new showfile for a venue I've started working at but had a crash on that so I took the desk back and started again. My crashes have all seemed to relate to the desk being busy with lots going on (effects and a chase running plus playbacks being flashed and lots of OSC messages). Buffer overruns and processor overloads have, apparently, been ruled out by support. That said, I've also had crashes where the desk was in a static state for a long time (hours). I have two desks, both seem to be affected. The fact that your issue seems to be repeatable gives some hope that it will give support more to go on. Fingers crossed 🤞.

@Veit0r Agree so much with @kgallen. They are great desks and make so much possible. The logic is biased towards programming shows and running them on the button but you can turn all that off and take control yourself if you want to. Enjoy your journey of discovery and come back to this forum if you need help.

I don't think I can actually help here - beyond asking dumb questions on the off chance you haven't already asked yourself them. So it's the actual default value, as in showing 69% yellow in the outputs window, the channel fader showing zero in the faders window (in channel mode), the UDKs released in the fader window (in playback mode)? What about in source mode - does the channel show D? Given how difficult it can be to set defaults (and get them to stick) deliberately, its hard to believe they got set accidentally (although a macro could do it). Is it, perhaps, down to dodgy faders - have you done a test mode start up? Then again, they didn't get parked somewhere along the line (red background)? (I did say dumb questions.)

Smart tag... Great at what it's meant for (recording cues in a stack for playback "on the button") confusing and a nuisance under other circumstances, especially for setting up a desk for busking (IMHO). Tracking similar. Default values, again great at making sure something happens when you raise intensity but default colour of white seems to throw a lot of people. Personally, I set R=G=B=0 as default for all RGB fixtures as a matter of course (and then get confused when I raise intensity and get full on black before remembering that was what I asked for 😁). Whilst having a mini rant... social media may not be the best place to look for help @kgallen and I and a few others watch this forum regularly and there's a lot of expertise here.

Default to white issue, done to death in this thread.

So true.

You're welcome. Just pleased I was close enough to help. Sorry about the link - I had it on the screen in Chrome and copied it in, no idea why that didn't work. It's always easier to find stuff in the manual if you already have some idea of how to do it. 😁

On the assumption assumption that you are running ZerOS and the process is similar to ZerOS on FLX... On FLX, after pressing Record you press position again then, in the record options window, you turn off SmartTag, tap/click the Beam button until the stripe is green then you tap/click the pallette you are recording to. The pallette should have the letters B and P on it after recording. The process is described under Advanced Pallettes in the manual. Apologies if this is no help - I've only used FLX, never had the pleasure of an Orb.

Save the show as .CSV. open this in a spreadsheet. The top row is a map of all fixtures and their parameter channels. You may have to put at least one cue on the master PB and it may need to include a cue that references every fixture. I can't remember. I also can't remember if channel numbers or addresses are included. I've only used it to check cues and parameter values.

@kgallen I don't have much experience with multi pixel fixtures but would this work? Select each pixel that should.come on together and record a group. Repeat until all the required pixels are in a group. Select the groups not the pixels. Run the effect by groups rather individually. Failing that... If the effect can work on a single fixture then giving them the same address will make them behave the same but rule out treating them individually. Heaven knows what it would do to RDM though. You can patch multiple fixtures, on different addresses to the same channel. Again that stops you treating them separately in this show but they can still be patched separately in another show Or build an actual chase recording each step separately.

@Nin First off, try test mode - see manual here. If your faders are playing up then maybe servisol will sort it otherwise contact support.

@Phil Mckerracher @kgallen So, after testing this on both v7.14 and v8 I have shown that... You don't seem to be able to alter defaults on a Solution showfile - even when it is loaded on an FLX running the FLX-only v8 and been saved on that and reloaded. This seems so wrong that I fear it may be me and the way I am doing it. If it isn't then it probably warrants a call to support. You can achieve default colour black by making amended copies of fixture personalities. Fixtures with a default of white behave exactly as I would expect (i.e. the reverse of what you and I would like). They start with white and, as the playback is raised, they fade out the colours that are not needed. Fixtures with a default of black, on the other hand do what I expected and would like and also what I suspect you need. These start at black and fade up the colours needed. Where another playback is already up the (default white) fixtures, the behaviour of the both black- and white-default fixtures is to raise the "missing" colours and the lower the "unwanted" ones effectively replacing the original PB's colour with the new one. T would seem to be the required behaviour but contrasts with faders set up for colour mixing. If you want to mix playbacks then you should refer to the instructions for this in the manual. My recommendation for you achieve the look you require is to set a default of black fr LEDs in your showfile. While this does not seem to be possible through changing the fixture defaults you can do it by creating modified fixture personality files and replacing the library ones in the patch. However there is another way - one which use all the time. On an FLX I use a multi-function key (latched and with release disabled). I save all the default values I need for a show onto this. Not just default colour black but things like stair edge lights at 50% and default positions for moving heads. I engage this when I start the desk up and record the "default" values I need for that day's show on to it. These values would, of course, be restored whenever that show file is loaded. As you do not have MFKs you could use instead. You might find it helpful to disable raise-on-lower on this PB. Be careful about recording HTP levels on this as they will become the minimum level for those fixtures and you will not be able to go below it. For our stair lights this is, of course, exactly the behaviour I require. Hopefully, this, and the various bits I have sent you by DM wi help you to achieve the reults you require. Have fn!

@Phil Mckerracher I loaded v7.14.4 on my spare desk and added your show file So, like you, I couldn't seem to set the default to be black instead of white. I also had some trouble with the fixtures on 13ch mode. I tried making a custom personality file with zero as the default for all the colours and they all defaulted to zero but red was stuck on 255. For my next attempt, I started with an empty show file and a new, 12ch personality and then added one fixture using the custom personality and another using the library one. This gave me problems and I was able to set up some playbacks that are similar to yours. I did some tests while recording the screen output. Unfortunately the resulting mp4 file is too big to attach here but results were as follows... The custom personality starts from black and the colours fade up with the fader. The standard personality starts from white and fades out the unwanted colours leaving the The fun starts if another PB is up. Taking yellow up and add blue as an example with just yellow, red and green are full and blue is out on both channels but, when blue is raised, the channel one goes to red, green AND blue full but the standard personality fades out red and green while doing nothing with blue - it's not until the yellow is faded out that blue goes to full. EDIT: Messaged you with a link to some files.

Thanks. No promises as to time scales but I'll try to make a start over the weekend.

@Phil Mckerracher Can you post your show file or DM it to me? I'm kind of busy this week pre-programming a show for Friday but as soon as I get a chance I'll load it up on my real FLX and have a play.