jeff oliver
I'm having the exact problem as the OP. Modo bass works fine outside of Sonar. But otherwise its unusable as the notes stick quite often. Hopes someone finds the culprit. Thanks.

Hi Jeff,
Have you contacted support at IK multimedia? They seem to have given up trying to help me. If more people contact them they might not think I'm the only one with the problem!
 
Cheers,
 
Darrell

In the first message you said:

Dazzell
I notice when I increase the buffer size the issue goes away but latency becomes an issue and MODO isn't playable.

So what ASIO buffer size are you using that fails and what size is required for MODO to work?  In general soft synths with as high a CPU needs as MODO are going to have a very hard time at any buffer size under 128.  No matter how awesome your CPU is.  In fact I'd say 512 or 1024 would be a more likely minimum.  MODO isn't a sample playback engine (so it has nothing in common with IK Sampletank libraries) it simulates the strings.  A very computationally complex operation.
 
If your buffer size is "reasonable" and MODO is still not playing correctly but only with SONAR the problem might be related to SONAR's multiprocessing settings.  In preferences is an option under Audio->Playback and Recording for "Use Multiprocessing Engine" and a sub-option for "Plug-In Load Balancing" and there are a couple of not visible setting you can adjust in the Configuration file (aud.ini), including EnableSetThreadIdealProcessor and MMCSSThreadPriority and a few more I have no clue what they really do.  Usually AUD.INI problems are best solved by exiting SONAR, removing the AUD.INI file and starting SONAR and letting it remake a default one.  Then start changing things, there are a lot of options that might improve your situation.  In addition Windows 10 has a new "Game Mode" causes all kinds of issues.  I believe Cakewalk recommends turning it off.  There are other threads on this.
 
I wasn't able to reproduce the effect you describe with MODO, but that kind of stuck sound is usually due to the computer not being able to fill the audio buffer up in time.  Which means something in your audio chain is taking too long.  Your MIDI interface (since it only happens when you play live), your CPU/Computer, your audio interface.   Perhaps it might be related to the drivers and chipsets that glue all those pieces together.  It can be related to how SONAR works with all of the those components (which would explain why it doesn't happen in Reaper).

msorrels
In the first message you said:

Dazzell
I notice when I increase the buffer size the issue goes away but latency becomes an issue and MODO isn't playable.

So what ASIO buffer size are you using that fails and what size is required for MODO to work?  In general soft synths with as high a CPU needs as MODO are going to have a very hard time at any buffer size under 128.  No matter how awesome your CPU is.  In fact I'd say 512 or 1024 would be a more likely minimum.  MODO isn't a sample playback engine (so it has nothing in common with IK Sampletank libraries) it simulates the strings.  A very computationally complex operation.
 
If your buffer size is "reasonable" and MODO is still not playing correctly but only with SONAR the problem might be related to SONAR's multiprocessing settings.  In preferences is an option under Audio->Playback and Recording for "Use Multiprocessing Engine" and a sub-option for "Plug-In Load Balancing" and there are a couple of not visible setting you can adjust in the Configuration file (aud.ini), including EnableSetThreadIdealProcessor and MMCSSThreadPriority and a few more I have no clue what they really do.  Usually AUD.INI problems are best solved by exiting SONAR, removing the AUD.INI file and starting SONAR and letting it remake a default one.  Then start changing things, there are a lot of options that might improve your situation.  In addition Windows 10 has a new "Game Mode" causes all kinds of issues.  I believe Cakewalk recommends turning it off.  There are other threads on this.
 
I wasn't able to reproduce the effect you describe with MODO, but that kind of stuck sound is usually due to the computer not being able to fill the audio buffer up in time.  Which means something in your audio chain is taking too long.  Your MIDI interface (since it only happens when you play live), your CPU/Computer, your audio interface.   Perhaps it might be related to the drivers and chipsets that glue all those pieces together.  It can be related to how SONAR works with all of the those components (which would explain why it doesn't happen in Reaper).

Thanks Matt. I hadn't played around with those settings. I'll experiment to see if changing those settings helps!