shithub: neindaw

--- a/README.md

+++ b/README.md

@@ -42,10 +42,9 @@

 echo 160 > A/F*/ctl

```

-Pipe sound to /dev/audio in background.  The numbers are how many

-bytes of the output should be read.

+Pipe sound to /dev/audio in background.

```

-while() { for(i in 22050 22050 22050 44100 44100) { audio/pcmconv -i f32c1r44100 -l $i < ../data } } > /dev/audio &

+audio/pcmconv -i f32c1r44100 < ../data > /dev/audio &

```

 Set B oscillator parameters and enable it.

@@ -55,34 +54,19 @@

 echo 1 > B/Enable/ctl

```

+Do a kick.

+```

+echo 0 > Control/Gate/ctl

+echo 1 > Control/Gate/ctl

+```

 Run `cfg` to configure the kick drum in a GUI.

```

 daw/cfg /n/kick

```

-## Description

-A DSP fs presents an interface to create instances of a DSP class by

-reading the `clone` file.  In the resulting directory `metadata` is

-used to read general info about the dsp, `data` is used to supply

-input to the DSP (if it has any inputs) by writing to it, and output

-can be read from it.  The format is raw stream of `float`.

-Each DSP instance, in addition to the mentioned files, provides a file

-tree that reflects the UI elements.  UI elements provide `ctl` file to

-read initial and current, maximum and minimum, step, and may be used

-to write a new value to it.  `metadata` is provided to read/write

-UI-specific metadata key/values.

-Several DSPs may be connected by chaining their `data` interfaces

-together.  If some parameters need to be changed dynamically during

-processing with frame accuracy, it can be achieved by running the

-chain for a chunk of data, changing the parameters, then continuing

-processing.

 ## TODO

- * a program to control DSP through an actual UI in rio

  * `<ui>/value` to watch the changes, add frame offset as well to know

    when it actually changed

  * optional frame offsets for all commands, perhaps that's easier than

binary files a/cfg.png b/cfg.png differ