Thanks again for the replies. I do use the 10,11 triggers on the same time line and I dont use the macros to recall a register, rather set the tape machine in ME2 and hit run. I have'nt tried a pause between the tape set and the run button however. Guess I can try that next but I'm not sure this will help. Like I said earlier, I've traveled this set up from truck to truck and this is the first time I've had problems with my macros firing the timeline. When this problem occurs, I've noticed everytime that it runs the timeline just misses the triggers ( I thought adding a .02 even .03 before the run trigger would help but no dice).

If you're calling up the move, then running it immediately, you might not be giving the SpotBox/Lance enough time to cue before processing the run trigger. This will sometimes cause the second channel to fail. If you're building a macro with a recall followed by a run I have discovered, through experimentation, that the shortest reliable delay built into the macro is 0.3 seconds. I use the Lance's internal ganging and send a trigger only to the first channel. As Tom suggested above, you can use the 11 and 10, triggers to call up your out transition animation in the same timeline as the in move - no need to have to quickly call up an out move and run it! Trigger 11 calls up the current register plus 100, trigger 10 calls up the current register in the 0s.

Also, sounds like you should be using triggers 10 and 11 so that you can have the off move on the same timeline.

Well, I seperated the the p-bus address's, gave it a longer k-frame to fire (.02), even inserted an extra play trigger k-frame, and it still blew past it on the timeline. Once again, this occured at random. Happened twice replaying to the ME (it just cut to the ME,never fire the spot) and once on the off move. I stayed away from using the macro's and did it the old fassion (4k) way after a while and did'nt seem to have any problem. Still not sure where the problem lies here...lance,spotbox,kalypso? I've used macro's a lot with kalypso's without a hitch, but it has always been with a FFwd and not a spotbox.

[quote="mtiffee"]I've seen this happen when using just 1 p-bus address for both channels. When using discreet addresses for all channels, no problems.[/quote] Mike, when you use discreet addresses for each channel do you still gang channels in the lance? Holding down ch a,b and set, etc. ? I am thinking once you gang them I wonder if it doesn't even care about ch B's P-bus address since it was told to hang with channel A ? Just curious.. later Bill

Thanks for the feedbackguys...I'll try seperating the channels and even adding an extra keyframe (cant hurt)... lets see if that does it. Thanks again

For many switchers, PBus commands are non-deterministic. Thus, one trigger might be hitting on the Odd field & trigger everything correctly, while that same trigger played later might hit on the Enen field & miss the command. What I have done is to build a couple of PLAY triggers, one field apart - instead of relying on just one trigger. In the case of macros, I issue a PLAY command followed by either a 1 field delay or no delay at all (depending on the switcher) and then issue another PLAY command. This has solved virtually all of my PBus trigger issues.

I've seen this happen when using just 1 p-bus address for both channels. When using discreet addresses for all channels, no problems.

Unger are you ganging channels on the lance or sending out two seperate P-bus plays triggers. Weird that a longer duration would play it correctly, great workaround if it works.. Bill

I used to have that problem when I first started using a Lance - my first keyframe was only 1 frame in duration, and the second keyframe was my 0 trigger to run the clip, and once in a while the switcher would only trigger one side. Changing that first keyframe's duration to 2 frames seemed to solve that problem. On using a macro for the move - I also use macros to fly and recall the off move (and also for the other way - macros run the off move, pause, and recall on the "on" move) and I've never had a problem with them. Hope this helps.