Would you continue to use JACK for audio? That would certainly simplify matters.
I experimented a while ago with packaging JACK for fink and I didn't get very far. I see a couple of options:
- 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.
- Biting the bullet & packaging JACK for fink. It sort of feels weird to me to install a systemwide server just to play Audio on an OS that is perfectly capable of playing Audio in the first place.
- 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 (especially on MacOS X, where a CoreMIDI client can feed into any other CoreMIDI client, and where GarageBand does an OK job for audio).
- Detecting the presence or absence of JACK at runtime, so users have an option.
The MIDI parts of AlsaDriver are pretty substantial, and it might be worth looking more closely at how MIDI setup is done in ArtsDriver (currently non-working, but nonetheless fairly complete from the MIDI perspective). aRts exposes a much simpler MIDI port concept to Rosegarden than we use from ALSA, and the driver is correspondingly much simpler
Yes, one of the first preliminary activities I did was run "wc" on the two drivers :-)
So from a user perspective, are the two drivers equally powerful, or is the ArtsDriver more limited?
Matthias
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
