Paul, I know you are busy, but thanks for going over the audio stack framework. See updated diagram...
http://www.networkmultimedia.org/index.html Comments below... On Tue, 2007-08-14 at 16:02 -0400, Paul Davis wrote: > On Tue, 2007-08-14 at 11:42 -0700, John Cherry wrote: > > Based on our discussions at the Collaboration Summit (and a slide from > > Donya), I constructed a little diagram to illustrate the Linux audio > > stack. It may not be completely refined yet, but it should give us a > > common way to reference the layers in the Linux audio stack and to > > discuss standardization points in the stack. > > > > http://www.networkmultimedia.org/index.html > > from the "too busy to even think dept" .... > > a couple of fixes/refinements... > > the diagram should show FFADO/Freebob (Firewire audio) as a similar > 2-layer entity to OSS. arguably it should show it being dependent on the > kernel ieee1394 drivers too. Added both FFADO/Freebob (pronounced: fado) as well as the firewire drivers. > > aRts has been declared dead by its founder/chief developers. Removed aRts unless I hear objections. > > not sure what NMM is, but if its not the same as KDE's "Phonon", you'd > better put Phonon in at the multimedia framework layer. Unless in the > time since I stopped following it, KDE has declared that dead too and > decided to embrace the G in GStreamer. Phonon is an application API, not really multimedia framework. I wedged this between the application layer and the multimedia framework layer. Is Phonon being used outside of the KDE media applications? http://phonon.kde.org/ NMM is Networke-Integrated Multimedia Middleware (http://www.networkmultimedia.org/index.html). I'm not exactly sure what it does, but there is an NMM backend for phonon. :) > > several entities in the "sound server" layer really span the framework > layer as well. JACK in particular dictates a particular style of > application design, and although backends to it exist inside GStreamer, > its primary purpose is to act as a framework for all pro-audio/music > apps, not just as a soundserver. similarly, PulseAudio could be > considered as spanning both layers - it doesn't inherently provide any > services at all, since in many common cases its nothing but a wrapper > API around existing services (JACK, ALSA etc). See how hard it is to put these things in a diagram? See the latest diagram. I let PulseAudio and JACK span the framework and sound servers layers, even though there are plugins for these in the existing frameworks. > > and now, back to the grindstone from whence i came. Thanks. Cranking out a living usually ranks pretty high on Maslow's hierarchy of needs. :) John _______________________________________________ Desktop_architects mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/desktop_architects
