Audio priority bug still exists

I had hoped the problem with the handling of audio priority in Cubase was fixed with version 5.5, but sadly it's not - yet. I've filled a bug report straight away, so I hope they'll fix it this time.

The bug results in pops and clicks in the audio whenever you initialize Reaktor as a VST or VSTi in Cubase (32 bit) - in my case in Windows Vista 64.

There's been a thread about this problem in the forum: http://www.native-instruments.com/forum/showthread.php?t=76540 - and the user Neverender even posted a wrapper workaround solution for the problem, which worked, but still it's not a sustainable solution. If others experience this problem, please report it! The more the merrier

Cheers.

 

Strange,

since with the Reaktor 5.5.1 beta release it's solved here in my case.
I'm also on Windows Vista 64, and I tried it with Reaktor as a VST and
also inside Kore FX in Cubase 5.5 32bit.
(I copied the new versions also to the IE plugin folder of Kore, so the new
versions are available from within Kore).

 

That does sound strange. I'm getting the exact same behaviour as I did with 5.1.5. Immidiately after initializing Reaktor the cpu meter shoots off spikes with the audio popping and clicking as a result. I also copied the new beta versions to the Kore plugin folder, but I haven't tested it yet - the prior experience just knocked me out last night. I'm hoping NI gets this fixed in the next beta release or I would have to go back to the wrapper solution made by Neverender, which just isn't a sustainable solution - but atleast it works

 

Hi,

I'm also getting the same issues that I had with Reaktor 5.1.5 when using the new beta - CPU spikes and crackling whenever Reaktor is loaded (Cubase 5.5 32bit, Win7 64bit, Intel i7 930).

Initially when just testing Reaktor 5.5.1 on its own within Cubase it seemed OK but as soon as there is any CPU load either from loading up 2 or 3 instances of Reaktor or loading it into an existing project, I get the same problems.

I've also logged it so we'll see what happens. Fingers crossed - apart from this issue still not being resolved, the rest of the update looks great!

Cheers.

 

please tell me that you are kidding... I beg you.


I reported this 2+ years ago!

Unbelievable.

 

Seems to be fixed here - I am using Cubase 5.5 on Win7/64 Pro based on a VERY quick check. Have tried both standalone VST and in KORE.....

But why are some still seeing problems? - is it to do with Cubase version perhaps? I'll try and do some more testing later.

 

Did some more testing after reading some of the posts here.
Seems I see the same behaviour as dre described.
Though the audio priority is NOT (!) reset to normal in my case, I also get CPU spikes and cracks after inititialasing Reaktor into a project, as soon as I move around the mouse - selecting tracks or if I open the Mixer a few times.

It seems improved to the prior situation, but still there's something wrong here.

 

I am still testing this, but it seems that I am still having the same problems with apparent cpu spikes in R5.5 on my quad core PC with projects that worked fine on my old dual core.

 

just wanted to add myself to the list of lucky ones ... i also have this problem since i moved to a quad core some months ago.
it seems to be related to multiprocessing and since it is happening on different hosts and vsts it might be some tech steinberg licenses to other companies like asio or vst.
just guessing though

in 5.5 it seems to be a little better...

 

Well,

I am glad I am not the only one experiencing this problem with Reaktor. Here has been my observations.

Cubase 5.1 and Reaktor 5.1 (whatever version before 5.5 is) - Cubase Priority changed from high. Nothing but CPU instability

Cubase 5.5 and Reaktor 5.5 - same problems but without the Priority changed from high. Same CPU instability

Reaper 3.63 or Presonus Studio One 1.5 with Reaktor 5.5 - No problems.

It is not NI fault I believe, Steinberg is having some kind of CPU scheduling problems with Reaktor.