Jump to content
Zero 88 Community Support Forum

All Activity

This stream auto-updates

  1. Yesterday
  2. Hi @Kauz In all my time @ Zero 88, I don't think anyone has actually asked how to do this! But, this is a very good question. Triggering a chase will always set it to full. Releasing a chase will always turn it off. Releasing therefore won't help you in this situation if you want the chase to dim to a certain level. If you don't want to simply move the chase's fader down manually, you could automate this by recording yourself an "inhibit" playback. You could then trigger the inhibit playback in a cue in the Master Playback, as a way of scaling the fixtures used in the chase playback. If you'd like instructions on how to do this, please let me know.
  3. Last week
  4. Hi, I created an intensity chase which I trigger from the Master Playback cue stack. With the next Master Playback Cue I would like to fade this chase down to (e. g.) 30 % during (e. g.) 60 seconds, as if I would move the chases's fader from 100 % down to 30 % and leave it there. The only related information I found in the manual was However, after the fade I would like to keep the chase running with intensity at 30 % (relative to the intensities given by the chase). Is there a way to do this?
  5. @AlRamsay - there isn't a voltage regulator for the output rails per se - the voltage is derived from a D to A convertor that feeds an op amp (IC39) who's output voltage is set by a small resistor network selected by the output voltage selector link. The op amp is supplied from one of the internal 5v rails which is regulated by a conventional voltage regulator that's located near the battery, the 5v rail will need checking. There's a possibility that the battery has leaked at some point & whilst the initial corrosion as cleaned - some of the battery chemicals have run along the PCB tracks & damaged them - I've repaired a couple of Sirius with similar corrosion issues, the stuff can spread like crazy. You're going to need a schematic to fault find and I'm happy to send you one but I won't post it here - if you'd like to eMail me ian at serviceguy.co.uk then I'll send you a copy.
  6. Earlier
  7. Hi, I've got a Sirius 24 that is not outputting the correct voltage at the analogue output. On a working desk, I am reading 0.23V-10.08V on the analogue output. On the faulty desk, I am reading 0.82V-2.80V, this is also reflected in the output LED being significantly dimmer than it should be at full output. This fault is common to all channels on the desk. Can you give me any guidance on how the output voltage is derived, is there a voltage regulator I should be looking at? Kind regards Alasdair
  8. Bonjour Eric. Oui je travaille dans le theatre. Jusqu'a present je travaillais avec dlight, qui fonctionne tres bien. J'ai eu envie de prendre quelque chose de plus rapide et qui pourrais faire du live (concert). Je vais essayer de comprendre le fonctionnement de la console. A bientot
  9. It sounds like everything is configured on your console. Please go to Z/Shift -> System Information -> Desk Info, and take a picture of this screen. Please then email this to support@zero88.com, and we can take a look.
  10. Yes - all the cables are correct - I've used a 2nd set too, also tested. Also 2nd lighting desk to provide input and various lamps etc to test output, but still nothing on the Z -DMX input screen either. Lost count on how many times I've rebooted. FAV test B Sept2023.zos
  11. Manually tapping the palettes used in the cue at the top of the Update Options, is the same as clicking "Update References", but "Update References" is essentially the shortcut to allow the console to automatically update the palettes that are used in the current cue. That is correct - "Remove" cares about tagged parameters, not selected fixtures. You can't use SmartTag in conjunction with "Remove". UI improvements are covered in ZOS-5728... You won't see what we call the "Parameter Table" on the internal touchscreen. See the link below for more information... https://www.zero88.com/manuals/zeros/desktops-windows/output-window It certainly isn't impossible! Thanks once again for your time - it really is appreciated.
  12. Thanks for the responses Edward. Point taken about the console being better/easier with an external monitor -- I was a bit limited by what the venue had available (unless I wanted to press into our hire budget for one, and the sound department had already eaten most of that). I'll certainly be looking back at this thread next time I use a FLX to remind myself. I tend to use whatever's in the venue, so currently I'm not sure when I'll next encounter one, but when I do I'll be prepared That makes sense, but in that case what happens if I select both the palette and the cue in the top of the update dialog? I figured that doing that was the way to achieve this functionality -- does that do something different? Ah, it was the record without smarttag -> paused feature that I was not understanding. Yeah that makes total sense -- I am not sure why it was confusing me. Maybe because pressing it caused a screen transition (i.e. showing the groups on screen), so in my mind it wanted to be by the screen! From this (and the manual page), I think I understand that: "Remove" in the Update dialog always only applies to tagged parameters; there's no way to apply it to selected fixtures other than by using something like Home to tag all the parameters. Is that correct? Also, all your examples were done with smart tag disabled. Does Remove ever do anything when smart tag is enabled? If not, could you maybe grey out the Remove button when smart tag is enabled in the update dialog? It was displaying parameter info for selected fixtures on the internal touchscreen I think (unless I'm misremembering and that only happened in Phantom ZerOS where I was using a virtual external monitor). That was useful, but I'd still like a mode to see the info inline for all fixtures. That would have been marginally quicker; I was selecting the fade time, hitting enter, typing a new time, hitting enter again. Orb had a Time key, right? I think Orb would have been closer to my ideal console than FLX is. Any plans to release a more syntax focussed ZerOS console in the future? (I know, no comments on future products!) But given that ZerOS must support the concept of a Time key, you could maybe add it to the things you can make the UDKs do on FLX? I'll consider this for next time. I guess I just figured it's such a useful window, I expected most people to want instant access to it!
  13. I've removed your show file from your original post, so this may have freed up enough storage for you to post your new show file. Please can you confirm your male to male DMX cable is wired correctly?
  14. Ah yes - I'd been temporarily checking that signal was still flowing through the ports even if in the wrong direction. I've redone the file, but this now takes it above the limit of file size I can send you
  15. Thank you for attaching your show file. I loaded your show file into ZerOS, and both DMX Ports are configured as DMX Out: If you would like DMX port 2 to be your DMX Input, choose "DMX In" under DMX 2.
  16. Hi Mark, loading that show file in and the DMX 2 port appears to be still be set to DMX out.
  17. I am using Port 2 (3-pin) for the input which will make plugging up for the coming show easier. Everything you say is what I am expecting, but still nothing happening. I've rebooted twice. Running v 7.14. Still no joy 😞 FAV test Sept2023.zos
  18. Hi @Mark Alington Please confirm you have chosen which DMX port you wish to use as your DMX Input, as per the link below... https://www.zero88.com/manuals/zeros/setup/universes/dmx-2#in Once you have configured your DMX input port, you should be able to exit Setup, and tap Z/Shift -> System Information -> DMX Outputs -> DMX In, and see the levels of the incoming DMX signal on your configured DMX port. Please let me know if you have any questions.
  19. Hi @Amy Worrall Glad you survived! Thank you very much for taking the time to leave this feedback. My responses below: FLX is easier to use with an external monitor. If you don't have a physical external monitor, you could turn a Windows PC or an iPad into one by connecting them to the console's network, and run the ZerOS Monitor apps. It is possible to record yourself a macro to get back to the Output window, which could then be put on a UDK. If you'd like information on this let me know. We also want to make various improvements to the FLX touchscreen, to bring it more inline with FLX S. In Setup -> Settings -> Record & Update, you can configure the Record & Update Options to always appear on the internal touchscreen when RECORD or UPDATE are pressed. This is a great suggestion. I have logged this on our system as reference number ZOS-3600. ZerOS uses the command line as its Undo history, allowing you to undo selection/control changes. With fixtures selected, a single press of the CLEAR key will clear selection, and clear the command line, leaving programmer values as they are. None of our current ZerOS consoles feature a TIME key - this is something you will only find on our Neo X consoles. To quickly increment/decrement a fade time value on FLX, tap on the fade time, and then hold SHIFT and use the Up/Down arrow keys. Brilliant - glad to hear it. Feature suggestion logged as ZOS-5952 on the system. I have made a note of your request. That is correct - FLX will only ever have the current show file stored on it, and it auto-saves after every change you make when outside of Setup. Setup -> Save is a bit like "Save As" - that's where you go and initially save your show file to a USB drive. Z -> Save Show, is a way of quickly saving a new revision of the show file to a USB drive - with the console simply adding an incremental number to the end of the show name. There is no "programming undo". To undo what you've described above, the only option would be to load in an earlier revision of the show file from a USB drive. This is why regularly tapping Z -> Save Show is best practice. Yes - to do this hold SETUP and tap the key of the attribute you are working in, for example SETUP+COLOUR. You can then change the encoders to Coarse/Fine, or simply adjust the encoder sensitivity. On ZerOS, you can open an equivalent of this window in table form in the Output window on the external monitor, by selecting the fixtures you'd like to view. There is too much information to display this nicely on the internal touchscreen. Great 🙂 Update Options window UI enhancements logged as ZOS-5728. This is described here... https://www.zero88.com/manuals/zeros/cues-playbacks/updating-cues/update-options#references The console uses the logic that if you have manually adjusted parameters, breaking the palette reference, and are about to update the cue, you have deliberately chosen to break that reference. However, if you wish to reinstate the reference, you can enable "Update References". This is described here... https://www.zero88.com/manuals/zeros/cues-playbacks/updating-cues/update-options#remove To remove an entire fixture from the current cue, select the fixture(s), tap HOME > UPDATE > Remove > ENTER. This can only be done with SmartTag disabled. To remove a fixture's attribute from the current cue, select the fixture(s), hold CLEAR and tap the attribute you wish to remove (CLEAR+COLOUR) > UPDATE > Remove > ENTER. This can only be done with SmartTag disabled. To remove an individual parameter, select the fixture(s), tap the attribute key to access the parameter (COLOUR), tap the parameter on the touchscreen to tag it, so that it goes blue on the encoders, UPDATE > Remove > ENTER. This can only be done with SmartTag disabled. Our old "Orb" series consoles have the "Fixture Levels" window. Bringing this to FLX could be interesting. The main reason the GROUP key is not alongside the attribute keys, is so that you can very easily use the GROUP key in syntax - GROUP 1 @ 75 ENTER Nice 👍 There is - tap Z and then enable Programmer Time on the fourth encoder wheel - this fade time will then be used by CLEAR CLEAR. This is a great suggestion. Logged as reference number ZOS-8097. To reduce the currently selected fixtures by 50%, type @, and then hold SHIFT and tap the Down arrow key, and then type 50 ENTER. @ -50 will be typed into the command line. You can also use SHIFT and Up arrow to access @ + syntax. More information here... https://www.zero88.com/manuals/zeros/selection-and-intensity/commands#scaling Upon booting FLX, it will always set the internal Grand Master level to full, irrespective of the fader position. The Grand Master fader can regain control of the Grand Master by taking the Grand Master fader to full. If the Master Playback is currently paused, only a single press of PAUSE is required to Go Back. The Pause button will be flashing if the Master Playback is currently paused. If it isn't flashing, two presses will be required to Go Back. Bear in mind, if you record a cue without SmartTag, the Master Playback will be in a paused state - the theory being you have just snapped into the cue you just recorded, ignoring fade times. Hold SETUP and tap the Master Playback's GO button, to open the Master Playback's Settings. Choose Raise and Lower, and set Release On Lower to disabled. To clear a whole fixture, you can use the "Clear Fixture" command. To access this, hold SETUP and tap an empty UDK. From the dropdown, choose Clear Fixture, and click OK. Now, select a fixture, and tap your Clear Fixture UDK, and the values of this fixture will be cleared. Thanks once again for taking the time to write up this feedback. Please let us know if you have any questions.
  20. Hi - I have followed all the guidance on the manual pages https://www.zero88.com/manuals/zeros/setup/triggers/dmx-in-2 I am still not getting any readings on DMX input even though all the options on the desk match all in the instructions. I know earlier software versions did not allow DMX in for FLX S24, but I was really looking forward to using this. Should I be getting a signal?
  21. This is really important feedback @Amy Worrall, thanks for taking the time to capture it all!
  22. Well, I survived! First night was yesterday. With very little time in the venue and no tech run (gotta love amateur theatre), I'm glad I prepared myself by getting help from you guys If anyone's interested, here's some thoughts: I was using a FLX without a monitor. A few things were annoying because of that: having to use shift+view to get the output window, as opposed to having it as one of the things that View will cycle through. (I constantly wanted to swap between the cue list and the output window, and I pretty much never cared about the fader display -- LX tape was sufficient to label my faders!). I didn't like how you had to press and hold record or update to get the record options, and when you did, you couldn't see the command line. I frequently wanted to issue the command "record cue N", where N was the number of an existing cue I was replacing, and to also specify tracking mode or some other record options. I wish that the current and next cue numbers were persistently displayed somehow, even when e.g. looking at the outputs window or a set of palettes. Maybe they could go on one end of the command line? I wasn't so keen on how the command line just fills up with multiple unrelated things. For those that don't know Eos, it clears the command line after each command is finished -- Eos maintains selection separately to the command line, so clearing the command line doesn't lose your selection. This wasn't too big a deal, I did get used to it. I really really really missed having a Time key. On Eos, to edit the time of the cue you're in, you can just type "Time 3 <enter>", or for a different cue, "Cue 6 time 3 <enter>". Time entry by navigating with the arrow keys on the cue list was probably my biggest slowdown. I loved the auto colour and gobo palettes feature. They saved loads of time. I did record a few "everything" palettes (e.g. having intensity, colour, position etc in just one palette, aka Eos Presets). They worked fine -- I put them under Colour, fairly arbitrarily. I think it'd be more understandable having a separate home for them, but this was fine. Am I correct that the desk only holds one show file at once, and auto-saves? I was very confused about whether the Save option through Setup, and the save option through the Z key, did the same thing as each other and whether they always saved to USB. Is there an Undo? I couldn't find one. Would have helped a lot when i replaced colour palette 8 instead of position palette 8! Is there a way to swap the encoders from fine to coarse mode? They were scrolling very slowly for me. Probably a small thing, but I missed Eos's "expanded" output tile view, where every parameter of every light was visible. (I'd want it as an option, since it would drastically increase scrolling!) I liked how Zeros displayed the fixture types above the output window items (And that I could name my dimmers and those names would appear there.) The Update button: It was great to show all the possible things that could be updated, but the tap targets were very small! It wasn't immediately clear to me what "also update references" did -- was it so that if I changed a palette it would update the cues that referred to the palette? If so, when would you ever _not_ want that? I think I mostly grokked how to remove things from cues (via update->remove), but I still wasn't perfectly clear. There was a toggle for Smart Tag in the update dialog, but I wish there was also the toggles for selected vs tagged, and all params vs tagged params. I wasn't sure how to specify "remove this entire fixture" vs "remove this parameter of this fixture", and I didn't grok what smart tag remove would even do. I know you guys explained it to me, it just hasn't quite sunk in! I still miss the Eos Blind Spreadsheet though. The ability to see precisely which move instructions are in any [cue, palette, preset, submaster, etc], with blank spaces where no instructions are found… and an easy press of "at enter" once you targetted the thing you don't want, and you get instant feedback by seeing the number go away… Minor nitpick, but I kept wanting the Groups key to be near the Color/Pos/Beam/etc keys. I'm not actually sure why, since on Eos they're nowhere near each other either. Playbacks were pretty intuitive. I managed to set one up that did LTP mixing of intensity params, and it worked fine. Clear-clear to remove manual values was fine. I wish there was an option to remove them with a fade, aka Eos "Sneak"… if there had been, I'd have used syntax to modify lights during the live show, knowing that I could put them back when I wanted without the audience noticing. Patching was fine. I liked the <channel> <at> <address> syntax for updating DMX addresses. I wish that if you typed that into the patch window for a non-existent channel, it'd get created automatically. As you've probably guessed, I'm very syntax focussed (I see faders etc as shortcuts, not as my primary interface to the console). My personal preference would be for ZerOS to allow all consoles to use all bits of syntax, even ones they don't have hard keys for (e.g. the Time button, which apparently existed on an earlier console!). Then, there could be a way (shortcut button, dedicated key on future hardware, reprogrammed UDK etc) to put a "complete" keypad onto the touchscreen, just like Eos does when running in Nomad. This would also have the benefit that Phantom ZerOS could have a console independent mode, that didn't show a facepanel, just the equivalent of one or two monitors, and this Keypad button got you access to all the inputs you need! It should also be obvious that I'd like to see a future ZerOS console that had an even more expanded syntax keypad than the FLX. I missed the Eos "%+" and "%-" buttons. I liked having easy access to make a bunch of lights brighter/dimmer all at once. (I didn't try using an intensity encoder on ZerOS though -- I know you can lock that on if you want, but I didn't get time to see if it would have been an intuitive workflow for me.) We ran into an odd bug where the grand master was down but the desk ignored the fact. Once we moved it to the top, it started working normally again. I didn't quite get the logic of when the "pause" button would immediately do a "back" action, vs which situations pressing it once would cause it to flash and you had to press it a second time to go back. I would have expected the latter to only happen during a fade… but actually it happened _most_ of the time, but not all -- sometimes a single press of pause _did_ go back. I was bitten a couple of times by the fact that bringing the master fader down released the cue list and reset it to cue 1. I was trying to edit some moving light positions, and I went to the relevant cue, then brought the master fader down so as to see what I was doing (with manual values in the movers in question)… but it released the cue and I had to start over. I solved my issue by only bringing it down to 10%… How do you "clear" (aka release/sneak) just _some_ manual values? I know you could do it by manipulating the command line, but suppose my command line was ages long. This was definitely a workflow I missed -- often, I'd bring intensities down on some other lights while I was editing the ones I cared about, then I wanted to clear that intensity reduction but keep my other changes ready to update into the current cue. I miss my "@ enter"!
  23. Hi Pete, Great - glad you were able to figure it out. In Setup -> Add Fixtures -> Next -> Universe Preview, you can see which DMX channels are patched vs available on each universe. In Z/Shift -> System Properties -> DMX Outputs, you can see the raw DMX output on each universe. Hope this helps.
  24. Je suis heureux d'apprendre que vous avez de nouveau mis à jour le logiciel ZerOS 7.14. Non : d'après votre description, il n'y a eu aucun problème avec votre précédente installation du logiciel. Il y avait simplement un problème avec votre fichier d'émission d'origine. Encore une fois, maintenant que cela a été corrigé, vous ne rencontrerez plus le problème avec la fonction de fader « inconnu ». Pleased to hear you have updated to ZerOS 7.14 software again. No - based on your description, there were no issues with your previous software installation. There was purely an issue with your original show file. Again, now this has been corrected, you won't encounter the issue with the "unknown" fader function.
  25. Hi Ed Alls well the Node hasn't got a name but for some reason the dmx 1 port was 0 then dmx port 2 and so on so has to re configure on pc. Also the Node wouldn't work with DHCP but would with the addresses 2xxx. Anyway finally got it working. Thanks anyway. One thing where do I find the dmx grid for each universe. Pete
  26. Hi Pete, What Ethernet to DMX gateway (“node”) are you using? What protocol are you using? sACN or Art-Net? What IP addresses are you using? How is the gateway connected to the console? Direct, or via an Ethernet switch as part of a larger network? Once you have patched fixtures onto a Desk Universe, you can then choose how those universes are routed from the console. In Setup -> Universes, the top-half allows you to choose which protocols you’re using. Then, scroll down to a Desk Universe, and you can then choose how that universe is sent. For example, which DMX port, which protocol universe? The Ethernet to DMX gateway will be able to send any protocol universe from each port, so you need to configure the Ethernet to DMX gateway to tell it which protocol universes you want it to receive and send from each port. Hope this helps.
  1. Load more activity
  • 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.