Re: any AudioUnit instruments supporting kMusicDeviceProperty_MIDIXMLNames
Re: any AudioUnit instruments supporting kMusicDeviceProperty_MIDIXMLNames
- Subject: Re: any AudioUnit instruments supporting kMusicDeviceProperty_MIDIXMLNames
- From: andre <email@hidden>
- Date: Mon, 04 Jul 2011 00:01:19 +0200
On 03.07.2011, at 22:14, Paul Davis wrote:
Further, in 2008, bill stewart @ apple said:
-------------------------------
2/ what is exactly kMusicDeviceProperty_MIDIXMLNames and how does
it work?
MIDI XML is a MIDI.org specification for using an XML file to express
the capabilities of a MIDI device (such things as patch names, drum
key assignments, etc). We had at some point the notion of having AU's
with sample/patch banks use this spec as a means of informing hosts
what they had. However, the custom view for an AU really obviates the
need for this, and we've not explored a generic view for this kind of
au. So, there doesn't seem to be a need for this at this point.
Which is a shame, IMO.
I understand that a typical DAW with a simple record-->playback--
>process workflow does not necessarily need to know anything about a
plugin, because it requires the user to take full responsibility for
using the sounds in the right way. The plugin is a black box and MIDI
content fed into it is static.
However, there are other types of hosts that need to know any possible
detail about the capabilities and patches of an instrument (patch
name, selection message, pitch range, instrument type, timing,
articulations, etc), because they are using the instrument in a more
intelligent way, generating MIDI content that is taylored to the
instrument (or a section of multiple instruments).
The recent advent of UI integration of articulations comes to my mind,
but also the (semi)automated composition and arrangement of scores.
We are using the MIDNAM XML format for our host (import/export only,
though) and would much like to extend it by the above mentioned
attributes. Especially for large sound libraries, a comprehensive XML
definition of its contents would be extremely useful for any kind of
host that goes beyond static audio production.
Lacking the general availability of such descriptions for most (if not
all) instruments and sound libraries, we are having a rather hard time
telling our customers they have to create one themselves before they
can actually use the instrument.
If there are other host developers who would like to see a wider
support for XML instrument descriptions, feel free to contact me off
list. I'd love to actively support this and contribute to it.
Andre
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden