-
Posts
3,259 -
Joined
-
Last visited
-
Days Won
78
Posts posted by Edward Z88
-
-
Hi Jean,
Many thanks for attaching the show file.
I have been using your show file, following your steps, trying various combinations, and have been unable to replicate the issue. I will continue to investigate this.
I noticed in your show file there is a fixture that has been discovered by RigSync called "RDM:0181". What fixture is this?
If you have any questions let me know.
Edward
-
Hi Jean,
8 hours ago, Jean Iwanowski said:Regarding the splitters, using only one of them doesn't fix the erratic RDM behaviour. I'm really starting to think those Showtec RDM splitters are a joke.
That's frustrating. In this case it does seem like these splitters are not truly RDM capable.
If you have any questions let me know.
Edward
-
Hi Jean,
1 hour ago, Jean Iwanowski said:Your reactivity is quite impressive, thanks a lot!
No problem!
1 hour ago, Jean Iwanowski said:However I am not sure I tried using only one splitter (not quite the solution in my case as I need 12 distinct DMX/RDM lines, but still interesting to try in order to confirm that those splitters break RDM conformity when chained).
I'll try that later today
Let me know how you get on following these tests.
Edward
-
Hi Jean,
Many thanks for the detailed description.
54 minutes ago, Jean Iwanowski said:The infrastructure is as follows : two Showtec DB-1-8/RDM splitters
55 minutes ago, Jean Iwanowski said:Has anyone positive experience with those splitters with other RDM consoles/fixtures? Or with ZerOS consoles? Do I do something wrong, or should I throw the splitters in the bin and buy better quality devices?
This is a bit of a case of déjà vu for me. I seem to remember several months ago, a customer reporting exactly this issue, when daisy-chaining these splitters. I'll have to check back through our records when I'm next in front of my laptop. From memory their issue was specifically when daisy chaining the second of their splitters from an output of the first. I believe daisy-chaining the second splitter from the first splitter's Thru port rather than an output was fine. I'd have to check that though. It seemed to be an issue with how the splitter was retiming the signal. Once this had been retimed twice through both splitters, it had been thrown out of the DMX and RDM specification.
If you just use the first splitter, disconnecting the second, do the fixtures connected to the first splitter respond correctly?
If you have any questions let me know.
Edward
-
Hi Jean,
1 hour ago, Jean Iwanowski said:Unfortunately I was just experimenting with the console at the time the problem appeared and I did not save the show at all. If it happens again, I'll make sure to send the show file to the support address.
No problem. We will investigate this to see if we can replicate the issue. If you are able to replicate the issue, a show file and the steps you took would be very helpful.
1 hour ago, Jean Iwanowski said:Good to know. Is there any way to check your "system" for known bugs and feature/improvement requests in order to avoid reporting something already known?
Our system is internal only, however we are always more than happy for console users to suggest features, and we can then either log the suggestion if it is a new request, or raise the priority of an existing request. Feel free to do this via the forum or email.
1 hour ago, Jean Iwanowski said:Thanks a lot. I'am currently experiencing quite a lot of problems with RDM/RigSync used through DMX/RDM splitters, but this is off-topic, I'll start a new topic about it.
Will take a look.
Edward
-
Hi Peter,
24 minutes ago, Pete-S said:Thank you Edward. The console is brand new out of the shop, so I assumed it was running the latest firmware.
No problem. If you email me the console's serial number, I will be able to confirm when this console was manufactured. Please don't post it here.
If you have any questions let me know.
Edward
-
Hi Pete,
44 minutes ago, Pete-S said:My FLX-S24 saves show files in the format *.isf, which I can open in PhantomZeroS, but this in turn only saves in the format *.zos, which the desk doesn't show in the file menu. What do I need to do to open show files from PhantomZeroS on my desk?
If your FLX S24 is saving show files in the .isf format, and is unable to load .zos format show files, this means your console is running out of date software. The show file format changed from .isf to .zos in ZerOS 7.9.8. The latest software for FLX S24 consoles is ZerOS 7.9.9, which can be downloaded from the link below...
https://zero88.com/zeros#download
Release notes are also available from this link, detailing the installation instructions.
Both .isf and .zos show files can be loaded into ZerOS 7.9.9.
If you have any questions let me know.
Edward
-
Hi Jean,
Welcome to the Zero 88 Forum.
32 minutes ago, Jean Iwanowski said:I just received my FLX console (zeros v.7.9.9). I still have quite a lot to learn/explore but I already am quite fond of it!
Really glad to hear you have just received your FLX console.
33 minutes ago, Jean Iwanowski said:After patching my fixtures (not sure if I used rig sync or not) I tried the various clear options. On several occasions (but not always) I noticed that when clicking on "Clear fixtures files " and then on "Reset desk" both the internal and external monitors turned grey and only a power cycle could bring the console back to normal operation. I guess this might be a bug in the software.
Sorry to hear this. This is not an issue we are aware of. Would you be able to email us a copy of the show file you were using when you experienced this? Our support address is support@zero88.com
35 minutes ago, Jean Iwanowski said:- When changing the type of a fixture, the user-defined name for that fixture is replaced by the library name of the fixture. This is a bit annoying since a common use case is changing the mode of the fixture, where one would expect the user-defined name to be preserved. Maybe an improvement for a future software version?
That is correct. Currently when you change a fixture, the replacement fixture will use the name of the new fixture, not the original custom name. The ability for replacement fixtures to use the original custom name is logged on our system as reference number ZOS-10745.
If you have any questions please let me know.
Edward
-
Hi Kevin,
23 minutes ago, kgallen said:Fantastic, thank you for the quick and thorough response!
No problem.
23 minutes ago, kgallen said:Specifically thanks for the detailed response on Q3 - I'm looking forward to some detail in this respect in the upcoming Macros webinar 🙂 [if not too cheeky a request, maybe you could include this one as a worked example 😉 ]
Yes good idea. We can use that as an example.
Edward
-
Hi Kevin,
ZerOS will recognise a remote switch "press" and "release". ZerOS only listens for the press, to trigger either a specific cue or a macro.
44 minutes ago, kgallen said:is it OK to keep the Remote Switch input "low" (shorted to common) for an extended period of time (many minutes)?
Keeping the remote switch "pressed" is fine. ZerOS will not register a "repeat" instruction and do something different.
45 minutes ago, kgallen said:Q2: Is the point (in time) of the remote switch release (effectively the "rising edge") irrelevant (other than needing to go high again at some point
Correct - potentially if we add the ability to map remote switches to front panel keys, we would listen to both the repeat and the release, but currently the release is ignored by ZerOS.
47 minutes ago, kgallen said:Q3: Can I make FLX sensitive to the Remote Switch input for specific cue "GO"s and ignore the Remote Switch input on other cues?
Remote Switches can either trigger a cue, or a macro. Therefore your Remote Switch could always trigger a single specific cue number, or it could trigger a go button press via a macro. If you wanted the remote switch to behave like the go button, but with the remote switch disabled at certain times, you could program a macro to enable/disable the remote input. This would simply consist of a series of arrow keys and enters, which takes you into Setup, enables/disables the option, and then exits Setup. This macro could then be triggered by the cue, prior to when you want to disable/enable the remote input.
54 minutes ago, kgallen said:- (a) Will the front panel "GO" button still work normally if a Remote Switch input that is also assigned to "GO" is still held "pressed" (Remote Switch input is still shorted to common, hence "logic low").
Yes - as the macro to press the go button will have already been triggered, the "repeat" and "release" of the remote switch will have no effect on the go button.
Hope this helps,
Edward
-
Hello,
FLX consoles currently do not support OSC commands. Available trigger methods are detailed here...
https://zero88.com/manuals/zeros/setup/triggers
If you have any questions let us know.
Edward
-
Hello,
2 hours ago, MihiGyver said:We use a LeapFrog 48 and i try to install ArtNet.
On the Desk is Version 7.9.9
First i try to connect it to ArtNetominator.
ZerOS consoles, including Leapfrog 48, will only send Art-Net DMX data, to Art-Net devices that report themselves as an Art-Net receiver. ArtNetominator does not report itself as an Art-Net receiver, and as such Leapfrog 48 will not transmit Art-Net DMX to it.
If you wish to test your network, you could use the demo Capture files on the link below, and use the Art-Net protocol...
https://zero88.com/manuals/zeros/networking/connecting-to-capture
Which Art-Net devices do you wish to control with the console?
If you have any questions let us know.
Edward
-
Hi Wosti,
The Fader Function options will affect the intensity behaviour, with attributes adhering to cue fade times.
Fader controls position, allows you to transfer from whatever position values your fixtures are currently at, to the position values recorded in the current cue you crossfade into. Therefore lowering the fader will send the fixtures back to their previous values. It can't be used as a method of transferring between the cues on the playback.
Therefore if you want to control the time of position crossfades between cues, you may wish to configure a Speed Override control to do this. For more information see the link below...
https://zero88.com/manuals/zeros/cues-playbacks/special-playback-functions
Hope this helps, if you have any questions let me know.
Edward
-
Hi Pete,
Hope you’re well.
2 hours ago, Peter6442peter said:My issue is when ever I push up a fader with memory on it the fixture snaps on at about 20percent
This sounds like the trigger level of the playback has been changed to 20%. To access this option, open the playback’s settings by holding SETUP and tapping the playback’s button. Then choose the Raise and Lower tab from the top. You will then be able to adjust the Trigger/Release level. The default is 5%, however if you want to access the full range of dimming you could adjust this to 1%. For more information on Raise and Lower, see here...
https://zero88.com/manuals/zeros/cues-playbacks/playback-settings/raise-and-lower
If this doesn’t solve the issue, it sounds like there may be a custom dimmer curve set on those fixtures.
2 hours ago, Peter6442peter said:and then fades up to full eg Red 100% Blue100% Green 100% White100% and then falls back to its programmed colour say Straw.
This will be due to the cue colour fade. To edit, view the playback the cue is programmed on by holding VIEW and tapping the playback’s button. Then tap on the colour time, which by default is 3 seconds. You can use the encoders to dial this to 0.
Hope this helps, if you have any questions let me know.
Edward
-
Hi Lloyd,
Welcome to the Zero 88 Forum.
14 hours ago, lightninglloyd said:ive downloaded the latest software for windows and the desk but just get a connection error
Please see the link below, containing information on using the Windows Remote application with FLX S24...
https://zero88.com/manuals/zeros/networking/using-the-remote-apps
If you wish to connect a laptop running ZerOS Monitor to the FLX S24, you will be able to use a single Ethernet cable between the two. Using this method, you will need to configure static IP addresses in range of one another, for both the FLX S24 and laptop running ZerOS Monitor. For more information on IP addressing, see the link below...
https://zero88.com/manuals/zeros/networking/ip-addressing
If you have any questions please let me know.
Edward
-
15 hours ago, Edward- Z88 said:
This is an issue we are aware of. In ZerOS 7.9.9, if you select a dimmer, and an LED RGB fixture together, RGB controls are unnecessarily duplicated on the encoders.
This is logged as reference number ZOS-10640 on our system.
Edward
-
Hi Peter,
31 minutes ago, Peter Wright said:However, when fading up any one of channels 1 to 16 the white colour option, inexplicably changed to red, and, in fact did control the red channel.
This is an issue we are aware of. In ZerOS 7.9.9, if you select a dimmer, and an LED RGB fixture together, RGB controls are unnecessarily duplicated on the encoders. Our software team have fixed this issue ready for the next release. If you would like access to this fix prior to the next software version is released, please drop me an email and I can share the beta software with you.
If you have any questions let me know.
Edward
-
Hi Romec,
17 hours ago, Romec said:-MOVE things instead of just copy it (pallets / cues)
This will be coming in a future update, and is already logged on our system. Currently you can only copy and then delete the original.
17 hours ago, Romec said:-controle the actual speed of a Fx on a submaster
You can do this using Speed Override. For more information see below...
https://zero88.com/manuals/zeros/cues-playbacks/special-playback-functions#override
17 hours ago, Romec said:maybe even have a executer window
Although there is no dedicated “executor” window, you can record snapshot palettes, to record whole lighting states. You could then view the palettes window and use this to recall lighting states for selected fixtures. For more information see here...
https://zero88.com/manuals/zeros/palettes/recording-palettes
Hope this helps, if you have any questions let us know.
Edward
-
14 minutes ago, kgallen said:
This looks like it's a wireless product, so will it work on inductive charging technology or is a powered USB hub required? If so is it USB-C compatible?
The amazing thing about it, is no power is required at all.
14 minutes ago, kgallen said:If you decide on a Mk2 revision, can I request storage slots for my minidiscs please?
An excellent idea. Logged as ZOS-0104.
Edward
-
Hi Daniel,
Welcome to the Zero 88 Forum.
4 hours ago, danielb said:I am missing all my and the standard effect palettes
1 hour ago, kgallen said:on the Effects page can you press "Create Auto Palettes"?
As Kevin mentions, after selecting your fixtures, go to the Effects window, and you will have a button to automatically create effects. Pressing this button will generate 45 effects for your fixtures. How many effects do you see after doing this?
If you have any questions let us know.
Edward
-
Dear All,
ZerOS Library 2.1 has now been released. This is available for ZerOS consoles running ZerOS 7.9.8 and later.
This release contains 23,831 fixtures.
ZerOS Library 2.1, along with further information, can be downloaded from the Library page below...
https://zero88.com/libraryFor installation instructions, see the link below...
https://zero88.com/manuals/zeros/patching/zeros-libraryLegacy Consoles
If your console cannot run ZerOS 7.9.8 software or later, individual fixture files that you require can be downloaded from the link below...
https://zero88.com/fixtures/legacy-consoles/Additional Fixtures
If the fixture you wish to control is missing from the latest library, see the link below...
https://zero88.com/library#supportIf you have any questions, please let us know.
Edward
-
Hi Peter,
45 minutes ago, Peter Wright said:but id the intensity playback is brought down to 0 and the colour(s) are left at full, fading the intensity back to full doesn't bring up the colour(s) without the fading the colour plyback(s) to 0 and then back up again.
That is correct. This is because by default, the playback will release when its fader is lowered, and will then trigger again when it is raised. As colour information by default mixes LTP between playbacks (latest takes precedence), raising your colour mix intensity playback, which has colour information at 0, becomes the most recent instruction to the fixture. The fixtures therefore go black. To avoid this, you can disable release on lower on your colour mix intensity playback. To do this hold SETUP, and tap the playback's button. From the playback settings choose Raise & Lower at the top, and then disable Release on Lower, and click OK. For more information see the link below...
https://zero88.com/manuals/zeros/cues-playbacks/playback-settings/raise-and-lower
47 minutes ago, Peter Wright said:is it correct that fade up of the intensity playback must precede fade up of colour playbacks for this to work?
It doesn't have to. As per my point above, if you have disabled release on lower, it won't "retrigger" when you raise its fader, allowing you to set a colour, and then raise the intensity over the top.
Hope this helps, if you have any questions let me know.
Edward
-
I have added a message to this page to help avoid confusion...
https://zero88.com/manuals/zeros/cues-playbacks/record-options
Edward
-
Hi Peter,
If you cannot see a SmartTag button in the Record Options window, this means that the console is in global Cue Only mode. See the link below for more information...
https://zero88.com/manuals/zeros/cues-playbacks/record-options/tracking#GlobalOptions
I hope this helps, if you have any questions let me know.
Edward
Potential bug / improvement suggestion
in FLX
Posted
Hi Jean,
I have checked, and "0181" is the ID of the S4 Lustr. Therefore RigSync has found one of these fixtures. Interestingly, RigSync seems to be detecting that the fixture is in "Mode 0", which obviously doesn't exist. This is why the fixture is appearing with its ID name, not the true text name. Were you going via your splitters at the time? If so it sounds like RigSync has managed to get some data over RDM, but not the full picture.
That is correct. RDM devices will report a UID, which in theory is not shared by any other fixture - a bit like a MAC address in the world of Ethernet and Wi-Fi.
If you patch fixtures manually, that are then discovered by RigSync, the console has no information to tell it that you chose to patch those fixtures manually, and therefore it sees them as new fixtures. This will likely result in the DMX address of your fixtures being changed by RigSync. This is because it will see they conflict with "other" fixtures in the console - the ones you patched manually - and so readdress them over RDM. This is where segregating your DMX network, and choosing to use or not use RDM for whole DMX lines is beneficial. This also helps with ensuring non-compliant fixtures won't be affected.
When in the Fixture Schedule, it is best to change the mode of a single type of fixture at a time. For more information see the link below...
https://zero88.com/manuals/zeros/patching/fixture-schedule/change-fixture
If the console discovers your RDM fixtures, and you decide for those particular fixtures you wish to patch them manually, you could delete the discovered fixtures in the Fixture Schedule. Doing this, will mean despite the console knowing they are still there on the DMX line, it will ignore them, and know you don't wish to use them. Resetting the console, would allow RigSync to patch those fixtures again. For more information see the link below...
https://zero88.com/manuals/zeros/setup/universes/remote-device-management
We do have an internal version of ZerOS software, which has a dedicated "RDM" tab within Setup for this log. Currently the information is very "raw", and not something we'd want to baffle a user with. Adding a nice RDM sniffer is definitely something we wish to add. This feature is logged as reference number ZOS-9042 on our system.
If you have any questions let me know.
Edward