Hello Andi, yes that's what I say. But why? You've just been able to connect your Synchron player to Studio One. I thought you might have an answer, or someone from the community.
But I also asked Presonus. If I get the answer I will put it here.
194,067 users have contributed to 42,911 threads and 257,913 posts.
In the past 24 hours, we have 6 new thread(s), 21 new post(s) and 82 new user(s).
Hello Andi, yes that's what I say. But why? You've just been able to connect your Synchron player to Studio One. I thought you might have an answer, or someone from the community.
But I also asked Presonus. If I get the answer I will put it here.
Hello,
the problem is only related to Synchron Player and VE Pro,
because Vienna Instruments Pro shows up the correct MIDI CC names.
I kindly ask VSL to check what differs in their implementation between Synchron Player and Vienna Instruments Pro with Studio One MIDI CC binding.
Thanks
Hello everyone,
I can confirm this strange CC behaviour for our VST3 Plugins:
- Vienna Synchron Player
- Synchron Pianos Player
- Plugins hosted inside VE Pro
Using the VST2 version and CC is using the correctly labelled automation tags. We will have to investigate here.
Best regards,
Andreas
Hello everyone!
We looked into this issue now and unfortunately, we found a few shortcomings and bugs in how Studio One handles CC vs Parameters in Studio One. We are in contact with the developers, but it's possible that we might at least implement a fix about the "n+1" issue for upcoming VST3 plugin updates throughout or software.
All assignable (changeable) parameters can be selected directly (see screenshot attached). For your pedal information, you will have to work with the "Ctrl X-X"+1 parameters, for now.
Best Regards,
Andreas Rautner