Event Tables and Snapshots Revisited

I was reading about this in an older thread: http://www.native-instruments.com/forum/threads/event-tables-and-snapshots.29437/

Kid_sputnik seems to be explaining it pretty well, but I need a more thorough walk-through since I am more or less clueless about what to do (precisely) when it comes to getting event tables to read data (wherever it's stored) for snapshots. Basically, I'm just using event tables for a Sine Bank module for additive synthesis, with a table size of 32. These event tables crossfade into each other to create an additive morph effect.

Here's the ensemble: http://www.native-instruments.com/en/community/reaktor-user-library/entry/show/8135/

My understanding is this: A Mouse Area module writes data into the Snap Value Array, then those values are fed into the WX/WY/W inputs of the event table. Now, while that's helpful (sort of), I'm still completely in the dark as to the fine points of actually implementing this solution. I'm afraid I need someone to hold my hand and walk me through this step-by-step.

Any help is appreciated. Please take a look at my ensemble to understand what I'm trying to do here. Thank you

 

this tutorial is so useful, i use it myself even though i wrote it:

http://www.nireaktor.com/reaktor-tutorials/using-multi-displays-in-reaktor-part-i/

 

Thanks! Since I'm not really building a sequencer, are there any parts of that tut I should disregard?

 

i don't think so... the input just reads the value at that point in the table. it can be used as a sequencer simply by reading out the values sequentially, at a given interval, but you can read them in any order or speed you want and it should be fine... i sometimes do minor modifications - you can simply download the .ens at the end and if it doesn't work how you want, just let me know what needs to be different.

 

So, I'm guessing that the Multi Display modules would replace the Event Tables in my ensemble? If so, how would I connect the Multi Display modules to the Sine Banks?

 

Okay, so now I think I understand it a little better. The Multi Displays are just there to display what's coming out of the Snap Array, which is receiving event data from the Mouse Area module. So, I deleted the Event Tables entirely and connected the Snap Array's Idx output directly into the Sine Bank's Idx input.

Now, there's the issue of crossfading from one Snap Array to the other.

 

Yeah, that doesn't work for my ensemble. I'm giving up for now. Lemme know if you have any ideas. Thanks anyway.

 

no, the event tables are there to hold the information. absolutely do not delete them. the multi displays are there because the event tables are ugly in a 2005 sort of way and they look it.

simply use an iteration module to read out all of the data from the event table at once.

 

LOL, good thing I saved that ensemble as a newer version. Back to the drawing board.

 

Okay. Here's how you connected everything in your tutorial...



And here is everything that is currently connected to the event tables in my ensemble going into the sine bank...



So, what is okay to disconnect? Do I disconnect the subtract module and the second output of the Order module from the RX and R inputs of the event table and connect the the Mod output of the Modulo in their place? Also, what do I connect to the Index and Apply inputs of the sine bank? Am I even going to keep any of those event modules feeding the event tables and the sine bank, or should I just get rid of those?

Sorry this is getting so technical. Thanks for being patient

 

Also try it:
http://www.native-instruments.com/forum/threads/event-table-snapshot-mod.219745/page-2#post-1284192

 

it looks to me like you can just replace the event tables you have with the macro from the tutorial. keep the order module, and feed the macro with the subtract module - which should be connected to the '2' output of the order module, not 1.

also, i think you need more events going into the 'app' input of the sine bank, probably an event equal to zero at each tick of the event clock would be a good idea.

btw, you might enjoy skywarp - check the user library.

 

I have Skywarp. I love it. I really like what you did with the reverb in that one.

Okay, I tried what you did and it's storing snapshot data perfectly, so success in that area

But the Sine Bank sounds weird, kinda growly, so you might be right about the App input of the sine bank. How would I implement an event equal to zero at each tick of the event clock? An Iterator?

 

just use the cr output of the system info module. use an order module, trigger the iteration first, then trigger the app with a 0.

EDIT - scratch that, i see you're using the gate from the iterator to trigger the sine bank - that code was a little tough to see. there must be some other problem.

is your ensemble mono or polyphonic? my macro appears to be mono so it could give you a problem in a poly synth (should be fixed by setting the modulo and the event table to poly).

 

Finally! I got it! I thought they were sounding weird, but then I realized I just needed to detune the pitch on the second sine bank. Everything works great! Thanx a million, and keep an eye peeled for version 1.3 !!

 

Crap. I think I celebrated a little too early. The sine waves still don't sound right.

Compare the latest version .... http://www.native-instruments.com/en/community/reaktor-user-library/entry/show/8135/

With the version I've been working on...

https://www.dropbox.com/s/tmaf54pj6blt3uu/Morphable Sine Bank x4 V1.3.ens?dl=0

The settings are almost precisely the same. The difference is huge. Something is definitely not right.

 

it seems to be working fine to me...

the difference between the two is that old one is using levels (decibels) and the new one is using amplitudes (0-1).

you could edit the multidisplay macro so the the mouse area, event table, multidisplay, and snap value array all use decibels by changing the ranges in the properties.

 

Yeah, I noticed the amplitudes were through the roof. I changed the range of the event tables in the macros from 0-1 to -96-0. Wondering If I should mess with X and/or Y ranges in the Mouse Area or the Snap Array?

 

I also noticed that the event tables in the multi-display module were in wrap mode, so I switched them to clip mode. Should I change them back?

 

my previous message lists all of the modules that need their ranges changed.

edit the 'Y' values, not the 'X's, where appropriate