From: Jasiu <kiputnik@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Broken JACK plugin in alsa-plugins and a way to fix it.
Date: Sat, 19 May 2007 16:54:45 +0200 [thread overview]
Message-ID: <f13492b00705190754x6ddae848j8ef07382ac49a544@mail.gmail.com> (raw)
In-Reply-To: <f13492b00705190644s51a0cc99g95e676257a4e9044@mail.gmail.com>
Sorry, it seems that while that fixed the problem for some apps
(notably mplayer) it broke a few others. (amarok, artsd) So please
just ignore my remake about the fix for now. It would be nice if
someone could explain to me why that bug happens, because currently
I'm more and more confused about that.
On 5/19/07, Jasiu <kiputnik@gmail.com> wrote:
> Hi.
>
> I want to note that JACK plugin in alsa-plugins in broken. (At least
> on my two systems.) It just plays for a few seconds and then stops
> hanging the application that was sending data to it. When it hangs
> jackd spits out this:
>
> subgraph starting at alsa-jack.jackP.3635.0 timed out
> (subgraph_wait_fd=7, status = 0, state = Running)
>
> What I want to note is that there is a fix to that and I would like it
> to be included in the tree. I'm not sure if it doesn't break anything
> else, but it works for me ok.
>
> Open pcm_jack.c and on the line 146 you'll find:
>
> write(jack->fd, buf, 1); /* for polling */
>
> Deleting this seems to get rid of the problem.
> So please if you can patch this out. (I didn't make a patch myself
> since this is so tiny fix that it isn't really worth.)
>
> Cheers.
>
next prev parent reply other threads:[~2007-05-19 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 13:44 Broken JACK plugin in alsa-plugins and a way to fix it Jasiu
2007-05-19 14:54 ` Jasiu [this message]
2007-05-21 15:43 ` Takashi Iwai
2007-05-22 12:27 ` Jasiu
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=f13492b00705190754x6ddae848j8ef07382ac49a544@mail.gmail.com \
--to=kiputnik@gmail.com \
--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).