Zipp, I have a guess as to what may have been wrong. It's been a long time since I've been on a 3K, so my memory might not be completely accurate. When you do a recue command within a timeline, you have to do it before the pause. If the recue command is on the same keyframe as the pause, it won't be executed until you resume running the timeline. Next time, have a keyframe with the recue command, a keyframe with the pause, and then a keyframe with the play command. Scott mentioned ganging channels and it's a good idea. Especially when you get into situations where you need to have different addresses for your channels. Ganging can prevent slippage between the key & fill channels. Just hold down the channels you want ganged (usually A & B, of course) and hit the "set" button. Once you do that, a trigger sent to any of the ganged channels will be executed by all.

When I said slaved together I was referring to ganging the channels. I have had the problem you described on a 3K. Ganging the channels usually sovled the problem. If not, I mapped the Lance controller as 2 devices and sent out a Run Trigger to each device. Kind of a pain on the 3K since you run out of Trigger real estate. I have also found that if you use trigger 11, don't put a pause on the same keyframe. Insert trigger 11 and put the pause in the next keyframe and give it a three or four frame duration. Scott

Scott, Good point, as I don?t remember seeing the key channel trigger on the monitor wall with this clip. By slave are you referring to the ?gang? mentioned in the lance manual? I do not do that. Could that be it? I usually set both A & B to device 1 in the controller, and then set all my ins and outs with both channels lit and send only one trigger to device 1. I?ve never had a problem. All my other effects with clips ran perfect that day. I just wat to make sure as I rarely use the # 1 or #11 cues. Mike, If it was a Lance or FF problem as you mentioned, FYI, it happened with both Cues # 1 & #11. Jeremy, I also use the .5 between K1 & K2. Thank you all!

I've come across this issue, and found a 5 frame delay between key frame 1 and 2 solves this problem every time, whether it's a grass or a sony. Keyframe 1 cues the FF, KF 2 gives the run command and turns the keyer on. When I first started I would make KF1 duration 2 frames. 5 frames avoids the issue but doesn't delay too much. Hope it helps.

Zipp, I have run into this a few times in the past when using a #11 trigger. One reason I try to avoid them. Not sure if it is a Lance or FF issue.

Were your Fast Forward channels slaved together? It sounds like your key channel was not recuing unless you did the manual recue. Scott