Using Pipeline with VST Instruments In Studio One Pro 3.5 ?

[Muziksculp]

Anyone know if it is possible to use Pipeline to send a VST Instrument's output to a HW Reverb in Studio One Pro ?

I am able to use Pipeline to send an Audio Track to a HW-Reverb via Pipeline, and also send a HW-Synth's Output to the HW-Reverb via Pipeline. But I an not able to send any VST-Instrument's Output to the HW-Reverb via Pipeline.

So I'm curious to know if this is not possible, or I'm missing something in terms of setting it up correctly so it works for VST-Instruments ?

Any feedback on this would be very helpful, and appreciated.

Thanks,
Muziksculp

[bustedfist]

In Cubase you'd use MIDI tracks routed to Rack Instruments and route the output of the Instrument Track to external kit. With the new Instrument tracks, I would assume similar. I don't use them, old school habits. You can set up external effects loops also, in VST Connections.

Anything sound similar to S1?

[xphen0m]

I'm sending IK's Modo Bass out to my external processing, so I'd say it's possible.

[Muziksculp]

I'm sending IK's Modo Bass out to my external processing, so I'd say it's possible.

Interesting, I can't see the audio signal from a VST Instrument showing up in Pipeline's wave display when I use Pipeline as a send on a VST Instrument. I also tried it as an Insert, but doesn't work either.

Can you share how you are setting Modo Bass Out to your external processor via Pipeline ?

Thanks,
Muziksculp

[Muziksculp]

Hi,

Here is a pic showing Pipeline Inserted on a FX-Channel, (Note : I also have the Bricasti M7 Control VST) inserted on the FX-Channel which remote controls the Bricasti M7 Reverb). The Bricasti M7 Control VST has no impact on Pipeline's signal flow.

As you can see in the first pic below, I have an Instance of Sytrus VST-Synth which I'm sending to the FX-Channel hosting the Pipeline that accesses the Bricasti M7 HW-Reverb via assigning the proper I/O for the Send and Return . Both Send and Returns are set properly, but there is no Signal Showing in the Pipeline Interface, although as you can see, there are signals registered in the console faders. So .. Something is not allowing the audio signal to flow through the Pipeline Plug-In.



Here is a second pic showing the Ping signal in Pipeline, and the latency setting to cancel out any phasing due to the I/O delay (37 Samples).

[Muziksculp]

Hi,

I finally got to the bottom of this issue.

Basically I had set the Audio Processing Preference Drop Out Protection to High, which enabled the new Low-Latency feature in Studio One Pro 3.5, well... Pipeline will not work with VST Instruments when the Low-Latency Audio Feature is Enabled. Because when I switched the Processing option to Low, and tried to use Pipeline with a VST Instrument, it worked !

So, if you want to use Pipeline, you need to disable the Low-Latency Feature, by setting the Audio Processing Drop Out Protection to Low.

This was a bit of a frustrating, and time consuming issue to resolve, but I'm happy I know what the issue was caused by, and hopefully this is useful info. for those of you who want to use Pipeline to process your VST-Instruments.

FInally, I wonder if Presonus can find a way for Pipeline to work with VST-Instruments when the Low-Latency feature is enabled (Processing Drop Out Protection is set to Maximum, High, or Medium), I'm guessing this won't be easy, or maybe it is impossible due to the very demanding calculations required for the audio engine to manage all the resources this type of functionality requires.

Here is a Gif showing a VST Instrument (Sytrus) sent to a Bricasti M7 HW-Reverb via Pipeline, when audio processing Drop Out Protection is set to Low.



Cheers,
Muziksculp

[LawrenceF]

This was a bit of a frustrating, and time consuming issue to resolve,

It's in the manual, see below. Pipeline (a high latency path by nature) is more of a post (mixing) effect, not used so much during initial recording and monitoring...

When monitoring an audio input or virtual instrument through the Native Low-Latency Monitoring system, any inserted FX on the corresponding Channel continue to function and can be heard in real time, provided that they add 3 ms or less of latency.. Plug-ins that meet this latency requirement show a green power button in the Console (rather than blue or grey). Any inserted plug-ins that introduce more than 3 ms of latency are not audible in the monitoring path while a Channel is armed for monitoring or recording under Native Low-Latency Monitoring.

[Muziksculp]

Thanks for the info. LawrenceF.

Yes, I should have figured this out earlier given it is mentioned in the manual.