overtone VS MuseScore

Are you talking synthesizers? If yes, then Overtone is a great project for that, if you are OK with using clojure.

I've never actually used it myself. I've preferred systems that talk to SuperCollider, like overtone, because it's already rock solid and has lots of good DSP built in.

Thanks. I don't know to what extend its "better-because-of-clojure" but I also found overtone https://github.com/overtone/overtone which should be good fun (though the underlying synthesizer is supercollider/C++).

You might want to look at Overtone, which is a clojure environment built on top of overtone, and which integrates with processing and a few other similar things.

https://overtone.github.io/

> I'm fluent in Python but find the use of colons is the real sticking point.

The you'd probably have hated its predecessor which was all about the parentheses: https://overtone.github.io/

It's too bad that superficial stuff like which characters you need to type is holding you back. Getting used to Ruby when you're familiar with Python is no big deal. I would just stick with it

There's a project you may find interesting: https://overtone.github.io/. Besides sound/synthesis stuff, it has https://github.com/overtone/midi-clj library, which allows you to write MIDI as lisp (Clojure, to be precise) code. Emacs has great support for Clojure programming (via Cider), and REPL-based development is perfect for writing music.

overtone, in clojure and using the SuperCollider engine

It's overtone.live that has a problem with windows, as documented here . It's used in the overtone playground project and that's probably the reason why I couldn't get it to work.

Follow the GitHub directions and you can find the link needed to build the label as: https://github.com/musescore/MuseScore/releases/download/v4.0.1/MuseScore-4.0.1.230121751.dmg

According to this thread, MuseSounds isn’t even a separate process, but it’s loaded dynamically. That settles the shared-memory discussion since they operate as one program in a shared address space.

I looked into the source, and from my perspective it looks like the only purpose of the dll API (it's inside libhandler.h) is to avoid releasing the source. There is only ONE implementation, the dll is ONLY used by Muse Score, and there is also no documentation on this API... The lib, MuseSamplerCoreLib.dll, is installed to Windows/System32. The sample format is proprietary I guess, but internally uses the open source opus codec (so sample data can be extracted by just using opusdec.exe from opus-codec.org) Here is some feedback from the team on the issue: https://github.com/musescore/MuseScore/issues/15706 https://musescore.org/en/node/340466

Under the GPL they don't owe you specifications. Under the GPL they don't owe you documentation. Under the GPL they don't owe you a build how-to or integration instructions. Per the GPL, all they owe you is the code, and that's here. If the interface you are talking about is in that repo, then they've met their obligation. The GPL doesn't say they have to make it easy to use their interface or explain what it does, it says they owe you the code that implements it.

I've been working on some version of this since May 2019. It is a web app that allows writing out music for the Highland bagpipe.

While it uses the same notation as normal music, bagpipe music tends to have a greater focus on gracenotes (embellishments). Most music software does not deal with this very well (e.g. MuseScore just displays a list of every single possible embellishment, of which there are hundreds [1]). PipeScore instead takes advantage of the fact that the form of many embellishments is dependent on the notes adjacent to it, allowing it to reduce the number of options down to just 13.

[1] https://github.com/musescore/MuseScore/blob/2b428c00c9df65c3...

musecore is opensource and supports tab playing and editing alongside notation: https://github.com/musescore/MuseScore

For all there musicians out there: MuseScore (https://musescore.org)

I am running this Musescore and Muse Hub on Kubuntu 22.10 and the Muse Hub doesn't work. I don't know how prevalent this problem is, but it looks like the bug is being tracked here: https://github.com/musescore/MuseScore/issues/14125

It's important to note that the new leadership is Muse Group, the developers behind the MuseScore software, which is itself licensed under GPLv3. Muse Group are a FOSS proponent; it would be very out-of-character for them to attempt to shift the software to a proprietary license.