And a simpler version, could be made more efficient on the reset side but I am not sure it is worth it. Not sure what I was thinking recreating moses with the swap/pack/route.
knob3.pd

Edit: went ahead and fixed the reset stuff, could still be made more efficient yet with a once between the bang of the [t f f b] and the [f ] but that is probably a meaningless improvement over the simpler [change]?

Edit (again): But I suppose there is no reason to test floats after the test has passed so sticking a spigot before moses would be a worthwhile improvement. Updated.

@dreamer said:

Larger might be possible, but I found that it's harder to hit the latching value as precision of the received value goes down and you may over-shoot.

You can just test if the number is larger or smaller than instead of equal to, a bit more complex and could be too much for the daisy but who knows, I know nothing about it.
knob2.pd

Edit: Suppose that bang should be triggered by the right float atom, forgot to switch that over, bang was mainly for easy reset while testing.

Edit: Actually it is not much heavier than the previous version, just a test which happens once to see if the number is larger or smaller then the previous and the route stuff. Have the right float atom go to the right inlet of the [f ], bang the [f ] and the reset bang once when this parameter is selected.

A couple which I have just come across and am looking forward too.

Berio's Sequenzas Essays on Performance, Composition and Analysis
Dhrupad: Tradition and Performance in Indian Music

Sadly the Berio does not include Sequenza 12 for Bassoon, what can you do.

@zigmhount said:

Pd with other MIDI clients from within the Pd patch.

I missed that, in that case I think I would just do it all in pd. Script to start pd instances so they are in known order (if needed) and then use [command] to get the port numbers and place them in suitably named [v ]s. Make your midi router a patch and then send your alsa commands out through [command].

@zigmhount I generally just pay attention to the order I start them in and specify the midi stuff at startup, pd -alsamidi -mididev 1 <files to open> first listed by aconnect will be the first started. The entire startup process including connecting the midi ports can be scripted so all you have to do is run a script and have everything good to go. I will try and get around to making my pd script a more generic startup/connect script if you want, probably can do it tomorrow. But perhaps someone knows a way to name them or has a better alternative. I just went with what I know when I made my script, more interested in making it all work then figuring out the best way.

@ingox Did you have a question? You did post this in Technical Issues Never knew append was implied if the arguments to [list] started with a float, feels like once a week I do [list symbol] and have to go back and add in "append." [text] used this way is much cleaner than any attempt I have made at anything beyond the simplest of recursion, still going to take pen and paper to figure this one out.

@seb-harmonik.ar So "here" in [send here] is a symbol even though it was never in a [symbol] or [list]? The names in named objects are implicitly symbols? In [1 2 3 here( here is a symbol and in the hash table because starting with a number makes that a list so "here" is a symbol but what about [this here( is an any (is that the same as a text/comment?) so does not end up in the hash table? I have been hoping that idea for [pdcontrol] to get the number of symbols in the hash table would happen so I could finally get a solid grasp on this.

Edit: Also, do symbols ever get removed from the hash table? If I delete ever occurrence of a symbol does that mean it is no longer in the hash table? Do symbols get removed when the patch that created them is closed?

@KMETE As far as pd is concerned a send and a receive is the same as a wire. The symbols used to name the send and receive may possibly cause things to slow down but you would need thousands of unique send and receives for that to be an issue and I am not sure if statically named send and receives actually have symbols which end up in the hash table. For all practical purposes, they are the same as wires and no faster or slower, but they can obscure the order of execution in surprising ways, especially when [value] is involved.

@Il-pleut said:

And I'm gonna stop there, I think...

My checking account will be happy about that.

@esaruoho I use a canvas on top of a [nbx], [nbx] gets from a [text] which has the info I want to display and is then applied as a label to the canvas, just click and drag like it is a numberbox.
lbt.pd

There is also https://forum.pdpatchrepo.info/topic/12960/a-drop-down-listbox-using-hsliders which is clever and works well despite some quirks but you get used to them fairly quickly.