N12 Audio Crackles Until It Stops Working


I’ve been encountering a problem where Nuendo 12’s audio starts crackling until it fully stops working. It’s only happening when I have Nuendo open. It’s like it’s not sure what the sample rate is? There’s nothing in particular that causes the issue.

Any suggestions on how I can troubleshoot this?

My specs are:
Windows 10
i7 6950X @3.5 GHz
64 GB Ram
Fireface 802 with latest driver


Does the audio sound like it’s sizzling? And degenerate over time until it’s gone?

What fixes it? Restart Nuendo? Reboot?

What is your sample rate etc.

What are your system specs?

Is your sound device USB?

I might have an insight but need info.

Cheers. P.

Hi Phil,

Yes, the audio starts to have small sizzling clicks that degrade over time. Usually restarting Nuendo fixes it for a little bit and then it returns.

Sample rate: 24bit/48k

My specs are:
Windows 10
i7 6950X @3.5 GHz
64 GB Ram
Fireface 802 with latest driver (USB)

Thanks for your help

Change your buffer size

Tried it but issue continues. This issue can happen in an empty session without hitting play. The crackle starts by itself and then gradually gets worse. I’m currently working on a simple piano sketch and I’ve had to restart the session several times, even at 512 buffer size.

1 Like

OK thanks for the info.

First thing to try is very simple. Move your RME to a clean USB port. Make sure you have latest drivers and firmware for the RME.

Try to find a USB port (direct in the back of your machine) that is not shared with other ports.

Drop a line back when tested.


1 Like

Hi Phil, I tried it and it’s seems to work so far. I don’t get how changing USB port would help, since the problem only happens in Nuendo, but thanks! I’ll report back if it happens again.

1 Like

Yup. Get a reasonable internet project. Put it on loop and just leave it running. You can actually browse and do other things, (don’t play audio from another application though).

Just leave it running for 15-30 minutes. Fingers crossed for you.

I’ll come back and explain why I pointed you to this in a bit. (Currently on phone, better to wait until I’m on main machine).