On Mon, 14 Jan 2002, Paul Davis wrote: > >I'm not sure if I understand why this would help to position jack as the > >standard linux sound server. It seems like we need to get some kind of > >discussion going between arts and jack developers as arts is in the position > >that jack would like to share. No doubt that jack has something to offer in > >terms of lower latency. Since you are the primary developer of jack, what do > >you think? > > like i said, linux is not an environment where we can force anything > on anyone. artsd does quite a lot more than just provide > approximations of JACK's features. those additional features > apparently made it attractive to the people that have adopted it. it > would be really very difficult to get artsd to support the JACK API > because artsd is another app that uses read/write to schedule > itself. i've discussed the issues involved with the author of arts > several times, and i really can't see it happening. > Well I certainly don't think I can just send a few emails to a mailing list and start things changing. I'm hoping to find some other people that think its a good idea, have some vision of how they would go about resolving the issue and would be willing to continue working on it. To that end as you are quite qualified to speak on this issue, who else should I talk to about this and what direction should be taken? It would be a shame to drop this issue and see arts become the standard sound server without any input from jack or audio users.
> i am also not clear that the GNOME or KDE people would be willing to > support an audio API that requires multithreading. > > also, JACK is not finished yet, which is a major problem. i think that > a finished JACK API, with latency and CPU load performance at least as > good as CoreAudio, plus a half dozen significant and extremely useful > applications will persuade people much more than any of these > technical arguments. > Without the other issues being resolved beforehand I can't see worrying about jack not being complete or as fast as coreaudio when both of these can be achieved in time. > however, don't let any of this stop your advocacy. its always been my > role in life to explain why things won't work, and then end up > somewhat suprised when they do. > > >I wouldn't mind working on some documentation or an example command line jack > >wave player(if such a thing doesn't already exist). > > it exists. andy added JACK support to his excellent alsaplayer several > weeks ago (it has both command line and GU interfaces), and plays all > kinds of things (mp3, many sound file formats, etc.) > > --p > Chris _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
