Hey @iainmccurdy I never had extreme stuck notes like in your case.
However I just now did a test with running Csound from terminal- and there was a difference between PortMidi & CoreMidi? Is that possible? (basically no stuck notes with PortMidi).
Roli Seaboard MPE with Cabbage
Well, in my testing its the other way around. PortMidi works really well, and CoreMidi in MacOS doesn’t. I also rebuilt Csound 10 just then from git with newest PortMidi on BREW. Don’t know if that makes a difference.
However I am still hearing stepping when doing pitchbends in Terminal Csound 6.10 (git).
Even when I tell Cabbage to use either I can hear a difference, and notice stuck notes. @rorywalsh I thought cabbage took over all MIDI?
UPDATE just worked out that Cabbage sets its buffer manually - so added -b 512 to my settings and pitchshift is fantastic now (in terminal CSOUND). Now everything is working well on my system and no issues to report (apart from 127 AFTOUCH). By using PortMidi in MacOS there are also hardly any (basically no) stuck notes.
If you use -+rtmidi=NULLthen Cabbage will use its own MIDI IO interface. If you don’t, then you may well be able to use Csound’s, but this approach will most likely lead to all sorts of problems when you load your plugin into a DAW.
Ok, I think I may have found the problem. With the changes I just made both of those files run just fine. It seems I was dropping some MIDI data from any midi messages containing aftertouch, hence the hung notes. Can one of you guys send me a MIDI file that pushes the boundaries a little more in terms of MPE? Btw, I’m using the synth posted by @alcomposer to test with. If either of you want me to test with any other synths let me know.
@rorywalsh Great to hear your making headway! And apologies for such a simple test synth! 
@iainmccurdy this finding makes me think that there may be a difference between Rise & Blocks after touch update speed.
Hey guys. Here is a rendering of @iainmccurdy’s first MIDI file using @alcomposer’s simple synth:
http://forum.cabbageaudio.com:/uploads/default/original/1X/0c5cd8b3a3ca01247b2498280e5913b752b45429.ogg
Does that sound right to you? This was done hosting the plugin in Reaper.
This sounds promising. I tried the same as you: MIDI file imported into Reaper playing a simple Cabbage synth as a plugin with the latest OSX beta and got loads of stuck notes.
You must have missed my earlier post where I said
I have fixed this now, and that soundbite is the result of my changes. I haven’t uploaded new betas yet however. I would still like to try something a little more complex. Any chance you could do another MIDI file for me?
Something in key of E-farp major, although I’ll also accept something in B-cat minor.
No, I had read this. I meant it is promising as the unfixed beta version exhibits problems but the one with your recent fixes does not.
How about something in the key of Lee Majors?
You mean all Cabbage plugin synths are broken for you in Reaper at the moment or just the ones that use some kind of aftertouch? To be honest, that may have been broken for some time…
Yes, any Cabbage synth that receives aftertouch often misses note offs. It’s quite possible that the issue has been around for a while and @Karamel1 did report problems with stuck notes in September, although Cabbage 1 seemed okay. I imagine that aftertouch has been rarely used (until recently) but it’s good to get it dealt with.
This is fantastic! It’s great that the Seaboard is finding these issues, as they could have cropped up in future as mysterious problems!
Also moving forward I think Aftertouch will become much more actively used in controllers. (It’s a pity it has taken manufacturers this long to use it to its full advantage)
Hi guys. there is a new beta here. Note that I’m currently doing some work on the GUI editor so if you tend to use that a bit you may notice some irregularities. I’m also updating the manual at the moment. I’ll upload the latest once I have made some progress.
Don’t forget that this version uses nslider en lieu or numberbox. I’ve updated all of Iain’s examples, but you may need to update your own. Let me know how it works for you.
Also heads up --aft-zero is a new flag implemented by jpff! Super!
@alcomposer Yes, thanks for pushing that forward Alex.
@rorywalsh The new build is no longer missing note offs for me. I haven’t tested it extensively but so far so good. The only thing I spotted are that my Windmills are missing their sails. I suspect this is the dreaded macros again.
I think its so good to have this fixed (after touch init 0). I just can’t work out why it was like that in the first place? Or changed in 2002? I imagine it was for a good reason, and it would be good to know what that reason was?
Wish I knew the code base better to make the simple change, my version was a bit silly- sticking the variable in oparms!
It does look like we will get this into 6.10 however which is great.
Thanks for doing this too. Looks like John integrated your changes, although not through the PR. But I still think PRs are the best way to get their attention
Maybe of topic, but I check on csound Dev list and it seems that 6.10 is not really ready. Do you think that we can expect new stable version of csound (and therefore of Cabbage) by the end of this week?
The current windows version of Csound should be stable enough so long as you either don’t install or simply remove the vst opcodes. If you are still experiencing quite a few crashes, I hate to say, but it’s most likely Cabbage.