Jump to content
Zero 88 Community Support Forum


  • Content Count

  • Joined

  • Last visited

  1. Correction: I misread your reply and didn't realise you have to press RECORD and then EFFECT before selecting the effect palette. However, would it be possible to revise this functionality so pressing the EFFECT key is not required? It seems like an unnecessary step when you can select the effect palette directly via the window.
  2. This is exactly the behaviour I am not experiencing, as it seems the green filters are completely ignored when recording a palette. I will upload a video shortly to demonstrate the issue. Would it also be possible for me to gain access to any public/private beta (if you have one)? Do you have any sort of roadmap for future features? I'd love to be able to flesh out this platform some more!
  3. Hi Edward, I edited my reply -- that was indeed the problem. However it is still incredibly frustrating that you have to save the palette via the command line, I don't quite understand why you can't simply tap on the palette or use an MFK to store the attributes. I am near certain this used to be possible on older versions of ZerOS. Thanks
  4. I do the following: - load the effect into the programmer - set the intensity to 50 - press record* - set "Intensity" and "Effect" to green - Type "48" (for example) and hit enter The effect is again stored in an effect palette, but the tagged attributes still aren't stored. The only time any other attributes are stored is via the snapshot function, and this will store them when using the effects palette window as opposed to command line syntax. This seems like really inconsistent behaviour (snapshot + click will save attributes but record + click will not) and I'm near certain this is a bug and should be treated as so. I'm happy to upload a short video to demonstrate the issue if that would be useful. Edit*: If I press RECORD and then the EFFECT key and type the number it then does store correctly -- however it would still be incredibly useful to just be able to click a palette -- I'm sure this used to work and that would be far simpler than this weird workaround.
  5. Hi, If I assign the Speed Override function to a fader, and then run an effect either via a playback or directly from the programmer, adjusting the fader seems to make no change to the speed of the running effect. I have also tried setting "Fader Controls: Effect" on the playback, this seems to make no change. It's worth noting that setting a fader to a grand master control does work, so it seems strictly related to the Speed Override function.
  6. I also have a fairly large show on Friday so if this could be fixed by then (or I could get access to the beta versions?) that would be highly appreciated.
  7. When using a fully intelligent rig it is typical not to have any fixtures assigned to the 48 channel faders on the desk. It would be HUGELY beneficial to be able to use these 48 faders as playbacks. I personally believe this would greatly open up the functionality of the desk to a significant degree, as it's quite difficult to build up complex looks across an array of fixtures when you only can access 10 playbacks at a time (or 20-30 depending on how dextrous you are managing playbacks across multiple pages). It's possible to do this on Avolites desks (for example) and this fairly simple change would make the Solution much more capable for operating live shows. Any thoughts?
  8. Hi, In the latest v7.9.6 update, when creating an effect, any tagged parameters are not correctly stored into the effect palette when recording the effect. To reproduce: - Select any fixtures, and create an effect in the waveform tab - Set the value of another parameter in the programmer, such as Colour, or Intensity - Press record - Select the attribute(s) you wish to store in the effect palette; any tagged attributes will already be selected (note how Intensity and Colour are selected here): ) - Store to any palette, but note how only the effect is saved ('E'), and not any of the other attributes (typically signified by 'I', 'C', etc): The expected behaviour would be that the tagged intensity and colour attributes are saved into the effect palette.
  9. This would be really useful as it's pretty hard to figure out what the buttons are on-the-fly. A background image in the window which has all the same labels as the desk (as opposed to rendering each label individually) would be fine.
  10. There are labels for every button on the Solution: The issue is that I don't see any.
  11. I've been suffering with this bug in Phantom ZerOS for a while now where the labels of buttons on the front panel window don't show. For example (on the Solution): However in Phantom Jester the labels appear fine: You can see that some labels appear fine (the ones on the buttons) on desks like the Orb: However the "background image" (ie. the lines on the desk behind the faders) are still missing. I've also tried uninstalling & updating to the latest version of ZerOS (v7.9.6) which didn't seem to help. Any ideas? Thanks!
  12. Just thought of something else-- Shift + Key to open window onto the current selected desktop Currently when you use the shift+key combo to open a window (ie SHIFT+COLOUR to open the colour pallette window) it will typically open onto Desktop 1. Would it be possible to make it open onto the desktop you are currently looking at, as opposed to opening the window and then having to cycle through Special->Screen until it opens on the correct desktop? Thanks!
  13. Hey! I've been using the Solution for a few weeks now (on the latest firmware) and have a ton of bugs, suggestions and questions I wanted to discuss. Weird behaviour on cues when using 'Fader Controls: Colour' Suppose I have 4 moving head washes with a Default preset/home (Record button -> Home -> Default) of full white, straight up. Now I create a Playback with 3 cues, using red, blue, and green colours in each queue respectively. Then open the setup for the Playback, and set 'Fader Controls' to 'Colour'. There are two things that I notice: 1) When fading the playback back down from full to off, the colours will fade between the colour of the current cue (ie. green), and the colour of the previous queue (ie. blue). I'm not sure if this is intentional or a bug, but in my opinion a preferred behaviour would be if it faded from the current cue (ie. green), back to the default colour (white). At the moment it fades from green to blue, and then snaps back to white as the cue is released. 2) Enabling 'Fader Controls: Colour' seems to break the colour fade between cues, but this works fine when 'Fader Controls: Colour' is disabled. I only just noticed this when playing around in Phantom ZerOS, and I'm not sure if this happens on the actual console. Setting programmer time without using a submaster fader Is there any command line syntax/menu to set the programmer time without using a fader? I find the fader difficult to set to the correct value and it's also annoying to have to 'waste' a fader just to set a value which doesn't need to be modified often. Bear in mind this is different from the 'Time' value which is set under Special -> Time (although, I would also like to know if there is any syntax for setting this value, as it would be useful to have a few macros I can quickly flick between to adjust the global fade values of cues based on the genre of song, for example). Set maximum/minimum for Programmer Time fader in fader setup When you assign a fader to Programmer Time, it gives you a range between 0.1 seconds and (I believe) 11.5 minutes. Would it be possible to set a minimum and maximum value for this range in the fader setup (ie. between 0.1 and 5 seconds). This would make it much easier to set more precise values when setting the Programmer Time via fader. Cue Step + Time button to fade to the next queue with set Time Say I have 3 cues each with a fade of 0.5 set on Up, Down, and Colour. Would it be possible to add functionality such that when the time button is held and the cue step button is pressed, the fade time of 0.5 is instead replaced with the 'Time' value of the console (ie. 5 seconds)? My suggestion would be to make this apply to any fade parameter (Up, Down, Colour, Beamshape, Position) which is set to a non-zero value Loading a look from the blind mode into the live editor While I'm sure this isn't strictly the correct use of blind mode, would it be possible to add an option when exiting blind mode to load the current look back into the non-blind (live) editor/mode? This means theoretically you could set up your next look in blind mode, and then jump out to instantly load the new look immediately and simultaneously. Remapping preset faders onto submasters within software, versus using dmx input <-> output I saw a suggestion from @Jon Hole to another user on the forum a while back to allow you to use preset faders as additional submasters. By looping a 5-pin DMX cable between one of the DMX outputs and the DMX input, assigning the DMX input to submasters, and assigning the preset faders to give output on that universe, you could set the faders to act as additional submasters. I really like this idea, however it would be a much cleaner solution to be able to do this in software. I feel like the faders/dimmers are greatly locked down to simply being dimmers over channels 1-48 in the current software, and it would be great to free them up for some additional functionality. Multiple DMX addresses on a single fader I also noticed that it's not possible to 'group' multiple addresses onto a single fader. For example, if I have 2x LED 4ch. pars (R/G/B/Dimmer) which are set to different addresses (ie. 1,2,3,4, and 5,6,7,8), it's not possibly with software to run these two fixtures on the same set of four dimmers, to have simultaneous control. Instead you would have to modify the DMX addresses of the fixtures themselves to overlap. Would it be possible to have a single fader control multiple DMX addresses? Selecting multiple cells in the programmer window & deleting entire columns When creating cues, you often pick up data which you don't need. For example, if I'm creating a cue stack to act as a colour chase for a set of movers, I will often also get unnecessary position data. While this can all be removed, I noticed there is no way to a) select multiple cells at once for deletion, b) select entire columns or multiple columns for deletion, and c) 'group' fixtures by type (for example, if I have 4x moving heads, they will all be presented individually within the programmer rather than all under one set of columns). Bug: Phantom ZerOS seems to have no labels on the front panel of the console (Solution) When I load up Phantom ZerOS on my PC (Windows 10), labels of the buttons don't appear on the "front panel" view of the desk. This also seems to happen with the Leapfrog 96, but not with the Orb XF or Frog 2 (possibly because the labels are on the button themselves rather than below? Not sure). Might be worth noting that PhantomJester seems to work fine. Screenshot: https://puu.sh/CrKKv/a5d72857bc.png Suggestion: a fix/workaround for fixtures which incorporate strobe into their dimmer curve Some cheaper fixtures (ie. the Lightmaxx Tri Par Wash) will incorporate strobe into their dimmer curve. This means when rolling the intensity between 0 and 100 (ie. in an effect), the light output will fade from dark to full brightness, then strobe awkwardly, before returning to full brightness again. Would it be possible to add some sort of workaround for this (perhaps in the fixture patch), where the desk is able to intelligently split the two ranges which are actually 'dimmer' and 'strobe' awkwardly mashed into one DMX channel? This means applying sine waves etc. on the dimmers of such fixtures would give the expected behaviour rather than strobing and flashing all over the place. Thanks for taking the time to read through my post, and please let me know if you have any ideas/suggestions :-)
  • 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.