From: Simon Lewis <simon.lewis@mnet-online.de>
To: alsa-devel@lists.sourceforge.net
Subject: pcm_multi broken in alsa-lib - no duplex mode with jackd
Date: Thu, 08 Mar 2007 18:17:30 +0100 [thread overview]
Message-ID: <45F0452A.40205@mnet-online.de> (raw)
Dear ALSA Developers
When I attempted to combine several device drivers using the pcm_multi
function in .asound.conf I learned the hardway that pcm_multi doesn't
work in duplex mode with jackd. Apparently pcm_multi was broken in
alsa-lib 1.0.9rc1 and has never been fixed.
Many JACK users have successfully used the following patch:
http://www.sound-man.co.uk/linuxaudio/pcm_multi-patch
I have since learned that many studio64 users have been bitten by this bug.
Please, please, please add the above patch to version 1.014 of ALSA libs
before they are finally released as stable.
With many thanks, Simon.
-------------------------------------------------------------------------
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 reply other threads:[~2007-03-08 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 17:17 Simon Lewis [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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-09 0:57 ` Lee Revell
2007-03-08 19:02 ` John Rigg
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=45F0452A.40205@mnet-online.de \
--to=simon.lewis@mnet-online.de \
--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 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.