The new Sonar is not behaving well with certain types of MIDI fx. The few that I've tried in the new program worked great in X3 without issue.
 
In X3 I had to adjust the TTSSEQ.ini file for the midi fx lookahead, and my humanizer (Frank's Humanizer MIDI fx) worked great on my drums. I upped "MFXLookAhead" to 100. In the new Sonar, I've had to up the same line to 960 AND ALSO up The Midi Playback buffer in the Preferences to 2500 ms (!!!!!) to stop getting dropped notes, primarily experienced with using *ANY* humanizer. The reason I'm even putting up with this is because Frank's plugin is a BIG timesaver and the same humanizer (www.midi-plugins.de) has some options to definitely help me tweak the timing that no other humanizer midifx has.
 
I talked to another member here recently and he also says that he had to up the midi playback buffer to around 1000 and "MFXLookAhead" to 960. These are unusually large numbers to use, and a big difference from what was going on in X3.
 
This doesn't just happen with Humanizer plugin from "Frank" nor just drum vstis. This happens with ANY humanizer on ANY vsti. And they worked great, without issue, in X3 once I adjusted "MFXLookAhead" to a workable number.
 
I don't understand it. Everything looks to be the same as X3 in the preferences, but there's obviously something different going on here between the last and the current versions.

did you lower the mfxlookahead value at all?
I would ideally like several of these baked into a prochannel for midi tracks (after all the prochannel tab shows up in the inspector when you click a midi track).  I think that would be a nice integration.  You could have basic things like transpose and filter, even delay, velocity and length compression -- even the chord analyzer with a nice big display of the current chord.  

My favorite humanizer continues to work perfectly in Platinum:
 

 

brundlefly
My favorite humanizer continues to work perfectly in Platinum:
 
 

Wow! What a helpful response to the OP!

Vern C
.... Frank's plugin is a BIG timesaver and the same humanizer (www.midi-plugins.de) has some options to definitely help me tweak the timing that no other humanizer midifx has.....

+1
 
I haven't upgraded yet, and as a user of Frank's humanizer, this gives me pause.  
 
Clearly something has changed with the midi FX implementation, but until a changelog is released for Sonar 2015 we won't know exactly what.
 

I've always had an issue with Frank's humanizing mfx, when I froze drums, the first drum hit would always get dropped because the humanizing mfx would move it a few ticks in front of the beat and it would not sound. My workaround would be to create a non-sounding note, something like C10 one beat or so before the first drum hit. It worked.

Then I found out about mfxlookahead variable.

I've been doing more experimenting into mfxlookahead and how it relates to humanizing mfx and this is what I got.
Mfxlookahead's default value is 960*4 (ticks, not ms) which is 4 beats in 960 tick resolution.

All it appears to do is store mfx changes in a buffer for playback, so if you're playing back a midi track with mfx and change a value, that's how long you'll have to wait before you hear a change. I've decided to live with 480, which in my case, is one beat. No big deal.

The midi buffers setting appears to be what affects the humanizing mfx.

I tried different settings, increasing by 500 each time and 1500 would work on some projects and not on others. Since this is in ms, the tempo of the project had a direct effect. The lowest setting that works on all projects (for me) appears to be 2500 ms.

This does not appear to have impacted midi playback if I loop a section either. Everything is playing as expected and freezing as expected at this setting for me.

Just passing it on and would love to hear of other people's experiences with this and what works.

gustabo
 
Wow! What a helpful response to the OP!

Seven years of helpful posts, and I can't get away with one moment of smarta$$? Sorry. Let me try again:
 
OP wrote: "This happens with ANY humanizer on ANY vsti."
 
It seems unlikely to me that there's something specific and common to all humanizers that would cause a problem. So I'm wondering if OP has tested any MFX bundled with SONAR or 3rd-party freebies that might reproduce this?
 
Dave

Dave,
I assume that the hand pictured isn't yours. If it is, nice hand...
You didn't specify the name of the mfx humanizer pictured that does work so it wasn't very helpful!

Seriously, he didn't mention in this thread but he did mention in another thread that he was getting the same issue with Cakewalk's humanize mfx and Frank's humanizer mfx.

brundleflySo I'm wondering if OP has tested any MFX bundled with SONAR or 3rd-party freebies that might reproduce this?

 

gustabohe did mention in another thread that he was getting the same issue with Cakewalk's humanize mfx and Frank's humanizer mfx.

Yup, I mentioned in another thread on the same subject that I got the same issue with Cakewalk's included Humanizing effect. I'm going to try other humanizers, and other types of effects, soon.

Seven years of helpful posts, and I can't get away with one moment of smarta$$?

 
Hey Dave, I say go for it. The odd smarta$$ comment never hurt anyone - and you actually deserve a few more