• 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!

Event FX render freak out

ianaeillo said:
I never run plugin nap and dropout protection is all over the place for me because I don’t understand how it works and my brain is too full to remember the sage words that Lokeyfly has said about it.

So here’s a correlation and why I think it might have to do with pipeline.

-If I have a session and I am rendering it to disk, because of my pipeline usage I can only bounce in realtime.

-while doing this, I often get an error that says “Audio engine dropout has occurred”

-When this happens, i either have to switch my dropout protection to something different and try again, or restart the session and try again

- I have discovered that 100% of the time immediately after receiving the aforementioned error, if I render an event fx or transform a track where the plugin is rendered/bounced the session will break. If I don’t receive the error, the session won’t break.

- I only get the error when using pipeline, of which I run 5-20 instances per session. However, I have also found out that it could be as few as one instance that can cause this.

-another predictor is that I also start to hear pops and clicks at the beginning of regions, as if no fades are on it or there is a clocking error.

That’s it. Sorry about all the words.
Click to expand...
I’m currently bouncing some outboard synths in real time. I have the audio engine dropout message, so once it’s done bouncing I’ll see if rendering event fx upsets it again…
 
soundofdrums said:
I’m currently bouncing some outboard synths in real time. I have the audio engine dropout message, so once it’s done bouncing I’ll see if rendering event fx upsets it again…
Click to expand...
Rendering event fx worked fine despite audio engine dropout out on previous realtime bounce 🤔
 
Update: I encountered this event fx render problem again just now where after rendering event fx most of my tracks stopped playing back. I decided to toggle mix engine fx on and off et voila, all my audio is back. So that seems to be the culprit. Specifically I’m using the Brit Console model. Anyone else noticed this behaviour?
 
Whoa. Okay. I use Alpine on *every* single session. I’ll try this next time it pops up this evening. Good thinking and thanks for reporting!
 
It worked! Hey! Thanks for this tip.
 
Nice! We’ve finally got to the bottom of this :)
 
soundofdrums said:
Update: I encountered this event fx render problem again just now where after rendering event fx most of my tracks stopped playing back. I decided to toggle mix engine fx on and off et voila, all my audio is back. So that seems to be the culprit. Specifically I’m using the Brit Console model. Anyone else noticed this behaviour?
Click to expand...
Nice. So toggling mix engine FX seems to clear some bottleneck, or buffers the audio rendering path.

I mentioned earlier that this rendering issue is by internal CPU . That still holds true. However, in Ianaeillo's case, there's likely some shaking hands with pipeline from CPU to audio interface. Still, the toggling Mix FX seems to clear that up for his needs as well. Maybe the future fix lies in some auto toggle that cleans this up.
Dunno, but glad you found the work around.
I think you'll be seeing an increase in your salary! 💰 🤑
 
Hey Guys,

it's really confusing to point an issue out here.
What I read is:

There is an issue with: Event-FX-Rendering
There is an issue with: Pipeline
There is an issue with: Mix Engine FX
There is an issue with: Reverse Reverb-Makro
There is an issue with: Dropout Protection

One requires the other, but does not have to. Also Plug-in Nap was mentioned. So I am totally lost to track this down.
Can you try to gimme the most simplified repro you can do? Start with an empty song. WITHOUT ANY VST! No irrelevant audio files in the pool. No hidden tracks. Just so many tracks as needed to show the issue. Exclude everything else that is completely irrelevant to the error.

Maybe then we all can find out what's goin on here.
Thanks in advance!
Ari
 
Ari said:
Hey Guys,

it's really confusing to point an issue out here.
What I read is:

There is an issue with: Event-FX-Rendering
There is an issue with: Pipeline
There is an issue with: Mix Engine FX
There is an issue with: Reverse Reverb-Makro
There is an issue with: Dropout Protection

One requires the other, but does not have to. Also Plug-in Nap was mentioned. So I am totally lost to track this down.
Can you try to gimme the most simplified repro you can do? Start with an empty song. WITHOUT ANY VST! No irrelevant audio files in the pool. No hidden tracks. Just so many tracks as needed to show the issue. Exclude everything else that is completely irrelevant to the error.

Maybe then we all can find out what's goin on here.
Thanks in advance!
Ari
Click to expand...
Yup. I’ll get on it this evening.
 
Ari said:
Hey Guys,

it's really confusing to point an issue out here.
What I read is:

There is an issue with: Event-FX-Rendering
There is an issue with: Pipeline
There is an issue with: Mix Engine FX
There is an issue with: Reverse Reverb-Makro
There is an issue with: Dropout Protection

One requires the other, but does not have to. Also Plug-in Nap was mentioned. So I am totally lost to track this down.
Can you try to gimme the most simplified repro you can do? Start with an empty song. WITHOUT ANY VST! No irrelevant audio files in the pool. No hidden tracks. Just so many tracks as needed to show the issue. Exclude everything else that is completely irrelevant to the error.

Maybe then we all can find out what's goin on here.
Thanks in advance!
Ari
Click to expand...
I understand the multifaceted processes by the two of us was confusing. We weren't trying to confuse anyone, just working through the problem between the two of us as we encountered it. I don't use SoundofDrums workflow and SOD doesn't use mine. We were attempting to work through the issue both of us were having. Neither of us were demonstrably saying much of anything, except what we observe to be happening when we get this error. I apologize for any consternation.

Question though. Are we allowed to use Presonus plugins to demonstrate whatever is happening here? Does Pipeline count as a plugin or VST? I can replicate it immediately in any of the sessions I am currently working on when rendering Melodyne as I showed in the video I posted. If it is allowed, however, I won't be able to follow the exact parameters of your request until Friday at the earliest, if this batch of mixes is approved.
 
"Are we allowed to use Presonus plugins to demonstrate whatever is happening here? Does Pipeline count as a plugin or VST? "

To prepare demo songs you can use everything that comes with a clean S1 installation. So you can use any plugins. VST on the other side is a technical standard a format to make different plugins of different vendors and different DAWs compatible. So a plug-in is not the same as a VST.
 
Last edited:
ianaeillo said:
Does Pipeline count as a plugin or VST?
Click to expand...
These are all plug-ins. VST is a special plug-in format (like AU, RTAS or CLAP). Studio One does not use any of these formats for its internal plug-ins, whether they are instruments (Mai Tai/Presence/etc.), or effect plug-ins (Pro EQ, Binaural Pan etc.).
 
Ari said:
"Are we allowed to use Presonus plugins to demonstrate whatever is happening here? Does Pipeline count as a plugin or VST? "

To prepare demo songs you can use everything that comes with a clean S1 installation. So you can use any plugins. VST on the other side is a technical standard a format to make different plugins of different vendors and different DAWs compatible. So a plug-in is not the same as a VST.
Click to expand...
Ok, this should make things clear. I have a fresh session with no 3rd party vsts, just audio files and a mix engine fx on my master bus (it doesn’t matter which model you choose). In my first video you’ll see I have a pipeline insert on an fx channel. Nothing is routed to that, it just exists in the song. If I put melodyne or any event fx on an event and then render it, most of my tracks will stop passing audio. If I toggle the mix engine fx off and on, my audio reappears.
In my second video I repeat the exact same process except that I removed the fx channel with pipeline inserted. Now when rendering the event fx everything behaves as expected. Conclusion: rendering event fx while there’s an instance of pipeline in the song (whether active or not) breaks the playback. For some reason toggling mix engine fx on and off unbreaks it 🤔
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Another update: if I don’t have mix engine fx in the song but keep the pipeline, rendering works as expected. Something is going on with the combo of pipeline and mix engine fx
 
Thanks @ianaeillo for the pipeline direction, I wouldn’t have been able to figure it out without that piece of the puzzle!!
 
You must log in or register to reply here.
Back
Top