My problem with a "clear" method for delwrite~ is that it takes a data-dependent amount of time to carry out. OTOH, there's a way to clear arrays. Some thinking is needed to figure out how to clearly distinguish between operations that are best carried out at "startup time" (whatever that means) and things that one can get away with in real time. I haven't figured out how to deal with this yet.
cheers M
On Fri, May 06, 2016 at 12:19:02AM -0400, Jaime Oliver wrote:
+1 on clear method for delwrite~ I have those forgotten snippets as a feature now and count on them, but it would be good for them to be optional. best,
J
On May 5, 2016, at 11:57 PM, Alexandre Torres Porres porres@gmail.com wrote:
2016-05-05 23:55 GMT-03:00 Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu>: almost ready to put out 0.47-0 for real :)
Awesome. I'd still have a couple of minor feature requests that I'd consider fair for this release so I'll insist on them; but I get it if you just wanna release it out for good - or if you have any thoughts against this or other issues, please share.
First: bringing back the paf~ external. I looked it up in the earlier releases and found the source from where it was last available (around 0.36 I guess). Here it is attached so you don't need to look for it. It kinda bother me that in the pd examples you mention it but it's not there, so if you decide to not bring it back, maybe remove this mention in F13.paf.control - but checking the source, seems like a fine code to go to waste :)
Second: Add a clear method message to [delwrite~] so it clears its buffer - this would be extremely useful when implementing some feedback reverberators and not that much work on the code.
Thanks Alex
<paf~.zip>_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list