-
Posts
3,288 -
Joined
-
Last visited
-
Days Won
83
Posts posted by Edward Z88
-
-
Hi Kevin,
1 minute ago, kgallen said:I got this tonight when I turned on the desk for the Dress Rehearsal. Frightened the life out of me! What does it mean?
In ZerOS 7.11, behind the scenes colour filters are now essentially a new palette type that cannot be edited.
It looks like ZerOS doesn't like the fact the listed filters are greater than 240, which is the usual palette limit for FLX. However, this is not something we have come across before, and I'm not sure why ZerOS has listed these particular filters - I am guessing you have used these filters in your show?
I have logged this as ZOS-10961, and will investigate what may have caused this.
You should be able to tap OK, and use your console normally.
Edward
-
2 hours ago, kgallen said:
Thanks Edward! As an extra ask it would be useful if it showed the last ‘n’ previous cues at the bottom where n is fixed to your choosing but at least 1, ideally 2 say. At the moment if you move around the cue stack, the current (green) can be on the bottom line - say this is cue ‘m’, but the lines above are not ‘m-1’ and ‘m-2’ etc so when you scroll with the arrow keys the cue list jumps about.
Interesting thoughts - thanks very much for sharing.
Edward
-
8 minutes ago, kgallen said:
As discussed elsewhere the cue stack behaviour is really annoying when programming. Any chance we could have a Setup option to stop it keep jumping back to Cue 1 when working at the end of the cue stack? We could use this during programming but turn it off during shows where looping back to cue 1 is useful.
I have logged these comments as reference number ZOS-8694, and raised the priority of this issue.
Edward
-
Hi Kevin,
1 hour ago, kgallen said:I copied the same Q16 to Q43 for the "whole stage" state. I found that Q43 contained lots of "blocked" values, shown in white in the Output Window.
I didn't like this (I wanted Q43 to track from Q42), so I deleted Q43, copied Q42 to Q43 then went back to Q16 and wrote down all of the FOH values and then added them back in to Q43.
Clearly this is the wrong way to do this!
What would be the right way - or a better way? Did I miss something on the Copy window that would have tracked rather than blocked the pasted cue? The desk is in tracking on, and Smart Tag would have been on (as I never turned it off during a Record or Update).
If a cue includes recorded values for a fixture, these recorded values will always be pasted if the cue is copied. In your scenario, you therefore end up with cue 43 mostly being a block cue, as it is almost identical to cue 42. Most of the lights in cue 43 are told to do something they're already doing, hence they are displayed in white in the Output window. This is normal behaviour.
If you would like to unblock cue 43, go into the cue, make no changes at all, tap UPDATE, ensure SmartTag is enabled, and then tap the Master Playback's button. SmartTag will look at your cue, and rip out all blocked values, allowing the fixtures to instead track from the previous cue.
1 hour ago, kgallen said:Reading the manual now, I can see I can Unblock the whole playback, but could I have just unblocked Q43 so it tracked from Q42? Whilst I didn't knowingly have any blocked values in the rest of my show, I wasn't fully sure, so did not want to trigger an Unblock on the entire (master) playback.
I have specifically added information on how SmartTag can be used to unblock cues here...
https://zero88.com/manuals/zeros/cues-playbacks/record-options/snapshot-smarttag#unblock
I hope this helps. If you have any questions let me know.
Edward
-
Hi @Zulu
31 minutes ago, Zulu said:Question: Can I do this as normal "update" in the Master Playback Cue, or it it linked somehow to the playback the cue was created from? Or any other Master Playback cue that uses the non-master playback? (I'm looking to reduce, not increase, certain levels)
If you output a cue from a playback, and then record this as a new cue in a different playback, the newly recorded cue does not reference the original cue.
Therefore, if you want to update one of the cues in the Master Playback, you can update it in the same way as any cue. To do this, output the cue you wish to edit, with no other playbacks active. Then use the channel faders/fixture controls to make your changes, tap UPDATE, and then tap your Master Playback's GO button.
The cue will then be updated, and will therefore be different to the cue you originally used to create the lighting state. The original cue is left unaffected.
Hope this helps.
Edward
-
Hi @Uriahdemon
On 5/14/2022 at 9:52 PM, Uriahdemon said:So got a hold of some Servisol Super 10 and it seems to have resolved the problems and fingers crossed. The faders do seem a bit sticky but hopefully that will resolve itself. I also took the time to remove the rear of the desk and change the internal battery, again fingers crossed and all good. Thanks very much for the help from everyone, really very much appreciated indeed !!
Pleased to hear the switch cleaner seemed to do the trick. Let us know if there's anything else we can help with.
Edward
-
Hi @drscoop
39 minutes ago, drscoop said:For Capture, I was referring to what I think is the IP address Capture "listens" to for output from PhantomOS. I think we're talking about the same thing with different terms...
Ah I see, thanks for clarifying. Yes - the connectivity options allow you to force Capture to listen for a protocol on a particular network interface of your PC.
39 minutes ago, drscoop said:The good news is, using the localhost Loopback IP, I now have control of my showfile using Phantom ZerOS again...
Great, pleased to hear it. Let us know if there’s anything else we can help with.
Edward
-
Hi @drscoop
1 minute ago, drscoop said:Just to clarify, the desk and PC are on different IPs but the Capture "listen" IP and the desk "broadcast" IPs matched... my poor choice of phrasing.
3 minutes ago, drscoop said:but with Capture restricted to listen to the broadcast IP reported by the desk, I got no response.
Apologies - I'm not quite sure what you mean by this. What do you mean by the "Capture "listen" IP"? Feel free to attach a screen shot if that's easiest.
3 minutes ago, drscoop said:I'm also a little intrigued - as the desk can output sACN and ArtNet, and Capture can receive both of these, is it possible to connect the two systems using a protocol other than CITP?
Yes - you can use sACN or Art-Net, instead of using CITP to control Capture. If you use sACN or Art-Net, you will just be sending DMX data over the network. This means there will not be 2-way communication between ZerOS and Capture with these protocols, whereas when using CITP, ZerOS can receive feedback from Capture. Please see the video below for more information...
It is worth mentioning that to output sACN or Art-Net from Phantom ZerOS, you will need an unlock dongle. An unlock dongle is not however required to output CITP from Phantom ZerOS to control Capture.
Edward
-
Hi Brett,
I found this on another website...
https://d1aeri3ty3izns.cloudfront.net/media/14/143194/download_143194_1.pdf
Edward
-
Hi @drscoop
Hope you're well.
The guide below provides useful information with regards to potential IP addresses you may use...
https://zero88.com/manuals/zeros/networking/connecting-to-capture
13 hours ago, drscoop said:Capture IP and desk broadcast IP match
13 hours ago, drscoop said:matched IPs
To confirm, devices on a network cannot share the same IP address. Devices need to be on different IP addresses, but on the same subnet. See the link below for more information...
https://zero88.com/manuals/zeros/networking/ip-addressing
13 hours ago, drscoop said:It seems to be a Capture listening issue, I think. I've also tried starting at CITP Universe 0 or 1
Capture defaults to starting at CITP universe 0. Therefore please ensure your Desk Universes are routed on CITP universe 0 upwards.
If you are still not getting any response in Capture, in Capture click the "Windows" drop-down at the top, and choose "Universes..". Then click the "More" button, and from the drop-down click "Connectivity Options". In the window that opens, double click on the IP address field below CITP. You can then force Capture to "listen" on a specific network interface, by choosing the IP address of the network interface your console is connected to. You will then need to restart Capture.
I hope this helps. Let us know how you get on.
Edward
-
Hi @penlec
2 hours ago, penlec said:Anybody know where I can pick up this manual? The link at the top of the conversation is no longer correct.
A quick Google provides the following product page...
https://prolight.co.uk/product/firecracker-1500w-dmx-strobe
There is a manual available to download from the "Resources" tab.
The Zero 88 fixture file for this strobe can be downloaded from the link below...
Edward
-
Hi Simon,
Hope you're well.
22 hours ago, SimonH said:Is it possible to replace the MCB’s on the betspack 4 with rcbo so I can feed the rack with an mcb and any fault will trip just the faulty circuit rather than the entire rack?
21 hours ago, kgallen said:I doubt Zero88 would support this modification to their product
As per @kgallen's comments, this is not something that we can support. The only channel protection options for Betapack 4s are MCBs.
You would need to look at Chilli Pro Bypass cabinets for RCBO protection per dimmed/hot channel.
Edward
-
Hi @Uriahdemon
I am very well thank you, hope you are too. Apologies for the delayed reply - as @Davidmk mentions, I was at ProLight + Sound last week.
On 4/25/2022 at 8:17 PM, Uriahdemon said:the problem has recurred again and it affected fandom faders i.e. I could be adjusting no fader however other random faders will increase in intensity from Zero.
Please boot the console into Test Mode as you did the last time you encountered issues with your faders. Please work each fader up and down, and make a note of any faders that don't respond correctly, or affect other faders.
Once you have determined the faulty faders, the next step would be to squirt a small amount of Servisol Super 10 switch contact cleaner into the fader tracks and work them up and down. If there is any dirt or grime in the fader, this should clear it, to allow the fader to register correctly. Please go sparingly with the switch cleaner – too much can cause irreparable damage to the fader. After doing this, you can then boot the console again, to see if this has improved the faders.
If cleaning the faders hasn’t helped, the faders will need to be replaced. Spare faders are available to purchase if you wish to carry out the repair yourself, or the faders can be replaced by one of our service centres.
I hope this information is useful. If you have any questions, please let us know.
Edward
-
1
-
-
Hi Holger,
7 minutes ago, Holger said:Cues 79-82 use the effects L3, L2, L4 and L1. (L2 is called blue but I changed it to test if the cue 80 really takes the effect - it worked.
Thank you for sharing your show file.
2 hours ago, Edward Z88 said:If you record a snapshot palette, it will be annotated ICBSPE, to indicate all parameters are included. However if there was no effect running at the point of recording the snapshot palette, the "E" information of the palette will be "No Effect", meaning no effect information will be displayed on the encoders.
Effect palettes 41 thru 48, do not include effect information. These snapshot palettes are static looks, with no effects running. As no effects are running, the Effect encoder wheels will remain blank.
To check whether a fixture's intensity is referencing a palette, select your fixtures, and then tap the "Z/Shift" key. The first encoder wheel will be the Intensity wheel. If the selected fixture's intensity is referencing a palette, you will see the palette code displayed above the encoder, with the percentage displayed in brackets.
For example, go into cue 79, and select fixture 1. "E43 (49)" is displayed, telling you this fixture is using the intensity information from effect palette 43.
The intensity wheel can be locked on the first encoder wheel if required, to save you having to tap the Z/Shift key to access it. To do this, tap SETUP -> Settings, and under Attributes enable "Always display intensity encoder".
Hope this helps.
Edward
-
Hi Holger,
If you're able to, please save a copy of your current show file to a USB drive, and then email this to us.
I will then be able to take a closer look at your Effect palettes.
Edward
-
Hi Holger,
Thank you for the screenshot.
15 minutes ago, Holger said:When I go to such a cue (with an effect) there is nothing over the encoder wheels - just black.
Even if I select fixtures (tap them), click on an effect: the intensities are set as stored by the effect, so the effect is working, but over the encoder wheeels nothing changes - just black.
I can see that Effect palettes 41 thru 48 are your snapshot palettes. Can you confirm that these palettes do include effect data for fixtures 1 thru 6?
If you record a snapshot palette, it will be annotated ICBSPE, to indicate all parameters are included. However if there was no effect running at the point of recording the snapshot palette, the "E" information of the palette will be "No Effect", meaning no effect information will be displayed on the encoders.
Edward
-
Hi Holger,
20 minutes ago, Holger said:And, this is how my Output Window looks like (attachment from Phantom). There are no tabs like source or intensity. Maybe only available with FLX (and not FLX S24)?
That is correct. Intensities, Source, Live, Preview and Blind buttons are not available on FLX S consoles.
9 minutes ago, Holger said:@Edward Z88 Thanks. But even if I go e.g. to cue 10 (green cue 10 in the master Playback list) I cannot find out if this is an effect or not?
To confirm whether there is an effect running, select your fixtures, and then tap the "Effect" tab at the top. If there is an effect running, you will see the Effect number displayed above the encoder wheels.
Hope this helps.
Edward
-
Hi Holger,
3 hours ago, Holger said:My question: Is there a way to find out if a cue is connected to an effect (which one?) or if it is just a "normal" cue?
On FLX S, there is no graphical information to tell you which cues use effects. You could however add this information to a Cue's name (for example by adding "[E]").
On the standard FLX console you could use Blind mode to look at your cues without outputting them, to see which ones use effects. Blind is not available on FLX S.
Edward
-
Hi Holger,
15 minutes ago, Holger said:Thanks, but there is only the information that there are different colors but not their meaning.
And - the link has a pdf which is mainly in English but some parts are in German....Please see the PDF attached...
Hope this helps.
Edward
-
Hi Holger,
Please see the link below for information on the Output window, including the different colour codes...
https://zero88.com/manuals/print?manual=zeros&type=section&content=output-window
Edward
-
Hi Holger,
1 minute ago, Holger said:@Edward Z88 BTW, your last link, https://zero88.com/manuals/zeros/networking/ip-addressing when I click on it I got the German manual https://zero88.com/storage/downloads/b4cc87f1-0290-4049-86c5-8a2e6212e0a0/FLX-&-FLX-S-Manual-German-01-2020.pdf - somehow difficult....
BTW another topic...
Apologies - due to your location, you were redirected to the German PDF.
See the link below for the English article I linked to...
https://zero88.com/manuals/print?manual=zeros&type=section&content=ip-addressing
Edward
-
Hi Holger,
4 minutes ago, Holger said:@Edward Z88 Thanks! I activated DHCP, now it works - here in the company. I have to test with the laptop which should be used, too.... In the evening or so....
Pleased to hear ZerOS Monitor can now reach your console correctly.
Let us know if you have any questions.
Edward
-
Hi Holger,
1 hour ago, Holger said:When I started or when I restart the ZerOS Monitor I always get an empty list and I have to type in the IP.
It sounds like your laptop and console may be on different subnets. You should only need to manually add a console's IP address if there is some form of routing on your network. If you are using a simple network, the console should therefore automatically be detected by ZerOS Monitor.
Please could you confirm the IP address, and Subnet Mask, of both your PC, and your console's Remote connection?
Please see the link below for more information on IP addresses...
https://zero88.com/manuals/zeros/networking/ip-addressing
41 minutes ago, iank99 said:Are you connecting your desk and PC via an ethernet switch or a direct cable?
If it's a direct cable then it will need to be a "crossover" cable but if it's a switch then it should take care of that for you. That the two units aren't acknowledging each other might suggest a cable/connection issue?
In almost all cases nowadays, you shouldn't need to worry about whether you're using a "straight" or "crossover" cable. Almost all modern equipment features Auto MDI-X, meaning the devices work out what cabling is being used.
Edward
-
Hi @Holger
11 minutes ago, Holger said:I installed and connected - it seems to be connected but I only get a black monitor...
Thank you for sharing a screenshot. Can you confirm that the ZerOS Monitor app on your PC has full access through your Windows Firewall?
Did the ZerOS Monitor app automatically detect your console, allowing you to click on the console to connect, or did you have to manually add the console's IP address into ZerOS Monitor?
If you close the ZerOS Monitor app and restart it, do you still only receive a black screen upon connecting to your console? If so please restart your PC, and let me know how you get on.
Edward
Unblocking a cue (after cue copy)
in FLX
Posted
No problem at all 👍
Edward