surge VS BespokeSynth

Good stuff!

I started getting in to this at the start of the year. Already had an old, dusty MicroKORG and MIDI interface to use it as a controller, but recently splashed out on a bigger controller as the Korg's tiny keys were hurting me - plus, I wanted something bigger to get better at piano!

A couple of free soft synths I'd recommend are Surge XT, and Vital.

https://surge-synthesizer.github.io/

https://vital.audio/

https://surge-synthesizer.github.io/ and https://asb2m10.github.io/dexed/ should work like a charm.

To get the equivalent of a symphonic orchestra in your computer, the solution is basically money; you buy the instruments you need. In the case of synthesizers, things are much cheaper - if you put in the effort yourself. https://surge-synthesizer.github.io/ is excellent and could even be used if you wanted to make a more retro-style soundtrack.

Instead of Synth1, try https://surge-synthesizer.github.io/ . It's pretty much better in every aspect except for the UI which is going to look a lot more daunting to you ;)

In general, this should only happen when a Program Change message is sent.

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.