alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: torbenh <torbenh@gmx.de>
To: alsa-devel@alsa-project.org
Subject: alsa jack plugin
Date: Mon, 8 Nov 2010 10:26:47 +0100	[thread overview]
Message-ID: <20101108092647.GS4410@siel.b> (raw)


the alsa jack plugin has quite some problems:
a) does not work correctly with mplayers alsa output. (and quite a few
   others)
b) it includes the pid in its clientname.
c) it requires port connections.
d) jack client is deactivated when alsa stream is not active.
e) no way to set the jack clientname

the master branch on git://hochstrom.endofinternet.org/alsa-plugins
carries fixes for a, b and e.

c and d have their own branches.

i have seen a few problems with making the write end of the fd
non-blocking. would it be possible to use eventfd(2) for this ?


-- 
torben Hohn

             reply	other threads:[~2010-11-08  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08  9:26 torbenh [this message]
2010-11-10 10:18 ` alsa jack plugin torbenh
2010-11-11 22:11   ` Paul Menzel
2010-11-17  7:16     ` Raymond Yau
2010-11-19 13:15       ` torbenh
2010-11-19 13:37         ` torbenh

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=20101108092647.GS4410@siel.b \
    --to=torbenh@gmx.de \
    --cc=alsa-devel@alsa-project.org \
    /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;
as well as URLs for NNTP newsgroup(s).