Support |
mark francombe wrote: > On Sat, Feb 12, 2011 at 12:19 PM, andy butler <akbutler@tiscali.co.uk> >wrote: >> The EDP keeps track of where you are in the beat. >> The Gordius can't know when to Quantise. > > Well probably quantise is the wrong word, effectively the same though. > Just to be clear what I mean... > Im imagining THIS scenario. > > Two hits of a gordius pedal set to RECORD defines the tempo of > course, midi clock is sent out of EDP (via a merge probably) BACK to > the Gordius. > A switch on Gordius can be pressed,at ANY time, and.. because gordius > is listening to midi clock IN.. WAITS before for a division of the > beat. Lets say an 8th beat.. (this gap might be anything smaller than > an 8th.) It sends out an UNDO command.. then waits for the same > division (8th) and then fires off another UNDO, waits an 8th... UNDO > etc etc as long as I keep my foot down.. I release.. its stops... > OR.. A more complex sequence or MULTS INSERTS SPEED CHANGES, REVERSES, > in a loop, all divided by a preset division. ok, here's the bottom line Gordius can't on it's own wait to start on the beat. Because it just counts midi *ticks*. That's all it does. Look up what a midi *tick* is....then you'll understand. 24 ticks per beat, or similar. Midi Clock *doesn't* tell the receiving device where the beat is. It's just a stream of identical ticks. If you start the sequence at the right place, it'll run in time. If not, it'll be synced in the out of time position. > in the evening Hilde sang a strange Norwegian song for > the kids... I videoed it.. it was very strange and haunting! Im gonna > make a track out of it.. glitch it up a bit... with her permission Ill > post later... would like to hear the original too! best regards andy