Your message dated Tue, 12 Jan 2010 10:04:43 +0100
with message-id <20100112090442.gx2...@ltw.loris.tv>
and subject line Re: Bug#564828: "subgraph starting at ... timed out" after 
about five seconds of audio playback in mplayer
has caused the Debian Bug report #564828,
regarding "subgraph starting at ... timed out" after about five seconds of 
audio playback in mplayer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
564828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jackd
Version: 0.109.2-5

Stock lenny system.  jackd started with "jackd -d alsa -d hw:0 -r
44100" ALSA set up to use jack output as in
<http://alsa.opensrc.org/index.php/Jack_(plugin)>.  mplayer defaults
to using ALSA to output.  After a few seconds of playback (of a WAV
file, though it does the same with FLAC and MP3 files), it hangs (does
not respond to 'q' to quit), and jackd produces the following message
on its terminal:

        subgraph starting at alsa-jack.jackP.8292.0 timed out 
(subgraph_wait_fd=7, status = 0, state = Running)

With 'mplayer -ao jack', on the other hand, everything works fine.

Ideas?

Thanks,
Jonathan

libasound2-plugins is version 1.0.16-1+b1
mplayer is from debian-multimedia.org, version 1:1.0.rc2svn20080706-0.1lenny1



--- End Message ---
--- Begin Message ---
On Mon, Jan 11, 2010 at 10:39:45PM -0600, Jonathan Nieder wrote:

Hi!

> Package: jackd
> Version: 0.109.2-5

First, this jackd version is old, really old. Nobody will ever fix it,
the fix is actually to update to current jackd.

> Stock lenny system.  jackd started with "jackd -d alsa -d hw:0 -r
> 44100" ALSA set up to use jack output as in

So what do we see here? Very old jackd without realtime priorities and
the default buffersize. You could try to add "-p 2048" or any other
value, maybe also -P. See jackd -d alsa -h

> <http://alsa.opensrc.org/index.php/Jack_(plugin)>.  mplayer defaults
> to using ALSA to output.  After a few seconds of playback (of a WAV

And here we go. The ALSA-jack-plugin is known to be a little bit
unstable.

> With 'mplayer -ao jack', on the other hand, everything works fine.
> Ideas?

Yeah, don't use mplayer with ao alsa when you really want ao jack. jackd
is for pro-audio, think of recording studios, and the alsa-jackd-bridge
is just a little hack to enable non-jackified apps to output in these
environments.

In general, update jackd, run it with realtime prios, update the
alsa-jackd bridge or replace it by pulseaudio. (I see exactly the same
problems with the alsa-jackd bridge, that's why I switched to
pulseaudio)

In current Debian unstable, we have all these things, jackd operates
the pro-audio gear and pulseaudio-module-jack bridges between "consumer
apps" and the pro-audio jackd.

To quote jackd author Paul Davis: jackd is not intended to be a generic
desktop sound server.


HTH

-- 
mail: a...@thur.de      http://adi.thur.de      PGP/GPG: key via keyserver


--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers

Reply via email to