social.noyu.me

i wonder if they're actually planning on adding midi editing, recording and synthesis in audacity 4 or if they're just gonna be like “use musescore” which amusingly enough actually has an honest-to-god midi piano roll + velocity editor in it these days

bleh, i was kind of excited about the prospect of contributing to audacity 4's midi support, but it turns out this isn't really open-source software any more in spirit, because large parts of the commit history of the core engine look like this now :(

oh, RETRACTION(?): i think this repo may be a clumsy way of letting audacity 4 depend on a copy of the framework/ subdirectory of the musescore source code without moving that into its own git repo just yet; the musescore variant has real commit history

@hikari Huh, so each of these updates is basically just updating a vendored chunk of the tree?

@misty yeah! i think there might be some small changes here and there to allow it to exist independently, but i suspect they are planning to squash those into one commit once they're done

@hikari @misty What about the Tenacity fork?

@jernej__s @misty i would guess they will have no interest in following along with audacity 4 because it's a near-total rewrite i believe

@hikari The retraction aside, I found out recently that Nexus actually Is Like That (https://github.com/sonatype/nexus-public/commits/main/), too.

And that the "OSS" build actually contained plenty of proprietary components, even before the rebranding (and seeming total death of their public repo?).

Bleh.

Fun way to find out while trying to understand the caching behaviour of their RPM backend (which, as it turns out, isn't open source -- as opposed to the DEB one!).