I have found [r pd-dsp-started] in [samplerate~] which give a bang when pd dsp start. But I would like to know if there is an opposite like [pd-dsp-ended]?

@algorithmicrhapsody I could not make that work for me on my windows system (extended though...... so I will try it in vanilla)...... but this should always work I think........

David.

@whale-av Unfortunately, it doesn't work in vanilla.

Perhaps it depends on the Pd version but normally it should work on vanilla. And what do you mean by [samplerate~] ? Normally it's an object with no help file so I can't figure out where you found [r pd-dsp-started].

Neat trick. It worked for me in Windows but not in Linux. Likewise, there is a help file for [samplerate~] in Windows but not in Linux, as Pierre said. Looks like this is a recent development that came in at the same time as [samplerate~] (0.45?), which means that it won't work on older releases also. David's solution is probably more reliable, but it's still good to know about this.

@algorithmicrhapsody Not working for me in win vanilla either....... but 0.46-7......
According to @Jojo Lapin 's link [r pd-dsp-stopped] should work?
David.

I still use 0.46.7 on Mac and there is only David's solution. With 0.47.1, I can use both solutions (and [samplerate~] has an help file):

Any clue why the symbol pd-dsp-started was added to Pd?

Is there any use for "pd-dsp-started" that is not covered by using the global "pd" receiver plus [route]?

@jancsika I am wondering if backward (and cross-platform) compatibility is being purposefully broken to push a "pure" data. It is understandable where tcl/tk is forcing new solutions as it develops......... but.......
Whereas the combination of extended and gem very nearly reached perfection, new issues seem to be plaguing this forum daily whilst vanilla is "teething", and with little real "advantage" to the user.
David.

@whale-av said:

@jancsika I am wondering if backward (and cross-platform) compatibility is being purposefully broken to push a "pure" data. It is understandable where tcl/tk is forcing new solutions as it develops......... but.......
Whereas the combination of extended and gem very nearly reached perfection, new issues seem to be plaguing this forum daily whilst vanilla is "teething", and with little real "advantage" to the user.
David.

I'm not exactly sure what you mean. Does the "pd-dsp-started" receiver only get a bang on some platforms?

@jancsika If we use [r pd-dsp-s_______ed] instead of the older [route dsp] it does not work prior to 0.47-1 on windows, but apparently, from reading above, [route dsp] no longer works on some platforms (it does still work under windows).
They behave differently though, so are not immediately interchangeable in all circumstances....... one is not a "drop in" replacement for the other....... care is needed.
Under windows 0.47-1 "pd-dsp-st_____ed" receivers get a bang when dsp is interrupted as well as intentionally turned on or off....... so when:
closing, opening or saving a patch, pasting or deleting objects, as well as or course changing the sample-rate,
More patches are having to be re-written for different platforms, with some deeper understanding of the differences..... and I think that is unfortunate........
That is all I wished to say.
David.

Well, I recently made a revision to [dsp-status(---[pdinfo] in Purr Data specifically to avoid reporting temporary suspensions of audio. That gets the user the ability to query dsp status with the least element of surprise. And it works for fetching the dsp status on [loadbang] which is the common case for querying dsp state. (And something you can't do in Pd Vanilla without a kluge.)

But I'm not sure I understand the use case for pd-dsp-started/stopped. Why would the user need to track all dsp graph rebuilds?

@jancsika I have not got around to trying your Purr Data yet. It seems to me that maybe you are ahead of the curve with respect to vanilla, and in your way doing what was done for extended back in 2013....... a huge amount of useful work....... making pure data actually work as expected!
Anyway, I will be quiet on this subject now, or I will be banned.
David.

@whale-av Why would you be banned?

Anyhow, it appears we already backported the "pd-dsp-started/stopped" callbacks to Pd-l2ork/Purr Data. So that plus [dsp-status(---[pdinfo] should cover most use cases.