Thanks for adding this device, love to be able to control VIs from my other controllers when setup internally. I do have a question. As of right now, the MIDI device module still plays the chain even if the chain is bypassed. Is this intended behavior or a bug?
I keep getting an error message saying Logic is set to 512 samples buffer, wants me to set it to 128. Problem is, I get the message even if I’m at 32 samples or 128. Bug?
I have a license for MG2 which works fine with all my VI’s. I tried MG 3 early on and am just getting back to checking this betra again after few months and downloaded the latest beta 3.50. I can’t seem to access Kontakt falcon, zebra etc.anymore I thought they were working in MG3 before . Do I need to activate MG3 again or something to get this to work or should myMG2 license be good?. I don’t see an option to authorize it just says buy. Not sure what I am missing?
Craig
Wow, using 13ms legato is perfect for what I have always imagined midi guitar legato to be, thank you! Having this tool is getting me back into a musical creative space that I have not been in for quite some time.
yes I did see that and it scanned all my plugins which I wish it would not do as I have over 900. I know in MG2 I could select which ones to scan one by one .
I watched your intro again to MG3 . I’m still getting used to the new GUI setup . The internal synth patches all work fine I Loaded one of my V-horns in Falcon and can’t get any sound to transmit .Took me a while to see I have to put it to Midi 1 legacy to get it to sound , Kontakt and other VIs are working although Omnishere seems to crash MG3 every time I try and load it.
Just checked and Omnisphere crashes MG2 as well when I try and load it both AU and VSt3 .
I am getting this screen when launching the latest Midi Guitar 3 Beta. I am running Cubase 13 Pro under the latest MacOS. It does not seem to change when up update my buffers in Cubase Audio for my Helix Audio Driver
The problem is here that iff we just let MG run for you guys, you would never know that MG3 is fast and usable. You would feel be sluggish, as it MG only gets these huge 512 size buffers from Logic/Cubase. There is nothing MG can do about that, since Logic/Cubase is in control here. So I thought the error message is needed.
But why does it happen? Here are some ideas:
There are quite a few audio settings in Logic/Cubase and it might be because of one of them.
It might also be that your interface doesn’t like to run as a system audio and Logic. If the audio device get in trouble delivering audio it may increase the buffersize.
It might be that you just need to press play in logic when there is a track actually playing or enable monitoring on the MG track. If Logic doesn’t play or monitor anything, it will use 512 or 1024 buffers regardless of what you set in its audio settings, to save CPU.
@larrygood , I’m also running MG3 on Cubase 13 Pro on an iMac. I have no problems when adjusting my audio interface (Behringer X-32 Mixer) to the required buffer size. You might want to try to do the audio setup first prior opening MG3.
