From: John Rigg <ad@carbon-black.co.uk>
To: Jeremy Hall <jhall@maoz.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@lists.sourceforge.net
Subject: Re: pcm_multi poll timeout error
Date: Fri, 9 Dec 2005 20:15:02 +0000 [thread overview]
Message-ID: <20051209201502.GA3751@localhost.localdomain> (raw)
In-Reply-To: <200512091755.jB9HtR5i008279@sith.maoz.com>
On Fri, Dec 09, 2005 at 12:55:27PM -0500, Jeremy Hall wrote:
> In the new year, John Rigg wrote:
> > On Fri, Dec 09, 2005 at 12:40:05PM +0100, Takashi Iwai wrote:
> > > The link_fd returns the file descriptor for linking multiple PCM
> > > streams. If you comment it out, it means that no link is possible.
> > > It means that snd_pcm_link() didn't do anything in fact after your
> > > patch.
> >
> > I can't understand why this works after my patch broke snd_pcm_link .
>
> It probably works because the rme cards are synced by an external means
> such as word clock or the entity they are connected to has master sync
Makes sense. So, the situation appears to be:
1 - The link code is unnecessary for duplex operation of multiple
clock-synchronised sound cards with jackd.
2 - It breaks the above when present.
John
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-09 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 19:13 pcm_multi poll timeout error John Rigg
2005-12-09 11:40 ` Takashi Iwai
2005-12-09 17:16 ` John Rigg
2005-12-09 17:55 ` Jeremy Hall
2005-12-09 20:15 ` John Rigg [this message]
2005-12-12 11:31 ` Takashi Iwai
2006-08-01 2:04 ` Lee Revell
2006-08-01 10:43 ` Takashi Iwai
2006-08-01 22:58 ` John Rigg
2006-08-06 15:03 ` John Rigg
2006-08-07 9:38 ` Takashi Iwai
2006-08-08 6:35 ` Clemens Ladisch
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=20051209201502.GA3751@localhost.localdomain \
--to=ad@carbon-black.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jhall@maoz.com \
--cc=tiwai@suse.de \
/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.