Juan Linietsky wrote: > I'm interested in extending the api only for retrieval of info about > bank names/info, patch names/info and controller names. Info would > default to some midi standard defaults. What do you have in mind for > an instrument api?
I don't have anything in mind for the instrument API - I'm just curious really. >From our app's perspective we want to be informed about possible instruments sometimes and prescriptive the rest of the time. I'm wondering actually how much you really need at the driver level for this kind of thing? Once you've worked out the device you're talking to its up to the user (or other enthusiastic individuals) to create templates of device specific MIDI mappings to allow the application's presentation of the features. It would be nice to have self describing MIDI devices but this isn't really part of the standard is it? And (again) how would you be consistent across external and soundcard devices? We already see this kind of distinction in OSS and ALSA and one thing any instrument interface is going to want is consistency of approach. Anyway, just some thoughts. For the moment I'm going to implement our ALSA layer such that it reports devices, synths, channels etc. and creates an Instrument map for the application to use. We'll see how we get on with that approach. R -- http://www.all-day-breakfast.com/rosegarden http://www.bownie.com _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
