M. Edward (Ed) Borasky
“I’ve never seen a happy clam. In fact, most of them were really steamed.” ~ M. Edward (Ed) Borasky
I presented a brief status report to the Silicon Valley Forth Interest Group for their annual Forth Day meetup yesterday (2024-11-16). The video should be up on YouTube in a day or so. The slides are at https://github.com/AlgoCompSynth/CLAMS/blob/main/presentations/CLAMS-quest.pdf.
I've made some design decisions and have a preliminary roadmap.
Once the first integrations are done, I am planning to develop the CLAMS Forth Domain Specific Language and an album-length collection of electronic music concurrently. After that, the only integration I'm sure I will be doing is a Raspberry Pi Zero 2 W with USB audio. I may also do USB MIDI and Bluetooth audio / MIDI, but neither of those is as important to me as USB audio.
Two more audio libraries for Arduino have come to my attention:
I haven't posted much here other than code for the past few months. Like many folks, I was caught off-guard by the Raspberry Pi Pico 2 / RP2350 announcement on 2024-08-08. That led to me acquiring several boards from some of the partners, and a complete rethinking of my development environment and long-term goals for the project.
The development environment is working mostly to my satisfaction. There are some enhancements I want to make, but I can build projects for RP2040 and RP2350 boards and some other Arm Cortex M and some ESP32 boards.
And that leads into the goal shift. Portability is now highly desirable. I want to be able to run on ESP32-S3, -C3 and -C6 boards, Teensy 4.1 boards, and Electro-Smith Daisy boards in addition to RP2040 and RP2350 boards.
The only development framework / platform that supports this diversity is Arduino. PlatformiO can do it, but it uses Arduino under the hood, adding a number of moving parts. So I need to develop a Forth that works on all these boards using the Arduino tools.
The Teensy and the Daisy already have both Arduino support and extensive audio libraries, so all I need to build there is the Forth control structure. For the other boards, there are two excellent libraries I can use: Arduino Audio Tools and AMY. My plan is to have both, assuming there is space in the flash on the boards.
Finally, I am going to restructure this repository using Git submodules. There will be one submodule for the development environment: https://github.com/AlgoCompSynth/CLAMS-devel.git, one for the documentation: https://github.com/AlgoCompSynth/CLAMS-doc.git, and one for the Forth itself: https://github.com/AlgoCompSynth/CLAMS-Forth.git.
CLAMS is a text-based interactive environment for composing and
performing music and visuals on a Pimoroni
PicoVision.
It can be made to work on other boards using the RP2040 microcontroller,
but you will need additional hardware.
CLAMS is a domain-specific language built on a Forth compiler /
interpreter. The user connects to the board via a serial connection and
enters CLAMS / Forth code interactively.
“Premature optimization may be the root of all evil, but it is damned fun!” ~ M. Edward (Ed) Borasky
Forth https://www.forth.com/starting-forth/ is an extensible interactive operating system. It supports editing, assembling, compiling, debugging and running real-time tasks from a terminal.
Forth is efficient. A well-designed Forth will usually run a task at
no worse than half the speed of a hand-optimized assembly version.
CLAMS will have several optimizations built in for the ultimate
speed.
Forth is lean. There are very few concepts to learn, there is minimal run-time overhead in RAM, and the whole package takes up much less flash space than MicroPython or CircuitPython.
Not really. CLAMS is an extended subset of the standard. It won’t
contain all of the standard’s core word set, and it will contain some
extensions to support real-time audio and the RP2040 hardware.
The RP2040 is both limited and complex. It uses the ARM Cortex M0+ instruction set, which doesn’t even have a 32-bit multiply that produces a 64-bit product. Division is handled by a co-processor. There are also co-processors for programmable I/O and interpolation / multiply-accumulate operations.
That said, if a word in CLAMS does exist in one of the standard word
sets, it should function the way it does in the standard. The search
order word set will be implemented, and all of the specialized
co-processor operations will be in specialized word sets.
Again, not really. There are a number of other micro-controller music
boards, most notably the Electro-Smith
Daisy
and the Rebel Technology
OWL
platforms. But they have their own SDKs, so there’s not much need to
port CLAMS to them. There are also a number of audio projects that use
the Teensy® USB Development
Board, which has a
comprehensive audio
library.
Also, the Daisy, OWL and Teensy processors are all more powerful than
the RP2040.
By contrast, there’s not much for the Raspberry Pi Pico / RP2040. There
are some simple demos, a few do-it-yourself hardware offerings, and
there’s the Allen Synthesis
EuroPi,
a Eurorack module with an open source MicroPython software platform.
CLAMS will be a different approach.
The overall concept is an interactive language for making music on Raspberry Pi Pico / RP2040. I’m aiming for ChucK (Salazar et al. 2014) semantics with Forth syntax - a single text-based language to implement both the definitions of synthesized instruments and the sequences of sounds they make, intended for live coding / algorave performances.