nih-plug VS semver

Super cool. Any experience doing audio/synthesis/DSP work with this in a Flutter app? It would be particularly awesome if this enabled building VST plugins with Flutter and one of the Rust crates for VSTs (like NIH-plug or similar).

Looks nice! Rust really is a perfect fit for real-time audio software. At work we also use cpal for audio output, and has found some bugs as well. In my free time I'm tinkering with CLAP plugins for Bitwig, your app looks quite similar to Bitwig Grid which I like a lot. Maybe providing it as a plugin would be a future option.

I don't think Max4Live is not a good choice for building audio plugins. It's a weird platform that was designed for 'institutionalized academic music,' as I once read someone describe it. It's difficult to program in and not efficient. None of my favorite music software is made with it. It's also quite buggy, in my experience. For doing some basic extensions to Ableton Live specifically, beyond what VST allows access to, it's OK, since it's the only official way to do so.

If you want to just dive into DSP using wires and boxes, with some additional code sprinkled in, SynthEdit or Reaktor Core are faster, more fun, and produce better results. If you don't mind C++, check out iPlug from REAPER's WDL codebase: https://www.cockos.com/wdl/ — there are some forks of it.

There's also JUCE. You'll find some people complain about it and some people regret using it, despite it being relatively popular.

There are some Rust things for doing VST (and AU) development. Here's one that I've seen a few things made with: https://github.com/robbert-vdh/nih-plug/tree/master I wouldn't worry too much about the differences between C++ and Rust in this world. Audio software tends to be buggy, so the bar for being considered 'good enough' is pretty low.

There’s nih-plug for VST and CLAP plugins

As it's written in Rust, perhaps it could be implemented as a CLAP plugin. This is a nice framework I've been playing with https://github.com/robbert-vdh/nih-plug/

The potential is both in terms of moving away from proprietary corporate-controlled standards (but also still providing shared wrappers to support those "legacy" :) audio plugin formats) and supporting Rust as a first class development language (via e.g. https://github.com/robbert-vdh/nih-plug).

Yep, Steinberg licensing sucks. I suggest you use nih-plug, it has a much nicer Rust API and supports generating both VST3 and CLAP plugins from your code. I'm only targetting CLAP nowadays, but unfortunately not many DAW's support it.

Your best bet is probably nih-plug.

We increase the version of our product as specified in SemVer and deploy it to production, preferably following good deployment practices to have no downtime.

Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀

Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.

npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.

We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org