Event Tables and Snapshots

I've been kinda stumped regarding the issue of getting an event table to have its values recalled within individual snapshots. I understand from what I've read that the event tables don't store information in snaps automatically, but you have to use other modules to make a macro to remember its values.

I was trying to reverse engineer the CS909 seq to do the trick, but I'm kinda baffled as to how to implement it.

If anyone can provide me a concise explanation of how to get my event tables to recall information from snapshots, or a ensemble with such an implemenation layed out simply, it would be hugely appreciated.

Cheers.

 

are you on R4 or 5? in 4 its much harder, since you need an individual snapvalue for each cell, plus a way of indexing them. in R5, you can use the sanpvalue array as a table, and use a mouse area over the table to draw in the data (see Lurker, which uses a multipic instead of the mouse area, but both work similar).

 

I'm using R5.

At any rate, thanks for the tip. To clarify, do you mean to use a snapvalue array in lieu of a table, or in combination?

I apologize if these are n00b questions, I've only just started on reaktor with version 5 a few months ago, although I've made some very nifty tools and learned a lot.

 

ok, heres the basic idea:

if you use a module to draw into the event table (like the mouse-area) you can have the events go to the snapvalue array FIRST. then, since in eventthru mode it passes out the events, they go to the WX/WY/W inputs of the table, which is the same thing as actually drawing into it. and when you change snaps, in "self iteration mode" the snap array send out the saved events in sequential order, which get re-written to the table. so the table really saves nothing, it just displays the events, and is also easy to use as a sequencer. it helps if you think of the snap array as another table, one that actually saves data, but has no GUI. you can also read right from the Array and use multidisplays to draw the sequencer data, but that is alot more hard work.

try to dissect this and see if you can figure it out. one of the trickiest things with this stuff is understanding how reaktor events work, and honestly after 2+ years im just starting to really get it, so give it some time.

one more thing...if you use this sequencer or make your own, keep in mind that anytime you change the size (X) or value range of the event table, you have to change them in the snapvalue array too. and if you change the value (0 to 1 currently) you have to change the mouse-area's Y-range (you DON'T have to for the mouse-areas X size though).

 

Thanks mate! Thats exactly what I was looking for, and its clear enough layed out that with some time, I should be able to wrap my head around the mechanics.

Cheers!

 

WOW!
really cool mini tuto

bookmarked!!!

 

=) t'anks!