MIDI Guitar 2 iPadOS 18.1.1 noise issue

Hi, after I installed the update 18.1.1 on my Ipad, MG2 no longer works properly. Only croaking sounds come out and the tracking is also massively faulty. Apple support has told me that the fault must lie with MG2 and that I need to contact the developers. I also deleted MG2 and reinstalled it. No change in the error. what should I do? Greetings Jörg

I have no problems with MG2 on iOS 18.1.1, I just updated from 18.0.1.

Just like @Dutti67, MG2 works as expected on my iPhone 14 on iOS 18.1.1. I just tested it with headphones and an audio interface.

A bit more info maybe? Third party synths/effects? MG2 native stuff? Using in a hosting app or standalone? Please…

I’d suggest to have a look in your settings and make sure you have everything configured correctly with your interface. Does anything look unusual in there?

For example, I use PD Space Guitar as an effect, which worked perfectly yesterday and the time before. Or when I use Nanologue via Midioutput (activated in MG2) everything was ok before the update. - However, a value of 257 is entered for the buffer size on the MG2 user interface (Audio Device IN/OUT). It should actually be an even number or 256, right? Maybe this has something to do with the error …

PS: I can’t change the 257 either and it doesn’t have the black background like the other entries above it. - AI is Steinberg UR 22 C

I’ve had the same thing but it’s intermittent. I’m also having general MIDI problems in AUM. The fault seems to be with iOS 18, which is very buggy.

Right, I’m seeing the sample buffer size locked at 257 also in MG2 standalone on iOS 18.1.1. But I typically use MG2 in AUM and I haven’t noticed an issue.

I tested MG2 standalone in response to your post and even though it’s showing the locked buffer size it functions as expected.

This sounds like one for @JamO.

1 Like

Oh. Thank you everyone for reporting.

This would be 3rd time an iOS update broke MG2.
If it’s of any comfort, the previous two times, Apples next iOS update fixed it again.

Unfortunately, I cant easily fix this on my side, or even tell whats going on right now. The best I can do is to rush out the MG3 beta update for iOS.

6 Likes

Gotcha. FYI, I updated to iOS 18.2 today and the buffer size is still locked at 257 but I couldn’t detect any performance issues on the surface of things.

I installed the 8.2 update today. No changes to the abnormal behaviour. Buffersize is still set to 257, leaving me as a fooled user.

I’m having massive issues too since IOS upgrade super frustrating was working perfectly before this

I’d recommend reselecting your input device every time you restart MG2 in standalone. I had an issue where the MG2 settings were showing input 2 as the source but the audio input was actually being grabbed from from input 1 – resulting in weird sounds. This might solve your issue.

EDIT: And furthermore, I’m experiencing no issues in AUM using MG2 as AUv3.

tested here: iOS 18.1.1 does not display the correct buffersize in settings for standalone apps, when the app is compiled with older JUCE.
JUCE has recently been updated to fix the issue.
The official Space Guitar 2 ( 1.3.75 ) will run, but the devicemanager is faulty.
The beta version of Space Guitar has the newer JUCE and the device manager works correct there.
So this means that MIDI Guitar 2.5 needs to be compiled with newer JUCE to fix the issue.
It is unknown to me whether this clash between JUCE and iOS is temporal, or that it will be fixed for backward compatibility by apple. but Apple mostly doesn’t do backward fixes…
The JUCE/iOS issues are discussed here:

2 Likes

I meant 18.2 update.

I’m new to the site but was browsing the forum checking out iOS threads as a MG2 user and saw the comment about rolling out a MG3 iOS beta possibly soon. That is exciting news and I would love to try it out!

My update is 18.2.1 and have the same issues.

Please get MG3 here:

Great, how do I load it into my iPad Pro 4th generation? Thanks.

I have the same problem. Did the same thing. Then I put it into AUM and it worked . Then tried stand alone & it worked for a bit then it crashed.