Yahoo Groups archive

PLAN B analog blog

Index last updated: 2026-04-28 23:10 UTC

Message

Re: m28 tap clock question/problem

2007-10-20 by (i think you can figure that out)

Running the risk of sounding like a smartass...

It's not a problem...it's a feature???

Phil Gallo and I have spent many hours working on this, and we did
improve it since the prototype by doubling the speed of the crystal
that drives the micro, but the bottom line is in order to upscale, the
processor has to determine the interval of the base frequency between
incoming triggers and it needs to take system cycles to do that. 
That's what you're experiencing and these are the pitfalls of a
mutliply by 2 and 3 function when dealing with realtime events.

The interval is the same as what it's receiving, it just lags behind a
few steps.  This is why the input is called 'Phase lock' and not
'external clock'

My suggestion:  use the M28 as the master clock.  Run the Oberkorn
from it.

Phil and I are looking into an expander for the m28 - a simple analog
clock to midi clock converter so that external midi devices can be
synced easily to the goings-on of the M28.




--- In PLAN_B_analog_blog@yahoogroups.com, "michaeltritter"
<mtritter@...> wrote:
>
> 
> having trouble syncing the tap clock to external sources (e.g.
analogue solutions oberkorn 
> sequencer) via the phase lock... it always seems to go slowly in and
out of sync. quite a nice 
> effect actually, but not necessarily the desired one.
> 
> anyone...?
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.