overtone VS MuseScore

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.

In that case, please ask for help on the official Support forum on musescore.org where you can attach the score itself and people should be able to take a look.

If you continue to have trouble, best to ask for help on the official Support forum on musescore.org and attach your score along with precise steps to reproduce the problem, so we can understand and assist better.

Is this what also led to https://github.com/musescore/MuseScore/issues/17663? If so I definitely urge you to spend the couple of minutes to test with a nightly build so we can known it is truly fixed for your case and not illustrate the other case that had been reported. As mentioned, testing nightlies is simple; they don’t interfere with normal installations at all.

Sorry, I don't know what "both buttons" means. There are buttons on the home page of musescore.org, buttons on the Download/Software page - both with and without Muse Hub - buttons for older versions, buttons for nightly builds, buttons for mobile apps, buttons within Muse Hub, probably others too. Please describe *exactly* what you are doing, step by step - the URL of the page you are on when you see the button, the text on the button you are clicking - and the exact text of the error you see.

Musescore seems to be the new standard

Not that I need to prove anything, but for anyone curious, here's a composition I created using the music notation software I help develop and support on my Chromebook. If you hit the play button on the composition, you'll hear the multitrack recording I created on my Chromebook as well, with my students singing the various parts. The piece was created for my online course teaching counterpoint, developed completely on my Chromebook. Here is a video from my most recent - the video is done from the Chromebook and the software managing the multicamera layout and screen share is software I developed on my Chromebook. And here is the online community I manage from my Chromebook.

I actually filed a github feature request for this exact thing yesterday, link here. On the principle that someone with more skills that me can get interested sooner than I can get good enough at C++ to do it myself.

Muse Hub is used by programs other than MuseScore, so it really doesn't make sense to offer it from there directly. Plus musescore.org was never designed to act in that way - downloads are pretty much always hosted elsewhere. Beyond that, I don't know all the ins and outs of how specific domains might be chosen, but I assume someone intelligent enough to set that up onows a ton more about it than I do, so I don't worry about it.

Unfortunately, MuseScore 4 seems to be missing that feature.

Sorry to hear you're having trouble! Definitely, we'd need the MSCZ file to be able to investigate. Normally we ask that people first post to the official Support forum on musescore.org to get confirmation before opening an issue on GitHub to report a bug formally, but it sounds like you've got things pretty well figured out in terms of having precise steps to reproduce the crash reliably, so I would encourage you to just go straight to the issue tracker on GitHub - https://github.com/musescore/MuseScore/issues