# Tidal 2.0?

**URL:** <https://uzu.lurk.org/t/tidal-2-0/4247>\
**Category:** TidalCycles\
**Tags:** innards\
**Created:** [31 August 2022 13:44 UTC](https://uzu.lurk.org/t/tidal-2-0/4247 "2022-08-31T13:44:53Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![archaic.tech](https://uzu.lurk.org/user_avatar/uzu.lurk.org/archaic.tech/32/2965_2.png) [@archaic.tech](https://uzu.lurk.org/u/archaic.tech)\
**Post date:** [11 September 2022 20:29 UTC](https://uzu.lurk.org/t/tidal-2-0/4247/12 "2022-09-11T20:29:13Z")

</div>

I'd be interested in contributing, [particularly to implement some of the ideas I sketched out here and have never fully implemented](https://club.tidalcycles.org/t/rfc-improving-the-interface-for-interacting-with-tidal-streams/3528). The general philosophy here would be a fully-mutable Tidal engine, where it's possible to add/remove/reconfigure OSC targets, and define custom OSC control functions live. This would make it easier for boot code to come from multiple sources.

I really like the idea of an abstract `Pattern`! I'd suggest a special-case `Silence` pattern, that could also implement `eq` and such. Currently, there's no way to determine which patterns are silent/hushed, which I've wanted an editor to display.

I'm also very interested in helping figure out better editor integration. The work that's been done in Strudel with AST-based tagging of mininotation events is awesome, and it would be great to figure out how this type of metadata could also be passed into Tidal!

---

_[View the full topic](https://uzu.lurk.org/t/tidal-2-0/4247)._