Problem (probably a bug) with MIDI Guitar 3 plugin

Windows/Mac
1

Hi there,
Using MIDI Guitar 3.0.66, Mac OS 15.7.2, Ableton 12.3.2 the VST3 plugin works like expected, until I quit Ableton and start it again (and reload my project)
Ableton becomes unresponsible instantly at loading (colorful rotating ball) .. have to ‘force quit’ it then.
After loading the project holding the option key and removing the plugin from the project, everything works again. Can re-add the plugin then and use it again.
Ableton crash log zips are corrupt, testflight seems not authorized to handle the Mac OS version. So unfortunately there is no more info which I could provide.
’ll try a lower version for now. Hope, this helps.
Cheers!

2

Thank you for reporting.

I guess something in the MG3 patch, (inside the Ableton project) doesn’t load correctly. Maybe some plugin or file (IR, Nam, etc) is missing. Obviously it’s not supposed to happen and I will try to think of what could cause it. But can you reproduce this if you just load the MG3 plugin into a new Ableton project?

3

yes - even without loading my MG3 patch.

atm my only workaround is to remove the plugin before saving the project and add it again the next time after starting.

4

Can.i get you to try to delete the files:
~/Library/Group Containers/X6D2Q4W5A8.midiguitargroup/Preferences/Devices.txt
~/Library/Group Containers/X6D2Q4W5A8.midiguitargroup/Preferences/MIDI Guitar 3.txt
~/Library/Group Containers/X6D2Q4W5A8.midiguitargroup/MIDI Guitar 3.settings
and try again?

5

Great, that seemed to work!
Btw: the plugin did not re-create these files.
Devices.txt had 16 dedicated input channels, which is not true for the configured interface. I got one with 6 (gt-1000 core - thats the one I use for the guitar) and one with 18 (rme)
The .settings showed 44.1 kHz (I’m on 96kHz), 0 input channels and 11 output channels.

When having the hangups, I noticed that the samplerate somehow changed several times. (once per hang?) The plugin showed an empty space then until I reconfigured it. Not very sure if I got everything correctly after so many restarts.

Anyway, thanks a lot for your quick help!
Cheers!

6

Thank you. Excellent reporting and feedback!

I’m starting to think it was too daunting to add this experimental option to open audio devices inside plugins. It’s obviously something DAWs cannot anticipate and the fallout we can’t really control. At least we should hide it behind a very clear notification about its a possible cause of trouble and a way to revert it.

1 Like