Jump to content
Vari-Lite Controls Support Forum

Edward Z88

Vari-Lite Admin
  • Posts

    3,228
  • Joined

  • Last visited

  • Days Won

    74

Everything posted by Edward Z88

  1. Hi @DALX Yes - if RigSync is enabled, and ZerOS discovers a fixture, it will first see if there is a fixture in the library with a matching ID. If there is, it will patch this. In the Fixture Schedule, you can then tap on the discovered fixture in the Change All Fixtures column, to view the fixture's DMX map. If there is not a fixture in the library with a matching ID, ZerOS will then ask the fixture what parameters it has, and automatically create a fixture file based on this data. Again, you can then view the fixture's DMX map in the Fixture Schedule. Note - many fixtures that support RDM, do not report their parameter information. In these cases, you will just see "Channel 1", "Channel 2", etc listed, as the console is not being told what parameter does what. When RigSync discovers a fixture, it will always add it into the patch. ZerOS will never "link" a fixture it discovers, to one that is already patched. Yes - a single fixture on the console can have multiple DMX start addresses, so that you can control multiple identical fixtures that are on different DMX addresses simultaneously. Please see the link below for more information... https://www.zero88.com/manuals/zeros/patching/fixture-schedule/edit-dmx-address Hope this helps,
  2. I don't have a personal licence for Capture, so don't have a Capture project for this one.
  3. The 36-channel mode of this fixture is a multicell mode. Please watch the tutorial below for information on controlling multicell fixtures on FLX S... Hope this helps.
  4. In case its of interest, here's the latest revision of the show file... Grease End Of Dress.zos My random tip for the day, which you may already know: Let's say you're currently in cue 9, and you need to make a cue 10, that is only slightly different. So, you make your tweaks, and are about to record cue 10. The director/lighting designer then asks you to quickly show the difference between this new state and cue 9, to check there's enough/not too make change. If you CLEAR CLEAR to reveal cue 9, you have obviously lost all your tweaks. For this, I like to use a "Clear Fixture" UDK. Select everything (1 THRU ENTER), and tap your Clear Fixture UDK. This clears all fixtures, allowing the current cues to play back, revealing cue 9. The nice thing is, that Clear Fixture can be backspaced. So backspace to undo, and you are then back in your proposed cue 10, ready to record/tweak. Apologies to @Uriahdemon for going off-topic!
  5. I think this is all totally valid. These are cases where SmartTag is a nuisance, but, as you say, changing the SmartTag logic here means it is no longer consistent. This is something we are working through internally. Personally, I very rarely program with SmartTag enabled. The only time I'll enable it is if I want to update a cue to remove attribute values for fixtures @ 0%, for example, to allow Move On Dark to take affect. Which is easy: Go into the cue > UPDATE > SmartTag > ENTER.
  6. Yep, Kevin's got the answer to this one... By default when you apply a palette, it instantly snaps onto the fixtures. Effect palettes operate in exactly the same way. "Programmer Time" can be used to add a transition fade time upon applying effect palettes. I'm currently programming & operating for Grease at my local theatre (250 cues plotted so far over 3 universes). I've found it really helpful to play with the balance between the base intensity, and the Size of intensity effects. For example, let's say I want to use a Smooth effect, and I want the fixtures to fade from 0% to 50%. If I apply the Smooth effect palette, my fixtures by default go from 0 to 100%, due to the Smooth effect palette's default midpoint of 50%. So, the first step is to reduce the intensity. If I set my fixture's intensity to 0%, keeping the size @ 100, this will result in my fixtures going from +50% to -50%. If you were to record this into a cue, you would be actually recording the fixtures @ 0%, which is why you see yellow intensity percentages in the Output window for this special case. But, you might not want your fixtures to be off for half the duration of the effect. So, I could set my fixtures to 12%, and then reduce size to 75. So now, my fixtures are fading from "-25%" to +50%. Of course, in terms of output, the fixtures are @ 0 from 0% thru -25% thru 0%, but it means you can decide the duration you want the fixtures to be off. This example would therefore still give a smooth intensity output from 0% to 50%, but with a different appearance to simply setting my fixture's intensity to 0%, and keeping Size @ 100. You can then tweak the base intensity level and size further to get what you want.
  7. Hi @Ian_p In Add Fixtures, we are aware of an issue where if you tap into the DMX address field, and then click "Back" to go back to the library, this can result in a crash. This will be fixed in ZerOS 7.14.
  8. When it comes to deleting, it is always best practice to err on the side of caution! When outside of Setup, it doesn't matter which window is shown on the internal touchscreen when you tap DELETE. After tapping delete, you then choose what you want to get rid of. To get rid of a group/palette/macro, tap DELETE, and then tap the item on the touchscreen. To delete a playback or UDK, tap DELETE, and tap the playback or UDK's button. To delete a cue, tap DELETE, type the cue number, and then tap the button of the playback you wish to remove the cue from. When in Setup > Fixture Schedule, the DELETE behaviour is reversed - you first select the fixtures you wish to remove, then tap DELETE, then confirm. Any fixtures with LEDs lit below their channel faders, will be deleted if you confirm the delete operation. https://www.zero88.com/manuals/zeros/patching/fixture-schedule/deleting-fixtures The next software update (ZerOS 7.14) should help improve this (the next beta version will include these enhancements, reference number ZOS-8853). Hope this helps,
  9. To "replace" your existing fixtures with your new fixtures, you can use "Change Fixtures" in the Fixture Schedule... https://www.zero88.com/manuals/zeros/patching/fixture-schedule/change-fixture To "add" the new fixtures into your programming, you'll need to manually add them into your cues.
  10. Hi @Uriahdemon When you record a cue, the console does not know what groups were used to select the fixtures. Groups can therefore be updated, without worrying about changing recorded cues. Are these new fixtures, that need to behave identically to an existing fixture of the same type? If so, your easiest option is to simply add an additional DMX address in the Fixture Schedule to the fixture that has already been patched. Then, the new fixture will be sent the same data as the original fixture. If the additional fixtures are patched with their own fixture numbers, then they will need to manually be added into the required cues. If the additional fixtures are the same type as existing fixtures, this may help you... https://www.zero88.com/manuals/zeros/palettes/advanced-palettes Hope this helps.
  11. Good evening Mac, If your intensity playbacks are sending your fixture’s attributes to defaults, this suggests the fixture’s defaults have been included in the cue. It is probably easiest to remake your intensity playbacks and overwrite them. First, make sure you double tap CLEAR. Then, select your fixtures, and tap @@. You definitely don’t want to press HOME - this will tag everything. Once the fixtures are on, tap RECORD, and best practice would be to ensure SmartTag is disabled in the Record Options. Then tap your playback’s button to store it. Double tap CLEAR, and then give your playback a try. Hope this helps.
  12. Hi Lewis, What version of ZerOS software are you running on your Orb console? To confirm the current software version running on your console, please click the “Other Windows” button, found top left of the Output Window. From the drop-down choose System Info. In the window that opens will be a line of text displaying the “Software Version”. The ZerOS Remote and ZerOS Monitor apps require the console to be running ZerOS 7.9.4 software or later. Let us know if you have any questions.
  13. Please click the link below to download the fixture file for the Equinox Waterwave XP... https://www.zero88.com/fixtures/legacy-library/Legacy library (gft41.0)/EQUINOX/Waterwave XP.ift
  14. Hi @Zulu @kgallen is correct - Spice dimmers do not have RDM functionality. I would therefore recommend ensuring RigSync is disabled on your console, prior to connecting DMX.
  15. If you raise playback faders, you can simply tap RECORD, and then tap the button below the playback you wish to store your scene onto. You can then lower your playback faders, and recall your scene using the playback you just recorded onto. As @kgallen mentioned, you will need to ensure SmartTag is enabled in the Record Options to capture other playbacks into cues, however SmartTag should be on by default.
  16. I've added this tip here... https://www.zero88.com/manuals/zeros/patching/fixture-schedule
  17. Hi @DALX In the Fixture Schedule, tap on the fixture in the "Change All Fixtures / Modes" column. The current mode will then be highlighted. Click Cancel to close. Hope this helps.
  18. Hi @discover Firstly, apologies if I have misunderstood your query. Would you like to operate your show, by mixing different combinations of cues together on the fly? If so, each of your cues will need to be programmed onto separate playback faders. In your example above, you would therefore end up with 9 playbacks - one for each cue. You could then raise the combination of playback faders you need to create your scene. If you wanted to, you could then record the combination of playbacks into a cue on the master playback. Hope this helps. Let us know if you have any questions.
  19. Excellent! Pleased to hear your touchscreen is up and running again.
  20. Apologies if you've already tried this - have you tried a different USB-A to USB-B cable?
  21. I'm not really sure what to suggest - there aren't any touchscreen compatibility issues affecting FLX between ZerOS 7.11 - 7.13. Could it be as simple as an intermittent USB cable connecting the touchscreen? When the touchscreen stops responding, is this always after having used the touchscreen with another device for example, or does it "randomly" stop responding? Has it worked at all with ZerOS 7.13?
  22. Hi @Petera - thanks for the update, really pleased to hear it.
  23. Shhh... https://common.zero88.com/a-z
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.