ion & ML question for a Noob....

Yes, this is a great feature of the Eos family called Marking. You can read up on it in Chapter 12 of the Ion v1.7 manual, but Mark is essentially a feature that tells your Non-Intensity Parameters to go to their next setting before the light actually turns on. The easiest way to do this would be to turn on AutoMark, which can be found in Show Settings. If you need to manually add Marks, just select each channel that has a new Non-Intensity value (such as a new scroll color) in a specific cue and press [Mark] [Earliest] [Enter] (there are other settings you can use as well, which you can read up on in the manual). Also, you probably already know this, but Marking doesn't really work unless the units do actually fade out between different Non-Intensity settings.

Hope that helps!

thanks for the swift reply though.... Matt

EDIT: Looks like Rochem beat me to it. So , what he said. 

==

Hi Matt,

The fact that you say that you see the gobo going to "Home" in LX 2 makes me think that you have somehow recorded gobo values into Q 2. I'm assuming that you are using the Mac 700's in a gobo in LX 1?

If you see something moving as a light fades up from 0, it is not marked properly(something might be preventing Auto Mark from working). If something moves as the light fades to 0, then the light has a hard command on a Non Intensity Parameter in the cue that also fades the light to 0. 

My suggestion would be to go into Q 2 in Blind, select your moving light channels, select all NIP's and then [@] [Cue Only] [Enter]. By removing the values Q only, it will ensure that Q 3 has the proper hard values for the move instructions. 

Also keep in mind that if the light is going out in Q 2, and the Q time is a 5, that it will take the lights 5 seconds to fade out, and then the console will take another 5 seconds to mark the light, so if you take Q three within 10 seconds of Q2, you will probably catch the tail end of the mark.

HTH,

EDIT: Looks like Rochem beat me to it. So , what he said. 

==

Hi Matt,

The fact that you say that you see the gobo going to "Home" in LX 2 makes me think that you have somehow recorded gobo values into Q 2. I'm assuming that you are using the Mac 700's in a gobo in LX 1?

If you see something moving as a light fades up from 0, it is not marked properly(something might be preventing Auto Mark from working). If something moves as the light fades to 0, then the light has a hard command on a Non Intensity Parameter in the cue that also fades the light to 0. 

My suggestion would be to go into Q 2 in Blind, select your moving light channels, select all NIP's and then [@] [Cue Only] [Enter]. By removing the values Q only, it will ensure that Q 3 has the proper hard values for the move instructions. 

Also keep in mind that if the light is going out in Q 2, and the Q time is a 5, that it will take the lights 5 seconds to fade out, and then the console will take another 5 seconds to mark the light, so if you take Q three within 10 seconds of Q2, you will probably catch the tail end of the mark.

HTH,

Once you've cleaned up all your cues, if you still have unwanted visible moves then discrete channel timing can be helpful.  You can delay the move of any parameter (intensity, color, focus, beam), speed up or slow down things to make everything behave the way you want.