musescore-microtonal-edo-plugin VS MuseScore

Link: https://github.com/euwbah/musescore-microtonal-edo-plugin

I just used MuseScore, with eubah's microtonal plugin made for EDOs: https://github.com/euwbah/musescore-microtonal-edo-plugin

This set of plugins seems more flexible (it allows any EDO), and it's more up to date.

Sibelius and MuseScore can both natively notate quarter tones, at least, and I think MuseScore might actually have more options for alternative microtonal accidentals - Sibelius doesn't seem to support custom accidentals, either. Sibeilus comes with a plugin that adds MIDI codes for microtonal playack, but I don't think MuseScore natively supports microtonal playback. There is a microtonal plugin for MuseScore that's endorsed on the Xenharmonic Wiki, which is a great resource for this kind of stuff.

For a shortcut, Musescore has a plugin called colornotes that does this, installable from the GUI. You can alter the color scheme by editing the .js plugin code: https://github.com/musescore/MuseScore/blob/master/share/ext...

It can also print note names inside of each head.

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.