Jam Origin

>> MIDI Guitar & MIDI Bass user forum

MG on iOS as Inter-App audio


#1

Hi, MG (actual iOS version) causes loud noise (sawtooth, 340Hz) after a while when loaded as an inter-app audio FX in AUM/ Quantiloop (these are the hosts I used to load MG so far)
Any help to avoid the apps to clash?


#2

unknown issue sofar…
be sure to rule out midi infinite loops and stuff: disable midi in and midi output in MG for testing. We ofcourse like to know what happens…
Also check if “background processing” is on: probably not related but we have to rule out the causes.


#3

Hi Paul,
Thx for getting back so quickly.
No related midi loop, as I did not yet purchase “Midi output”.
The setting of the “background processing” switch is “on”.
-> this setting does not get stored permanently.
(I think this should be e.g. set in the App preferences to turn on permanently)

In the meantime I tried the following and it seems to work and solve the issue:
1.) start MG first -> Global iOS Audio Sample Rate is fixed to 44,1kHz & Buffer Size 256
2.) then start IAA host (AUM/ Quantiloop)
3.) Add MG as an IAA Insert or Effect
-> No noise occurred so far, fingers crossed…
edit: also here, MG keeps getting disconnected from the host (Audio signal is routed outside the host) …which feels like a Bug.

This leads to another very much related question:
Do you recommend to open MG always first, because of the fixed sample rate and buffer settings?
(It seems to me that 44,1kHz/ 256 Samples is the only supported setting)
That means, even when using MG on an iOS device as a side app to create Midi notes, I’m having the respective latency in the Audio chain?

And, I also tried to following:
1.) start IAA host (AUM/ Quantiloop) first, set the sample rate in the host to 44,1kHz/ 256 Samples
2.) then add MG as an IAA Insert or Effect
3.) switch to MG and turn on “background processing” immediately (otherwise MG get’s disconnected from the host. That’s why I recommend to save the “Background processing” switch “ON” permanently)
-> No noise occurred so far, but the MG keeps getting disconnected from the host…which feels like a Bug.


#4

I now purchased the Midi Output and use MG2.5 just as a midi Trigger.
It seems to me that using MG as IAA is not the way to go.

As I had a quick look into the roadmap of MG,
And I really would like to see this fixed before moving to more synth sounds:

  1. a fix of the communication between between the iOS apps (hosts like AUM/ Quantiloop and MG) and /or
  2. removal of the audio out function at all (the latency fixing…44,1kHz/256) when using it as a Midi interface

But, this aside, the MIDI Machines & Deep Expressor in MG 2.7 sound very promising!


#5

Good thoughs Stefan, Im also having problems when MG is not the first app I start. I have the sensation that only support 44,1kHz & 256 could be a bit too limiting and can lead to problems when trying to integrate MG with other apps inside AUM or other hosts, so maybe if it can be more flexible buffer side would help.

At least I think that some advice about to start first MG is mandatory at least acording my experience to avoid people problems.

Seeing the roadmap its interesting the new additions coming, but I keep thinking that one thing that MG needs more urgently is to have some solid environment in IOS that allows it to launch and save configurations with other external synthesizers (its no to play another IOS synths with MG what we want anyway?) and probably the best would be if it could operate like some AU host (like the desktop version) and be able to load inside other AU synths or at least to operate like an AU plugin and be able to load inside other hosts like AB or AUM, so would be interesting to know if Jam Origin is planning some of this in their roadmap.


#6

Thank you guys, for testing and detailed feedback.
We’ll be focusing on improving IAA compatibility, asap.

As for AUv3, this is obviously the real solution. In fact we build an MG AUv3 before starting looking into IAA. But unfortunately the only host we could find that would work with an Audio => Midi plugin is AudioBus3. I guess its a chicken-and-egg problem: since there are no real useful iOS AUv3 that produce midi from audio, hosts didnt care to support this. So maybe whats needed is that we hatch the egg. The problem is that then we will get lots of frustrated users who cant use it in their DAW.

The other side is also very compeilling: using MG to host other AUv3’s (similar to the desktp version). This is definetly planned, but as you can imagine, its a rather big task to support loading 3rd party audiounits.


#7

Just imagine MG2 for iOS as a host that could load AUv3!!! We can dream…


#8

Ok, I think we solved the IAA issue. Its indeed a bug with MG and has to do with the way we interfere with the iOS audio system in order to enable and disable background processing.

I’m uploading a TestFlight version today to Apple. It takes roughly 1-2 days before Apple approves it, usually.


#9

BETA version is up with IAA fixes!
https://jamosapien.com/t/midi-guitar-2-5-2-for-ios-interapp-audio-fixes/303


#10

Loaded it, but there is not option to restore purchases (i have the full version) so it remains as trial version , is that normal?
If yes, I can revert to my previous version?
This new version neither appears as loadable in audiobus 3.


#11

the beta automatically restores virtual purchases when you open teh shop, but you need to be online for that. Beta IAP is completely virtual and not linked to real purchases
AB currently doesnt support IAA at all ( at least here, and It seems like the actual version)


#12

The beta I installed does not restore my purchases, there is not even a button to invoque that, only the purchase buttons. How I can return to my previous version?
Sorry about AB no supporting, IAA all that multitude of formats is so confussing…


#13

you only need to open the shop and wait, just as with the real IAP’s
to return to normal none-beta version just download it from the appstore