R5 & LimeLite Snapshot problem.. Please help

I try to make random snapshots in Limelite but fail to save them properly. The steps I go through are the following:
1. Click on an existing snapshot to load it
2. Set Random amount to 5
3. Click Random to get a new snap
4. Click Append (or Insert), enter name and press Enter.

The snapshot I just created sounds fine until I click on an other snap and then click back the one I made. The sequencers (all of them including Tie, Mod etc.) are VERY altered and not what I saved previously.

If I alter manualy an existing snap and then Append it (or Insert it) everything is saved correctly. The problem has to do only when I Random change snapshots.
I have tried everything. Append and then Enter. Append and then Overwrite a couple of times. The same with Insert instead of Append. I also checked and changed the Snapshot and Random Isolate settings in the Properties of the sequencers' XY modules in various combinations but got nothing. The problem insists. (Tried the same with Massive and everything seems to work fine there).

I'm new to Reaktor (not completly lost though..), so I would appreciate any info given.
Thanks in advance

 

By a search in the forums I realized that the problem has to do with Event Tables not been saved with snapshots. So, why normal altered snaps (no Random key used) are saved correctly?
I also found in the LimeLite structure that it's full with Snap Value modules which don't work with Random (as read in the info of the module). What if I replace on by one the Snap Value modules with Snap Value Arrays? Is this possible or should I go for the Massive Snapshot system? (mouse area above the table). LimeLite also has a Macro called Last Snap Value Recall (or something like this) which I also can't figure out what it does.
Please somebody give me some instructions.. I really want to make LimeLite work with random patches correctly. I have already made huge sample maps to use with it which took me weeks to complete and now I'm stack with such a simple thing (simple for most of you). I'm completly dissapointed with all these modules and their limitations. If only there was a book explaining all these..

 

I have seen crazy things created with Reaktor. I can't believe that LimeLite can't be modified in a way that it stores correctly snapshots created with the Random function. If not, so why the existance of this button???? I contacted a NI dealer to gather info and they told me that they hadn't tested Reaktor Electronic Instruments Vol.2 Pack but one of their sailsmen had recently purchased the Electr.Instr.2 XT version. So I asked him to test Limelite for me in his machine and the answer was..... everything is stored correctly!!!! What's going on?...

Can't anyone give me a clue??
..Forget it or shut up accepted as well..

 

Sorry, I can't help, but just wanted to say I have the same problem. I just forget it and program the damn thing myself just like in the pre-random days of olde yesteryear. I agree though it sucks, its still an awesome program you have to admit though.

Maybe NI can come up with a patch like they did for some of the problems with some of the ensembles in Electronic Instruments Vol 1.

 

it is possible that LimeLite was not created with the idea of using the Random button. the ensemble is based on LimeLite in the user library (made with Reaktor 3) which was based on drum machines such as Dirty Groovy (made with Reaktor 2). i think i am correct in thinking the random button you describe was part of new things in Reaktor 4.

so i cannot help, apart from suggesting that you programme new snaps rather than use the random button.

sowari

 

in the original version of limelite, it uses buttons for seq steps. i think those can be randomized with the snapshot module, but im not sure. the EI2 one uses snapvalues and an XY (makes me think he was building in a way he would have in R5 with SnapValArrays and Multidisplays). as you said, its the snap values modules problem.

 

i've had the same problem with limelite. every time i program a new patch in limelite i just record two to twelve bars direct to audio so i can be certain it will be available later. i've downloaded limelight from the user library 6 times because it keeps dying on me. the random button is really the problem in my opinion, because the crashes always occur after i'm random merging a couple of patches i've programmed.

is there a way to fix this (i'm not afraid of reprogramming).

 

First of all I'm not a programer (..but I'm willing to be though soon!..). BUT from an extensive search I have made on this subject I came to a conclusion that it CAN be reprogramed to work with the Random concept correctly.
The general idea is to remove the Snap Value modules (which don't work with the random operation) and replace them with snap value arrays (which can store table information with the snapshots), XY modules for the sequencers' displays and Mouse Area modules over the XYs to collect the mouse movements and clicks and transfer them in the XY or Snap Value Arrays (I'm not sure). A good structure picture of what I describe resides inside Massive from R5's Library (and Lurker).
This reprogramming can apply to other older but great synths as well. Vierring for example can benefit from random creating snaps.
I also have a project idea on LimeLite that can be applied to Massive as well: Forget the Random button. Wouldn't be great to create a randomization section inside the instrument? Imagine 4 buttons with randomization amount input field next to any one of them. One button for the rhythm section (Kick, Snare & HiHats), one for melodic (Tie & Pod), one for fx (XFX, Delay, Filter and Pitch Shift) & finally one for all of the instrument (with dedicated switch to include or not sequencers' steps randomization).
Please any experienced user's comments are needed.. Can this be done? And if yes what are the traps that must be avoided?
Take it serious!.. LimeLite and Massive are GREAT pro synths. They introduce you the Reaktor side of music but ALWAYS stay musical and groovy (with randomization amounts 3-5%..). When I work on a project I make an audio mixdown of the full arrangement without the drums (16 bars of the main theme/section is enough) then I split the exported audio into bars (every bar a separate audio file with small fade ins & outs to avoid clipping) and then I import these samples in Limelite and Massive while using them as VSTis in my initial full arrangement and start programming & randomizing. Imagine what's happening!!!!... From the time I started using them many people in the studio keep asking me "wow!!!! how did you do this and what's that???.." )))

If LimeLite and Massive where hardware units from Roland or Korg (or even the new groovy Daft Punk synth by Access called Virus GroovePlant or something..) they would cost 3000euro each and they would certainly turn out to be classics (the TR909 of the new millenium)!!!!!...

Thanks for reading

 

interesting reading...3 things

1...why do you need to have small fade in and outs on your audio? if you carefully edit your loops so the the beginning and end are zero (use the zoom in on your audio editor to do this), then you don't have clips.

2...why can't you get similar results by progamming LimeLite?

3...have you had a look at rick scott's uploads in the User Library? he loves random stuff.

sowari