Editing Mark Time

T-Rex, there are two ways the timing is handled (this is true of both automarks and referenced marks).

If you do not apply discrete timing, the lights will use the timing of the cue in which they actually move.  So, if they go active in cue 10, and mark in cue 9, they will use the FCB time of cue 9.

If you apply discrete timing (following the above example, the discrete timing would be applied to the lights move instructions in cue 10), they will mark in that time, regardless of the cue they mark in.

Hope that helps.

a

Thanks Anne!

I just was wondering, say you had cues back to back, and didn't want to create an autofollow cue.

...Okay lets simplify this: Lets say I have a Mac 2000 patched into channel 5, and it goes out in cue 9, and is marked for a different position in cue 10. Lets say cue 9's time is 9 and cue 10's time is 5, but i want the mac 2k to mark in a time of 0 so we can practically have the cues execute back to back, how would i apply the mark time of zero without effecting the fade times in the actual cues??

or is it even possible?? aside from creating an autofollow cue that only moves the mac 2k in the dark??

i would add in cue 10 [chan5 focus color beam delay (x)] to put the move after the fade

As an FYI, if a light is at a level, fading to zero and then marking for the next cue, the mark is not triggered until the light hits zero.  So, placing a discrete delay time in the subsequent cue isn't necessary, unless you want to further stage the mark from the point the light goes inactive.  Does that make sense??

:-)

a

Exactly!! :-)

Hello,

I still didnt get why there is no global time set for the mark cues. I am used to Whog, MA, horizon and those consoles know when the intensity for a moving light i am using in a cue is fading to zero, the next move they have to do (if  marked in the next Cue) is matching all its parrameters to the next cue (except intensity). I would like for that to happen as quick as possible, as i am sometimes running cues in quick succession and for the light to go to its marked cues taking the time of the next fade doesn't really work. I understand that i could change the FCB times in the cuelist, but that seems to defeat the purpose of Mark, as it would very time consuming (and annoying) to do that for the whole list. Is there something i am missing?

Looking at my playlist and playing back cues i always wondered why it would run down the programed time (in red) and then start to run another time (in green). As far as i understand now, that would be the time for the "MIB".??

Hello,

I still didnt get why there is no global time set for the mark cues. I am used to Whog, MA, horizon and those consoles know when the intensity for a moving light i am using in a cue is fading to zero, the next move they have to do (if  marked in the next Cue) is matching all its parrameters to the next cue (except intensity). I would like for that to happen as quick as possible, as i am sometimes running cues in quick succession and for the light to go to its marked cues taking the time of the next fade doesn't really work. I understand that i could change the FCB times in the cuelist, but that seems to defeat the purpose of Mark, as it would very time consuming (and annoying) to do that for the whole list. Is there something i am missing?

Looking at my playlist and playing back cues i always wondered why it would run down the programed time (in red) and then start to run another time (in green). As far as i understand now, that would be the time for the "MIB".??

The green fading time refers to marks that could not start on GO because the light was fading to zero in the mark Q.  You can see this in preview where a green MK symbol covers a green zero and a magenta MK symbol covers a tracked out channel.  You could always set your FCB record defaults to zero, if speed its what you need.