From: Takashi Iwai <tiwai@suse.de>
To: Eduard Hasenleithner <ehasenle@spamcop.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ice1712 pro mode and general playback performance (was alsaplayer)
Date: Wed, 23 Jul 2003 10:24:12 +0200 [thread overview]
Message-ID: <s5hu19dfy6r.wl@alsa2.suse.de> (raw)
In-Reply-To: <1058903481.26606.24.camel@boundary.priv>
At 22 Jul 2003 21:51:21 +0200,
Eduard Hasenleithner wrote:
>
> The only user-space solution to this problem is a deamon
> which runs with real-time priority and client programs can
> connect to it. "jack" is one example for this kind of software
> as it also provides this real-time capability. But you have
> to either run all your audio applications as root or apply
> a kernel patch which both enables a considerable security risk.
yes, a kind of daemon would be needed.
btw, it's the feature of jack to force all applications to run in
rt priority. this is designed to get the exact synchronization.
in your case, only the sound daemon needs higher priority.
hence, even esound or arts may help.
hmm, it's worthy to try once esound or arts with rt-priority and with
enough large buffers.
> I do not request a "kernel pre-buffer" solution to be
> included into the alsa package. But I want to hear if
> my conclusions are right that with the current linux
> (2.4.x) infrastructure I cannot use my ice1712 soundcard
> for the same tasks as I used with my onboard sound chip.
i agree here.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
prev parent reply other threads:[~2003-07-23 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 19:51 ice1712 pro mode and general playback performance (was alsaplayer) Eduard Hasenleithner
2003-07-23 8:24 ` Takashi Iwai [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=s5hu19dfy6r.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ehasenle@spamcop.net \
/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.