[FLX S24 Communication Erros reported by Co-Processor]

Hi Stefan,

Really sorry to hear this. Thanks very much for linking to a video of the issue. 

When the issues are shown, do you always have your USB hub connected? If so please could you send a link to the USB hub you are using? If you disconnect the USB hub, do the issues go away? This potentially sounds like a power issue, and the hub is trying to draw too much current from the USB ports.

If you have any questions please let us know.

Edward

[FLX control via Midi.]

4 minutes ago, Davidmk said:

Why doesn't it show up on separate octaves? Bug, surely

Correct. Unfortunately the “First Note” field is applicable for “Separate Octaves”, however is incorrectly hidden when Separate Octaves is chosen. Logged on our system, to be fixed in a future update. Most people will just live in “Separate Octaves” with the default of the First Note of 0.

Edward

[FLX control via Midi.]

Hi David,

2 hours ago, Davidmk said:

I've got the same for the first button but it fires pb1 not two. Edward said midi 0 would fire pb1 and you said midi 1 was firing pb2 1 if that is true then my desk must be operating in a parallel universe (or, being 2 versions behind is making the difference).

I reckon I have worked out where the confusion may be. If you tap SETUP -> Triggers -> Combine Octaves, what is your “First Note” set to? By default, this should be 0. This will mean in Channels, a Note 1 triggers fixture 1, in Cues Note 1 triggers cue 1, and in Playbacks Note 0 triggers playback 1. If you have the First Note set to 1, and then click Separate Octaves, in Playbacks Note 1 will trigger playback 1. Note 0 will have no function. 

Could this be what you’re seeing?

If so, to save @Uriahdemon remapping all the Novation buttons, you can tap Combine Octaves, change the First Note to 1, and then click Separate Octaves.

Edward

[FLX control via Midi.]

Hi David,

26 minutes ago, Davidmk said:

The desk is still on the last-but-one version of ZerOS - don't know if that makes a difference. It thought it looked OK on Capture though.

This has been how MIDI Notes has operated on ZerOS since it was introduced - the first note (note 0) triggering playback 1. Therefore if your configuration was working, a software update won’t change that.

So not sure where the problem Mac has found has arisen from?

When we do come to map the MIDI Notes 1:1 with playback’s, you will need to remap your set up.

Edward

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

Hi Joe,

On 10/14/2020 at 11:52 AM, 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.

Just thought I'd post to confirm that recording intensity effects onto UDKs play back correctly.

Edward

[FLX control via Midi.]

Hi Mac,

1 minute ago, Uriahdemon said:

Indeed it is Ed,  just sussed that out this end.....  thanks for your help  !!!!

No problem - in a future update we will ensure MIDI Notes are patched 1:1 with playbacks, which will also allow the Master Playback to be triggered.

Edward

[FLX control via Midi.]

Hi Mac,

3 minutes ago, Uriahdemon said:

That is triggering PB2 as opposed to PB1 have you any idea why that may be happening please.... did you come across that and just ignore PB 1.......??

MIDI Notes 0, will trigger playback 1, and MIDI Note 1 will trigger playback 2 and so on.

This may be what you are seeing?

Edward

[Manual Fade and Go Fade in Cue list + BUG ?]

Hello,

9 minutes ago, Transversales said:

Is there a way to mix manual fade (2 way) with Go (fade) ? Using the manual fade seem to desactivate permanently the Go button.

No there isn't - if you choose to use the Manual Fade options, the fader advances you through your cues, rather than the Go button.

10 minutes ago, Transversales said:

After using a manual fade on a cue list, how to revert to another fader mode (HTP or the other manual fade) without deleting the cue list, turning on/off the FLX S48 or making a save/Load of a file.

After operating a cue list with Manual Fader 1-way or 2-way, it cannot simply be changed to a different Fader Function. Therefore if you do wish to operate the cue list with a different fader function, change the cue list to the fader function you need, and then copy it to an empty playback fader. The new copy will then playback with your newly chosen fader function.

13 minutes ago, Transversales said:

if after using manual fade you press CLEAR+GO, the fader become desactivated (Go is still not responding), and trying to change the fader mode, make appear a new line at the begining of the cue list, with the Q# "--".

The same things could be reproduced on any MFF.

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.

If you have any questions let us know.

Edward

[FLX ZerOS 7.9.5 - Weird Arrow Keys Behavior]

Hello,

39 minutes ago, Delete-0-Enter said:

Sad this didn't get fixed in ZerOS 7.9.8. ☹️

After resetting the console, currently the active window is the Output window. To focus onto the Cues window on the external monitor if you don't have a mouse or touchscreen connected, jump into the playback's settings and then click OK. Your arrow keys will navigate the Cues window.

Or, coincidentally, use the syntax DELETE 0 ENTER.

Edward

[Update to ZerOS-7.9.8 there are problems.]

Hi Alex,

On 10/15/2020 at 1:04 PM, AlexSky said:

Checked... same values change but are not displayed on the console LSD.

 

On 10/15/2020 at 1:43 PM, AlexSky said:

As I understood on the ORB XF console in version 7.9.8. the LSD screen does not work, and in version 7.9.7 everything works perfectly.

Thanks for all your information on this.

We have found an issue that is affecting the encoder displays on some ORB series consoles. We will look to release a bug fix for this as soon as possible.

In the meantime if you wish to roll back to ZerOS 7.9.7, please see the link below...

https://zero88.com/zeros#legacy

If you have any questions please let us know.

Edward

[Update to ZerOS-7.9.8 there are problems.]

Hi Alex,

After recording a cue with intensity information stored, please tap on the "Fade Up" or "Fade Down" fields in the Cue list window. Do the encoders display fade and delay times correctly?

Edward

[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