From: Takashi Iwai <tiwai@suse.de>
To: John Rigg <ad@sound-man.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: pcm_multi poll timeout error
Date: Mon, 07 Aug 2006 11:38:57 +0200 [thread overview]
Message-ID: <s5hd5bcsx5a.wl%tiwai@suse.de> (raw)
In-Reply-To: <20060806150349.GA3461@localhost.localdomain>
At Sun, 6 Aug 2006 16:03:49 +0100,
John Rigg wrote:
>
> On Tue, Aug 01, 2006 at 12:43:44PM +0200, Takashi Iwai wrote:
> > At Mon, 31 Jul 2006 22:04:26 -0400,
> > Lee Revell wrote:
> > >
> > > On Mon, 2005-12-12 at 12:31 +0100, Takashi Iwai wrote:
> > > > At Fri, 9 Dec 2005 20:15:02 +0000,
> > > > John Rigg wrote:
> > > > >
> > > > > 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.
> > > >
> > > > Hm, the question is what the cable-sync really does. Basically the
> > > > linked PCM streams in ALSA are just for trigger actions,
> > > > i.e. start/stop streams. The others are not really related.
> > > >
> > > > However, the recent changes of multi pcm tries to use only one pollfd
> > > > as a master, and this seems broken in your case. Or, it's really the
> > > > matter of linked streams.
> > > >
> > > > Will come back to this issue later...
> > > >
> > >
> > > Takashi-san,
> > >
> > > I'm not sure I fully understand - are you saying JACK is broken or that
> > > it's an ALSA bug?
> >
> > It's an "undefined behavior".
> > I suppose that software-linked PCM streams do right thing, but we need
> > to investigate the detail.
> >
> > John, could you check whether the problem still appears with the
> > latest ALSA HG version, especially with alsa-lib? I remember that
> > some fixes have been done on multi plugin.
>
> The problem still appears with alsa-lib-1.0.12rc2 version. There are
> no changes in pcm_multi since 1.0.11.
The change was not in pcm_multi.c but in pcm_hw.c.
But anyway this seems irrelevant.
> Is there an easy way to view changes in the hg repository, ie. an
> equivalent to the old cvs viewer on Sourceforge?
> I'm testing this on my production system, which is a little disruptive,
> so it would be convenient to be able to check for changes in the code before
> trying it.
Try access to http://hg-mirror.alsa-project.org from your browser.
Takashi
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-08-07 9:38 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
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 [this message]
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=s5hd5bcsx5a.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=ad@sound-man.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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