Big Problem with Izotope Neutron 4 on C13 / Win11

After installation of Izotope Neutron 4 I faced
strange behavior! I am also using Izotope Nectar 4 and Ozone 11 without problems.

This happened for all projects on C13.0.21 and also C12.

Audio tracks are replayed, but not on the position I have select. Only the Locator area is played!

MIDI (VST instruments) and instrument tracks played no sound, but playing on the Cubase Keyboard in the Editor creates sounds. Also playing on the keyboard of a VST creates sound. But no track midi note is played.


Here no sound is played, notes are coming from Cubase track

Notes played on the keyboard of the vst instrument are replayed correct

Also notes in the editor Cubase keyboard are played well.

now it works.

I uninstalled Neutron and Neoverb and Cubase works fine!

Nevertheless: these Izotope products were not used in the tested projects, so I am a bit confused…

And I am confused, how a third party plugin can cause such massive problems. Must be somehow nested into the mixer area without selection. But why was no track note played?

Anyone else with similar issues?
My system setup:
Cubase 13.0.21
Win 11 / i7-14700k / 64GB RAM
Focusrite Scarlett 4i4
Maschine Mikro Mk3


Hi guys,
stupid question:
could such a problem be caused by Efficiency core handling of a i7-14700K?
Can’t believe that a 3rd party plugin can “shut down” core functions of Cubase that way…

After Update to C13.0.40 I faced exactly the same behavior as described above here in this thread. Cubase was not usable!

I am using a i7-14700k processor and tried deactivation of the Efficiency Cores in the BIOS.

THAT is the obviously the solution. After that change my projects ran fine.

I think that is an important information also for Steinberg.


1 Like

For what it is worth, I use Cubase 12 with both Neutron and Neoverb and have not had any problems. i5 with win10

I forgot to mention that I had the same problem with Cubase 12.0.70.

So the issue had to be independent of the Cubase release, but I would have expected crackles and dropouts instead of playing only some notes with a wrong timing.

@Steinberg: Feature proposal:
Why not scan the processor type during Cubase startup and display a message as a warning?
This would save users time and most probably also Steinberg support. :slight_smile:


I’m sorry, I can’t replicate it here on my side. But I’m on Mac.

As no other users are mentioning the same issue on the forum, I’m afraid, it will be something specific for your system.

Could you test your system by using LatencyMon utility, please?

not at home currently.

If you ask me: it’s something specific with the Intel 14th gen, maybe even specific for i7-14700k.