I would also point out that internal messages such as pd-dsp-started don't really come with an expected behavior for user patches. Saying how it works is a "bug" belies that fact that I don't believe it was ever intended to be used for this and just because it can be grabbed via a [r] also doesn't guarantee anything. This is also why it's so hard to change almost *any* behavior within Pd as you can never really be 100% certain you aren't breaking someone's end use case.
On Feb 18, 2020, at 11:57 PM, pd-list-request@lists.iem.at wrote:
If, say, you want to send one and only one bang to [switch~] so as to graph tables when DSP starts, then [r pd-dsp-started] is only useful if you spigot-out future bangs/saves/etc, otherwise you are graphing tables on every save...
It's a feature if you use it for randomness, say, to randomize seeds according to when dsp on/off switching or graph redrawing falls, say linked with a [timer] object :)
Perhaps [r pd-dsp-started] should only send bangs when dsp starts or stops, and not when the dsp graph is redrawn.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
- Dan Wilcox danomatika@gmail.com [2020-02-19 10:38]:
I would also point out that internal messages such as pd-dsp-started don't really come with an expected behavior for user patches. Saying how it works is a "bug" belies that fact that I don't believe it was ever intended to be used for this and just because it can be grabbed via a [r] also doesn't guarantee anything.
The method you point out is shown in the help patch of [samplerate~] without any reference that it should be considered a bug or temporary measure.
This is also why it's so hard to change almost *any* behavior within Pd as you can never really be 100% certain you aren't breaking someone's end use case.
Do you feel this regression condition is much different in other software?
best, P
I would also point out that internal messages such as pd-dsp-started don't really come with an expected behavior for user patches.
I have to second Peter: the "pd-dsp-started" message is a public, documented message! It's just that not many people know it exists :-) Judging from the [samplerate~] help patch, the message has been added in Pd 0.47.
Christof
On 19.02.2020 10:46, Peter P. wrote:
- Dan Wilcox danomatika@gmail.com [2020-02-19 10:38]:
I would also point out that internal messages such as pd-dsp-started don't really come with an expected behavior for user patches. Saying how it works is a "bug" belies that fact that I don't believe it was ever intended to be used for this and just because it can be grabbed via a [r] also doesn't guarantee anything.
The method you point out is shown in the help patch of [samplerate~] without any reference that it should be considered a bug or temporary measure.
This is also why it's so hard to change almost *any* behavior within Pd as you can never really be 100% certain you aren't breaking someone's end use case.
Do you feel this regression condition is much different in other software?
best, P
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Christof Ressi -
Dan Wilcox -
Peter P.