In Pd vanilla, how does one query whether DSP is on or off?

I know you can send messages to "pd" to turn signal processing on or off, but I can't find where to ask the current status. (By the way, the search facility on this forum is really excruciating -- I did search this topic but you get hundreds of "matches" with apparently no concern for relevance at all.)

Context: I quite like the output~ abstraction in Purr Data, so I was seeing if it was possible to use it in Pd vanilla, but it complains about no [pdinfo] object. I can't find which external supplies this object. I'd be satisfied with an answer "install this external" or "here's the other way to query DSP state."

Thanks.

hjh

@jancsika good points, I agree. By the way, in Ofelia is an object called [ofGetDspState]. Getting mouse coordinates without externals is another example, there are some vanilla solutions, for example https://forum.pdpatchrepo.info/topic/10854/xy-abstraction-to-get-mouse-click-and-drag-coordinates-vanilla and some externals like [mouse] from else. I asked myself why there is not a simple object for mouse coordinates in vanilla (I think it still would be nice), on the other hand i am fine with using a (workaround) abstraction or an external if it is not basic enough or not needed from enough people. I can imagine that it is difficult to decide what is really important for Pure Data vanilla.

i think a concept of pure data vanilla is to have only a few basic objects, and everything (most of it) can be build with it, or with the help of libraries

Sure, I understand this, and I understand that every audio environment will, sooner or later, present obstacles for incoming users. I'm suggesting that the obstacles come up more quickly in Pd. To be concrete, if the new SuperCollider user is looking for a resonant low pass filter (not an exotic requirement), she goes to the main help page and from there, there are multiple paths through the documentation to find the answer RLPF.ar -- a built-in UGen that works like you'd expect.

By contrast, Pd has [biquad~], which "formally" does it but then... where is the coefficient calculator? Oh... I already forgot. And it takes the coefficients as a list, so you can't modulate at audio rate (so forget about filter envelopes or LFOs). So you give up and ask the forum, and wait a few hours for a reply. (Eventually I ended up with [omniFilter_abs~] based on MMB abstractions.)

I can accept that there's always going to be a difference of opinion about what is a "basic" feature. I guess I shouldn't push too hard because Pd isn't my main axe -- I'm using it for teaching because I need graphics for fall semester a year from now, but I don't use it for my own projects because I would rather build on top of a richly-featured framework than rebuild on top of a (deliberately) minimal feature set. So I should probably back off. At the same time, I get the feeling the experienced Pd user community might sometimes underestimate the degree of frustration felt by knowledgeable audio programmers coming to this platform and finding many, many basic things to be difficult.

hjh

Should also say: I'm writing deliberately provocatively. I've actually enjoyed digging into a different way of thinking in Pd, and the students take to it better than to code. GEM is fun, and Ofelia is even fun-ner. Just, no harm in noting where it could improve. (And, I did notice the comment about [text] -- tried it here a couple of weeks ago, much nicer than previous sequencing options.)

Thanks for listening.
hjh

@ddw_music thanks for your explanations. "....better than to code" actually that was a reason why i started with pure data. slowly i get a understanding of text based programming too. and there are definitely things that are much more efficient with text based programming. still pure data is my main programming language, and i think even if i would be really good at text based programming i would still use pure data regularly, because it is easy to use for certain things. i do not know how experienced programmers think about that... and i can not compare it to super collider, because i have no experience with it.
i am also more into sequencing than audio synthesis, but there are some more basic filters (in the audio filters section) if you open "list of all objects", and in the pure data doc are some more complex ones like H13.butterworth.pd. some of the doc filter examples are explained in more detail in this book, starting at page 256: http://msp.ucsd.edu/techniques/latest/book.pdf
and i have the feeling that open frameworks for example is at least not better documented, while lua is documented quite well (perhaps because there is a bigger userbase?). of course it would be nice to have a pure data library database where you can search for vocoder for example, and it shows all available vocoder objects and the corresponding libraries.
there is only a very old list as far as i know: http://blazicek.net/list_of_pure_data_objects.html
and of course suggestions to improve pure data, or anything else, are always very welcome.
so your main audio programming language is super collider?
can i ask what you use for graphics programming besides GEM and Ofelia?

jona

@ddw_music This is going to be a long thread.
[biquad~] was easy in extended.
Trying to convert a massive patch to vanilla I collated this.... stuff-coefficients.zip
Some calcs done at signal rate, others not.
Obviously strayed or I might have something more useful.
David.

@Jona "....better than to code" actually that was a reason why i started with pure data.

Sure -- different people have different cognitive styles, which is why it's good to have multiple tools with different approaches. I had a couple of students who really took to Pd, which never happened in the classroom with SuperCollider for me -- and that's more important to me than my own personal biases.

I can also see that some of what I'm experiencing with Pd is simply lack of fluency -- such as, there are efficient and inefficient ways to express complex math expressions in data flows. I simply haven't practiced those skills, so of course my perception is going to be that "it's really hard." (In SC, wiring up GUIs is admittedly harder than in Pd.)

so your main audio programming language is super collider?

Yes. Features that I feel are better developed in SC than in other audio programming environments are: polyphony (and parallel signal graphs -- not the same as parallel processing btw), glitch-free instantiation of audio UGens, and feature-complete implementations of standard data structures (multidimensional arrays whose elements are "variant" types, hash tables, queues and linked lists). These data structures have been invaluable in my big project over the last few years (a live-coding dialect for SC).

On the downside, both synthesis and GUIs are "heavy" in that there's more background involved -- hslider --> [osc~] is easy, SC sliders are not exactly hard to use, but more to learn at the beginning. So a lot of potential users probably give up.

of course it would be nice to have a pure data library database where you can search for vocoder for example, and it shows all available vocoder objects and the corresponding libraries.

Indeed... but maintaining such a list is a huge effort. SC has the same problem with third-party UGen plug-ins and class library extensions -- some great stuff out there, but how do you find it?

can i ask what you use for graphics programming besides GEM and Ofelia?

I've done almost nothing with graphics (no time), so only those two.

hjh

@ddw_music Please hammer away at the <ctrl-b> help browser in Purr Data by adding issues to the tracker:

https://git.purrdata.net/jwilkes/purr-data/issues

If it's not returning useful results for a term like biquad there are probably lots of ways to tweak it.

That help browser searches all the external libs that are already installed on your machine, so being able to successfully leverage that should address a lot of the problems.

Also-- please report if any of the externals are broken. I've never seen a single Pd external lib that shipped with tests, and we're talking about trivial bugs like broken arg parsers in a constructor, pointers to nowhere, etc. An unfortunate part of the Pd culture is that instead of reporting a bug a new user quickly learns, "if doing X crashes Pd then don't do X."

I mean, there's an XML parsing class that had a bug which ended up indexing past the end of an array for a core part of the algorithm. All that effort to do something as mind-numbing as string parsing in C, and the developer apparently never even called a method on it. It's like the code equivalent of 5'33".

Lack of feedback is something that discourage devs. And that's probably a reason why so many projects are never finished. And thus users are discouraged to contribute. Damn.

@Nicolas-Danet I think of it from the standpoint of the user-- there's almost certainly a low threshold of crashers and other bugs that the user quickly interprets as the natural state of the system,

That's esp. important for devs to keep in mind. I'm typically running Purr Data from the terminal where it will spit out a "fault" or some kind of error message to the virtual terminal. But for people running from a graphical menu Pd simply disappears on crash. Over time they may become anxious about doing any kind of business that could lead to Pd going away-- e.g., data structures, some external library, or even some method of an external library.

Add to that the open source "it's free" ethos and a user may be convinced that it would be rude to complain on the list that something isn't ripe soon enough for their tastes.

@jancsika "Please hammer away at the <ctrl-b> help browser in Purr Data by adding issues to the tracker"

OK, good to know. Actually I just reported one (https://git.purrdata.net/jwilkes/purr-data/issues/570) -- comport-help.pd is not found in the help browser, but the object is available.

Searching for "biquad" does turn up biquad~ help, but the problem is that the help patch illustrates nothing about calculating filter coefficients. It's just not useful for musical purposes without being able to specify cutoff frequency and Q. Sure, you can "build it" with what's given -- actually, I looked at that a couple of months ago, and decided it would take me at least a whole afternoon to hack up my own coefficient calculator, and then I just went looking for other people's abstractions. (Compare Max, where filtergraph is built-in, or SC where RLPF is built-in.)

I should also say WRT Purr-Data, I'm afraid I'm going to have to stop using it next semester. GEM is necessary for this two-semester course, and the media lab is all Mac. That Purr-Data for Mac doesn't support GEM is, unfortunately, a deal-breaker.

hjh

Searching for "biquad" does turn up biquad~ help, but the problem is that the help patch illustrates nothing about calculating filter coefficients.

Try the search again using the settings I gave in the comment under the issue you added to the tracker.

Using those settings, a search for "fmod" also returns "fmod". Unfortunately the search results aren't prepending the library name which is an issue that needs fixing.

Also I see that [creb/fmod] easily loses precision. I think I've got a fix for that...

That Purr-Data for Mac doesn't support GEM is, unfortunately, a deal-breaker.

I'm not sure what your original terms were. Are you in search of

1. the most suitable software
2. the most suitable free/open source software
3. the most suitable gratis software
4. something else?

@jancsika said:

Searching for "biquad" does turn up biquad~ help, but the problem is that the help patch illustrates nothing about calculating filter coefficients.

Try the search again using the settings I gave in the comment under the issue you added to the tracker.

Seen that, thanks.

That Purr-Data for Mac doesn't support GEM is, unfortunately, a deal-breaker.

I'm not sure what your original terms were. Are you in search of

1. the most suitable software
2. the most suitable free/open source software
3. the most suitable gratis software
4. something else?

Pd-vanilla plus a few specific external libraries will meet the needs of that course. Purr Data's GUI is more attractive, and the zoom feature is extremely useful in the classroom, but these are not critical. The ability to use GEM or Ofelia on Mac, Windows and Linux platforms is critical for me.

I suppose really "the most suitable software" is Ableton Live + Max4Live. But I can't in good conscience require students to use a specific commercial software package when I know, practically speaking, most of the students here will not pay for it. So FLOSS is preferable, yes.

But that's not really relevant to the comment. The point is that Purr Data is, unfortunately, not currently suitable for multimedia on an OS platform that is widely used for digital arts, while Pd-vanilla is.

hjh