Actually, [z~] is cleared everytime you change the right inlet (try feeding it with [osc~] and then switch between high values like 22000 and 44000, you'll certainly here the dropout)! I've just found out, that this is the behaviour my abstraction [cmavg~] needs for changing the number of samples to be averaged (together with clearing the [rpole~]). When you replace [z~] with a pair of [delwrite~] and [delread~], it won't work properly! So [delwrite~] definitely needs a method for clearing the buffer!
Gesendet: Dienstag, 08. Dezember 2015 um 19:37 Uhr Von: "Alexandre Torres Porres" <[email protected]> An: "Miller Puckette" <[email protected]>, "Fred Jan Kraan" <[email protected]>, "IOhannes m zmoelnig" <[email protected]> Cc: "[email protected]" <[email protected]> Betreff: [PD] no "clear" message option in [cyclone/delay~], [delwrite~] and [z~] As discussed in the previous thread, we can't clear delay buffers in Pd (you can do it with tapin~ in max, for instance), at least not with [delwrite~], [delay~] and [z~]. So we're pretty much tied up and needed it for an "moving sum" object or a "moving average" filter. It doesn't seem hard to allow a "clear" message into delwrite~ for the next update. [delay~] in Max actually can also clear, so we could add this feature in [cyclone/delay~]! and [z~] could also be cleared, maybe, why not? cheers_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
