@Kate-O Welcome to the forum.....

It works for me.......... but the value to be updated (repeated when it matches) needs to be banged into the right inlet of [==]

If you want only values greater than the last output use [>= ]...... greater than or equal......instead of [==]....... as with [==] the spigot is only open when the input equals the last output.
David.

@myQwil I stopped receiving BBC radio stations on my internet radio earlier this year,
The BBC had decided to drop MP3 Shoutcast and only stream DASH and HLS.
I spent this evening searching forums for stream comversion backends for the RPI, and then remembered your external.
I don't live in the UK so I had to modify the BBC Radio4 URL slightly, and I now have a zero latency livestream of HLS in Pd on my laptop.
Next stage is to stream the output from Pd to the internet radio.
Then to stop playback as the client disconnects.
Then to run the patch permanently on my RPI.
It really is a very useful external.
Thank you,
David.

@zigmhount If a devicename is reported in the Pd midisettings dialog (I would expect that to be the case) then you can choose the midi ports to use for each Pd instance within a patch instead....... https://forum.pdpatchrepo.info/topic/13217/save-and-recall-midi-settings-in-a-project
This one seems a little easier to use........ set_midi-order.pd
If there are spaces in the names you can convert the whole name to a symbol that contains spaces with this.... concat.zip
David.

@noahdeetzers gop_switch.zip
Changes the properties of the graph on parent (GOP) window of a sub-patch or an abstraction.
This lets you "see" different parts of that patch in the parent patch, by moving the window.
Connecting wires are not shown in the GOP window, so the GUI is "clean".
In Pd extended only the "donecanvasdialog" method lets you change the values of GUI's (showing through the window) from the parent patch.
In recent Pd Vanilla the "coords" method lets you change the GUIs through the window, and works better than the "donecanvasdialog" method, which sometimes moves the GUIs in the window and creates a very messy view. That could be OS dependant..... I am unsure...
David.

@Blindekinder I like to have arrow heads on connections in edit mode..... cordarrows-plugin.tcl
tcl plugins must be loaded as Pd starts...... so just put them in one of Pd's standard paths, or a path set in "Preferences" "Paths"
David.

@esaruoho The simple immediate solution is [sigmund~] which is a standard object in Pd.
Single frequencies give the best results but complex audio can be analysed for the strongest frequency .
David.

@jameslo There can be spaces in the address.... the [oscformat] help is full of them between symbols.
Pretty sure [set patch 1( will correctly set the header although I cannot test with Qlab.
I think the "backslashes" were always in the workings of Pd..... just that up to version 0.4? they were totally reserved.....we could not type them (as is also the case in this forum) and they were not displayed.
David.

@esaruoho If your array max level is 1 and min level is 0 then you would multiply the "played" array by your [osc~] output using [*~].
So you need to "play" the array at your required speed.
If you want to do that once then you can use [line~] or [vline~]
If you want to do it repeatedly then [phasor~] ......

You will need to know the sample size...... the length of the array.... so that the [phasor~] output (0 to 1) plays the entire array.... as below........
David.

@esaruoho I might have made it too hungry...... updating every millisecond.
If you change the [line 0 1] inside [fade] to something like [line 0 250] it will output the list every 250ms which might be fast enough for your purpose, but stop dropouts.

But if you are adding the outputs of the oscillators together you could use just one [line] or [line~] to set the final summed level at 1 as [else/multi.vsl] sets their volumes, and then ramp down the summed level to zero in the required time...... which will be much more efficient.
David.

@esaruoho Split the message using [unpack] and then use [line] to decay each output ... and then [pack] to put the list back together?
this.zip ... is not very elegant, but fairly simple.....
David.