From: Jan Depner <eviltwin69@cableone.net>
To: Chris Cannam <cannam@all-day-breakfast.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: alsa timer slippage
Date: 14 Dec 2003 08:38:51 -0600 [thread overview]
Message-ID: <1071412731.10990.11.camel@eviltwin> (raw)
In-Reply-To: <200312141434.59757.cannam@all-day-breakfast.com>
Multiple soundcards usually have to use word clock or some proprietary
method of syncing the cards. Usually one card will be the master and
the others slaves. I know you can put up to 4 ST Audio DSP24 cards in
one system and set one up as master. I believe the same is true for the
M-Audio Delta 1010.
As for having a bad timer on a system, I've worked a lot with realtime
systems and sometimes you just get a lemon.
Jan
On Sun, 2003-12-14 at 08:34, Chris Cannam wrote:
> On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote:
> > If I'm not mistaken the timing for your audio is coming from your
> > sound card not your system clock.
>
> Is that so? Obvious though it is, that simply hadn't occurred to me.
>
> I mentally ruled out a hardware problem quite early on because I
> wasn't seeing this problem when using a low-latency kernel on the
> same hardware -- but maybe I just hadn't done enough testing with the
> low-latency kernel. I'll give it another shot.
>
> The other points that brings to mind are, what if you have more than
> one soundcard or no soundcard at all (only say USB devices)? and what
> if the soundcard's just a chip on the motherboard, as mine is --
> wouldn't it get its own timing from the system clock? It's plausible
> that this crappy i810 could have a crappy timer, though this example
> would be unusually crappy.
>
>
> Chris
>
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-12-14 14:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 14:07 alsa timer slippage Chris Cannam
2003-12-14 14:02 ` Jan Depner
2003-12-14 14:27 ` Måns Rullgård
2003-12-14 14:34 ` Chris Cannam
2003-12-14 14:38 ` Jan Depner [this message]
2003-12-14 14:48 ` Chris Cannam
2003-12-14 15:12 ` listing devices Patrick Shirkey
2003-12-14 15:55 ` Patrick Shirkey
2003-12-15 1:14 ` alsa timer slippage Fernando Pablo Lopez-Lezcano
2003-12-14 18:54 ` Chris Cannam
[not found] <E1AVXB7-00025m-JG@sc8-sf-list2.sourceforge.net>
2003-12-15 1:30 ` Pedro Lopez-Cabanillas
2003-12-15 9:16 ` Chris Cannam
2003-12-15 9:53 ` Chris Cannam
2003-12-17 15:13 ` Jaroslav Kysela
2003-12-17 15:44 ` Chris Cannam
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=1071412731.10990.11.camel@eviltwin \
--to=eviltwin69@cableone.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=cannam@all-day-breakfast.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.