That new keyboard is WAY nicer. Thanks for adding that! Today tried for hours to get a recipe from the Cookbook to function with this project. Previously did the AU, but today was going for the AU and the app also (partially to avoid the App Store Connect hassles and partially because thought it would be MUCH easier than it was). An oscillator (not an EXS sampler) edition of this project template would certainly be a nice and appreciated addition. I imagine that is likely pretty easy when somebody is very comfy with how AudioKit 5 does things and how the MIDI system of that framework is built. If there is an easy way to slap an oscillator into that, certainly would like to know how. Basically there weren't compatible noteOn methods seemingly. I switched it from MIDISamplerInstrument to MIDIInstrument with the VocalTract and thought that should do it, but without a compatible noteOn it was a bigger challenge than anticipated. Anyway, thanks in advance for posting a short how-to on converting that to oscillator compatibility or for posting an oscillator example!

PS: "Modular, modular, modular" is a nice software architecture CHANT for such a framework. Modular architecture is easier to use and maintain. I am way into modular product design though.

Thanks for posting that and that tutorial! Any recommendations on how to reduce aliasing in the audio when using Audiokit 5? Built something simple with that a while ago and it sounded a little too rough.

Thanks in advance!

Weirdly the first build archive uploaded to App Store Connect had the AU bundle ID, but subsequent builds had the main App bundle ID. Hadn't changed those after the first upload. Already tried changing the scheme and building another archive.

Know of a way to force the archive to use the AU bundle ID again instead of the main App bundle ID? So weird that Xcode did that once and not again after. Having a build with a main app and an AU extension both in the same build is unique.

Thanks in advance for posting a solution!