What changed with the MIDI engine?

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.  

brundlefly
My favorite humanizer continues to work perfectly in Platinum:
 
 

Wow! What a helpful response to the OP!

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.

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.

Humanizer on Platinum?
 
.

AT
Or pre-humanizer. 
 

Spoke to Cakewalk tech support tonight about another issue but brought up the humanizing mfx while I was on the phone with them.
mfxlookahead only has to do with how soon a change that you make in an mfx, while playing back, kicks in.
The humanizing mfx, and the dropped lead note that I was experiencing when freezing has to with the midi buffers settings.
I double checked mine and it is set at 2000ms, not 2500ms as I stated previously.

brundlefly

Vern C
I got the same issue with Cakewalk's included Humanizing effect.

Are you talking about the Random functions of the Velocity and/or Quantize MFX? I wasn't aware Cakewalk/SONAR ever bundled a "Humanizing" MFX, and I'm not seeing one now.
 
 

Yes, that's what I meant by that. It's the Quantize MFX. It's the randomization function.

In a very interesting turn of events, I *THINK* I've narrowed my particular problem down to drum maps. I was getting dropped notes when using a humanizer no matter what buffer setting I used.....until I thought about unrouting the midi drum track from the drum map. I've tested this with a library I'm using in Kontakt 5 and so far after several playthroughs, I have not gotten a single dropped note. When I re-enabled the drum map, I started getting dropped notes again.
 
I'm going to test this some more this weekend with Addictive Drums and Superior Drummer, and if I have time Steven Slate Drums 4.

brundlefly
Is the drum map the difference between your X3 and Platinum setups or is it not affecting X3? I added a drum map to my test project, and still didn't encounter any problems.
 
Any chance your drum map is routing some notes to an unused note number in the kit? Is it always the same note number/kit piece/articulation getting "dropped"?

The drum maps are the same between X3 and Platinum. It seems to be a combo of using a humanizer AND a drum map. However, once I disabled the drum map with the humanizer still enabled, the dropped notes stopped happening and everything played fine, even through several playthroughs. This leads me to believe it's an issue with drum maps and MAYBE not necessarily with the humanizer. It wasn't specific notes that were dropped, it was random with each playthrough.
 
What's interesting is that no matter what midi buffer I was using, I still got a dropped note. However, the number of dropped notes seemed to have "threshold". It happened a lot at lower buffers (~ 250-500). The more I raised the buffer, the less the dropped notes were happening. However, at 2500 and ANY higher number, I was still getting a FEW dropped notes, but not as bad as the lower values.
 
This was until I decided to disable the drum map late last night and see what happened. Low and behold, the dropped notes stopped occurring, even with the humanizer still enabled. I think I'm close to getting to the bottom of this.

I think it must have something to do with all this bleeding edge hardware and operating systems everyone is running.   My hairy old quad core with Win7 just keeps plugging along. Anybody have a sample project to post using only bundled FX and synths?
 
 

Hi Vern, 
yes I'm using a DrumMap - I'll try what you suggest. Maybe re-create the DrumMap in Platinum?