Timeline

Hi!

I´m working on a project where an old tape-piece is to be programmed and performed from a laptop. In this occasion, I need to change several snapshots (mostly controlling the values sendt to an eventtable from a snap value array module.) I might do this using a DAW, (ableton) to send midi program change messsages, but I would like to keep the instrument as a reaktor exclusively, if possible. Is there a way to incorporate som form of a timeline function that, at given positions, would send program changes to various instruments? The piece is 5 minutes long, and just the thought of such a long eventtable makes me nervous. Not to mention the struggle to program it...

Any suggestions?

 

Does the event table need to be so big?

Without knowing more about the specifics of the problem I'd probably approach it in beats. I'd use an event table with 2 rows with the first row containing a beat number and the second a program change.

When the current beat matches the value in the current table column send the appropriate program change and move along to the next column of the table.

Or something like that.

Matt.

 

How very interesting!

I like your approach, specially since I don´t understand it. It means that I´ll be able to learn something, and at the same time maybe solve my "impossible issue." What a kick!
My experience with tables is quite extensive, but I always limit myself to use it in the manner described first, by the module itself: The table can be 1-dimensional (a row of values) adressed by X
I guess I never really understood the 2-dimensional aspect of the module.

Here´s a bunch of questions:

1. if the table gives out a value, say "3", how can I make the instrument or the ensemble interpret that as a program change? (The snapshot module, perhaps?)

2. You say When the current beat matches the value in the current table column send the appropriate program change and move along to the next column of the table. How would you program that?
In my world, the table would be driven by a clock of some form, thus calling for a table that is 5 mins, (or 300 beats) long.

2 b: Who, or rather what, would supervise the matching of the current beat and the value in the current table column? And how do I make it so that only the values in column (Y) 2 is send to the out-port?

Hopefully these are adequate questions.
Anyhow: I´m really looking forward to the answer; this could be it...

 

1) You can use the channel message module; use a value module to trigger the appropriate program change number from your event table output.

If you need help wiring up the channel message module, there are some good ideas here:

http://www.native-instruments.com/forum/showthread.php?t=107095

 

I've never done it myself but I am sure I have read about someone else doing it. But let's say I am wrong... in that case just use two event tables. The first table would have beat numbers and the second table would have corresponding program changes.

The table is still driven by a clock but indirectly.

Your beat table would contain beat numbers in ascending order. You would then use, for example, a counter module as an index into that table.

On each clock beat you compare the current beat to the value from the table. When they match you read the program change and bump the counter so that it indexes the next beat value in the table.

I'll leave that one to you for now. If you're still struggling after you've built it maybe post a concrete structure.

M.

 

Check out Massive 1.1 in the premium library provided by NI.
It has this instrument called "snapper" on top.

 

The snapper from Massive1.1
Yep. That's what you need.

 

Thanks everybody for answering!
I will look into it imediately.