ref: 273708af801f439567333d6f77469af66edfd0cc
parent: 92275f3b95309a13c8e1aa136bb62e7f6ea71458
author: Sigrid Haflínudóttir <ftrvxmtrx@gmail.com>
date: Mon May 11 15:41:58 EDT 2020
add piper readme
--- /dev/null
+++ b/piper/README.md
@@ -1,0 +1,33 @@
+# piper
+
+WIP.
+
+```
+daw/kick_drum -s kick -m /n/kick
+daw/ay -s ay -m /n/ay
+games/orca -u /fd/3 |[3] daw/piper /n/kick /n/ay
+```
+
+Instances are created by piper automatically, but there is no
+automatic mixer connection yet, so still need to run `mixfs` and do
+manual `audio/pcmconv -i f32c1r44100` for each `data` entry.
+
+Piper accepts simple commands like so:
+
+```
+;00C4d8
+```
+
+`;` is for UDP message, `00` is first instance of the first group
+(`/n/kick/0`), `C4` is the note, `d` is velocity, `8` is duration.
+Notes can be connected with `:` like so:
+
+```
+;00C4d8:!C2df
+```
+
+In this case the second note is for the `B` oscillator of the kick
+drum, and `!` is a way to "negate" the frequency value, so in fact
+it's `C2` *negative*.
+
+Commands can be separated with `;`.