The cursed, "CPU Overload" Cubase export error...

[Melb_shredder]

I've looked around the net about this and I seem to be one of many having this issue when exporting in realtime... I get absolutely no issues during playback and my CPU doesn't hit over 20% at most when Mastering, and yet it happens quite a lot when I go to export. It'll get a way through and BAM CPU Overload!

A quick fix was simply to up my latency from 3ms in my Hammerfall DSP driver to 6ms... Not a big issue, but that latency swap could cause issues during mix time.... And I don't get why that would matter if during realtime playback I'm issue free???

I'm wondering if anyone else gets this issue? I've only started using outboard gear recently hence the need for realtime exports

[Maamar Huq]

Sounds like a HDD/Ram issue to me.

[Melb_shredder]

^^ I won't rule that out at all actually... I'm ashamed to admit how little ram I'm actually accessing currently.. I'll give you a clue, I'm scared to move to 64 bit because of my worry my plugins won't all be fine when I make the change :P
So yo know what.. I am an idiot because I didn't consider that at all *facepalm*
However I do notice people with epic set ups still having this issue, so I figure the thread was worth discussing if others have had this happen

[botus99]

I may be completely wrong here, but it might have something to do with it being a 32bit program (and only accessing 2 or 3 gigs of RAM and idk how much processing power). Many times I would max out my CPU on Cubase, yet my CPU meter only showed ~60% of my processor being used.

I've run into that issue with 8gigs of RAM and a 3.3gz hexacore and had sessions ruined (forced to start over) because of this error.

[fenixdoido]

Don't export realtime,

[Pedro Teixeira]

^ - Wow, great piece of advice, I bet it never crossed his mind!

Melb: I get the exact same thing on a mix I'm working on. But this is on an 8core Mac Pro, which makes it even worse, the project is not heavy AT ALL and it still does it, the only channels that have plugins are the busses, the single channels have nothing on them, they're all previously printed and still the Asio Buffer meter is almost maxed out with just a few plugins, although I have to export in realtime cause of the outboard that I'm using.

Are you running a Mac? Because I read yesterday that Cubase and general audio has 4x better performance on Windows. Which is what I'm going to do, install fucking windows 7 on my mac and be done with this piece of shit

[Melb_shredder]

Originally Posted by fenixdoido

Don't export realtime,

Oh? Did you miss the 'I use outboard gear' part? :P I run everything through my GSSL and some other stuff so as far as I'm aware you couldn't possibly do it any other way

The thing is, like I said.. I'm using barely any CPU at all.. I don't see how 1 instance of HeQ -> Multiband (Outboard) -> and L1 could cause this issue?

But hey.. my fix seems to work for now... So hmmm!

@Pedro - I'm running an Intel Dual core e7500?? at 3.4ghz with Windows 7. Not Mac. I can't get used to them haha.

But as I said.. I can run projects with 50+ tracks and running extensive plugins and it won't drop out etc... But just on exports.

[Mutant]

A good workaround would be exporting offline, then doing the online export in some properly coded host like REAPER for example.

[Derykus]

So during the entire normal playback, you don't see even the slightest single tick or pop of CPU overload OR disk usage overload?

Could you just print the track to a stereo track in the project, and then export?

[Arsenu,]

hey have you ever considered not exporting in realtime?

[006]

Just run it through while playing back, record it to a stereo track and then export that. Problem solved

[Emdprodukt]

Originally Posted by Arsenu,

hey have you ever considered not exporting in realtime?

Have you ever considered to read before you write? He's using outboard.

[006]

Be he can export in offline mode... if he does it like I said.

[Emdprodukt]

That' still rendering in real time just without the cpu spikes (hopefully!). Never said he can't do it the way you described it!

[006]

I know, just more pointing out the guy you quoted isn't exactly wrong for saying it

[Emdprodukt]

Well he talks about NOT exporting in real time. Your method is still exporting in real time

[hoehlentroll]

Did u consider using tapeit (silverspike) on master?

[Arsenu,]

Originally Posted by Emdprodukt

Have you ever considered to read before you write? He's using outboard.

if it wasn't obvious enough, i'll add:

trolololololol

[Emdprodukt]

Originally Posted by Arsenu,

if it wasn't obvious enough, i'll add:

trolololololol

no it wasn't but maybe that's just me.

[006]

Originally Posted by Emdprodukt

Well he talks about NOT exporting in real time. Your method is still exporting in real time

Touché

[fenixdoido]

Originally Posted by Melb_shredder

Oh? Did you miss the 'I use outboard gear' part? :P I run everything through my GSSL and some other stuff so as far as I'm aware you couldn't possibly do it any other way

The thing is, like I said.. I'm using barely any CPU at all.. I don't see how 1 instance of HeQ -> Multiband (Outboard) -> and L1 could cause this issue?

But hey.. my fix seems to work for now... So hmmm!

@Pedro - I'm running an Intel Dual core e7500?? at 3.4ghz with Windows 7. Not Mac. I can't get used to them haha.

But as I said.. I can run projects with 50+ tracks and running extensive plugins and it won't drop out etc... But just on exports.

Man, for some reason nothing i wrote after the " , " appeared.
What I wrote was for you to Export Offline all the tracks that don't use outboard gear (print the tracks).

How is the CPU usage when you start exporting (F12 in Cubase)?
How is your DAW buffer?
Cubase 64 bits or 32 Bits? (if you are using 32 bits on a 64 bits Windows, it will emulate the 32 bits process)

Cheers

[006]

Why is this still a discussion?

I have already provided the answer. Melb, can you try what I said and report back?

[Derykus]

Originally Posted by 006

Why is this still a discussion?

I have already provided the answer. Melb, can you try what I said and report back?

Did you miss the part where I provided the same answer that you stole from me ya' little thief?

[JeffTD]

You're using an RME interface - you can use the RME Mixer to route outputs to inputs digitally and record the entire stereo mix to a new stereo track.

[006]

Originally Posted by Derykus

Did you miss the part where I provided the same answer that you stole from me ya' little thief?

I didn't read the replies, read the OP and posted my suggestion. Sorry... in that case, why is this still a discussion? Two people have already given a solution that will work 100%.