reaktor stability vs. reaktor session

by the looks of things on the reaktor forum, there doesn't seem to be too many complaints about stability these days. i don't know if you guys have seen the reaktor session forum, but just about every thread is about it crashing all the time.
i use session on a mac 1.67ghz powerbook with logic 7 pro. logic never causes me any problems unless i use reaktor session, with which it is unusable for any significant amount of time. at some point, usually when switching instruments or patches, it will crash logic.
what i'm wondering is, has anyone used both programs and noticed a stability difference?
i love the sound of reaktor but as it is currently with session, quite frankly i'm usually scared to open it in logic. i definitely don't need the programming power of the full reaktor, but i'd almost be tempted if it were rock solid. thoughts anyone?

rob

powerbook 1.67ghz 1 gb ram, firewire 410, logic pro 7.01, stylus rmx, reaktor session, crytal synth, albino 2, kontakt. everything validated.

 

reaktor 4.13 is rock solid when i use it with Logic Pro 7.01

i can't remember the last time it crashed....

i use a powerbook 1.67

 

I'm using Reaktor 4.13 and Logic 7.01 on a 1.5 PB (10.3.8) and its really stable, although I manage to cripple my laptops CPU really easily with reaktor. Only problem I've encountered is with EI2 Limelite. Something to do with internal event timing in logic.

 

oh ya, it's easy to cripple the cpu, but i'd use it mainly to make loops or record synth phrases, so i'm inclined to bounce quickly. i also have ei2, but i find with any of the sequenced synths, they don't sync right at all. limelite actually usually seems ok for me. krypt on the other hand rarely syncs up, therefor making it a bit useless in plug-in mode.
that's if i can even keep session open for long enough to even make a loop or play a phrase.

do the sequenced synths also not sync right with the full reaktor? especially curious about krypt and akkord, as they are always off..

thanks for the input,

rob

 

when you say "sync up" do you mean syncing up with other things in Logic, or just the clock.

i just loaded akkord and krypt (seperately) into Cubase SE and set a 4 bar loop ...and both seemed to be sycing correctly, meaning there were no glitches when the loop repeated.

one thing, if you close the reaktor widow, is the performance better?

btw, i did this test on a 1.33Ghz powerbook, using Reaktor 4.

also have you got your energy saver set to "highest performance" (Mac system preferences).

sowari

 

ok, just did some tests. seems like krypt (usually) syncs ok, however, it does not start on the proper beat. every time i started the clock, krypt would start three sixteenths prior to the end of its sequencer, meaning the first beat in the krypt sequence would play at the fourth sixteenth of logic's clock (when in 1/16th mode obviously). this seems to be a re-occuring thing with sequenced synths in reaktor session for me. same type of thing always happened with gobox. it would start at the wrong place in the grid.
does this happen for you guys with the full reaktor? as cool as ensembles like gobox and krypt are to me, i just don't want to use them when i have to first find out where the clock is actually starting on their sequencer compared to logic. i want to know that when i input data to sound on the first sixteenth or whatever note, that it will play at that note.
btw, sowari, thanks for the tips. i've always got it set to highest performance, and nothing is different with closed window.

if someone could verify this, that would be great, because i feel like i'm going a bit crazy. i usually just erase all the data from a krypt sequence for example, and put down hits on the quarter notes to see if its is syncing right, and it never does (although it is in time).
if this doesn't happen for you guys, then it may be time for me to upgrade. i'm not sure if other session users notice this stuff, so maybe that's why n.i. hasn't been made aware. or maybe i've made some crucial error...

anyways thanks again,
rob

 

concerning krypt, i just played it along side a repeated 4 bar break beat in cubase and it seemen ok to me, although on some of the snaps, there seemed to be a flammed first beat which did not happen again when the pattern repeated....

i have a vague memory of clocking problems with logic before?

concerning go box, this does not even reset istelf in standalone mode, (you have to reload it to do that) however
in the user library ther is Go Box mkII v1.0 By richard durham, this has helped some people with their sync problems.

the original version has a very idiosyncratic clock, and i don't think the builder was thinking of it as a plug-in in a host application, it is very much a live .ens. but try richard's version and see what you think.

as to krypt, maybe send an email to tech support?

sowari