BespokeSynth VS scheme-for-max

https://github.com/BespokeSynth/BespokeSynth

BespokeSynth takes the concept of a modular synthesizer and expands it so that the application is less just a synth and more a complete modular DAW. I've used it to create MIDI/audio workflows that I couldn't get exactly the way I wanted in Ableton or FL Studio. It also has a module for doing audio processing livecoded in Python that I'm just starting to scratch the surface of.

Video from the creator covering I Feel Love in BespokeSynth: https://www.youtube.com/watch?v=kzYUgPMMpts

https://www.google.com/search?q=awesome+generative+ai+site%3... ; #GenerativeArt #GenetativeMusic

- BespokeSynth DAW: https://github.com/BespokeSynth/BespokeSynth :

> [...] live-patchable environment, so you can build while the music is playing; VST, VST3, LV2 hosting;

Then I realized bespoke sync is also written in C (https://github.com/BespokeSynth/BespokeSynth) , and I learned about the ninja build system (which is what ysfx uses to compile JSFX).

Today I'm looking at a couple open source projects that are dear to my heart: OpenParliament API and BespokeSynth. If you've followed my work last term for OSD600 you've seen me write about my work on Bespoke already, which is a modular software synth. OpenParliament, on the other hand, is a great site with easy to consume information about Canadian government, the API for which I'm taking a look at today. This is part of my work for SPO600, or Software Portability and Optimization, so expect more on that soon! For now let's dive into these repos and how contributing to them works.

In the final installment of my efforts to bring midi import and export to BespokeSynth (part 1 and part 2 here) I'm working my way through the details of handling midi in Juce, with the added layer of having some Juce functionalities handled by Bespoke.

In last week's post I discussed my plans to implement midi import and export in BespokeSynth, a modular synth making app that's built on JUCE, an open source framework for developing VST plugins. So far I've been chipping away on a few fronts: making a demo app to try implementing midi import and export separately from Bespoke, looking at examples of components from other apps that do what I want to, and looking at how Bespoke already uses some components I'll need to implement it.

For my release 0.4 I'm going to be working on BespokeSynth which is a neat program my prof showed me earlier in the semester.

Mine is Scheme for Max, now on it's fourth open source release, but really written so I could make computer music how I want to. It's an extension to the popular Max/MSP visual music programming environment that embeds an s7 Scheme interpreter and provides a substantial API/FFI to Max. It allows you to script Max (and thus also Ableton Live) with Scheme, enabling interactive coding, algorithmic music, live coding, macros, and just much more pleasant scripting than in JavaScript. It locks in with the scheduler so you can even use Scheme powered sequencers within Ableton Live alongside regular Live tracks, and you can build sophisticated Live control surfaces using the Live API.

Github page here: https://github.com/iainctduncan/scheme-for-max

The project page is here, with links to lots of documentation I've done: https://github.com/iainctduncan/scheme-for-max

To download Scheme for Max and for tutorials, documentation, and the cookbook, visit the GitHub page: https://github.com/iainctduncan/scheme-for-max

If you like things like Janet, you might also like s7 Scheme. It is also a minimal Scheme built entirely in C and dead easy to embed. I used it to make Scheme for Max and Scheme for Pd, extensions to the Max and Pd computer music platform to allow scripting them in Scheme. (https://github.com/iainctduncan/scheme-for-max) Janet was one of the options I looked pretty closely at before choosing s7.

The author (Bill Schottstaedt, Stanford CCRMA) is not too interested in making pretty web pages, ha, but the language is great!

Project page: https://github.com/iainctduncan/scheme-for-max

I created Scheme for Max and Scheme for Pure Data. They are extensions to the Max/MSP, Ableton Live, and Pure Data computer music environments that embed an s7 Scheme interpreter in the host so that you can script, automate, and live code the hosts with s7, a Scheme from the CCRMA computer music center at Stanford and the same one used in the Snd editor and the Common Music 3 algorithmic composition environment. This allows you to do things like write algorithmic music tools, sequencers, and use the Ableton Live API in Scheme, including with Common Lisp style macros. It has an API for integrating with Max to share data structures, hook into the scheduler, run in the high priority thread, and so on. S4M allows you to do all the goodness of high level music programming in a Lisp, without losing the ability to use modern commercial tooling and instruments. It's my thesis project for a Masters in Music Technology with Andy Schloss and George Tzanetakis at the University of Victoria, and I plan to continue to a PhD working on it. I tried submitting twice, but it never made the page, which surprised me a bit given Lisp interest here.

The github page is here: https://github.com/iainctduncan/scheme-for-max

The youtube channel with various demos is here: https://www.youtube.com/c/musicwithlisp