From: torbenh <torbenh@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Re: alsa jack plugin
Date: Fri, 19 Nov 2010 14:37:11 +0100 [thread overview]
Message-ID: <20101119133711.GF4646@siel.b> (raw)
In-Reply-To: <20101119131553.GE4646@siel.b>
On Fri, Nov 19, 2010 at 02:15:54PM +0100, torbenh wrote:
> On Wed, Nov 17, 2010 at 03:16:32PM +0800, Raymond Yau wrote:
> > 2010/11/12 Paul Menzel <paulepanter@users.sourceforge.net>
> >
> > > Am Mittwoch, den 10.11.2010, 11:18 +0100 schrieb torbenh:
> > > > On Mon, Nov 08, 2010 at 10:26:47AM +0100, torbenh wrote:
> > > > >
> > > > > the alsa jack plugin has quite some problems:
> > > > > a) does not work correctly with mplayers alsa output. (and quite a few
> > > > > others)
> > >
> >
> > AFAIK, mplayer , aplay and the alsa-jack plugin 1.0.1still working with
> > jack-0.118
> >
> > So you have to tell the jack plugin fail to work from from which version of
> > jack if jack change the protocol
>
> jack did not change the protocoll.
>
> however, the write to the socket fd might block.
> doing potentially blocking things in jacks process callback is not
> legal. (this kind of problems only show under low-latency situations,
> period_size of 128 and lower)
>
> the result of the blocking write is jack kicking the client.
> and just making the fd NONBLOCK, "fixed" the problem.
> (it seems to cause some other problems down the road, since some
> bytes written to the fd get lost)
>
> i would really like to exchange the socket for a signalfd.
> increasing the signal count of the fd would never block.
err... that should read eventfd, obviously :S
>
> (but i am not sure about the requirements, signalfd only exists since
> 2.6.27, and i am not sure, if the old socket based code should be left
> in there as a fallback)
>
>
>
> >
> > The current Documentation of jack plugin "doc/README-jack" has a mistake
> >
> >
> > pcm.jack {
> > type jack
> > playback_ports {
> > 0 alsa_pcm:playback_1
> > - 1 alsa_pcm:playback_1
> > + 1 alsa_pcm:playback_2
> > }
> > capture_ports {
> > 0 alsa_pcm:capture_1
> > - 1 alsa_pcm:pcapture_1
> > + 1 alsa_pcm:pcapture_2
> > }
> > }
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
> --
> torben Hohn
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
torben Hohn
prev parent reply other threads:[~2010-11-19 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 9:26 alsa jack plugin torbenh
2010-11-10 10:18 ` 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 [this message]
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=20101119133711.GF4646@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).