# Projucer settings for an Auv3 that works as a MIDI plugin for Audiobus **URL:** \ **Category:** MacOSX and iOS\ **Created:** [January 29, 2019, 3:31pm UTC](https://forum.juce.com/t/projucer-settings-for-an-auv3-that-works-as-a-midi-plugin-for-audiobus/31512 "2019-01-29T15:31:37Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![leehu](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/leehu/32/3280_2.png) [@leehu](https://forum.juce.com/u/leehu)\ **Post date:** [January 29, 2019, 3:31pm UTC](https://forum.juce.com/t/projucer-settings-for-an-auv3-that-works-as-a-midi-plugin-for-audiobus/31512/1 "2019-01-29T15:31:37Z")
Hi, does anyone create these and therefore know the correct Projucer settings? Half the time I can’t get them to appear and if they do I just get “Not Supported” when trying to load them. thanks ---
**Author:** ![dstenning](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/dstenning/32/2686_2.png) [@dstenning](https://forum.juce.com/u/dstenning)\ **Post date:** [January 29, 2019, 10:06pm UTC](https://forum.juce.com/t/projucer-settings-for-an-auv3-that-works-as-a-midi-plugin-for-audiobus/31512/2 "2019-01-29T22:06:47Z")
see here. > [@iOS AUv3 version of examples /PluginSamples/Arpeggiator](https://forum.juce.com/t/ios-auv3-version-of-examples-pluginsamples-arpeggiator/24593/26): > > Word of warning: an AUv3 with type kAudioUnitType\_MIDIProcessor (that is to say, an aumf, as opposed to an aufx) won’t pass Review. While aumf is a recognized type in iOS, and some hosts can see it, Garageband ignores aumf AUs, and that is the principle test host the reviewers use in the final step. It will past TestFlight, which is largely automated, but not actual Review. Until they change this, you need to render your MIDI effect as an instrument or aufx (leave the “MIDI input” box in ProJuc… ( short answer - doesn’t look like there’s been much movement on this front ) ---
**Author:** ![crandall1](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/crandall1/32/157_2.png) [@crandall1](https://forum.juce.com/u/crandall1)\ **Post date:** [January 29, 2019, 10:23pm UTC](https://forum.juce.com/t/projucer-settings-for-an-auv3-that-works-as-a-midi-plugin-for-audiobus/31512/3 "2019-01-29T22:23:36Z")
GarageBand (latest version) recognizes aumf now; we’re about to submit an aumf for review. Note that your AUv3 must also pass audio cleanly if it is an effect. Otherwise, many hosts won’t load it. Make sure you’ve removed the mono portions of the channel layout so that it is a true stereo insert effect. Then, hosts that are able to route MIDI to and from inserts will be able to instance it and note it as such. That being said, if you’re making a commercial product that only works in AudioBus, you might as well not bother. For MIDI generators and MIDI-only effects, I would suggest creating them as instruments with MIDI in and out. This will allow most hosts to work with them no matter what their routing. ---
**Author:** ![leehu](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/leehu/32/3280_2.png) [@leehu](https://forum.juce.com/u/leehu)\ **Post date:** [January 30, 2019, 7:37am UTC](https://forum.juce.com/t/projucer-settings-for-an-auv3-that-works-as-a-midi-plugin-for-audiobus/31512/4 "2019-01-30T07:37:52Z")
Found my issue - MIDI in AUv3 needs iOS 11.0 or later which was causing the problems. Maybe Projucer should flag AUv3 that specify MIDI output that are set prior to iOS 11.0. ---
**Author:** ![rlg](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/rlg/32/7362_2.png) [@rlg](https://forum.juce.com/u/rlg)\ **Post date:** [March 13, 2019, 8:11pm UTC](https://forum.juce.com/t/projucer-settings-for-an-auv3-that-works-as-a-midi-plugin-for-audiobus/31512/5 "2019-03-13T20:11:16Z")
This! I was banging my head against the wall trying to figure out why MIDI wouldn’t work, until setting the Deployment Target to 11.0 fixed it.