Edward Z88
-
Posts
3,291 -
Joined
-
Last visited
-
Days Won
84
Posts posted by Edward Z88
-
-
3 hours ago, kgallen said:
@Edward Z88 Does this work on FLX too? (Shift key then keypad?). Thanks!
https://www.zero88.com/manuals/zeros/controlling-fixtures/parameters#syntax
-
1
-
-
1 hour ago, Oliver_74 said:
Hi,
is it possible to type in the pan/tilt values? Otherwise it’s pretty hard/impossible to set the same values using the encoder wheels
thank you 🙂
You can set specific percentages. To do this, hold Z/Shift and tap the Pan or Tilt label on the touchscreen. Then tap the Z/Shift key, and use the onscreen number pad to type in @ 25 ENTER. This would then take Pan or Tilt to 25%.
-
Dear All,
After over seven years, and over 3,000 forum posts, it is time for me to say farewell to my time at Zero 88 (now Vari-Lite). Working for Zero 88 has been a pleasure, and I have thoroughly enjoyed being part of this active group of forum members.
We were on ZerOS version 7.9.2 when I joined, and FLX S wasn't even around yet. Since then, ZerOS has come a long way, and is now more stable and feature-rich than ever. The ZerOS online manual, plus all the ZerOS training videos, mean that all aspects of ZerOS are now documented to enable users to get the most out of their consoles.
I want to say a massive public thank you to @Jon Hole. Over these years he has been a brilliant mentor and friend (and my manager for a period of time!), and was instrumental in me getting into my role at Zero 88 in the first place. Jon and I will of course keep in touch, and hopefully work together again some time in the future.
So, I'll type ENTER ENTER @ . RECORD ENTER, and record a fade to black on this chapter.
Thanks again to everyone. I really have enjoyed my role.
Edward
-
3
-
1
-
-
12 hours ago, Jean Iwanowski said:
I just sent you the photo. Thanks for your help!
Thank you for this. This confirms your FLX has the latest DMX circuitry.
If you wish to continue using RDM, the next thing to try is using an Art-Net to DMX/RDM gateway. If this works with these fixtures, this would confirm there was a compatibility issue between these fixtures and the FLX console's DMX ports.
-
13 hours ago, Jean Iwanowski said:
the ETC fixtures that seemingly announce themselves incorrectly.
I have never seen an ETC fixture with poor RDM implementation. They always seem to be very good. However, I have not personally tested High End Systems fixtures, which is I believe what the Ministar is.
13 hours ago, Jean Iwanowski said:What bothers me here is that I just linked the FLX and the fixture with a short DMX cable and terminated the line directly after the device. I do not see what could go wrong there. The cable could be damaged, or the cable/termination might have the wrong impedance, but they should not since they were sold as DMX compliant parts, and even then I am not sure it could have such an impact. In your experience, is such a cable problem probable? Otherwise either the fixture or the desk has a problem.
Try a different cable, but if that doesn't work either, sounds like cabling should be fine. We were running ZerOS 7.14.3 software at "PlugFest" this year. At "PlugFest", we perform rigorous interoperability tests with FLX S and a bunch of other equipment. FLX S performed incredibly well in these tests.
Please could you email me a photo of your console's serial number to support@zero88.com?
-
12 minutes ago, Jean Iwanowski said:
- faulty_minib.heic :how the fixture schedule looks after RDM detection of the Mini-B
- faulty_minib
Thank you for the show file. This suggests that this fixture is incorrectly reporting with the RDM Device Model ID of an Axcor Spot 300, but with a name of "MINI B SPOT". Therefore, the DMX map will be incorrect, as the fixture is telling the console it is an Axcor Spot 300 when it isn't.
13 minutes ago, Jean Iwanowski said:But as soon as I exit setup, another problem appears (see rdm_error.heic). I do not see how it can be related to the incorrectly announced fixture. Or does RDM communicate based on a device type, so the FLX tries to speak with an Axcor Spot 300 and the fixture does not answer since it actually is a Mini-B Spot?
This would suggest the console can only intermittently reach the fixture. Check that the DMX line is terminated, and ensure any DMX splitters are RDM compatible.
15 minutes ago, Jean Iwanowski said:Is it something you add in the library to make work with fixtures easier? If so, do you know if the Ministar will be added to the library soon?
This fixture will be included in a future ZerOS software update. I do not have a date for when this will be implemented. Please see this link, should you wish to create your own custom fixture file...
https://www.zero88.com/manuals/zeros/patching/add-fixtures/windows-fixture-editor
-
1 hour ago, Jean Iwanowski said:
There seems to be a problem when adding a Mini-B spot through RigSync : the device is recognized as Mini-B (name field in the Fixture Schedule screen) but the profile appears in red and is named something like "Axcor 300" (sorry, I do not have my FLX in front of me at the time of writing this message). The fixture then does not work at all. I tested this without any other device on the DMX line. When adding the fixture manually (RigSync disabled), everything works as expected.
Sounds there could be an issue with their RDM implementation. Please see this recent thread, for an in-depth description of what may be going on...
1 hour ago, Jean Iwanowski said:Anyways, my reseller advised me to lower the frequency on the DMX bus, which he said might help. Is this possible with the FLX? I could not find such a setting.
You can change the DMX Transmission to "Delta", which means the console will lower the DMX frame rate when values are not changing. This option can be found in Setup > Universes > DMX.
-
To do this, you would need to copy/move cue 10.5 to an empty playback, and then play back this cue along with cue 10. You could then press UPDATE, ensure SmartTag is enabled, and press GO, to merge the data
(On Orb, you could use LOAD syntax, to allow you to go into a cue and also load a cue into the programmer, to allow you to easily merge the data.)
-
1
-
-
Hello,
I'd recommend updating your console's software to ZerOS 7.14.3.
The latest software is ZerOS 7.14.3, which can be downloaded from the link below…
https://vari-lite.s3.eu-west-1.amazonaws.com/software-firmware/ZerOS-7.14.3.exe
Release notes listing software changes can be found on the ZerOS webpage…
https://www.vari-lite.com/global/products/zeros-software
Software updates completely wipe your console, so make sure you save a copy of your show file to a USB drive first if you need it. For information on saving your show file, please see the link below…
https://zero88.com/manuals/zeros/setup/save
Once you have backed up your show file, installation instructions can be found here…
https://zero88.com/manuals/zeros/setup/load/zeros-software
Once installed, you will be able to load your show file back into the console from a USB drive. For more information, please see the link below…
https://zero88.com/manuals/zeros/setup/load/zeros-show-files
I hope this information is helpful. If you have any questions regarding the software installation process, please let us know.
-
Hi @SKLSKL
4 hours ago, SKLSKL said:I've just got a PIXELpoint Batten and when I go to add the fixture there are 7 or 8 different ProLight Battens but not the pixelpoint. Is there one similar that I could use or does a new fixture need to be created for it?
I would recommend operating the Equinox PIXELpoint Battens in 120-channel mode. This will allow you to patch a "40-cell – 8-bit" RGB Multicell fixture, which can be found under the “Generic” manufacturer in Add Fixtures.
If you cannot find these generic multicell fixtures on your console, I would recommend updating your console’s software. If you would like installation instructions, please let me know.
Once you have patched this fixture, please watch the video below for more information on controlling multicell fixtures...
Please let us know if you have any questions.
-
Hi @EwenA
18 minutes ago, EwenA said:see attached show files for the other modes this fixture has.
Thanks very much for grabbing all of those. Please find the zip file attached, including each of the RDM modes for these fixtures...
Please extract the files and load each one in, and then plug in a fixture. It should be discovered and patched, and you should then be able to change its mode correctly.
I hope this helps. Please let me know if you have any questions.
-
Hi @EwenA
23 minutes ago, EwenA said:Any suggestions as to what is going on and how to resolve this so that rig sync is usable? Show file attached.
Thank you very much for attaching your show file.
This is interesting. These fixtures are reporting an RDM "Device Model ID", that does not match the RDM Device Model ID that is in our library. Therefore, when the console sees these fixtures, it thinks they must be different to the F2 FC fixtures already in the library. This is why you are seeing this behaviour:
23 minutes ago, EwenA said:If I patch them in manually and disable RDM everything works as expected. If I then enable RDM rig sync adds in two new fixtures with the total CLF2-FC, and updates the dmx address on the two units.
As the console cannot find a suitable fixture in the library with a matching RDM Device Model ID, the console is then creating a fixture personality automatically, based on the information it can obtain over RDM. These fixtures are only reporting a limited amount of information over RDM. For example, the fixtures are not telling the console what its parameters are doing. The console therefore has no way of knowing which parameter is intensity, or which parameter is red for example. This is why you are seeing this behaviour:
23 minutes ago, EwenA said:Rigsync patches them as a CLF2-FC, and does not give me control of the fixtures.
Your show file includes the RDM Device Model ID that your fixtures are actually reporting. I have therefore added this RDM information into the F2 FC fixture from the library, and then exported this fixture file, which can be found attached...
If you reset the console, load in this fixture file, and then connect your fixtures, the console should then automatically patch this correct fixture from the file, rather than attempt to create a basic fixture file over RDM. The only issue is this file only includes the RDM information for the personality the fixtures were in when you saved your show file. Therefore if you were to change your fixture's mode, it would report RDM information that the console cannot find a match for. The only way around this, would be to send me separate show files for each of the fixture's modes, where you have allowed the console to discover the fixture in each mode. I can then extract the RDM information from the show files for each mode, and then add these into fixture files, which you can then load in to your console. That way, the console will then know about the fixtures, irrespective of which mode they're in, and RigSync will then work seamlessly.
As you can see, things get complicated quite quickly with RDM. Ultimately this is all due to these fixtures reporting something different to the information that we have for them.
I hope this helps. Please let me know if you have any questions.
Edward
-
1 hour ago, kgallen said:
I suggest we request to @Edward Z88 for a copy of the correct set of schematics for your units.
I have emailed you both a link to the Rackmaster schematic.
-
Hi Brett,
In this situation I would have used the Output Window Preview function, or the Fixture Levels window, to work out which cue the movers were incorrectly recorded in.
Then, I would have gone into that cue, selected the fixtures, tapped HOME, tapped UPDATE, and in the Update Options window disabled "SmartTag", enabled "Track Forwards" and "Remove", and then tapped the playback's GO button.
Edward
-
Hi Brett,
Please tap the RECORD button to open the Record Options window. You should see a "SmartTag" button. You may wish to disable SmartTag, so that it has a blue stripe on its button. This will mean the console will only include parameters you have manually adjusted when recording/updating. Unchanged parameters, or parameters currently being controlled by other cues, will not be included when recording/updating. If SmartTag is enabled, the console will decide what does and what doesn't get included.
Edward
-
Welcome to the forum.
I have not personally had experience with converting MSC to OSC. However, another potential solution - could you contact the SFX6 team, and see whether OSC is on their road-map? You never know - they may be planning on implementing it soon, which would save you the time and effort of figuring out a protocol converter.
-
1
-
-
Hi @Speedy
Welcome to the forum.
To record custom Home, Default, or Max Level values, you will need to ensure that “SmartTag” is disabled in the record options.
If your custom Max Level values are not currently how you want them, first tap DELETE > HOME > Max Level.
Then double tap CLEAR, and set the fixtures you need to your desired maximum level. Then press and hold RECORD, and in the Record Options that open on the touchscreen, ensure SmartTag has a blue stripe, meaning disabled. If it has a red stripe, tap to disable. Then tap the HOME key, and then choose Max Level. Now only the lights you adjusted will be given a Max Level.
I hope this helps.
-
1
-
-
Hi Benjamin,
If these errors appear, and the console is switched off and on again, the console will usually reboot into the previously installed version. However as your console has booted into ZerOS 7.14.3, this confirms the software installation completed successfully. The installer must have encountered an issue right at the end whilst it was wrapping things up.
The only thing I’d check is going into Setup > Add Fixtures, to check the fixture library is installed. If it is, then you can ignore those errors.
Edward
-
3 hours ago, Niels-Oliver Harfst said:
Hi, thanks for the fast answer! Which of the numbers is the Serial number 😅?
Edit:
Nevermind, I think I got it.Thank you for emailing the photo of the console's serial number. We will be in touch.
-
Welcome to the forum.
Thank you for your description of the issue. The first thing to look at would be the internal touchscreen ribbon cable that plugs into the processor. This intermittent behavior could suggest the touchscreen is not connected correctly. Please email a photo of your console's serial number to support@zero88.com, and we can then confirm whether the console is in warranty. If it is out of warranty, we can provide instructions on how to open the console.
58 minutes ago, Niels-Oliver Harfst said:Is it possible to connect the console to an external regular monitor without a working screen
FLX S24 does not have an external monitor output.
Please let us know if you have any questions.
-
3 hours ago, Zulu said:
When I introduce the 2nd playback, I get a sudden jump to the new colour. The intention is to be able to cross fade manually from one colour to the other without a visible colour jump.
This should be a helpful one to watch...
3 hours ago, Zulu said:How do I clear the desk of everything except the patching, to start a new show?
Setup > Clear Options > Clear All will clear all programming, but leave all of your settings and patch.
Setup > Clear Options > Reset Desk will clear the patch and most settings, but will leave any network protocols enabled and configured.
Often the best option is load the "Setup Only", of a show file where you know the settings are how you'd like them...
ZerOS Show Files - ZerOS | Zero 88
Please let me know if you have any questions.
-
Bonjour,
Si vous avez enregistré des positions sur un fader de lecture, vous constaterez peut-être que les appareils se déplacent vers leur position lorsque vous augmentez le fader de lecture. Pour éviter de voir ce mouvement, maintenez SETUP et appuyez sur le bouton de votre lecture pour ouvrir les paramètres de lecture. Ici, définissez la « Fonction du bouton » sur « Go (Snap) », plutôt que sur Flash. Cliquez ensuite sur OK. Maintenant, vous pouvez appuyer sur le bouton de lecture pour préparer les appareils, puis augmenter le fader de lecture pour activer l'intensité.
J'espère que ça aide.
Hello,
If you have recorded positions onto a playback fader, you may find you see the fixtures moving to their position upon raising the playback fader. To avoid seeing this movement, hold SETUP and tap your playback's button, to open the playback's settings. In here, set the "Button Function" to "Go (Snap)", rather than flash. Then click OK. Now, you can tap the playback's button to prepare the fixtures, and then raise the playback's fader to turn on the intensity.
I hope this helps.
-
1
-
-
Hi @delicolor
12 hours ago, delicolor said:I sent something to Support@zero88.com on Wednesday and didn't hear anything back. Has it changed or is it a domain hiccup?
support@zero88.com is still valid and comes through to me and the rest of the team. I’ve been on holiday without access to my emails. I’m back next week.
-
Hi All,
Apologies for the confusion here. Group/palette syntax isn’t available on Solution consoles. Keys such as GROUP purely change the MFKs, and do not bring the function onto the command line.
You therefore cannot delete/copy/move multiple Groups or Effects in one operation.
ZerOS 7.14.3 Released and ZerOS 7.15 Coming Soon!
in News & Announcements
Posted
Ah that’s a shame - I must have missed you. I was there all day Monday too in a personal capacity.