Ableton Forum

all my live5 songs that ive been working on this past week (4 of them), cause live5 to shutdown when loaded. this happens any time i load them, when i restart or when live5 has been running from a fresh new set.
the common theme in all of them is stylusRMX and reaktor5. these sets loaded up fine the whole week but now live5 closes during the loading process.. no error message or anything, just closes.. and still shows activity in the task manager.

another theory is that the crashes are tied to the fact that the sets use limelite2 in reaktor 5, and i have had in the past problems with limelite2 crashing live4 on start-up, but they loaded fine, and the sets loaded for a few days.... im stumpted, and sad i cant access my new live5 tunes.... any ideas!!???

i have isolated this as a limelite (instrument in reaktor instrument vol 2)

anyone else have this issue. it drives me crazy that i cant open my sets.


please help!

just remove reaktor from your plugins folder.

and the set will load.

yes ben, i know that... appreciate the responce. but then what?
am i stuck without limelite in my tracks?
should i never use limelite in live ever.

im trying to reconcile if there is a way to control this bug so i can use limelite in live5... any ideas?

thanks again!

pentajigga wrote:yes ben, i know that... appreciate the responce. but then what?
am i stuck without limelite in my tracks?
should i never use limelite in live ever.

im trying to reconcile if there is a way to control this bug so i can use limelite in live5... any ideas?

thanks again!

Use it - resample or render it too audio then delete the instrument before saving the .als file Pentajigga.
It's a better alternative at the moment.
And atleast you can still use it.
Or download Voxengo Recorder (it's free) and whack that on the end of it to record .wav files for later use.

are you on full reaktor?

just save the ensemble, delete the plugin, save the live file.

then when you load the live file, dump reaktor on again, and load the ensemble.

if you're on a 'non-saving' version of reaktor then you may be in trouble.

ben - interesting work-around.. ill give it a try.. btw.. does anyone know what the deal is with this bug and if its being fixed on either NI or abes side?
thanks

this is all about NI. their memory management, preset management system especially with Reaktor is all fucked up. I have all but given up on it as a result.