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~].

@Vnms I have used https://github.com/drmartinjaros/biquadgraphpd for calculating this stuff, makes it simple and might help you find your flaw and should work better than ChatGPT.

@gentleclockdivider manual or help files or here on the forum, too long ago to recall. Seb gives the full answer above, I put it in pd terms since most (including myself) find pd far easier to understand than pd's dense C.

Regarding Max's join, make it, just an abstraction away. [list store] mostly does that and a great deal more.

@gentleclockdivider Yeah, will fix that error. The first inlet in the case of [pack] is always a list, a float or symbol is just a list of one element list. Internally [pack] works like this:

So left inlet will always add the appropriate selector even if it is a single element.

@gentleclockdivider First inlet of [pack] and many objects treats everything on the first inlet as a list which it unpacks and fans out to the other inlets in order, a symbol or float is just a list of one element in this case.

This is standard behavior for vanilla objects. [pak] is not vanilla and many external objects go against vanillas standard behavior.

@FFW try this, open ffw-test.pd and see if it expands on mouse over and shrinks when the mouse leaves. Restart pd before opening it just in case you have one of those weird things going on caused by a confused instance of pd. This should work,
Archive.zip
Edit: if it doesn't work, what version of pd are you running?

@FFW That is because you are not sending 0 to the third argument and then 1 or 2 as I do in mine. Sending 0 to that argument disables GOP then sending 1 or 2 reenables it which tells pd to redraw and the reason for all that extra stuff at the bottom of mine. Try something like this for your minimal test:

This should make it work, donecanvasdialog does the exact same thing as the canvas properties dialog does when you click "ok" or "apply," this is the exact message the tcl/tk frontend sends to the pd core so if your canvas properties dialog works than this should work.

Edit: Fixed some errors in the image, had 1 instead of $1.

@FFW said:

And [donecanvasdialog( is worse: all the guis remain visible as ghosts.

With your version or with the one I posted?

Your issue with the seq helpfile is just an error in the helpfile, possibly who ever made it used a custom font which can cause such issues for everyone who uses the default fonts.