dune 3 , when gui shows taskmager cpu increases

[gentleclockdivider]

Still the same problem , whenever the gui of dune 3 is shown ( useing the demo ) and tweking a control , the cpu in taskmanager goes above 40 % when there isn no actual audio processing (cpu in renoise is 2 %) .
When touching an on screen control , the gui of my host ( renoise ) becomes sluggish ,especially the osciloscope and spectrum view
I reallyy want to jump in on the black friday deal , but since I have already posted this one year ago I don't think a solution will come verry soon .
My pc is running win 10 ., all 064 bit plugins

You can download a demo or renoise and see for yourselves

I hope this get sorted soon


cheers

[Teksonik]

Does it only happen in Renoise ? I have not noticed this issue here in four different DAWs but I don't own Renoise. I have downloaded the demo but won't be able to do any testing until tomorrow.

If I encounter the same issue I'll report back here.

[Richard]

It seems to be a Renoise issue. I get a CPU spike under Renoise with any VST synth while turning a knob. It is only ~10% or so here, so not as bad as on your PC, but still noticeable.

[gentleclockdivider]

I think it has to do with the value's shown in the black display box .
Maybe the option to hide these , and see what it gives ?

[gentleclockdivider]

Hi this is the response of thedeveloper of renoise


quote

I could never replicate the high “idle” CPU load with Dune, but I can replicate the higher CPU usage when very quickly turning a knob in Dune.

Did a quick profiling of the fast knob mouse move in Dune. The CPU load is caused by Dune here. Below is a snippet of a the profiling.

SPluginChildWinProc is dispatching the windows events in the VST editor in Renoise (Events are mouse moves here). user32.dll is doing the Windows event stuff.

The CPU time then is mostly spend in DUNE 3.dll. Of course could be side effect of how Renoise handles VSTs, if this does not happen in other hosts, but I can’t “see” what dune is doing here, so I can’t do much here.

Function Name Inclusive Samples % Exclusive Samples % Module Name
TThirdPartyAudioPluginEditor::SPluginChildWinProc 80.26 0.03 Renoise.exe
TThirdPartyAudioPluginEditor::SCallPluginWindowProc 80.23 0.03 Renoise.exe
[user32.dll] 80.21 0.03 user32.dll
[DUNE 3.dll] 80.18 0.03 DUNE 3.dll
[DUNE 3.dll] 80.13 0.00 DUNE 3.dll
[lots of other calls in Dune 3.dll following…] 80.13 0.00 DUNE 3.dll
[user32.dll] 0.03 0.03 user32.dll




unquote

[HYPNAGOGIA]

Did some testings of my own.
Here are my readings from Demo version of Renoise:

Idle: 0.7-1.5% (Renoise) | 0.6-1.3% (Task Manager)

DUNE 3:
Loading: 2.3-4.7% (RN) | 1-1.7% (TM)
Moving a knob: 3.1-3.4% (RN) | 18-21.6% (TM)

THE LEGEND:
Loading: 1.2% (RN) | 3.8-7% (TM)
Moving a knob: 1.2-1.3% (RN) | 9.5-11.7% (TM)

SERUM (DEMO):
Loading: 1% (RN) | 0.2-2.4% (TM)
Moving a knob: 1.6% (RN) | 5.9-9% (TM)

ANALOG LAB 4:
Loading: 3.6-5.4% (RN) | 1.2-3.7% (TM)
Moving a knob: 4.2% (RN) | 6.5-9% (TM)

MINIMOOG V ORIGINAL:
Loading: 2.6-3.9% (RN) | 1-2.1% (TM)
Moving a knob: 2.9% (RN) | 5.3-7.5% (TM)

HELM:
Loading: 3.3-3.8% (RN) | 2.4-4.8% (TM)
Moving a knob: 3.9-4.4% (RN) | 8.2-15.4% (TM)

It's safe to say that a lot of plugins exhibit that behavior.
Maybe D3 just jumps more because it has more graphical elements. I don't know.
But at this point, I'd say it seems like it's on Renoise side of things.