[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Date Index][Thread Index][Author Index]

Re: BeatSync (was vortex info)



At 10:49 AM -0800 11/12/97, Kim Flint wrote:
>At 11:02 AM +0100 11/12/97, Haible Juergen wrote:
>>      >The OB Echoplex can sync continuously to the old type of pulse
>>clock from
>>      >old sequencers and arpeggiators, using the BeatSync jack.

hmmmm. I said this while sleep-deprived....now that I've had a big jug of
coffee I'm thinkin' it might not be quite exactly right. I'm not sure that
BeatSync works with the old pulse type clocks. Pulses sent by metronomes or
drum triggers or whatever, sure. But I'm not sure about those old clock
lines. Does anyone know more about how those old clocks work? How many
pulses are sent to define the time? It's possible it works, but I'm
starting to doubt it. Matthias would know.

BeatSync uses pulses to define the cycle time for the loop. So you might
hit a drum trigger to define the start and stop times. (or the cycle times,
if you are familiar with how the echoplex deals with
cycles/multiplies/sync; meaning the total length can be some multiple of
the defined cycle time.)

If it turns out I'm wrong about the pulse clocks, sorry if I misled you....

kim


>> It
>>also works
>>      >with other pulses, like drum triggers. You can even use audio
>>sources, like
>>      >a metronome output or a mic'd drum or even a guitar. Just has
>>to be some
>>      >kind of pulse. The sync operates the same as midi sync for
>>setting loop
>>      >times, and keeping them in time. The echoplex can also drive
>>pulse clocks
>>      >out the same jack, so you could sync the arpeggiator to the
>>loop.
>>
>>This sounds amazing !
>
>>Asuming in the "fast" part, the Echoplex would be triggered every
>>500ms, and then suddenly the triggers only come every 10 seconds.
>>Does the Echoplex really wait these 10 seconds until it resets its
>>cycle, or does it only wait during some time "window" ?
>>And what does it play from 0.5s to 10s during the first long
>>loop (there isn't anything stored in this place of the RAM, I asume?)
>>
>>Sorry for the stupid question - I just cannot imagine what would happen.
>
>No, it won't do that I'm afraid. As the clock varies within a certain
>tolerance, the echoplex will stay in sync by retriggering the loop to keep
>it lined up. But if the tempo changes too much, it assumes that you don't
>want to stay in sync anymore and it stops trying. So then the loop just
>plays on in its normal length. The echoplex can't do time stretching or
>tape-speed-changing effects. Still very useful though, because most clocks
>have a lot of jitter and drift around in speed. The sync keep things lined
>up, so that the loop and the sequencer or whatever don't drift from each
>other.
>
>kim
>
>______________________________________________________________________
>Kim Flint                   | Looper's Delight
>kflint@annihilist.com       | http://www.annihilist.com/loop/loop.html
>http://www.annihilist.com/  | Loopers-Delight-request@annihilist.com


______________________________________________________________________
Kim Flint                   | Looper's Delight
kflint@annihilist.com       | http://www.annihilist.com/loop/loop.html
http://www.annihilist.com/  | Loopers-Delight-request@annihilist.com