论文标题
潮汐周期的替代时间表
Alternate Timelines for TidalCycles
论文作者
论文摘要
自2009年左右以来，通过对其核心代表性的几次重写，已经开发了潮汐（或简短的潮汐）实时编码环境。该发展没有实现固定的目标，而是以使用的方式来指导，这是由开放式音乐的动机。这种开发过程可以看作是长期的即兴创作，对在编写过程中获得的潮汐性质有所了解，可以追溯到指导下一步的发展步骤。 这使令人担忧的想法是，在此开发过程中将错过关键的见解，否则这将导致非常不同的软件。实际上，我已经领导或共同领导的初学者研讨会的参与者经常在没有良好答案的情况下提出问题，因为他们在软件中造成了不足或缺少功能。众所周知，初学者的思想能够看到专家已经视而不见。开展研讨会是寻找新开发想法的绝佳方法，但是本文探讨了另一种技术 - 重写。
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 make music. This development process can be seen as a long-form improvisation, with insights into the nature of Tidal gained through the process of writing it, feeding back to guide the next steps of development. This brings the worrying thought that key insights will have been missed along this development journey, that would otherwise have lead to very different software. Indeed participants at beginners' workshops that I have lead or co-lead have often asked questions without good answers, because they made deficiencies or missing features in the software clear. It is well known that a beginner's mind is able to see much that an expert has become blind to. Running workshops are an excellent way to find new development ideas, but the present paper explores a different technique - the rewrite.
