Subject: RE: [linux-audio-dev] midi events in jack callback (was: Reborn)
From: mikko.a.helin_AT_nokia.com
Date: Fri Aug 16 2002 - 17:52:03 EEST
So we need something which handles the timing like the DirectMusic(tm) in the Linux kernel. How about the ALSA project, could they put this stuff there? I mean even DirectMusic can synchronize it's master clock to audio clock, it surely must be possible also in Linux? Funny someone mentioned the MIDI clock, even the brand new Cubase SX (latest ver. 1.02) can't output solid MIDI clock, people on Cubase forum are complaining that they can't use external MIDI synced arpeggiators and sequencers. It' may though be a DirectMusic issue (in SX Steinberg decided to forget the MROS and go for DirectMusic API - synching ASIO with DirectMusic must be a pain in someone's ass).
-Mikko
> -----Original Message-----
> From: ext Paul Davis [mailto:pbd_AT_op.net]
> Sent: 16. August 2002 17:35
> To: linux-audio-dev_AT_music.columbia.edu
> Subject: Re: [linux-audio-dev] midi events in jack callback (was:
> Reborn)
>
>
> >> none of this, alas, addresses the more fundamental
> question of how to
> >> do the timing correctly. without something like the
> hard-timer patch,
> >> its more or less impossible to do MIDI sequencing correctly under
> >> linux. of course, you can do it "well enough" with existing
> >> mechanisms, but the reason most people haven't noticed this yet is
> >> that there is fairly strong division between audio + MIDI software.
> >> its only when *this* MIDI event needs to be delivered at
> audio frame N
> >> that you start to see the problems. there is no way to accurately
> >> schedule anything under Linux with hard-timers unless by accurately
>
> ^^^^
> OOPS. make that "without"
>
>
> >> you mean either "resolution = HZ" or "resolution = RTC Hz" or
> >> "resolution = audio interrupt frequency".
> >
> > What do you think the solution is? Someone on #lad mentioned that
>
> the hard-timers patch or something like it needs to go into
> the kernel.
>
> >ardour apparently outputs MIDI clock sync. How do you swing
> that one?
>
> no, it outputs MIDI Time Code, which is an entirely different beast.
> it has nothing to do with event scheduling, since its resolution is a
> video frame (about 1/30 sec). many people seem to confuse MIDI clock
> with MIDI time code - they are not related in any way whatsoever. in
> addition, ardour's MTC output is not "lockable" - it happens in a
> bursty way that other MTC devices will not lock to, though the
> reasonable ones will follow it (they will sync, but not lock).
>
> > Right now, all of my MIDI messages are output with
> reasonably constant
> >latency clocked from a remote MIDI clock: effectively software MIDI
> >thru. This + close-to-realtime audio means that my PC will hopefully
> >output correct on both MIDI and audio in sync with constant latency,
>
> its only an issue when "correct" means "within less than a
> millisecond". many proprietary MIDI devices these days claim to be
> accurate to within the MIDI data rate (about 0.33msecs).
>
> the truth is that right now, it doesn't make much difference because
> most destinations for the message will take at least 1msec to respond
> to the data. but if you want "correct", you're stuck on Linux without
> the hard-timers patch.
>
> >using my drum machine or hard disk recorder as the clock source.
>
> these devices provide a very low resolution clock, and it can't be
> used to schedule MIDI data, only to provide a low resolution
> positional reference.
>
> --p
>
>
>
>
This archive was generated by hypermail 2b28 : Fri Aug 16 2002 - 17:50:53 EEST