-
Posts
2,522 -
Joined
-
Last visited
-
Days Won
36
Everything posted by Jon Hole
-
As Edward says, so long as you're in Tracking mode, this should happen automatically as ZerOS executes "Move Fades" - ie, the only parameters that "move" (change) are the parameters that are recorded within that cue - so as long as those parameters aren't included within future cues, they'll be left alone doing whatever they were doing before - in your case, a 20 minutes fade. (Don't get confused with the word "move" - this is nothing to do with moving lights, and just describing that a "parameter" (could be intensity, colour, beam, position etc) is moving from one value to another). Therefore, if you're finding that in your next cue the fixture is snapping, you're either (a) not in tracking mode, or (b) have programmed that moving light into the following cues. You can use the "Remove" function within the Record Window to solve this - go into the "following cue", clear the programmer, select the moving light, press HOME (this is just a quick way of "tagging" all the parameters of that fixture), and then press RECORD {REMOVE} CUE x ENTER. Alternatively, as mentioned by Pete, you could store this on an additional Playback and either run it manually, or trigger it via a macro.
-
Hi Peter, In the Output Window, intensities shown in red are from the "Programmer". The easiest way to think of this, is it's where information goes before you record it somewhere. So if you push faders 1 - 6 up to 100%, this information goes into the "programmer". You may choose to then record this (so the information is transferred from the "programmer" to where you record it), or you may choose to clear the programmer, by pressing CLEAR twice (first press clears the selection, second press clears the programmer). If you pull those six faders back down to 0%, this new information goes into the programmer. The important thing to remember about the programmer is that the programmer always wins. So often, you may push up faders, record to a cue, pull down the faders, and then try and play back that cue. But pulling down the faders has added lots of 0%'s into the programmer, and the programmer always wins, so it appears like the cue hasn't worked. Press clear twice, clear the programmer, and now the cue works. Another thing to bare in mind if you're coming from a Frog console - don't lower the Playback Fader when recording cues. If you're recording cues into a Playback (the Master Playback for example), just keep the fader at full (100%). You may find out YouTube training videos helpful.
-
Hi, Hold SETUP and press the Playback's button. In this window, under "Fader Controls" you can choose "Colour". Now, as you fade up the Blue fader, instead of snapping from Red to Blue, or fading over a pre-defined length of time, it now fades from Red to Blue with the fader - if you stop moving the fader, the colour fade stops. For more information see here... https://zero88.com/manuals/zeros/cues-playbacks/playback-settings/general#fadercontrols If you want "colour mixing" on the faders (so when Red and Blue are up together you get Magenta), you can use this tool with a few other tricks to achieve that. Follow the instructions here: https://zero88.com/manuals/zeros/cues-playbacks/playing-back-cues/rgb-colour-mixing-on-playbacks However, I would generally suggest there are better ways of controlling colour in a live situation. Make sure you're familiar with Programmer Time which is a fantastic tool for live busking of colour (and any other parameters). For more information see here... https://zero88.com/manuals/zeros/z-key/z-encoders#programmertime
-
Hi Nico, There isn't a Mac version of Phantom ZerOS, no. Unofficially (and completely at your own risk) I have in the past had success using "WineBottler" to run Phantom ZerOS on my Mac. However, I haven't tried recently, and there's been a lot of changes to both ZerOS and macOS since I last tried, so I don't know how successfully, if at all, it would work.
-
(I opened this thread before you replied Kevin, but didn't actually get around to replying until after you commented, so hadn't seen what you had said!)
-
Hi Carpo, Please can you let us know exactly which fixture you are using? Many thanks, Jon
-
This is really easy - as long as you're in Tracking Mode, and haven't got "Smart Tag" or "Snap Shot" enabled, you just set the channel to the level you want, RECORD HOME {Max Value} and only that channel will be updated - all the other channels will be left as they were. This is what I meant when I said "based upon usual recording rules of tagging, snapshot etc"
-
Moving Fixtures onto Preset Faders in ZerOS 7.9.3
Jon Hole replied to TrippingZebra's topic in Solution & Solution XL
That's correct - any fixture could be placed anywhere without the fixture number changing, which could become very very confusing. -
Hi Edi, The idea makes sense. It could be expanded with "x THRU y ENTER ENTER" syntax too. I've logged this idea as ZOS-8510 Jon
-
Hi Edi, Just setup all the fixtures how you want them to be, and then press RECORD HOME. The home positions are stored per fixture, so when you press RECORD HOME, the current values for each individual fixture will be recorded (based upon usual recording rules of tagging, snapshot etc)
-
Kevin's correct, this changes what happens to active (triggered) Playbacks when you change page. The "per-playback" option is "Page Lock" which affects a Playback whether it's active or released.
-
Hi MANTOT, We'll have a fix for this very shortly - until then, be in landscape before connecting to the console and it'll connect in landscape correctly. Please can you provide a screenshot from the phone?
-
Hi Phillip, I'm assuming this has been solved as you haven't replied to Kevin's questions, but if not - please email support@zero88.com and we'll get it sorted straight away.
-
One secret now means we need to let you into a second one... (For future eavesdroppers - this is purely academic, this knowledge is NO use to how you program the console at all, and can be completely ignored if you're not familiar with Non-tracking mode). ZerOS showfiles are always stored as "tracked" values, even if you're in Non-tracking mode. This allows the showfile to be smaller, and for users to switch between Tracking and Non-Tracking mode whenever they want without things breaking. We just change how we read and interact with the data depending on the mode they're currently in.
-
Hi Rob, It's still on the deck, but not scheduled for the next release (which is concentrating on stability, performance and bug fixes).
-
This isn't an odd request at all. In fact, we've had 3 other requests for this (or at least, something very similar). I've added this thread to the issue collecting all these ideas - ZOS-2765
-
Hi Brian, We've experimented with the idea of a "default" showfile - a specific file you could easily load (but not quite so easily overwrite - perhaps requiring a code). This was initially for an internal purpose (for use during tradeshows to revert consoles back to a default state), however it could also be useful for situations like this. This would probably be listed under the "Source" dropdown - so you have the USB devices, and a "Default showfile" section. Thoughts?
-
Thanks for reminding me of that, Kevin...
-
I'd argue it's closer to this statement
-
Well, who knew this small project was going to take so long! But discoveries and lesson's we've learnt along the way have created some positive changes to our whole App lineup, across iOS and Android too. We'll shortly be ready to enter public Beta Testing of our Apple Watch app - if you'd like to be part of this, please email me with an email address that's accessible on the iPhone which your Apple Watch is paired to. Here's a sneak-peak:
-
Hi Jason, thanks for the feedback, sorry for my delay in replying! Hopefully it's a little clearer on the "official" FLX training videos - we'll keep an eye on this for any future videos we do. We no longer have all the original files, so we can't take the background music out, but we may be able to cut them together so we get rid of the loud bits at the beginning and the end! We're not, we've been having fun doing something completely different instead:
-
Hi Simon, There's no reason the Master Playback fader needs to be down to play one of the other Playbacks (the old "submasters" are now also called "playbacks" in the new software). When you use multiple Playbacks at the same time, the intensities will mix "Highest Takes Precedence" (HTP) and the attributes (Position, Colour, Beamshape) will mix "Latest Takes Precedence" (LTP). Jon