| .. | ||
| common | ||
| fx_ap1 | ||
| fx_ap2 | ||
| fx_balance | ||
| fx_bitcrush | ||
| fx_chorus | ||
| fx_clip | ||
| fx_comb | ||
| fx_comp | ||
| fx_delay | ||
| fx_dist | ||
| fx_drive | ||
| fx_eq_3band | ||
| fx_flanger | ||
| fx_fuzz | ||
| fx_hp1 | ||
| fx_hs1 | ||
| fx_lp1 | ||
| fx_ls1 | ||
| fx_mm1 | ||
| fx_mm2 | ||
| fx_noise_gate | ||
| fx_notch | ||
| fx_one_pole | ||
| fx_pan | ||
| fx_phaser | ||
| fx_reverb | ||
| fx_satur | ||
| fx_slew_lim | ||
| fx_svf | ||
| fx_trem | ||
| fx_vibrato | ||
| fx_wah | ||
| fxpp_ap1 | ||
| fxpp_ap2 | ||
| fxpp_balance | ||
| fxpp_bitcrush | ||
| fxpp_chorus | ||
| fxpp_clip | ||
| fxpp_comb | ||
| fxpp_comp | ||
| fxpp_delay | ||
| fxpp_dist | ||
| fxpp_drive | ||
| fxpp_eq_3band | ||
| fxpp_flanger | ||
| fxpp_fuzz | ||
| fxpp_hp1 | ||
| fxpp_hs1 | ||
| fxpp_lp1 | ||
| fxpp_ls1 | ||
| fxpp_mm1 | ||
| fxpp_mm2 | ||
| fxpp_noise_gate | ||
| fxpp_notch | ||
| fxpp_one_pole | ||
| fxpp_pan | ||
| fxpp_phaser | ||
| fxpp_reverb | ||
| fxpp_satur | ||
| fxpp_slew_lim | ||
| fxpp_svf | ||
| fxpp_trem | ||
| fxpp_vibrato | ||
| fxpp_wah | ||
| synth_mono | ||
| synth_poly | ||
| synth_simple | ||
| synthpp_mono | ||
| synthpp_poly | ||
| synthpp_simple | ||
| README.md | ||
Examples
Each subfolder contains an example application, except the common folder, which contains common code for all examples.
In order to build an example just cd to *example*/*platofrm* and use the following platform-specific instructions.
Building for any platform requires a recent enough version of GNU Make installed.
VST3
Prerequisites
Windows (via MSYS2/Mingw-w64), macOS, and Linux OSes are supported. Building tested with GCC, probably also works with Clang.
You also need to download the VST3 SDK and place it in the same folder as the Brickworks folder, or otherwise edit common/vst3/vst3.mk and change the VST3_SDK_DIR variable to point to the correct directory.
Build
In order to build just type make. You'll find the resulting VST3 directory in build/example.vst3.
Installation
If all went fine, you can install for the current user (i.e., into the user VST3 folder) by invoking make install-user.
On macOS and Linux you can also install for all users (i.e., into the system VST3 folder) by make install.
Web
Prerequisites
You need Clang with WebAssembly target support and OpenSSL installed.
Build
In order to build just type make. You'll find the resulting output directory in build/web.
Running
The output files need to be served over HTTPS. A self-signed certificate is generated in the output directory (hence the OpenSSL requirement) to make it possible to run an HTTPS-enabled web server, e.g. http-server -S, directly on/from the output folder.
Daisy Seed
Prerequisites
Building and firmware upload was only tested on Linux. You need arm-none-eabi-gcc (for building) and dfu-util (for firmware upload) installed.
You also need to clone libDaisy, cd to it, and run make. You should either place it in the same folder as the Brickworks folder, or otherwise edit common/daisy-seed/daisy-seed.mk and change the LIBDAISY_DIR variable to point to the correct directory.
Build
In order to build just type make. You'll find the resulting output files in build.
Firmware upload
To upload the firmware:
- branch the board to the uploading machine via USB;
- put the board in DFU mode by pressing BOOT, then RESET, then letting go of RESET and then of BOOT;
- type
make program-dfu.
Effect examples report output parameter values and CPU usage statistics via USB serial. You can read the output by, e.g., screen /dev/ttyACM0.
Thanks
Thanks to Mads Kjeldgaard for publishing instructions to build for the Daisy Seed and uploading the firmware.