Leaderboard

Bonjour Edward. Merci beaucoup pour votre reponse.

Hello, Based on the information on that webpage, that touchscreen should be compatible with FLX. Please let us know if you have any questions.

Thanks for highlighting, it’s now been removed 👍

Hi. Yes, use SHIFT+COPY for a MOVE. See this page in the manual ("MOVING CUES IN A PLAYBACK"): https://www.zero88.com/manuals/zeros/cues-playbacks/moving

Yes of course - if there is a particular cue you'd like me to look at in a show file, just email it to me and I can take a look.

Great question. This is a complex subject, so apologies if my explanations don't help! If you update a cue by simply changing values, you have to think about how the fixtures are going to get to those values, and how the fixtures are going to get from those values to the values in the next cue. However this is where SmartTag is your friend - if you set a fixture to 0 and update a cue, but the fixture was already at 0 in the previous cue, this operation essentially IS an Update > Remove. This is because SmartTag does not include an instruction for a light, if the light is already doing that thing in the previous cue. So if it was @ 0 already, there's no need to tell it to be @ 0 again. Intensity data is therefore removed - tick. SmartTag also strips out attribute data for the fixture if it is @ 0, hence this operation means all data is removed for the fixture in this cue. However, this then becomes a question of tracking. If you did this update as Cue Only, the next cue will now have data added in, to tell the fixtures to be in the same values, as if the previous cue had never been updated. So in this scenario, an UPDATE > SmartTag > Track Forwards would have been required. If you use UPDATE > Remove, your cue will have absolutely no instructions for the tagged parameters. The parameters can therefore continue doing what they were already doing, OR Move On Dark can grab that fixture in order to prepare it. This therefore could be a good option if the fixtures were on in the previous cue, and you want them to remain on in this cue with no change. So the choice as to whether to simply update the values stored in a cue, or remove them completely, really needs to be made on a case by case basis, thinking about how this could effect cue transitions. When programming quickly during plotting or even technical rehearsal, it may make sense to do a "quick and dirty" update, to just change the values rather than remove the values. Then, run through your cues prior to the dress. If there are any weird transitions, or Move On Dark isn't working as expected, you can then go into the troublesome cue, select fixtures > HOME > UPDATE > Track Forwards > Remove > ENTER if necessary to tidy things up. I hope this makes sense. Let me know if you have any questions.

Far and away my biggest want is Mac Phantom zerOS. My Apple silicon Mac runs Capture at 100+ fps without the fan even turning on! Phantom is pretty stable under Parallels 19 running side-by-side on the same monitor with Capture, but there are some glitchy bits that I assume are due to the emulation.

Hi Edward, thank you, very much appreciated. Rob

Hi, the possibility of having a customizable multi desktop as happens for example with Orb is very important, I hope that it will be taken into consideration in the next updates. Thank you P.

I think you'll find cue 1 has always had a zero time but you've never noticed it. The manual says... Cue 1, will always have a 0 second fade up and fade down time for intensity. This is to ensure that the intensity follows the level of the playback fader. Check here for more information. (Incidentally, when @Edward Z88 checks the forum he'll likely move your post to the FLX S thread.)

Triggering on the release of GO was a deliberate change several years ago - it allows for the “GoTo” command to jump to a specific cue

Thanks Kevin. We've updated the discontinued FLX page to say "Full size" and to link to the two current FLX S consoles. Agreed. Whilst I stand by our choice of name for "FLX S" (we wanted to build a family), what wasn't so wise in hindsight was not foreseeing a family of consoles back when the full sized FLX launched - we should have added a suffix to the end of the full sized FLX. We now have a much more robust naming scheme for whatever the future may bring ("FLX" or "Neo" for the family, "S" and "X" for the generation/platform, and "24", "48", "5", "15" or "Server" for the variant). I think it's perfectly clear that "Leap Frog" and "Leapfrog 48" were COMPLETELY different desks, but "Leapfrog 48" and "Solution" were identical. Don't know what you're talking about 😇

Thanks Kevin - your reply is really clear, so not much more I can add really. Your time is much appreciated on this. This is a fair comment - customers will occasionally say they have a "FLX", when they mean "FLX S24", so we just have to be mindful to not then tell them how to do something via syntax strings!

On this occasion I think I’ll be lazy and leave it where it is. This conversation is useful for FLX S and FLX users alike.