The event tick

Christopher List, in his Reaktor-Phile, says: "Anytime one event source has two wires coming out it, you need to remember that the two things "downstream" are not going to recieve the same event at the exact same moment.
Events are "procedural", which is to say, they do one thing, then another, then another - like stepping through lines of a program.
This all happens in one event "tick" - i.e. at effectively the same time in terms of milliseconds - but at a fine-grained level, one thing always has to happen before the other."

Well, I'd like to know if there's a way to point out the event tick, 'cause when I try to measure it with the Event History, it shows to me a 0 milliseconds delay. Now, is it possible that a event has 0 milliseconds delay from the previous one?

Sorry if I'm not very clear! Thanks

 

What's the minimum delay between two event ticks?

 

much lower (!) than one sample (audiorate) but you can not size it because as CList would say: "events are coming one by one" and all meters are only control rate based.
You can send hundrets of events during one audio sample! Use an iteration module f.i..

 

For all intents and purposes, they happen at the same time.
You can determine the ordering of events with some fancy structure programming to test it, but there is no measurable time delay between them. The time delay - if measurable - would be on the order of micro or nanoseconds, and is only visible at the CPU level - it's not visible at the reaktor software level.

In the same way that no two things *ever* happen at the same time on a computer with a single processor, the processor goes step by step through it's actions, but the steps are separated by time slices that are on the order of Gigahertz, so they happen so fast that they are, as far as we are concerned, instant. If you're typing in Firefox while a song is playing in itunes, those things are not happening at *exactly* the same time, the processor is switching back and forth between processing a little of the audio, then processing your typing, and so on. So the events in reaktor, as far as *measurable* time is concerned happen at the same time, but they happened in an ORDERED way.

The point I was trying to make in the faq is that you need to form in your mind the idea of a "tick" of the sample clock. A lot of things can happen in that one tick, but they will not all happen "at the same time" (or "instantly"), they will happen sequentially - one after the other in a very specific order. Rephrased: Each step in the list of things that will happen will occur at the same measurable time, but they will be ordered (and order the same way each time).

Note also that the sample clock is the lowest level of time granularity as far as reaktor is concerned. Events (and samples) cannot occur "between" ticks of the sample clock.

Hope that helps clarify this
Chris

 

yes they cannot occur between ticks but they really happen and you can see the result of that events at next audio tick.