We have added expr and expr~ support this month and it should come to the plugdata toolchain shortly!

@donnerbono Latest HVCC now supports expr and expr~!

You will have to put 0.5 instead of .5 though

Some other limitations also apply: https://wasted-audio.github.io/hvcc/docs/02.getting_started.html#known-limitations

Clearly you need some header files. On debian based systems alsa/asoundlib.h comes from libasound2-dev

You need to install all the build requirements on your machine first ..

At least it's extremely fun to play with! -> https://github.com/evgenykochetkov/pd-mf

@crttrkix Subpatches don't get "passed on" values of anything. That's not how they work.

The name of a subpatch is just that: a name.

Everything else a subpatch inherits from the parent, $0 (identity) and any arguments.

Why would the subpatches have different contents?

You've put the same code in the subpatch inside the abstraction, so every instance of that abstractions contains the same code and subpatch.

If you are really this scared of the concept of a "chat room" then just post a dedicated ticket on github.

"MIT License with Attribution" is not a thing.
MIT License already requires attribution:

"The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."

So someone has to provide this copyright notice as part of any software that uses it, thus providing attribution.

Sorry to say, but your custom license does not appear to be valid open source. Or at least very disputably so.
I recommend that you pick a proper open source license: https://opensource.org/licenses

And we got a new release! many updates and bugfixes.

Full release notes:
https://github.com/plugdata-team/plugdata/releases/tag/v0.9.2

The patches to the book are online: http://aspress.co.uk/sd/

@atux said:

A real AI should be able to do this:

I don't think you understand what AI is or does

This is because symbol can't handle numbers, it requires strings.
By adding a string (- in your case) before or after $0 it turns it into a string.

Try using [f $0] instead:

New compiled mode features in the upcoming plugdata v0.9.2!

This doesn't make any sense. RTSP is for video streaming, and this specific package is for Perl programs ..

Why do you think this even remotely applies to this topic?

For sending midi over the network there is rtpmidi:
Windows: https://www.tobias-erichsen.de/software/rtpmidi.html
Linux: https://github.com/davidmoreno/rtpmidid

It is/should be built in on macOS.

But as said above OSC is probably easier to setup (and much higher resolution)

Yes.

For instance this monosynth patch that loads two separate waveforms and cross-fades between them:

@mbbaker No, a larger block size will allow the CPU more time to process the audio.

Use a larger block size?

You will have to create the same behavior using what is available indeed. Also checkout compatible abstractions like https://github.com/Wasted-Audio/heavylib (included in plugdata)

In the strictest sense you can use a "list", but not the [list] object.
A list is simply a message that contains multiple values, like [1 2 3 4(

Similarly you can use a table/graphical array (canvas object), but not the [array] object.