I sincerely apologize for the confusion caused by my earlier announcement, which was based on a misunderstanding.

Initially, I believed that Apple’s “App-based lifecycle” would no longer be available in future versions of iOS, and therefore announced a plan to discontinue the Legacy apps and asked users to upgrade to new versions. However, after reviewing the information more carefully, I found that this change applies only when using the latest SDK. This means that the Legacy apps are still very likely to continue working.

I deeply regret having spread incorrect information and for encouraging upgrades that may not have been necessary. Going forward, I will take greater care to confirm details before making announcements, to ensure that I do not cause unnecessary inconvenience or concern.

Once again, I sincerely apologize for the misunderstanding and any trouble it may have caused.

2025-10-03,
KIRA Ryouta

Clarification About Legacy Apps and SDK Changes

Users can smoothly migrate to new apps! Settings / Saved Sessions can be loaded.

The new apps can load the old settings. Saved sessions in AU host apps (e.g. AUM) works with the new apps except if users use the “*deprecated” audio units. Files in iTunes File Sharing need to migrate manually.

In preparation for next year’s OS update, I have decided to designate four of my apps as “Legacy” and release them as renewed apps under new titles.
The Legacy apps are scheduled to be discontinued in the future.
Although the new apps have “26” at the end of their names, I plan to keep supporting them under the same names in the coming years.

• KQ MiniSynth
• KQ Dixie
• KQ Unotone
• KQ Sampei

Apple has stated that apps not adopting “Scene feature” will become unusable in next year’s update, leading to this situation.
If true, many older apps are expected to become unusable in iOS/iPadOS 27.
It appears that the Scene becomes mandatory when applying the latest SDK.
I apologize for making unnecessary app changes based on a mistaken understanding.

https://apps.apple.com/developer/ryouta-kira/id862984358?see-all=i-phonei-pad-apps

The lost functions in the *26 are:

• Inter-App Audio (Audiobus)
• Deprecated Audio Units

You can safely migrate to the *26 if you don’t use those functions. The app preferences and Audio Unit ID are common.
Some issues might occur if you use the both versions simultaneously.

For those who have purchased the older versions, I have prepared update bundles.
These bundles offer a discount.

KQ MiniSynth Update Bundle
https://itunes.apple.com/us/app-bundle/id1843517244?mt=8

KQ Dixie Update Bundle
https://itunes.apple.com/us/app-bundle/id1843517393?mt=8

KQ Unotone Update Bundle
https://itunes.apple.com/us/app-bundle/id1843517755?mt=8

KQ Sampei Update Bundle
https://itunes.apple.com/us/app-bundle/id1843517785?mt=8

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.)

https://www.youtube.com/embed/ZYBy2bkTvGw

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;
}