kgallen

"Launched in the next month or two" said Jon. Ah, we're back to the old project plan 🤣 So there's time there to sneak in some other stuff to keep the rest of us quiet while he deals with the new requests from the Signify suits upstairs. And anyway we've 7.11 to play with for a while - Jon cunningly slipped that one out in double-quick time to keep us occupied whilst he was tinkering on the 7.12 stuff! 😝👍

Does that mean if we voted for that option we get a substitute vote to allocate to one of the remaining options?

Thanks Edward! The key for me is the sound source is designed to be controlled/triggered (like a dimmer or luminaire) whereas the lighting desk (FLX) is designed to be a controllER. So being able to generate control actions from the FLX (by outputting MIDI rather than just receiving MIDI) makes network topology sense to me. FLX doesn’t have any other ‘auxiliary’ control outputs.

I have this underlying requirement too (or maybe I like tinkering!) where I would like to trigger my sound cues from lighting cues. At the moment I too press Go on my FLX and Play on one of my Sony MDS-E12 minidisc decks. My solution is to build a DMX interface to ‘contact closure’ (or possibly RS232 commands if I want to get fancy), but it would be nice to take MIDI from the FLX instead 🙂 Need to tick the appropriate box in the ‘new features’ list for FLX in the General Discussion section!

Which I prefer since a "magic sheet" set up on the internal screen is organised the same on the external screen. For the few ZerOS versions where the Groups pane was double width, it was a real "pane" (sic.)...

There is no comparison to FLX-S. Maybe you need to play with the desk a bit more and adapt your programming style from fader-per-channel mindset to using for example the colour palettes and mood boards, groups and layered playbacks? Good luck! Yes I'm still learning too!

https://www.zero88.com/manuals/zeros/cues-playbacks/playing-back-cues/rgb-colour-mixing-on-playbacks Make sure you follow the instructions exactly. If you accidentally adjust something you didn't mean to then that parameter will get "tagged" and what you record to the playback won't be what you intend and won't work properly for what you require. If you mess up the sequence, easiest to delete the playback and start again.

I agree. I’ve been asking about this for some years. I have the same frustration when programming a sequential (theatre) stack.

Ditto, no networking on mine either. My FLX is only ever attached to a USB keyboard and mouse, touchscreen monitor (USB+DVI-D) and lighting network via DMX outputs. And a USB stick and desk light.

I have certainly had my (full size) FLX freeze both in a show and after having sat idle for a while. This was on earlier ZOS versions (and all were reported here). I don’t have enough hours experience in the last couple of years and ZOS versions to know if this is still the situation. I had concerns at the time that there was an underlying hardware issue (signal timing or signal integrity), since my FLX is a very early build, but if this phenomena is also seen on the FLX S range then maybe the pendulum swings to more of a software problem than hardware.

Colour fade time in the cue is non zero. It defaults to 3 seconds.

Sounds like dimmer preheat slightly too high assuming it’s tungsten lamps you’re seeing? If LED, you can confirm on the DMX Output window (under the Z key) that the desk is outputting 0 on the intensity channels.

Basically Keith means you have too much information programmed into each of the two playbacks. i.e. you have fixture information recorded in Playback 21 that overrides something in Playback 22 and vise versa. It sounds like you have some fixture data recorded in each that does not show with that playback activated alone. My suggestion would be to delete both playbacks, clear the programmer (Clear-Clear) then set the fixtures for Playback 21 and record to 21, then Clear-Clear again, set the fixtures required then record Playback 22. In each case after the clear-clear you should only modify the attributes you want to record, so set the intensity and set the colour. Don't fiddle with anything else not required otherwise you will tag other attributes that will thus get recorded and your recording won't be "clean" which sounds like the issue you originally had. This is assuming you're using Smart Tag. If you are not then you can be more clinical by ensuring you only manually Tag the attributes you require in each Playback. Hope that makes sense. I think if you read Keith's reply a few times it will make some sense, but in order to repair the mal-formed Playbacks in this situtation, it's probably easier to delete them and start again.

That seems quite a high resistance for a cable. Also that the differential pair on pins 2 and 3 have very different resistances looks very suspicious. A thorough check of the cable and connectors/termination is needed.

Eric - battery on FLX : only for the real time clock I understand, not for show data.

This is a double post (maybe it wasn’t deliberate, but please don’t 😉).

It will by default if you’re using Smart Tag. The house lights question has come up on the forum a few times recently, I’m not sure it should be a big issue.

Adding the photo I wanted to add earlier now the Forum Gods have given me space to fill again 😆 Being able to add header comments/lines within the cue stack, like this ‘Act 1’ header seen on an ETC console: (that’s ‘all’ - you clever folk can argue the tracking thing! 🤣)

Being able to add header comments/lines within the cue stack, like this ‘Act 1’ header seen on an ETC console: (Jon - can I have some more ‘space’? Forum says I’ve used up all of my attachment space and to use Manage Attachments but when I try that from My Account it says Access Forbidden).

There is no power-down procedure. Just turn it off. FLX has an on/off switch at the back. FLX-S I think you have to unplug. You won't lose anything 😉

Probably an option like SMPTE.

I would like to, but the touch is too slow for anything except basic operations and it is not multi-touch. However it is 17" (43cm) screen which suits my work position. The capacitive screens available are much larger (22", 56cm) and such a screen is too large to fit my workspace. So for most touch operations I rely on the FLX internal touch screen. J'aimerais bien, mais le toucher est trop lent pour autre chose que les opérations de base et ce n'est pas multi-touch. Cependant c'est un écran de 17" (43cm) qui convient à ma position de travail. Les écrans capacitifs disponibles sont beaucoup plus grands (22", 56cm) et un tel écran est trop grand pour s'adapter à mon espace de travail. Donc, pour la plupart des opérations tactiles, je m'appuie sur l'écran tactile interne FLX. At the time of purchase I too did not understand the different screen types. Au moment de l'achat, je ne comprenais pas non plus les différents types d'écran.

Hi Delfine, I have the "original" Iiyama touch screen which is "resistive". It is also very slow on my FLX. Your screen is "optical" touch. It sounds like it is also very slow. A screen like an iPad is "capacitive". I think these are the fastest. Maybe you should consider a capacitive touch screen? J'ai l'écran tactile "d'origine" Iiyama qui est "résistif". Il est également très lent sur mon FLX. Votre écran est tactile "optique". On dirait que c'est aussi très lent. Un écran comme un iPad est « capacitif ». Je pense que ce sont les plus rapides. Peut-être devriez-vous envisager un écran tactile capacitif ? Regards, Kevin

Thanks Edward - I shouldn't be now as I've been re-watching some of your excellent training videos including the one discussing REMOVE. In my particular application, I was trying to remove a tagged beam parameter from a beam palette. I failed. Maybe this is something that the desk doesn't allow. However I think it was my inability... In the end I deleted the pair of palettes that I recorded incorrectly (actually I changed my mind on what beam parameters I wanted in the palette) and re-recorded them.

Yep, agreed. In my current case I have a number of different mover models from the same range from the same manufacturer and it seems colour and position are close enough when I’ve manually copied the parameter values.