18 Jun
2005
18 Jun
'05
4:58 a.m.
I agree with Rui,
arts piped into jack is probably the best solution currently.
And when doing paranoid low latency audio work just kill artsd as Rui said.
I'm not a big user of consumer audio apps (eg mailer that emits
BOING.WAV) but
I guess due to certain apps being KDE centric and some GNOME centric I
guess that
some GNOME apps still require esd running ?
What's the current "coding standard" for consumer audio apps that should
work in both
KDE and GNOME enviroments ? Use ALSA directly, support both artsd/esd etc ?
I hate fragmentation and I think there should be only one audio server
for consumer apps
even if it's decoupled from jack (eg artsd that can output either to
ALSA or to jack)
but the question is who is going to give up their audio server for the
competition.
(eg gnome using arts) or do you think KDE and GNOME will over time agree
to a common
consumer audio server ? (eg this polypaudio)
How does windows handle such stuff ? You simply write MME/WDM audio apps
and
windows applies transparent software mixing to each API ?
cheers,
Benno
http://www.linuxsampler.org
Rui Nuno Capela wrote:
I guess we are
in need of some guys who help making JACK ready
for the desktop.
If you're on KDE 3.3+, try these Setup/Options on qjackctl:
[X] Execute script on Startup:
`artsshell -q terminate`
[X] Execute script after Startup:
`artsd -F 4 -S 1024 -a jack -m artsmessage -c drkonqi -l 3 -f &`
and optionally, for completeness sake:
[X] Execute script on Shutdown:
`artsshell -q terminate`
[X] Execute script after Shutdown:
`killall artsd`
From then on, enjoy your jackified KDE desktop
thru artsd :)
Cheers.