I had this happen, not on mixdown, but from a high-CPU plugin (Waves PRS amp sim) waking up from Plugin Nap. Playing the song, as soon as it hit the region where the plug was used, CPU spiked to red and audio dropout. Disabling Plugin Nap for that plugin solved it. Maybe something to check?

Actually I found the problem. It’s the pipeline stereo hardware insert into my API 2500. When I disable the hardware insert then it fixes the problem. I tried turning off plug-in nap but doesn’t solve the problem.
Any ideas on why the hardware insert could be causing the cpu spike on the start of mixdown? I’ve tried to change a bunch of settings to no avail.

I'm getting exactly the same thing on v6.

5.5 I had exactly the same setup and template, nothing has changed, but now on every mix down I'm getting this message.

Robdp wroteI'm getting exactly the same thing on v6.

5.5 I had exactly the same setup and template, nothing has changed, but now on every mix down I'm getting this message.

Yes im the same. Was working fine with 5.5. But version 6 it's doing the CPU spike like crazy.

Does it do it every time you press play or only on mixdown?

ianaeillo wroteDoes it do it every time you press play or only on mixdown?

Only on mixdown. But when I turn off and on plugins it also does it. When I mute plugins it doesn't do it.

Most likely you've already tried this, but I always have an empty bar in front of the song. Sometimes there seems to be a little hickup when the songs starts right away.

tremo wroteI had this happen, not on mixdown, but from a high-CPU plugin (Waves PRS amp sim) waking up from Plugin Nap. Playing the song, as soon as it hit the region where the plug was used, CPU spiked to red and audio dropout. Disabling Plugin Nap for that plugin solved it. Maybe something to check?

Oh Wow

I just started having this issue last night when I tried to render (using pipeline). I’ve been trying to reverse engineer this, because songs I mixed earlier in the month are now giving me the same Audio Dropout Notification when they didn’t before.

I’m going to try your suggestion and see if that helps

Frank Crow.

joedarwish wroteActually I found the problem. It’s the pipeline stereo hardware insert into my API 2500. When I disable the hardware insert then it fixes the problem. I tried turning off plug-in nap but doesn’t solve the problem.
Any ideas on why the hardware insert could be causing the cpu spike on the start of mixdown? I’ve tried to change a bunch of settings to no avail.

Sir

Did you ever find a workaround?

Frank Crow

joedarwish wroteI've just upgraded to Studio One 6. Using M1 Mac Studio.

When I go to mixdown my song, as soon as I click OK to mixdown, the CPU metre spikes to red for a millisecond then continues to bounce the song. But it says there's an audio dropout detected due to the cpu spike right at the beginning.

The song is fine once it's mixed down with no actual real dropouts. But it's annoying that the CPU spikes at the beginning and gives an audio dropout warning.

I have my buffer size set to 1024 and tried medium and high dropout protection but still no go. Am using Universal Audio Apollo x6. My CPU usage when playing the actual song is only 60% on the metre.
Any help much appreciated.

Hi,

same here with Intel 12700K Win11 22H2 and 2x Pipeline XT for external hardware comps.

markusvogl wrote

joedarwish wroteI've just upgraded to Studio One 6. Using M1 Mac Studio.

When I go to mixdown my song, as soon as I click OK to mixdown, the CPU metre spikes to red for a millisecond then continues to bounce the song. But it says there's an audio dropout detected due to the cpu spike right at the beginning.

The song is fine once it's mixed down with no actual real dropouts. But it's annoying that the CPU spikes at the beginning and gives an audio dropout warning.

I have my buffer size set to 1024 and tried medium and high dropout protection but still no go. Am using Universal Audio Apollo x6. My CPU usage when playing the actual song is only 60% on the metre.
Any help much appreciated.

Hi,

same here with Intel 12700K Win11 22H2 and 2x Pipeline XT for external hardware comps.

I don't have an M1 like the OP but since you report that you're having the same issues with Windows I'd like to try to reproduce it with my system. Please give me the exact repeatable steps to test so I can confirm if this is a bug. Thanks!

Trucky wrote

markusvogl wrote

joedarwish wroteI've just upgraded to Studio One 6. Using M1 Mac Studio.

When I go to mixdown my song, as soon as I click OK to mixdown, the CPU metre spikes to red for a millisecond then continues to bounce the song. But it says there's an audio dropout detected due to the cpu spike right at the beginning.

The song is fine once it's mixed down with no actual real dropouts. But it's annoying that the CPU spikes at the beginning and gives an audio dropout warning.

I have my buffer size set to 1024 and tried medium and high dropout protection but still no go. Am using Universal Audio Apollo x6. My CPU usage when playing the actual song is only 60% on the metre.
Any help much appreciated.

Hi,

same here with Intel 12700K Win11 22H2 and 2x Pipeline XT for external hardware comps.

I don't have an M1 like the OP but since you report that you're having the same issues with Windows I'd like to try to reproduce it with my system. Please give me the exact repeatable steps to test so I can confirm if this is a bug. Thanks!

Hi,

I think the whole thing is a combination of the 12th gen Intel and Windows 11 22H2 (even worse since 22H2 forced update) thread director (or the same behavior on Mac with performance core (P core) or efficiency core (E core)). I would first have to find a setup where the behavior shows up even at low CPU load. Sometimes it happens there too (but not always).

Best regards
Markus

markusvogl wroteHi,

I think the whole thing is a combination of the 12th gen Intel and Windows 11 22H2 (even worse since 22H2 forced update) thread director (or the same behavior on Mac with performance core (P core) or efficiency core (E core)). I would first have to find a setup where the behavior shows up even at low CPU load. Sometimes it happens there too (but not always).

Best regards
Markus

Thanks for responding but please provide repeatable steps that I or someone else with those specs can confirm and report as a bug.

Trucky wrote

markusvogl wroteHi,

I think the whole thing is a combination of the 12th gen Intel and Windows 11 22H2 (even worse since 22H2 forced update) thread director (or the same behavior on Mac with performance core (P core) or efficiency core (E core)). I would first have to find a setup where the behavior shows up even at low CPU load. Sometimes it happens there too (but not always).

Best regards
Markus

Thanks for responding but please provide repeatable steps that I or someone else with those specs can confirm and report as a bug.

Hi,

I found out that since the forced update to Windows 11 22H2 there are more CPU spikes that seem to occur even when audio bouncing (and even if you do nothing in the DAW). Here are two screenshots of my computer with an empty Studio One template and a few audio tracks. I have added 3x Pipeline XT. I'm not sure if the issue is a combination of Apollo 8 and Windows 11 22H2.

Best regards
Markus

Did anyone resolve this?

Having the same problem with v6 on M1 mini. I feel like pipeline has something to do with it?

Back and forth with support but they don’t seem to believe me that it’s not a plug-in issue. Spikes right when I begin export.

adoniramlipton wroteDid anyone resolve this?

Having the same problem with v6 on M1 mini. I feel like pipeline has something to do with it?

Back and forth with support but they don’t seem to believe me that it’s not a plug-in issue. Spikes right when I begin export.

I don't have an M1 but if you provide the repeatable steps or attach a song that creates the issue I'll forward to the QA team to confirm.

Thanks. Intermittent power outages cuz if ice storms right now but hopefully I can boot up tomorrow.

I have a suspicion this is a pipeline related issue somehow.

adoniramlipton wroteDid anyone resolve this?

Having the same problem with v6 on M1 mini. I feel like pipeline has something to do with it?

Back and forth with support but they don’t seem to believe me that it’s not a plug-in issue. Spikes right when I begin export.

I went back and forth with support for a minute and finally just gave up. No matter how I tried to describe it they didn’t seem to understand. They often offered suggestions that I’d already told had been completed. It made me wonder if they’d even read my ticket. So far my work around is simply to not strip any track that I plan to use pipeline on. I strip silence my whole session at some point in my work flow but now I leave the kick, snares, bass and vocals whole until after I process and render. It seems to be the only workaround for me.

Mine spikes immediately when I use my dbx 160a but with multiple other hardware it spikes immediately at the beginning of the next event (no exception).