Merged the upstream 1.1.0 version of Ambience into my fork and released it today.

https://github.com/michaelquigley/ambience/releases/tag/v1.1.0

Should be ready to go!

#linux #audio #linuxaudio #studio #vst #vst3 #foss #software

@fortifieduniverse If you're going to maintain a fork maybe rename the project?
@dreamer If I planned to revamp the plugin in a major way, then I would rename it. But this is just a "fork" in the sense that I've added Linux build support, and a couple of quality-of-life improvements.

@fortifieduniverse Releasing someone elses work under the same name is imo a bit disrespectful.

If you're going to fork and continue development on your end then it's best to rename the project.

@dreamer and quite honestly I think it's more disrespectful to change the name and call it something else.

@fortifieduniverse @dreamer Interesting discussion.

To me as a non-programmer (and not knowing any written/unwritten rules in the open source community), keeping the same name seems quite obvious, especially when the Linux-port-purpose is so clear on the Github: https://github.com/michaelquigley/ambience

Isn't it the same with these DISTRHO ports: https://distrho.sourceforge.io/ports.php

GitHub - michaelquigley/ambience

Contribute to michaelquigley/ambience development by creating an account on GitHub.

GitHub

@mosgaard @fortifieduniverse Not really. The distrho ports do not conflict with the original JUCE versions, in this case there is a clear conflict if one installs both.

So I will concede on the name (unless the OG dev complains of course), but you really should change the slug by changing the manufacturer and plugin codes: https://github.com/michaelquigley/ambience/blob/master/CMakeLists.txt#L48-L49

You can also try to clean all of this up (it's kind of a mess imo) and open a PR upstream of course.

I already opened a PR for easy Linux builds.

ambience/CMakeLists.txt at master · michaelquigley/ambience

Contribute to michaelquigley/ambience development by creating an account on GitHub.

GitHub

@dreamer @mosgaard "You can also try to clean all of this up (it's kind of a mess imo)" ... this whole thing is an example of the attitude that keeps people away from the Linux community.

It's not "a mess". It's a choice you can freely choose not to make. I'm not trying to take credit for anyone's (AI generated) work. I literally built the thing because I wanted to use it, made a few tweaks I liked, and shared it. Everyone is free to use it or not.

@dreamer @mosgaard The original author (on their website) clearly says (paraphrasing) "do what you want with it."

If the upstream offers a Linux binary, maybe I'll change the metadata. We'll see what happens.

But approaching like I'm automatically a bad actor... makes me not want to share next time.