I thought about this for quite some time, but couldn't see that unifying the two would bring enough benefit to be worth it. In particular, the particular way wraparound is handled in delay lines might change with the iplementation, but making the actual storage visible as a table would lock us into one implementation.
cheers Miller
On Mon, Apr 11, 2011 at 09:27:30AM -0400, Mathieu Bouchard wrote:
On Sun, 10 Apr 2011, samuel rowe wrote:
I've been trying to modify some bi-directional delay lines I found in the archives At the moment I can only select the input position in the delay line, then connect it up to another one via a scattering junction and select the output position for the second one Ideally I want to only use one delay line and control the input and output positions in it,
What if you invented your own delay line using [tabread~] and [tabwrite~] instead of [delread~] and [delwrite~]Â ?
(I've wondered why delread~ and delwrite~ aren't just implemented using tables. Anyone knows ?)
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list