![HiHi :hihi:](./images/smilies/icon_hihi.gif)
![HiHi :hihi:](./images/smilies/icon_hihi.gif)
I hope so... my copy of Reaktor Session is in the mail, and I was looking forward to finally trying out all the stuff that resulted from the Sickle vs. dburgan Reaktor wars... and I'm on a 1GHz Athlon, 512 MB RAM.dburgan wrote:Reaktor standalone seems to be pretty variable in how it behaves CPU-wise. A lot of the ensembles I threw together work fine on my laptop (60-70% CPU) but choke on my main music computer (which has a faster CPU and more RAM). Go figure. I'm not totally sure what the limiting factor is. Maybe the slower the processor, the better it works??![]()
It is strange - I can get away with running 95% of ensembles on my old Athlon 500 if I'm careful about samplerates etc. Tassman is equally erratic if not worse.dburgan wrote:Reaktor standalone seems to be pretty variable in how it behaves CPU-wise. A lot of the ensembles I threw together work fine on my laptop (60-70% CPU) but choke on my main music computer (which has a faster CPU and more RAM). Go figure. I'm not totally sure what the limiting factor is. Maybe the slower the processor, the better it works??![]()
Thank you Ian and Bluedad! You have just answered a major problem I've had with Reaktor Session.bluedad wrote: I heard a tip about running reaktor as a vst would help, and sure enough, my problems had been in stand alone. The cpu would immediately shoot through the ceiling. I tried it in vst and it was very workable then.
...Meaning people who buy a new computer every year? Hmmm...Sicklecell666 wrote:I had someone report that the had less CPU use on my ensembles when loaded into a host..
![]()
![]()
![]()
I don't care though..my shit's for the elite, anyways..
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement