From: Paul Barton-Davis <pbd@Op.Net>
To: linux-sound@vger.kernel.org
Subject: Re: Sync Issues (was Re: External MIDI Sync using OSS/Free)
Date: Thu, 28 Oct 1999 14:45:09 +0000 [thread overview]
Message-ID: <marc-linux-sound-94112190919473@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94097346918347@msgid-missing>
> What lowlatency patches?? kernel patches?? That's just ugly. Where
>can I get them?
not ugly! the kernel folks, well Ingo Molnar in particular, recognized
that the kernel wasn't well tuned for low latency requirements. Ingo
believes that his patches will be in kernel 2.4.
look at http://www.gardena.net/benno/linux/audio for more details.
> How can you tell if you've underrun under OSS? Using ALSA, I guess you
>can use it's time stuff to calculate if you've missed a frame, but even
>that seems hacky.
no, ALSA has an ioctl to tell you if had underruns or overruns. its
The Right Way (TM). OTOH, i haven't written any audio programs that
ever use it, because I write them so that if I did have an
{over,under}run, it would mean that some totally catastrophic has
happened. maybe i don't write the right kinds of applications :)
> I don't like using one dsp as the sync master since I always want to be
>able to sync to something external, like MIDI.
if you mean MTC, this simply isn't accurate enough for syncing
soundcards. you can use MTC as a master clock for tempo, but between
MIDI clock messages you will still have to be prepared to do the
actual syncing of soundcards. Given that a MTC messages take on the
order of 1ms to arrive (!), its not a high-quality sync source.
so, i don't think you can "sync soundcards" from MIDI. You can use MTC
to help inform your own sense of the forward passage of time and to
dictate MIDI-related tempo, but thats not the same thing that Benno
was talking about.
--p
next prev parent reply other threads:[~1999-10-28 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-26 21:06 Sync Issues (was Re: External MIDI Sync using OSS/Free) Billy Biggs
1999-10-26 23:21 ` Billy Biggs
1999-10-27 2:16 ` Paul Barton-Davis
1999-10-28 9:22 ` Benno Senoner
1999-10-28 13:47 ` Billy Biggs
1999-10-28 14:45 ` Paul Barton-Davis [this message]
1999-10-28 14:59 ` Billy Biggs
1999-10-28 16:13 ` Paul Barton-Davis
1999-10-28 23:46 ` Benno Senoner
1999-10-29 0:06 ` Benno Senoner
1999-10-30 16:06 ` Jaroslav Kysela
1999-10-30 18:05 ` Jaroslav Kysela
1999-10-30 18:12 ` Billy Biggs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-sound-94112190919473@msgid-missing \
--to=pbd@op.net \
--cc=linux-sound@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox