crusherX can be both an instrument receiving midi notes and an effect receiving audio. S1 sees it as an effect only, so how do I get S1 to pass midi notes to crusherx so it can be used as an instrument and not just an effect
SOLVED, it cant as is vst2
Last edited by gregh on Sat Apr 17, 2021 3:11 pm, edited 2 times in total.
win10, old i5 machine (plenty good enough) S1Pro, Bitwig, Adam A7 monitors
https://greghooper2.bandcamp.com/ |
Is it in plugin manager on the view menu?
Or on the black list. You using VST2 or 3? You restarted S1 and rescanned for plugins?
Forum Moderator.
Please add your specs to your SIGNATURE. Search the STUDIO ONE 6 ONLINE MANUAL. Access your MY.PRESONUS account. OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET. Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce. Studio OnePro6 Melodyne Studio Win10 Ryzen 5 3600 - Motu M2 Ventura Mac Mini M2 - Zen Go TB |
Tacman7 wroteIs it in plugin manager on the view menu? it is visible as an effect - but it is an effect that can take midi notes and be played in other DAWs but so far does not seem to be able to do that in S1 and vst2 I can get around this using the demo of bluecat patchwork, but dont really want to have to pay for another plugin when should be possible in S1
win10, old i5 machine (plenty good enough) S1Pro, Bitwig, Adam A7 monitors
https://greghooper2.bandcamp.com/ |
the answer might be that what i want is impossible because S1 does not support vst2 sidechaining
win10, old i5 machine (plenty good enough) S1Pro, Bitwig, Adam A7 monitors
https://greghooper2.bandcamp.com/ |
I have several instruments that can also be used as an effect.
I use the plugin manager as a troubleshooting tool so as to see if your instrument might be installed but having a problem or is it installed in the wrong place etc. Also some plugins have features that only work using the vst3 plugin where the vst2 plugin doesn't work. S1 can not do what's required for the Vocoder: viewtopic.php?f=151&t=42832&p=262149& S1 doesn't allow audio routing into external instruments
Forum Moderator.
Please add your specs to your SIGNATURE. Search the STUDIO ONE 6 ONLINE MANUAL. Access your MY.PRESONUS account. OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET. Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce. Studio OnePro6 Melodyne Studio Win10 Ryzen 5 3600 - Motu M2 Ventura Mac Mini M2 - Zen Go TB |
Similar to the vocoder issue, except in my case it is midi rather than audio routing that is not supported for VST2. Not quite a deal breaker, but close
win10, old i5 machine (plenty good enough) S1Pro, Bitwig, Adam A7 monitors
https://greghooper2.bandcamp.com/ |
webhamster wroteNormally you can create a seperate midi track and set the midi output to plugin. Doesn't that work for crusherX? No, I have discovered this is because crusher-X is VST2 and S1 only allows midi input into VST3 fx plugins. Good news is crusher-X is going to go VST3 eventually
win10, old i5 machine (plenty good enough) S1Pro, Bitwig, Adam A7 monitors
https://greghooper2.bandcamp.com/ |
Users browsing this forum: No registered users and 57 guests