Event FX render freak out

[soundofdrums]

Anyone else have troubles rendering event fx? Most of the time when I render multiple event fx I lose audio for a bunch of other tracks in the song. Seems like a random cull, at least I can’t make any sense of which tracks remain working and which don’t. The only way to fix this is to remove my audio interface and reselect it. I’ve been having trouble with this for a number of iterations, so it’s not a new issue. I’m now on Mac OS Sequoia, m4 MacBook Pro, audio interface: UA Apollo. Any thoughts/workarounds/known issue?

 

[ianaeillo]

Anyone else have troubles rendering event fx? Most of the time when I render multiple event fx I lose audio for a bunch of other tracks in the song. Seems like a random cull, at least I can’t make any sense of which tracks remain working and which don’t. The only way to fix this is to remove my audio interface and reselect it. I’ve been having trouble with this for a number of iterations, so it’s not a new issue. I’m now on Mac OS Sequoia, m4 MacBook Pro, audio interface: UA Apollo. Any thoughts/workarounds/known issue?

Just made this video yesterday. It started in V5 but has been happening more and more frequently.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[ianaeillo]

It's also not just EventFX. I just ran Gregor's Reverse Reverb macro and the bouncing of the track made it break the session.

 

[soundofdrums]

Well, glad it’s not just me I guess, but yeah hope they sort this out soon. That’s the only thing I want from the next major update!
Have you tried disabling then reenabling your audio interface to fix it rather than reloading the whole session? That works for me.

 

[ianaeillo]

Well, glad it’s not just me I guess, but yeah hope they sort this out soon. That’s the only thing I want from the next major update!
Have you tried disabling then reenabling your audio interface to fix it rather than reloading the whole session? That works for me.

Yeah it's not just you. I've been trying to find the source of the problem but I can't nail it down.

I can't disable then reenable my interface because it's the master clock for a few other things and for a separate computer and it's a hassle to get everything back up. So restarting the session is it for me!

 

[soundofdrums]

Ah yeah, makes sense. Either way, it’s annoying! Strange that they’ve missed it in the bug fixes for so long, I would’ve thought it’s a pretty common and important feature. I wonder if it’s interface dependent somehow. What audio interface are you running?

 

[ianaeillo]

Ah yeah, makes sense. Either way, it’s annoying! Strange that they’ve missed it in the bug fixes for so long, I would’ve thought it’s a pretty common and important feature. I wonder if it’s interface dependent somehow. What audio interface are you running?

Two Metric Halo LIO-8 mkIV on one system, Presonus Quantum 2632 (the original quantum) on another, and a Yamaha DM3s on another. All three suffer from this.

Do you use Pipeline at all? Ive been wondering if it’s related to that somehow.

 

[soundofdrums]

Ah that rules out the interface speculation then. I do use pipeline but only on occasional sessions. This problem happens in all sessions regardless of outboard/pipeline

 

[lokeyfly]

....... The only way to fix this is to remove my audio interface and reselect it. I’ve been having trouble with this for a number of iterations, so it’s not a new issue.

Any thoughts/workarounds/known issue?

I've never come across this in any past versions of Studio One. It wouldn't be an audio interface issue, because rendering is an internal process performed by the CPU.
I don't have much to add as of yet, but I saw your and Ianaeillo's comments.

Likely worth looking at pipeline, or some routing.

 

[soundofdrums]

I've never come across this in any past versions of Studio One. It wouldn't be an audio interface issue, because rendering is an internal process performed by the CPU.
I don't have much to add as of yet, but I saw your and Ianaeillo's comments.

Likely worth looking at pipeline, or some routing.

I do have an instance of pipeline in my session template but by default it’s disabled. I’m guessing disabled plugins shouldn’t be able to cause problems? I’ll delete that while pipeline fx return channel and see if the problem persists

 

[AAV]

I've never seen the problem either, but 1) I never use pipeline - and 2) I am on windows (11). Use event fx all the time, including several ARA plugs and standard effects on a per event basis.

 

[soundofdrums]

Interesting. I’m in a new song now, same as my usual template and it’s not currently doing it, so clearly something I often do (that I haven’t done yet in this song) must be causing it. Maybe it is a routing thing of some kind

 

[lokeyfly]

Interesting. I’m in a new song now, same as my usual template and it’s not currently doing it, so clearly something I often do (that I haven’t done yet in this song) must be causing it. Maybe it is a routing thing of some kind

Glad its working so far. Just a thought is all, see if in the track/song you had this problem, that the track wasn't a stored preset track from another song. Then newly loaded. That might mean there was a stored effect on it that is no longer being used in that current song. Perhaps some dangling issue routing like that. Check FX sends, or bus sends no longer directed anywhere.

 

[soundofdrums]

Good call, I’ll go back into a song which isn’t working and check it out

 

[lokeyfly]

Cool. I'd like to think such things don't impact render at all. That they simply zero out. That seems to have been my experience, only developments as they happen, perhaps something unnoticed occurred and that's what you're seeing. Also, as I know respectfully M series Mac's are hugely powerful these days, make sure nothing is co contributing to internal processing on your Mac. At least what you can uncover. If it persists, its definately worth opening a ticket with support. Let us know because it helps others if they find your thread. Thx.

 

[soundofdrums]

I’ll report back. It’s actually good to see a session with the render working as expected because I seem to encounter this issue in most sessions. Might help to narrow down what is causing it if I can find differences between the sessions. One thought, since the last time I experienced the issue I’ve turned off plugin nap and have set my dropout protection to off. I’ll see if either of those trigger the issue if I turn them back on.

 

[lokeyfly]

Worth trying! I hadn't considered turning off plugin nap. I never turn it off, but that's not to say it isn't possible. Or dropout protection.
Give it a go.

 

[ianaeillo]

Yeah I can’t pinpoint it. I was waiting until I found a solution to post here, but it seemed like I saw a few people post about it on Reddit so I’m glad you posted about it Soundofdrums! Thank you.

Do me a favor Soundofdrums. In your sessions where it happens more frequently, could you try

Bouncing two regions together (Command+B)

And

Pick any track that has plugins and try Transform To Rendered Audio

I think I’m narrowing it down but I’m not 100%

 

[ianaeillo]

I’ll report back. It’s actually good to see a session with the render working as expected because I seem to encounter this issue in most sessions. Might help to narrow down what is causing it if I can find differences between the sessions. One thought, since the last time I experienced the issue I’ve turned off plugin nap and have set my dropout protection to off. I’ll see if either of those trigger the issue if I turn them back on.

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.

 

[soundofdrums]

Yeah I can’t pinpoint it. I was waiting until I found a solution to post here, but it seemed like I saw a few people post about it on Reddit so I’m glad you posted about it Soundofdrums! Thank you.

Do me a favor Soundofdrums. In your sessions where it happens more frequently, could you try

Bouncing two regions together (Command+B)

And

Pick any track that has plugins and try Transform To Rendered Audio

I think I’m narrowing it down but I’m not 100%

I’ll give it a go. Annoyingly I now can’t recreate the problem . Didn’t seem to have anything to do with plugin nap or dropout protection. Next time it happens I’ll try the bouncing and transforming