Thanks guys. I will try your suggestions. I may not have had a long enough delay on my macros and timelines. John

Having the MISC level active at the start of the build shouldn't affect anything unless you have a macro attached to the 1st KF of the effect at that level that drives some other effect. The switcher requires somewhere between 3 & 5 fields to process the effect information after your e-mem is recalled before the effect is actually executed - that's the same whether you manually press the e-mem or if you have a macro do it for you. As was mentioned above, macros replay their series of button presses almost instantly. So you need to factor in the recall time of both the switcher processing as well as any cue-up time for external devices. When I build macros that recall & run timelines, I always insert a pause of at least 2/10 sec. between the recall and the run commands - I will increase that pause to up to 10 frames depending on the external devices being used. To verify whether it's the switcher or the external device that's causing your problem, try doing a manual recall of the effect with the AUTO RUN turned ON. If all aspects of the effect will run properly, then the issue may be with the macros & any necessary pauses for switcher processing time. My guess is that with AUTO RUN turned ON, you'll still see a problem with your FF catching up. In that case, you'll know that the FF is the culprit and you can adjust the amount of pause in the macro as necessary.

John, What I think you want to be doing in the replay example here is to use macro a little more as a helper, than a nuts-and-bolts control system. Also, remember that macros execute commands as fast as the system can "press" buttons, unless you program in delays -- this could be the reason for your timing issues. The macro is likely trying to run the replay timeline before the Fast Forward and timeline have time to set themselves. Since your replay-in is likely always going to be M/E-3 to M/E-2, and your replay-out is M/E-2 to M/E-3, both with the FF covering the transition, build each of those timelines as you normally would, maybe even without macro. Just make sure those each work as conventional timelines on their own. Next, create two macros, one that recalls your replay-in, and one that recalls your replay out. Now, you can add a macro level (your macro MISC) to your replay-in and replay-out timelines by LEARN MOD, or you could have just built it that way from the get-go. Leave it enabled throughout the timeline, just don't have any extra macros assigned to keyframes -- only have macros on keyframes where you need Macro to do something... At the end of each timeline, insert a macro keyframe that has those macros from above that recall the opposite effect (end of the "in" recalls the "out", end of the "out" recalls the "in"). Now, when you run the "in", the "out" automatically recalls at the end and vice versa -- very helpful, especially if the FF elements are different for "in" and "out". You have initially to get into this state by recalling the in or the out yourself, though, either by the master e-mem pad or replace-attaching the recall macros to panel buttons. To take care of your "set-source-recall/run-replay" goal, make a macro that only sets the replay machine on your replay M/E, and presses the "RUN" button. This will select your source and run the replay, assuming that you already have the replay-in effect called up. I haven't personally created a macro that also recalls the replay timeline, but I suppose you could do it. I would think the important thing would be to program a delay that gives the FF time to cue. So, your macro would probably go: recall timeline, select replay source on replay M/E, delay (experiment with how long the effect needs to properly cue), run timeline. Good luck, Chad