Dealing with Legacy issues

I'm hoping to get some advice on how to deal with legacy issues

I've been building multi-fx ensembles, and often a warning comes up saying legacy mode is on and that Core Cell Modules will not work properly.

Should I usually say "yes" to turning legacy mode off?
What is the disadvantage of this?

As a builder should I strive to make ensembles that need no legacy?

What can be done to covert old legacy instruments?

 

you do need to turn Legacy off when you insert Core Cell Modules.

some older Reaktor Ensembles don't work properly if Legacy is turned off, so you need to see what works and what doesn't.

sowari

 

The main disadvantage? No event loops.

ew

 

Thanks for your help, guys.

Sowari - so next time that error comes up, I'll try turning off legacy, and then check to make sure the instrument is still working properly.

ew - that's good to know about legacy and event loops. Is it recommended to "Globally disable event loops" in preferences, and then enable "event loops" in the instrument properties if needed?

 

i would recommend not to check "Globally disable event loops" in preferences, but then enable them in macros/instruments if the warning sign comes up about even loops.

sowari

 

Agreed. You don't want to globally disable them; a lot of your R4 and earlier ensembles rely on them.

ew

 

Yes, and event loops are sometimes the sensible way to do things, so some R5 ensembles will need them (ok, mine will, i cant speak for anyone else!). To extend what Sowari said, I turn Globally disable event loops OFF, but then disable event loops at the instrument level, and then enable at the macro level. Disabling at the highest point under global is the key.

Correct me if I am wrong, but doesn't Legacy mode also affect the way global event resets work as well? I know R5 introduced a smarter event init system compared to R4. There is actually documentation on it (<Reaktor 5 Path>\Documentation\Technical Information\Initialization Algorithm.rtf or something like that).