Idle thinking about synthesizers:
Are there any components that CAN'T be described as a collection of the following items as inputs/outputs?
* Level/Voltage (-1.0 to +1.0)
* Frequency (in Hz)
* Trigger (boolean)
Conversation
Fixed LFO? Output Level.
Step Sequencer? N Level inputs, 1 Trigger input, 1 Level output
Variable LFO? 1 Frequency input, 1 Level output
Fixed LPF? 1 Level input, 1 Level output
Variable LPF? 1 Level input, 1 Frequency input, 1 Level output
1
Analog or digital? In the digital domain, I ended up with synchronous state machines, running at two rates. One rate audio path, one rate control path. Some writeup here: zwizwa.be/rai - If you're into embedded, also check out axoloti.com
1
Definitely! I'm planning digital for now, and would like to take what I'm working with and move it to an embedded device, once I figure some stuff out.
It's mostly just a learning project for me :)
Thanks for the links!
1
1
Johannes did a good job with Axoloti, finding a balance between usability and DSP geekery. It's similar to a Nord Modular. Pure data is definitely DSP geekery and definetly something to check out. I played with that a lot.
Max/MSP and Pure Data are both fundamentally dataflow-style languages, but specifically as control/audio languages are described as being in the “Patcher” family en.wikipedia.org/wiki/Pure_Data
1
There’s effectively a 1:1 relationship between the Patcher languages and how you’d control a network of synthesizing instruments, or for that matter, how systems like Ableton or Reason work
1
1
Show replies
Also when I grow up I want to put Rust on the Axoloti board. You might beat me to it though. In fact this would be a great Rust teaching toy.
1
Talked to Johannes. More boards are available soon. Seriously this thing needs a layer of Rust.
2