[Effect continuing through the show NEWBIE]

Hi @Geoffc

Welcome to the forum.

50 minutes ago, Geoffc said:

I do not know enough about the console to play around and I am concerned with ruining the show set up even more.

Firstly, I'd recommend saving a copy of the console's current show file to a USB drive. That way, if you make any incorrect changes, you can then simply load in your previous show file from the USB drive. Please click the link below for information on saving show files...

https://www.zero88.com/manuals/zeros/setup/save

42 minutes ago, Geoffc said:

I added an effect into a cue ( cue 20 ) but after that all of the following cues have that effect 

The effect therefore needs to stop in cue 21. Please follow this process to stop the effect:

1. Go into cue 21, so that it is live and outputting (green row in the Cues window)
2. Double tap CLEAR
3. Select the fixtures running the effect. For example by using the buttons below the fixture's channel faders.
4. Tap the "Effect" tab at the top of the internal touchscreen, and choose [No Effect]. The effect should stop.
5. Then press-and-hold UPDATE, and you should see the Update Options appear on the internal touchscreen.
6. In the Update Options, ensure that the SmartTag button is disabled, indicated with a blue stripe. If it has a red stripe, tap it to disable.
   1. If you cannot see a SmartTag button in this window, please see this link for more information - https://www.zero88.com/manuals/zeros/cues-playbacks/record-options
7. Ensure that "Track Forwards" has a red stripe, rather than "Cue Only".
   1. With Track Forwards selected, you will send your "No Effect" instruction down through subsequent cues, therefore stopping the effect from running in those cues.
8. Tap your Master Playback's GO button to complete the process.
9. Then, press-and-hold RECORD, to open the Record Options on the internal touchscreen. Tap "SmartTag" and "Cue Only" again, to re-enable them (red stripe), and the console will then be back in the default programming behaviour. Tap RECORD again to save and close.

 

I hope this helps. Please let us know if you have any questions.

[Select, save just one feature ("slicing" a show)]

27 minutes ago, discover said:

a) Do y understand you right: "prepare" means in this case:
moving them to the new postion without/before lighting up?

That is correct. By "prepare", I mean triggering all programmed parameters to go to their defined values, prior to raising the intensity with the playback's fader. So: Colour, Beam, Shape, Position, & Effect values will be activated.

28 minutes ago, discover said:

b) If I "change the playback's flash button to be a Go button"
will it just afect this single flash button?

That is correct. If you open the settings of a playback, you will only be configuring the behaviour of this single playback. Please click the link below for more information...

https://www.zero88.com/manuals/zeros/cues-playbacks/playback-settings

[Select, save just one feature ("slicing" a show)]

1 minute ago, discover said:

As  Kevin stated above, to leave SmartTag enabled: will this disabling refer to:
- all Playbacks/Cues or 
- just this Playback/Cue?

Enabling/disabling SmartTag will affect what gets included when recording/updating. It does not affect cues that have already been recorded.

To be selective of what does and what doesn't get recorded, you will need to work with SmartTag disabled. Please click the link below for more information...

https://www.zero88.com/manuals/zeros/cues-playbacks/record-options/snapshot-smarttag#smarttag

[Varytec Event Par IP65 4in1 14x8W]

Fixture file for the Varytec Event Par IP65 4in1 14x8w...

Varytec Event Par IP65 4in1 14x8w.ift

(We had already made this fixture file).

[What Happened To The Colour Swatches ?]

10 hours ago, DALX said:

My question is why does the swatch colour appear on 21C L601 Silver but not 22C L332 Special Rose Pink or 22C, 23C, 24C, 25C. I tried shortening the colour name to one line but that did not make the colour swatch appear.

If no colour splash is shown on the colour palette tile, this suggests that not all of the fixtures recorded in that palette are exactly the same colour. For example, let's say you raise channel fader 1, change the fixture's colour, but then decide you don't want that fixture so lower its fader and then raise channel fader 2. If you then change fixture 2's colour, and record a colour palette, a colour splash won't show, because you will have also included fixture 1 in a different colour in the palette. In this example, CLEAR should have been pressed, prior to mixing fixture 2's colour.

The colour splash will reappear if all fixtures in that colour palette are updated to be the same colour.

When you record a palette, by default ZerOS doesn't care what fixtures are on, or which fixtures are selected. ZerOS just cares about the fixtures you have adjusted.

[Select, save just one feature ("slicing" a show)]

On 11/17/2023 at 7:25 PM, discover said:

Has it to be stored necessarly with a intensity/light on (raised fader)?

No - you don't have to include intensity information in a cue, you could just record position information. However, if you just want to record position data without the fixture being on, you'll need to ensure SmartTag is disabled in the Record Options window. So, this would be the workflow:

1. Double tap CLEAR
2. Select your fixtures, and only adjust their position, leaving their intensity off
3. Press-and-hold RECORD to open the Record Options window, and ensure that "SmartTag" has a blue stripe, meaning disabled. If it is red, tap it to disable.
4. Then, tap the button below the playback you wish to record to
5. Double tap CLEAR

On 11/17/2023 at 7:25 PM, discover said:

In a theatre show I might fade the lights of a current scene and
with a next Cue/Playback, I want to move the moving heads "in the dark" ("blind") to their next position.

- The audiance shall not see the movement of the moving lights at all.

If you have recorded a lighting state on a playback fader, and you want the lights to prepare before raising the playback's fader, you could change the playback's flash button to be a Go button. This means you could then press the playback's button to prepare the fixtures, prior to then raising the playback's fader. To change the playback's button, hold SETUP and tap the playback's button, and from the options at the bottom choose either Go (Fade) or Go (Snap).

Hope this helps.

[speed override stop macro]

3 minutes ago, Ed75 said:

In a week I'll start programming a show again on FLX, I am into  making  the switch back again to FLX now

Excellent - let us know if there’s anything we can help with.

[speed override stop macro]

Hi @Ed75

17 minutes ago, Ed75 said:

On my FLX I'm trying to make a macro which stops the 'speed override' from working. I find it very easy to use speed override when checking cues, and therefore I put it under a playback fader also. But to avoid accidents I would like to record a macro which stops the override. Like pushing the override wheel in the Z screen . Then I would program the macro in one of the first cues of a show, and voila, no speed accidents . The way of recording a macro by recording the button strokes doesn't seem to work. (on the wheels?)

This is a nice idea. To do this, you would need to record a macro of pressing the Speed Override encoder's button. However this encoder is in the Z window. Therefore, if you usually live outside of the Z window, you will need to include going into the Z window as part of the Macro. So:

RECORD MACRO x ENTER > Keys > Z > tap encoder button 2 (Speed Override reset) > Z > MACRO.

Now, go into the settings of that Macro (hold SETUP and tap your Macro onscreen, or use the syntax MACRO x SETUP), and set the playback speed to slow.

Now, when this macro is triggered whilst outside of Z, Speed Override will be reset.

Macros on ZerOS are not conditional, so there would be no way of running a different macro dependent on whether or not you're currently in the Z key.

I hope this helps. Let me know if you have any questions.

['Tis the season to be... hilarious! (original title: No more excuses ;-)]

1 hour ago, kgallen said:

Look, I know you boys have now got Neo and probably lots of other secret stuff to work on as well as ZerOS, but Christmas just isn't the same without an Advent Calendar 😉

1 hour ago, kgallen said:

For those who don't know, we used to be treated to beauties like this (and yes I did just re-watch it instead of testing Edward's latest ZerOS beta 😆 ). I'll note we're still waiting for the feature with the drop down menu that drops the scenery!!!

Ah yes the Advent Calendar. This was a lot of fun to make, and is still all very relevant! Although we're not posting a new one this year, do work through the Advent Calendar again, which is available here!...

[ORB XF Lighting Controls Not Responding]

1 hour ago, iank99 said:

It's also possible that if you have fixtures connected to your desk i.e. LED's or moving heads that there might have been changes in the fixture definitions since your early version - I can't remember how ZerOS handles that situation I'm afraid but I would expect it to make a decent go at leaving you with useable fixtures.

Upon loading a show file, ZerOS will compare the fixtures in the show file with the latest versions of the fixtures in the installed ZerOS Library. If the fixture personalities are identical in absolutely everyway, ZerOS will patch these fixtures from the library, rather than the show file. If there are any differences in the fixtures, ZerOS will load the fixtures from the show file, leaving you with two slightly different versions of the same fixture in Add Fixtures.

[USB Stick doesnt seem to read?]

Hi @Shane Considine

Welcome to the forum.

Please ensure the USB drive is not in the exFAT format, as this format is not supported by FLX S24 consoles. If your USB drive is a large capacity drive in the exFAT format, you should be able to reformat it to the NTFS format on a Windows PC, which will then be compatible with FLX S24.

Please let us know if you have any questions.

[Jester Zero 88 Help]

14 hours ago, tiffayo123 said:

our main problem is that when the console is not plugged into the wall dmx port the lights start going wild at like stupid times

Out of interest, do you have any "ChilliNet" button panels around your venue that are used to recall scenes on the dimmer when the Jester's disconnected?

[Old desk for spares]

34 minutes ago, Techie_v2 said:

So a year or two ago we had a leak over a weekend which drenched our FLX.

 

Oh yes I remember this. I’m glad you were able to get a replacement, and hope the insurance company was easy to deal with. 

35 minutes ago, Techie_v2 said:

So my question is, where do we stand and is there a market, if we wanted to try and raise some capital by selling it as spares on a generic auction type website?

FLX is still a bit too new for there to be much of a spares market for it.

If someone at your venue is pretty handy with swapping out boards/touchscreens, I think I’d be tempted to keep hold of it as spares for your good FLX. Or, you could even source replacements for damaged components, and give yourself a second console (as a spare, or Tracking Backup).

However, if you don’t ever think you’d make use of it, and aren’t in a hurry to get rid of it, it might be worth sticking it on an online auction site for a buy it now price, as spares/repairs. 

[ETC fixture not being picked up on RigSync]

14 minutes ago, alg said:

Re the saving of the port allocation, I guess in the short term I can simply swop round my use of the ports to take account of the fact the port 1 will always default to RigSync enabled and use that for my LED fixtures and use Port 2 with RigSync disabled for the Betapacks. So for now I will pass on your Beta S/W offer, thanks.

Makes perfect sense. No problem.

15 minutes ago, alg said:

Re the DMX addressing, the Betapacks are not RDM enabled. I did try running with it on but found RigSync would insist on changing the DMX start address on each of the 5 packs making a nonsense of the labelling on the packs for patch purposes. What was happening was whilst the desk had reallocated DMX channels to the new Coloursource fixture i.e. 1-5 the Betapack was still seeing the DMX output and so I had the Betapack and Coloursource all running off the same channels on the desk.

If the Betapack channels are patched manually, and RigSync cannot see them, upon discovering a new fixture RigSync should not patch the discovered fixture to an address which is already in use on the same universe. If the console has done exactly that, please email me a copy of your console's show file.

17 minutes ago, alg said:

Re the RigSync control of the Coloursource Fresnels via the splitter, since these fixtures were previously discovered and known to the desk I assume there was no RDM management going on and the DMX was simply taking the fixture up and down. So I cannot say RigSync was working only that it was possible to take the control the fixtures in terms of setting intensity etc.

So when you originally allowed RigSync to discover and configure the fixtures, you were not connected via the Splitter?

Now that the fixtures are connected via the Splitter, do you receive "Device not responding" errors at the top of the Output window? If so, this means that the console is not getting an RDM response from the fixtures via the splitter, even if they can still receive DMX.

18 minutes ago, alg said:

Re the issue with the lack of DMX output, I will need to check this in the theatre when I can next get across, possibly tomorrow or Friday afternoon. If I still have problems I will phone direct as you suggest.

No problem - let us know how you get on.

[ETC fixture not being picked up on RigSync]

Hi @alg

As @kgallen mentions, this may be easiest to troubleshoot over the phone.

52 minutes ago, alg said:

I have checked further this morning. It would appear that regardless of how I configure Universe 1 outputs the desk always reverts to Port 1 with Rig Sync enabled and the opposite for Port 2. Simply powering the desk off will reset to these settings. Why does the desk not retain the settings I input i.e Port 1 RigSync disabled and Port RigSync enabled?

Thank you for checking this. It sounds like you have encountered an issue we are aware of in ZerOS 7.14, where the RigSync settings per DMX port may not be saved. This issue has been fixed in the latest stable beta. If you would like access to the stable beta software that solves this issue, please let me know, and I can share this with you.

1 hour ago, alg said:

However it simply allocates the fixture to DMX start address of 1 and takes the next 5 addresses. This means the first 5 DMX channels that should be driving the first Betapack only is now driving both dimmer and ETC fixture.

If RigSync is enabled on the DMX port the Betapack 3s are connected to, RigSync may have readdressed the Betapack 3s, leaving the ETC fixture at its current address.

On 11/14/2023 at 1:43 PM, alg said:

Port 2 has RigSync enabled and feeds an 8 way Chauvet DMX splitter, this currentlysupports our existing four Coloursource fresnels. All appears good with this existing set up.

56 minutes ago, alg said:

The next problem is why is RigSync not working via the Chauvet DMX splitter, as  noted previously the device is RDM compliant. Does RigSync not work via other manufacturers products? This is well used  by our supplier in his installations an hires and is made by one of the large lighting companies, surely it should be compatible.

Based on your description my understanding is that RigSync DOES work via the Chauvet DMX Splitter with the ColorSource Fresnels? If so, the splitter is RDM enabled, and RigSync should be able to discover any RDM-compliant devices connected to the Splitter's DMX ports. I am not sure why the ColorSource JNR Spot is not being discovered, whereas other fixtures are. If you unplug the ColorSource Fresnels from the splitter, and connect the ColorSource JNR Spot instead, does RigSync then discover the fixture?

Some DMX splitters have the ability to switch off RDM on the output ports, so this would be worth checking.

1 hour ago, alg said:

More alarming whilst investigating the desk has taken umbridge and has now completly blocked all DMX ouput from the desk! All the Dimmers and previously installed fixtures will simply not respond to the desk. I have powered off and restarted but still no output. What can cause such a wholsale inhibit on the DMX outputs?

In Setup > Universes > DMX, confirm the DMX ports are indeed enabled. In Setup > Fixture Schedule, doublecheck which universes fixtures are patched onto. In Setup > Universes, scroll down to the Desk Universe the fixtures are patched on, and confirm the DMX ports have been added to that Desk Universe. Z/Shift > System Information > DMX Outputs will show you the levels of the DMX universes the console is outputting.

Please let us know if you have any questions.

[Strange Control Issue]

Hi @scottydog75

48 minutes ago, scottydog75 said:

When selecting 101 only and setting intensity, fixture comes on. If I selected my Fresnels group, all Fresnels expect 101 illuminates, even though the output window suggests it should be on. Fresnel 101 also did not respond to cues within the Master PB.

I ended up resolving this by physically plugging the Fresnel into a nearby dimmer circuit, and re-patching the desk, which then resolved all issues

This is indeed strange behaviour, and is most likely down to the venue’s dimmers. What dimmers are they? Sounds like they could be doing some form of load limiting (either intentionally or incorrectly!). 

The DMX Outputs window on the console shows the raw outputs of the console, and won’t lie. 

46 minutes ago, scottydog75 said:

Completely unrelated, is there anyway the desk can calculate total cues (including . cues)? I know there is a 'last cue' number in the PB view, but this number does not include . cues. (Purely for bragging rights with my local lighting folk..! )

Copy your playback to an empty playback, hold SETUP and tap the button of the playback you pasted, Advanced > Renumber. The “last cue” field now shows the total cues in that playback. 

Hope this helps. 

[Playback levels]

10 minutes ago, Les Green said:

All sorted now. Thanks for your help. I am a relative beginner and I didn’t know about LTP!

No problem at all - really pleased to hear that solved the issue. Let us know if there's anything else we can help with.

[ETC fixture not being picked up on RigSync]

1 hour ago, alg said:

Port one serves our 30 channels of BetaPack dimming with no RigSunc enabled. Port 2 has RigSync enabled and feeds an 8 way Chauvet DMX splitter, this currentlysupports our existing four Coloursource fresnels.

In Setup > Universes > DMX, can you doublecheck that RigSync is definitely disabled on port 1, and enabled on port 2...

https://www.zero88.com/manuals/zeros/setup/universes/dmx-2

1 hour ago, alg said:

I have tried to add an additional ETC Coloursource Junior spot, the RigSync is not picking this new fixture up

The RDM information for this fixture is included in the latest library, so ZerOS should automatically patch the fixture from the library when it is discovered.

[Effect recorded into default is hard to get rid of]

16 minutes ago, Davidmk said:

Did expect update remove to get rid of colour values for the affected fixtures though.

Fixtures must have default values. It is therefore not possible to remove parameters, because they must have a default value assigned.

You are therefore essentially always "updating" when recording to the Home key. DELETE HOME is a special operation, that reverts the values to the library defaults (but of course does not remove parameter data).

Hope this makes sense.

[Effect recorded into default is hard to get rid of]

On 11/12/2023 at 3:01 AM, Davidmk said:

I must have accidentally recorded the warm rainbow into default

Effect data (Speed, Size, etc) cannot be stored as a fixture's default values. However, if a fixture's parameters were referencing the values stored in an effect palette, these values would get stored in the fixtures Defaults, as per any other parameter referencing a palette. So if you apply a [Rainbow - Warm] effect, and then RECORD > HOME > Default, RGB will store a reference to E23 (effect palette 23).

On 11/12/2023 at 3:01 AM, Davidmk said:

What's the right to get to get effects out of  defaults if you accidentally put them in?

19 hours ago, Davidmk said:

The fix, ultimately, was to record an actual colour into default and then to delete it.

Yep, that is the best solution: select the fixtures, set the desired colour values, such as applying colour palette 1 [White], and then RECORD > HOME > Default.

[Playback levels]

Hi @Les Green

Welcome to the forum.

I believe my colleague Keith has replied to your email regarding this.

18 hours ago, Les Green said:

I can’t remove a lantern or reduce its intensity. I used to be able to do this by moving the requisite fader to maximum then reducing it to the required intensity or zero

23 minutes ago, thierry said:

(being LTP mode)

I think @thierry has hit the nail on the head - you'll need to make sure your channel faders are in "LTP" mode, rather than "HTP" mode. When in LTP mode, the channel faders can be used to reduce the levels of intensities active in cues. When in HTP mode, the channel faders mix with the active cues, rather than override them. The Channel Mix Mode can be set from the SPECIAL MFKs.

18 hours ago, Les Green said:

I can add an extra lantern by putting the fader up to the level I require then RECORD>MERGE

As a side note, we would recommend using the UPDATE key when adding/removing lights from an existing cue. To do this, go into a cue, make your changes, tap UPDATE, and then tap the playback's GO button.

Hope this helps.

[confusion about blocked values]

On 11/6/2023 at 10:19 PM, LLuk said:

But i still dont understand why there are again some blocked values after update every single cue with no changes but SmartTag enabled.

On 11/11/2023 at 1:15 PM, LLuk said:

BUT...then the next cue(cue 11) changes to blocked values.

i do the same (update - enter)with cue 11, and then again cue 12 get blocked values.

The issue here is that you are unblocking cue only.

Let's say cue 11 is blocked, and cue 12 tracks from cue 11.

If you unblock cue 11 (UPDATE > SmartTag > GO), you are removing data from the cue. If you are doing this as a "Cue Only" update, this means the console will remove blocked data from cue 11, and add that removed data back into cue 12, to make sure that cue 12 looks exactly how it was programmed. This is exactly the same as if you were to turn a light off in a cue, and do this as a Cue Only update - the console would need to add the light into the next cue, so the next cue looks how you originally programmed it. In your example, cue 12 then may become partially blocked, as it is now telling fixtures to go to values they were at in the previous cue.

So, in this example you could update cue 11 with SmartTag and Track Forwards enabled, and this would unblock the current cue, and would not add/remove data to/from the next cue.

I hope this helps. Please let me know if you have any questions.

[confusion about blocked values]

Hi @LLuk

1 hour ago, LLuk said:

when i have blocked values in a cue (for exempel cue 10) and i want them unblocked,
i press update - (smarttag enabled) - enter, and they change to tracked values(when its possible).

BUT...then the next cue(cue 11) changes to blocked values.

i do the same (update - enter)with cue 11, and then again cue 12 get blocked values.

 

Before unblocking cue 10, are you sure that cue 11 wasn’t also blocked? If you went into cue 10 and then cue 11, were the fixture’s intensity percentages displayed in white in the Output window in both cues?

Unblocking cue 10 would not also unblock cue 11, so you’d find that the intensity percentages were purple in cue 10 when unblocked, and white again in cue 11. 

As mentioned, you’ll have to do this if you want to unblock every cue in the stack…

1 hour ago, LLuk said:

(setup - PB button - advanced - block/unblock).

 

[Fixture - Showtec Shark Zoom (Wash) One - work only with 15 Channel mode.]

15 hours ago, discover said:

I have learned,  followed your instructions and set-it up accordingly.
This has worked out. 😀

15 hours ago, discover said:

- In this case, I go for the higher mode (15 Channel) which makes life easier. 

Excellent - pleased to hear it. Let us know if there's anything else we can help with.

[Unexplained circuit response.]

Hi @Stan Vigurs

39 minutes ago, Stan Vigurs said:

I just finished programming our next production and noticed that when I was setting the value on circuit 14, circuit 26 was also responding albeit in a somewhat erratic nature. 

Were you raising fixture 14's channel fader, and noticing that it was also adjusting fixture 26's intensity? If so, I would recommend testing your console's faders.

To do this, switch off the console, and then switch it on with the SETUP key held down. After around half a minute, the console will boot into Test Mode, with a virtual front panel shown on the internal touchscreen. Please move each fader up and down, and check that the console is registering the level of the faders correctly. If a physical fader's level does not match the fader level the console is registering onscreen, or a physical fader activates a different fader onscreen, please let me know, and I can advise the best steps to take.

To exit Test Mode, switch the console off and back on again, and it will then boot normally.

Please let us know if you have any questions.