it's being reported in the roli software, I doubt that it's anything to do with bitwig as it shows the notes wrong on the dashboard, hopefully its not at midi source level or it will be an issue with the seaboard itself which would require a firmware update. hopefully its just their lack of skill to handle midi data.dlandis wrote: ↑Sun Oct 15, 2023 10:28 pmGotcha. Yes, this seems like a different issue than what I am seeing and others have reported in Studio One for sure. For one thing, what you've showed here is much more random sounding. The bug in SO reverts to the original pitch struck. And no, I don't think I've ever seen anything like this in Bitwig (thanks for the clarification, BTW.) Has anyone you know reported similar behavior with Equator 2 in Bitwig? Is it only Equator 2 or are other MPE synths showing the same erratic behavior? Have the techies at Bitwig been of help? Do you get the same behavior with the Arturia turned off (trying to think outside of the box a bit.) BTW, I do not have the Rise 2 as my MPE controller; I have two Seabord Blocks, a Lightpad M, and a Touch Block (FWIW; not sure that's the issue at all, of course.)MegaPixel wrote: ↑Sun Oct 15, 2023 6:47 pmIt actually stems from their software...dlandis wrote: ↑Sun Oct 15, 2023 4:23 pm As far as the glide issue you mention, I've never seen it in Bitwig. It does, however, still happen in Studio One as this is a recognized Studio One bug (with no scheduled date for rectification, and yes, it does happen similarly in all VSTs that allow for the use of MPE in Studio One.) It is most pronounced on patches with a longer release segment of the ADSR envelope.
Skip to time 2m 44s
https://youtu.be/ZNui93uVSv0?t=144
I reported the issue over 6 months ago.
After all this I went to work on kilohearts phaseplant mpe bug, snapping back to zero issue than last note pressed location, which is now fixed.