first draft for sound preloading

Merge pull request #542 from tidalcycles/loading-animation
feat: add loader bar to animate loading state
2026-07-22 05:05:26 -04:00 · 2023-03-24 20:55:29 +01:00 · 2023-03-24 12:54:20 +01:00 · 2023-03-24 12:41:00 +01:00 · 2023-03-23 22:39:26 +01:00 · 2023-03-23 22:35:57 +01:00
83 changed files with 6298 additions and 3207 deletions
@@ -123,7 +123,14 @@ To publish all packages that have been changed since the last release, run:

 ```sh
 npm login
-npx lerna publish
+
+# this will increment all the versions in package.json files of non private packages to selected versions
+npx lerna version --no-private
+
+# publish all packages inside /packages using pnpm! don't use lerna to publish!!
+pnpm --filter "./packages/**" publish --dry-run
+
+# the last command was only a dry-run, make sure everything looks ok, if yes, run the same command without flag
 ```

 To manually publish a single package, increase the version in the `package.json`, then run `pnpm publish`.
@@ -67,7 +67,7 @@
    "jsdoc": "^3.6.10",
    "jsdoc-json": "^2.0.2",
    "jsdoc-to-markdown": "^7.1.1",
-    "lerna": "^4.0.0",
+    "lerna": "^6.5.1",
    "prettier": "^2.8.1",
    "rollup-plugin-visualizer": "^5.8.1"
  }
@@ -23,6 +23,15 @@ const generic_params = [
   *
   */
  [['s', 'n', 'gain'], 'sound'],
+  /**
+   * Define a custom webaudio node to use as a sound source.
+   *
+   * @name source
+   * @param {function} getSource
+   * @synonyms src
+   *
+   */
+  ['source', 'src'],
  /**
   * Selects the given index from the sample map.
   * Numbers too high will wrap around.
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/core",
-  "version": "0.6.8",
+  "version": "0.7.2",
  "description": "Port of Tidal Cycles to JavaScript",
  "main": "index.mjs",
  "type": "module",
@@ -1127,6 +1127,8 @@ function _composeOp(a, b, func) {
 export const polyrhythm = stack;
 export const pr = stack;

+export const pm = polymeter;
+
 // methods that create patterns, which are added to patternified Pattern methods
 // TODO: remove? this is only used in old transpiler (shapeshifter)
 Pattern.prototype.factories = {
@@ -1374,11 +1376,6 @@ export function polymeter(...args) {
  return polymeterSteps(0, ...args);
 }

-// alias
-export function pm(...args) {
-  polymeter(...args);
-}
-
 export const mask = curry((a, b) => reify(b).mask(a));
 export const struct = curry((a, b) => reify(b).struct(a));
 export const superimpose = curry((a, b) => reify(b).superimpose(...a));
@@ -4,7 +4,7 @@ Copyright (C) 2022 Strudel contributors - see <https://github.com/tidalcycles/st
 This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program.  If not, see <https://www.gnu.org/licenses/>.
 */

-import { Pattern, toMidi, getDrawContext, freqToMidi, isNote } from './index.mjs';
+import { Pattern, noteToMidi, getDrawContext, freqToMidi, isNote } from './index.mjs';

 const scale = (normalized, min, max) => normalized * (max - min) + min;
 const getValue = (e) => {
@@ -18,7 +18,7 @@ const getValue = (e) => {
  }
  note = note ?? n;
  if (typeof note === 'string') {
-    return toMidi(note);
+    return noteToMidi(note);
  }
  if (typeof note === 'number') {
    return note;
@@ -41,24 +41,13 @@ export function repl({
      throw new Error('no code to evaluate');
    }
    try {
-      beforeEval?.({ code });
-      scheduler.setCps(1); // reset cps in case the code does not contain a setCps call
-      // problem: when the code does contain a setCps after an awaited promise,
-      // the cps will be 1 until the promise resolves
-      // example:
-      /*
-      await new Promise(resolve => setTimeout(resolve,1000))
-      setCps(.5)
-      note("c a f e")
-      */
-      // to make sure the setCps inside the code is called immediately,
-      // it has to be placed first
+      await beforeEval?.({ code });
      let { pattern } = await _evaluate(code, transpiler);

      logger(`[eval] code updated`);
      pattern = editPattern?.(pattern) || pattern;
+      await afterEval?.({ code, pattern });
      scheduler.setPattern(pattern, autostart);
-      afterEval?.({ code, pattern });
      return pattern;
    } catch (err) {
      // console.warn(`[repl] eval error: ${err.message}`);
@@ -8,8 +8,8 @@ import { pure } from '../pattern.mjs';
 import {
  isNote,
  tokenizeNote,
-  toMidi,
-  fromMidi,
+  noteToMidi,
+  midiToFreq,
  freqToMidi,
  _mod,
  compose,
@@ -75,27 +75,27 @@ describe('isNote', () => {
    expect(tokenizeNote(123)).toStrictEqual([]);
  });
 });
-describe('toMidi', () => {
+describe('noteToMidi', () => {
  it('should turn notes into midi', () => {
-    expect(toMidi('A4')).toEqual(69);
-    expect(toMidi('C4')).toEqual(60);
-    expect(toMidi('Db4')).toEqual(61);
-    expect(toMidi('C3')).toEqual(48);
-    expect(toMidi('Cb3')).toEqual(47);
-    expect(toMidi('Cbb3')).toEqual(46);
-    expect(toMidi('C#3')).toEqual(49);
-    expect(toMidi('C#3')).toEqual(49);
-    expect(toMidi('C##3')).toEqual(50);
+    expect(noteToMidi('A4')).toEqual(69);
+    expect(noteToMidi('C4')).toEqual(60);
+    expect(noteToMidi('Db4')).toEqual(61);
+    expect(noteToMidi('C3')).toEqual(48);
+    expect(noteToMidi('Cb3')).toEqual(47);
+    expect(noteToMidi('Cbb3')).toEqual(46);
+    expect(noteToMidi('C#3')).toEqual(49);
+    expect(noteToMidi('C#3')).toEqual(49);
+    expect(noteToMidi('C##3')).toEqual(50);
  });
  it('should throw an error when given a non-note', () => {
-    expect(() => toMidi('Q')).toThrowError(`not a note: "Q"`);
-    expect(() => toMidi('Z')).toThrowError(`not a note: "Z"`);
+    expect(() => noteToMidi('Q')).toThrowError(`not a note: "Q"`);
+    expect(() => noteToMidi('Z')).toThrowError(`not a note: "Z"`);
  });
 });
-describe('fromMidi', () => {
+describe('midiToFreq', () => {
  it('should turn midi into frequency', () => {
-    expect(fromMidi(69)).toEqual(440);
-    expect(fromMidi(57)).toEqual(220);
+    expect(midiToFreq(69)).toEqual(440);
+    expect(midiToFreq(57)).toEqual(220);
  });
 });
 describe('freqToMidi', () => {
@@ -19,7 +19,7 @@ export const tokenizeNote = (note) => {
 };

 // turns the given note into its midi number representation
-export const toMidi = (note) => {
+export const noteToMidi = (note) => {
  const [pc, acc, oct = 3] = tokenizeNote(note);
  if (!pc) {
    throw new Error('not a note: "' + note + '"');
@@ -28,7 +28,7 @@ export const toMidi = (note) => {
  const offset = acc?.split('').reduce((o, char) => o + { '#': 1, b: -1, s: 1 }[char], 0) || 0;
  return (Number(oct) + 1) * 12 + chroma + offset;
 };
-export const fromMidi = (n) => {
+export const midiToFreq = (n) => {
  return Math.pow(2, (n - 69) / 12) * 440;
 };

@@ -45,7 +45,7 @@ export const valueToMidi = (value, fallbackValue) => {
    return freqToMidi(freq);
  }
  if (typeof note === 'string') {
-    return toMidi(note);
+    return noteToMidi(note);
  }
  if (typeof note === 'number') {
    return note;
@@ -62,9 +62,9 @@ export const valueToMidi = (value, fallbackValue) => {
 */
 export const getFreq = (noteOrMidi) => {
  if (typeof noteOrMidi === 'number') {
-    return fromMidi(noteOrMidi);
+    return midiToFreq(noteOrMidi);
  }
-  return fromMidi(toMidi(noteOrMidi));
+  return midiToFreq(noteToMidi(noteOrMidi));
 };

 /**
@@ -91,7 +91,7 @@ export const getPlayableNoteValue = (hap) => {
  }
  // if value is number => interpret as midi number as long as its not marked as frequency
  if (typeof note === 'number' && context.type !== 'frequency') {
-    note = fromMidi(hap.value);
+    note = midiToFreq(hap.value);
  } else if (typeof note === 'number' && context.type === 'frequency') {
    note = hap.value; // legacy workaround.. will be removed in the future
  } else if (typeof note !== 'string' || !isNote(note)) {
@@ -110,9 +110,9 @@ export const getFrequency = (hap) => {
    return getFreq(value.note || value.n || value.value);
  }
  if (typeof value === 'number' && context.type !== 'frequency') {
-    value = fromMidi(hap.value);
+    value = midiToFreq(hap.value);
  } else if (typeof value === 'string' && isNote(value)) {
-    value = fromMidi(toMidi(hap.value));
+    value = midiToFreq(noteToMidi(hap.value));
  } else if (typeof value !== 'number') {
    throw new Error('not a note or frequency: ' + value);
  }
@@ -170,7 +170,7 @@ export function parseNumeral(numOrString) {
    return asNumber;
  }
  if (isNote(numOrString)) {
-    return toMidi(numOrString);
+    return noteToMidi(numOrString);
  }
  throw new Error(`cannot parse as numeral: "${numOrString}"`);
 }
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/csound",
-  "version": "0.6.2",
+  "version": "0.7.1",
  "description": "csound bindings for strudel",
  "main": "index.mjs",
  "publishConfig": {
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/eval",
-  "version": "0.6.2",
+  "version": "0.7.1",
  "description": "Code evaluator for strudel",
  "main": "index.mjs",
  "publishConfig": {
@@ -7,7 +7,7 @@ This program is free software: you can redistribute it and/or modify it under th
 import * as _WebMidi from 'webmidi';
 import { Pattern, isPattern, logger } from '@strudel.cycles/core';
 import { getAudioContext } from '@strudel.cycles/webaudio';
-import { toMidi } from '@strudel.cycles/core';
+import { noteToMidi } from '@strudel.cycles/core';

 // if you use WebMidi from outside of this package, make sure to import that instance:
 export const { WebMidi } = _WebMidi;
@@ -114,7 +114,7 @@ Pattern.prototype.midi = function (output) {
    const duration = hap.duration.valueOf() * 1000 - 5;

    if (note) {
-      const midiNumber = toMidi(note);
+      const midiNumber = noteToMidi(note);
      device.playNote(midiNumber, midichan, {
        time,
        duration,
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/midi",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "Midi API for strudel",
  "main": "index.mjs",
  "publishConfig": {
@@ -279,7 +279,7 @@ function peg$parse(input, options) {
  var peg$f8 = function(p, s, r) { return x => x.options_['ops'].push({ type_: "bjorklund", arguments_ :{ pulse: p, step:s, rotation:r }}) };
  var peg$f9 = function(a) { return x => x.options_['ops'].push({ type_: "stretch", arguments_ :{ amount:a, type: 'slow' }}) };
  var peg$f10 = function(a) { return x => x.options_['ops'].push({ type_: "stretch", arguments_ :{ amount:a, type: 'fast' }}) };
-  var peg$f11 = function(a) { return x => x.options_['ops'].push({ type_: "degradeBy", arguments_ :{ amount:a } }) };
+  var peg$f11 = function(a) { return x => x.options_['ops'].push({ type_: "degradeBy", arguments_ :{ amount:a, seed: seed++ } }) };
  var peg$f12 = function(s) { return x => x.options_['ops'].push({ type_: "tail", arguments_ :{ element:s } }) };
  var peg$f13 = function(s, ops) { const result = new ElementStub(s, {ops: [], weight: 1, reps: 1});
    for (const op of ops) {
@@ -289,8 +289,8 @@ function peg$parse(input, options) {
  };
  var peg$f14 = function(s) { return new PatternStub(s, 'fastcat'); };
  var peg$f15 = function(tail) { return { alignment: 'stack', list: tail }; };
-  var peg$f16 = function(tail) { return { alignment: 'rand', list: tail }; };
-  var peg$f17 = function(head, tail) { if (tail && tail.list.length > 0) { return new PatternStub([head, ...tail.list], tail.alignment); } else { return head; } };
+  var peg$f16 = function(tail) { return { alignment: 'rand', list: tail, seed: seed++ }; };
+  var peg$f17 = function(head, tail) { if (tail && tail.list.length > 0) { return new PatternStub([head, ...tail.list], tail.alignment, tail.seed); } else { return head; } };
  var peg$f18 = function(head, tail) { return new PatternStub(tail ? [head, ...tail.list] : [head], 'polymeter'); };
  var peg$f19 = function(sc) { return sc; };
  var peg$f20 = function(s) { return { name: "struct", args: { mini:s }}};
@@ -2185,10 +2185,13 @@ function peg$parse(input, options) {
    this.location_ = location();
  }

-  var PatternStub = function(source, alignment)
+  var PatternStub = function(source, alignment, seed)
  {
    this.type_ = "pattern";
-    this.arguments_ = { alignment : alignment};
+    this.arguments_ = { alignment: alignment };
+    if (seed !== undefined) {
+      this.arguments_.seed = seed;
+    }
    this.source_ = source;
  }

@@ -2214,6 +2217,7 @@ function peg$parse(input, options) {
    this.options_ = options;
  }

+  var seed = 0;

  peg$result = peg$startRuleFunction();

@@ -19,10 +19,13 @@ This program is free software: you can redistribute it and/or modify it under th
    this.location_ = location();
  }

-  var PatternStub = function(source, alignment)
+  var PatternStub = function(source, alignment, seed)
  {
    this.type_ = "pattern";
-    this.arguments_ = { alignment : alignment};
+    this.arguments_ = { alignment: alignment };
+    if (seed !== undefined) {
+      this.arguments_.seed = seed;
+    }
    this.source_ = source;
  }

@@ -48,6 +51,7 @@ This program is free software: you can redistribute it and/or modify it under th
    this.options_ = options;
  }

+  var seed = 0;
 }

 start = statement
@@ -137,7 +141,7 @@ op_fast = "*"a:slice
  { return x => x.options_['ops'].push({ type_: "stretch", arguments_ :{ amount:a, type: 'fast' }}) }

 op_degrade = "?"a:number?
-  { return x => x.options_['ops'].push({ type_: "degradeBy", arguments_ :{ amount:a } }) }
+  { return x => x.options_['ops'].push({ type_: "degradeBy", arguments_ :{ amount:a, seed: seed++ } }) }

 op_tail = ":" s:slice
  { return x => x.options_['ops'].push({ type_: "tail", arguments_ :{ element:s } }) }
@@ -162,12 +166,12 @@ stack_tail = tail:(comma @sequence)+
 // a choose is a series of pipe-separated sequence, one of which is
 // chosen at random, each cycle
 choose_tail = tail:(pipe @sequence)+
-  { return { alignment: 'rand', list: tail }; }
+  { return { alignment: 'rand', list: tail, seed: seed++ }; }

 // if the stack contains only one element, we don't create a stack but return the
 // underlying element
 stack_or_choose = head:sequence tail:(stack_tail / choose_tail)?
-  { if (tail && tail.list.length > 0) { return new PatternStub([head, ...tail.list], tail.alignment); } else { return head; } }
+  { if (tail && tail.list.length > 0) { return new PatternStub([head, ...tail.list], tail.alignment, tail.seed); } else { return head; } }

 polymeter_stack = head:sequence tail:stack_tail?
  { return new PatternStub(tail ? [head, ...tail.list] : [head], 'polymeter'); }
@@ -7,12 +7,7 @@ This program is free software: you can redistribute it and/or modify it under th
 import * as krill from './krill-parser.js';
 import * as strudel from '@strudel.cycles/core';

-/* var _seedState = 0;
-const randOffset = 0.0002;
-
-function _nextSeed() {
-  return _seedState++;
-} */
+const randOffset = 0.0003;

 const applyOptions = (parent, code) => (pat, i) => {
  const ast = parent.source_[i];
@@ -44,27 +39,9 @@ const applyOptions = (parent, code) => (pat, i) => {
          break;
        }
        case 'degradeBy': {
-          // TODO: find out what is right here
-          // example:
-          /*
-           stack(
-             s("hh*8").degrade(),
-             s("[ht*8]?")
-           )
-        */
-          // above example will only be in sync when _degradeBy is used...
-          // it also seems that the nextSeed will create undeterministic behaviour
-          // as it uses a global _seedState. This is probably the reason for
-          // https://github.com/tidalcycles/strudel/issues/245
-
-          // this is how it was:
-          /* 
-        return strudel.reify(pat)._degradeByWith(
-          strudel.rand.early(randOffset * _nextSeed()).segment(1),
-          op.arguments_.amount ?? 0.5,
-        ); 
-        */
-          pat = strudel.reify(pat).degradeBy(op.arguments_.amount === null ? 0.5 : op.arguments_.amount);
+          pat = strudel
+            .reify(pat)
+            ._degradeByWith(strudel.rand.early(randOffset * op.arguments_.seed), op.arguments_.amount ?? 0.5);
          break;
        }
        case 'tail': {
@@ -114,9 +91,7 @@ export function patternifyAST(ast, code) {
        return strudel.stack(...aligned);
      }
      if (alignment === 'rand') {
-        // https://github.com/tidalcycles/strudel/issues/245#issuecomment-1345406422
-        // return strudel.chooseInWith(strudel.rand.early(randOffset * _nextSeed()).segment(1), children);
-        return strudel.chooseCycles(...children);
+        return strudel.chooseInWith(strudel.rand.early(randOffset * ast.arguments_.seed).segment(1), children);
      }
      const weightedChildren = ast.source_.some((child) => !!child.options_?.weight);
      if (!weightedChildren && alignment === 'slowcat') {
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/mini",
-  "version": "0.6.0",
+  "version": "0.7.2",
  "description": "Mini notation for strudel",
  "main": "index.mjs",
  "type": "module",
@@ -140,10 +140,22 @@ describe('mini', () => {
    expect(haps.length < 230).toBe(true);
    // 'Had too many cycles remaining after degradeBy 0.8');
  });
-  it('supports lists', () => {
-    expect(minV('a:b c:d:[e:f] g')).toEqual([['a', 'b'], ['c', 'd', ['e', 'f']], 'g']);
+  it('supports multiple independent uses of the random choice operator ("|")', () => {
+    const numCycles = 1000;
+    const values = mini('[a|b] [a|b]')
+      .queryArc(0, numCycles)
+      .map((e) => e.value);
+    const observed = { aa: 0, ab: 0, ba: 0, bb: 0 };
+    for (let i = 0; i < values.length; i += 2) {
+      const chunk = values.slice(i, i + 2);
+      observed[chunk.join('')]++;
+    }
+    for (const count of Object.values(observed)) {
+      // Should fall within 99% confidence interval for binomial with p=0.25.
+      expect(215 <= count && count <= 286).toBe(true);
+    }
  });
-  /*it('supports the random choice operator ("|") with nesting', () => {
+  it('supports the random choice operator ("|") with nesting', () => {
    const numCycles = 900;
    const haps = mini('a | [b | c] | [d | e | f]').queryArc(0, numCycles);
    // Should have about 1/3 a, 1/6 each of b | c, and 1/9 each of d | e | f.
@@ -168,6 +180,8 @@ describe('mini', () => {
    // 15.086 is the chisq for 5 degrees of freedom at 99%, so for 99% of uniformly-distributed
    //  PRNG, this test should succeed
    expect(chisq <= 15.086).toBe(true);
-    // assert(chisq <= 15.086, chisq + ' was expected to be less than 15.086 under chi-squared test');
-  });*/
+  });
+  it('supports lists', () => {
+    expect(minV('a:b c:d:[e:f] g')).toEqual([['a', 'b'], ['c', 'd', ['e', 'f']], 'g']);
+  });
 });
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/osc",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "OSC messaging for strudel",
  "main": "osc.mjs",
  "publishConfig": {
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/react",
-  "version": "0.6.4",
+  "version": "0.7.1",
  "description": "React components for strudel",
  "main": "src/index.js",
  "publishConfig": {
@@ -82,7 +82,7 @@ export function MiniRepl({
              e.preventDefault();
              flash(view);
              await activateCode();
-            } else if (e.code === 'Period') {
+            } else if (e.key === '.') {
              stop();
              e.preventDefault();
            }
@@ -93,26 +93,6 @@ export function MiniRepl({
    ),
  );

-  // set active pattern on ctrl+enter
-  useLayoutEffect(() => {
-    if (enableKeyboard) {
-      const handleKeyPress = async (e) => {
-        if (e.ctrlKey || e.altKey) {
-          if (e.code === 'Enter') {
-            e.preventDefault();
-            flash(view);
-            await activateCode();
-          } else if (e.code === 'Period') {
-            stop();
-            e.preventDefault();
-          }
-        }
-      };
-      window.addEventListener('keydown', handleKeyPress, true);
-      return () => window.removeEventListener('keydown', handleKeyPress, true);
-    }
-  }, [enableKeyboard, pattern, code, evaluate, stop, view]);
-
  const [log, setLog] = useState([]);
  useLogger(
    useCallback((e) => {
@@ -46,17 +46,17 @@ function useStrudel({
        drawContext,
        transpiler,
        editPattern,
-        beforeEval: ({ code }) => {
+        beforeEval: async ({ code }) => {
          setCode(code);
-          beforeEval?.();
+          await beforeEval?.();
        },
-        afterEval: (res) => {
+        afterEval: async (res) => {
          const { pattern: _pattern, code } = res;
          setActiveCode(code);
          setPattern(_pattern);
          setEvalError();
          setSchedulerError();
-          afterEval?.(res);
+          await afterEval?.(res);
        },
        onToggle: (v) => {
          setStarted(v);
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/serial",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "Webserial API for strudel",
  "main": "serial.mjs",
  "publishConfig": {
@@ -1,4 +1,6 @@
-import { toMidi } from '@strudel.cycles/core';
+import { noteToMidi, freqToMidi } from '@strudel.cycles/core';
+import { getAudioContext, registerSound, getEnvelope } from '@strudel.cycles/webaudio';
+import gm from './gm.mjs';

 let loadCache = {};
 async function loadFont(name) {
@@ -8,7 +10,6 @@ async function loadFont(name) {
  const load = async () => {
    // TODO: make soundfont source configurable
    const url = `https://felixroos.github.io/webaudiofontdata/sound/${name}.js`;
-    console.log('load font', name, url);
    const preset = await fetch(url).then((res) => res.text());
    let [_, data] = preset.split('={');
    return eval('{' + data);
@@ -17,15 +18,24 @@ async function loadFont(name) {
  return loadCache[name];
 }

-export async function getFontBufferSource(name, pitch, ac) {
-  if (typeof pitch === 'string') {
-    pitch = toMidi(pitch);
+export async function getFontBufferSource(name, value, ac) {
+  let { note = 'c3', freq } = value;
+  let midi;
+  if (freq) {
+    midi = freqToMidi(freq);
+  } else if (typeof note === 'string') {
+    midi = noteToMidi(note);
+  } else if (typeof note === 'number') {
+    midi = note;
+  } else {
+    throw new Error(`unexpected "note" type "${typeof note}"`);
  }
-  const { buffer, zone } = await getFontPitch(name, pitch, ac);
+
+  const { buffer, zone } = await getFontPitch(name, midi, ac);
  const src = ac.createBufferSource();
  src.buffer = buffer;
  const baseDetune = zone.originalPitch - 100.0 * zone.coarseTune - zone.fineTune;
-  const playbackRate = 1.0 * Math.pow(2, (100.0 * pitch - baseDetune) / 1200.0);
+  const playbackRate = 1.0 * Math.pow(2, (100.0 * midi - baseDetune) / 1200.0);
  // src detune?
  src.playbackRate.value = playbackRate;
  const loop = zone.loopStart > 1 && zone.loopStart < zone.loopEnd;
@@ -114,3 +124,34 @@ async function getBuffer(zone, audioContext) {
    }
  }
 }
+
+export function registerSoundfonts() {
+  Object.entries(gm).forEach(([name, fonts]) => {
+    registerSound(
+      name,
+      async (time, value, onended) => {
+        const { n = 0 } = value;
+        const { attack = 0.001, decay = 0.001, sustain = 1, release = 0.001 } = value;
+        const font = fonts[n % fonts.length];
+        const ctx = getAudioContext();
+        const bufferSource = await getFontBufferSource(font, value, ctx);
+        bufferSource.start(time);
+        const { node: envelope, stop: releaseEnvelope } = getEnvelope(attack, decay, sustain, release, 0.3, time);
+        bufferSource.connect(envelope);
+        const stop = (releaseTime) => {
+          bufferSource.stop(releaseTime + release);
+          releaseEnvelope(releaseTime);
+        };
+        bufferSource.onended = () => {
+          bufferSource.disconnect();
+          envelope.disconnect();
+          onended();
+        };
+        return { node: envelope, stop };
+      },
+      { type: 'soundfont', prebake: true, fonts },
+    );
+  });
+}
+
+registerSoundfonts();
@@ -1,6 +1,6 @@
-import { getFontBufferSource } from './fontloader.mjs';
+import { getFontBufferSource, registerSoundfonts } from './fontloader.mjs';
 import * as soundfontList from './list.mjs';
 import { startPresetNote } from 'sfumato';
 import { loadSoundfont } from './sfumato.mjs';

-export { loadSoundfont, startPresetNote, getFontBufferSource, soundfontList };
+export { loadSoundfont, startPresetNote, getFontBufferSource, soundfontList, registerSoundfonts };
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/soundfonts",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "Soundsfont support for strudel",
  "main": "index.mjs",
  "publishConfig": {
@@ -1,5 +1,5 @@
-import { Pattern, getPlayableNoteValue, toMidi } from '@strudel.cycles/core';
-import { getAudioContext } from '@strudel.cycles/webaudio';
+import { Pattern, getPlayableNoteValue, noteToMidi } from '@strudel.cycles/core';
+import { getAudioContext, registerSound } from '@strudel.cycles/webaudio';
 import { loadSoundfont as _loadSoundfont, startPresetNote } from 'sfumato';

 Pattern.prototype.soundfont = function (sf, n = 0) {
@@ -8,7 +8,7 @@ Pattern.prototype.soundfont = function (sf, n = 0) {
    const note = getPlayableNoteValue(h);
    const preset = sf.presets[n % sf.presets.length];
    const deadline = ctx.currentTime + t - ct;
-    const args = [ctx, preset, toMidi(note), deadline];
+    const args = [ctx, preset, noteToMidi(note), deadline];
    const stop = startPresetNote(...args);
    stop(deadline + h.duration);
  });
@@ -21,5 +21,29 @@ export function loadSoundfont(url) {
  }
  const sf = _loadSoundfont(url);
  soundfontCache.set(url, sf);
+  /*sf.then((font) => {
+    font.presets.forEach((preset) => {
+      console.log('preset', preset.header.name);
+      registerSound(
+        preset.header.name.replaceAll(' ', '_'),
+        (time, value, onended) => {
+          const ctx = getAudioContext();
+          let { note } = value; // freq ?
+
+          const p = font.presets.find((p) => p.header.name === preset.header.name);
+
+          if (!p) {
+            throw new Error('preset not found');
+          }
+          const deadline = time; // - ctx.currentTime;
+          const args = [ctx, p, noteToMidi(note), deadline];
+          const stop = startPresetNote(...args);
+          return { node: undefined, stop };
+        },
+        { type: 'soundfont' },
+      );
+    });
+    //console.log('f', f);
+  });*/
  return sf;
 }
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/tonal",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "Tonal functions for strudel",
  "main": "index.mjs",
  "publishConfig": {
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/tone",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "Tone.js API for strudel",
  "main": "index.mjs",
  "type": "module",
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/transpiler",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "Transpiler for strudel user code. Converts syntactically correct but semantically meaningless JS into evaluatable strudel code.",
  "main": "index.mjs",
  "publishConfig": {
@@ -0,0 +1,70 @@
+import { getAudioContext } from './webaudio.mjs';
+
+export function gainNode(value) {
+  const node = getAudioContext().createGain();
+  node.gain.value = value;
+  return node;
+}
+
+export const getOscillator = ({ s, freq, t }) => {
+  // make oscillator
+  const o = getAudioContext().createOscillator();
+  o.type = s || 'triangle';
+  o.frequency.value = Number(freq);
+  o.start(t);
+  //o.stop(t + duration + release);
+  const stop = (time) => o.stop(time);
+  return { node: o, stop };
+};
+
+// alternative to getADSR returning the gain node and a stop handle to trigger the release anytime in the future
+export const getEnvelope = (attack, decay, sustain, release, velocity, begin) => {
+  const gainNode = getAudioContext().createGain();
+  gainNode.gain.setValueAtTime(0, begin);
+  gainNode.gain.linearRampToValueAtTime(velocity, begin + attack); // attack
+  gainNode.gain.linearRampToValueAtTime(sustain * velocity, begin + attack + decay); // sustain start
+  // sustain end
+  return {
+    node: gainNode,
+    stop: (t) => {
+      //if (typeof gainNode.gain.cancelAndHoldAtTime === 'function') {
+      // gainNode.gain.cancelAndHoldAtTime(t); // this seems to release instantly....
+      // see https://discord.com/channels/779427371270275082/937365093082079272/1086053607360712735
+      //} else {
+      // firefox: this will glitch when the sustain has not been reached yet at the time of release
+      gainNode.gain.setValueAtTime(sustain * velocity, t);
+      //}
+      gainNode.gain.linearRampToValueAtTime(0, t + release);
+    },
+  };
+};
+
+export const getADSR = (attack, decay, sustain, release, velocity, begin, end) => {
+  const gainNode = getAudioContext().createGain();
+  gainNode.gain.setValueAtTime(0, begin);
+  gainNode.gain.linearRampToValueAtTime(velocity, begin + attack); // attack
+  gainNode.gain.linearRampToValueAtTime(sustain * velocity, begin + attack + decay); // sustain start
+  gainNode.gain.setValueAtTime(sustain * velocity, end); // sustain end
+  gainNode.gain.linearRampToValueAtTime(0, end + release); // release
+  // for some reason, using exponential ramping creates little cracklings
+  /* let t = begin;
+  gainNode.gain.setValueAtTime(0, t);
+  gainNode.gain.exponentialRampToValueAtTime(velocity, (t += attack));
+  const sustainGain = Math.max(sustain * velocity, 0.001);
+  gainNode.gain.exponentialRampToValueAtTime(sustainGain, (t += decay));
+  if (end - begin < attack + decay) {
+    gainNode.gain.cancelAndHoldAtTime(end);
+  } else {
+    gainNode.gain.setValueAtTime(sustainGain, end);
+  }
+  gainNode.gain.exponentialRampToValueAtTime(0.001, end + release); // release */
+  return gainNode;
+};
+
+export const getFilter = (type, frequency, Q) => {
+  const filter = getAudioContext().createBiquadFilter();
+  filter.type = type;
+  filter.frequency.value = frequency;
+  filter.Q.value = Q;
+  return filter;
+};
@@ -6,3 +6,5 @@ This program is free software: you can redistribute it and/or modify it under th

 export * from './webaudio.mjs';
 export * from './sampler.mjs';
+export * from './helpers.mjs';
+export * from './synth.mjs';
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/webaudio",
-  "version": "0.6.1",
+  "version": "0.7.1",
  "description": "Web Audio helpers for Strudel",
  "main": "index.mjs",
  "type": "module",
@@ -34,7 +34,8 @@
  },
  "homepage": "https://github.com/tidalcycles/strudel#readme",
  "dependencies": {
-    "@strudel.cycles/core": "workspace:*"
+    "@strudel.cycles/core": "workspace:*",
+    "nanostores": "^0.7.4"
  },
  "devDependencies": {
    "vite": "^3.2.2"
@@ -1,5 +1,6 @@
-import { logger, toMidi, valueToMidi } from '@strudel.cycles/core';
-import { getAudioContext } from './index.mjs';
+import { logger, noteToMidi, valueToMidi } from '@strudel.cycles/core';
+import { getAudioContext, registerSound } from './index.mjs';
+import { getEnvelope } from './helpers.mjs';

 const bufferCache = {}; // string: Promise<ArrayBuffer>
 const loadCache = {}; // string: Promise<ArrayBuffer>
@@ -20,7 +21,7 @@ function humanFileSize(bytes, si) {
  return bytes.toFixed(1) + ' ' + units[u];
 }

-export const getSampleBufferSource = async (s, n, note, speed, freq) => {
+export const getSampleBufferSource = async (s, n, note, speed, freq, bank) => {
  let transpose = 0;
  if (freq !== undefined && note !== undefined) {
    logger('[sampler] hap has note and freq. ignoring note', 'warning');
@@ -29,28 +30,11 @@ export const getSampleBufferSource = async (s, n, note, speed, freq) => {
  transpose = midi - 36; // C3 is middle C

  const ac = getAudioContext();
-  // is sample from loaded samples(..)
-  const samples = getLoadedSamples();
-  if (!samples) {
-    throw new Error('no samples loaded');
-  }
-  const bank = samples?.[s];
-  if (!bank) {
-    throw new Error(
-      `sample not found: "${s}"`,
-      // , try one of ${Object.keys(samples)
-      // .map((s) => `"${s}"`)
-      // .join(', ')}.
-    );
-  }
-  if (typeof bank !== 'object') {
-    throw new Error('wrong format for sample bank:', s);
-  }
  let sampleUrl;
  if (Array.isArray(bank)) {
    sampleUrl = bank[n % bank.length];
  } else {
-    const midiDiff = (noteA) => toMidi(noteA) - midi;
+    const midiDiff = (noteA) => noteToMidi(noteA) - midi;
    // object format will expect keys as notes
    const closest = Object.keys(bank)
      .filter((k) => !k.startsWith('_'))
@@ -107,8 +91,6 @@ export const getLoadedBuffer = (url) => {
  return bufferCache[url];
 };

-let sampleCache = { current: undefined };
-
 /**
 * Loads a collection of samples to use with `s`
 * @example
@@ -123,7 +105,7 @@ let sampleCache = { current: undefined };
 *
 */

-export const samples = async (sampleMap, baseUrl = sampleMap._base || '') => {
+export const samples = async (sampleMap, baseUrl = sampleMap._base || '', options = {}) => {
  if (typeof sampleMap === 'string') {
    if (sampleMap.startsWith('github:')) {
      let [_, path] = sampleMap.split('github:');
@@ -141,43 +123,134 @@ export const samples = async (sampleMap, baseUrl = sampleMap._base || '') => {
    }
    return fetch(sampleMap)
      .then((res) => res.json())
-      .then((json) => samples(json, baseUrl || json._base || base))
+      .then((json) => samples(json, baseUrl || json._base || base, options))
      .catch((error) => {
        console.error(error);
        throw new Error(`error loading "${sampleMap}"`);
      });
  }
-  sampleCache.current = {
-    ...sampleCache.current,
-    ...Object.fromEntries(
-      Object.entries(sampleMap).map(([key, value]) => {
-        if (typeof value === 'string') {
-          value = [value];
-        }
-        if (typeof value !== 'object') {
-          throw new Error('wrong sample map format for ' + key);
-        }
-        baseUrl = value._base || baseUrl;
-        const replaceUrl = (v) => (baseUrl + v).replace('github:', 'https://raw.githubusercontent.com/');
-        if (Array.isArray(value)) {
-          return [key, value.map(replaceUrl)];
-        }
-        // must be object
-        return [
-          key,
-          Object.fromEntries(
-            Object.entries(value).map(([note, samples]) => {
-              return [note, (typeof samples === 'string' ? [samples] : samples).map(replaceUrl)];
-            }),
-          ),
-        ];
-      }),
-    ),
+  const { prebake, tag } = options;
+  Object.entries(sampleMap).forEach(([key, value]) => {
+    if (typeof value === 'string') {
+      value = [value];
+    }
+    if (typeof value !== 'object') {
+      throw new Error('wrong sample map format for ' + key);
+    }
+    baseUrl = value._base || baseUrl;
+    const replaceUrl = (v) => (baseUrl + v).replace('github:', 'https://raw.githubusercontent.com/');
+    if (Array.isArray(value)) {
+      //return [key, value.map(replaceUrl)];
+      value = value.map(replaceUrl);
+    } else {
+      // must be object
+      value = Object.fromEntries(
+        Object.entries(value).map(([note, samples]) => {
+          return [note, (typeof samples === 'string' ? [samples] : samples).map(replaceUrl)];
+        }),
+      );
+    }
+    registerSound(key, (t, hapValue, onended) => onTriggerSample(t, hapValue, onended, value), {
+      type: 'sample',
+      samples: value,
+      baseUrl,
+      prebake,
+      tag,
+    });
+  });
+};
+
+const cutGroups = [];
+
+export async function onTriggerSample(t, value, onended, bank) {
+  const {
+    s,
+    freq,
+    unit,
+    nudge = 0, // TODO: is this in seconds?
+    cut,
+    loop,
+    clip = 0, // if 1, samples will be cut off when the hap ends
+    n = 0,
+    note,
+    speed = 1, // sample playback speed
+    begin = 0,
+    end = 1,
+  } = value;
+  // load sample
+  if (speed === 0) {
+    // no playback
+    return;
+  }
+  const ac = getAudioContext();
+  // destructure adsr here, because the default should be different for synths and samples
+  const { attack = 0.001, decay = 0.001, sustain = 1, release = 0.001 } = value;
+  //const soundfont = getSoundfontKey(s);
+  const time = t + nudge;
+
+  const bufferSource = await getSampleBufferSource(s, n, note, speed, freq, bank);
+
+  // asny stuff above took too long?
+  if (ac.currentTime > t) {
+    logger(`[sampler] still loading sound "${s}:${n}"`, 'highlight');
+    // console.warn('sample still loading:', s, n);
+    return;
+  }
+  if (!bufferSource) {
+    logger(`[sampler] could not load "${s}:${n}"`, 'error');
+    return;
+  }
+  bufferSource.playbackRate.value = Math.abs(speed) * bufferSource.playbackRate.value;
+  if (unit === 'c') {
+    // are there other units?
+    bufferSource.playbackRate.value = bufferSource.playbackRate.value * bufferSource.buffer.duration * 1; //cps;
+  }
+  // "The computation of the offset into the sound is performed using the sound buffer's natural sample rate,
+  // rather than the current playback rate, so even if the sound is playing at twice its normal speed,
+  // the midway point through a 10-second audio buffer is still 5."
+  const offset = begin * bufferSource.buffer.duration;
+  bufferSource.start(time, offset);
+  const bufferDuration = bufferSource.buffer.duration / bufferSource.playbackRate.value;
+  /*if (loop) {
+    // TODO: idea for loopBegin / loopEnd
+    // if one of [loopBegin,loopEnd] is <= 1, interpret it as normlized
+    // if [loopBegin,loopEnd] is bigger >= 1, interpret it as sample number
+    // this will simplify perfectly looping things, while still keeping the normalized option
+    // the only drawback is that looping between samples 0 and 1 is not possible (which is not real use case)
+    bufferSource.loop = true;
+    bufferSource.loopStart = offset;
+    bufferSource.loopEnd = offset + duration;
+    duration = loop * duration;
+  }*/
+  const { node: envelope, stop: releaseEnvelope } = getEnvelope(attack, decay, sustain, release, 1, t);
+  bufferSource.connect(envelope);
+  const out = ac.createGain(); // we need a separate gain for the cutgroups because firefox...
+  envelope.connect(out);
+  bufferSource.onended = function () {
+    bufferSource.disconnect();
+    envelope.disconnect();
+    out.disconnect();
+    onended();
  };
-};
+  const stop = (endTime, playWholeBuffer = !clip) => {
+    let releaseTime = endTime;
+    if (playWholeBuffer) {
+      releaseTime = t + (end - begin) * bufferDuration;
+    }
+    bufferSource.stop(releaseTime + release);
+    releaseEnvelope(releaseTime);
+  };
+  const handle = { node: out, bufferSource, stop };

-export const resetLoadedSamples = () => {
-  sampleCache.current = undefined;
-};
+  // cut groups
+  if (cut !== undefined) {
+    const prev = cutGroups[cut];
+    if (prev) {
+      prev.node.gain.setValueAtTime(1, time);
+      prev.node.gain.linearRampToValueAtTime(0, time + 0.01);
+    }
+    cutGroups[cut] = handle;
+  }

-export const getLoadedSamples = () => sampleCache.current;
+  return handle;
+}
@@ -0,0 +1,44 @@
+import { midiToFreq, noteToMidi } from '@strudel.cycles/core';
+import { registerSound } from './webaudio.mjs';
+import { getOscillator, gainNode, getEnvelope } from './helpers.mjs';
+
+export function registerSynthSounds() {
+  ['sine', 'square', 'triangle', 'sawtooth'].forEach((wave) => {
+    registerSound(
+      wave,
+      (t, value, onended) => {
+        // destructure adsr here, because the default should be different for synths and samples
+        const { attack = 0.001, decay = 0.05, sustain = 0.6, release = 0.01 } = value;
+        let { n, note, freq } = value;
+        // with synths, n and note are the same thing
+        n = note || n || 36;
+        if (typeof n === 'string') {
+          n = noteToMidi(n); // e.g. c3 => 48
+        }
+        // get frequency
+        if (!freq && typeof n === 'number') {
+          freq = midiToFreq(n); // + 48);
+        }
+        // maybe pull out the above frequency resolution?? (there is also getFrequency but it has no default)
+        // make oscillator
+        const { node: o, stop } = getOscillator({ t, s: wave, freq });
+        const g = gainNode(0.3);
+        // envelope
+        const { node: envelope, stop: releaseEnvelope } = getEnvelope(attack, decay, sustain, release, 1, t);
+        o.onended = () => {
+          o.disconnect();
+          g.disconnect();
+          onended();
+        };
+        return {
+          node: o.connect(g).connect(envelope),
+          stop: (releaseTime) => {
+            releaseEnvelope(releaseTime);
+            stop(releaseTime + release);
+          },
+        };
+      },
+      { type: 'synth', prebake: true },
+    );
+  });
+}
@@ -5,15 +5,22 @@ This program is free software: you can redistribute it and/or modify it under th
 */

 import * as strudel from '@strudel.cycles/core';
-import { fromMidi, logger, toMidi } from '@strudel.cycles/core';
 import './feedbackdelay.mjs';
 import './reverb.mjs';
-import { getSampleBufferSource } from './sampler.mjs';
-const { Pattern } = strudel;
+const { Pattern, logger } = strudel;
 import './vowel.mjs';
 import workletsUrl from './worklets.mjs?url';
+import { getFilter, gainNode } from './helpers.mjs';
+import { map } from 'nanostores';

-// export const getAudioContext = () => Tone.getContext().rawContext;
+export const soundMap = map();
+export function registerSound(key, onTrigger, data = {}) {
+  soundMap.setKey(key, { onTrigger, data });
+}
+export function getSound(s) {
+  return soundMap.get()[s];
+}
+export const resetLoadedSounds = () => soundMap.set({});

 let audioContext;
 export const getAudioContext = () => {
@@ -38,65 +45,6 @@ export const panic = () => {
  destination = null;
 };

-const getFilter = (type, frequency, Q) => {
-  const filter = getAudioContext().createBiquadFilter();
-  filter.type = type;
-  filter.frequency.value = frequency;
-  filter.Q.value = Q;
-  return filter;
-};
-
-const getADSR = (attack, decay, sustain, release, velocity, begin, end) => {
-  const gainNode = getAudioContext().createGain();
-  gainNode.gain.setValueAtTime(0, begin);
-  gainNode.gain.linearRampToValueAtTime(velocity, begin + attack); // attack
-  gainNode.gain.linearRampToValueAtTime(sustain * velocity, begin + attack + decay); // sustain start
-  gainNode.gain.setValueAtTime(sustain * velocity, end); // sustain end
-  gainNode.gain.linearRampToValueAtTime(0, end + release); // release
-  // for some reason, using exponential ramping creates little cracklings
-  /* let t = begin;
-  gainNode.gain.setValueAtTime(0, t);
-  gainNode.gain.exponentialRampToValueAtTime(velocity, (t += attack));
-  const sustainGain = Math.max(sustain * velocity, 0.001);
-  gainNode.gain.exponentialRampToValueAtTime(sustainGain, (t += decay));
-  if (end - begin < attack + decay) {
-    gainNode.gain.cancelAndHoldAtTime(end);
-  } else {
-    gainNode.gain.setValueAtTime(sustainGain, end);
-  }
-  gainNode.gain.exponentialRampToValueAtTime(0.001, end + release); // release */
-  return gainNode;
-};
-
-const getOscillator = ({ s, freq, t, duration, release }) => {
-  // make oscillator
-  const o = getAudioContext().createOscillator();
-  o.type = s || 'triangle';
-  o.frequency.value = Number(freq);
-  o.start(t);
-  o.stop(t + duration + release);
-  return o;
-};
-
-const getSoundfontKey = (s) => {
-  if (!globalThis.soundfontList) {
-    // soundfont package not loaded
-    return false;
-  }
-  if (globalThis.soundfontList?.instruments?.includes(s)) {
-    return s;
-  }
-  // check if s is one of the soundfonts, which are loaded into globalThis, to avoid coupling both packages
-  const nameIndex = globalThis.soundfontList?.instrumentNames?.indexOf(s);
-  // convert number nameIndex (0-128) to 3 digit string (001-128)
-  const name = nameIndex < 10 ? `00${nameIndex}` : nameIndex < 100 ? `0${nameIndex}` : nameIndex;
-  if (nameIndex !== -1) {
-    // TODO: indices of instrumentNames do not seem to match instruments
-    return globalThis.soundfontList.instruments.find((instrument) => instrument.startsWith(name));
-  }
-  return;
-};
-
 let workletsLoading;
 function loadWorklets() {
  if (workletsLoading) {
@@ -136,13 +84,6 @@ export async function initAudioOnFirstClick() {
  });
 }

-function gainNode(value) {
-  const node = getAudioContext().createGain();
-  node.gain.value = value;
-  return node;
-}
-const cutGroups = [];
-
 let delays = {};
 function getDelay(orbit, delaytime, delayfeedback, t) {
  if (!delays[orbit]) {
@@ -186,15 +127,11 @@ export const webaudioOutput = async (hap, deadline, hapDuration, cps) => {

  // calculate absolute time
  let t = ac.currentTime + deadline;
-  // destructure value
+  // destructure
  let {
-    freq,
-    s,
+    s = 'triangle',
    bank,
-    sf,
-    clip = 0, // if 1, samples will be cut off when the hap ends
-    n = 0,
-    note,
+    source,
    gain = 0.8,
    // low pass
    cutoff,
@@ -210,110 +147,48 @@ export const webaudioOutput = async (hap, deadline, hapDuration, cps) => {
    crush,
    shape,
    pan,
-    speed = 1, // sample playback speed
-    begin = 0,
-    end = 1,
    vowel,
    delay = 0,
    delayfeedback = 0.5,
    delaytime = 0.25,
-    unit,
-    nudge = 0, // TODO: is this in seconds?
-    cut,
-    loop,
    orbit = 1,
    room,
    size = 2,
  } = hap.value;
  const { velocity = 1 } = hap.context;
  gain *= velocity; // legacy fix for velocity
-  // the chain will hold all audio nodes that connect to each other
-  const chain = [];
+  let toDisconnect = []; // audio nodes that will be disconnected when the source has ended
+  const onended = () => {
+    toDisconnect.forEach((n) => n?.disconnect());
+  };
  if (bank && s) {
    s = `${bank}_${s}`;
  }
-  if (!s || ['sine', 'square', 'triangle', 'sawtooth'].includes(s)) {
-    // destructure adsr here, because the default should be different for synths and samples
-    const { attack = 0.001, decay = 0.05, sustain = 0.6, release = 0.01 } = hap.value;
-    // with synths, n and note are the same thing
-    n = note || n || 36;
-    if (typeof n === 'string') {
-      n = toMidi(n); // e.g. c3 => 48
+  // get source AudioNode
+  let sourceNode;
+  if (source) {
+    sourceNode = source(t, hap.value, hapDuration);
+  } else if (getSound(s)) {
+    const { onTrigger } = getSound(s);
+    const soundHandle = await onTrigger(t, { ...hap.value, s }, onended);
+    if (soundHandle) {
+      sourceNode = soundHandle.node;
+      soundHandle.stop(t + hapDuration);
    }
-    // get frequency
-    if (!freq && typeof n === 'number') {
-      freq = fromMidi(n); // + 48);
-    }
-    // make oscillator
-    const o = getOscillator({ t, s, freq, duration: hapDuration, release });
-    chain.push(o);
-    // level down oscillators as they are really loud compared to samples i've tested
-    chain.push(gainNode(0.3));
-    // TODO: make adsr work with samples without pops
-    // envelope
-    const adsr = getADSR(attack, decay, sustain, release, 1, t, t + hapDuration);
-    chain.push(adsr);
  } else {
-    // destructure adsr here, because the default should be different for synths and samples
-    const { attack = 0.001, decay = 0.001, sustain = 1, release = 0.001 } = hap.value;
-    // load sample
-    if (speed === 0) {
-      // no playback
-      return;
-    }
-    if (!s) {
-      console.warn('no sample specified');
-      return;
-    }
-    const soundfont = getSoundfontKey(s);
-    let bufferSource;
-
-    if (soundfont) {
-      // is soundfont
-      bufferSource = await globalThis.getFontBufferSource(soundfont, note || n, ac, freq);
-    } else {
-      // is sample from loaded samples(..)
-      bufferSource = await getSampleBufferSource(s, n, note, speed, freq);
-    }
-    // asny stuff above took too long?
-    if (ac.currentTime > t) {
-      logger(`[sampler] still loading sound "${s}:${n}"`, 'highlight');
-      // console.warn('sample still loading:', s, n);
-      return;
-    }
-    if (!bufferSource) {
-      console.warn('no buffer source');
-      return;
-    }
-    bufferSource.playbackRate.value = Math.abs(speed) * bufferSource.playbackRate.value;
-    if (unit === 'c') {
-      // are there other units?
-      bufferSource.playbackRate.value = bufferSource.playbackRate.value * bufferSource.buffer.duration * cps;
-    }
-    let duration = soundfont || clip ? hapDuration : bufferSource.buffer.duration / bufferSource.playbackRate.value;
-    // "The computation of the offset into the sound is performed using the sound buffer's natural sample rate,
-    // rather than the current playback rate, so even if the sound is playing at twice its normal speed,
-    // the midway point through a 10-second audio buffer is still 5."
-    const offset = begin * duration * bufferSource.playbackRate.value;
-    duration = (end - begin) * duration;
-    if (loop) {
-      bufferSource.loop = true;
-      bufferSource.loopStart = offset;
-      bufferSource.loopEnd = offset + duration;
-      duration = loop * duration;
-    }
-    t += nudge;
-
-    bufferSource.start(t, offset);
-    if (cut !== undefined) {
-      cutGroups[cut]?.stop(t); // fade out?
-      cutGroups[cut] = bufferSource;
-    }
-    chain.push(bufferSource);
-    bufferSource.stop(t + duration + release);
-    const adsr = getADSR(attack, decay, sustain, release, 1, t, t + duration);
-    chain.push(adsr);
+    throw new Error(`sound ${s} not found! Is it loaded?`);
  }
+  if (!sourceNode) {
+    // if onTrigger does not return anything, we will just silently skip
+    // this can be used for things like speed(0) in the sampler
+    return;
+  }
+  if (ac.currentTime > t) {
+    logger('[webaudio] skip hap: still loading', ac.currentTime - t);
+    return;
+  }
+  const chain = []; // audio nodes that will be connected to each other sequentially
+  chain.push(sourceNode);

  // gain stage
  chain.push(gainNode(gain));
@@ -357,8 +232,9 @@ export const webaudioOutput = async (hap, deadline, hapDuration, cps) => {
  // connect chain elements together
  chain.slice(1).reduce((last, current) => last.connect(current), chain[0]);

-  // disconnect all nodes when source node has ended:
-  chain[0].onended = () => chain.concat([delaySend, reverbSend]).forEach((n) => n?.disconnect());
+  // toDisconnect = all the node that should be disconnected in onended callback
+  // this is crucial for performance
+  toDisconnect = chain.concat([delaySend, reverbSend]);
 };

 export const webaudioOutputTrigger = (t, hap, ct, cps) => webaudioOutput(hap, t - ct, hap.duration / cps, cps);
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/webdirt",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "WebDirt integration for Strudel",
  "main": "index.mjs",
  "type": "module",
@@ -1,7 +1,7 @@
 import * as strudel from '@strudel.cycles/core';
 const { Pattern } = strudel;
 import * as WebDirt from 'WebDirt';
-import { getLoadedSamples, loadBuffer, getLoadedBuffer } from '@strudel.cycles/webaudio';
+//import { loadBuffer, getLoadedBuffer } from '@strudel.cycles/webaudio';

 let webDirt;

@@ -62,8 +62,9 @@ export function loadWebDirt(config) {
 * @noAutocomplete
 */
 Pattern.prototype.webdirt = function () {
+  throw new Error('webdirt support has been dropped..');
  // create a WebDirt object and initialize Web Audio context
-  return this.onTrigger(async (time, e, currentTime) => {
+  /* return this.onTrigger(async (time, e, currentTime) => {
    if (!webDirt) {
      throw new Error('WebDirt not initialized!');
    }
@@ -92,5 +93,5 @@ Pattern.prototype.webdirt = function () {
        webDirt.playSample(msg, deadline);
      }
    }
-  });
+  }); */
 };
@@ -1,6 +1,6 @@
 {
  "name": "@strudel.cycles/xen",
-  "version": "0.6.0",
+  "version": "0.7.1",
  "description": "Xenharmonic API for strudel",
  "main": "index.mjs",
  "publishConfig": {
@@ -1,597 +0,0 @@
-[
-	{
-		"id": "toussaintEuclideanAlgorithmGenerates2005",
-		"type": "paper-conference",
-		"abstract": "The Euclidean algorithm (which comes down to us from Euclid's Elements) computes the greatest common divisor of two given integers. It is shown here that the structure of the Euclidean algorithm may be used to automatically generate, very efficiently, a large family of rhythms used as timelines (ostinatos), in traditional world music. These rhythms, here dubbed Euclidean rhythms, have the property that their onset patterns are distributed as evenly as possible in a mathematically precise sense, and optimal manner.",
-		"container-title": "In Proceedings of BRIDGES: Mathematical Connections in Art, Music and Science",
-		"page": "47–56",
-		"title": "The Euclidean Algorithm Generates Traditional Musical Rhythms",
-		"URL": "http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.62.231",
-		"author": [
-			{
-				"family": "Toussaint",
-				"given": "Godfried"
-			}
-		],
-		"issued": {
-			"date-parts": [
-				[
-					"2005"
-				]
-			]
-		}
-	},
-	{
-		"id": "roberts2015",
-		"type": "paper-conference",
-		"abstract": "We describe research extending the interactive affordances of textual code fragments in creative coding environments. In particular we examine the potential of source code both to display the state of running processes and also to alter state using means other than traditional text editing. In contrast to previous research that has focused on the inclusion of additional interactive widgets inside or alongside text editors, our research adds a parsing stage to the runtime evaluation of code fragments and imparts additional interactive capabilities on the source code itself. After implementing various techniques in the creative coding environment Gibber, we evaluate our research through a survey on the various methods of visual feedback provided by our research. In addition to results quantifying preferences for certain techniques over others, we found near unanimous support among survey respondents for including similar techniques in other live coding environments.",
-		"collection-title": "NIME 2015",
-		"container-title": "Proceedings of the international conference on New Interfaces for Musical Expression",
-		"event-place": "Baton Rouge, Louisiana, USA",
-		"ISBN": "978-0-692-49547-6",
-		"page": "126–131",
-		"publisher": "The School of Music and the Center for Computation and Technology (CCT), Louisiana State University",
-		"publisher-place": "Baton Rouge, Louisiana, USA",
-		"source": "ACM Digital Library",
-		"title": "Beyond Editing: Extended Interaction with Textual Code Fragments",
-		"title-short": "Beyond Editing",
-		"author": [
-			{
-				"family": "Roberts",
-				"given": "Charles"
-			},
-			{
-				"family": "Wright",
-				"given": "Matthew"
-			},
-			{
-				"family": "Kuchera-Morin",
-				"given": "JoAnn"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2021",
-					1,
-					27
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2015",
-					5,
-					30
-				]
-			]
-		}
-	},
-	{
-		"id": "rohrhuberSuperDirt2022",
-		"type": "software",
-		"abstract": "Tidal Audio Engine",
-		"genre": "SuperCollider",
-		"license": "GPL-2.0",
-		"note": "original-date: 2015-11-03T20:18:44Z",
-		"publisher": "musikinformatik",
-		"source": "GitHub",
-		"title": "SuperDirt",
-		"URL": "https://github.com/musikinformatik/SuperDirt",
-		"author": [
-			{
-				"family": "Rohrhuber",
-				"given": "Julian"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2022",
-					6,
-					24
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2022",
-					6,
-					24
-				]
-			]
-		}
-	},
-	{
-		"id": "mcleanAlgorithmicPattern2020",
-		"type": "paper-conference",
-		"abstract": "This paper brings together two main perspectives on algorithmic pattern. First, the writing of musical patterns in live coding performance, and second, the weaving of patterns in textiles. In both cases, algorithmic pattern is an interface between the human and the outcome, where small changes have far-reaching impact on the results. By bringing contemporary live coding and ancient textile approaches together, we reach a common view of pattern as algorithmic movement (e.g. looping, shifting, reflecting, interfering) in the making of things. This works beyond the usual definition of pattern used in musical interfaces, of mere repeating sequences. We conclude by considering the place of algorithmic pattern in a wider activity of making.",
-		"container-title": "Proceedings of the International Conference on New Interfaces for Musical Expression",
-		"event-place": "Birmingham, UK",
-		"event-title": "NIME2020",
-		"page": "265--270",
-		"publisher-place": "Birmingham, UK",
-		"title": "Algorithmic Pattern",
-		"URL": "https://zenodo.org/record/4813352",
-		"author": [
-			{
-				"family": "Mclean",
-				"given": "Alex"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2022",
-					1,
-					9
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2020",
-					6,
-					1
-				]
-			]
-		}
-	},
-	{
-		"id": "mcleanFeedforward2020",
-		"type": "paper-conference",
-		"abstract": "This is an improvised, from-scratch live coding performance. The NIME interface which this performance showcases is the new Feedfoward editor for the TidalCycles live coding environment. Feedforward is written in Haskell using the ncurses library for terminal-based user interfaces. It runs on low-powered hardware including the Raspberry Pi Zero, with formative testing of prototypes conducted with several groups of children between the ages of 8 and 14. Feedforward has a number of features designed to support improvised, multi-pattern live coding. Individual Tidal patterns are addressable with hotkeys for fast mute and unmuting. Each pattern has a stereo VU meter, to aid the quick matching of sound to pattern within a mix. In addition, TidalCycles has been extended to store context with each event, so that source code positions in its polyrhythmic sequence mini-notation are tracked. This allows steps to be highlighted in the source code when- ever they are active. This works even when Tidal combinators have been applied to manipulate the timeline. Formal evaluation has yet to take place, but this feature appears to support learning of how pattern manipulations work in Tidal. Feedforward and TidalCycles is free/open source software under a GPL licence version 3.0.",
-		"container-title": "Proceedings of New Interfaces for Musical Expression",
-		"event-place": "Birmingham",
-		"event-title": "NIME2020",
-		"publisher-place": "Birmingham",
-		"title": "Feedforward",
-		"URL": "https://zenodo.org/record/6353969",
-		"author": [
-			{
-				"family": "McLean",
-				"given": "Alex"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2022",
-					6,
-					24
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2020",
-					7,
-					21
-				]
-			]
-		}
-	},
-	{
-		"id": "robertsGibberLiveCoding2012",
-		"type": "paper-conference",
-		"abstract": "We present Gibber: a live coding environment for web browsers. Gibber performances are written in pure Java-Script with no syntactical additions or modifications; this enables Gibber code to be executed in any web page viewed inside a browser implementing a realtime audio API. Gib-ber offers an array of synthesis options (FM, granular, subtractive, physical modeling), audio effects and sequenc-ing objects to control them. The Gibber environment en-ables simple networked performances where multiple users simultaneously control a remote instance of Gibber. We strove to make the syntax of Gibber clear and concise; when coupled with the ability to run examples in any web page this gives Gibber interesting possibilities as an edu-cational tool. 1.",
-		"container-title": "In Proceedings of the 2012 International Computer Music Conference",
-		"source": "CiteSeer",
-		"title": "Gibber: Live coding audio in the browser",
-		"title-short": "Gibber",
-		"author": [
-			{
-				"family": "Roberts",
-				"given": "Charles"
-			},
-			{
-				"family": "Kuchera-morin",
-				"given": "Joann"
-			}
-		],
-		"issued": {
-			"date-parts": [
-				[
-					"2012"
-				]
-			]
-		}
-	},
-	{
-		"id": "ogbornEstuaryBrowserbasedCollaborative2017",
-		"type": "paper-conference",
-		"abstract": "This paper describes the initial design and development of Estuary, a browser-based collaborative projectional editing environment built on top of the popular TidalCycles language for the live coding of musical pattern. Key features of Estuary include a strict form of structure editing (making syntactical errors impossible), a click-only border-free approach to interface design, explicit notations to modulate the liveness of different parts of the code, and a server-based network collaboration system that can be used for many simultaneous collaborative live coding performances, as well as to present different views of the same live coding activity. Estuary has been developed using Reﬂex-DOM, a Haskell-based framework for web development whose strictness promises robustness and security advantages.",
-		"container-title": "Proceedings of the International Conference on Live Coding",
-		"event-place": "Morelia",
-		"event-title": "ICLC2017",
-		"language": "en",
-		"page": "11",
-		"publisher-place": "Morelia",
-		"source": "Zotero",
-		"title": "Estuary: Browser-based Collaborative Projectional Live Coding of Musical Patterns",
-		"author": [
-			{
-				"family": "Ogborn",
-				"given": "David"
-			},
-			{
-				"family": "Beverley",
-				"given": "Jamie"
-			},
-			{
-				"family": "Navarro del Angel",
-				"given": "Luis"
-			},
-			{
-				"family": "Tsabary",
-				"given": "Eldad"
-			},
-			{
-				"family": "McLean",
-				"given": "Alex"
-			}
-		],
-		"issued": {
-			"date-parts": [
-				[
-					"2017"
-				]
-			]
-		}
-	},
-	{
-		"id": "mcleanTidalVortexZero2022",
-		"type": "paper-conference",
-		"abstract": "In this paper we introduce ‘version zero’ of TidalVortex, an alternative implementation of the TidalCycles live coding system, using the Python programming language.  This is open-ended work, exploring what happens when we try to extract the 'essence' of a system like TidalCycles and translate it into another programming language, while taking advantage of the affordance of its new host. First, we review the substantial prior art in porting TidalCycles, and in representing musical patterns in Python. We then compare equivalent patterns written in Haskell (TidalCycles) and Python (TidalVortex), and relate implementation details of how functional reactive paradigms have translated from the pure functional, strongly typed Haskell to the more multi-paradigm, dynamically typed Python. Finally, we conclude with reflections and generalisable outcomes.",
-		"container-title": "Proceedings of the 7th International Conference on Live Coding",
-		"DOI": "10.5281/zenodo.6456380",
-		"event-place": "Limerick, Ireland",
-		"event-title": "ICMC2022",
-		"note": "event-title: International Conference on Computer Music (ICMC)",
-		"publisher": "Zenodo",
-		"publisher-place": "Limerick, Ireland",
-		"title": "TidalVortex Zero",
-		"URL": "https://zenodo.org/record/6456380/export/hx",
-		"author": [
-			{
-				"family": "McLean",
-				"given": "Alex"
-			},
-			{
-				"family": "Forment",
-				"given": "Raphaël"
-			},
-			{
-				"family": "Le Beux",
-				"given": "Sylvain"
-			},
-			{
-				"family": "Silvani",
-				"given": "Damián"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2022",
-					6,
-					24
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2022",
-					4,
-					12
-				]
-			]
-		}
-	},
-	{
-		"id": "solomonPurescriptocarina2022",
-		"type": "software",
-		"abstract": "Web audio graphs as a stream",
-		"genre": "PureScript",
-		"license": "Apache-2.0",
-		"note": "original-date: 2021-03-25T12:19:55Z",
-		"source": "GitHub",
-		"title": "purescript-ocarina",
-		"URL": "https://github.com/mikesol/purescript-ocarina",
-		"author": [
-			{
-				"family": "Solomon",
-				"given": "Mike"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2022",
-					6,
-					24
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2022",
-					6,
-					20
-				]
-			]
-		}
-	},
-	{
-		"id": "orlareyFaustProgrammingLanguage2023",
-		"type": "software",
-		"abstract": "Functional programming language for signal processing and sound synthesis",
-		"genre": "C++",
-		"note": "original-date: 2016-11-05T13:09:11Z",
-		"publisher": "GRAME",
-		"source": "GitHub",
-		"title": "Faust - Programming Language for Audio Applications and Plugins",
-		"URL": "https://github.com/grame-cncm/faust",
-		"author": [
-			{
-				"family": "Orlarey",
-				"given": "Yann"
-			},
-			{
-				"family": "Fober",
-				"given": "Dominique"
-			},
-			{
-				"family": "Letz",
-				"given": "Stéphane"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					14
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					13
-				]
-			]
-		}
-	},
-	{
-		"id": "jackHydra2023",
-		"type": "software",
-		"abstract": "Livecoding networked visuals in the browser",
-		"genre": "JavaScript",
-		"license": "AGPL-3.0",
-		"note": "original-date: 2022-06-13T16:57:34Z",
-		"source": "GitHub",
-		"title": "Hydra",
-		"URL": "https://github.com/ojack/hydra",
-		"author": [
-			{
-				"family": "Jack",
-				"given": "Olivia"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					14
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					8
-				]
-			]
-		}
-	},
-	{
-		"id": "lanGlicol2023",
-		"type": "software",
-		"abstract": "Graph-oriented live coding language and music DSP library written in Rust",
-		"genre": "Rust",
-		"license": "MIT",
-		"note": "original-date: 2020-07-13T22:13:33Z",
-		"source": "GitHub",
-		"title": "Glicol",
-		"URL": "https://github.com/chaosprint/glicol",
-		"author": [
-			{
-				"family": "Lan",
-				"given": "Qichao"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					14
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					14
-				]
-			]
-		}
-	},
-	{
-		"id": "ogbornWebDirt2022",
-		"type": "software",
-		"abstract": "Sampling engine implemented in Web Audio API (rough re-creation of Dirt)",
-		"genre": "JavaScript",
-		"license": "GPL-3.0",
-		"note": "original-date: 2016-05-04T21:19:04Z",
-		"source": "GitHub",
-		"title": "WebDirt",
-		"URL": "https://github.com/dktr0/WebDirt",
-		"author": [
-			{
-				"family": "Ogborn",
-				"given": "David"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					14
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2022",
-					12,
-					14
-				]
-			]
-		}
-	},
-	{
-		"id": "roosStrudelAlgorithmicPatterns2022",
-		"type": "paper-conference",
-		"abstract": "This paper introduces Strudel (or sometimes StrudelCycles), an alternative implementation of the Tidal (or Tidal-Cycles) live coding system, using the JavaScript programming language. Strudel is an attempt to make live coding more accessible, by creating a system that runs entirely in the browser, while opening Tidals approach to algorithmic patterns (Mclean 2020) up to modern audio/visual web technologies. The Strudel REPL is a live code editor dedicated to manipulating Strudel patterns while they play, with builtin visual feedback. While Strudel is written in JavaScript, the API is optimized for simplicity and readability by applying code transformations on the syntax tree level, allowing language operations that would otherwise be impossible. The application supports multiple ways to output sound, including Tone.js, Web Audio nodes, OSC (Open Sound Control) messages, Web Serial andWeb MIDI. The project is split into multiple packages, allowing granular reuse in other applications. Apart from TidalCycles, Strudel draws inspiration from many prior existing projects like TidalVortex (McLean et al. 2022), Gibber (Roberts and Kuchera-morin 2012), Estuary (Ogborn et al. 2017), Hydra (Jack [2022] 2022), Ocarina (Solomon [2021] 2022) and Feedforward (McLean 2020).",
-		"container-title": "Proceedings of Web Audio Conference",
-		"event-place": "Cannes, France",
-		"event-title": "WAC2022",
-		"note": "DOI: 10.5281/zenodo.6821023\npublisher: Zenodo",
-		"publisher-place": "Cannes, France",
-		"title": "Strudel: Algorithmic Patterns for the Web",
-		"URL": "https://zenodo.org/record/6821023",
-		"author": [
-			{
-				"family": "Roos",
-				"given": "Felix"
-			},
-			{
-				"family": "McLean",
-				"given": "Alex"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2022",
-					11,
-					29
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2022",
-					6,
-					28
-				]
-			]
-		}
-	},
-	{
-		"id": "yiWebAssemblyAudioWorkletCsound2018",
-		"type": "paper-conference",
-		"abstract": "This paper describes WebAssembly AudioWorklet (WAAW)\nCsound, one of the implementations of Web Audio Csound.\nWe begin by introducing the background to this current implementation, stemming from the two first ports of Csound\nto the web platform using Native Clients and asm.js. The\ntechnology of WebAssembly is then introduced and discussed in its more relevant aspects. The AudioWorklet interface of Web Audio API is explored, together with its use in\nWAAW Csound. We complement this discussion by considering the overarching question of support for multiple platforms, which implement different versions of Web Audio.\nSome initial examples of the system are presented to illustrate various potential applications. Finally, we complement\nthe paper by discussing current issues that are fundamental\nfor this project and others that rely on the development of\na robust support for WASM-based audio computing.",
-		"event-place": "Berlin, Germany",
-		"event-title": "Web Audio Conference WAC-2018",
-		"language": "en",
-		"publisher-place": "Berlin, Germany",
-		"source": "mural.maynoothuniversity.ie",
-		"title": "WebAssembly AudioWorklet Csound",
-		"URL": "https://mural.maynoothuniversity.ie/16018/",
-		"author": [
-			{
-				"family": "Yi",
-				"given": "Steven"
-			},
-			{
-				"family": "Lazzarini",
-				"given": "Victor"
-			},
-			{
-				"family": "Costello",
-				"given": "Edward"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					14
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2018"
-				]
-			]
-		}
-	},
-	{
-		"id": "majdaPeggy2023",
-		"type": "software",
-		"abstract": "Peggy: Parser generator for JavaScript",
-		"genre": "JavaScript",
-		"license": "MIT",
-		"note": "original-date: 2020-11-21T11:52:39Z",
-		"publisher": "peggyjs",
-		"source": "GitHub",
-		"title": "Peggy",
-		"URL": "https://github.com/peggyjs/peggy",
-		"author": [
-			{
-				"family": "Majda",
-				"given": "David"
-			}
-		],
-		"accessed": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					14
-				]
-			]
-		},
-		"issued": {
-			"date-parts": [
-				[
-					"2023",
-					3,
-					14
-				]
-			]
-		}
-	}
-]
@@ -0,0 +1,818 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+  <meta http-equiv="Content-Style-Type" content="text/css" />
+  <meta name="generator" content="pandoc" />
+  <meta name="date" content="2022-12-14" />
+  <title>Strudel: live coding patterns on the Web</title>
+  <style type="text/css">code{white-space: pre;}</style>
+  <style type="text/css">
+pre > code.sourceCode { white-space: pre; position: relative; }
+pre > code.sourceCode > span { display: inline-block; line-height: 1.25; }
+pre > code.sourceCode > span:empty { height: 1.2em; }
+.sourceCode { overflow: visible; }
+code.sourceCode > span { color: inherit; text-decoration: inherit; }
+div.sourceCode { margin: 1em 0; }
+pre.sourceCode { margin: 0; }
+@media screen {
+div.sourceCode { overflow: auto; }
+}
+@media print {
+pre > code.sourceCode { white-space: pre-wrap; }
+pre > code.sourceCode > span { text-indent: -5em; padding-left: 5em; }
+}
+pre.numberSource code
+  { counter-reset: source-line 0; }
+pre.numberSource code > span
+  { position: relative; left: -4em; counter-increment: source-line; }
+pre.numberSource code > span > a:first-child::before
+  { content: counter(source-line);
+    position: relative; left: -1em; text-align: right; vertical-align: baseline;
+    border: none; display: inline-block;
+    -webkit-touch-callout: none; -webkit-user-select: none;
+    -khtml-user-select: none; -moz-user-select: none;
+    -ms-user-select: none; user-select: none;
+    padding: 0 4px; width: 4em;
+    color: #aaaaaa;
+  }
+pre.numberSource { margin-left: 3em; border-left: 1px solid #aaaaaa;  padding-left: 4px; }
+div.sourceCode
+  {   }
+@media screen {
+pre > code.sourceCode > span > a:first-child::before { text-decoration: underline; }
+}
+code span.al { color: #ff0000; font-weight: bold; } /* Alert */
+code span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */
+code span.at { color: #7d9029; } /* Attribute */
+code span.bn { color: #40a070; } /* BaseN */
+code span.bu { color: #008000; } /* BuiltIn */
+code span.cf { color: #007020; font-weight: bold; } /* ControlFlow */
+code span.ch { color: #4070a0; } /* Char */
+code span.cn { color: #880000; } /* Constant */
+code span.co { color: #60a0b0; font-style: italic; } /* Comment */
+code span.cv { color: #60a0b0; font-weight: bold; font-style: italic; } /* CommentVar */
+code span.do { color: #ba2121; font-style: italic; } /* Documentation */
+code span.dt { color: #902000; } /* DataType */
+code span.dv { color: #40a070; } /* DecVal */
+code span.er { color: #ff0000; font-weight: bold; } /* Error */
+code span.ex { } /* Extension */
+code span.fl { color: #40a070; } /* Float */
+code span.fu { color: #06287e; } /* Function */
+code span.im { color: #008000; font-weight: bold; } /* Import */
+code span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */
+code span.kw { color: #007020; font-weight: bold; } /* Keyword */
+code span.op { color: #666666; } /* Operator */
+code span.ot { color: #007020; } /* Other */
+code span.pp { color: #bc7a00; } /* Preprocessor */
+code span.sc { color: #4070a0; } /* SpecialChar */
+code span.ss { color: #bb6688; } /* SpecialString */
+code span.st { color: #4070a0; } /* String */
+code span.va { color: #19177c; } /* Variable */
+code span.vs { color: #4070a0; } /* VerbatimString */
+code span.wa { color: #60a0b0; font-weight: bold; font-style: italic; } /* Warning */
+  </style>
+  <link rel="stylesheet" href="css/iclc.css" />
+</head>
+<body>
+<div id="header">
+<h1 class="title">Strudel: live coding patterns on the Web</h1>
+<ul id="authorlist">
+<li>true</li>
+<li>true</li>
+</ul>
+<h3 class="date">2022-12-14</h3>
+</div>
+
+<h2 class="abstract">Abstract</h2>
+<div id="abstract">
+<p>This paper introduces Strudel, which brings the TidalCycles approach
+to live coding algorithmic patterns to native JavaScript and the web. We
+begin by giving a little background of the first year of development,
+before sharing some detail about its implementation and examples of use.
+We go on to outline the wide range of synthesis and other outputs
+available in Strudel, including WebAudio, MIDI, OSC (for SuperDirt),
+WebSerial and CSound, and introduce Strudel’s REPL live editor,
+including its built-in visualisations. We then compare Strudel with
+Tidal, the trade-offs involved between JavaScript and Haskell, and the
+unique capabilities offered by Strudel for aligning patterns.</p>
+</div>
+
+<h1 data-number="1" id="introduction"><span
+class="header-section-number">1</span> Introduction</h1>
+<p>In the following paper, we introduce <em>Strudel</em>, an alternative
+implementation of the TidalCycles (or ‘Tidal’ for short) live coding
+system, using the JavaScript programming language. Strudel is an attempt
+to make live coding more accessible, by creating a system that runs
+entirely in the browser, while opening Tidal’s approach to algorithmic
+patterns <span class="citation"
+data-cites="mcleanAlgorithmicPattern2020a">(Mclean 2020)</span> up to
+modern audio/visual web technologies. The Strudel REPL is a live code
+editor dedicated to manipulating patterns while they play, with builtin
+visual feedback. While Strudel is written in JavaScript, the API is
+optimized for simplicity and readability by applying code
+transformations on the syntax tree level, allowing language operations
+that would otherwise be impossible. The application supports multiple
+ways to output sound, including Tone.js, Web Audio Nodes, OSC (Open
+Sound Control) messages, Web Serial, Web MIDI and Csound. The project is
+split into multiple packages, allowing granular reuse in other
+applications. Apart from TidalCycles, Strudel draws inspiration from
+many prior existing projects like TidalVortex <span class="citation"
+data-cites="mcleanTidalVortexZero2022">(McLean et al. 2022)</span>,
+Gibber <span class="citation"
+data-cites="robertsGibberLiveCoding2012">(Roberts and Kuchera-morin
+2012)</span>, Estuary <span class="citation"
+data-cites="ogbornEstuaryBrowserbasedCollaborative2017">(Ogborn et al.
+2017)</span>, Hydra <span class="citation"
+data-cites="jackHydra2022">(Jack [2022] 2022)</span>, Ocarina <span
+class="citation" data-cites="solomonPurescriptocarina2022">(Solomon
+[2021] 2022)</span> and Feedforward <span class="citation"
+data-cites="mcleanFeedforward2020">(McLean 2020)</span>. This paper
+expands the Strudel Demo paper for the Web Audio Conference 2022 <span
+class="citation" data-cites="StrudelWAC2022">(Roos and McLean
+2022)</span>.</p>
+<p>The first tentative commit to the Strudel project was on 22nd January
+2022 by Alex McLean, with the core representation implemented over the
+following few days. Although this was his first attempt at a
+JavaScript-based application, by 27th January, Alex had managed to
+upload the initial version to the ‘npm’ javascript package database,
+sharing with the wider community for comment. By 4th February, Felix
+Roos had discovered Strudel and contributed a ‘REPL’ user interface to
+it, and then contributed a scheduler the next day, so that Strudel could
+already make sound. At this point, Alex and Felix shared ownership to
+the repository, and the project has since proved to be a productive
+confluence of Felix’s own work into music representation and
+visualisation, with Alex’s experience with making Tidal. Felix has since
+become the primary contributor to Strudel, with Alex continuing to jump
+between developing both Strudel and Tidal. Aspects of Strudel’s
+development have therefore fed back into TidalCycles, and both systems
+have maintained a shared conceptual underpinning. We plan to continue
+working towards feature parity between these systems, although within
+the syntactical trade-offs and library ecosystems of JavaScript and
+Haskell, some divergence is inevitable and healthy.</p>
+<p>Over the first year of its life, Strudel is now a fully-fledged live
+coding environment, porting Tidal’s core represention of patterns,
+pattern transformations, and mininotation for polymetric sequences,
+combined with a wealth of features for synthesising and visualising
+those patterns.</p>
+<h1 data-number="2" id="from-tidal-to-strudel-and-back"><span
+class="header-section-number">2</span> From Tidal to Strudel and
+back</h1>
+<p>As mentioned above, the original Tidal is implemented as a domain
+specific language (DSL) embedded in the Haskell pure functional
+programming language, and takes advantage of Haskell’s terse syntax and
+advanced, ‘strong’ type system. JavaScript on the other hand, is a
+multi-paradigm programming language, with a dynamic type system. Because
+Tidal leans heavily on many of Haskell’s more unique features, it was
+not always clear that it could meaningfully be ported to a
+multi-paradigm scripting language. However, this possibility was already
+demonstrated with an earlier port to Python [TidalVortex; <span
+class="citation" data-cites="mcleanTidalVortexZero2022">McLean et al.
+(2022)</span>], and we have now successfully implemented Tidal’s pure
+functional representation of patterns in Strudel, including partial
+application, currying, and the functor, applicative and monadic
+structures that underlie Tidal’s expressive pattern transformations. The
+result is a terse and highly composable system, where everything is
+either a pattern, or a function for combining and manipulating patterns,
+offering a rich creative ground for exploration.</p>
+<p>This development process has been far from a one-way port, however.
+The process of porting Tidal’s concepts has also opened up new
+possibilities, some just from revisiting every design decision, and some
+from the particular affordances and constraints offered by JavaScript.
+This has lead to new features (and indeed bugfixes) that have found
+their way back to Tidal where appropriate, and ongoing work that we will
+return to in the conclusion of this paper.</p>
+<h1 data-number="3" id="representing-patterns"><span
+class="header-section-number">3</span> Representing Patterns</h1>
+<p>Patterns are the essence of Tidal. Its patterns are abstract entities
+that represent flows of time as functions, adapting a technique called
+pure functional reactive programming. Taking a time span as its input, a
+Pattern can output a set of events that happen within that time span. It
+depends on the structure of the Pattern how the events are located in
+time. From now on, this process of generating events from a time span
+will be called <strong>querying</strong>. Example:</p>
+<div class="sourceCode" id="cb1"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="kw">const</span> pattern <span class="op">=</span> <span class="fu">sequence</span>(c3<span class="op">,</span> [e3<span class="op">,</span> g3])</span>
+<span id="cb1-2"><a href="#cb1-2" aria-hidden="true" tabindex="-1"></a><span class="kw">const</span> events <span class="op">=</span> pattern<span class="op">.</span><span class="fu">queryArc</span>(<span class="dv">0</span><span class="op">,</span> <span class="dv">1</span>)</span>
+<span id="cb1-3"><a href="#cb1-3" aria-hidden="true" tabindex="-1"></a><span class="bu">console</span><span class="op">.</span><span class="fu">log</span>(events<span class="op">.</span><span class="fu">map</span>(e <span class="kw">=&gt;</span> e<span class="op">.</span><span class="fu">show</span>()))</span></code></pre></div>
+<p>In this example, we create a pattern using the <code>sequence</code>
+function and <strong>query</strong> it for the time span from
+<code>0</code> to <code>1</code>. Those numbers represent units of time
+called <strong>cycles</strong>. The length of one cycle depends on the
+tempo, which defaults to one cycle per second. The resulting events
+are:</p>
+<div class="sourceCode" id="cb2"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a>[{ <span class="dt">value</span><span class="op">:</span> <span class="st">&#39;c3&#39;</span><span class="op">,</span> <span class="dt">begin</span><span class="op">:</span> <span class="dv">0</span><span class="op">,</span> <span class="dt">end</span><span class="op">:</span> <span class="dv">1</span><span class="op">/</span><span class="dv">2</span> }<span class="op">,</span></span>
+<span id="cb2-2"><a href="#cb2-2" aria-hidden="true" tabindex="-1"></a>{ <span class="dt">value</span><span class="op">:</span> <span class="st">&#39;e3&#39;</span><span class="op">,</span> <span class="dt">begin</span><span class="op">:</span> <span class="dv">1</span><span class="op">/</span><span class="dv">2</span><span class="op">,</span> <span class="dt">end</span><span class="op">:</span> <span class="dv">3</span><span class="op">/</span><span class="dv">4</span> }<span class="op">,</span></span>
+<span id="cb2-3"><a href="#cb2-3" aria-hidden="true" tabindex="-1"></a>{ <span class="dt">value</span><span class="op">:</span> <span class="st">&#39;g3&#39;</span><span class="op">,</span> <span class="dt">begin</span><span class="op">:</span> <span class="dv">3</span><span class="op">/</span><span class="dv">4</span><span class="op">,</span> <span class="dt">end</span><span class="op">:</span> <span class="dv">1</span> }]</span></code></pre></div>
+<p>Each event has a value, a begin time and an end time, where time is
+represented as a fraction. In the above case, the events are placed in
+sequential order, where c3 takes the first half, and e3 and g3 together
+take the second half. This temporal placement is the result of the
+<code>sequence</code> function, which divides its arguments equally over
+one cycle. If an argument is an array, the same rule applies to that
+part of the cycle. In the example, e3 and g3 are divided equally over
+the second half of the whole cycle.</p>
+<p>The above examples do not represent how Strudel is used in practice.
+In the live coding editor, the user only has to type in the pattern
+itself, the querying will be handled by the scheduler. The scheduler
+will repeatedly query the pattern for events, which are then scheduled
+as sound synthesis or other event triggers. Also, the above event data
+structure has been simplified for readability.</p>
+<figure>
+<img src="images/strudel-screenshot2.png" style="width:60.0%"
+alt="Screenshot of the Strudel ‘REPL’ live coding editor, including piano-roll visualisation." />
+<figcaption aria-hidden="true">Screenshot of the Strudel ‘REPL’ live
+coding editor, including piano-roll visualisation.</figcaption>
+</figure>
+<h1 data-number="4" id="making-patterns"><span
+class="header-section-number">4</span> Making Patterns</h1>
+<p>In practice, the end-user live coder will not deal with constructing
+patterns directly, but will rather build patterns using Strudel’s
+extensive combinator library to create, combine and transform
+patterns.</p>
+<p>The live coder will rarely use the <code>sequence</code> function as
+seen above, as sequencing is implicit in many functions. For example in
+the following, the <code>note</code> function constructs a pattern of
+notes, sequencing its arguments in the same manner as the previous
+example.</p>
+<div class="sourceCode" id="cb3"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="fu">note</span>(c3<span class="op">,</span> [e3<span class="op">,</span> g3])</span></code></pre></div>
+<p>Perhaps more often, they will use the mini-notation for even terser
+notation of rhythmic sequences: [^This last example is also valid Tidal
+code, albeit the parenthesis is not required in its Haskell syntax in
+this case. Tidal does not support passing sequences as lists directly to
+the <code>note</code> function, however.].</p>
+<div class="sourceCode" id="cb4"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb4-1"><a href="#cb4-1" aria-hidden="true" tabindex="-1"></a><span class="fu">note</span>(<span class="st">&quot;c3 [e3 g3]&quot;</span>)</span></code></pre></div>
+<p>Such sequences are often treated only a starting point for
+manipulation, where they then undergo pattern transformations such as
+repetition, symmetry, interference/combination or randomisation,
+potentially at multiple timescales. Because Strudel patterns are
+represented as pure functions of time rather than as data structures,
+very long and complex generative results can be represented and
+manipulated without having to store the resulting sequences in
+memory.</p>
+<h1 data-number="5" id="pattern-example"><span
+class="header-section-number">5</span> Pattern Example</h1>
+<p>The following example showcases how patterns can be utilized to
+create musical complexity from simple parts, using repetition and
+interference:</p>
+<div class="sourceCode" id="cb5"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="st">&quot;&lt;0 2 [4 6](3,4,1) 3&gt;&quot;</span></span>
+<span id="cb5-2"><a href="#cb5-2" aria-hidden="true" tabindex="-1"></a><span class="op">.</span><span class="fu">off</span>(<span class="dv">1</span><span class="op">/</span><span class="dv">4</span><span class="op">,</span> <span class="fu">add</span>(<span class="dv">2</span>))</span>
+<span id="cb5-3"><a href="#cb5-3" aria-hidden="true" tabindex="-1"></a><span class="op">.</span><span class="fu">off</span>(<span class="dv">1</span><span class="op">/</span><span class="dv">2</span><span class="op">,</span> <span class="fu">add</span>(<span class="dv">6</span>))</span>
+<span id="cb5-4"><a href="#cb5-4" aria-hidden="true" tabindex="-1"></a><span class="op">.</span><span class="fu">scale</span>(<span class="st">&#39;D minor&#39;</span>)</span>
+<span id="cb5-5"><a href="#cb5-5" aria-hidden="true" tabindex="-1"></a><span class="op">.</span><span class="fu">legato</span>(<span class="op">.</span><span class="dv">25</span>)</span>
+<span id="cb5-6"><a href="#cb5-6" aria-hidden="true" tabindex="-1"></a><span class="op">.</span><span class="fu">note</span>()<span class="op">.</span><span class="fu">s</span>(<span class="st">&quot;sawtooth square&quot;</span>)</span>
+<span id="cb5-7"><a href="#cb5-7" aria-hidden="true" tabindex="-1"></a><span class="op">.</span><span class="fu">delay</span>(<span class="op">.</span><span class="dv">8</span>)<span class="op">.</span><span class="fu">delaytime</span>(<span class="op">.</span><span class="dv">125</span>)</span></code></pre></div>
+<p>The pattern starts with a rhythm of numbers in mini notation, which
+are later interpreted inside the scale of D minor. The first line could
+also be expressed without mini notation:</p>
+<div class="sourceCode" id="cb6"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="fu">cat</span>(<span class="dv">0</span><span class="op">,</span> <span class="dv">2</span><span class="op">,</span> [<span class="dv">4</span><span class="op">,</span> <span class="dv">6</span>]<span class="op">.</span><span class="fu">euclid</span>(<span class="dv">3</span><span class="op">,</span> <span class="dv">4</span><span class="op">,</span> <span class="dv">1</span>)<span class="op">,</span> <span class="dv">3</span>)</span></code></pre></div>
+<p>These numbers then undergo various pattern transformations. Here is a
+short description of all the functions used:</p>
+<ul>
+<li><code>cat</code>: play elements sequentially, where each lasts one
+cycle</li>
+<li><code>brackets</code>: elements inside brackets are divided equally
+over the time of their parent</li>
+<li><code>.euclid(p, s, o)</code>: place p pulses evenly over s steps,
+with offset o <span class="citation"
+data-cites="toussaintEuclideanAlgorithmGenerates2005">(Toussaint
+2005)</span></li>
+<li><code>.off(n, f)</code>: layers a pattern on top of itself, with the
+new layer offset by n cycles, and with function f applied</li>
+<li><code>.legato(n)</code>: multiply the duration of all events in a
+pattern by a factor of n</li>
+<li><code>.echo(t, n, v)</code>: copy each event t times, with n cycles
+in between each copy, decreasing velocity by v</li>
+<li><code>.note()</code>: interpretes values as notes</li>
+<li><code>.s(name)</code>: play back each event with the given
+sound</li>
+<li><code>.delay(wet)</code>: add delay</li>
+<li><code>.delaytime(t)</code>: set delay time</li>
+</ul>
+<p>Much of the above will be familiar to Tidal users.</p>
+<!-- This example shows some of Strudel's unique support for chords and transposition familiar to students of Western music theory. This differs a little from Tidal's approach and thanks to the integration of the javascript library XXX (*TODO* ? or is this all your work Felix?), Strudel's support for tonal transformations such as voice leading is perhaps respects more advanced than Tidal. -->
+<h1 data-number="6" id="ways-to-make-sound-and-other-events"><span
+class="header-section-number">6</span> Ways to make Sound (and other
+events)</h1>
+<p>To generate sound, Strudel supports bindings for different
+outputs:</p>
+<ul>
+<li>Tone.js (deprecated)</li>
+<li>Web Audio API</li>
+<li>WebDirt, a js recreation of Tidal’s <em>Dirt</em> sample engine
+(deprecated)</li>
+<li>OSC via osc-js, compatible with superdirt</li>
+<li>Csound via the Csound WebAssembly build</li>
+<li>MIDI via WebMIDI</li>
+<li>Serial via WebSerial</li>
+</ul>
+<p>At first, we used Tone.js as sound output, but it proved to be
+limited for the use case of Strudel, where each individual event could
+potentially have a completely different audio graph. While the Web Audio
+API takes a <em>fire-and-forget</em> approach, creating a lot of Tone.js
+instruments and effects causes performance issues quickly. For that
+reason, we chose to search for alternatives.</p>
+<p>Strudel’s new default output uses the Web Audio API to create a new
+audio graph for each event. It currently supports basic oscillators,
+sample playback, various effects and an experimental support for
+soundfonts.</p>
+<p>WebDirt <span class="citation"
+data-cites="ogbornDktr0WebDirt2022">(Ogborn [2016] 2022)</span> was
+created as part of the Estuary Live Coding System <span class="citation"
+data-cites="ogbornEstuaryBrowserbasedCollaborative2017">(Ogborn et al.
+2017)</span>, and proved to be a solid choice for handling samples in
+Strudel as well. We are however focused on working more directly with
+the Web Audio API to be able to integrate new features more tightly.</p>
+<p>Using the OSC protocol via Strudel’s provided Node.js-based OSC proxy
+server, it is possible to send network messages to trigger events. This
+is mainly used to render sound using SuperDirt <span class="citation"
+data-cites="SuperDirt2022">(<em>SuperDirt</em> [2015] 2022)</span>,
+which is the well-developed Supercollider-based synthesis framework that
+Tidal live coders generally use as standard.</p>
+<p>Recently, the experimental integration of Csound proved to bring a
+new dimension of sound design capabilities to Strudel. Thanks to the
+WebAssembly distribution of this classic system <span class="citation"
+data-cites="CsoundWebAssembly">(Yi, Lazzarini, and Costello
+2018)</span>, Csound ‘orchestra’ synthesisers can be embedded in and
+then patterned with Strudel code.</p>
+<p>MIDI output can also be used to send MIDI messages to either external
+instruments or to other programs on the same device. Unlike OSC, Strudel
+is able to send MIDI directly without requiring additional proxy
+software, but only from web browsers that support it (at the time of
+writing, this means Chromium-based browsers).</p>
+<p>Finally, Strudel supports Serial output, for example to trigger
+events via microcontrollers. This has already been explored for robot
+choreography by Kate Sicchio and Alex McLean, via a performance
+presented at the International Conference on Live Interfaces 2022.</p>
+<h1 data-number="7" id="the-strudel-repl"><span
+class="header-section-number">7</span> The Strudel REPL</h1>
+<p>While Strudel can be used as a library in any JavaScript codebase,
+its main, reference user interface is the Strudel REPL[^REPL stands for
+read, evaluate, print/play, loop. It is friendly jargon for an
+interactive programming interface from computing heritage, usually for a
+commandline interface but also applied to live coding editors.], which
+is a browser-based live coding environment. This live code editor is
+dedicated to manipulating Strudel patterns while they play. The REPL
+features built-in visual feedback, which highlights which elements in
+the patterned (mini-notation) sequences are influencing the event that
+is currently being played. This feedback is designed to support both
+learning and live use of Strudel.</p>
+<p>Besides a UI for playback control and meta information, the main part
+of the REPL interface is the code editor powered by CodeMirror. In it,
+the user can edit and evaluate pattern code live, using one of the
+available synthesis outputs to create music and/or sound art. The
+control flow of the REPL follows 3 basic steps:</p>
+<ol type="1">
+<li>The user writes and updates code. Each update transpiles and
+evaluates it to create a <code>Pattern</code> instance</li>
+<li>While the REPL is running, the <code>Scheduler</code> queries the
+active <code>Pattern</code> by a regular interval, generating
+<code>Events</code> (also known as <code>Haps</code> in Strudel) for the
+next time span.</li>
+<li>For each scheduling tick, all generated <code>Events</code> are
+triggered by calling their <code>onTrigger</code> method, which is set
+by the output.</li>
+</ol>
+<figure>
+<img
+src="https://github.com/tidalcycles/strudel/raw/talk/talk/public/strudelflow.png?raw=true"
+style="width:43.0%" alt="REPL control flow" />
+<figcaption aria-hidden="true">REPL control flow</figcaption>
+</figure>
+<h2 data-number="7.1" id="user-code"><span
+class="header-section-number">7.1</span> User Code</h2>
+<p>To create a <code>Pattern</code> from the user code, two steps are
+needed:</p>
+<ol type="1">
+<li>Transpile the JS input code to make it functional</li>
+<li>Evaluate the transpiled code</li>
+</ol>
+<h3 data-number="7.1.1" id="transpilation-evaluation"><span
+class="header-section-number">7.1.1</span> Transpilation &amp;
+Evaluation</h3>
+<p>In the JavaScript world, using transpilation is a common practise to
+be able to use language features that are not supported by the base
+language. Tools like <code>babel</code> will transpile code that
+contains unsupported language features into a version of the code
+without those features.</p>
+<p>In the same tradition, Strudel can add a transpilation step to
+simplify the user code in the context of live coding. For example, the
+Strudel REPL lets the user create mini notation patterns using just
+double quoted strings, while single quoted strings remain what they
+are:</p>
+<div class="sourceCode" id="cb7"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="st">&quot;c3 [e3 g3]*2&quot;</span></span></code></pre></div>
+<p>is transpiled to:</p>
+<div class="sourceCode" id="cb8"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a><span class="fu">mini</span>(<span class="st">&quot;c3 [e3 g3]*2&quot;</span>)<span class="op">.</span><span class="fu">withMiniLocation</span>([<span class="dv">1</span><span class="op">,</span><span class="dv">0</span><span class="op">,</span><span class="dv">0</span>]<span class="op">,</span>[<span class="dv">1</span><span class="op">,</span><span class="dv">14</span><span class="op">,</span><span class="dv">14</span>])</span></code></pre></div>
+<p>Here, the string is wrapped in <code>mini</code>, which will create a
+pattern from a mini notation string. Additionally, the
+<code>withMiniLocation</code> method passes the original source code
+location of the string to the pattern, which enables highlighting active
+events.</p>
+<p>Other convenient features like pseudo variables, operator overloading
+and top level await are possible with transpilation.</p>
+<p>After the transpilation, the code is ready to be evaluated into a
+<code>Pattern</code>.</p>
+<p>Behind the scenes, the user code string is parsed with
+<code>acorn</code>, turning it into an Abstract Syntax Tree (AST). The
+AST allows changing the structure of the code before generating the
+transpiled version using <code>escodegen</code>.</p>
+<h3 data-number="7.1.2" id="mini-notation"><span
+class="header-section-number">7.1.2</span> Mini Notation</h3>
+<p>While the transpilation allows JavaScript to express Patterns in a
+less verbose way, it is still preferable to use the Mini Notation as a
+more compact way to express rhythm. Strudel aims to provide the same
+Mini Notation features and syntax as used in Tidal.</p>
+<p>The Mini Notation parser is implemented using <code>peggy</code>,
+which allows generating performant parsers for Domain Specific Languages
+(DSLs) using a concise grammar notation. The generated parser turns the
+Mini Notation string into an AST which is used to call the respective
+Strudel functions with the given structure. For example,
+<code>"c3 [e3 g3]*2"</code> will result in the following calls:</p>
+<div class="sourceCode" id="cb9"><pre class="sourceCode js"><code class="sourceCode javascript"><span id="cb9-1"><a href="#cb9-1" aria-hidden="true" tabindex="-1"></a><span class="fu">seq</span>(</span>
+<span id="cb9-2"><a href="#cb9-2" aria-hidden="true" tabindex="-1"></a>  <span class="fu">reify</span>(<span class="st">&#39;c3&#39;</span>)<span class="op">.</span><span class="fu">withLocation</span>([<span class="dv">1</span><span class="op">,</span><span class="dv">1</span><span class="op">,</span><span class="dv">1</span>]<span class="op">,</span> [<span class="dv">1</span><span class="op">,</span><span class="dv">4</span><span class="op">,</span><span class="dv">4</span>])<span class="op">,</span></span>
+<span id="cb9-3"><a href="#cb9-3" aria-hidden="true" tabindex="-1"></a>  <span class="fu">seq</span>(</span>
+<span id="cb9-4"><a href="#cb9-4" aria-hidden="true" tabindex="-1"></a>    <span class="fu">reify</span>(<span class="st">&#39;e3&#39;</span>)<span class="op">.</span><span class="fu">withLocation</span>([<span class="dv">1</span><span class="op">,</span><span class="dv">5</span><span class="op">,</span><span class="dv">5</span>]<span class="op">,</span> [<span class="dv">1</span><span class="op">,</span><span class="dv">8</span><span class="op">,</span><span class="dv">8</span>])<span class="op">,</span></span>
+<span id="cb9-5"><a href="#cb9-5" aria-hidden="true" tabindex="-1"></a>    <span class="fu">reify</span>(<span class="st">&#39;g3&#39;</span>)<span class="op">.</span><span class="fu">withLocation</span>([<span class="dv">1</span><span class="op">,</span><span class="dv">8</span><span class="op">,</span><span class="dv">8</span>]<span class="op">,</span> [<span class="dv">1</span><span class="op">,</span><span class="dv">10</span><span class="op">,</span><span class="dv">10</span>])<span class="op">,</span></span>
+<span id="cb9-6"><a href="#cb9-6" aria-hidden="true" tabindex="-1"></a>  )<span class="op">.</span><span class="fu">fast</span>(<span class="dv">2</span>)</span>
+<span id="cb9-7"><a href="#cb9-7" aria-hidden="true" tabindex="-1"></a>)</span></code></pre></div>
+<h3 data-number="7.1.3" id="highlighting-locations"><span
+class="header-section-number">7.1.3</span> Highlighting Locations</h3>
+<p>As seen in the examples above, both the JS and the Mini Notation
+parser add source code locations using <code>withMiniLocation</code> and
+<code>withLocation</code> methods. While the JS parser adds locations
+relative to the user code as a whole, the Mini Notation adds locations
+relative to the position of the mini notation string. The absolute
+location of elements within Mini Notation can be calculated by simply
+adding both locations together. This absolute location can be used to
+highlight active events in real time.</p>
+<h2 data-number="7.2" id="scheduling-events"><span
+class="header-section-number">7.2</span> Scheduling Events</h2>
+<p>After an instance of <code>Pattern</code> is obtained from the user
+code, it is used by the scheduler to get queried for events. Once
+started, the scheduler runs at a fixed interval to query active pattern
+for events withing the current interval’s time span. A simplified
+implementation looks like this:</p>
+<div class="sourceCode" id="cb10"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb10-1"><a href="#cb10-1" aria-hidden="true" tabindex="-1"></a><span class="kw">let</span> pattern <span class="op">=</span> <span class="fu">seq</span>(<span class="st">&#39;c3&#39;</span><span class="op">,</span> [<span class="st">&#39;e3&#39;</span><span class="op">,</span> <span class="st">&#39;g3&#39;</span>])<span class="op">;</span> <span class="co">// pattern from user</span></span>
+<span id="cb10-2"><a href="#cb10-2" aria-hidden="true" tabindex="-1"></a><span class="kw">let</span> interval <span class="op">=</span> <span class="fl">0.5</span><span class="op">;</span> <span class="co">// query interval in seconds</span></span>
+<span id="cb10-3"><a href="#cb10-3" aria-hidden="true" tabindex="-1"></a><span class="kw">let</span> time <span class="op">=</span> <span class="dv">0</span><span class="op">;</span> <span class="co">// beginning of current time span</span></span>
+<span id="cb10-4"><a href="#cb10-4" aria-hidden="true" tabindex="-1"></a><span class="kw">let</span> minLatency <span class="op">=</span> <span class="op">.</span><span class="dv">1</span><span class="op">;</span> <span class="co">// min time before a hap should trigger</span></span>
+<span id="cb10-5"><a href="#cb10-5" aria-hidden="true" tabindex="-1"></a><span class="pp">setInterval</span>(() <span class="kw">=&gt;</span> {</span>
+<span id="cb10-6"><a href="#cb10-6" aria-hidden="true" tabindex="-1"></a>  <span class="kw">const</span> haps <span class="op">=</span> pattern<span class="op">.</span><span class="fu">queryArc</span>(time<span class="op">,</span> time <span class="op">+</span> interval)<span class="op">;</span></span>
+<span id="cb10-7"><a href="#cb10-7" aria-hidden="true" tabindex="-1"></a>  time <span class="op">+=</span> interval<span class="op">;</span> <span class="co">// increment time</span></span>
+<span id="cb10-8"><a href="#cb10-8" aria-hidden="true" tabindex="-1"></a>  haps<span class="op">.</span><span class="fu">forEach</span>((hap) <span class="kw">=&gt;</span> {</span>
+<span id="cb10-9"><a href="#cb10-9" aria-hidden="true" tabindex="-1"></a>    <span class="kw">const</span> deadline <span class="op">=</span> hap<span class="op">.</span><span class="at">whole</span><span class="op">.</span><span class="at">begin</span> <span class="op">-</span> time <span class="op">+</span> minLatency<span class="op">;</span></span>
+<span id="cb10-10"><a href="#cb10-10" aria-hidden="true" tabindex="-1"></a>    <span class="fu">onTrigger</span>(hap<span class="op">,</span> deadline<span class="op">,</span> duration)<span class="op">;</span></span>
+<span id="cb10-11"><a href="#cb10-11" aria-hidden="true" tabindex="-1"></a>  })<span class="op">;</span></span>
+<span id="cb10-12"><a href="#cb10-12" aria-hidden="true" tabindex="-1"></a>}<span class="op">,</span> interval <span class="op">*</span> <span class="dv">1000</span>)<span class="op">;</span> <span class="co">// query each &quot;interval&quot; seconds</span></span></code></pre></div>
+<p>Note that the above code is simplified for illustrative purposes. The
+actual implementation has to work around imprecise callbacks of
+<code>setInterval</code>. More about the implementation details can be
+read in <a
+href="https://loophole-letters.vercel.app/web-audio-scheduling">this
+blog post</a>.</p>
+<p>The fact that <code>Pattern.queryArc</code> is a pure function that
+maps a time span to a set of events allows us to choose any interval we
+like without changing the resulting output. It also means that when the
+pattern is changed from outside, the next scheduling callback will work
+with the new pattern, keeping its clock running.</p>
+<p>The latency between the time the pattern is evaluated and the change
+is heard is between <code>minLatency</code> and
+<code>interval + minLatency</code>, in our example between 100ms and
+600ms. In Strudel, the current query interval is 50ms with a minLatency
+of 100ms, meaning the latency is between 50ms and 150ms.</p>
+<h2 data-number="7.3" id="output"><span
+class="header-section-number">7.3</span> Output</h2>
+<p>The last step is to trigger each event in the chosen output. This is
+where the given time and value of each event is used to generate audio
+or any other form of time based output. The default output of the
+Strudel REPL is the WebAudio output. To understand what an output does,
+we first have to understand what control parameters are.</p>
+<h3 data-number="7.3.1" id="control-parameters"><span
+class="header-section-number">7.3.1</span> Control Parameters</h3>
+<p>To be able to manipulate multiple aspects of sound in parallel, so
+called control parameters are used to shape the value of each event.
+Example:</p>
+<div class="sourceCode" id="cb11"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb11-1"><a href="#cb11-1" aria-hidden="true" tabindex="-1"></a><span class="fu">note</span>(<span class="st">&quot;c3 e3&quot;</span>)<span class="op">.</span><span class="fu">cutoff</span>(<span class="dv">1000</span>)<span class="op">.</span><span class="fu">s</span>(<span class="st">&#39;sawtooth&#39;</span>)</span>
+<span id="cb11-2"><a href="#cb11-2" aria-hidden="true" tabindex="-1"></a>  <span class="op">.</span><span class="fu">queryArc</span>(<span class="dv">0</span><span class="op">,</span> <span class="dv">1</span>)<span class="op">.</span><span class="fu">map</span>(hap <span class="kw">=&gt;</span> hap<span class="op">.</span><span class="at">value</span>)</span>
+<span id="cb11-3"><a href="#cb11-3" aria-hidden="true" tabindex="-1"></a><span class="co">/* [</span></span>
+<span id="cb11-4"><a href="#cb11-4" aria-hidden="true" tabindex="-1"></a><span class="co">  { note: &#39;c3&#39;, cutoff: 1000, s: &#39;sawtooth&#39; }</span></span>
+<span id="cb11-5"><a href="#cb11-5" aria-hidden="true" tabindex="-1"></a><span class="co">  { note: &#39;e3&#39;, cutoff: 1000, s: &#39;sawtooth&#39; }</span></span>
+<span id="cb11-6"><a href="#cb11-6" aria-hidden="true" tabindex="-1"></a><span class="co">] */</span></span></code></pre></div>
+<p>Here, the control parameter functions <code>note</code>,
+<code>cutoff</code> and <code>s</code> are used, where each controls a
+different property in the value object. Each control parameter function
+accepts a primitive value, a list of values to be sequenced into a
+<code>Pattern</code>, or a <code>Pattern</code>. In the example,
+<code>note</code> gets a <code>Pattern</code> from a Mini Notation
+expression (double quoted), while <code>cutoff</code> and <code>s</code>
+are given a <code>Number</code> and a (single quoted)
+<code>String</code> respectively.</p>
+<p>Strudel comes with a large default set of control parameter functions
+that are based on the ones used by Tidal and SuperDirt, focusing on
+music and audio terminology. It is however possible to create custom
+control paramters for any purpose:</p>
+<div class="sourceCode" id="cb12"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb12-1"><a href="#cb12-1" aria-hidden="true" tabindex="-1"></a><span class="kw">const</span> { x<span class="op">,</span> y } <span class="op">=</span> <span class="fu">createParams</span>(<span class="st">&#39;x&#39;</span><span class="op">,</span> <span class="st">&#39;y&#39;</span>)</span>
+<span id="cb12-2"><a href="#cb12-2" aria-hidden="true" tabindex="-1"></a><span class="fu">x</span>(sine<span class="op">.</span><span class="fu">range</span>(<span class="dv">0</span><span class="op">,</span> <span class="dv">200</span>))<span class="op">.</span><span class="fu">y</span>(cosine<span class="op">.</span><span class="fu">range</span>(<span class="dv">0</span><span class="op">,</span><span class="dv">200</span>))</span></code></pre></div>
+<p>This example creates the custom control parameters <code>x</code> and
+<code>y</code> which are then used to form a pattern that descibes the
+coordinates of a circle.</p>
+<h3 data-number="7.3.2" id="outputs"><span
+class="header-section-number">7.3.2</span> Outputs</h3>
+<p>Now that we know how the value of an event is manipulated using
+control parameters, we can look at how outputs can use that value to
+generate anything. The scheduler above was calling the
+<code>onTrigger</code> function which is used to implement the output. A
+very simple version of the web audio output could look like this:</p>
+<div class="sourceCode" id="cb13"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb13-1"><a href="#cb13-1" aria-hidden="true" tabindex="-1"></a><span class="kw">function</span> <span class="fu">onTrigger</span>(hap<span class="op">,</span> deadline<span class="op">,</span> duration) {</span>
+<span id="cb13-2"><a href="#cb13-2" aria-hidden="true" tabindex="-1"></a>  <span class="kw">const</span> { note } <span class="op">=</span> hap<span class="op">.</span><span class="at">value</span><span class="op">;</span></span>
+<span id="cb13-3"><a href="#cb13-3" aria-hidden="true" tabindex="-1"></a>  <span class="kw">const</span> time <span class="op">=</span> <span class="fu">getAudioContext</span>()<span class="op">.</span><span class="at">currentTime</span> <span class="op">+</span> deadline<span class="op">;</span></span>
+<span id="cb13-4"><a href="#cb13-4" aria-hidden="true" tabindex="-1"></a>  <span class="kw">const</span> o <span class="op">=</span> <span class="fu">getAudioContext</span>()<span class="op">.</span><span class="fu">createOscillator</span>()<span class="op">;</span></span>
+<span id="cb13-5"><a href="#cb13-5" aria-hidden="true" tabindex="-1"></a>  o<span class="op">.</span><span class="at">frequency</span><span class="op">.</span><span class="at">value</span> <span class="op">=</span> <span class="fu">getFreq</span>(note)<span class="op">;</span></span>
+<span id="cb13-6"><a href="#cb13-6" aria-hidden="true" tabindex="-1"></a>  o<span class="op">.</span><span class="fu">start</span>(time)<span class="op">;</span></span>
+<span id="cb13-7"><a href="#cb13-7" aria-hidden="true" tabindex="-1"></a>  o<span class="op">.</span><span class="fu">stop</span>(time <span class="op">+</span> <span class="bu">event</span><span class="op">.</span><span class="at">duration</span>)<span class="op">;</span></span>
+<span id="cb13-8"><a href="#cb13-8" aria-hidden="true" tabindex="-1"></a>  o<span class="op">.</span><span class="fu">connect</span>(<span class="fu">getAudioContext</span>()<span class="op">.</span><span class="at">destination</span>)<span class="op">;</span></span>
+<span id="cb13-9"><a href="#cb13-9" aria-hidden="true" tabindex="-1"></a>}</span></code></pre></div>
+<p>The above example will create an <code>OscillatorNode</code> for each
+event, where the frequency is controlled by the <code>note</code> param.
+In essence, this is how the WebAudio API output of Strudel works, only
+with many more parameters to control synths, samples and effects.</p>
+<h1 data-number="8" id="pattern-alignment-and-combination"><span
+class="header-section-number">8</span> Pattern alignment and
+combination</h1>
+<p>One core aspect of Strudel, inherited from Tidal, is the flexible way
+that patterns can be combined, irrespective of their structure. Its
+declarative approach means a live coder does not have to think about the
+details of <em>how</em> this is done, only <em>what</em> is to be
+done.</p>
+<p>As a simple example, consider two number patterns
+<code>"0 [1 2] 3"</code>, and <code>"10 20"</code>. The first has three
+contiguous steps of equal lengths, with the second step broken down into
+two substeps, giving four events in total. There are a very large number
+of ways in which the structure of these two patterns could be combined,
+but the default method in both Strudel and Tidal is to line up the
+cycles of the two patterns, and then take events from the first pattern
+and match them with those in the second pattern. Therefore, the
+following two lines are equivalent:</p>
+<div class="sourceCode" id="cb14"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb14-1"><a href="#cb14-1" aria-hidden="true" tabindex="-1"></a><span class="st">&quot;0 [1 2] 3&quot;</span><span class="op">.</span><span class="fu">add</span>(<span class="st">&quot;10 20&quot;</span>)</span>
+<span id="cb14-2"><a href="#cb14-2" aria-hidden="true" tabindex="-1"></a><span class="st">&quot;10 [11 22] 23&quot;</span></span></code></pre></div>
+<p>Where the events only partially overlap, they are treated as
+fragments of the event in the first pattern. This is a little difficult
+to conceptualise, but lets start by comparing the two patterns in the
+following example:</p>
+<div class="sourceCode" id="cb15"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb15-1"><a href="#cb15-1" aria-hidden="true" tabindex="-1"></a><span class="st">&quot;0 1 2&quot;</span><span class="op">.</span><span class="fu">add</span>(<span class="st">&quot;10 20&quot;</span>)</span>
+<span id="cb15-2"><a href="#cb15-2" aria-hidden="true" tabindex="-1"></a><span class="st">&quot;10 [11 21] 20&quot;</span></span></code></pre></div>
+<p>They are similar to the previous example in that the number
+<code>1</code> is split in two, with its two halves added to
+<code>10</code> and <code>20</code> respectively. However, the
+<code>11</code> ‘remembers’ that it is a fragment of that original
+<code>1</code> event, and so is treated as having a duration of a third
+of a cycle, despite only being active for a sixth of a cycle. Likewise,
+the <code>21</code> is also a fragment of that original <code>1</code>
+event, but a fragment of its second half. Because the start of its event
+is missing, it wouldn’t actually trigger a sound (unless it underwent
+further pattern transformations/combinations).</p>
+<p>In practice, the effect of this default, implicit method for
+combining two patterns is that the second pattern is added <em>in</em>
+to the first one, and indeed this can be made explicit:</p>
+<div class="sourceCode" id="cb16"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb16-1"><a href="#cb16-1" aria-hidden="true" tabindex="-1"></a><span class="st">&quot;0 1 2&quot;</span><span class="op">.</span><span class="at">add</span><span class="op">.</span><span class="fu">in</span>(<span class="st">&quot;10 20&quot;</span>)</span></code></pre></div>
+<p>This makes way for other ways to align the pattern, and several are
+already defined, in particular:</p>
+<ul>
+<li><code>in</code> - as explained above, aligns cycles, and applies
+values from the pattern on the right <em>in</em> to the pattern on the
+left.</li>
+<li><code>out</code> - as with <code>in</code>, but values are applied
+<em>out</em> of the pattern on the left (i.e. <em>in</em> to the one on
+the right).</li>
+<li><code>mix</code> - structures from both patterns are combined, so
+that the new events are not fragments but are created at intersections
+of events from both sides.</li>
+<li><code>squeeze</code> - cycles from the pattern on the right are
+squeezed into events on the left. So that
+e.g. <code>"0 1 2".add.squeeze("10 20")</code> is equivalent to
+<code>"[10 20] [11 21] [12 22]"</code>.</li>
+<li><code>squeezeout</code> - as with <code>squeeze</code>, but cycles
+from the left are squeezed into events on the right. So,
+<code>"0 1 2".add.squeezeout("10 20")</code> is equivalent to
+<code>[10 11 12] [20 21 22]</code>.</li>
+<li><code>trig</code> is similar to <code>squeezeout</code> in that
+cycles from the right are aligned with events on the left. However those
+cycles are not ‘squeezed’, rather they are truncated to fit the event.
+So <code>"0 1 2 3 4 5 6 7".add.trig("10 [20 30]")</code> would be
+equivalent to <code>10 11 12 13 20 21 30 31</code>. In effect, events on
+the right ‘trigger’ cycles on the left.</li>
+<li><code>trigzero</code> is similar to <code>trig</code>, but the
+pattern is ‘triggered’ from its very first cycle, rather than from the
+current cycle. <code>trig</code> and <code>trigzero</code> therefore
+only give different results where the leftmost pattern differs from one
+cycle to the next.</li>
+</ul>
+<p>We will save going deeper into the background, design and
+practicalities of these alignment functions for future publications.
+However in the next section, we take them as a case study for looking at
+the different design affordances offered by Haskell to Tidal, and
+JavaScript to Strudel.</p>
+<h1 data-number="9" id="comparing-strudel-and-haskell-in-use"><span
+class="header-section-number">9</span> Comparing Strudel and Haskell in
+use</h1>
+<p>Unlike Haskell, JavaScript lacks the ability to define custom infix
+operators, or change the meaning of existing ones. So the above Strudel
+example of <code>"0 1 2".add.out("10 20")</code> is equivalent to the
+Tidal expression <code>"0 1 2" +| "10 20"</code>, where the vertical bar
+in the operator <code>+|</code> stands for <code>out</code> (where
+<code>a |+ b</code> would be equivalent of
+<code>a.add.in(b)</code>).</p>
+<p>From this we can already see that Tidal tends towards brevity through
+mixing infix operators with functions, and Strudel tends towards
+spelling out operations which are joined together with the
+<code>.</code> operator. This then is the design trade-off of Tidal’s
+tersity, versus Strudel’s simplicity.</p>
+<p>To demonstrate this, consider the following Tidal pattern:</p>
+<pre class="tidal"><code>iter 4 $ every 3 (||+ n &quot;10 20&quot;) $ (n &quot;0 1 3&quot;) # s &quot;triangle&quot; # crush 4</code></pre>
+<p>This can be directly translated to the Strudel equivalent:</p>
+<div class="sourceCode" id="cb18"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb18-1"><a href="#cb18-1" aria-hidden="true" tabindex="-1"></a><span class="fu">iter</span>(<span class="dv">4</span><span class="op">,</span> <span class="fu">every</span>(<span class="dv">3</span><span class="op">,</span> add<span class="op">.</span><span class="fu">squeeze</span>(<span class="st">&quot;10 20&quot;</span>)<span class="op">,</span> <span class="fu">n</span>(<span class="st">&quot;0 1 3&quot;</span>)<span class="op">.</span><span class="fu">s</span>(<span class="st">&quot;triangle&quot;</span>)<span class="op">.</span><span class="fu">crush</span>(<span class="dv">4</span>)))</span></code></pre></div>
+<p>Although for a more canonical Strudel expression, we would reorder it
+as:</p>
+<div class="sourceCode" id="cb19"><pre
+class="sourceCode js"><code class="sourceCode javascript"><span id="cb19-1"><a href="#cb19-1" aria-hidden="true" tabindex="-1"></a><span class="fu">n</span>(<span class="st">&quot;0 1 3&quot;</span>)<span class="op">.</span><span class="fu">every</span>(<span class="dv">3</span><span class="op">,</span> add<span class="op">.</span><span class="fu">squeeze</span>(<span class="st">&quot;10 20&quot;</span>))<span class="op">.</span><span class="fu">iter</span>(<span class="dv">4</span>)<span class="op">.</span><span class="fu">s</span>(<span class="st">&quot;triangle&quot;</span>)<span class="op">.</span><span class="fu">crush</span>(<span class="dv">4</span>)</span></code></pre></div>
+<p>The Strudel example uses the <code>.</code> method call operator for
+all operations and combinations, whereas the Tidal example has
+<code>#</code> for the default method for combining patterns and uses
+infix operators for other methods. The lack of parenthesis in the Tidal
+example is partly due to the way that arguments are applied to Haskell’s
+functions, and partly due to the use of the <code>$</code> operator as
+an alternative way to establish precedence and control the order of
+evaluation.</p>
+<p>Considering the above, we argue that the Haskell syntax is a little
+cleaner, but that the Strudel syntax is easier to learn. Our informal
+observation is that while Haskell’s dollar <code>$</code> operator is
+very useful in making code easier to work with, it is one of the most
+difficult aspects of Tidal use for beginners to learn. On the other
+hand, the deeper levels of parenthesis in Strudel code can be difficult
+to keep track of, especially while coding under pressure of live musical
+performance. However this difficulty can be largely be mitigated by
+reordering expressions, and further mitigated by supporting editor
+features.</p>
+<p>With Strudel, we have little choice but to embrace the affordances
+and constraints offered by JavaScript, and while designing a
+domain-specific language entirely based on method calls is a challenge,
+through creative adoption of functional programming techniques like
+partial application, we are so far very happy with the results. Tidal’s
+functional reactive approach to pattern-making has in general translated
+well to JavaScript, and opportunities and constraints have overall
+traded off to create a very approachable and useable live coding
+environment.</p>
+<h2 data-number="9.1" id="the-trade-off-of-flexible-typing"><span
+class="header-section-number">9.1</span> The trade-off of flexible
+typing</h2>
+<p>We have identified one problem with porting Tidal to JavaScript where
+we have missed Haskell’s strict typing and type inference. In both Tidal
+and Strudel, time is rational, where any point in time is represented as
+the ratio of two integers. This allows representation of musical ratios
+such that are impossible to represent accurately using the more common
+floating point numbers. However while libraries are available that
+support rational numbers in JavaScript, the lack of strict typing means
+that it is easy to implement pattern methods where computationally
+expensive conversion from floating point to rational numbers are
+performed late, and therefore often enough to overload the CPUs, due to
+the large number of iterative calculations required to estimate a ratio
+for a given floating point number. To mitigate this problem, we might
+consider moving to TypeScript in the future.</p>
+<h1 data-number="10" id="future-outlook"><span
+class="header-section-number">10</span> Future Outlook</h1>
+<p>The project is still young, with many features on the horizon. As
+general guiding principles, Strudel aims to be</p>
+<ol type="1">
+<li>accessible</li>
+<li>consistent with Tidal’s approach to pattern</li>
+<li>modular and extensible</li>
+</ol>
+<p>While Haskell’s type system makes it a great language for the ongoing
+development of Tidal’s inner representation of pattern, JavaScript’s
+vibrant ecosystem, flexibility and accessibility makes it a great host
+for more ad-hoc experiments, including interface design. For the future,
+it is planned to integrate additional alternative sound engines such as
+Glicol <span class="citation" data-cites="lanChaosprintGlicol2022">(Lan
+[2020] 2022)</span> and Faust <span class="citation"
+data-cites="FaustProgrammingLanguage2022">(<em>Faust - Programming
+Language for Audio Applications and Plugins</em> [2016] 2022)</span>.
+Strudel is already approaching feature parity with Tidal, but there are
+more Tidal functions to be ported, and work to be done to improve
+compatibility with Tidal’s mininotation. Tidal version 2.0 is under
+development, which brings a new representation for sequences to its
+patterns, which will then be brought to Strudel. Besides sound, other
+ways to render events are being explored, such as graphical, and
+choreographic output. We are also looking into alternative ways of
+editing patterns, including multi-user editing for network music,
+parsing a novel syntax to escape the constraints of javascript, and
+developing hardware/e-textile interfaces. In summary, there is a lot of
+fun ahead.</p>
+<h1 data-number="11" id="links"><span
+class="header-section-number">11</span> Links</h1>
+<p>The Strudel REPL is available at <a
+href="https://strudel.tidalcycles.org"
+class="uri">https://strudel.tidalcycles.org</a>, including an
+interactive tutorial. The repository is at <a
+href="https://github.com/tidalcycles/strudel"
+class="uri">https://github.com/tidalcycles/strudel</a>, all the code is
+open source under the AGPL-3.0 License.</p>
+<h1 data-number="12" id="acknowledgments"><span
+class="header-section-number">12</span> Acknowledgments</h1>
+<p>Thanks to the Strudel and wider Tidal, live coding, WebAudio and
+free/open source software communities for inspiration and support. Alex
+McLean’s work on this project is supported by a UKRI Future Leaders
+Fellowship [grant number MR/V025260/1].</p>
+<h1 class="unnumbered" id="references">References</h1>
+<div id="refs" class="references csl-bib-body hanging-indent"
+role="doc-bibliography">
+<div id="ref-FaustProgrammingLanguage2022" class="csl-entry"
+role="doc-biblioentry">
+<em>Faust - Programming Language for Audio Applications and
+Plugins</em>. (2016) 2022. C++. GRAME. <a
+href="https://github.com/grame-cncm/faust">https://github.com/grame-cncm/faust</a>.
+</div>
+<div id="ref-jackHydra2022" class="csl-entry" role="doc-biblioentry">
+Jack, Olivia. (2022) 2022. <em>Hydra</em>. <a
+href="https://github.com/ojack/hydra">https://github.com/ojack/hydra</a>.
+</div>
+<div id="ref-lanChaosprintGlicol2022" class="csl-entry"
+role="doc-biblioentry">
+Lan, Qichao. (2020) 2022. <em>Chaosprint/Glicol</em>. Rust. <a
+href="https://github.com/chaosprint/glicol">https://github.com/chaosprint/glicol</a>.
+</div>
+<div id="ref-mcleanAlgorithmicPattern2020a" class="csl-entry"
+role="doc-biblioentry">
+Mclean, Alex. 2020. <span>“Algorithmic Pattern.”</span> In
+<em>Proceedings of the International Conference on New Interfaces for
+Musical Expression</em>, 265--270. Birmingham, UK. <a
+href="https://zenodo.org/record/4813352">https://zenodo.org/record/4813352</a>.
+</div>
+<div id="ref-mcleanFeedforward2020" class="csl-entry"
+role="doc-biblioentry">
+McLean, Alex. 2020. <span>“Feedforward.”</span> In <em>Proceedings of
+New Interfaces for Musical Expression</em>. Birmingham. <a
+href="https://zenodo.org/record/6353969">https://zenodo.org/record/6353969</a>.
+</div>
+<div id="ref-mcleanTidalVortexZero2022" class="csl-entry"
+role="doc-biblioentry">
+McLean, Alex, Raphaël Forment, Sylvain Le Beux, and Damián Silvani.
+2022. <span>“TidalVortex Zero.”</span> In <em>Proceedings of the 7th
+International Conference on Live Coding</em>. Limerick, Ireland: Zenodo.
+<a
+href="https://doi.org/10.5281/zenodo.6456380">https://doi.org/10.5281/zenodo.6456380</a>.
+</div>
+<div id="ref-ogbornDktr0WebDirt2022" class="csl-entry"
+role="doc-biblioentry">
+Ogborn, David. (2016) 2022. <em>Dktr0/WebDirt</em>. JavaScript. <a
+href="https://github.com/dktr0/WebDirt">https://github.com/dktr0/WebDirt</a>.
+</div>
+<div id="ref-ogbornEstuaryBrowserbasedCollaborative2017"
+class="csl-entry" role="doc-biblioentry">
+Ogborn, David, Jamie Beverley, Luis Navarro del Angel, Eldad Tsabary,
+and Alex McLean. 2017. <span>“Estuary: Browser-Based Collaborative
+Projectional Live Coding of Musical Patterns.”</span> In <em>Proceedings
+of the International Conference on Live Coding</em>, 11. Morelia.
+</div>
+<div id="ref-robertsGibberLiveCoding2012" class="csl-entry"
+role="doc-biblioentry">
+Roberts, Charles, and Joann Kuchera-morin. 2012. <span>“Gibber: Live
+Coding Audio in the Browser.”</span> In <em>In Proceedings of the 2012
+International Computer Music Conference</em>.
+</div>
+<div id="ref-StrudelWAC2022" class="csl-entry" role="doc-biblioentry">
+Roos, Felix, and Alex McLean. 2022. <span>“Strudel: Algorithmic Patterns
+for the Web.”</span> In. Zenodo. <a
+href="https://doi.org/10.5281/zenodo.6768844">https://doi.org/10.5281/zenodo.6768844</a>.
+</div>
+<div id="ref-solomonPurescriptocarina2022" class="csl-entry"
+role="doc-biblioentry">
+Solomon, Mike. (2021) 2022. <em>Purescript-Ocarina</em>. PureScript. <a
+href="https://github.com/mikesol/purescript-ocarina">https://github.com/mikesol/purescript-ocarina</a>.
+</div>
+<div id="ref-SuperDirt2022" class="csl-entry" role="doc-biblioentry">
+<em>SuperDirt</em>. (2015) 2022. SuperCollider. musikinformatik. <a
+href="https://github.com/musikinformatik/SuperDirt">https://github.com/musikinformatik/SuperDirt</a>.
+</div>
+<div id="ref-toussaintEuclideanAlgorithmGenerates2005" class="csl-entry"
+role="doc-biblioentry">
+Toussaint, Godfried. 2005. <span>“The Euclidean Algorithm Generates
+Traditional Musical Rhythms.”</span> In <em>In Proceedings of BRIDGES:
+Mathematical Connections in Art, Music and Science</em>, 47–56. <a
+href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.62.231">http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.62.231</a>.
+</div>
+<div id="ref-CsoundWebAssembly" class="csl-entry"
+role="doc-biblioentry">
+Yi, Steven, Victor Lazzarini, and Edward Costello. 2018.
+<span>“WebAssembly AudioWorklet Csound.”</span> In. Berlin, Germany. <a
+href="https://mural.maynoothuniversity.ie/16018/">https://mural.maynoothuniversity.ie/16018/</a>.
+</div>
+</div>
+</body>
+</html>
@@ -8,7 +8,7 @@ author:
    affiliation: Then Try This
    email: alex@slab.org
 abstract: |
-  This paper introduces Strudel, which faithfully ports the TidalCycles approach to live coding algorithmic patterns to native JavaScript and the web. We begin by giving a little background of the first year of development, before sharing some detail about its implementation and examples of use. We go on to outline the wide range of synthesis and other outputs available in Strudel, including WebAudio, MIDI, OSC (for SuperDirt), WebSerial and CSound, and introduce Strudel's REPL live editor, including its built-in visualisations. We then compare Strudel with Tidal, the trade-offs involved between JavaScript and Haskell, and the unique capabilities offered by Strudel for aligning patterns, before concluding with some thoughts about the future.
+  This paper introduces Strudel, which brings the TidalCycles approach to live coding algorithmic patterns to native JavaScript and the web. We begin by giving a little background of the first year of development, before sharing some detail about its implementation and examples of use. We go on to outline the wide range of synthesis and other outputs available in Strudel, including WebAudio, MIDI, OSC (for SuperDirt), WebSerial and CSound, and introduce Strudel's REPL live editor, including its built-in visualisations. We then compare Strudel with Tidal, the trade-offs involved between JavaScript and Haskell, and the unique capabilities offered by Strudel for aligning patterns, before concluding with some thoughts about the future.
 bibliography: citations.json
 fontsize: 11pt
 geometry: margin=2cm
@@ -23,36 +23,37 @@ date: '2022-12-14'

 In the following paper, we introduce *Strudel*, an alternative
 implementation of the TidalCycles (or 'Tidal' for short) live coding
-system. Whereas Tidal is implemented in the pure functional Haskell programming language, Strudel brings it to the multi-paradigm, web-centric JavaScript language. Strudel is an
+system, using the JavaScript programming language. Strudel is an
 attempt to make live coding more accessible, by creating a system that
-can run entirely in the browser, while opening Tidal's approach to
-algorithmic patterns [@mcleanAlgorithmicPattern2020] up to modern
+runs entirely in the browser, while opening Tidal's approach to
+algorithmic patterns [@mcleanAlgorithmicPattern2020a] up to modern
 audio/visual web technologies. The Strudel REPL is a live code editor
 dedicated to manipulating patterns while they play, with builtin
-visual feedback. While Strudel is written in standard JavaScript, it does support some optimisations for simplicity, readability and editability by applying code
+visual feedback. While Strudel is written in JavaScript, the API is
+optimized for simplicity and readability by applying code
 transformations on the syntax tree level, allowing language operations
 that would otherwise be impossible. The application supports multiple
 ways to output sound, including Tone.js, Web Audio Nodes, OSC (Open
 Sound Control) messages, Web Serial, Web MIDI and Csound. The project
 is split into multiple packages, allowing granular reuse in other
 applications. Apart from TidalCycles, Strudel draws inspiration from
-several other existing projects like TidalVortex
+many prior existing projects like TidalVortex
 [@mcleanTidalVortexZero2022], Gibber [@robertsGibberLiveCoding2012],
 Estuary [@ogbornEstuaryBrowserbasedCollaborative2017], Hydra
-[@jackHydra2023], Ocarina [@solomonPurescriptocarina2022] and
-Feedforward [@mcleanFeedforward2020]. This paper builds upon a 
-demo paper presented at Web Audio Conference 2022 [@roosStrudelAlgorithmicPatterns2022].
+[@jackHydra2022], Ocarina [@solomonPurescriptocarina2022] and
+Feedforward [@mcleanFeedforward2020]. This paper expands the Strudel
+Demo paper for the Web Audio Conference 2022 [@StrudelWAC2022].

 The first tentative commit to the Strudel project was on 22nd January
 2022 by Alex McLean, with the core representation implemented over the
 following few days. Although this was his first attempt at a
 JavaScript-based application, by 27th January, Alex had managed to
-upload an initial version to the 'npm' JavaScript package database,
+upload the initial version to the 'npm' javascript package database,
 sharing with the wider community for comment. By 4th February, Felix
 Roos had discovered Strudel and contributed a 'REPL' user interface to
-it, and a scheduler the following day, so that Strudel
-could already begin to make sound.  At this point, Alex and Felix shared
-ownership of the repository, and the project has since proved to be a
+it, and then contributed a scheduler the next day, so that Strudel
+could already make sound.  At this point, Alex and Felix shared
+ownership to the repository, and the project has since proved to be a
 productive confluence of Felix's own work into music representation
 and visualisation, with Alex's experience with making Tidal. Felix has
 since become the primary contributor to Strudel, with Alex continuing
@@ -60,24 +61,24 @@ to jump between developing both Strudel and Tidal. Aspects of
 Strudel's development have therefore fed back into TidalCycles, and
 both systems have maintained a shared conceptual underpinning. We plan
 to continue working towards feature parity between these systems,
-although within the different syntactical trade-offs and library ecosystems of
+although within the syntactical trade-offs and library ecosystems of
 JavaScript and Haskell, some divergence is inevitable and healthy.

-Now celebrating the first year of its life, Strudel is now a fully-fledged live
-coding environment, porting Tidal's core representation of patterns,
+Over the first year of its life, Strudel is now a fully-fledged live
+coding environment, porting Tidal's core represention of patterns,
 pattern transformations, and mini-notation for polymetric sequences,
 combined with a wealth of features for synthesising and visualising
 those patterns.

 # From Tidal to Strudel and back

-As mentioned earlier, the original Tidal is implemented as a domain specific language (DSL) embedded in the Haskell pure functional programming language, and takes advantage of Haskell's terse syntax and advanced, 'strong' type system. JavaScript on the other hand, is a multi-paradigm programming language, with a dynamic type system. Because Tidal leans heavily on many of Haskell's more unique features, it was not always clear that it could meaningfully be ported to a multi-paradigm scripting language. However, this possibility was already demonstrated with an earlier port to Python [TidalVortex; @mcleanTidalVortexZero2022], and we have now successfully implemented Tidal's pure functional representation of patterns in Strudel, including partial application, currying, and the functor, applicative and monadic structures that underlie Tidal's expressive pattern transformations. The result is a terse and highly composable system, where everything is either a pattern, or a function for combining and manipulating patterns, offering a rich creative ground for exploration.
+As mentioned above, the original Tidal is implemented as a domain specific language (DSL) embedded in the Haskell pure functional programming language, and takes advantage of Haskell's terse syntax and advanced, 'strong' type system. JavaScript on the other hand, is a multi-paradigm programming language, with a dynamic type system. Because Tidal leans heavily on many of Haskell's more unique features, it was not always clear that it could meaningfully be ported to a multi-paradigm scripting language. However, this possibility was already demonstrated with an earlier port to Python [TidalVortex; @mcleanTidalVortexZero2022], and we have now successfully implemented Tidal's pure functional representation of patterns in Strudel, including partial application, currying, and the functor, applicative and monadic structures that underlie Tidal's expressive pattern transformations. The result is a terse and highly composable system, where everything is either a pattern, or a function for combining and manipulating patterns, offering a rich creative ground for exploration.

 This development process has been far from a one-way port, however. The process of porting Tidal's concepts has also opened up new possibilities, some just from revisiting every design decision, and some from the particular affordances and constraints offered by JavaScript. This has lead to new features (and indeed bugfixes) that have found their way back to Tidal where appropriate, and ongoing work that we will return to in the conclusion of this paper.

 # Representing Patterns

-Patterns are the essence of Tidal. Its patterns are abstract entities that represent flows of time as functions, adapting a technique called pure functional reactive programming. Taking a time span as its input, a Pattern will output a set of events that happen within that time span. It depends on the structure of the Pattern how the events are located in time.
+Patterns are the essence of Tidal. Its patterns are abstract entities that represent flows of time as functions, adapting a technique called pure functional reactive programming. Taking a time span as its input, a Pattern can output a set of events that happen within that time span. It depends on the structure of the Pattern how the events are located in time.
 From now on, this process of generating events from a time span will be called **querying**.
 Example:

@@ -100,7 +101,7 @@ The resulting events are:

 Each event has a value, a begin time and an end time, where time is represented as a fraction. In the above case, the events are placed in sequential order, where c3 takes the first half, and e3 and g3 together take the second half. This temporal placement is the result of the `sequence` function, which divides its arguments equally over one cycle. If an argument is an array, the same rule applies to that part of the cycle. In the example, e3 and g3 are divided equally over the second half of the whole cycle.

-Note that the query function is not just a way to access a pattern, but true to the principles of functional programming, is the pattern itself. This means that in theory there is no way to change a pattern, it is opaque as a pure function. In practice though, Strudel and Tidal are all about transforming patterns, so how is this done? The answer is, by replacing the pattern with a new one, that calls the old one. This new function is only able to manipulate the query before passing it to the old pattern, and manipulate the results from it before returning them to caller. But, this is enough to support all the temporal and structural manipulations provided by Strudel (and Tidal's) extensive library of functions.
+Note that the query function is not just a way to access a pattern, but true to the principles of functional programming, is the pattern itself. This means that in theory there is no way to change a pattern, it is opaque as a pure function. In practice though, Strudel and Tidal are all about transforming patterns, so how is this done? The answer is, by replacing the pattern with a new one, that calls the old one. This new one is only able to manipulate the query before passing it to the old pattern, and manipulate the results from it before returning them to caller. But, this is enough to support all the temporal and structural manipulations provided by Strudel (and Tidal's) extensive library of functions.

 The above examples do not represent how Strudel is used in practice. In the live coding editor, the user only has to type in the pattern itself, the querying will be handled by the scheduler. The scheduler will repeatedly query the pattern for events, which are then scheduled as sound synthesis or other event triggers.
 Also, the above event data structure has been simplified for readability.
@@ -109,7 +110,7 @@ Also, the above event data structure has been simplified for readability.

 # Making Patterns

-In practice, the end-user live coder will not deal with constructing patterns directly, but will rather build patterns using Strudel's extensive combinator library, to create, combine and transform patterns.
+In practice, the end-user live coder will not deal with constructing patterns directly, but will rather build patterns using Strudel's extensive combinator library to create, combine and transform patterns.

 The live coder will rarely use the `sequence` function as seen above, as sequencing is implicit in many functions. For example in the following, the `note` function constructs a pattern of notes, sequencing its arguments in the same manner as the previous example.

@@ -117,29 +118,29 @@ The live coder will rarely use the `sequence` function as seen above, as sequenc
 note(c3, [e3, g3])
 ```

-Perhaps more often, they will use the mini-notation for even terser notation of rhythmic sequences: ^[This example is also valid Tidal code, albeit the parenthesis is not required in its Haskell syntax in this case. Tidal does not support passing sequences as lists directly to the `note` function, however.].
+Perhaps more often, they will use the mini-notation for even terser notation of rhythmic sequences: ^[This last example is also valid Tidal code, albeit the parenthesis is not required in its Haskell syntax in this case. Tidal does not support passing sequences as lists directly to the `note` function, however.].

 ```js
 note("c3 [e3 g3]")
 ```

-Such sequences are often treated only as a starting point for manipulation, where functions are then applied which represent pattern transformations such as repetition, symmetry, interference/combination or randomisation, potentially at multiple timescales. Because Strudel patterns are represented as pure functions of time rather than as data structures, very long and complex generative results can be represented and manipulated without having to store the resulting sequences in memory.
+Such sequences are often treated only as a starting point for manipulation, where they then undergo pattern transformations such as repetition, symmetry, interference/combination or randomisation, potentially at multiple timescales. Because Strudel patterns are represented as pure functions of time rather than as data structures, very long and complex generative results can be represented and manipulated without having to store the resulting sequences in memory.

 # Pattern Example

-The following example showcases how patterns can be utilised to create musical complexity from simple parts, using repetition and interference:
+The following example showcases how patterns can be utilized to create musical complexity from simple parts, using repetition and interference:

 ```js
 "<0 2 [4 6](3,4,1) 3>"
 .off(1/4, add(2))
 .off(1/2, add(6))
-.scale('D3 minor')
-.note().s("sawtooth square")
+.scale('D minor')
 .legato(.25)
+.note().s("sawtooth square")
 .delay(.8).delaytime(.125)
 ```

-The pattern starts with a rhythmic pattern of numbers expressed in mini-notation, which are later interpreted inside the scale of D minor.
+The pattern starts with a rhythm of numbers in mini-notation, which are later interpreted inside the scale of D minor.
 The first line could also be expressed without mini-notation:

 ```js
@@ -152,16 +153,16 @@ These numbers then undergo various pattern transformations. Here is a short desc
 - `brackets`: elements inside brackets are divided equally over the time of their parent
 - `.euclid(p, s, o)`: place p pulses evenly over s steps, with offset o [@toussaintEuclideanAlgorithmGenerates2005]
 - `.off(n, f)`: layers a pattern on top of itself, with the new layer offset by n cycles, and with function f applied
- `.scale(name)`: interpretes numbers as indices inside the given scale
- `.note()`: interprets values as notes
- `.s(name)`: play back each event with the given sound
 - `.legato(n)`: multiply the duration of all events in a pattern by a factor of n
- `.delay(amount)`: delay effect send amount
+- `.echo(t, n, v)`: copy each event t times, with n cycles in between each copy, decreasing velocity by v
+- `.note()`: interpretes values as notes
+- `.s(name)`: play back each event with the given sound
+- `.delay(wet)`: add delay
 - `.delaytime(t)`: set delay time

 Much of the above will be familiar to Tidal users.

-<!-- This example shows some of Strudel's unique support for chords and transposition familiar to students of Western music theory. This differs a little from Tidal's approach and thanks to the integration of the JavaScript library XXX (*TODO* ? or is this all your work Felix?), Strudel's support for tonal transformations such as voice leading is perhaps respects more advanced than Tidal. -->
+<!-- This example shows some of Strudel's unique support for chords and transposition familiar to students of Western music theory. This differs a little from Tidal's approach and thanks to the integration of the javascript library XXX (*TODO* ? or is this all your work Felix?), Strudel's support for tonal transformations such as voice leading is perhaps respects more advanced than Tidal. -->

 # Ways to make Sound (and other events)

@@ -180,11 +181,11 @@ While the Web Audio API takes a *fire-and-forget* approach, creating a lot of To

 Strudel's new default output uses the Web Audio API to create a new audio graph for each event. It currently supports basic oscillators, sample playback, various effects and an experimental support for soundfonts.

-WebDirt [@ogbornWebDirt2022] was created as part of the Estuary Live Coding System [@ogbornEstuaryBrowserbasedCollaborative2017], and proved to be a solid choice for handling samples in Strudel as well. We are however focused on working more directly with the Web Audio API to be able to integrate new features more tightly.
+WebDirt [@ogbornDktr0WebDirt2022] was created as part of the Estuary Live Coding System [@ogbornEstuaryBrowserbasedCollaborative2017], and proved to be a solid choice for handling samples in Strudel as well. We are however focused on working more directly with the Web Audio API to be able to integrate new features more tightly.

-Using the OSC protocol via Strudel's provided Node.js-based OSC proxy server, it is possible to send network messages to trigger events. This is mainly used to render sound using SuperDirt [@rohrhuberSuperDirt2022], which is the well-developed Supercollider-based synthesis framework used by Tidal live coders as standard.
+Using the OSC protocol via Strudel's provided Node.js-based OSC proxy server, it is possible to send network messages to trigger events. This is mainly used to render sound using SuperDirt [@SuperDirt2022], which is the well-developed Supercollider-based synthesis framework that Tidal live coders generally use as standard.

-Recently, the experimental integration of Csound proved to bring a new dimension of sound design capabilities to Strudel. Thanks to the WebAssembly distribution of this classic system [@yiWebAssemblyAudioWorkletCsound2018], Csound 'orchestra' synthesisers can be embedded in and then patterned with Strudel code.
+Recently, the experimental integration of Csound proved to bring a new dimension of sound design capabilities to Strudel. Thanks to the WebAssembly distribution of this classic system [@CsoundWebAssembly], Csound 'orchestra' synthesisers can be embedded in and then patterned with Strudel code.

 MIDI output can also be used to send MIDI messages to either external instruments or to other programs on the same device. Unlike OSC, Strudel is able to send MIDI directly without requiring additional proxy software, but only from web browsers that support it (at the time of writing, this means Chromium-based browsers).

@@ -230,13 +231,17 @@ mini("c3 [e3 g3]*2").withMiniLocation([1,0,0],[1,14,14])

 Here, the string is wrapped in `mini`, which will create a pattern from a mini-notation string. Additionally, the `withMiniLocation` method passes the original source code location of the string to the pattern, which enables highlighting active events.

-Other convenient features like pseudo variables, operator overloading and top level await are possible with transpilation. After the transpilation, the code is ready to be evaluated into a `Pattern`. Behind the scenes, the user code string is parsed with `acorn`, turning it into an Abstract Syntax Tree (AST). The AST allows changing the structure of the code before generating the transpiled version using `escodegen`.
+Other convenient features like pseudo variables, operator overloading and top level await are possible with transpilation.
+
+After the transpilation, the code is ready to be evaluated into a `Pattern`.
+
+Behind the scenes, the user code string is parsed with `acorn`, turning it into an Abstract Syntax Tree (AST). The AST allows changing the structure of the code before generating the transpiled version using `escodegen`.

 ### Mini-notation

-While the transpilation allows us to express patterns in JavaScript in a less verbose way, it is still preferable to use the mini-notation as a more compact way to express rhythm. Strudel aims to provide the same mini-notation features and syntax as used in Tidal.
+While the transpilation allows JavaScript to express Patterns in a less verbose way, it is still preferable to use the mini-notation as a more compact way to express rhythm. Strudel aims to provide the same mini-notation features and syntax as used in Tidal.

-The mini-notation parser is implemented using `peggy` [@majdaPeggy2023], which allows generating performant parsers for Domain Specific Languages (DSLs) using a concise grammar notation. The generated parser turns the mini-notation string into an AST which is used to call the respective Strudel functions with the required structure. For example, `"c3 [e3 g3]*2"` will result in the following calls:
+The mini-notation parser is implemented using `peggy`, which allows generating performant parsers for Domain Specific Languages (DSLs) using a concise grammar notation. The generated parser turns the mini-notation string into an AST which is used to call the respective Strudel functions with the given structure. For example, `"c3 [e3 g3]*2"` will result in the following calls:

 ```js
 seq(
@@ -250,12 +255,12 @@ seq(

 ### Highlighting Locations

-As seen in the examples above, both the JS and the mini-notation parser add source code locations using `withMiniLocation` and `withLocation` methods. While the JS parser adds locations relative to the user code as a whole, the mini-notation adds locations relative to the position of the mini-notation string. The absolute location of elements within mini-notation can be calculated by simply adding both locations together. This absolute location is then used to highlight active events in real time. 
+As seen in the examples above, both the JS and the mini-notation parser add source code locations using `withMiniLocation` and `withLocation` methods. While the JS parser adds locations relative to the user code as a whole, the mini-notation adds locations relative to the position of the mini-notation string. The absolute location of elements within mini-notation can be calculated by simply adding both locations together. This absolute location can be used to highlight active events in real time.

 ## Scheduling Events

 After an instance of `Pattern` is obtained from the user code,
-the scheduler queries it for events. Once started, the scheduler runs at a fixed interval to query the active pattern for events within the current interval's time span. A simplified implementation looks like this:
+it is used by the scheduler to get queried for events. Once started, the scheduler runs at a fixed interval to query the active pattern for events within the current interval's time span. A simplified implementation looks like this:

 ```js
 let pattern = seq('c3', ['e3', 'g3']); // pattern from user
@@ -272,7 +277,7 @@ setInterval(() => {
 }, interval * 1000); // query each "interval" seconds
 ```

-Note that the above code is simplified for illustrative purposes, for example the actual implementation has to work around imprecise callbacks of `setInterval`. ^[Further implementation details of the Strudel scheduler can be read in this blog post: [loophole-letters.vercel.app/web-audio-scheduling](https://loophole-letters.vercel.app/web-audio-scheduling).]
+Note that the above code is simplified for illustrative purposes. The actual implementation has to work around imprecise callbacks of `setInterval`. More about the implementation details can be read in [this blog post](https://loophole-letters.vercel.app/web-audio-scheduling).

 The fact that `Pattern.queryArc` is a pure function that maps a time span to a set of events allows us to choose any interval we like without changing the resulting output. It also means that when the pattern is changed from outside, the next scheduling callback will work with the new pattern, keeping its clock running.

@@ -305,7 +310,7 @@ const { x, y } = createParams('x', 'y')
 x(sine.range(0, 200)).y(cosine.range(0,200))
 ```

-This example creates the custom control parameters `x` and `y` which are then used to form a pattern that describes the coordinates of a circle.
+This example creates the custom control parameters `x` and `y` which are then used to form a pattern that descibes the coordinates of a circle.

 ### Outputs

@@ -323,13 +328,13 @@ function onTrigger(hap, deadline, duration) {
 }
 ```

-The above example will create an `OscillatorNode` for each event, where the frequency is controlled by the `note` parameter. In essence, this is how the WebAudio API output of Strudel works, only with many more parameters to control synths, samples and effects.
+The above example will create an `OscillatorNode` for each event, where the frequency is controlled by the `note` param. In essence, this is how the WebAudio API output of Strudel works, only with many more parameters to control synths, samples and effects.

 # Pattern alignment and combination

 One core aspect of Strudel, inherited from Tidal, is the flexible way that patterns can be combined, irrespective of their structure. Its declarative approach means a live coder does not have to think about the details of *how* this is done, only *what* is to be done.

-As a simple example, consider two number patterns `"0 [1 2] 3"`, and `"10 20"`. The first has three contiguous steps of equal lengths, the second of which is broken down into two substeps, giving four events in total. The second pattern simply has two steps, taking up half a cycle each. There are a very large number of ways in which the structure of these two patterns could be combined, but the default method in both Strudel and Tidal is to line up the cycles of the two patterns, and then take events from the first pattern and match them with those in the second pattern. Therefore, the following two lines are equivalent:
+As a simple example, consider two number patterns `"0 [1 2] 3"`, and `"10 20"`. The first has three contiguous steps of equal lengths, with the second step broken down into two substeps, giving four events in total. There are a very large number of ways in which the structure of these two patterns could be combined, but the default method in both Strudel and Tidal is to line up the cycles of the two patterns, and then take events from the first pattern and match them with those in the second pattern. Therefore, the following two lines are equivalent:

 ```js
 "0 [1 2] 3".add("10 20")
@@ -384,20 +389,20 @@ versus Strudel's simplicity.
 To demonstrate this, consider the following Tidal pattern:

 ```haskell
-iter 4 $ every 3 (||+ n "10 20") $ n "20 21 23" # s "triangle" # crush 4
+iter 4 $ every 3 (||+ n "10 20") $ (n "0 1 3") # s "triangle" # crush 4
 ```

 This can be directly translated to the Strudel equivalent:

 ```js
-iter(4, every(3, x => x.add.squeeze(n("10 20")), n("20 21 23").s("triangle").crush(4)))
+iter(4, every(3, add.squeeze("10 20"), n("0 1 3").s("triangle").crush(4)))
 ```

 Although for a more canonical Strudel expression, we would reorder it
 as:

 ```js
-n("20 21 23").every(3, x => x.add.squeeze(n("10 20"))).iter(4).s("triangle").crush(4)
+n("0 1 3").every(3, add.squeeze("10 20")).iter(4).s("triangle").crush(4)
 ```

 The Strudel example uses the `.` method call operator for all
@@ -421,17 +426,17 @@ features.

 With Strudel, we have little choice but to embrace the affordances and
 constraints offered by JavaScript, and while designing a
-domain-specific language based on chaining method calls is a
+domain-specific language based on method calls is a
 challenge, through creative adoption of functional programming
 techniques like partial application, we are so far very happy with the
 results. Tidal's functional reactive approach to pattern-making has in
 general translated well to JavaScript, and opportunities and
-constraints have traded off to create a very approachable and
-usable live coding environment.
+constraints have overall traded off to create a very approachable and
+useable live coding environment.

 ## The trade-off of flexible typing

-We have identified one problem with porting Tidal to JavaScript where we have missed Haskell's strict typing and type inference. In both Tidal and Strudel, time is rational, where any point in time is represented as the ratio of two integers. This allows representation of musical ratios such that are impossible to represent accurately using the more common floating point numbers. However while libraries are available that support rational numbers in JavaScript, the lack of strict typing means that computationally expensive conversion from floating point to rational numbers may be performed late, and therefore often enough to overload the CPUs, due to the large number of iterative calculations required to estimate a ratio for a given floating point number. To mitigate this problem, we might consider moving to TypeScript in the future.
+We have identified one problem with porting Tidal to JavaScript where we have missed Haskell's strict typing and type inference. In both Tidal and Strudel, time is rational, where any point in time is represented as the ratio of two integers. This allows representation of musical ratios such that are impossible to represent accurately using the more common floating point numbers. However while libraries are available that support rational numbers in JavaScript, the lack of strict typing means that it is easy to implement pattern methods where computationally expensive conversion from floating point to rational numbers are performed late, and therefore often enough to overload the CPUs, due to the large number of iterative calculations required to estimate a ratio for a given floating point number. To mitigate this problem, we might consider moving to TypeScript in the future.

 # Future Outlook

@@ -441,14 +446,14 @@ The project is still young, with many features on the horizon. As general guidin
 2. consistent with Tidal's approach to pattern
 3. modular and extensible

-While Haskell's type system makes it a great language for the ongoing development of Tidal's inner representation of pattern, JavaScript's vibrant ecosystem, flexibility and accessibility makes it a great host for more ad-hoc experiments, including interface design. For the future, it is planned to integrate additional alternative sound engines such as Glicol [@lanGlicol2023] and Faust [@orlareyFaustProgrammingLanguage2023]. Strudel is already approaching feature parity with Tidal, but there are more Tidal functions to be ported, and work to be done to improve compatibility with Tidal's mini-notation. Tidal version 2.0 is under development, which brings a new representation for sequences to its patterns, which will then be brought to Strudel. Besides sound, other ways to render events are being explored, such as graphical, and choreographic output. We are also looking into alternative ways of editing patterns, including multi-user editing for network music, parsing a novel syntax to escape the constraints of JavaScript, and developing hardware/e-textile interfaces. In summary, there is a lot of fun ahead.
+While Haskell's type system makes it a great language for the ongoing development of Tidal's inner representation of pattern, JavaScript's vibrant ecosystem, flexibility and accessibility makes it a great host for more ad-hoc experiments, including interface design. For the future, it is planned to integrate additional alternative sound engines such as Glicol [@lanChaosprintGlicol2022] and Faust [@FaustProgrammingLanguage2022]. Strudel is already approaching feature parity with Tidal, but there are more Tidal functions to be ported, and work to be done to improve compatibility with Tidal's mini-notation. Tidal version 2.0 is under development, which brings a new representation for sequences to its patterns, which will then be brought to Strudel. Besides sound, other ways to render events are being explored, such as graphical, and choreographic output. We are also looking into alternative ways of editing patterns, including multi-user editing for network music, parsing a novel syntax to escape the constraints of JavaScript, and developing hardware/e-textile interfaces. In summary, there is a lot of fun ahead.

 # Links

 The Strudel REPL is available at <https://strudel.tidalcycles.org>, including an interactive tutorial.
 The repository is at <https://github.com/tidalcycles/strudel>, all the code is open source under the AGPL-3.0 License.

-# Acknowledgements
+# Acknowledgments

 Thanks to the Strudel and wider Tidal, live coding, WebAudio and free/open source software communities for inspiration and support. Alex McLean's work on this project is supported by a UKRI Future Leaders Fellowship [grant number MR/V025260/1].

@@ -63,6 +63,7 @@ exports[`renders tunes > tune: arpoon 1`] = `
  "[ 0/1 → 1/2 | s:bd bank:RolandTR909 gain:0.5 ]",
  "[ 1/2 → 1/1 | s:bd bank:RolandTR909 gain:0.5 ]",
  "[ 1/2 → 2/3 | s:hh bank:RolandTR909 gain:0.5 ]",
+  "[ 5/6 → 1/1 | s:hh bank:RolandTR909 gain:0.5 ]",
 ]
 `;

@@ -8193,11 +8194,11 @@ exports[`renders tunes > tune: orbit 1`] = `

 exports[`renders tunes > tune: outroMusic 1`] = `
 [
-  "[ (0/1 → 1/1) ⇝ 3/1 | note:E3 s:0040_FluidR3_GM_sf2_file attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
-  "[ (0/1 → 1/1) ⇝ 3/1 | note:G3 s:0040_FluidR3_GM_sf2_file attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
-  "[ (0/1 → 1/1) ⇝ 3/1 | note:B3 s:0040_FluidR3_GM_sf2_file attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
-  "[ (0/1 → 1/1) ⇝ 3/1 | note:D4 s:0040_FluidR3_GM_sf2_file attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
-  "[ (0/1 → 1/1) ⇝ 9/2 | note:C5 s:0040_FluidR3_GM_sf2_file attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
+  "[ (0/1 → 1/1) ⇝ 3/1 | note:E3 s:gm_epiano1 n:1 attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
+  "[ (0/1 → 1/1) ⇝ 3/1 | note:G3 s:gm_epiano1 n:1 attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
+  "[ (0/1 → 1/1) ⇝ 3/1 | note:B3 s:gm_epiano1 n:1 attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
+  "[ (0/1 → 1/1) ⇝ 3/1 | note:D4 s:gm_epiano1 n:1 attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
+  "[ (0/1 → 1/1) ⇝ 9/2 | note:C5 s:gm_epiano1 n:1 attack:0.05 decay:0.1 sustain:0.7 cutoff:1111.7252990603447 gain:0.3 ]",
  "[ 0/1 → 3/4 | note:C2 s:sawtooth attack:0.05 decay:0.1 sustain:0.7 cutoff:864.536878321087 gain:0.3 ]",
  "[ 0/1 → 3/4 | s:bd speed:0.9107561463868479 n:3 ]",
  "[ (3/4 → 1/1) ⇝ 3/2 | s:sd speed:0.9931522866332672 n:3 ]",
@@ -15,8 +15,8 @@
    "isNoteWithOctave",
    "isNote",
    "tokenizeNote",
-    "toMidi",
-    "fromMidi",
+    "noteToMidi",
+    "midiToFreq",
    "freqToMidi",
    "valueToMidi",
    "_mod",
@@ -0,0 +1,8 @@
+https://www.1001fonts.com/galactico-font.html
+
+If the License is “Free” do what ever you want with it, even for commercial use, any “shout-out” or support thrown our way is much appreciated, even donating to buy a cup of coffee helps a lot. If the License is “For Personal Use Only” do what ever you want with it for yourself, but if you plan to make money out of it, meaning for commercial use, buy a license @ www.hellodonmarciano.com
+
+I’ll appreciate your support when and if possible. Enjoy!
+
+Galactico is licensed under the 1001Fonts Free For Commercial Use License (FFC)
+https://www.1001fonts.com/licenses/ffc.html
@@ -0,0 +1,7 @@
+This font was created by Nate Piekos of Blambot Comic Fonts.  It's freeware to use as you'd like, but if you redistribute it, you must include this text file with the zip.
+
+~Nate Piekos
+
+Blambot Comic Fonts
+http://www.piekosarts.com/blambotfonts
+blambot@piekosarts.com
@@ -1986,7 +1986,7 @@
    "Idiophones/Struck%20Idiophones/Tambourine%202/Tamb2_Shake_rr3_Mid.wav",
    "Idiophones/Struck%20Idiophones/Tambourine%202/Tamb2_Shake_rr4_Mid.wav"
  ],
-  "triangle": [
+  "triangles": [
    "Idiophones/Struck%20Idiophones/Triangles/Triangle1_HitFM_v1_rr1_Mid.wav",
    "Idiophones/Struck%20Idiophones/Triangles/Triangle1_HitFM_v1_rr2_Mid.wav",
    "Idiophones/Struck%20Idiophones/Triangles/Triangle1_HitM_v1_rr2_Mid.wav",
@@ -73,6 +73,7 @@ export const SIDEBAR: Sidebar = {
    ],
    Development: [
      { text: 'REPL', link: 'technical-manual/repl' },
+      { text: 'Sounds', link: 'technical-manual/sounds' },
      { text: 'Packages', link: 'technical-manual/packages' },
      { text: 'Docs', link: 'technical-manual/docs' },
      { text: 'Testing', link: 'technical-manual/testing' },
@@ -18,6 +18,7 @@ if (typeof window !== 'undefined') {
    import('@strudel.cycles/webaudio'),
    import('@strudel.cycles/osc'),
    import('@strudel.cycles/csound'),
+    import('@strudel.cycles/soundfonts'),
  );
 }

@@ -26,7 +26,7 @@ to fit better for the larger context, while mini notation is more practical for

 ## Limits of Mini Notation

-While the Mini Notation is a powerful way to write rhythms shortly, it also has its limits. Take this example:
+While the Mini Notation is a powerful way to write rhythms concisely, it also has its limits. Take this example:

 <MiniRepl
  client:idle
@@ -46,16 +46,16 @@ For drum sounds, strudel uses the comprehensive [tidal-drum-machines](https://gi

 Furthermore, strudel also loads instrument samples from [VCSL](https://github.com/sgossner/VCSL) by default.

-To see which sample names are available, open the `samples` tab in the [REPL](https://strudel.tidalcycles.org/).
+To see which sample names are available, open the `sounds` tab in the [REPL](https://strudel.tidalcycles.org/).

-Note that only the sample maps (mapping names to URLs) are loaded initially, while the audio samples itself are not loaded until they are actually played.
+Note that only the sample maps (mapping names to URLs) are loaded initially, while the audio samples themselves are not loaded until they are actually played.
 This behaviour of loading things only when they are needed is also called `lazy loading`.
 While it saves resources, it can also lead to sounds not being audible the first time they are triggered, because the sound is still loading.
 [This might be fixed in the future](https://github.com/tidalcycles/strudel/issues/187)

 # Sound Banks

-If we look at the `samples` tab, we can see that the drum samples are all prefixed with drum machine names: `RolandTR808_bd`, `RolandTR808_sd`, `RolandTR808_hh` etc..
+If we open the `sounds` tab and then `drum machines`, we can see that the drum samples are all prefixed with drum machine names: `RolandTR808_bd`, `RolandTR808_sd`, `RolandTR808_hh` etc..

 We _could_ use them like this:

@@ -75,9 +75,9 @@ Also note that some banks won't have samples for all sounds!

 # Selecting Sounds

-If we look again at the `samples` tab, there is also a number behind each name, indicating how many individual samples are available.
+If we open the `sounds` tab again, followed by tab `drum machines`, there is also a number behind each name, indicating how many individual samples are available.
 For example `RolandTR909_hh(4)` means there are 4 samples of a TR909 hihat available.
-By default, `s` will play the first sample, but we can selecting the other ones using `n`, starting from 0:
+By default, `s` will play the first sample, but we can select the other ones using `n`, starting from 0:

 <MiniRepl client:idle tune={`s("hh*4").bank("RolandTR909").n("<0 1 2 3>")`} />

@@ -58,5 +58,6 @@ These packages provide bindings for different ways to output strudel patterns:

 ## Tools

- [pnpm workspaces](https://pnpm.io/)
- Publishing packages is done with [lerna](https://lerna.js.org/).
+- [pnpm](https://pnpm.io/) for package management, workspaces and publishing
+- [lerna](https://lerna.js.org/) for bumping versions
+- see CONTRIBUTING.md for more info
@@ -0,0 +1,75 @@
+---
+title: Sounds
+layout: ../../layouts/MainLayout.astro
+---
+
+import { MiniRepl } from '../../docs/MiniRepl';
+
+# Sounds
+
+Let's take a closer look about how sounds are implemented in the webaudio output.
+
+## Registering a sound
+
+All sounds are registered in the sound map, using the the `registerSound` function:
+
+```ts
+function registerSound(
+  name: string, // The name of the sound that should be given to `s`, e.g. `mysaw`
+  // The function called by the scheduler to trigger the sound:
+  (
+    time: number, // The audio context time the sound should start
+    value: object, // The value of the `Hap`
+    onended: () => void // A callback that should be fired when the sound has ended
+  ) => {
+    node: AudioNode, // node to connect to rest of the effects chain
+    stop: (time:number) => void // a function that will stop the sound
+  },
+  data: object // meta data, only for ui logic in sounds tab
+);
+```
+
+When `registerSound` is called, it registers `{ onTrigger, data }` under the given `name` in a [nanostore map](https://github.com/nanostores/nanostores#maps).
+
+### Example
+
+This might be a bit abstract, so here is a minimal example:
+
+```js
+registerSound(
+  'mysaw',
+  (time, value, onended) => {
+    let { freq } = value; // destructure control params
+    const ctx = getAudioContext();
+    // create oscillator
+    const o = new OscillatorNode(ctx, { type: 'sawtooth', frequency: Number(freq) });
+    o.start(time);
+    // add gain node to level down osc
+    const g = new GainNode(ctx, { gain: 0.3 });
+    // connect osc to gain
+    const node = o.connect(g);
+    // this function can be called from outside to stop the sound
+    const stop = (time) => o.stop(time);
+    // ended will be fired when stop has been fired
+    o.addEventListener('ended', () => {
+      o.disconnect();
+      g.disconnect();
+      onended();
+    });
+    return { node, stop };
+  },
+  { type: 'synth' },
+);
+// use the sound
+freq(220, 440, 330).s('mysaw');
+```
+
+You can actually use this code in the [REPL](https://strudel.tidalcycles.org/) and it'll work.
+After evaluating the code, you should see `mysaw` in listed in the sounds tab.
+
+## Playing sounds
+
+Now here is what happens when a sound is played:
+When the webaudio output plays a `Hap`, it will lookup and call the `onTrigger` function for the given `s`.
+The returned `node` can then be connected to the rest of the standard effects chain
+Having the stop function separate allows playing sounds via midi too, where you don't know how long the noteon will last
@@ -3,11 +3,12 @@ import { logger } from '@strudel.cycles/core';
 import { useEvent, cx } from '@strudel.cycles/react';
 // import { cx } from '@strudel.cycles/react';
 import { nanoid } from 'nanoid';
-import React, { useCallback, useLayoutEffect, useRef, useState } from 'react';
-import { loadedSamples } from './Repl';
+import React, { useMemo, useCallback, useLayoutEffect, useRef, useState } from 'react';
 import { Reference } from './Reference';
 import { themes } from './themes.mjs';
 import { useSettings, settingsMap, setActiveFooter, defaultSettings } from '../settings.mjs';
+import { getAudioContext, soundMap } from '@strudel.cycles/webaudio';
+import { useStore } from '@nanostores/react';

 export function Footer({ context }) {
  const footerContent = useRef();
@@ -72,7 +73,7 @@ export function Footer({ context }) {
      <div className="flex justify-between px-2">
        <div className={cx('flex select-none max-w-full overflow-auto', activeFooter && 'pb-2')}>
          <FooterTab name="intro" label="welcome" />
-          <FooterTab name="samples" />
+          <FooterTab name="sounds" />
          <FooterTab name="console" />
          <FooterTab name="reference" />
          <FooterTab name="settings" />
@@ -84,13 +85,10 @@ export function Footer({ context }) {
        )}
      </div>
      {activeFooter !== '' && (
-        <div
-          className="text-white font-mono text-sm h-[360px] flex-none overflow-auto max-w-full relative"
-          ref={footerContent}
-        >
+        <div className="text-white flex-none h-[360px] overflow-auto max-w-full relative" ref={footerContent}>
          {activeFooter === 'intro' && <WelcomeTab />}
          {activeFooter === 'console' && <ConsoleTab log={log} />}
-          {activeFooter === 'samples' && <SamplesTab />}
+          {activeFooter === 'sounds' && <SoundsTab />}
          {activeFooter === 'reference' && <Reference />}
          {activeFooter === 'settings' && <SettingsTab scheduler={context.scheduler} />}
        </div>
@@ -154,7 +152,7 @@ function WelcomeTab() {
      <h3>about</h3>
      <p>
        strudel is a JavaScript version of{' '}
-        <a href="tidalcycles.org/" target="_blank">
+        <a href="https://tidalcycles.org/" target="_blank">
          tidalcycles
        </a>
        , which is a popular live coding language for music, written in Haskell. You can find the source code at{' '}
@@ -173,7 +171,7 @@ function WelcomeTab() {

 function ConsoleTab({ log }) {
  return (
-    <div id="console-tab" className="break-all px-4 dark:text-white text-stone-900">
+    <div id="console-tab" className="break-all px-4 dark:text-white text-stone-900 text-sm">
      <pre>{`███████╗████████╗██████╗ ██╗   ██╗██████╗ ███████╗██╗     
 ██╔════╝╚══██╔══╝██╔══██╗██║   ██║██╔══██╗██╔════╝██║     
 ███████╗   ██║   ██████╔╝██║   ██║██║  ██║█████╗  ██║     
@@ -193,36 +191,104 @@ function ConsoleTab({ log }) {
  );
 }

-function SamplesTab() {
+const getSamples = (samples) =>
+  Array.isArray(samples) ? samples.length : typeof samples === 'object' ? Object.values(samples).length : 1;
+
+function SoundsTab() {
+  const sounds = useStore(soundMap);
+  const { soundsFilter } = useSettings();
+  const soundEntries = useMemo(() => {
+    let filtered = Object.entries(sounds).filter(([key]) => !key.startsWith('_'));
+    if (!sounds) {
+      return [];
+    }
+    if (soundsFilter === 'user') {
+      return filtered.filter(([key, { data }]) => !data.prebake);
+    }
+    if (soundsFilter === 'drums') {
+      return filtered.filter(([_, { data }]) => data.type === 'sample' && data.tag === 'drum-machines');
+    }
+    if (soundsFilter === 'samples') {
+      return filtered.filter(([_, { data }]) => data.type === 'sample' && data.tag !== 'drum-machines');
+    }
+    if (soundsFilter === 'synths') {
+      return filtered.filter(([_, { data }]) => ['synth', 'soundfont'].includes(data.type));
+    }
+    return filtered;
+  }, [sounds, soundsFilter]);
+  // holds mutable ref to current triggered sound
+  const trigRef = useRef();
+  // stop current sound on mouseup
+  useEvent('mouseup', () => {
+    const t = trigRef.current;
+    trigRef.current = undefined;
+    t?.then((ref) => {
+      ref?.stop(getAudioContext().currentTime + 0.01);
+    });
+  });
  return (
-    <div id="samples-tab" className="break-normal w-full px-4 dark:text-white text-stone-900">
-      <span>{loadedSamples.length} banks loaded:</span>
-      {loadedSamples.map(([name, samples]) => (
-        <span key={name} className="cursor-pointer hover:opacity-50" onClick={() => {}}>
-          {' '}
-          {name}(
-          {Array.isArray(samples) ? samples.length : typeof samples === 'object' ? Object.values(samples).length : 1}){' '}
-        </span>
-      ))}
+    <div id="sounds-tab" className="flex flex-col w-full h-full dark:text-white text-stone-900">
+      <div className="px-2 pb-2 flex-none">
+        <ButtonGroup
+          value={soundsFilter}
+          onChange={(value) => settingsMap.setKey('soundsFilter', value)}
+          items={{
+            samples: 'samples',
+            drums: 'drum-machines',
+            synths: 'Synths',
+            user: 'User',
+          }}
+        ></ButtonGroup>
+      </div>
+      <div className="p-2 min-h-0 max-h-full grow overflow-auto font-mono text-sm break-normal">
+        {soundEntries.map(([name, { data, onTrigger }]) => (
+          <span
+            key={name}
+            className="cursor-pointer hover:opacity-50"
+            onMouseDown={async () => {
+              const ctx = getAudioContext();
+              const params = {
+                note: ['synth', 'soundfont'].includes(data.type) ? 'a3' : undefined,
+                s: name,
+                clip: 1,
+                release: 0.5,
+              };
+              const time = ctx.currentTime + 0.05;
+              const onended = () => trigRef.current?.node?.disconnect();
+              trigRef.current = Promise.resolve(onTrigger(time, params, onended));
+              trigRef.current.then((ref) => {
+                ref?.node.connect(ctx.destination);
+              });
+            }}
+          >
+            {' '}
+            {name}
+            {data?.type === 'sample' ? `(${getSamples(data.samples)})` : ''}
+            {data?.type === 'soundfont' ? `(${data.fonts.length})` : ''}
+          </span>
+        ))}
+        {!soundEntries.length ? 'No custom sounds loaded in this pattern (yet).' : ''}
+      </div>
    </div>
  );
 }

 function ButtonGroup({ value, onChange, items }) {
  return (
-    <div className="flex grow border border-foreground rounded-md">
+    <div className="flex max-w-lg">
      {Object.entries(items).map(([key, label], i, arr) => (
        <button
          key={key}
          onClick={() => onChange(key)}
          className={cx(
-            'p-2 grow',
-            i === 0 && 'rounded-l-md',
-            i === arr.length - 1 && 'rounded-r-md',
-            value === key ? 'bg-background' : 'bg-lineHighlight',
+            'px-2 border-b h-8',
+            // i === 0 && 'rounded-l-md',
+            // i === arr.length - 1 && 'rounded-r-md',
+            // value === key ? 'bg-background' : 'bg-lineHighlight',
+            value === key ? 'border-foreground' : 'border-transparent',
          )}
        >
-          {label}
+          {label.toLowerCase()}
        </button>
      ))}
    </div>
@@ -282,6 +348,8 @@ const fontFamilyOptions = {
  BigBlueTerminal: 'BigBlueTerminal',
  x3270: 'x3270',
  PressStart: 'PressStart2P',
+  galactico: 'galactico',
+  'we-come-in-peace': 'we-come-in-peace',
 };

 function SettingsTab({ scheduler }) {
@@ -0,0 +1,13 @@
+import { cx } from '@strudel.cycles/react';
+import React from 'react';
+
+function Loader({ active }) {
+  return (
+    <div className="overflow-hidden opacity-50 fixed top-0 left-0 w-full z-[1000]">
+      <div className={cx('h-[2px] block w-full', active ? 'bg-foreground animate-train' : 'bg-transparent')}>
+        <div />
+      </div>
+    </div>
+  );
+}
+export default Loader;
@@ -6,7 +6,7 @@ const visibleFunctions = jsdocJson.docs
 export function Reference() {
  return (
    <div className="flex h-full w-full pt-2 text-foreground">
-      <div className="w-64 flex-none h-full overflow-y-auto overflow-x-hidden pr-4">
+      <div className="w-42 flex-none h-full overflow-y-auto overflow-x-hidden pr-4">
        {visibleFunctions.map((entry, i) => (
          <a key={i} className="cursor-pointer block hover:bg-lineHighlight py-1 px-4" href={`#doc-${i}`}>
            {entry.name} {/* <span className="text-gray-600">{entry.meta.filename}</span> */}
@@ -6,13 +6,7 @@ This program is free software: you can redistribute it and/or modify it under th

 import { cleanupDraw, cleanupUi, controls, evalScope, getDrawContext, logger } from '@strudel.cycles/core';
 import { CodeMirror, cx, flash, useHighlighting, useStrudel, useKeydown } from '@strudel.cycles/react';
-import {
-  getAudioContext,
-  getLoadedSamples,
-  initAudioOnFirstClick,
-  resetLoadedSamples,
-  webaudioOutput,
-} from '@strudel.cycles/webaudio';
+import { getAudioContext, initAudioOnFirstClick, resetLoadedSounds, webaudioOutput } from '@strudel.cycles/webaudio';
 import { createClient } from '@supabase/supabase-js';
 import { nanoid } from 'nanoid';
 import React, { createContext, useCallback, useEffect, useState } from 'react';
@@ -24,6 +18,7 @@ import * as tunes from './tunes.mjs';
 import PlayCircleIcon from '@heroicons/react/20/solid/PlayCircleIcon';
 import { themes } from './themes.mjs';
 import { settingsMap, useSettings, setLatestCode } from '../settings.mjs';
+import Loader from './Loader';

 const { latestCode } = settingsMap.get();

@@ -48,12 +43,11 @@ const modules = [
  import('@strudel.cycles/csound'),
 ];

-evalScope(
+const modulesLoading = evalScope(
  controls, // sadly, this cannot be exported from core direclty
  ...modules,
 );

-export let loadedSamples = [];
 const presets = prebake();

 let drawContext, clearCanvas;
@@ -62,11 +56,6 @@ if (typeof window !== 'undefined') {
  clearCanvas = () => drawContext.clearRect(0, 0, drawContext.canvas.height, drawContext.canvas.width);
 }

-Promise.all([...modules, presets]).then((data) => {
-  // console.log('modules and sample registry loade', data);
-  loadedSamples = Object.entries(getLoadedSamples() || {});
-});
-
 const getTime = () => getAudioContext().currentTime;

 async function initCode() {
@@ -114,7 +103,7 @@ export function Repl({ embedded = false }) {
  const isEmbedded = embedded || window.location !== window.parent.location;
  const [view, setView] = useState(); // codemirror view
  const [lastShared, setLastShared] = useState();
-  const [pending, setPending] = useState(false);
+  const [pending, setPending] = useState(true);

  const { theme, keybindings, fontSize, fontFamily } = useSettings();

@@ -123,16 +112,45 @@ export function Repl({ embedded = false }) {
      initialCode: '// LOADING',
      defaultOutput: webaudioOutput,
      getTime,
-      beforeEval: () => {
+      beforeEval: async () => {
+        setPending(true);
+        await modulesLoading;
        cleanupUi();
        cleanupDraw();
-        setPending(true);
      },
-      afterEval: ({ code }) => {
+      afterEval: async ({ code, pattern }) => {
+        // preload sounds
+        const t = scheduler.getTime();
+        const lookahead = 16;
+        const upcoming = pattern
+          .queryArc(t, t + lookahead)
+          .filter((h) => h.value.s)
+          .map((h) => `${h.value.bank ? `${h.value.bank}_` : ''}${h.value.s}:${h.value.n || 0}`)
+          .filter((v, i, all) => all.indexOf(v) === i);
+        // console.log('now preloading sounds:', upcoming);
+        const preload = upcoming.map(async (v) => {
+          const [s, n] = v.split(':');
+          const sound = soundMap.value[s];
+          if (!sound) {
+            throw new Error(`[preload] error: sound not found: "${s}:${n}"`);
+          }
+          // TODO: only preload if not already preloaded...
+          // TODO: add sound.preload interface that only loads the sample, without creating a buffersource
+          return sound.onTrigger(getAudioContext().currentTime + 0.5, { s, n }, () => {
+            // console.log('onended');
+          });
+        });
+        await Promise.all(preload);
+        // console.log('preloading done');
+
        setPending(false);
        setLatestCode(code);
        window.location.hash = '#' + encodeURIComponent(btoa(code));
      },
+      onEvalError: (err) => {
+        console.log('errr');
+        setPending(false);
+      },
      onToggle: (play) => !play && cleanupDraw(false),
      drawContext,
    });
@@ -147,6 +165,7 @@ export function Repl({ embedded = false }) {
        'highlight',
      );
      setCode(decoded || latestCode || randomTune);
+      setPending(false);
    });
  }, []);

@@ -156,10 +175,14 @@ export function Repl({ embedded = false }) {
      async (e) => {
        if (e.ctrlKey || e.altKey) {
          if (e.code === 'Enter') {
+            if (getAudioContext().state !== 'running') {
+              alert('please click play to initialize the audio. you can use shortcuts after that!');
+              return;
+            }
            e.preventDefault();
            flash(view);
            await activateCode();
-          } else if (e.code === 'Period') {
+          } else if (e.key === '.') {
            stop();
            e.preventDefault();
          }
@@ -211,7 +234,8 @@ export function Repl({ embedded = false }) {
    const { code, name } = getRandomTune();
    logger(`[repl] ✨ loading random tune "${name}"`);
    clearCanvas();
-    resetLoadedSamples();
+    resetLoadedSounds();
+    scheduler.setCps(1);
    await prebake(); // declare default samples
    await evaluate(code, false);
  };
@@ -265,6 +289,7 @@ export function Repl({ embedded = false }) {
          //        'bg-gradient-to-t from-green-900 to-slate-900', //
        )}
      >
+        <Loader active={pending} />
        <Header context={context} />
        <section className="grow flex text-gray-100 relative overflow-auto cursor-text pb-0" id="code">
          <CodeMirror
@@ -1,22 +1,28 @@
-import { Pattern, toMidi, valueToMidi } from '@strudel.cycles/core';
-import { samples } from '@strudel.cycles/webaudio';
+import { Pattern, noteToMidi, valueToMidi } from '@strudel.cycles/core';
+//import { registerSoundfonts } from '@strudel.cycles/soundfonts';
+import { registerSynthSounds, samples } from '@strudel.cycles/webaudio';

 export async function prebake() {
  // https://archive.org/details/SalamanderGrandPianoV3
  // License: CC-by http://creativecommons.org/licenses/by/3.0/ Author: Alexander Holm
-  return await Promise.all([
-    samples(`./piano.json`, `./piano/`),
+  registerSynthSounds();
+  //registerSoundfonts();
+  await Promise.all([
+    samples(`./piano.json`, `./piano/`, { prebake: true }),
    // https://github.com/sgossner/VCSL/
    // https://api.github.com/repositories/126427031/contents/
    // LICENSE: CC0 general-purpose
-    samples(`./vcsl.json`, 'github:sgossner/VCSL/master/'),
-    samples(`./tidal-drum-machines.json`, 'github:ritchse/tidal-drum-machines/main/machines/'),
-    samples(`./EmuSP12.json`, `./EmuSP12/`),
+    samples(`./vcsl.json`, 'github:sgossner/VCSL/master/', { prebake: true }),
+    samples(`./tidal-drum-machines.json`, 'github:ritchse/tidal-drum-machines/main/machines/', {
+      prebake: true,
+      tag: 'drum-machines',
+    }),
+    samples(`./EmuSP12.json`, `./EmuSP12/`, { prebake: true, tag: 'drum-machines' }),
    // samples('github:tidalcycles/Dirt-Samples/master'),
  ]);
 }

-const maxPan = toMidi('C8');
+const maxPan = noteToMidi('C8');
 const panwidth = (pan, width) => pan * width + (1 - width) / 2;

 Pattern.prototype.piano = function () {
@@ -566,7 +566,7 @@ samples({
 "C^7 Am7 Dm7 G7".slow(2).voicings('lefthand')
  .stack("0@6 [<1 2> <2 0> 1]@2".scale('C5 major'))
  .note().slow(4)
-  .s('0040_FluidR3_GM_sf2_file')
+  .s("gm_epiano1:1")
  .color('steelblue')
  .stack(
   "<-7 ~@2 [~@2 -7] -9 ~@2 [~@2 -9] -10!2 ~ [~@2 -10] -5 ~ [-3 -2 -10]@2>*2".scale('C3 major')
@@ -9,6 +9,7 @@ export const defaultSettings = {
  fontSize: 18,
  latestCode: '',
  isZen: false,
+  soundsFilter: 'all',
 };

 export const settingsMap = persistentMap('strudel-settings', defaultSettings);
@@ -10,6 +10,14 @@
  font-family: 'x3270';
  src: url('/fonts/3270/3270-Regular.ttf');
 }
+@font-face {
+  font-family: 'galactico';
+  src: url('/fonts/galactico/Galactico-Basic.otf');
+}
+@font-face {
+  font-family: 'we-come-in-peace';
+  src: url('/fonts/we-come-in-peace/we-come-in-peace-bb.regular.ttf');
+}

 .cm-gutters {
  display: none !important;
@@ -22,7 +30,6 @@
  --app-height: 100vh;
 }

-#console-tab,
-#samples-tab {
+#console-tab {
  font-family: BigBlueTerminal, monospace;
 }
@@ -10,6 +10,15 @@ module.exports = {
  ],
  theme: {
    extend: {
+      keyframes: {
+        train: {
+          '0%': { transform: 'translateX(-100%)' },
+          '100%': { transform: 'translateX(100%)' },
+        },
+      },
+      animation: {
+        train: 'train 2s linear infinite',
+      },
      colors: {
        // codemirror-theme settings
        background: 'var(--background)',
Author	SHA1	Message	Date
Felix Roos	bd6a2c6650	first draft for sound preloading	2023-03-24 20:55:29 +01:00
Felix Roos	c5a2ae47d7	Merge pull request #542 from tidalcycles/loading-animation feat: add loader bar to animate loading state	2023-03-24 12:54:20 +01:00
Felix Roos	17654b885b	feat: add loader bar to animate loading state	2023-03-24 12:41:00 +01:00
Felix Roos	acaf0ca0af	Merge pull request #539 from tidalcycles/setcps-reset-only-on-shuffle do not reset cps before eval #517	2023-03-23 22:39:26 +01:00
Felix Roos	6a201be1fd	Merge remote-tracking branch 'origin/main' into setcps-reset-only-on-shuffle	2023-03-23 22:35:57 +01:00
Felix Roos	8617b9164e	do not reset cps before eval #517	2023-03-23 22:34:25 +01:00
Felix Roos	991e5f1b3c	Merge pull request #538 from tidalcycles/improve-loading improve initial loading + wait before eval	2023-03-23 22:27:31 +01:00
Felix Roos	55c533c947	improve initial loading + wait before eval	2023-03-23 21:56:20 +01:00
Felix Roos	d17543d5d9	Merge pull request #537 from tidalcycles/fix-keypress-period fix period key for dvorak + remove duplicated code	2023-03-23 21:40:19 +01:00
Felix Roos	73169563c4	fix period key for dvorak + remove duplicated code	2023-03-23 21:37:38 +01:00
Felix Roos	d351cb9f7f	Merge pull request #535 from tidalcycles/update-lerna Update lerna	2023-03-23 11:44:56 +01:00
Felix Roos	251be60630	update package publishing guide	2023-03-23 11:39:33 +01:00
Felix Roos	18d7222804	Publish - @strudel.cycles/core@0.7.2 - @strudel.cycles/csound@0.7.1 - @strudel.cycles/eval@0.7.1 - @strudel.cycles/midi@0.7.1 - @strudel.cycles/mini@0.7.2 - @strudel.cycles/osc@0.7.1 - @strudel.cycles/react@0.7.1 - @strudel.cycles/serial@0.7.1 - @strudel.cycles/soundfonts@0.7.1 - @strudel.cycles/tonal@0.7.1 - @strudel.cycles/tone@0.7.1 - @strudel.cycles/transpiler@0.7.1 - @strudel.cycles/webaudio@0.7.1 - @strudel.cycles/webdirt@0.7.1 - @strudel.cycles/xen@0.7.1	2023-03-23 11:34:07 +01:00
Felix Roos	ff1c37d361	bump core + mini to 0.7.1	2023-03-23 11:26:23 +01:00
Felix Roos	3abe6db3de	Publish - @strudel.cycles/core@0.7.0 - @strudel.cycles/csound@0.7.0 - @strudel.cycles/eval@0.7.0 - @strudel.cycles/midi@0.7.0 - @strudel.cycles/mini@0.7.0 - @strudel.cycles/osc@0.7.0 - @strudel.cycles/react@0.7.0 - @strudel.cycles/serial@0.7.0 - @strudel.cycles/soundfonts@0.7.0 - @strudel.cycles/tonal@0.7.0 - @strudel.cycles/tone@0.7.0 - @strudel.cycles/transpiler@0.7.0 - @strudel.cycles/webaudio@0.7.0 - @strudel.cycles/webdirt@0.7.0 - @strudel.cycles/xen@0.7.0	2023-03-23 11:21:02 +01:00
Felix Roos	b9ca9d3b06	update lerna	2023-03-23 11:17:21 +01:00
Felix Roos	9bbc04843d	Merge pull request #534 from tidalcycles/soundfont-freq-support feat: add freq support to gm soundfonts	2023-03-23 10:21:55 +01:00
Felix Roos	ddf61a6438	Merge pull request #531 from ijc8/main Maintain random seed state in parser, not globally	2023-03-23 10:18:58 +01:00
Felix Roos	ba35a81e9b	- feat: add freq support to gm soundfonts - refactor: toMidi -> noteToMidi - refactor: fromMidi -> midiToFreq	2023-03-23 10:18:24 +01:00
Felix Roos	13133583ca	Merge pull request #527 from bwagner/main FIXES: alias pm for polymeter	2023-03-21 22:35:17 +01:00
Felix Roos	e91b981740	Merge pull request #529 from revolunet/patch-1 fix(footer): fix link to tidalcycles	2023-03-21 22:29:06 +01:00
Bernhard Wagner	1458ee64ec	FIXES: alias pm for polymeter	2023-03-21 21:20:57 +01:00
Ian Clester	4e2a5e1663	Add pairwise independence test, tweak `randOffset`	2023-03-20 22:27:35 -04:00
Ian Clester	c98b0e9687	Format code with prettier	2023-03-20 19:19:42 -04:00
Ian Clester	4e25990de9	Uncomment test for random choice operator (`\|`)	2023-03-20 17:46:57 -04:00
Ian Clester	4b51f1a3fc	Sync up `?` with `degrade()`	2023-03-20 15:26:27 -04:00
Ian Clester	5490b01004	Maintain random seed state in parser, not globally	2023-03-20 14:59:43 -04:00
Julien Bouquillon	43176e1f1d	fix(footer): fix link to tidalcycles	2023-03-20 01:38:21 +01:00
Bernhard Wagner	fffd3c07ca	FIXES: alias pm for polymeter (return statement was missing)	2023-03-18 22:12:12 +01:00
Felix Roos	952bd38e70	Merge pull request #525 from bwagner/patch-4 Update intro.mdx	2023-03-18 20:25:21 +01:00
Felix Roos	8589f5cc89	Merge pull request #524 from bwagner/patch-3 Update samples.mdx	2023-03-18 20:24:38 +01:00
Bernhard Wagner	ec594d52f8	Update intro.mdx shortly -> concisely	2023-03-18 19:31:57 +01:00
Bernhard Wagner	848cbf9c60	Update samples.mdx fixes few typos and the former `samples` tab is now `sounds`	2023-03-18 15:37:59 +01:00
Felix Roos	e02be7dd9a	Merge pull request #521 from tidalcycles/fix-envelope fix: envelopes in chrome	2023-03-17 09:03:10 +01:00
Felix Roos	33d35e47a6	fix: envelope in chrome	2023-03-17 08:56:05 +01:00
Felix Roos	18d62b32c2	Merge pull request #516 from tidalcycles/source-nodes registerSound API + improved sounds tab + regroup soundfonts	2023-03-16 16:13:30 +01:00
Felix Roos	58ed51b49c	snapshot	2023-03-16 15:49:56 +01:00
Felix Roos	9f9fe529e4	fix only tune that uses soundfonts	2023-03-16 15:49:08 +01:00
Felix Roos	aad721890a	pass duration to source callback	2023-03-16 15:48:59 +01:00
Felix Roos	e63a5d10c8	regroup sounds - extra tab for drum-machines - combine synths and soundfonts	2023-03-16 15:21:16 +01:00
Felix Roos	15681262de	use only _ for easier copying via double click	2023-03-16 15:19:38 +01:00
Felix Roos	b5d3aa81f9	format	2023-03-16 12:25:08 +01:00
Felix Roos	a688061616	group soundfonts into readable names	2023-03-16 12:23:58 +01:00
Felix Roos	f788d347ec	add envelope to soundfonts	2023-03-15 23:02:05 +01:00
Felix Roos	a33ce67dd4	fix: endless preview	2023-03-15 23:01:56 +01:00
Felix Roos	8a22c5627a	fix: cut glitches due to envelope release trouble	2023-03-15 22:42:03 +01:00
Felix Roos	7b529a30f4	style sounds tab	2023-03-14 22:54:12 +01:00
Felix Roos	4910b34f26	Merge pull request #518 from tidalcycles/fonts add 2 illegible fonts	2023-03-14 21:54:52 +01:00
Felix Roos	6a73b43e3a	add 2 illegible fonts	2023-03-12 21:16:46 +01:00
Felix Roos	b59b26460d	soundfont list curation part 2	2023-03-12 20:48:29 +01:00
Felix Roos	aa324ae25d	start curating the soundfont list	2023-03-10 11:33:55 +01:00
Felix Roos	ff412f6396	level down soundfonts + do not load in prebake (breaks static rendering) + instead load on import	2023-03-09 23:19:19 +01:00
Felix Roos	ac148b2f32	register soundfonts as sounds too	2023-03-09 22:48:40 +01:00
Felix Roos	6f5d096e6d	rename setSound to registerSound	2023-03-09 21:32:40 +01:00
Felix Roos	ff1e6714c6	document setSound api	2023-03-09 21:27:24 +01:00
Felix Roos	41d82eaadf	add cleanup to sound tab	2023-03-09 10:53:35 +01:00
Felix Roos	be6b011204	proper audio node cleanup + cleanup onTriggerSample	2023-03-09 10:46:45 +01:00
Felix Roos	65e48c05f0	sounds onset and offset can be triggered independently + sounds tab now supports mousedown / mouseup to listen	2023-03-09 08:35:20 +01:00
Felix Roos	cee08ea67d	sounds list can now filter out defaults	2023-03-08 00:33:21 +01:00
Felix Roos	35ef26c013	can now pass meta data to setSound + added types for synth and sample + list sample count for samples in sounds tab (as before)	2023-03-07 21:43:01 +01:00
Felix Roos	b08a0b8102	use nanostore for soundmap + rename tab samples to sounds + listed sounds are now reactive	2023-03-06 23:11:09 +01:00
Felix Roos	6059c69995	first draft of soundMap to register keys for s + refactor sampler to use it + refactor synth to use it + add 'source' control + wip: samples tab + wip: webadirt ? + wip: soundfonts	2023-03-05 23:27:37 +01:00