@oid Strange...... they work for me.....
Here they are again..... here.zip
David.

@gentleclockdivider @seb-harmonik-ar made a patch that you might find useful...... https://forum.pdpatchrepo.info/topic/7997/changing-the-creation-arguments-of-sel
David.

@snabb This should be useful.........
https://curiousart.org/digital_proj/pd_eBook.pdf
David.

@gentleclockdivider [div 48] will send a number every time [mod 96] sends a number to its left inlet.... like all objects. 0 for numbers below 48...... 1 for 48 to 95...... 2 from 96.... etc.
[change] is very unusual.
All objects send something to at least one of their outlets when they receive a recognisable message on the left inlet. If they don't recognise it as valid data they send an error message to the console.
David

@gentleclockdivider Almost all objects output something when they receive a recognisable message on their left (hot) inlet. Not when they receive on the right (cold) inlet..... the value/message is then stored in the object and will be passed on when the left inlet is banged afterwards, or overwritten by a new value/message to the left inlet.
Output is always from right to left.
[list] objects are a bit different but follow the left/right rule.
Some objects can also be "set" by a message to the left...... [set 25( will set a slider to the 25 position but it will not output anything.
Audio objects send a constant stream, but [metro] is one of very few that do so for control rate messages.

I posted this a while ago........ https://forum.pdpatchrepo.info/topic/13320/welcome-to-the-forum and there is a link "How Pd works" that should explain everything.
And it will be vital to understand the order of operations as your patches grow.
[print] is most useful for debugging.
David.

@gentleclockdivider [change] or [sel 1].
Boolean.... true/false.... will always send a 1 or 0 for every input...... and a bang will bang no matter what message it receives.

[moses] left outlet is < and the right > or =.
So maybe a [moses 48] feeding a [moses 49] from its right outlet if you don't want 48.
Or put a [select 48] before the [moses 48] as select will then feed any value except 48 to its right outlet.
David.

@oid Yes, I was going to get around to that.
I remember there was once a debate about whether a fast master and division or a slow master and multiplication would be better.
David.

@gentleclockdivider When you use the toggle you stop and then start both [metro] at the same time.
For them to sync you need to do the same when you change the timing for the blue metro.
You don't need to stop them, as a 1 to the left inlets will restart them.
I cannot edit your patch (using vanilla) so here is a partial screenshot..
David.

Changing just the tempo doesn't restart the [metro].
It bangs effectively after a delay...... changing the delay time during that delay "does just that" and it doesn't output a bang as the message arrives...... only as the delay expires... so it no longer syncs.

@gentleclockdivider Does sending a start at the same time to the [metro] left inlet help?
Between the green [/ 3] and the left inlet of the blue [metro] put the message [1 $1(
The parts of the message are distributed across the inlets of the [metro] so you know it gets them at the same time.
Disconnect the direct cord between [/ 3] and the right inlet of the [metro] of course.

When you say... "out of sync" ..... out of sync with the red [metro]..?
You might need to do the same for both?
David.

@FunkyEXP In Pd..... yes... you would create the following in your patch.......
Unity.... I don't know how it would handle that..... but I imagine that it will see the 12 incoming channels and you will have to organise them properly for the project.
I don't know of any external that would format a 5:1 Dolby etc. stream in Pd though, if that is what you were thinking. It will simply be the 6 mono channels from Pd..... raw PCM.
David.