16 Jan
2005
16 Jan
'05
11:37 a.m.
Christoph Eckert writes:
The objection I hear most is that jack doesn't support network audio.
I'd be very interested to hear reactions to that as we are about to have
an Accessibility Workgroup (Free Standards Group) face to face meeting
where accessibility requirements for common audio will be on the table.
He wants to be able to start an audio app and
hear it's
output. He doesn't want to see a dialog box pop-up
exclaiming that the audio device is blocked by another app.
Yeah.
Furthermore, a common interface for audio programmers (»Make
your application a jack client«) would be great. Normal
applications shouldn't access an audio device exclusively.
KDE and Gnome will always have an underlaying soundserver. at
least for portability issues. That's absolutely OK, as long
that their servers talk - maybe - to jack instead of grabbing
the device exclusively.
Best regards & thanks for all thoughts
ce
--
Janina Sajka Phone: +1.202.494.7040
Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
Chair, Accessibility Workgroup Free Standards Group (FSG)
janina(a)freestandards.org http://a11y.org
If Linux can't solve your computing problem, you need a different problem.