CPU and Rhino

Official support for: bigtickaudio.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Anyone care to share their CPU usage figures on the new Tim Conrardy bank. Some of the sounds are blitzing my Athlon 1.2!!

Post

You're right, these algorithmic presets really eat up a lot of cpu - as a matter of fact, any preset using the step sequencer is likely to be cpu-hungry, because a single note is actually turned into many more notes behind the scenes. There isn't much that can be done about that, unfortunately.

Programming sounds that are both impressive and easy on the cpu is not an easy task - Daniel is incredibly good at that, actually. Tim has only been using Rhino for 1 week, but with more time he'll get better at optimizing cpu usage. I can't wait for his second bank :-)

'Tick

Post

Hey! Since I'm here, perhaps we can talk about what we can do to optimize CPU when programming, so i know what to do on bank2 :)

For now: you can try turning off an osc or two on the algorithmic stuff and see if you can get the same effect without CPU overload.

Post

tconrardy wrote:Hey! Since I'm here, perhaps we can talk about what we can do to optimize CPU when programming, so i know what to do on bank2 :)

For now: you can try turning off an osc or two on the algorithmic stuff and see if you can get the same effect without CPU overload.
Reducing the number of voices is the easiest. Either you can do it, or we can if we have a smaller computer. Especially with the Algorythmics presets. Makes a big difference.

I'm using an Athlon 1600 with 1024 Mb ram, and still find that some patches get high cpu use. Most of the Algos have so much going on that more than three voices just muddies them up anyway.

Post

The only thing about reducing voices is that you are taking away the power of Rhino. Its suppose to be a 6 voice synth! Would perhaps taking off an effect help as well.?
Also i found if you keep the envelopes release time short, it helps on CPU.

Also: what about making a patch MONO. Would that help reduce CPU overload? or...even 2 poly, so at least you will still get the ring aftewards :)

Post

Here are a few more tips:
- set all unused envelopes to a flat line.
- make sure all unused oscs are turned off
- use shorter release times

Generally speaking, if you're able to achieve the same effect with less oscillators, you'll get a big improvement in cpu usage. The additive generator and the waveshaper can get very useful to use only 1 osc instead of 2. Of course, then, you'll be tempted to use the saved osc for something else :-)

'Tick

Post Reply

Return to “Big Tick”