Reaktor save/debug mode?

Hi, i was creating new module for reactor community (mix of maths and distinct mk4 ), and i did something stupid- ive created some extreme cpu load loophole or something and managed to save ensemble before crash. Thats the only one ensemble i got. Now, its not possible to start it out, its just forever loading with crash. Is there any save-mode or something, that let me run the program to fix it or anything like that? Any chance to edit it?

Man, it was like two weeks of work and it was 99% finished (ive just making some final panel connections, and i think, one of the panel controllers set module to the infinite position)

 

That's a bad situation.

Always 'save as' and give a new name when you have made any significant changes to your work. Not just in Reaktor, but basically anything you are working on when using any kind of computer. And make backups often onto separate hard drives and hard copy media and upload to cloud storage if you have that option.

It might be worth reaching out to NI support to see if they would be able to retrieve anything from the file you have that crashes.

There is an option to 'save backup file before saving' in preferences. If you have that checked, then Reaktor generates a file that can be used to retrieve work if it all goes wrong, but it needs to be active. Not sure where Reaktor stores the backup files, because I use the manual 'save as' strategy.

 

My way is in front of the name the version number and at the end the release number like this:
400_iOS_r025
Every time I take a good hack count up the release and save it.
Or save it with a new count before create new unknown macros.
At the end of the day I create a 7zip file of the last release and move it in the folder devs.

 

@ Michał Gąsiorowski
Yes, please send them the file.
Reaktor crashes have high development priority.

 

When it 'crashes' does it crash to desktop, or just seem to freeze during the core compile?
If it's the second one, how long are you leaving it? sometimes it can take a few minutes (even 20 mins), but eventually get there, and you get one chance to undo your edit before you have to wait again.
This is a known issue and there are workarounds, so if it is that, we can probably help you fix it. Try loading it and leaving it for a long time to see if it eventually loads.

 

it seem to freeze during core compilation. but 2 hours is not enough for it to start Its a pity that you cant modify working code without compile it- at first i though that turning off audio enginge should do the trick, but it doesnt matter. Also, enselmble is binary file, so no way to edit it for example with text editor (unlike for example max for live instruments).

 

Hi,

there are some things I would try:

• Disable the Reaktor engine and use drag'n drop to add your ensemble as instrument
• Disable event loops in your global settings. This may reduce the crash to a warning pop-up and even help detecting the problem.

If you are able to open without a running engine, you should be able to fix the problem. Be sure to make backups with different names for each modification as the previous posts stated.

 

If it is the core-compiler that causes the problem I would also try to clean the cache.

 

Hi there, thanks for ideas, but i tried all that already