From: Chris C. <ca...@al...> - 2004-09-16 16:33:11
|
On Thursday 16 Sep 2004 16:55, Matthias Neeracher wrote: > - Going fully native. Using CoreAudio is not all that hard. That > would lose the inter-application pluggability of Jack, though, and > I'm not sure how important that is. I really can't comment on the relevance of JACK for an OS/X user. There is an article about it (JACK on OS/X I mean) in this month's Sound on Sound magazine, which presents it as an interesting system with some potential rather than an absolute must-have. To my mind the pluggability of JACK is a really dramatically impressive thing, but then the platform I use doesn't have so much commercial audio software ready to do impressive things without it. > - Running MIDI-only. I don't understand Rosegarden well enough yet > to get a feeling for how important Audio is vs. MIDI, but my > current instinct is to see it as primarily a MIDI based tool My personal feeling has always been that the most useful aspect of audio in Rosegarden is for synth plugins. I always thought the audio support we had was rather half-cocked before we managed to get synth plugins going. Obviously a MIDI-only version wouldn't be able to use those. > (especially on MacOS X, where a CoreMIDI client can feed into any > other CoreMIDI client Also true of ALSA on Linux, btw. > So from a user perspective, are the two drivers equally powerful, > or is the ArtsDriver more limited? The ArtsDriver is totally non-functional -- in fact it probably doesn't even compile -- so it's hard to compare. It has no support for plugins (the plugin host code itself is independent of driver type, but it still needs to be controlled through the driver), the audio sample playback code was never 100% complete, and I'm not sure recording of either audio or MIDI ever worked correctly. I might be maligning it though -- I think most of the basics were implemented one way or another. MIDI playback certainly used to work fine, but the timing code in AlsaDriver has been restructured a bit since then and it's possible the API might have changed sympathetically to it in a way that could break ArtsDriver. Chris |