Alternatively, ‘aumi’ plugins are pure MIDI processor plugins. So if you already have a working infrastructure for AU instruments, you’re 80% done.Įdit Feb.’18: AU MIDI plugins can have two different identifiers: ‘aumu’ (like regular AU instruments) can combine audio output with MIDI output. They provide audio I/O buses (which they can ignore) and expect render calls at frequent intervals. The Rozeta sequencer suite is one first practical example of where I see lots of potential for MIDI AU plugins.ĪUv3 MIDI plugins are essentially identical to normal AU instrument plugins. In my opinion an even richer application angle than the one shown in the WWDC video as it supports my personal belief that musicians should be able to mix and match sequencers and sound sources – rather than having a sequencer tied to a sound source.
However, the feature also opens doors for custom sequencers and other MIDI generators that don’t necessarily need their own sound source or synth engine. Users can then record their performance in any compatible AU host. (Jump to 39:00 to hear the explanation and 44:00 to see a demo)Īpparently, Apple’s main use case for the feature was to support AU instruments that have their own virtual keyboard (or other performance UI). It was first demonstrated in Apple’s WWDC’17 CoreAudio video: One of the most interesting music related novelties quietly introduced in iOS11 is the ability for AUv3 Extension plugins to send MIDI messages to their host.
I have made some amendmends to the text below to reflect these new insights. It assumes familiarity with ‘normal’ AUv3 plugin development.Įdit Feb.’18: Apple have clarified some of the open questions I had. AUv3 MIDI Plugins for iOS Developers Abstract: this text provides tips, background information and considerations for iOS developers wishing to create AUv3 MIDI plugins or to support MIDI plugins in AU host software.
0 kommentar(er)
