Analogue-sequencer

Saacha,

I don't disagree with your observation - if, in fact, you have a
device that will calculate tempos referencing an absolute time
reference, then that is ideal - I have that - in my Protools system,
referencing a house sync generator that phase locks everything,
including MTC.  

The problem in my studio is that ACID (or, more specifically, Windows
XP and its drivers) is not as accurate a calculator to convert the MTC
to same tempo as Protools - it is not as stable, even when locked to
this pristine absolute timing source.

So, all I am saying is that assuming that two devices are able to play
at identical tempos is assuming quite a lot.

gary

sascha.matzke@... wrote:
>
> Hi,
> 
> On 5/31/06, Colin f <colin@...> wrote:
> >
> > If you can assume that absolute to relative timebase conversion is
going
> > to
> > be accurate, you would expect the handling of MIDI clock would be
equally
> > accurate too, in which case, you wouldn't be considering using MTC
to get
> > round dodgy MIDI clock handling.
> 
> 
> Not quite - in my understanding - with midi clock you have to depend
on a
> as-close-to-realtime-as-possible behaviour of the midi clock master.
Most
> software sequencers these days produce considerable jitter on their midi
> clock output which is definitely a problem (for instance when I
scroll or
> zoom in Tracktion the midi clock gets noticeable slower and recovers
when I
> stop).
> 
> IMO with MTC this problem could at least be partially solved as MTC
messages
> contain absolute time references which could be used to calculate the
> current tempo independent from interval in which those message are
arriving.
> So yes, the MTC slave would run on it's own tempo, but (dependend on the
> processing power available) would be able to provide better
synchronization
> with devices which are not capable of "realtime" sync output (which
> conceptually would be any software on a "modern" preemptive multitasking
> operation system uncapable of providing realtime scheduling).
> 
> Sascha
> 
> 
> [Non-text portions of this message have been removed]
>