From: Lee Revell <rlrevell@joe-job.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Pierre Ossman <ossman@cendio.se>,
alsa-devel@alsa-project.org, mzcbylcnhqvb@0pointer.de
Subject: Re: [RFC][PATCH] Transparent network support through polypaudio
Date: Tue, 28 Feb 2006 23:09:13 -0500 [thread overview]
Message-ID: <1141186155.5860.91.camel@mindpipe> (raw)
In-Reply-To: <20060214094741.GA8943@turing.informatik.uni-halle.de>
On Tue, 2006-02-14 at 10:47 +0100, Clemens Ladisch wrote:
> And you're speaking with mplayer's ALSA driver maintainer.
> Is there anything wrong with mplayer? ;-)
Actually, since you mention it...
I still get smoother playback with OSS emulation than mplayer's ALSA
driver. I think it's because the ALSA driver resets the stream on
xruns:
alsa-space: xrun of at least 862.101 msecs. resetting stream3% 7 0
alsa-space: xrun of at least 53.590 msecs. resetting stream.2% 27 0
alsa-play: xrun of at least 5.844 msecs. resetting stream 5.1% 102 0
alsa-space: xrun of at least 442.926 msecs. resetting stream1% 168 0
alsa-space: xrun of at least 50.325 msecs. resetting stream 5.2% 4 0
alsa-play: xrun of at least 15.953 msecs. resetting stream 5.1% 84 0
This seems like a waste of CPU - after all there's nothing we can do but
drop frames if I'm trying to play a movie that my CPU can't quite
handle. Shouldn't mplayer just ignore xruns?
Lee
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-03-01 4:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 14:53 [RFC][PATCH] Transparent network support through polypaudio Pierre Ossman
2006-02-14 9:47 ` Clemens Ladisch
2006-02-14 10:35 ` Pierre Ossman
2006-02-14 14:35 ` Clemens Ladisch
2006-02-14 15:48 ` Pierre Ossman
2006-02-14 20:24 ` latency issue with mplayer ALSA plugin Thierry Vignaud
2006-02-15 9:30 ` Clemens Ladisch
2006-03-01 4:09 ` Lee Revell [this message]
2006-03-01 8:32 ` [RFC][PATCH] Transparent network support through polypaudio Clemens Ladisch
2006-03-01 17:00 ` Lee Revell
2006-03-07 14:01 ` Pierre Ossman
2006-02-15 9:44 ` Pierre Ossman
2006-02-17 19:05 ` Pierre Ossman
2006-02-21 16:15 ` Takashi Iwai
2006-02-21 16:38 ` Pierre Ossman
2006-02-21 16:41 ` Takashi Iwai
2006-02-22 9:48 ` Pierre Ossman
2006-02-22 15:41 ` Takashi Iwai
2006-02-23 13:02 ` Pierre Ossman
2006-02-23 14:34 ` Takashi Iwai
2006-02-24 13:22 ` Pierre Ossman
2006-02-24 13:57 ` Takashi Iwai
2006-02-24 14:03 ` Pierre Ossman
2006-02-27 8:09 ` Pierre Ossman
2006-02-27 19:22 ` Takashi Iwai
2006-02-28 8:11 ` Pierre Ossman
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=1141186155.5860.91.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=mzcbylcnhqvb@0pointer.de \
--cc=ossman@cendio.se \
/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