MIDI over USB

[fr810]

@leehu

maybe this is because iOS MIDI is mulit-ported like OSX and Android isn’t like Windows

Yes that’s spot on. I forgot about that. We had a similar issue with ROLI’s NOISE app on Android: you can only open midi devices once.

So the standalone target is a simple standalone app to get you going quickly. It will simply connect all midi devices to your AudioProcessor - so without even opening any MidiDevices in your own code, you should be getting the midi into your AudioProcessor via the processBlock callback. You don’t need to use any AudioDeviceManager or anything. Check-out the JuceDemoPlugin or the AUv3Synth samples.

If you need something more custom [1] then you may need to roll your own custom app for your plugin. See option number 2 in this post for more information:

Styling the Standalone plugin window?

There are two approaches here that you could do: you use the standalone app that JUCE already provides for you. Then you don’t need any macros etc. This is the approach that JUCE’s audio plugin demo uses. If you want different behaviour in your standalone app (compared to your plug-in), you can use: PluginHostType::getPluginLoadedAs() == AudioProcessor::wrapperType_Standalone For example, you could use this in a parentHierarchyChanged callback in your plug-ins editor to change the window st…

[1] Let us know why the midi handling of the default standalone target app does not work for you. Maybe we can add it to JUCE.