pichi wrote:So just Bram Bos apps for now regarding AU.
I talked to him about this some time ago. I couldn't convince him to change his plugins, so I'll consider making MTS handle his plugins differently so they don't lose their settings when transport starts.
This would merely take us to the next problem though: RuisMaker responds to some MIDI controllers which MTS sends for initialization purposes, and RuisMaker's "Ignore MIDI CC" setting doesn't seem to work.
pichi wrote:Edit:All IAAs fine except Korgs Odyssei. But I couldn't get it to respond to midi in Auria either...
Perhaps it responds to one particular MIDI channel only?
Giel Bremmers
That doesn't seem to be the case. It's the odd man out in the Korg catalog. I think you can play it from an external keyboard but not program it within a DAW.
Anyway thanks for your efforts.
Korg is a major PITA regarding its iOS apps. To my knowledge, NONE of them support IAA (Korg Module certainly does not). However using AudioBus 2, they can be selected as an Input Device with MTS selected as an Output Device. Then they can be assigned to a MIDI TRACK via the Virtual MIDI INSTRUMENT option and should play out of MTS (KORG MODULE works this way). Just make sure to set the sampling rate for new MTS songs at 44.1 khz, not 48 khz, or the audio playback will be 1.5 semitone sharp.
Add Tardigrain to the list of AUs which do not work in MTS. Does not produce any sound; appears not to trigger.
Plus further testing has revealed none of Audio Damage’s AUs can BPM sync in MTS (e.g. programming Dubstation to do a quarter note delay does not have the desired effect.)