Ableton Forum

redrobot wrote:the more cpu hungry ensembles in Reaktor I tend to record with the audio recorder inside Reaktor and then drop the audio into Live afterwards.

faster: set up an audio channel as a "record" channel. whenever you want to record audio from any source arm this channel and route the source channel into it.

if you start transport with the record clips slot in your RECORD channel and also stop the clip recording from there, the clips will be perfectly cut according to your global quant value.

ive used most methods of bouncing audio at one time or another and recently i started doing it this way instead.

this is definitely the fastest and most versitile, great for bouncing reaktor .. way better than that finicky little recorder bro ..
.

I'm using about 20 instances of reaktor with my new track and there is only one word, FREEZE.

My lead synth made with a custom instrument uses about 50-60% CPU, so it must alway be frozen to even move something in live. I've got about 10 of those 50-60% frozen so if they unfreeze for whatever reason, boom!

Freeze = 20 instances of a WAV file.

Not quite the same as running multiple Reaktors in a live situation.

-Ben

MrYellow wrote:Freeze = 20 instances of a WAV file.

Not quite the same as running multiple Reaktors in a live situation.

-Ben

Well duh. There is no way in hell you can run multiple reaktor's live without it blowing up. Why would I do that live?

Anubis wrote:In my experience the lighter ones draw 20-25% whie others draw 40 to 45%. The ensembles generally appear to behave rather quirky and not as stable as other Vst's in hosts such as Live. I've found that they're consistently reliable only when used as standalone.

I have to qualify my previous post by adding that I was referring to the ensembles included in the Electronic Instruments 2 suite. For example, Metaphysical Function and Limelite. Nevertheless, they still draw 25 to 40% in standalone mode. And thats just what Reaktor itself reports. Windows task manager reports about 50% CPU usage with these bad boys- again, as standalone apps! And they are still very finicky inside of hosts. Most crash Wavelab when I try to open the FX versions. However, these are definately the craziest instruments I have ever come accross and well worth the 'baggage'.

I got 38-40% on the performance test... Is this reasonable with a:

P4 3.0 Ghz (1mb L2 Cache)
1024 Ram 3200

?

Reaktor is a CPU eating beast, but it can be conquered. Try lowering your sample rate, this adds a downsampled distortion, great fot electro or drum and bass, or do as mentioned in another post and bounce your audio. There are also more efficient ensembles in the legacy library, which you have to unzip and install, but they all pale in comparison to the newer units. The only other way to fix the problems is to go in the enemble and edit it's construction to free up cpu.

Anarogue wrote:

MrYellow wrote:Freeze = 20 instances of a WAV file.

Not quite the same as running multiple Reaktors in a live situation.

-Ben

Well duh. There is no way in hell you can run multiple reaktor's live without it blowing up.[ ...]

wrong. Just wrong.

Is R5 a CPU hog?

Not on my system, AMD 64 3200+ 1.5 gigs of ram on windows xp sp 2

so no -

I can run a a couple instances of reaktor and reaktor efx like space reverb or flat blaster

plus all my other usual plugs (mostly ableton plugs)

I can say I've never hit more than like 70%

Albino's big huge pads kill my cpu - goes all the way up to 1 million and my computer just about has a heart attack

doh!

a

Have anyone experienced any stability improvements in the new 5.1 upgrade? Or did they just throw in a couple of new ensembles?

i got caught out when i first bought my laptop. I was using Reaktor sessions on a 1.6 Dothan and i only had to play a three finger chord using Carbon and the thing would melt down.

I simply thought is was the way of the world until i discovered the BIOS. Pressing F2 during boot up opened the BIOS screen. After tooling around i found the advanced screen and found CPU power was set to low consumption, i guess this is the optimum setting for anyone wanting to use a laptop on the move.

Anyway, i switched it to high consumption and Jesus wept, the meter reading in Live dropped from max down to 10%!! I felt like a bloody idiot

Anyway, just thought id post this just incase any of you guys happen to be crap with computers like me.

Benno wrote:i got caught out when i first bought my laptop. I was using Reaktor sessions on a 1.6 Dothan and i only had to play a three finger chord using Carbon and the thing would melt down.

I simply thought is was the way of the world until i discovered the BIOS. Pressing F2 during boot up opened the BIOS screen. After tooling around i found the advanced screen and found CPU power was set to low consumption, i guess this is the optimum setting for anyone wanting to use a laptop on the move.

Anyway, i switched it to high consumption and Jesus wept, the meter reading in Live dropped from max down to 10%!! I felt like a bloody idiot

Anyway, just thought id post this just incase any of you guys happen to be crap with computers like me.

Hehe, you made me happy again. Not that I am on a laptop, but that was a very nice and amuzing anecdote!