Matthew Kaney

I think that bus logic has been moved back out of the `Value` type, so the original code here (and in the current documentation) is still correct with recent Tidal...

I'd be interested in working out a fix for this. I'm curious, would it make sense to you for targets to listen for handshake messages on their own sockets (separate...

After thinking this over, I've changed my mind on separate ports. Thinking in terms of #797, I could imagine the control port becoming the sort of general-purpose OSC API for...

It looks like hosc currently hard-codes IPv4 sockets [here](https://github.com/rd--/hosc/blob/e14989eeb9012429c35ad9eb71eaf4bb78f96c69/Sound/OSC/Transport/FD/UDP.hs#L47) and [here](https://github.com/rd--/hosc/blob/e14989eeb9012429c35ad9eb71eaf4bb78f96c69/Sound/OSC/Transport/FD/TCP.hs#L51). I was testing out a patch that would fix that when I noticed another issue: it seems that any...

(Actually, `getAddrInfo` will still resolve "localhost" to "127.0.0.1" if you give it a hint expressing your preference for IPv4. Hosc should be doing that.)

Yes, that's exactly what I was suggesting—thanks!

We're discussing this over in #982, but I thought I'd pick up the conversation about the specific interface here. Overall, I think there are a few ways to simplify the...

I can add some context: this doesn't work because `trigger` internally uses a state lookup to get the time offset when the `d1` function was called (the actual code is...

All checks are passing! @yaxu, can you let me know if this is good with you whenever you have time? Two build changes: * `tidal-parse` dependency updates. Fixes #1069 *...

Btw, can you update the BootTidal.hs file so that it's easier to test this branch?