# \[paper\] Alternate timelines for TidalCycles **URL:** \ **Category:** TidalCycles\ **Tags:** resources\ **Created:** [16 December 2021 13:50 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721 "2021-12-16T13:50:30Z")\ **Posts on this page:** 8\ **Page:** 1
**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:** [16 December 2021 13:50 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721/1 "2021-12-16T13:50:30Z")
My paper for [this year's ICLC](https://iclc.toplap.org/2021/): > **[Alternate Timelines for TidalCycles](https://zenodo.org/records/5786103)** > > The TidalCycles (or Tidal for short) live coding environment has been developed since around 2009, via several rewrites of its core representation. Rather than having fixed goals, this development has been guided by use, motivated by the open aim to... ---
**Author:** ![jwaldmann](https://uzu.lurk.org/letter_avatar_proxy/v4/letter/j/977dab/32.png) [@jwaldmann](https://uzu.lurk.org/u/jwaldmann)\ **Post date:** [17 December 2021 01:01 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721/2 "2021-12-17T01:01:33Z")
A paper describing a "live coding" session of re-writing the code for a (musical) live coding system. Love the double meaning here! ---
**Author:** ![cleary](https://uzu.lurk.org/user_avatar/uzu.lurk.org/cleary/32/177_2.png) [@cleary](https://uzu.lurk.org/u/cleary)\ **Post date:** [17 December 2021 04:12 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721/3 "2021-12-17T04:12:09Z")
Looking forward to giving this a read! When @dktr0 implemented the JSoLangs for estuary, the concept of livecoding a livecoding language was made a simple reality for me, and my few idle attempts to further investigate/dissect that thought have proven to be a bit of a twisty loop that I very quickly escape.... hoping this might help put some of those thought threads into an order I can make sense of ---
**Author:** ![flechtwerk](https://uzu.lurk.org/letter_avatar_proxy/v4/letter/f/e36b37/32.png) [@flechtwerk](https://uzu.lurk.org/u/flechtwerk)\ **Post date:** [17 December 2021 16:18 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721/4 "2021-12-17T16:18:19Z")
Very interesting read, thank you for this! In the end I had the thought whether it wouldn't be possible to port Tidal to sclang as well and make it (and its "mini notation") a kind of alternative pattern library for SuperCollider...? Possibly being able to directly address the synths loaded onto the server, without the mediation of SuperDirt... But just thinking out loud here. ---
**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:** [17 December 2021 18:34 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721/5 "2021-12-17T18:34:07Z")
Yes @flechtwerk I had the same thought earlier! It would be interesting to try. By the way I uploaded a new version of the paper: > **[Alternate Timelines for TidalCycles](https://zenodo.org/record/5788732)** > > The TidalCycles (or Tidal for short) live coding environment has been developed since around 2009, via several rewrites of its core representation. Rather than having fixed goals, this development has been guided by use, motivated by the open aim to... No real changes, but a lot of typos fixed! ---
**Author:** ![Raph](https://uzu.lurk.org/user_avatar/uzu.lurk.org/raph/32/45_2.png) [@Raph](https://uzu.lurk.org/u/Raph)\ **Post date:** [17 December 2021 23:07 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721/6 "2021-12-17T23:07:49Z")
I usually open Tidal Club and SC forum in neighbouring tabs and thought that it would be a good idea to post a link to @flechtwerk post: > **[Porting TidalCycles to sclang?](https://scsynth.org/t/porting-tidalcycles-to-sclang/5030)** > > Just some food for thought: Over at the TidalCycles discourse, Alex McLean has published an interesting paper where he mentions the recent effort of porting Tidal to Python and make it in general less Haskel-centric, more language independent: ... ---
**Author:** ![zygomega](https://uzu.lurk.org/user_avatar/uzu.lurk.org/zygomega/32/1906_2.png) [@zygomega](https://uzu.lurk.org/u/zygomega)\ **Post date:** [19 December 2021 02:25 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721/7 "2021-12-19T02:25:34Z")
A great read. It’s sometimes hard to describe the benefits (and sheer joy) of refactoring, but this does a fantastic job of it. It also made me think of a dual to this. That I wish Haskell (and all languages) could be written in a more livecoding style - a fresh page, a simple loop and you start laying down little snippets of code, building up to the full program you have in mind. ---
**Author:** ![cleary](https://uzu.lurk.org/user_avatar/uzu.lurk.org/cleary/32/177_2.png) [@cleary](https://uzu.lurk.org/u/cleary)\ **Post date:** [19 December 2021 23:35 UTC](https://uzu.lurk.org/t/paper-alternate-timelines-for-tidalcycles/3721/8 "2021-12-19T23:35:18Z")
This is an epic thread! So much interest (and work already done in similar areas)!