Things that need to be done for full migration to untik:
✓ unstep: add untik support by using untik-clock-consumer
✓ unpunch: add untik support by using untik-clock-consumer
✓ qseq3: support untik (by using untik-clock-consumer)
✓ unstep: turn loop on/off (for metaseq clocks)
✓ unpunch: turn loop on/off (for metaseq clocks)
✓untik: advertize start/stop
✓ untik: advertize ~tick length~ tempo
✓ qseq3: define range, turn on/off range
✓ unstep: use div or not? yes
✓ unpunch: use div or not? yes
✓ unpunch: remove poly stuff
✓ unpunch: adjust clock selector appearance to GUI
✓ untik-clock-consumer: how to request a refresh parameters of a certain clock?
✓ ~think about support for existing saved sessions:~ do we want to take care of backwards compatibility? No, too complex
✓ untik: implement a handy looper
✓ untik: add async detection and correction (can be taken from master). Can this be improved so that it automatically detects drop-outs and adjusts clock accordingly?
✓ master: add support for untik
✓ untik: provide a way to provide a precise timestamp on request
✓ untik: implement a way to schedule events with future timestamps. Maybe attach a message to an event.
✓ untik: fix time-to-tick param; use it consistently for all clocks
metaseq: add support for untik
unpunch: add option to automaticall adjust grid|subgrid to beats|ticks of untik
These instruments, effects or abstractions use [master-param] and need to be converted to untik:
Things that need to be done for full migration to untik:
These instruments, effects or abstractions use [master-param] and need to be converted to untik: