Granular AudioTable - DEMO

demo of a recordable audiotable with two-grain granular playback

 (58 Votes)
Chris List
1.0 (Updated 19 years ago)
752.8kB
October 25, 2004
Reaktor 5 or lower
Experimental

DESCRIPTION

A simple demo instrument for a grainular audio-table player. The player can record samples loaded into the "Universal Sound Source" instrument - or the external input. The recording will happen when the "rec" button is pressed. Pressing it with no input will clear the audio table - so be careful!

Samples are played with the keyboard.

Use the scroll-bar to select which part of the sample to play. The Scrollbar settings are saved with the snapshot.

Enjoy,
Chris List
clist@mindspring.com


Techincal Notes:
- The audio table could be expanded in the "Y" direction and a knob added for recording / playing multiple rows of the audio table so that multiple samples could be saved - I haven't bothered to do this.

- The grain-player structure uses a classic "windowing" technique. The attack / decay of the window is currently fixed at 20% of the overall grainsize. This could be broken-out into a knob - like the normal grain-player module - by replacing the constant "0.1" in the GrainAmpEnv macro with a knob with a range of 0...0.5 (do not go above 0.5!)

Similarly, separate attack/decay times can also be achived by multiplying different knob values to the "up" and "down" inputs of the slew-limiter (the same spot in the structure mentioned above), however I find this to be nearly inaudible.

COMMENTS  (5)

Please login to add a comment
steffen goerke
19 years ago
fantastic i love your grains....
Phil Durrant
19 years ago
i echo stephen.
Omar Sharan
19 years ago
used it in a song . cool stuff
Red Wierenga
19 years ago
This is really excellent. Very good, clean design. Lots of potential for many uses. Thanks.
Chris List
19 years ago
...er, never mind what I said about the seperate attack/decay times. To be able to do this you'd need to add another SlewLimiter module to the structure. This is because the envelope for grain#2 is currently just the inverse of grain #1. That means the attack for grain #2 is the decay for grain #1. Obviously you could just add this second slew-limiter, but that would make a structure that's already a bit of pig cpu-wise even worse.
now