Phase-lock-loop Hog timing macros, or the closest equivalent we get to a "tap sync". What these do is drag the console's timing closer to a beat you input with a GO button, to help lock it in very close. It uses the whole-console "rate thruster", because sliding the clock rate of everything up and down keeps all cuelist and effects timing together which is really what you want when spinning a dance floor. This was originally posted on Lightnetwork, but wasn't useful because Delphi trashes all the spacing in such files and makes them unreadable. Here's the original concept: wait cue action arg parameter ----------------------------------------------------- 1 push choose 0 7 0 0 8 2 link to 1 Fol 3 wheel rightwheel 1 2 4 link to 1 Fol 5 wheel rightwheel -2 Fol 6 link to 1 9 release choose 0 7 0 0 Fol 10 nothing >R8 in comment I MOVE the macro to fader 8 on a page [it's actually on the template page, in fact, so it keeps running across any page changes] and generally keep fader 8 chosen, so main GO or the fader's GO will keep the macro going. Then I have another macro that simply does "goto 8/9" when I want to stop the sync macro and clean up the choose-key state. === and somewhat later... === Here's a much better macro that converges a bit faster when you're trying to speed up, and uses a 1s beat timing instead of 2s. It also self-releases if you don't do anything for 4 seconds, obviating the need for the manual cleanup. At 120bpm, you hit GO every *other* music beat and the desk should soon sync up. wait cue action arg parameter ----------------------------------------------------- 1 push choose 0 7 0 0 4s 1.5 release choose 0 7 0 0 >R8 in comment 8s 2 link to 1 Fol 3 wheel rightwheel 1 1s 4 link to 1 Fol 5 wheel rightwheel -2 1s 6 link to 1 Fol 7 wheel rightwheel -1 1s 8 link to 1 Fol 8.5 link to 7 9 release choose 0 7 0 0 Fol 10 nothing >R8 in comment Now the goto 8/9 isn't really needed, but I still have the cues in there just in case of confusion. Note that as written, the macro depends on being attached to master 8 -- you can change the "choose" argument and comment macro to reflect whichever master you'd prefer to hang this on. The console rate% will "bobble" between 2 or 3 different values once it has gotten close. Leaving it on whatever the middle value was will let the macro exit with the timing closest to the beats, and then you probably won't have to resync for a while or until the music changes. If you need to radically change speed, start the macro and then use the rightwheel to yank it quickly into the right ballpark first, and then fine-tune by GOing the macro on alternate beats. To construct the macro, start recording and rough in the keystrokes and wheel movements, and then go back and fix up the event types and timing and arguments manually. You will then have to fiddle with the "skip" buttons to move the cue pointer around and add the links. I wrote this with a specific approaching event [Arisia] in mind, which has by now happened, and it all seems to have worked fairly well. Every so often the HogPC would get sort of confused about whether the macro was running or not, or would take a really long time to start up again, but since I had some other people driving and it wasn't always my hands on the keyboard, I'm not sure what was going on. Haven't had another chance to brute-test it yet, but I think it had something to do with changing to a page with something *else* on playback 8 while the macro was running, so it sort of half-released. HogPC is not always entirely clear about its own keyboard state to begin with... _H* 040120