Hi, On 5/31/06, Colin f <colin@colinfraser.com> 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]
Message
Re: [analogue-sequencer] Re: Midi Timecode?
2006-05-31 by sascha.matzke@gmail.com
Attachments
- No local attachments were found for this message.