Is it valid to add an iOS config to a VST?

MacOSX and iOS
21

But I don’t understand why you are getting that assertion. The AudioProcessorPlayer will call reset accordingly. See this line here.

This is why I’ve asked if you also see this in the “audio plugin demo” so that I can have a go at reproducing this. For me, the “audio plugin demo” works fine on iOS.

22

ok, got ya… i’ll try the audio plugin demo shortly and see if I get the same result… I’ll also check whether that function is being called correctly in my plugin… cheers

23

Confirmed that the AUV3 is now building OK even though 10.8 is selected as target platform… thanks

24

My plugin is returning at this point so it’s never calling reset():

const String newInputDeviceName (numInputChansNeeded == 0 ? String() : newSetup.inputDeviceName);
const String newOutputDeviceName (numOutputChansNeeded == 0 ? String() : newSetup.outputDeviceName);

String error;
AudioIODeviceType* type = getCurrentDeviceTypeObject();

if (type == nullptr || (newInputDeviceName.isEmpty() && newOutputDeviceName.isEmpty()))
{
    deleteCurrentDevice();

    if (treatAsChosenDevice)
        updateXml();

    return String();
}

In the demo plugin, newOutputDeviceName is “iOS Audio”, for my plugin it is empty… Wondering whether this is something to do with the fact I’ve declared it as a midi effect plugin?

25

Oh yes, Midi effect plug-ins will not work on iOS - they are not yet supported by AUv3 in iOS. We need to add a Projucer warning about this.

26

ah, ok. I’ve unchecked this and I still get the same issue of no output device specified - where does this get set?

Also, I have channel configuration set to 1,1… do I need to set this to be empty?