This repository has been archived by the owner on Oct 3, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Home
Alex McLean edited this page Jul 6, 2020
·
13 revisions
Welcome to the tidal-listener wiki!
This is a work-in-progress and the below is not yet implemented.
Basic protocol ideas (>
, incoming message <
, outgoing message)
> /ping
< /pong
> /code <id> <source> - run code, get ok or errors back
< /code/ok
or
< /code/error <id> <error message>
> /name <name> - Set a name (optional, doesn't have to be unique)
< /name/ok
< /expand <code> - 'Expand' an expression into canonical mininotation, ref https://github.com/tidalcycles/Tidal/issues/633
> /expand/ok <expanded code>
> /port <number> - port listening to replies, if not the sending port
< /port/ok
> /highlights/on - get stream of active code spans+durations back
< /highlights/on ok
> /highlights/off
< /highlights/off ok
< /code/highlight <id> <row> <col> <row> <col>
> /cps - get cps
< /cps <number>
> /cps/set <number> - set cps
< /cps/set ok
< /cps <number> - sent to all clients ?
We probably need a way to add an identifier to incoming commands that gets added to outgoing commands, to help clients match up replies.