Two things to have in mind here:
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.
Hope one of these hits home for you guys.