Question

With Studio One 5 release came MPE support but unfortunately it does not work with VST3 instruments.  Please fix this!

Answer 1

I hope this feature gets supported soon! I just got a Roli Seaboard Block 25 key keyboard hoping to be able to work with it inside Studio One 5. The VST that the Seaboard comes with called Roli Studio Player will only run as a VST3 inside Studio One 5. So unfortunately it will sound glitchy whenever you press two notes at once in the current version.
Please upvote this request everyone!

Answer 2

Thank you for the feature request. 

If anyone else agrees or disagrees, please VOTE!

The developers pay close attention to those that are voted on the most. 

You are allowed one vote. You can change your vote later if you choose.

(Here's some helpful info on how to use the voting system)

Please vote the original question / feature request. 

Please DO NOT Vote on THIS response!

Answer 3

Equator (by ROLI) runs as VST2 and VST3 inside Studio One. Unfortunately, the most recent ROLI installer hides the installed VST2 version. In order to fix this, you need to remove the VST3 dll manually from the VST3 plug-ins folder. This will make the VST2 re-appear in Studio One next time you launch. Hope this helps.

Answer 4

Yes, please fix this as soon as possible! The workaround below might help with Equator and Roli Studio, but the recently released Equator 2 no longer comes with a VST2 version.

Answer 5

@arndkaiser Thank you for mentioning this. I did some digging and found it is similar with ROLI Studio Player. You have to trick Studio One 5 into not recognizing the VST3 version, and only use the VST2 file.

Navigate to C:\Program Files\Common Files\VST3
The file "ROLI Studio Player.vst3" can either be deleted, or renamed ROLI Studio Player.broken, something like that. This forces the software to not recognize it.

Then, the VST2 version is stored in C:\Program Files\Common Files\Steinberg\VST2

So you have to add this as a plugin location within Studio One.
You'll know it works if it says "Category: VST2" in the bottom right corner.
Also be sure to enable MPE for your device, as well as enable MPE in the vst window.
Hope this helps for the time being until VST3 is implemented :)

Answer 6

It seems strange that a host that is a trend setting in coming out with VST3 a while back would ignore it when implementing MPE. I'd like to do some ROLI stuff but not being able to use Equator 2 means I'll just wait.

Answer 7

I upgraded just for MPE support, not knowing how barebones it was.  Please give us full-blown MPE support for all 64 bit VST types. MANY MPE synths are vst3 only and the vst2 standard is no longer being licensed. Strange, strange omission.

Answer 8

Studio one Guys ! Please Fix this !  We need MPE in studio one .

Answer 9

I am also waiting and hoping that Presonus will give MPE Vst3 a kiss. I upgraded from SO1.3 based upon MPE being available. I would like to be able to use Equater 2 without having the Roli Studio player inbetween or resort to hacks to get things going.

Best regards guy,

Sin

Answer 10

I find it hard to understand that Studio One that is so deep in being the best and feature proof is just simply not supporting VST3 MPE my Seaboard is a kind of useless with Studio One. MPE and VST3 is the future PreSonus!

Answer 11

Many plugins are now issued in VST3 only because VST2 is not free and is proprietary.

There's actually no difference in terms of MPE support between VST2 and VST3, from what I read and learned. It would just make a lot of sense if the MPE support was the same all around.

Please fix this!!!

Answer 12

Yes please, this is the main reason preventing me to use Studio One

Answer 13

Hey can we get an update or something PreSonus.  Like is it on the board somewhere?  It's been a year since this question was asked.  Hop on to Jira or something and see if it's in the backlog.

Answer 14

I just installed the roli software for a client & discovered this same problem. It's almost Feb 2022. This needs a fix already.
I'm thankful to the other posters for all the solution to the missing vst2 problem. I was scratching my head on that too.
Luke