Jump to content
Vari-Lite Controls Support Forum

Jon Hole

Vari-Lite Admin
 View Profile  See their activity

  • Posts

    2,518

  • Joined

  • Last visited

  • Days Won

    35

 Content Type 

Posts posted by Jon Hole

  6. Touch Screen Help

    in Solution & Solution XL

    Posted

    Unfortunately, Iiyama (who produce these screens) appear to have two different drivers but the screens report themselves back identically.

    In a normal consumer's situation this isn't a problem - the correct driver is included within the box, they install it on their PC and it works.

    However, when we have to store all the drivers, if monitors requiring different drivers don't identify themselves uniquely, we don't know which is which... so we've had to include a manual method of switching between the drivers.

  8. Edit fixtures on 7.9.3

    in Solution & Solution XL

    Posted

    23 hours ago, grusus said:

    removing it from setup with no option to manualy enter values (like was before) is in my opinion a step backward. 

    Hi grusus, the "old" method (entering values within Setup) had many many limitations:

    1. Values had to be entered "blind". This meant you generally had to write down all the values you wanted, enter SETUP and then type them all in.
    2. Values had to be updated one-by-one, or use the same value for every fixture - nothing inbetween.
    3. Values were stored as percentages only. So a fixture with 540 degree pan just moved to the nearest 5.4 degrees - not very useful!
    4. There were no "details" (for Gobo, Shutter etc), just numerical values
    5. There were no Palette References, so when touring it was difficult and time consuming to update values

    The new method solves all these problems - allowing you to use "normal" programming techniques (groups, encoders, referencing palettes, parameter details etc), update the values live to ensure they're correct, and the console stores these values as 16bit parameters resulting in the outcome being much more useful and accurate.

    18 hours ago, grusus said:

    From 2 years it is getting worse after each update.

    I'm sorry to hear you think this - we've had a lot of positive response to our software updates recently, especially from Solution users. Over the last 13 months alone, the Solution has benefited from:

    1. Multiple Playbacks, significantly improving the functionality and flexibility of the console
    2. New "syntax" order, bringing Solution in line with most other consoles
    3. Updated "Special" MFK layout, making many tools within this menu much quicker and simpler to use
    4. Improved Remote Apps, including adding Syntax control
    5. Global Tap Tempos
    6. SETUP+INSERT brings features such as Highlight, RemDim and Park which Solution never previously had
    7. Improved ASCII importing, including from ETC showfiles
    8. "Auto-select" option on Channel Faders
    9. Automatic Effect Offset options 
    10. Remote Device Management
    11. New Fixture Schedule layout allows you to manage fixtures much more quickly and simply
    12. New Add Fixtures process with many new functions including Universe Preview and Patch Offset
    13. Expanded CITP functionality
    14. Over 100 other enhancements and bug fixes

  11. Smart tag

    in FLX

    Posted

    18 hours ago, kgallen said:

    I'll have a think if there is any move on dark impact but I don't think so with a simple rotator.

    If you take the intensity to 0% there could be, but if you leave it at full you should be fine.

  14. Smart tag

    in FLX

    Posted

    Yes, that's correct.

    The rules are along the lines of "snapshot" (record absolutely everything) except for:

    • Ignore fixtures at 0%
    • Ignore parameters which are the same as the previous cue (or default if you're recording the first cue)

    This is helpful, as it avoids any "blocked" values being recorded (in tracking mode, blocked values are values which are recorded even though they are identical as the previous cue, and so don't need to be stored again).

  15. Preset Faders as Haze/House Light control

    in Leap Frog 48 & 96

    Posted

    17 hours ago, BigDick said:

    When did this change?

    It was introduced with FLX two years ago, and then transitioned over to the rest of the ZerOS range last year.

    17 hours ago, BigDick said:

    Who do I need to thank!?

    Ultimately, you can probably trace it back to my next door neighbor who convinced me to purchase a Mac all the way back in 2005!! :lol:

  19. Theater cues crossfades

    in FLX

    Posted

    Hi Emmanuel,

    As Kevin says, record all your cues onto a single Playback. Press the Play/Pause icon top left and you'll see those cues. You can select any of the cells and adjust the cue's fade time using the encoder wheel. This allows you just to press the GO button, and get smooth, recreatable fades.

    However, if you want to do this manually, just hold SETUP, press the GO button, and then change "Fader Function" to "Manual Fade (2 ways)". I've just tested this and it behaves how you want. I believe the issue Kevin's describing is that if you switch back to HTP Master, you'll need to release the playback first (Kevin, is that correct?). To release the Playback (release="turn off"), hold down the CLEAR button, and press the GO button.

  20. Preset Faders as Haze/House Light control

    in Leap Frog 48 & 96

    Posted

    Hi, the Preset Master Faders are still used, but only when the console isn't in "Wide Mode". It's not possible to change their functionality.

    There's no "exclusive" option for Playbacks on the Leapfrog 48s, but you can use the "Inhibit" function.

    Record the Haze machine at full output onto a Playback, go to the Playback settings and enable "Inhibit". This allows you to record the Haze machine at full into all your cues, but have a dedicated "Master" for the Haze machine... which would give you a similar result as you're looking for, just in a different way.

    Jon

  24. Playing two ques at once

    in FLX

    Posted

    10 hours ago, Looking Glass Theatre said:

    When I hit the go button for the next que, the red stops fading up. Is there any way of solving this on my FLX?

    As Edward says, so long as you're in Tracking mode, this should happen automatically as ZerOS executes "Move Fades" - ie, the only parameters that "move" (change) are the parameters that are recorded within that cue - so as long as those parameters aren't included within future cues, they'll be left alone doing whatever they were doing before - in your case, a 20 minutes fade. (Don't get confused with the word "move" - this is nothing to do with moving lights, and just describing that a "parameter" (could be intensity, colour, beam, position etc) is moving from one value to another).

    Therefore, if you're finding that in your next cue the fixture is snapping, you're either (a) not in tracking mode, or (b) have programmed that moving light into the following cues. You can use the "Remove" function within the Record Window to solve this - go into the "following cue", clear the programmer, select the moving light, press HOME (this is just a quick way of "tagging" all the parameters of that fixture), and then press RECORD {REMOVE} CUE x ENTER.

    Alternatively, as mentioned by Pete, you could store this on an additional Playback and either run it manually, or trigger it via a macro.

  25. Part of the fixtures recordes in a playback had intensity 0 all over a sudden

    in FLX

    Posted

    Hi Peter,

    In the Output Window, intensities shown in red are from the "Programmer". The easiest way to think of this, is it's where information goes before you record it somewhere. So if you push faders 1 - 6 up to 100%, this information goes into the "programmer". You may choose to then record this (so the information is transferred from the "programmer" to where you record it), or you may choose to clear the programmer, by pressing CLEAR twice (first press clears the selection, second press clears the programmer). If you pull those six faders back down to 0%, this new information goes into the programmer. The important thing to remember about the programmer is that the programmer always wins. So often, you may push up faders, record to a cue, pull down the faders, and then try and play back that cue. But pulling down the faders has added lots of 0%'s into the programmer, and the programmer always wins, so it appears like the cue hasn't worked. Press clear twice, clear the programmer, and now the cue works.

    Another thing to bare in mind if you're coming from a Frog console - don't lower the Playback Fader when recording cues. If you're recording cues into a Playback (the Master Playback for example), just keep the fader at full (100%).

    You may find out YouTube training videos helpful.

×
×
  • 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.