AES 2 - Focus on Effects - DELAY

10 Apr 2018

With the continuing development of the AES we look at moving from our planning into our implementation stage. 

 

As discussed in the video ending blog 1 -  we are focusing on the effects of the AES first and foremost as they are the most important aspect of the design.

 

In this edition we were specifically targeting the delay, and how to stack multiple on top of each other within MAX.

Most importantly - we use something other than the 'delay~' node. #success.

 

The video attached is both short and sweet explaining in fair detail how we make our delay, stack it and implement controllability ready for OSC input later. 


It focuses around the tapin~ and tapout~ nodes within max (our development environment - sensible choice as its built for handling and processing audio)

 

max: https://cycling74.com/

tapin~: https://docs.cycling74.com/max5/refpages/msp-ref/tapin~.html

 

 

The tapin tapout combo is a nifty little object group within max.

 

It essentially allows the creations of a rolling buffer of variable length *using tapin*, that we can then callback into any number of times using tapout.

 

In the example at the bottom we make a buffer with 10000ms of data, that we 'tapout' 1000,1500,2000 worth of data from. The beauty of the rolling buffer means that these are able to create the delays we would normally expect in an audio environment to an unlimited (to the length of the buffer) scale!

 

 

 

 

In AES 3, we look at the frequency alteration effect (and maybe the timestretch if we have time [no pun intended])

 

Please reload

Join the PfP mailing list