On Feb. 5th, 2023 I updated KQ MiniSynth to the version 3.1. I write about using wind synthesizer (e.g. Aerophone, EWI, Carry-on DWI) with KQ MiniSynth.

First, add a Custom Controller to allow the Breath Controller to be entered.
If the amount of breath, such as Carry-on DWI, is sent in CC#11 instead of CC#2, set “Breath Source” to “CC#11/#43/#2/#34” from the settings. This will cause CC#11 to be converted internally to CC#2.

New in version 3.1 is the curve function. This allows you to adjust the breath sensitivity.

Applying an LPF of VCF with a cutoff frequency of about 20 Hz to the breath signal will smooth the signal.

Oscillator sync is recommended for wind synths. To do this, prepare two oscillators, input the V/Oct from the I/O panel to one and the pitch of the modulated breath to the other, and connect the output of the former to the SYNC of the latter, resulting in a specific sound. In the patching example, a V/Oct vibrator is used for modulation.

It is also recommended to use a LPF of VCF to slightly increase resonance and modulate STR with a breath signal; in the case of a LPF, STR is the opposite of cutoff, so an Invert should be placed in between.

In the patching example below, Or is used to process the breath signal only when a Gate/Velo signal is present.

A patch is here. (KQ MiniSynth is required.)

On iOS/iPadOS 16, a toolbar appears when you tap with three fingers. There is a workaround, which is described here.
This behavior was fixed on iOS/iPadOS 16.1. The information on this page is old.

Edited on 2022/10/7: A glitch occurs when you override UIWindow.

To put it simply, you can use a ViewController or similar to return .none in the editingInteractionConfiguration, and make that ViewController the firstResponder.
If not ViewController, AppDelegate or UIView may also work.
FirstResponder is an object that first receives events other than touch, so if there is an object inheriting from UIResponder that handles keyboard input, make it the firstResponder and editingInteractionConfiguration should be implemented.

An example in Objective-C is shown below; Swift users can draw an analogy from here.

Translated with www.DeepL.com/Translator (free version)

ViewController

// becomeFirstResponder returns "NO" in "viewDidLoad".
- (void)viewDidAppear:(BOOL)animated
{
    [super viewDidAppear:animated];
    [self becomeFirstResponder];
}

- (BOOL)canBecomeFirstResponder
{
    return YES;
}

- (UIEditingInteractionConfiguration)editingInteractionConfiguration
{
    return UIEditingInteractionConfigurationNone;
}