From: John Rigg <ad@sound-man.co.uk>
To: Marc Brooker <marcbrooker@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Sample Rate Conversion Quality in ALSA
Date: Mon, 21 Aug 2006 21:15:06 +0100 [thread overview]
Message-ID: <20060821201506.GA3729@localhost.localdomain> (raw)
In-Reply-To: <b5ee41f40608211207o165b7e20qb40625ad17065d18@mail.gmail.com>
On Mon, Aug 21, 2006 at 09:07:31PM +0200, Marc Brooker wrote:
> On a related note, on an Athlon64 3200+ running Ubuntu Dapper for i386
> with backported alsa-libs 1.0.11 and alsa-plugins 1.0.11 (with
> samplerate plugin) cpu usage figures (while playing a VBR mp3 using
> gstreamer):
> standard ALSA linear: 2%
> samplerate: 6%
> samplerate_medium: 9%
> samplerate_best: 20%
>
> From this it seems that samplerate_best is too costly, but samplerate
> and samplerate_medium would be usable on most modern hardware.
If you're running an i386 distro you're only using half of the
Athlon64's registers. It would be interesting to see if that
samplerate_best CPU load is reduced in 64-bit mode.
John
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
prev parent reply other threads:[~2006-08-21 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 10:16 Sample Rate Conversion Quality in ALSA Marc Brooker
2006-08-21 12:45 ` James Courtier-Dutton
2006-08-21 12:54 ` Takashi Iwai
2006-08-21 15:05 ` Marc Brooker
2006-08-21 15:16 ` Takashi Iwai
2006-08-21 15:59 ` Lee Revell
2006-08-21 16:06 ` Takashi Iwai
2006-08-21 13:02 ` Marc Brooker
2006-08-21 15:03 ` John Rigg
2006-08-21 19:07 ` Marc Brooker
2006-08-21 19:15 ` Lee Revell
2006-08-21 20:16 ` Marc Brooker
2006-08-21 20:15 ` John Rigg [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=20060821201506.GA3729@localhost.localdomain \
--to=ad@sound-man.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=marcbrooker@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.