Edward Z88
-
Posts
3,288 -
Joined
-
Last visited
-
Days Won
83
Posts posted by Edward Z88
-
-
1 hour ago, beyond the blue said:
One of the queues is a dim sequence over 12 minutes, one of the lights in the sequence needs to change colour as it dims , how do I program it to do this without ruining the rest of the lights in the sequence?
To do this, tap on the cue that has the 12 minute fade time in the Cues window, so that it goes yellow. Then hold Z/SHIFT and press the GO button, to snap into the cue. You should then see the fixtures in their recorded values that they get to when the fade time has completed. You can then select the light you need, and change its colour. Then tap UPDATE, and tap the playback's GO button.
Now, go into the previous cue, and press the GO button to run the cue. If the colour fade time needs tweaking, tap on the value in the cue's Colour column, and then tap the first encoder wheel's button, to open a number pad. You can then type in a colour fade time for the cue, and click OK.
I hope this helps.
-
Hi @Zebroid66
Thank you for the information.
20 hours ago, Zebroid66 said:By the way, in firmware ZerOS Version 7.13.2, I have a bug where the indicator for the fader page keeps flashing all the time.
This is an issue we are aware of on Solution consoles, caused by opening the "Panel" desktop. This issue will be fixed in the next ZerOS software update.
Please let us know if you have any questions.
-
Hi @Zebroid66
19 hours ago, Zebroid66 said:I found the problem, and it lies in my Wi-Fi signal transmitter.
Thank you for the update. Out of interest, what transmitter are you using? How have you solved the issue?
-
Hi @Zebroid66
Would you be able to attach a copy of your console’s show file, and confirm which type of fixture and how many of them you are attempting to patch?
-
Hi @Kauz
4 hours ago, Kauz said:
oops! I should have checked the latest software prior to asking the question. With the release of 7.14 you guys were 50 days ahead of my post. Thank you for resolving this issue and reminding me of the new release! After the upgrade I got the Go button operational again by means of switching the fader function back to "HTP master".
No problem at all.
4 hours ago, Kauz said:Is it now also possible to use the Go button while the fader is configured to "Manual Fade" mode?
No - this functionality is not possible. When in Manual Fade mode, the GO button is disabled, and the fader movement is the only way of activating the next cue.
4 hours ago, Kauz said:Sidenote: My use case is a multi user issue. If I would leave the console in "Manual Fade" mode after a show, less experienced colleagues will be confused because the Go button doesn't work. I am afraid I will have to write a checklist what to do before leaving the desk to "operators". Maybe I can assign at least some tasks to macro.
Have you experimented with the Speed Override control? This allows you to use the GO button to trigger cues, and a secondary fader to speed up or slow down the fade transitions. This also means you can lower the intensity output of the Master Playback using the Master Playback's fader, which is not possible when set to Manual Fade mode.
Please click the link below for more information...
https://www.zero88.com/manuals/zeros/cues-playbacks/special-playback-functions
Let us know if you have any questions.
-
Hi @Kauz
5 hours ago, Kauz said:it looks like I experienced the issue mentioned above just yesterday with a recent ZerOS version on our FLX.
It sounds like you may not be running the latest software on your FLX. The two issues below have been fixed in ZerOS 7.14:
5 hours ago, Kauz said:s mentioned above, there is no easy way to make the Go button work again. From my humble user perspective this feels like a bug. Moreover, I am surprised that there is a (theatre) console on the market which doesn't (at least) support switching between automatic and manual crossfade during a show.
The ability to change the playback Fader Function from "Manual Fade" back to "HTP Master" has been implemented, reference number ZOS-8363.
5 hours ago, Kauz said:ZOS-5803. Can you give a rough prediction when we might see this improvement in ZerOS?
On 10/16/2020 at 3:16 PM, Edward Z88 said:We are aware of this issue, where after manually releasing a Manual Fade playback it can no longer be triggered. This is logged on our software tracking system as reference number ZOS-5803.
ZOS-5803 has also been implemented. Both of these reference numbers can be found alongside the various other changes and improvements in the ZerOS 7.14 release notes...
I hope this helps.
-
9 minutes ago, kgallen said:
Edward, would you be prepared to add that to the "Manual Tagging" section of this page - or a cross-link or one of your "lightbulb" boxes to point to that if it's documented elsewhere in the manual?
Done - https://www.zero88.com/manuals/zeros/controlling-fixtures/tagging
-
1
-
-
On 8/27/2023 at 2:12 AM, Amy Worrall said:
For instance, can I un-tag a whole fixture in order to not record it when creating a cue?
20 minutes ago, kgallen said:Hi @Edward Z88
Could you answer this part of the original query. I'm pretty sure I'm wrong in my answer. I couldn't find anything in the manual, but I'm sure there must be something...
This part of my answer I'm pretty sure is wrong, or at least missing something:
On 8/27/2023 at 10:07 AM, kgallen said:To untag a whole fixture, select it then (I think) it's CLEAR+HOME (need to check the manual!). To untag a whole attribute it's CLEAR+COLOUR (for example)
Thanks, Kevin
You can clear a single fixture from the programmer, meaning it won't get recorded in cues when SmartTag is disabled. To do this, hold SETUP and tap an empty UDK. From the Normal dropdown, choose Clear Fixture, and click OK. Now, you can select fixtures, and tap the Clear Fixture UDK, and those fixtures will be completely removed from the programmer.
I cannot think of a reason why you would want to leave a whole fixture in the programmer but untagged. If you wanted to do this, you would have to hold CLEAR, and tap each attribute key, and then tap the Intensity wheel's encoder button to untag intensity too. Personally if I had fixtures in the programmer, but only wanted some of them to get recorded, I would select the fixtures first, and then tap RECORD > Selected Fixtures.
Hope this helps.
-
Hi @Amy Worrall
As usual, @kgallen & @Davidmk have done an excellent job of responding to your points. Do let us know if you have any outstanding questions.
Just to add a couple of extra comments on the points below...
On 8/27/2023 at 2:12 AM, Amy Worrall said:- I know that I should turn SmartTag off, and things that are manually tagged will get recorded. Does this just apply at a parameter level, or is it also a concept at a fixture level? For instance, can I un-tag a whole fixture in order to not record it when creating a cue?
On 8/28/2023 at 11:25 AM, Amy Worrall said:Essentially, because my mental model from Eos is all about being specific about what stuff to record into each thing (cue/palette/etc), which seems to map best to being in control of the tagging myself on ZerOS. On Eos, I'm used to it recording every manual change by default, unless I specify a specific list of channels/parameters. That seems to map to ZerOS tagging everything I change, unless I go back and untag things I don't want it to record.
You are correct - you will definitely want to work with SmartTag disabled, coming from Eos. With SmartTag disabled, you are forced to build the next cue from the last cue, which is a workflow you'll be more familiar with. Personally I always program cue stacks with SmartTag disabled.
On 8/27/2023 at 2:12 AM, Amy Worrall said:- Does ZerOS have the equivalent of by-type palettes? (i.e. I set the colour on one fixture into a by-type colour palette, and any others of the same brand, even if they're patched in the future, will get that colour.)
On 8/27/2023 at 10:50 AM, Davidmk said:So, I presume all ZerOS pallettes are "by-type".
Yep - all ZerOS palettes would be "by-type".
On 8/27/2023 at 2:12 AM, Amy Worrall said:- From the manual, I think I read that there's a way to e.g. store non-colour data in a colour palette, etc. I don't want to do that -- is it the sort of thing I might end up doing by accident?
Please see the link below for more information...
https://www.zero88.com/manuals/zeros/palettes/advanced-palettes
You'll see you'd be hard-pushed to do this by accident!
On 8/27/2023 at 2:12 AM, Amy Worrall said:- What's the easiest way to select a bunch of cues and adjust things like their fade time all at once?
On FLX, there isn't TIME syntax. Therefore, you will need to edit individual attribute timings for each cue. Note - if you tap on a fade time cell, you can hold SHIFT and tap the Up/Down arrow keys to increment/decrement by a second, which will speed things up, saving you having to type into each cell.
On 8/27/2023 at 2:12 AM, Amy Worrall said:- Is there an equivalent of copy-to/recall-from? Especially, is there an equivalent to how on Eos you can go into blind, select e.g. cues 1-20, then do channel 15 copy-to channel 18, and it'll apply that copy operation on all of those cues at once.
FLX does not feature fixture-copy. You therefore cannot say "Fixture 15 copy to fixture 18". If fixture 15 and fixture 18 are the same type, you could do this via a palette. Please see the link below...
https://www.zero88.com/manuals/zeros/palettes/advanced-palettes
If you have a USB keyboard connected, you can use @ CUE syntax. 2 @ 0/10 ENTER would set fixture 2 to the values it is at in cue 10 of the Master Playback.
I hope this helps. If you have any questions, please let us know.
-
Welcome to the Zero 88 Forum.
50 minutes ago, Jakob Klucke said:I am looking to make a fader (just like the master fader) just for certain groups and lights.
The ideal situation would be that I do a black out on my LED's , Washis and Moving Heads while the big normal stage lights are staying on.
To do this, you could record an Inhibit playback, to create a custom intensity master fader:
- First, set all of the fixtures that you would like to be controlled by your custom master fader to full.
- Then tap RECORD, and tap an empty playback's button.
- Hold SETUP, and tap the button of the playback you just recorded, to open the Playback's Settings.
- Under "Intensity Mixing" choose Inhibit, and click OK.
- Now, this playback fader will act as an intensity master control, just for the fixtures recorded to it.
Please see the link below for more information on Inhibit...
https://www.zero88.com/manuals/zeros/cues-playbacks/playback-settings/general#intensitymixing
Let us know if you have any questions.
-
Hi @DALX
1 hour ago, DALX said:I was curious if the DMX Input option allowed FLX S to act as a dmx merge. It is only working on individual channels at present so for fixture 1 which happens to have dimmer as channel 1, I can control intensity, but no colour change
ZerOS will not map the DMX Input universe to a DMX output and merge the console output. DMX Input is not designed to provide full remote control of fixtures patched in the console. DMX Input can be used to control individual fixture intensities, or playback levels. Please see the links below for more information...
- https://www.zero88.com/manuals/zeros/patching/fixture-schedule/dmx-in
- https://www.zero88.com/manuals/zeros/setup/triggers/dmx-in-2
1 hour ago, DALX said:Can DMX IN eventually be expanded so fixture 1 of one desk can control all attributes of fixture 1 on another desk ? I guess it have have to use the network port to allow handshaking to confirm that the fixtures are identical ?
There are currently no plans for this functionality. What would be the real-world scenario where this could be useful?
Let me know if you have any questions.
-
Hi @Harold
Welcome to the Zero 88 Forum.
12 hours ago, Harold said:Are files saved using Phantom 7.14 able to be loaded onto a board running 7.13.2?
No. ZerOS 7.14 includes a significant change to how colour mixing is processed internally, which means show files saved in ZerOS 7.14 cannot be loaded into earlier versions of ZerOS.
Where possible, we aim to make show files saved in the latest version compatible with the previous version, however in this instance it is not possible. We never guarantee that show files can be loaded into earlier versions of ZerOS. We do always guarantee show files from earlier software can be loaded into the latest version.
12 hours ago, Harold said:We're waiting for the IT person here to update the firmware (I have no choice, I have to wait) and I can't load files I've edited or built from my computer to the console.
The console's software will need to be updated. Software updates only take a couple of minutes to do and are straightforward. Once updated, you will be able to load in your show file without issue.
If you have any questions, please let us know.
-
1
-
-
52 minutes ago, SCE said:
Gonne update to 7.14 but I have this weekend a large show so doesn't like to do this right now.
Makes sense 👍
2 hours ago, SCE said:First I will do upgrade and if that not helps then I will send you a showfile.
OK great. If you would like to send over your show file first I would be happy to investigate.
2 hours ago, SCE said:Meanwhile any other thoughts, options or info is always welcome.
There's nothing obvious that comes to mind, so a show file would be helpful.
-
Hi @SCE
12 hours ago, SCE said:I cannot record any effects to a playback. I used smart tag on and off, Snapshot.
The effect (I select rainbow) is shown on my RGB spots, I press RECORD and select a empty playback, it is stored well, I clear the programmer.
Then move playback fader up and no effect is shown or running,If you would like ONLY the rainbow effect to be recorded, without intensity, you will need to ensure that SmartTag is disabled in the Record Options window. When SmartTag is enabled, the console will only record fixtures that are on.
If you can share your show file, I would be happy to take a look to see what may be preventing the effect from outputting. If you do share your show file, please detail the fixture numbers you are using, the effect you are applying, and the playback you are attempting to record to. I will then be able to investigate.
12 hours ago, SCE said:I running a Zero88 Solution desk on 7.9.9
As a side note, the latest software for Solution consoles is ZerOS 7.14. If you would like to update your console's software, please let me know, and I can share installation instructions.
-
Bonjour,
Heureux d'apprendre que vous êtes en mesure d'utiliser la console comme prévu.
FLX n'enregistrera JAMAIS automatiquement un cue en appuyant sur RECORD. Vous devez définir où vous voulez stocker l'état après avoir appuyé sur RECORD. Si la mémoire enregistrait automatiquement sur la lecture 1, cela suggère que le bouton de la lecture 1 était enfoncé ou que quelque chose appuyait sur les touches d'un clavier externe.
Hello,
Pleased to hear you are able to use the console as expected.
FLX will NEVER automatically record a cue upon pressing RECORD. You must define where you want to store the state to after pressing RECORD. If the cue was automatically recording to Playback 1, this suggests either playback 1's button was stuck down, or something was pressing down keys on an external keyboard.
-
1
-
-
16 hours ago, PJRichards said:
If for example in a festival situation you suddenly want to use a look you've not already used so you built it using pallets in the programmer - I am correct to think that it's not then possible to have for example a white strobe bump on a MFF which would successfully trigger more than once over the top of this - I'd have to quickly save a cue somewhere with the new look on it and load it in order for any other playback to bump over the top more than once.
The "White Strobe" playback would need both intensity information and colour information stored, to ensure that whatever the fixtures were doing, you would achieve an intensity strobe in white when played back. Therefore, if the colour of the fixtures is currently in the programmer, this playback would take that data out of the programmer when it is triggered.
So, you would either need to store your look to a palette (SHIFT-RECORD to include everything in a single palette), and apply this after using the strobe playback, or as you say, you would need to record the current state onto a fader, trigger it, and that way upon releasing your white strobe playback, the fixtures will go back to the state in the active playback.
Hope this helps.
-
40 minutes ago, PJRichards said:
Thanks Edward - Try pushing fader 7 up again and releasing after you've completed the above, so yellow is still on the command line, nothing cleared.
If you trigger playback 7 again, this then becomes the latest instruction for the fixtures, and so playback 7 takes control over the fixtures. If these fixtures were the only things in the programmer, and playback 7 has taken control of them, the programmer is emptied - you'll notice that the LED in the CLEAR button turns off, because playback 7 has taken control, and so there is nothing left in the programmer. Therefore, lowering the playback fader, results in the fixtures going back to default. This is where you could disable release on lower to prevent the fixtures going back to default.
-
Hi Mil,
18 minutes ago, lugamil said:In the example above, the timecoded approach obviously wouldn't work. I don't know what the DJ will do.
Correct - based on your original description I wasn't sure whether you were looking to sync to an audio track or live music.
19 minutes ago, lugamil said:Using OSC, is it possible to send a GO/NEXT signal to a fader which is set to global tap tempo to set the global tap tempo?
It is not possible to trigger a Global Tap Tempo playback over OSC.
It is possible to send a Playback Go x message, where x is the playback you wish to trigger. Each time this command is sent you would step through each cue on playback x.
If you sent these commands to a chase that was running, you would end up with a mixture of the chase automatically running using Tap Tempo, and jumping cues when OSC GO messages are received.
I hope this makes sense.
-
36 minutes ago, PJRichards said:
If 7, 16 or 17 are faded down / released then the fixtures return to default for that attribute.
These are the exact steps I'm following:
- Load show file
- Raise playback 13
-
ENTER ENTER (to select fixtures and see parameter table in the Output Window)
- The fixtures are in colour palette 12 (Blue) by default
- Raise playback 7 - the fixtures go Warm White as programmed
- Press playback 7's button - the fixtures go Red as programmed
- Apply colour palette 6 - the fixtures go Yellow as programmed
- Release playback 7, by either lowering its fader or hold CLEAR and tap playback 7's button - the fixtures remain in yellow, as colour palette 6 last changed the fixture's colour (LTP)
If I DON'T apply colour palette 6 in step 6 above, the fixtures DO go back to default as expected upon lowering playback 7 in step 7. This is because if a playback has control of fixtures, and that playback is released, the fixtures then go back to the values of the playback that previously had control of the fixtures. If no playbacks that have values for the fixtures are currently active, the fixtures go back to their defaults.
It is possible to prevent a playback from releasing when lowered, meaning it will remain in control of the fixtures until something else on the console takes control of the fixtures. To configure this, hold SETUP and tap the playback's button to open the playback's settings. Choose Raise & Lower from the top, set Release On Lower to disabled, and click OK.
Hope this helps.
-
Hi Mil,
51 minutes ago, lugamil said:I was wondering if it is possible to match a chase, cue or effect to music. I found some topics asking similar questions but most are years old and much has changed since.
FLX S consoles do not have Sound-to-Light functionality, so there is no way of automating a chase to follow the beat of an audio track.
When a chase is programmed on a playback, the playback's button automatically becomes a Tap Tempo, allowing you tap the playback's button to synchronise the chase to a beat.
52 minutes ago, lugamil said:With the last update however, OSC was introduced which I believe could make this possible with an external device.
I've never used OSC before. Would this be possible and how? Has anyone tried/done this?You could program a sequence of cues on a playback. Theoretically, you could then send repeated OSC GO messages to trigger the cues on this particular playback one after the other, essentially resulting in the cue stack on the playback behaving as a chase. To do this you would need to come up with a way of a software package taking an audio track, and then repeatedly sending a particular OSC message on each beat.
Alternatively, you could use more of a "timecoded" approach, where you start an audio track in a software package, and automatically at certain points in the track the software package sends OSC messages to FLX S, which then trigger certain cues at different points in the song.
Hope this helps,
-
Salut @jeansted
Bienvenue sur le forum Zéro 88.Pour voir les cues sur le Master Playback dans la fenêtre Cues, maintenez enfoncée la touche VIEW et appuyez sur le bouton GO du Master Playback.
J'espère que ça aide.
Welcome to the Zero 88 Forum.
To view the cues on the Master Playback in the Cues window, press and hold the VIEW key and tap the Master Playback's GO button.
I hope this helps.
-
1
-
-
Hi Mac,
3 hours ago, Uriahdemon said:Are the workflows for the Solution XL the same as those for the FLX given they are using the same software. Any good/bad points and given the desk is now a legacy product what is the lifetime expectancy for ongoing support on it please.
The core functionality and workflow of Solution XL consoles is similar to FLX, as they both run ZerOS. In many ways Solution consoles are more similar to FLX S than FLX - there is no syntax numpad, and you are limited on the number of fixtures you can patch. There are a handful of features introduced in recent versions of ZerOS, that have not come across to Solution consoles, due to Solution consoles featuring older processors. Solution consoles were discontinued in 2021, and so the warranty of the very last Solution consoles will be running out in early 2024.
If you have any questions, please let us know.
-
Hi @PJRichards
17 hours ago, PJRichards said:Could you possibly explain the priority levels for items on the command line when busking a show
Intensity values in the programmer have the highest priority on the console. The CLEAR key is required to remove high-priority intensity programmer values, to allow cues to playback as programmed.
All other attributes (Colour, Beam, Shape, Position) mix LTP, irrespective of whether they are being controlled manually or by a cue.
17 hours ago, PJRichards said:if you use a pallet for an attribute then whilst it initially works and you get the look wanted, if you happen to release an underlying playback which also had that attribute information on it then it seems to release the fixture back to default values for that attribute.
17 hours ago, PJRichards said:if I then release MFF2 the colour reverts back to the fixture default value
You shouldn't be seeing this behaviour. If you have fixtures in red on a playback, you select them and tap your blue palette, lower the playback fader so it releases - the fixtures should stay blue, because nothing has told the fixtures to change colour.
Therefore it sounds like there could be a setting in your show file that is affecting this behaviour. Please feel free to attach your show file, and detail which fixtures, playbacks and palettes you are using. We can then investigate further.
Please let us know if you have any questions.
-
On 8/11/2023 at 5:08 PM, discover said:
How can we lock parts of the FLX S Desk for simple users
e.g. disabling them to enter the programming mode?Just playing cues/playbacks etc would be sufficient.
FLX S consoles can be locked to prevent programming from being edited and prevent settings from being changed. Whilst locked, cues can continue to be played back.
On 8/11/2023 at 6:09 PM, Davidmk said:Check the manual here. I'm an FLX user but I think this applies to FLX S as well.
@Davidmk has helpfully linked to the relevant section of the manual that provides more detail.
If you have any questions, please let us know.
-
1
-
Colour fade
in FLX S24 & FLX S48
Posted
If the fixture is already in blue in the cue with the 12 minute fade, you’ll just just need to set the colour fade time of that cue to 12 minutes too. To set the colour time, tap the cue’s colour column, and then tap the first encoder wheel’s button. You can then type 12.00.00 into the numpad to achieve that.