# 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:** 4\
**Page:** 3

<div class="post-metadata">

**Author:** ![mashaal](https://uzu.lurk.org/user_avatar/uzu.lurk.org/mashaal/32/2100_2.png) [@mashaal](https://uzu.lurk.org/u/mashaal)\
**Post date:** [3 June 2023 06:44 UTC](https://uzu.lurk.org/t/tidal-2-0/4247/41 "2023-06-03T06:44:03Z")

</div>

Is there an way to test 2.0 out? Is there a specific branch to build locally?

---

<div class="post-metadata">

**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\
**Post date:** [3 June 2023 09:40 UTC](https://uzu.lurk.org/t/tidal-2-0/4247/42 "2023-06-03T09:40:50Z")

</div>

I'm developing on the cycseq branch, and occasionally merging into main. It's very unstable though!

In principle, I think as a DSL it would be OK for tidal to overload functions like `seq`, `sequence` etc, just as it currently overloads `<*` and `*>` from prelude. I'm just looking for the words that help me work best with patterns.

---

<div class="post-metadata">

**Author:** ![ndr\_brt](https://uzu.lurk.org/user_avatar/uzu.lurk.org/ndr_brt/32/396_2.png) [@ndr\_brt](https://uzu.lurk.org/u/ndr_brt)\
**Post date:** [14 June 2023 08:17 UTC](https://uzu.lurk.org/t/tidal-2-0/4247/43 "2023-06-14T08:17:48Z")

</div>

Maybe `beat` could be a good name too, I see it as a function that could be used also in a "cycle" approach, like using it within `every`, `while` or so.

---

<div class="post-metadata">

**Author:** ![yaxu](https://uzu.lurk.org/user_avatar/uzu.lurk.org/yaxu/32/2_2.png) [@yaxu](https://uzu.lurk.org/u/yaxu)\
**Post date:** [14 June 2023 11:12 UTC](https://uzu.lurk.org/t/tidal-2-0/4247/44 "2023-06-14T11:12:08Z")

</div>

Yes switching between different modes would be nice, we might be fighting against Haskell's type system there though!

The idea of a 'mode' marking the behaviour of part of a pattern extends beyond the sequence/cycle distinction. For example:

`fast "1 2" "bd sd"`

With the traditional tidal representation of pattern signals, this gives `bd [bd sd]`. Other potential interpretations include:

- `"bd sd@0.5"`
- `"bd sd*2"`
- `"[bd sd] [bd sd]*2"`
- `"bd bd*2 sd sd*2"`

there are many more!

I'm searching for a nice way to modify how patterns are aligned and applied following the rules of different 'modes', but plaintext feels a bit limited for expressing this..

[Previous page](https://uzu.lurk.org/t/tidal-2-0/4247.md?page=2)