[7.9.8 Keyboard shortcuts - nice but...]

Hi Pritch,

Thanks for the comments. We had quite a few conversations about which key should be Thru.

The > symbol makes the most sense as being Thru, and has been the shortcut for Thru on ZerOS for many years. We therefore decided to leave Thru as > as this is what users will be used to, despite the fact you need to use Shift.

Forward slash (/) is used on FLX to allow you to define a Playback/Cue number, and so we couldn’t use / for Thru.

If you have any questions let us know.

Edward

[FLX control via Midi.]

4 hours ago, Uriahdemon said:

What values have you entered in Triggers>Notes please...??

 

4 minutes ago, Davidmk said:

I can't remember. I'll look it up and get back to you.

I'm going to guess, in Setup -> Triggers, MIDI Notes is set to playbacks, and the Channel is left at 0 (to receive Notes commands from all channels), or set to the channel number set on the Novation.

Your octaves will likely be set to "Separate", to give you access to playbacks 0 to 127.

Edward

[FLX control via Midi.]

10 minutes ago, Davidmk said:

You will find that it is useful to see what the pads are actually sending and you can find that using the Z key (system info->events if my memory serves). "Flash" should send a note-on when you press the key and note-off when you release, "latch" should send a note-on when you press it the first time and note-off when you press it again.

^Yep exactly right, tap Z -> System Information -> Event Monitor to see incoming MIDI Notes or MIDI Show Control commands. Incoming MIDI Timecode clock can be found in the status bar along the bottom of the Cues window on the external monitor.

Edward

[Update to ZerOS-7.9.8 there are problems.]

Hi Alexander,

57 minutes ago, AlexSky said:

Yes, I did so too, and in ORB XF encoders 2 and 3 remaining blank (blue), and "intensity" and 1 encoder, work. And in Phantom ORB XF everything works great. The contrast LSD checked all right.

Thank you for confirming. On ORB XF, if you select a fixture, and encoders 2 and 3 remain blank, please view the "Wheels" desktop on the external monitor. Are the parameters displayed on encoders 2 and 3 here? If you use the physical encoders, do the values change on the external monitor?

Edward

[ZerOS 7.9.7.28 (RELEASE CANDIDATE) and ZerOS Monitor (Windows) 1.9.2 (RELEASE CANDIDATE)]

Hi Joe,

3 minutes ago, JWylie91 said:

Brilliant, slightly relieved it is a bug and not just myself doing something stupid.

Thanks for your help.

I look forward to the update.

Yes don't worry nothing you have done - thanks very much for helping us find the issue!

Edward

[ZerOS 7.9.7.28 (RELEASE CANDIDATE) and ZerOS Monitor (Windows) 1.9.2 (RELEASE CANDIDATE)]

Hi Joe,

Thanks for the further information. I have been able to recreate the issue.

There is an issue in some scenarios where the effect parameters for intensity effects are not getting recorded into cues, for multi-parameter fixtures. I have logged this on our software tracking system as ZOS-10476. Currently no release date yet, but we may do a minor release to fix this, and also include an update to ZerOS Library.

If you have any questions please let me know.

Edward

[Starcloth flicker issue.]

Hi Steve,

Are you controlling any other fixtures on that DMX line? Are they also showing a "flicker" when the starcloths do?

You say the display in the controller box flickers - this almost sounds like a power issue, where they are momentarily loosing power and booting back up? Are both starcloth controller boxes connected to the same power supply? If you disconnect the controller boxes from the DMX line, and leave and watch them, do the displays continue to flicker?

5 hours ago, Gingersteve91 said:

Any ideas if this is due to something clever the desk is trying to do in the background?... We’ve turned rigsync off for the universe, tried new DMX lines, terminators, different modes but no change. 

 

If you have RigSync disabled and this hasn't had an effect, then this rules out an out of spec fixture being the issue. You've tried all the usual troubleshooting of new cabling and terminators to rule these factors out too. The console will be outputting DMX at a continuous 30Hz, so there is nothing obvious that could be causing this.

If you'd like to give me a call when you're in the venue troubleshooting it, drop me an email and I'll send you my number.

Edward

[FLX control via Midi.]

Hi Chris,

I have taken a quick look at the YouTube link. If I wanted to run my show like this on FLX, I would simply use some intensity playback masters, and then a touchscreen with all my palettes programmed, which I can then just tap and fade between using Programmer Time. To achieve this via MIDI, you can then just instead record your different looks onto individual playbacks which can be triggered by Notes, and fade between them using the cue fades.

Edward

[Update to ZerOS-7.9.8 there are problems.]

Hi Alex,

16 hours ago, AlexSky said:

Devices in which no values were displayed: Briteq BT-575S, Briteq BT-575W, Briteq Led Mega Beam, Briteq Led Pixel bar RGB.

I have patched a BriteQ BT-575S into Phantom ORB XF running ZerOS 7.9.8. Selecting the fixture and tapping COLOUR, shows me "Colour Wheel" and "Colour Wheel Mode" parameters on encoders 1 and 2. Tap BEAM, and gobo controls are shown on encoders 2 and 3, tap BEAM again and I can page through.

What are you seeing when doing this? Are the encoders remaining blank (blue)? Is the "Intensity" display visible above the intensity wheel? Have you held SETUP and adjusted the LCD contrast?

16 hours ago, AlexSky said:

It is also unclear how in 7.9.8 to create a new device using Fixture Type Editor with a resolution of .zlbr

The Fixture Editor software still allows you to create fixtures in the .ift file format, which can be loaded into ZerOS 7.9.8. These custom fixture files will therefore be displayed in red in Add Fixtures and the Fixture Schedule, to indicate the fixtures are not from the library. If you would like fixtures adding to the library which are missing, please email the fixture's manual to us at fixturesupport@zero88.com, and we'll be able to get this added to the library for the next release.

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

Edward

[ZerOS 7.9.7.28 (RELEASE CANDIDATE) and ZerOS Monitor (Windows) 1.9.2 (RELEASE CANDIDATE)]

Hi Joe,

3 hours ago, JWylie91 said:

I have attached the showfile I am experimenting on, Playback one is currently outputting the effect properly as I have altered a value in its playback settings whereas playback 2 hangs on the 50% intensity value as I am yet to change anything in the settings option.

Great, thanks very much for attaching your show file. I will take a look at this tomorrow and investigate what may be going on.

Edward

[ZerOS 7.9.7.28 (RELEASE CANDIDATE) and ZerOS Monitor (Windows) 1.9.2 (RELEASE CANDIDATE)]

Hi Joe,

26 minutes ago, JWylie91 said:

It appears that the default setting under Move on Dark had Don't Move Effect selected. 

"Don't Move Effect" will be chosen by default. This is to ensure that if a fixture goes dark, it does not start running an effect that is coming up the next time the fixture is used. This is to avoid your fixtures unnecessarily moving in the rig.

30 minutes ago, JWylie91 said:

Once this was deselected on my playback the effect started working as expected. 

I am a little unsure of what your initial issue may have been. I have been unable to recreate the issue you have described, however, glad to hear you have solved it!

Edward

[Presets to become Channel/Playback selectable on Solution series?]

Hello,

Thanks for the information.

19 minutes ago, delicolor said:

It seemed to be fine via the actual playback faders but via the triggering they went up OK but stayed up.

18 minutes ago, delicolor said:

However I will look more closely when next in the venue as it might have been something I overlooked.

Yes please take a look when you next get a chance - when DMX In is controlling a playback, the physical fader level and fader level from the DMX Input should mix with LTP catch behaviour.

23 minutes ago, delicolor said:

I cannot emulate this on Phantom ZerOs due to the inability to connect DMX OUT to IN to fire the triggers.

24 channels of DMX In can be sent to Phantom, by opening the "DMX In Panel" window from the Phantom ZerOS launcher, and then using the virtual faders to emulate your DMX input.

39 minutes ago, delicolor said:

The illustration shows the display with only blue selected at 100% but white misleadingly remains highlighted. The same seems to happen with intensity. It is immediately updated to show correctly if adding/deselecting fixtures or refreshing the outputs screen.

Well spotted - the parameter table is not updating the tag/untag state straight away when parameters with no Special defined and no details are manually tagged/untagged. The encoder displays are updating correctly, and tapping into the Output window updates the parameter table correctly.

I have logged this on our software tracking system as reference number ZOS-10473.

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

Edward

[FLX control via Midi.]

Hi Mac,

5 minutes ago, Uriahdemon said:

I was wondering if Phantom ZerOS was able to interface with the midi as I do most of my programming using Phantom ZerOS on a PC with Capture....??

Currently ZerOS does not support MIDI over USB, and so you will not be able to trigger Phantom ZerOS with MIDI.

You will however be able to do all of your MIDI configuration in Phantom, save the show and load in into your FLX, and your FLX will then be preconfigured ready to accept MIDI triggers.

Edward

[ZerOS 7.9.7.28 (RELEASE CANDIDATE) and ZerOS Monitor (Windows) 1.9.2 (RELEASE CANDIDATE)]

Hi Joe,

OK thanks for the information.

1 minute ago, JWylie91 said:

I shall update to 7.9.8 today and report back if this is still happening. 

Yes please update to ZerOS 7.9.8, and if you are still having difficulties, please email me a copy of the show file that is showing the issue, and I'll take a look.

Edward

[Move on dark]

Hi Simon,

Hope you're well.

10 hours ago, SimonH said:

anyone tell me how to change the move on dark times for a cue that’s recorded? 

To change the Move On Dark timings for a playback, go into the Playback Settings by pressing and holding SETUP, and tapping the playback's button. Then choose the Move On Dark tab, and adjust the delay and fade time. Press OK on the Settings window, and you will see the new times displayed along the bottom of the playback status bar in the Cues window on the external monitor.

As @kgallen mentioned, Move On Dark timings are available for the whole playback, not individual cues. For individual cues, Don't Move flags are available in the Cue Settings.

10 hours ago, SimonH said:

I’ve altered the default but it hasn’t changed the existing cues. 

Editing defaults within Setup -> Defaults, will never affect existing cues. These defaults will be used by any future cues recorded.

Hope this helps,

Edward

[FLX control via Midi.]

Hi David & Chris,

1 hour ago, stowedout said:

My next project is to try using an Akai APC20 and assign faders to parameters to give a bit more flexibility while busking  shows

 

12 minutes ago, Davidmk said:

How are you planning to use faders in this context?

Most MIDI fader banks, send their fader levels over the MIDI Control Change (CC) protocol. ZerOS currently doesn't support this protocol, however it is on our software tracker as a potential future enhancement (software tracker reference number ZOS-10271).

The three MIDI protocols currently supported in ZerOS are Timecode, Show Control and Notes. I am not aware of such a device, but it could be possible that when a MIDI fader hits a certain level, it fires a MIDI Note, allowing you take advantage of MIDI fader handles purely to trigger ZerOS.

If you have any questions let us know.

Edward

[ZerOS 7.9.8 Released]

Dear All,

Zero 88 are pleased to announce the launch of ZerOS version 7.9.8 software - a new software release for the following consoles:

• FLX
• FLX S24
• FLX S48
• ZerOS Server
• Solution
• Solution XL
• ORB
• ORB XF
• SCD Server
• Leapfrog 48 & 96

The ZerOS 7.9.8 download for your console, Phantom ZerOS 7.9.8 offline editor download, and the release notes, can be found at zero88.com/zeros

Also available from the link is the new ZerOS Monitor 2.0 for Windows, supporting new keyboard shortcuts to allow you to remotely control your console.

If you have any questions, please don't hesitate to contact us at support@zero88.com

Kind regards

Edward

[FLX control via Midi.]

Hello,

1 hour ago, Davidmk said:

You will need a USB to midi interface. There is one that Z88 recommend

This is the one we use for training, testing, and demonstrations...

https://motu.com/products/midi/fastlane_usb

Edward

[Presets to become Channel/Playback selectable on Solution series?]

Hello,

3 hours ago, delicolor said:

Edward, I assume that if I route the DMX OUT to DMX IN via a splitter in the above scenario, the channels I don't use to trigger Playbacks are available to route on to fixtures if desired?

Yes, exactly right. Rather than wasting a whole output for just a few channels used to trigger your playbacks, you could use a DMX splitter plugged into a DMX output, route one of the outputs back into the console, and then use the other outputs to control fixtures. 

Edward

[FLX control via Midi.]

Hi Mac,

8 minutes ago, Davidmk said:

Stowedout did a topic on this, it's pinned near the top of the FLX page, he uses a different approach that you might find interesting.

Yes, take a look at @stowedout’s quick overview of his set up below...

This is the thread David mentioned, which explains this...

I’m sure you have seen this article already, but for the ZerOS side on how this is configured, see below...

http://support.zero88.com/990063141

If you have any questions let us know. 

Edward

[Fixture editor 3 wheel groups]

Hello,

ZerOS does not use the customised wheel groups defined in the Fixture Editor. These are used by legacy consoles. 

The order ZerOS consoles will display the parameters on the encoder wheels, is the order the parameters are listed in the Fixture Editor. To move a parameter to the end of an attribute, change the parameter to a different attribute, and then back again.

If you wish to have your “White” parameter on the third encoder wheel, you would need to create a pair of dummy parameters, that would sit on encoders 1 and 2 of the second encoder page.

When creating fixture files, we tend to only ever list parameters in the order of DMX address, unless there are odd cases where two related parameters are not next to each other, such as a function, and the function’s speed, or a function, and the function’s rotation. 

If you have any questions let me know.

Edward

[Activate Chaser speed manually]

Hi Adam, 

Welcome to the Zero 88 Forum.

30 minutes ago, StageAdam said:

Hello in the chasers speed if I selected manual how do I Trigger it

What console are you using?

Edward

[ZerOS 7.9.7.28 (RELEASE CANDIDATE) and ZerOS Monitor (Windows) 1.9.2 (RELEASE CANDIDATE)]

Hi Joe,

23 minutes ago, JWylie91 said:

when saving an effect such as chase 1/2 in cue 2 where cue 1 is simply bringing the intensity up to 100 the effect seems to be being registered and the intensities of my Rogue R1's drop to 50 when calling cue 2. The fixture also shows the chaser 1/2 effect in the intensity section of the cue window, however there is no movement of intensity values or visible effect.

So to confirm, cue 1 has your fixtures at full. Then select the fixtures, and apply Chaser 1/2. As part of this effect, the fixtures are automatically taken to 50%. You then record this as cue 2.

On playing this back, when going into cue 2 from cue 1, your fixtures will fade down, with the intensity chase fading up. You should then end up with chasing intensity percentages displayed in green in the Output Window.

Are you finding in cue 2 your fixture intensities stay at 50%, displayed in green in the Output window? If so it sounds as though the Size of the effect is recorded at 0?

Edward

[ZerOS 7.9.7.28 (RELEASE CANDIDATE) and ZerOS Monitor (Windows) 1.9.2 (RELEASE CANDIDATE)]

Hi Joe,

If you select the fixture, and open the "Shutter, Strobe, Control" parameter details by tapping the middle encoder button, try tapping the last "Macros" detail, which will set the parameter to a DMX level of 251. Leave it there for a few seconds, and see whether the fixtures respond. If they don't, it sounds like DMX Lamp Off is disabled in the fixture menu.

If you have any questions let me know.

Edward

[ZerOS 7.9.7.28 (RELEASE CANDIDATE) and ZerOS Monitor (Windows) 1.9.2 (RELEASE CANDIDATE)]

Hi Joe,

26 minutes ago, JWylie91 said:

When I create auto macros for my Mac 250 Entours I used to always get a Lamp on and a Lamp off macro auto produced. 

I have just taken a look at the Martin Mac 250 Entour fixture. The new library has a "Fixture Global Reset", and a "Lamp Off" macro available for the fixture.

28 minutes ago, JWylie91 said:

• No Lamp off in shutter options when the Mac's are selected - I cannot lamp them off other than manually on the fixture.

In the new library, if a macro has been created to control a function of a parameter, that parameter's detail will instead display "Macros", to indicate the fixture macros can be used to access this function. 

30 minutes ago, JWylie91 said:

• Lots of auto created macros however no Lamp on macro

There are two fixture macros for the Mac 250 Entour. If you are seeing more these will be from other fixtures currently patched in the console. Lamp On can be accessed by selecting the fixture, and tapping the middle encoder button of the "Shutter, Strobe, Control" parameter, to view the details. You can then tap "Lamp On", to send the command.

30 minutes ago, JWylie91 said:

• No response when selecting Lamp off in the macro menu

After selecting the fixture, and applying the "Lamp Off" macro, the first parameter is taken to full, and then lowered again. This can be seen in the DMX Outputs window, and so the macro seems to be working correctly. Can you confirm the DMX lamp off function hasn't been disabled on the fixture (PERS/dLOF)? More information on page 14 below...

https://cdn01.usedlighting.com/products/files/f58c30c67693da.pdf

If you have any questions let us know.

Edward