BespokeSynth VS Nebula

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.

(I am a Nebula maintainer.) We recently merged support for gVisor-based services, although it's very new, and I don't know of much experimentation that's been done with it yet: https://github.com/slackhq/nebula/pull/965

Nebula, originally from Slack[0].

Wireguard rightly gets a lot of attention, but Nebula is a really simple and easy to deploy mesh network that is often overlooked.

It does lack a management GUI and that stuff is very much DIY.

[0] https://github.com/slackhq/nebula

Fair enough about the android mobile client... My use case only involves meshing linux appliances across various networks so we only need the nebula core binaries which are under MIT license

https://github.com/slackhq/nebula/blob/master/LICENSE

That's not at all confusing with Slack's Nebula. https://github.com/slackhq/nebula

Sounds like a bunch of your pain points are just related to needing an online CA or ICA. But, looking through the Nebula docs I don't know that it supports things like CRL addresses where you could host the CRL, or OCSP responders. Someone got support for an OCSP responder but never submitted a PR with completed code: https://github.com/slackhq/nebula/issues/72

Nebula is a scalable, cross-platform overlay networking tool focused on performance, simplicity, and security. This portable tool is equally adapted for linking a small number of computers or scaling to connect tens of thousands. It integrates encryption, security groups, certificates, and tunneling into a powerful, cohesive connectivity solution. Thanks for the recommendation go to jmeador42.

Replying to my own comment as I can no longer edit it:

The folks over at Slack had an interesting discussion regarding the the "battle of the VPNs" article published by Netmaker I sourced in my parent comment:

https://github.com/slackhq/nebula/discussions/911

Interesting. I thought recognized the logo, apparently seems to be a commercial support offering of https://github.com/slackhq/nebula and they support the "nebula" iOS app. I had been using for nebula/defined in the past.

Nebula: Is super easy to get running. It uses an interesting angle, working on the service and not just the device level. Unfortunately their NAT support seems to be still quite problematic and I am not going to maintain all those forwarded ports manually. There is a PR to support PCP but even if that ever gets applied I am not sure how well that will play with older routers. While it should be battle proven at slack, the community seems to be not that active. It still has the in-house tool that just got released.

The catch is that I want this to be reliable and fault tolerant, so if some of the game servers in the network go down, the remaining online servers should still always be able to receive broadcasts from any other online server. The servers can also be in multiple geographic locations and I am planning on using a mesh overlay network like Nebula to connect them. Essentially each pair of online servers will likely have a secure link between them that goes directly through the underlying network.