• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Solved Studio One 7 - Sound Variations with EWs OPUS not working

Steenvay

New member
Hey everyone,

I recently updated from Studio One 4 to 7.2.3.108761 and wanted to optimize my workflow using Sound Variations on my instrument tracks.
I'm using almost exclusively plugins from EastWest at the moment, utilising their OPUS player (VST-2).

I was told that adding an instrument with Keyswitches will automatically add those keyswitches as sound variations.
When I do that with an OPUS instrument that uses keyswitches (in my example the 3FL KS Master track from EW H ollywood Orchestral Winds), it actually adds all the switches *that are not active while adding the instrument or using the "reload map from instrument" option*.


So when I add a new instrument, it adds every switch except the C0 one that is active by standard. If I switch to, say D0 and then click "reload map from instrument", it will add C0 correctly but ignore D0 instead.
The switches/sound variations that get added itself are named correctly as far as I checked though.

If I now mark one or multiple notes in the piano roll and then select one of the options to use a different sound variation, the note itself doesnt get colored (stays the same), however the variation gets added in the bar below the piano roll showing the automations. It does nothing, however, as if the info saved there isn't correctly attributed to something actually happening.

My question would be how to fix this in case it is a known issue or easily solvable. I know that I could load multiple patches manually into one mult, and then assigning the sound variations myself via MIDI channels (at least I think I can), but wanted to check first if I'm just making a simple mistake I can't see myself right now.

Thanks for reading and every answer you're able to provide!



I tried showing the most important info in this one screenshot, if I can provide anything helping you with a possible fix, please feel free to let me know
S1 SV issue.png
 
Hi and welcome to the forum!

Is this in both the VST2 and VST3 version of Opus? If so, did you report this to East West's tech support? Also, are you on the latest version of Opus?
Hey, thank you!

I didn't report it to EW directly yet, as I usually tend to ask the community on these things first - force of habit.
I updated Opus about a week ago, so it should be the most recent version
 
Using Opus as a VST2 instrument has seen reports of unreliable behaviour in Studio One and Cubase, among others. I'm pretty sure that keyswitches are not fully supported under VST2. It should be used as a VST3 instrument.
 
Last edited:
Using Opus as a VST2 instrument has seen reports of unreliable behaviour in Studio One and Cubase, among others. I'm pretty sure that keyswitches are not fully supported under VST2. It should be used as a VST3 instrument.
Hey, thank you!

I didn't report it to EW directly yet, as I usually tend to ask the community on these things first - force of habit.
I updated Opus about a week ago, so it should be the most recent version
Thank you both!
Using the VST3 plugin did the trick, was hidden in the browser (only showing when sorting by vendor instead of flat).
Case closed :)
 
I just spoke with the EastWest development team. They replied that there's an issue in the VST2 implementation of Sound Variations, and they'll look into it to provide a fix in a future update.
 
Back
Top