Automark Query

Malcq,

I too would be interested in the real answer, but the workaround (you may already know) is to put the Intensity at 01% in any cue that you don't want the automark to happen.

B

Thanks for that, although I had read that elsewhere it had not occurred to me in the heat of the moment. My console is in transit at the moment but I will try it out the next time I get in front of it

Malcg

Thanks for that, although I had read that elsewhere it had not occurred to me in the heat of the moment. My console is in transit at the moment but I will try it out the next time I get in front of it

Malcg

You can also disable automark on a cue-by-cue basis.  On Ion, this appears as a soft key.  [cue # {automark off}]   The softkey is either automark off, or disable automark, or something like that

If you are having problems like a focus not marking in time, change the focus time for the cue when the lamp comes up to a shorter time.  Automark takes it's timing from the cue in in which the lamp comes up.  If it is a multipart cue, then the timing of part 1 is used.

  If changing the focus time is not practical (the focus time is used by other lamps) try a discreet timing, or make the main part of the state something other than part 1, and set a shorter focus time on part 1

Hope that helps

Cheers BFJ

If I might add a bit of commentary here regarding timing.  When using either referenced marks or automarks, the desk will use the timing of the cue in which the lights actually mark (preset) - I think that's what you meant Brent, since that's the way the rest of the post reads :-)

So, if the data is stored in cue 10, marking in cue 9, it'll use the time of cue 9.  And Brent is right, if the mark happens in a multipart cue, an automark will use the timing of part 1.  (As a note, when using referenced marks, you can mark back to a specific part).  The timing can be changed in the marking cue as Brent suggests.  

Its worth noting if you want to/need to use discrete timing, that timing is applied in the cue where the move instruction is stored.  So, in this instance, you'd put the discrete timing on the lights in cue 10 - even though they will use that time in cue 9.  That can be a bit confusing at first.  But since the value that you want the lights to assume is stored in cue 10, the timing is there as well.

thanks all!!

a

anne that is a great way to explaine the whole tracking concept.

thanks

:-) Sarah and I have been working on a white paper (well, started it eons ago and got sidetracked) about control philosophy.  If you are interested in that sort of stuff... stand by.  We hope to get it posted shortly.   

Thanks!

a

Thanks for the clarification... it's been a while since i programmed a show on the Ion and don't have one on hand (funnily enough)

Cheers

Sounds great Anne! Can we expect global automark timing in 1.5?

Its not in 1.5, sorry.