From: Zsolt Barat <barat@medien.uni-weimar.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Problem with RME 9632 and Plug
Date: Wed, 04 Aug 2004 17:03:31 +0200 [thread overview]
Message-ID: <4110FAC3.3000009@medien.uni-weimar.de> (raw)
In-Reply-To: <200408041301.i74D1omu022274@localhost.localdomain>
Paul Davis wrote:
>Yeah, but bio2jack is a (working) hack and half. And it doesn't
>support lowlatency work properly either, because the thread that
>*really* does audio isn't scheduled as part of the JACK graph and
>doesn't get SCHED_FIFO status. I see this in xmms all the time when I
>do a multiway compile - JACK has no (or almost no) xruns, but the
>audio in xmms skips because the "feeder" thread doesn't get scheduled
>in time to fill the intermediate buffer.
>
>
>
mplayer_g2 will probably change its architecture, so a poll like
behaviour like jack uses will be possible. developers are still welcome
to port (write) ao_jack for mplayer_g2 though.
on the other side, adding low latency features to mplayer aren't really
possible, cause mplayer is designed intentionally as a movie player, so
while you watching movies you will never get low latency audio. adding
some low-lat features when it will be used as stand-alone audio app
could be possible. but there are several audio-only-apps which already
have full jack and alsa support (alsaplayer) so i don't really see a
need for blown up low-lat audio support in mplayer.
regards
Zsolt
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-08-04 15:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 13:46 Problem with RME 9632 and Plug Ed Wildgoose
2004-08-03 14:36 ` Paul Davis
2004-08-03 15:44 ` Ed Wildgoose
2004-08-03 16:21 ` Ed Wildgoose
2004-08-03 17:32 ` Paul Davis
2004-08-03 23:55 ` Ed Wildgoose
2004-08-04 0:18 ` Paul Davis
2004-08-04 7:39 ` Jaroslav Kysela
2004-08-04 9:35 ` Ed Wildgoose
2004-08-04 10:20 ` Jaroslav Kysela
2004-08-04 11:16 ` Ed Wildgoose
2004-08-04 12:24 ` Paul Davis
2004-08-04 12:43 ` Ed Wildgoose
2004-08-04 13:01 ` Paul Davis
2004-08-04 13:31 ` Ed Wildgoose
2004-08-04 15:13 ` Zsolt Barat
2004-08-04 15:03 ` Zsolt Barat [this message]
2004-08-04 15:24 ` Paul Davis
2004-08-04 13:35 ` James Courtier-Dutton
2004-08-04 9:44 ` Takashi Iwai
2004-08-04 9:55 ` Ed Wildgoose
2004-08-04 10:21 ` Ed Wildgoose
2004-08-04 10:20 ` Jaroslav Kysela
2004-08-04 10:27 ` Takashi Iwai
2004-08-04 10:56 ` Jaroslav Kysela
2004-08-04 11:15 ` Takashi Iwai
2004-08-04 10:30 ` Ed Wildgoose
2004-08-04 10:53 ` Jaroslav Kysela
2004-08-04 11:21 ` Ed Wildgoose
2004-08-04 9:52 ` Ed Wildgoose
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=4110FAC3.3000009@medien.uni-weimar.de \
--to=barat@medien.uni-weimar.de \
--cc=alsa-devel@lists.sourceforge.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.