VeeSeeVSTRack VS overtone

There is also VeeSeeVSTRack https://github.com/bsp2/VeeSeeVSTRack

Since some people don’t like the cathedral development style VCV rack uses, I point people to a fork of an older version of VCV rack with two features VCV rack 2 doesn’t have:

* It can run as a VST plugin, so one can use it with their favorite digital audio workstation (DAW)

* The code is BSD licensed

Here is that VST plugin fork: https://github.com/bsp2/VeeSeeVSTRack#downloads

Hete is an old VST port I found. Haven't used it in a while so I don't know if it's stable: https://github.com/bsp2/VeeSeeVSTRack

* The VST fork of VCVrack for a modular synth: https://github.com/bsp2/VeeSeeVSTRack#downloads

I would get a keyboard controller with full sized keys and a 5-pin DIN MIDI out for just over $200, but that can come later.

Again, I prefer the fork at https://github.com/bsp2/VeeSeeVSTRack#downloads because it’s a working VSTi, and because it’s under a BSD (not GPL) license, which has more flexibility in certain circumstances; I remember the arguments around 2001 or 2002 when there were concerns Python’s license was not “GPL compatible”, so I have always found GPL licenses pedantic.

Try vcvrack.com to get a handle on the basic principles.

I set up a drum beat and a pattern on a muted track to control this Eurorack simulator. https://vcvrack.com/

Here's the best way to learn about synthesis. https://vcvrack.com/

Since nobody else has mentioned it, you might want to try VCV Rack. It's a pretty good modular synth in software (bonus, it's free!). You can save and load complete patches, so it scratches that itch to recapture a complex configuration. Lots of good information in its dedicated subreddit.

> Midi being an “artist” tool places it more as a medium like paint.

I’ve used MIDI “as paint”.

Written music using code to MIDI(1), and wrote “cross instrument” music, ie using my keyboard as drum machine.

But these days MIDI is chiefly an archival method for me.

Every time I touch my keyboard is recorded, is much smaller than a comparable audio recording, by design “forced fidelity” in the recording, and I am able to pipe the MIDI format through transcription software (which would be near impossible from an audio recording today).

(1) http://overtone.github.io/

I've never actually used it myself. I've preferred systems that talk to SuperCollider, like overtone, because it's already rock solid and has lots of good DSP built in.

Thanks. I don't know to what extend its "better-because-of-clojure" but I also found overtone https://github.com/overtone/overtone which should be good fun (though the underlying synthesizer is supercollider/C++).

You might want to look at Overtone, which is a clojure environment built on top of overtone, and which integrates with processing and a few other similar things.

https://overtone.github.io/

> I'm fluent in Python but find the use of colons is the real sticking point.

The you'd probably have hated its predecessor which was all about the parentheses: https://overtone.github.io/

It's too bad that superficial stuff like which characters you need to type is holding you back. Getting used to Ruby when you're familiar with Python is no big deal. I would just stick with it

There's a project you may find interesting: https://overtone.github.io/. Besides sound/synthesis stuff, it has https://github.com/overtone/midi-clj library, which allows you to write MIDI as lisp (Clojure, to be precise) code. Emacs has great support for Clojure programming (via Cider), and REPL-based development is perfect for writing music.