@impression If you go the route of moving the GOP, [iemguts/canvasposition] will be of help, stick one in the subpatches/abstractions to get their location as needed so you don't have to track all the GOP positions manually, something like this:

@impression Dynamic patching can do all you need, [iemguts/canvasdelete] will be of great use and simplify everything, the iemguts library might have other externals which will be of use to you as well. Using [send] and [receive] and their audio counterparts instead of physical connections is nice when practical, lets you just pass the names to the [send]/[send~]/[throw~]s in the abstraction through its arguments. Previous post has some on dynamic patching and there is a good amount about it on the forum.

Moving the GOP could probably work, pd can handle a surprising amount, just stick a [switch~] inside of any abstraction which does audio rate stuff so you can turn it off and be sure to turn off any message rate stuff in the appropriate way when you hide it.

You can show a gop in a gop, what is not working for you?

@atux [bonk~] might work for you. It has been years since I have played with it but if memory serves for a simple source of 3 fairly different sounds like kick, snare, and hihat I did not even have to use the [learn( method, just get it configured right and I was able to use the color temp part of the right outlet and some [moses] to get bangs for each instrument. But I don't really remember the details and can not seem to locate the patch I used it in. The help file is not the greatest but other than the [learn( method it was fairly easy to figure out.

There is also pd-next which is mostly vanilla pd but with color themes and [closebang]/[initbang]. Nice for those that prefer vanilla but don't want to stare at a white screen.
https://forum.pdpatchrepo.info/topic/10943/a-little-pd-mod

@gentleclockdivider Realized I completely missed your point. This behavior is the same as it is with messages.

My guess is that the logic is that it will cause an error in the log window instead of possibly difficult to find problems. Imagine if you had a bunch of [text]s or [value]s or [send]s or what ever all with a common basename and one with just the basename, [v i], [v i1], [v i2] etc and were passing those names to abstractions through a float in their arguments with a [symbol i$1] in the abstraction, passing the escaped dollar argument means you get an error instead of accidentally setting the wrong [v] since it is very unlikely anyone would have an escaped dollar argument in the name of their [v] or what ever. If the symbol just combined with the empty symbol to create [symbol i] things would seem to work or might do something bad depending what your [v]s are used for and you will have no error message to control click on to find the problem, all you would know is that it did not work correctly.

@polyplexmescalia Most people won't notice the difference between aliasing and the weird smearing of low quality mp3s, so downsampling might be enough for your needs? Perhaps fake the smearing with an allpass filter/phaser on top of the downsampling?

@willblackhurst What are you using to make the screen capture? I never had an issue using ffmpeg and jack_rec. A bit of speculation, it is how PipeWire and Jack are setup, your screen capture app does not speak Jack and PipeWire is trying to sync the realtime audio from Jack with the non-realtime audio of what ever screen capture app you are using. Pure conjecture, I have not played with PipeWire enough to say for certain, and the time I have spent with it was quite awhile ago. Does your screen capture app speak jack or what ever you are using for audio in pd?

When I did this I believe I did something like this:

When you are done with your capture just run killall on ffmpeg and jack_rec and then use ffmpeg to combine the audio and video. Audio and video were not quite synced but they were close enough for the majority of cases and you really had to look for it to see they were out of sync, not difficult to fix if needed.

A little ridiculous, had to jump through some hoops to get that symbol back into a float. I used the -u flag of [fudiparse] so I could just use a simple [list split] in an earlier version but [fudiparse] and [fudiformat] should drop in now. There is some external which would make the symbol to float conversion easier but I can never remember which one it is and I have been trying to figure out the logic of why some float symbols will not convert with [float] and they weirdly are not even consistent regarding which hoops you have to jump through, first time I had to form a list and put it into a [text].

What about implementing your own fixed or floating point encoding for sysex? Break the float into two ints at the decimal, first first bit of the message is the length of the first int, reconstruct after the fudiparse?

Edit: Suppose a simple integer based fp implementation would not actually work here, did not think that through.

@Vnms nope, no python knowledge required, you just run the script with the output of the web app as args and it gives you what you need to stick into [biquad~].