Need some help for Ion: autoblocks, encoders, level wheel, capture.

This is for the Ion 1.4.2 (I just upgraded, so some of this may be moot).

Auto-Blocks: great concept, but the show we just programmed was programmed in a somewhat haphazard method.  By opening, almost every cue had an auto-block.  I want to keep the ability for auto-blocks, but is there either any way to refine this feature, or to clear the auto-block from selected cues?

Encoder wheels: what do users feel are the best settings?  I played a bit with them, but I'd spin the wheel and either jump wayyyyy to far, or it would barely move.  (this was with an I-cue and some gobo rotators)

Level wheel: how do you switch it to proportional?  right now, if 2 channels are at 25% adn 50%, and I roll them down, then ch 1 goes out first, while ch 2 keeps rolling until it hits 0.  How do I change this so they both hit 0 at the same time? (this occurs on 1.4.3 as well)

Park button:  with a channel parked, sometime the LED on the button is lit, adn sometimes not.  If I run a macro to restore the Parked channel, the LED lights up.  Its as if the console doesn't recognize it has a parked channel, even when the lights are at the correct intensity, and the Park Park screen shows the parked channel.  Thoughts?

Capture: I'm not clear as to when you might use this feature.  Could someone give me some scenarios or advantages?

Thanks very much.

  • Hi Andrew

    Autoblock: There is an "auto-block clean up" function, however I don't know if this has been implemented yet.

    Encoders:  In Setup somewhere (probably under the DESK tab) you can set the acceleration rate of the encoders.  This setting essentailly controls the acceleration factor of the encoders.  The purpose of this is so you can get from a low value on a parameter to a high value rather quickly.  Try adjusting this setting. 

    Level Wheel: Not 100% sure, but look somewhere under desk settings and see if there is a way to adjust this.  If in doubt, try using desk help, or search the manual

    Capture: An example where i have found this useful is when a moving light has gone haywire during a show.  What I do, is take the lamp to 0%.  Capture it, then reset.  This prevents the light swinging into position at full and changing colour, gobo, etc after completing it's reset command.  Once the lamp is reset, I usually [all NP sneak] and once it's in posi, release the capture and sneak the intensity.

    I also find Capture  handy during rehearsals if you need to hold a chan, or a particular parameter, especially in a fast moving / cue heavy show.  You can turn on capture, and then adjust levels, parameters, etc while running through cues.  When you finally get a moment or two, you can update your changes (either [update trace] or [update live] works well in this scenario.

    Hope that helps

    Cheers

  • Regarding Capture, I always leave it on for the same reason Brent just said but more. Actually I always have capture locked so that anything I do is captured [Capture][Capture][Enter]. Reason being I don't want any Goto's or cue execution or anything to undo any manual changes I have made, super annoying when they clear out. If I want to release them then I'll sneak everything.
  • Hi all... we haven't yet implemented auto-block clean up.  No firm ETA on that yet.

    just so you know, you know.  :-)

    a

Related