just realized maybe it's not delread~ or delread4~ but an issue with delwrite~ :) - perhaps it just doesn't create a delay line as long as it says it does.

cheers

2016-05-02 2:44 GMT-03:00 Alexandre Torres Porres <porres@gmail.com>:
I guess you sent this update as soon as I started writing an email about this delay bug :)

anyway, trying the object on this release confirms that the bug i pointed ( https://sourceforge.net/p/pure-data/bugs/1217/ ) still exists.

I'm now trying delread~ and finding that it has similar issues, i added an example patch to that issue thread - also attached here

moreover, i guess you can update the help file of delread~ too, so you refer to the new [delread4~] object name instead of the now "old" [vd~] in the "see also".

cheers

2016-05-02 2:04 GMT-03:00 Miller Puckette <msp@ucsd.edu>:
Sorry for the noise -

I broke the variable delay reader in 0.47-0test3 - I've uploaded test4
to replace it... http://msp.ucsd.edu/software.htm etc. as usual.

cheers
Miller

_______________________________________________
Pd-announce mailing list
Pd-announce@lists.iem.at
https://lists.puredata.info/listinfo/pd-announce
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list