- commit
- 2efbe4a6598e509febe233685ede0bde18ae955e
- parent
- e85472798c43ad1786ed499adac6bb71af732610
- Author
- Tobias Bengfort <tobias.bengfort@posteo.de>
- Date
- 2023-12-22 07:56
add README
Diffstat
| A | README.md | 32 | ++++++++++++++++++++++++++++++++ |
1 files changed, 32 insertions, 0 deletions
diff --git a/README.md b/README.md
@@ -0,0 +1,32 @@ -1 1 This is a simple tool that does one thing: Arrange audio samples into something -1 2 bigger: -1 3 -1 4 Usage: beat OUTFILE SAMPLERATE BPM BEATS TRACKS BEAT INFILE [BEAT INFILEā¦] -1 5 Example: beat beat.flac 44100 240 8 2 0 kick.flac 2 snare.flac 3 kick.flac 4 kick.flac 6 snare.flac -1 6 -1 7 ## Parameters -1 8 -1 9 - samplerate: all input files must have the same sample rate -1 10 - BPM: beats per minute -1 11 - beats: total number of beats -1 12 - tracks: to avoid clipping, the samples are multiplied by `1/sqrt(tracks)` -1 13 -1 14 The rest of the parameters are pairs of beats and file paths. -1 15 -1 16 ## Typical usage -1 17 -1 18 I use this in combination with some other tools: -1 19 -1 20 - record samples with audacity -1 21 - add effects to samples using `sox` (e.g. reverb or distortion) -1 22 - arrange samples using `beat` -1 23 - keep the parameters for `beat` in a text file -1 24 - orchestrate everything using a Makefile -1 25 -1 26 For bigger projects I may have multiple levels, where samples are first -1 27 combined into bigger samples, then have effects applied to them, and then get -1 28 combined into the final song. -1 29 -1 30 This allows me to do audio production in the same way I create software: By -1 31 manipulating text files. `beat` acts as something like a linker from that -1 32 perspective.