Huge CPU spikes with Rhino...

[telephone]

Hello i'm using Rhino together Cubase SX 3.1.1 but when editing the envelopes the cpu rises too 80 90%!!!!!! My Processor is an Pentium IV 3 GHz.
If played normally the CPU seems to be ok around 10-15% with heavy patches.
I think this is not normal since all my other plugins don't react like that when editing envelopes.

I have also tried with Cubase SX 2.2.0.33 and the same hapened. Does somebody have a work around for this? Or is this a common problem known here?
Maybe some settings in Cubase?

Thanks any help will be apreciated much.

[bleebsen]

Just guessing, but sounds like denormalisation to me. A common P4 problem with audio plugins.

[telephone]

Just guessing, but sounds like denormalisation to me. A common P4 problem with audio plugins.

Can i do something on that? I never have had such problems with other synths before!

[Bojo Software]

I don't think it's a problem at all. The CPU can easily spike when the GUI is redrawn in plugins, but since it uses a thread with a lower priority it shouldn't give you any audio problems.

Bo

[telephone]

I don't think it's a problem at all. The CPU can easily spike when the GUI is redrawn in plugins, but since it uses a thread with a lower priority it shouldn't give you any audio problems.

Bo

Thanks for your reply! I also don't think it's amajor problem since it looks like it is not suffering my audio quality when playing in real time. Altough it is a strange thing to see.
And if there is a workaround for that i would be glad to know~!

I've found a threat here regarding denormalisation with a tool for that:

http://www.digitalfishphones.com/main.p ... &subItem=6


I wonder actually how i should put that plugtool in front of Rhino? It clearly says to put the tool in the first slot and Rhino in the second slot. In cubase i don't know how to get that?

[boin]

Just guessing, but sounds like denormalisation to me. A common P4 problem with audio plugins.

FWIW: I've been using Rhino for a long time and don't remember ever having a single denormal problem with it in the several PC's I used in the period.

[telephone]

Just guessing, but sounds like denormalisation to me. A common P4 problem with audio plugins.

FWIW: I've been using Rhino for a long time and don't remember ever having a single denormal problem with it in the several PC's I used in the period.

I'm not quite sure if it is a denormalisation problem since when i don't touch the screen the CPU usage is quite normal! If i use the slide bars there is still no problem, only when i drag on a envelope point the spikes occur!

But again no spikes when played or no sound that is not being played, and that is when denormalisation happens isn'nt it?
To be more clear when no sound is there denormalisation can occur! If i drag the envelopes it can still give denormalisation issues?.

[Bojo Software]

I'm pretty sure Rhino doesn't have denormalisation problems. The envelope redrawing is probably pretty complicated due to the versatility of the envelopes. When you drag the envelopes, Rhino has to redraw the GUI. This is what causes the CPU spikes.

I wouldn't worry about those CPU spikes.

Bo

[telephone]

I'm pretty sure Rhino doesn't have denormalisation problems. The envelope redrawing is probably pretty complicated due to the versatility of the envelopes. When you drag the envelopes, Rhino has to redraw the GUI. This is what causes the CPU spikes.

I wouldn't worry about those CPU spikes.

Bo

Thanks Bojo,

I will forget the whole issue, since there are no conflicts with audio signals.

Greets Wilfred.

[bleebsen]

Bad guess on me, then...

Maybe try updating your graphics card driver then. I had redraw issues with CamelAudio plugins until I did.

[telephone]

Bad guess on me, then...

Maybe try updating your graphics card driver then. I had redraw issues with CamelAudio plugins until I did.

Good to try out anyway! I will do upgrading! And let you know if that works out.

[Big Tick]

Envs drawing also uses floating point, so there may be a few denormals still hiding in there. Still, as pointed out, it does not affect the audio thread, and thus has no impact on the audio output.

'Tick

[telephone]

Envs drawing also uses floating point, so there may be a few denormals still hiding in there. Still, as pointed out, it does not affect the audio thread, and thus has no impact on the audio output.

'Tick

Hello Bigh Tick it is not a major problem i'm still happy with Rhino. My next comp will be a AMD dual core and for sure the problem will be solved then regarding denormalisation problems.

By the way installed the latest GraphicsCard driver with no results.


Thanks for all the help!!!!