I bought this about a month ago, and am on 3.0.68. From the very beginning, it crashes Live frequently. I have never had a plug-in that has such a deleterious effect on Live, which has been rock solid for 20 years.
First off, if the plug-in is in a Live set, Live always asks to access data from other apps. No other plug-in triggers this dialog. Then it might crash out. I restart it and it might work. Quite often, dropping the plug-in on an audio track makes Live crash. I would estimate this happens about 80% of the time.
I stopped using it after the first few days in exasperation, but I now need to use it for a project, so need to troubleshoot this. Where do I start? I presume this is not normal behaviour. Perhaps few people use it in Live.
I’m on an M2 MacBook Pro, macOS 15.7.4. Live 12.3.7.
I never use VST plug-ins, but tried the VST3 plug-in instead of the AU one. Seems much more reliable so far. I haven’t had a crash yet. I’ve added Midi Guitar to several tracks and have opened/closed Live a few times. So far so good.
Thanks for reporting. I don’t think this is a common issue. The VST is generally better as it can output midi directly to the track (not going around virtual midi), but the AU should definetly not crash, then something is wrong on my side. I’ll try reproduce this here with the AU.
Do you load any external plugins inside the MG3 plugin?
Are you using this for MIDI control only? If so, I would recommend using the standalone version with a MIDI Output Device to trigger MIDI tracks and VIs. I have been using MG3 this way for almost 2 years with no real issues. This is my main MIDI controller now and can’t be any happier.
Not sure what you mean by midi controller. I’m using it to take my guitar audio input and convert it to midi which then drives a midi instrument on another track in Live. I used to use a Roland VG-99 for that, but when I trialled Midi Guitar, it was a lot better at tracking, with fewer ghost notes. Amazing really.
I have also been dropping it on a track that has guitar audio, routing it to a midi instrument on another track. This is a great way to hear old bits of guitar audio as another instrument. Works MUCH better than the built-in Ableton audio-to-midi functionality.
I mean using the standalone version with the midi output module and have it drive any other software (like Live) as if it was a hardware midi controller. No need to put it on a track as a plugin, a;though dropping it on existing audio tracks to have it play midi is pretty cool.
MIDI Guitar converts your guitar audio to MIDI data and then sends it somewhere to control something. So, I think it’s pretty safe to say it is a MIDI controller, just like a keyboard.
Chalk and cheese!
Forum member @pasha has reported issues with Live 12.3.6 (IIRC). On the other hand, I use Live 12 all the time with MG3 (plug-in) and I haven’t been able to replicate the crashes and issues discussed.
I hope an answer can be found for those having trouble. Any more info about your setup that might give a clue?
I needed to clarify because people often make a distinction between midi controllers and midi instruments, e.g. I use a midi controller to drive faders etc, in Live, but I play my keyboard as an instrument. In then end, they all produce midi messages, pitch bend, modulation, etc., so one can call them all controllers, but I think people generally use the term “midi controller” for devices that control parameters via CC messages etc.
I wasn’t sure whether he meant the common meaning of “controller”, as I thought is was obvious that I was using Guitar Midi to generate midi data.
Anyway, thank you all for your help. On some forums you just hear the sound of crickets. Nice to be part of one where people chip in with help!
