From: John Rigg <aldev@sound-man.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: pcm_multi broken in alsa-lib - no duplex mode with jackd
Date: Sat, 10 Mar 2007 14:17:13 +0000 [thread overview]
Message-ID: <20070310141713.GA2868@localhost.localdomain> (raw)
In-Reply-To: <s5hslcegynp.wl%tiwai@suse.de>
On Fri, Mar 09, 2007 at 05:38:34PM +0100, Takashi Iwai wrote:
> At Thu, 8 Mar 2007 21:51:28 +0000,
> John Rigg wrote:
> >
> > On Thu, Mar 08, 2007 at 07:58:23PM +0100, Takashi Iwai wrote:
> > > At Thu, 08 Mar 2007 18:16:02 +0100,
> > > Simon Lewis wrote:
> > > > Many JACK users have successfully used the following patch:
> > > >
> > > > http://www.sound-man.co.uk/linuxaudio/pcm_multi-patch
> > >
> > > Well, the patch is no real fix. It's likely a workaround for JACK,
> > > though. Someone has to take time to track down this bug more deeply.
> >
> > True, the patch is just a workaround for JACK. However, I would
> > argue that most users of pcm_multi are probably JACK users.
>
> No, multi plugin is used in many surround PCM definitions as default.
> It's pretty hidden, but multi streams are no rare case.
I hadn't noticed that. Thanks for pointing it out (and thank you for
looking at this problem!)
> > Surely adding code that breaks something for the majority of users (no
> > matter how correct that code is in isolation) is not a good thing.
>
> Sure. However, this code addition was for bugfixes of major other use
> cases like above, IIRC. The regression should be avoided and should
> be fixed. But the point is, we (at least, I) haven't been enough
> informed, unfortunately (or simply burried in a big TODO list :)
>
> Now, let's back to the original problem: Could someone give a pointer
> describing for this problem, or just explain a bit details here?
> I vaguely remember but not precisely at all now...
> I'm willing to dig down after knowing how I can reproduce the bug.
To summarise, using multiple sound cards with pcm_multi and jackd
no longer works in duplex mode ever since extra linking code was
added to pcm_multi.c in alsa-lib-1.0.9rc1.
Trying to start jackd in duplex fails with a poll timeout message.
It still works in playback-only or capture-only modes.
The lack of duplex operation makes overdubbing in a recording studio,
for example, impossible.
A configuration which produces the problem with two ice1712 cards
set up as a 16 channel multi device is shown here:
http://www.sound-man.co.uk/linuxaudio/ice1712multi.html
With the .asoundrc described in the above link the following
command fails with a poll timeout message:
jackd -d alsa -P multi_playback -C multi_capture
The following still work:
jackd -d alsa -P multi_playback
jackd -d alsa -C multi_capture
John
-------------------------------------------------------------------------
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:[~2007-03-10 14:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 17:16 pcm_multi broken in alsa-lib - no duplex mode with jackd Simon Lewis
2007-03-08 17:22 ` Lee Revell
2007-03-08 18:58 ` Takashi Iwai
2007-03-08 21:51 ` John Rigg
2007-03-09 16:38 ` Takashi Iwai
2007-03-09 17:02 ` Achim_Kuntz
2007-03-10 14:17 ` John Rigg [this message]
2007-03-12 23:46 ` Takashi Iwai
2007-03-13 2:01 ` Takashi Iwai
2007-03-13 2:07 ` Takashi Iwai
2007-03-13 9:05 ` Simon Lewis
2007-03-13 9:18 ` Takashi Iwai
2007-03-14 18:41 ` Simon Lewis
2007-03-13 15:34 ` John Rigg
2007-03-11 18:33 ` pcm_multi broken in alsa-lib - no duplex mode Simon Lewis
2007-03-12 11:44 ` Takashi Iwai
2007-03-09 0:57 ` pcm_multi broken in alsa-lib - no duplex mode with jackd Lee Revell
2007-03-08 19:02 ` John Rigg
-- strict thread matches above, loose matches on Subject: below --
2007-03-08 17:17 Simon Lewis
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=20070310141713.GA2868@localhost.localdomain \
--to=aldev@sound-man.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox