AW: Re: CV Clock to Seqn

[Haible_Juergen#Tel2743]

>  Why build a clock into your sequencer? (I assume we're talking analog
>  sequencers here - right?)
>
>  I mean, you're going to want it in sync with your other gear - right? So
>  much of the time you'll be clocking it from a drum machine trigger signal
>  - or a gate out from a MIDI-CV, or something - don't you think?
>
>  Put your energy into building a separate CV-able LFO module with a pulse
>  output (as well as triangle, saw, etc) - rather than building this into
>  your sequencer. Then I think you'll find that this LFO will get used a
>  lot more on it's own to drive other stuff than it will working as a clock
>  for your sequencer. As far as linear or exp. scaling goes, if you want
>  the LFO to do audio range stuff, it's exponential...
>
>  - CList

Good points, but sometimes you find an internal clock very handy,
especially when you want to use one row for note duration. You
can build in a single switch for this, instead of routing a CV to an
external clock VCO and back.
You need expo control for note duration stuff as well, cause you want
your eighths and quarters stay eighths and quarters when you change
the tempo ... ok, this can work with a linear clock as well, but then you 
need
an extra multiplier ...
In my own system, I use CList's method (external clock) so far, but only
because my current sequencer module is a very small one.
But if I will ever come to build the big one which I have planned, it will
have an internal clock with all extras you can think of. The idea is
to make this clock the master of all - you won't find other clock sources
where you can program a "swing" feelig just with one row of analogue
CV's that easy!
Another idea is making it syncable to an external clock, but setting
the pulse width (= gate time) independently: Sync an internal SAW
 VCO to external pulses, but add an internal loop to keep the SAW
amplitude constant. Then derive the Gate Time from this SAW.

JH.