-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
26 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# DaisySP | ||
|
||
OWL patches in C++ can use objects from the [DaisySP library](https://electro-smith.github.io/DaisySP/index.html) directly. While it was written to run on Daisy platform, there's nothing preventing compatibility with OWL patches in its code. | ||
|
||
|
||
## DaisySP patch structure | ||
|
||
Integrating DaisySP into an OWL patch takes just a few simple steps: | ||
|
||
1. Import main library header by adding `#include "daisysp.h"` | ||
|
||
2. Import libray namespace into current patch with `using namespace daisysp;` statement | ||
|
||
3. Add required objects as patch members. It's also possible to use object pointer and create objects dynamically in constructor to delay memory allocation. | ||
|
||
4. Call each object's `::Init()` method in patch constructor. Most objects require passing sample rate, so it becomes something like `object.Init(getSampleRate());` | ||
|
||
5. Update object parameters with `object.Set*()` calls inside your patch's `processAudio(...)` method | ||
|
||
6. Generate object audio by calling `object.Process(...);` inside a for-loop once for every sample. | ||
|
||
|
||
## Example patch | ||
|
||
[Filthy kick](https://www.rebeltech.org/patch-library/patch/FilthyKick) shows how to use all of the above. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters