I asked this question in the software forum but got no response, so here goes.  I got MG2 last Christmas, used it in several CW projects with no problems.  However, with the latest version of CW 2018.09 (build 29), I'm unable to save my settings in MG2 unless I freeze the track.  I had to rebuild a few projects that were created in earlier versions of CW.  If anyone else is using MG2, are you having this problem too?  Am I missing something simple?  Thanks in advance for any replies.

I've had problems with MIDIGUITAR 2 for months. Every time I try to bounce to track using midiguitar 2 on a track it crashes . ( I often use midiguitar2 for guitar sounds I made in it, NO midi-synth triggering). I uninstalled it and installed an old Beta version of Midiguitar 2 and that fixed my problem.

I was using MIDIGuitar2 on my desktop PC just after the current 2018.08 CbB update, and it crashed pretty quickly. 
 
At the time though it was before I moved to the beta drivers for my 1st gen Focusrite 6i6 - the "stable" drivers has its buffer sizes in ms (1ms, 2ms etc) which gives odd buffer sizes - i.e. not powers of 2. I ended up having to use ASIO4ALL to get a buffer size of 256 which it prefers.
 
As I've used it on my laptop several times (prior to 2018.08) using my 2i2 without issue, I put it down to some weirdness between MIDIGuitar2 & ASIO4ALL. 
 
When I get time, I'll play about with it again to see if it's more stable using ASIO drivers that support a buffer size of 256. The latest beta drivers for the 1st gen Focusrites (which I was forced to install due to Windows 1809) now use power of 2 buffer sizes.
 
It's worth mentioning though, that I never save a project with MIDIGuitar2.
 
I only use it to get the MIDI data out for triggering acoustic or 12 string guitar samples, and only then if melodyne doesn't do a decent job of extracting the MIDI.
 
Once I've got the MIDI data onto another track, I delete MIDIGuitar2.
 
Invariably, I'll replace that track with a real acoustic / 12 string once I get around to it, but using Melodyne and/or MIDIGuitar2 gets my ideas down quickly.
 

Ok, did a quick 30 min test and it seems to be fine for me at a buffer size of 128, using 44.1Hkz/24 bit.
 
I had it inserted as a FX on an Audio track, MIDI output enabled, routed to a SONiVOX Singles Taylor Acoustic on a separate instrument track.
 
It actually worked at a buffer size of 32, but latency was increased to I reverted to 128.
 
I'm using the latest version (v2.2.1).
 
 

^ This is how I use the plug-in. I may leave it in the project but do not use any of the built-in effects or its internal plug-in host. If it is losing its setup the only thing I can suggest is go back to the version the project is created with and save the MIDI Guitar settings as a preset in the plug-in's built-in preset manager.

Well, I've been using is to trigger Dimension Pro or Rapture samples.  Regardless of buffer time (I use 256), it will not save the presets, even if I create a preset in its own preset manager.  I have to freeze the track if I want to save it.  This didn't happen in the March version of CW.  Thanks for all your replies.

Lynn
Well, I've been using is to trigger Dimension Pro or Rapture samples.

Inside the MG2 plug-in or by adding separate track(s) for the synths. I do the latter.

Lynn
Well, I've been using is to trigger Dimension Pro or Rapture samples.  Regardless of buffer time (I use 256), it will not save the presets, even if I create a preset in its own preset manager.  I have to freeze the track if I want to save it.  This didn't happen in the March version of CW.  Thanks for all your replies.

Yep, you're right - it doesn't recall presets.
 
Also, if you save a preset within MG2 itself, you have to manually recall it from within MG2. The CbB/Sonar preset system doesn't recall anything.
 
I think this is a MG2 issue. The same thing happens in Sonar Platinum.

scook

Lynn
Well, I've been using is to trigger Dimension Pro or Rapture samples.

Inside the MG2 plug-in or by adding separate track(s) for the synths. I do the latter.

I insert DP or Rapture inside MG2, find the sample I want, then create a preset within MG2.

Sorry, I do not use the plug-in that way. I can understand using the built-in VST host when running stand alone but unless there is an effect chain unique to MG2, I see no advantage to using the built-in host when running inside a DAW.
 
It does appear to have trouble loading preset when the project loads. The only way I could see keeping it straight using the build-in host and effects would be to name presets for each project/track.