Hmm, as far as I can tell, z 1 should already be sending to both targets, as you have superdirt and atomtarget in the oscmap for the atomStream. So you could just d1 = z 1 to use the d1 alias for this.
I have a similar question so I figured I'd post it here.
I'm looking for a way to send a duplicate OSC output to another port (that I'll receive using MaxMSP). So I'd like the exact same OSC messages going to SuperDirt to also go to this new location. I'd like to use Tidal exactly as I have been if possible, with d1, d2, etc, but have the OSC go to two places simultaneously. I'm guessing this is trivial once fully understood?
I've found the custom OSC documentation page, and I've been trying to hack a new BootTidal file together but my limited understanding is stopping me from getting this exactly right.
In the custom OSC docs example, I understand that this is where we 'enable' the multiple outputs: let oscmap = [(target, [oscplay]), (superdirtTarget, [superdirtShape]) ]
but the part in the default BootTidal file about starting the stream gets confusing because it also has the port assignments in it, so it's a bit hard to parse the differences.
This assumes that you schedule the incoming messages in max/msp - the osc messages will be sent in timestamped osc bundles in batches. If you'd rather tidal scheduled outgoing messages then you can do that like this: