MuseScore VS Rdiff-backup

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.

For starters it has a tendency to paint itself into a corner on ENOSPC situations. You won't even be able to perform a restore if a backup was started but unfinished because it ran out of space. There's this process of "regressing" the repo [0] which must occur before you can do practically anything after an interrupted/failed backup. What this actually must do is undo the partial forward progress, by performing what's effectively a restore of the files that got pushed into the future relative to the rest of the repository, which requires more space. Unless you have/can create free space to do these things, it can become wedged... and if it's a dedicated backup system where you've intentionally filled disks up with restore points, you can find yourself having to throw out backups just to make things functional again - even ability to restore is affected.

That's the most obvious glaring problem, beyond that it's just kind of garbage in terms of the amount of space and time it requires to perform restores. Especially restores of files having many reverse-differential increments leading back to the desired restore point. It can require 2X the file's size in spare space to assemble the desired version, while it iteratively reconstructs all the intermediate versions in arriving at the desired version. Unless someone fixed this since I last had to deal with it, which is possible.

Source: Ages ago I worked for a startup[1] that shipped a backup appliance originally implemented by contractors using rdiff-backup. Writing a replacement that didn't suck but was compatible with rdiff-backup's repos consumed several years of my life...

There are far better options in 2024.

[0] https://github.com/rdiff-backup/rdiff-backup/blob/master/src...

[1] https://www.crunchbase.com/organization/axcient

and that should install the latest version, rdiff-backup-2.2.4-2.el8.x86_64.rpm. This is all described in the rdiff-backup README file.

Rdiff-backup - close to what you do currently but at least provides versioning. Based on rsync

as in just a copy of your files? This I would barely consider a backup, more of just a mirror from a point in time. What're you missing by doing this? versions of files, deduplication, and encryption (last one being very important for the best kind of backups, which should be off-site). Just because it's not files doesn't mean it's proprietary. Proprietary would mean secret and undocumented. There are many great options. Borg is my favorite but Kopia is probably better if you use windows, urbackup is an option if you want centralized management of backups and rdiff-backup is if you want something kinda what you have currently but adding versioning but lacks deduplication and encryption.

If you're comfortable with the cli and you want to have your backup in a plain file format with some incremental backups, there's rdiffbackup. It uses rsync under the hood and has worked quite well for me.

Rdiff Backup - Reverse differential backups that uses rsync, linking, and can tunnel via ssh. You get a full current backup with increments available to restore any version of the file with minimal storage space used.

borg is great. we've been using it for the past 3 years to archive hundreds of file-level backups of servers, database dumps and VM images. average size of each borg repo is few GB but there are few outliers up to few hundreds of GB.

borg replaced https://rdiff-backup.net/ for us and gave:

Robocopy is great if you don't have access to rsync. If rsync via WSL2 for instance is an option, I'd personally go with rdiffbackup.