11 posts
Page 1 of 1
Hi, I plan on recording audio from a polyphonic aftertouch vsti (arturia modular v) and I can't quite get the polyphonic aftertouch data to reach the vsti inside studio one.

Just to be clear, I am able to get polyphonic aftertouch to work perfectly when I run the vsti in standalone mode. Somehow though nothing happens when I try to trigger polyphonic aftertouch in modular v in studio one as if somehow it's being interfered with.

If I go in blocks dashboard and set the pressure tracking to one of the monophonic aftertouch modes like 'last played' then monophonic aftertouch works flawlessly inside of Studio One. It's when I set it to 'Multi-Channel' that it doesn't do anything even though it works just fine when the vsti is in Standalone.

I am at this point avoiding using MPE because I feel the implementation is just a crazy mess of channel messages and for now I'm fine with just being able to record the vsti audio output.
User avatar
by roblof on Wed Feb 28, 2018 6:25 am
Studio One does not support polyphonic aftertouch.

We have tried to get this support for years to properly record electronic drums, where it is used for cymbal choking.

iMac late 2015, Behringer X-Touch, X-Touch ONE, M-Air mr18, X-Air xr18, x32 with Dante/aes67, x32-rack with Dante/aes67, s16 and sd16 stageboxes, p16 monitor system, TurboSound iQ-speakers, Waves x-wsg with SoundGrid server, Motör 61, BCR-2000, StudioLive 24, FirePod 10, Apogee Ensemble, Alesis HD24, Studio One Pro v4, Notion 6, NI Komplete 11 Ultimate, Halion 6, Nuendo 10, Ableton Live 8 Suite, Reaper 4, misc Line6 gear/software, True Temperament Frets on basses and guitars, Korg Kronos, Roland vk-7, Behringer Deepmind 12, Behringer Neutron, Yamaha 02r.....
User avatar
by badsearcher on Wed Feb 28, 2018 2:24 pm
Wait, I was under the understanding that Studio One would at least 'not get in the way' of polyphonic aftertouch, like it would pass it through to the vsti.

It just can't record.

Considering I'm willing to compromise and just record the audio output from the vsti as I play, all I need is for the poly aftertouch to "reach" the vsti and then I'm in business.

Has anyone been able to accomplish poly aftertouch from a roli product reaching a vsti inside studio one?
User avatar
by niles on Wed Feb 28, 2018 2:42 pm
badsearcher wroteWait, I was under the understanding that Studio One would at least 'not get in the way' of polyphonic aftertouch, like it would pass it through to the vsti.

It just can't record.
Correct, but it only recognizes polyphonic aftertouch on MIDI channel 1.

OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • HD6450 (WQHD) • RME AIO
User avatar
by badsearcher on Wed Feb 28, 2018 8:57 pm
huh, well that doesn't make any sense because I open up Modular V in standalone and set it to only accept inputs from channel 1 and polyphonic aftertouch from roli seaboard works perfectly. Correct me if I'm wrong but that would show that it's transmitting all of polyphonic aftertouch on one single channel, yes?

Is it possible that I have to go into the text file that presonus creates for midi instruments and change some setting or manually add some line of code before studio one will pass through polyphonic aftertouch?
User avatar
by niles on Thu Mar 01, 2018 1:41 am
badsearcher wrotehuh, well that doesn't make any sense because I open up Modular V in standalone and set it to only accept inputs from channel 1 and polyphonic aftertouch from roli seaboard works perfectly. Correct me if I'm wrong but that would show that it's transmitting all of polyphonic aftertouch on one single channel, yes?
I'm not familiar with Modular V, so I don't know if its standalone operation is identical to the VST instance.
That being said. An easy way to check the channels of incoming polyphonic aftertouch messages (PolyPressure) in Studio One, is checking Studio One's MIDI monitor.

badsearcher wroteIs it possible that I have to go into the text file that presonus creates for midi instruments and change some setting or manually add some line of code before studio one will pass through polyphonic aftertouch?
Not that I'm aware of. But maybe official support can give a definitive answer.

OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • HD6450 (WQHD) • RME AIO
User avatar
by badsearcher on Thu Mar 01, 2018 3:15 am
I'm going to check studio one's midi monitor but at this point, I looked at the readout from the seaboard blocks using MIDI OX and can verify the seaboard blocks IS for certain sending out key aftertouch all on channel 1. But let's check midi monitor.
User avatar
by badsearcher on Thu Mar 01, 2018 3:18 am
Wait, yes, I'm seeing lots of polypressure midi ins from the midi monitor.

damn, so maybe there is some kind of impasse with modular v. I'm going to look for a different manufacturers' vsti to see if maybe it's just an issue with Arturia's VST's.
User avatar
by badsearcher on Thu Mar 01, 2018 3:43 am
So, I apparently still had an instance of the old version of Modular V which is a VST 2 and I fired it up and polyphonic aftertouch worked without a problem.

So, shoot, I guess the issue isn't on Presonus's end.

I wonder what it could be... maybe something to do with VST 3 in contrast to VST 2?
User avatar
by niles on Thu Mar 01, 2018 7:07 am
badsearcher wroteSo, shoot, I guess the issue isn't on Presonus's end.
Basically any polyphonic aftertouch issue related to instruments in Studio One is not a PreSonus issue because Studio One does not support polyphonic aftertouch (Poly Pressure).

That being said. I just did a quick test with a VST3 that is responding correctly to Poly Pressure messages in another DAW. The result is, it does respond on Poly Pressure messages, but incorrect. Only the initial value of the Poly Pressure message is processed at Note-On. So changing the actual pressure after the Note-On does not reach the VST3.

OS: Windows 10 Pro | HW: P9X79 • i7 3930K • 16GB • HD6450 (WQHD) • RME AIO
User avatar
by badsearcher on Thu Mar 01, 2018 3:23 pm
AH HA! Thank you for verifying for me!!! That's the exact same behavior I'm seeing.

So there is something off about the fact that it's a VST3 or rather how Presonus handles midi to a vst3.

Alright, well I have to see I can scare up a version of the VST that I want that isn't a VST3.

But again thank you, now I know I don't have to go bother Arturia when clearly the issue is Studio One's VST3 integration.

11 posts
Page 1 of 1

Who is online

Users browsing this forum: Tacman7, talanarney and 12 guests