Snap Value Array, with Sequencer Number?

Hi there,

I am following this awesome tutorial on event tables and does clear alot of things up for me. I have intergrated, successfully, a event table which modulates pitch which is able to store snapshots. As In I can have different sequences for each snapshot.

However my question is, which isnt mentioned in the tutorial, can I have the snap value array that stores the snapshots, and the knob "sequencer", controlling which sequence I can have.

So I can have 32 or so sequences which is later going to be modulated again, in a master sequencer, hopefully.

I hope this makes sense, I have tried hooking up my control in the YO and RY inputs of my event table, but it only works on sequence 0.

I have attached a screenshot.

Thanks very much...

 

No one can help you here only with a screenshot picture: you are using primary level only and are using no trigger-value- and order-conbinations so no one can see in which order events „are walking” through the structure.
The order is important for a right use of the snap-value-array. Which means: if two readers would follow to your picture only they will have a different way (order) to build the structure which means although they build the same structure the structures would work in different way which will potentially cause different results.
It is absolutely necessary to build the structure with trigger-value- and order-modules or inside of core.
So you have to think about order of events again.

ciao herw

 

As this is absolutely neccessary in understanding event-order in REAKTOR i will give you here a simple example:

Have a look to the very simple structure in picture 1.
Nothing special. Two identical structures with simplest algebraic calculations.
Debugging the event-initialization-oder doesn't show any problems (picture 2).

But now i change the knob 1 and knob 2 from 0 to 1.
First you can see with eventwatcher that one event from knob causes four events at the numeric readout. You don't see the fourth at the numeric readout but the eventwatcher (picture 3)recognizes four events (two events from the multiply module and in consequence four (!) events from the add-module).
But the main point here is that the results from both structures are only the same at the last event. The eventwatcher shows different intermediate results.
So thinking about your struture is only possible with order-value-modules for identical results mainly at the input idx and R/W at the snap value array and the event-table.

ciao herw

PS: how do i construct such a „bug”?
I inserted the modules of the structures in different order and connected them in different order. So REAKTOR interprets the „programming code” (the wires) in different order.
So if you want to see this effect you have to use my attached ensemble.

What is the consequence?
You have to use order-value-combinations to get an identic calculable structure OR you have to use core where this is no problem as all events from same source are calculated simultaniously (picture 4).

 

Hmmm, I can see the problem now.
I never knew the order of modules could have such an impact on stuff like sequencers. There is ovbiousley a problem which needs to be dealt in core, but I have absoultey no experience in it!
Thankyou very much for your reply you have been very hellpfull.

 

Where can I find the tutorial you are talking about?