MuseScore Studio 4.4.4 is now available!

Cheers everyone,

If you need more info and/or help on the mitigation of corrupted scores, there is a dedicated thread in the "Support and bug reports" forum: https://musescore.org/en/node/372713 :)

@shoogle wrote > Pressing an arrow key while nothing is selected in the score will restore the previous selection instead of jumping to the beginning or end of the score (#24157, #25371)

Here on MacOS 13.5.2 in MuseScore Studio 4.4.4:

• With nothing selected, pressing up arrow does not jump to the start of the score, which is good.

• Regarding "previous selection restoration" I don't see the selection restored when pressing the up arrow. I tried with a single note List selection, a multi-note List selection, and a Range Selection.

Is the new functionality supposed to work with all of those selection types?

The mitigation for empty saved files is great!
I have never suffered from the issue myself, but I can imagine how frustrating it can be.

For the anti-corruption feature—if it doesn’t work after several tries, could it create a new file with duplicate information, but do it as if copying and pasting instead of simply duplicating the file? Copy-pasting into a new score usually works…

Can you fix this one vulnerability?
In the first step, make the musescore smaller
The second step is to drag another window to the side of the screen so that Windows expands this window
The third step is to let Windows automatically change the window size of MuseScore
Next, you'll see that musescore's taskbar isn't fully displayed (which should be correct if it could be collapsed), and there's a large blank space at the bottom of the musescore window, with the supposed mixer at the bottom moving up instead of sitting where it should be.

Did the stability enhancements for this update help to resolve issues with intermittent events of MS4 failing to respond, on larger scores? I've recently encountered an issue, while using either my windows laptop, or, my windows gaming desktop (beefy hardware), where interacting with things within a larger score (for instance, my project is currently 12:45 minutes long, has 28 parts, and is almost 200 measures in length), causes the studio to freeze, windows to paint the window a translucent white color, and add the tag (not responding) at the top of the window. However, if playback was set to play, it would still play the playback accurately while not responding, and when it does come back, it just picks up with the playback bar where it was when the program wakes back up again, and continues as normal.

I also noticed that if I spend a lengthy period of time working on a singular large scale score, progressively, interaction latency becomes unbearably delayed... (ex. attempting to select a note or measure via Shift+ L click, or L click, the selection isn't selected after the command is issued for approx. 800ms - 1000ms... at times it's been even longer. Force quitting the application and reloading tends to resolve the issue, temporarily. however, the intermittent application crashes still occurred no matter how long I was in my scores. This happened across ALL of my scores, during the last build release. I'm going to do some independent testing with this new build to see if it performs any better. But I figured I'd at least make mention of the problem. It seems program related, given that it happened on both my desktop and laptop at around the same frequency.)

"Scroll wheel & scroll gestures are now solely used for scrolling, i.e. not for changing the values of sliders and knobs (e.g. in the Mixer) (#11128)"

This creates a big new problem in the mixer. For those who have a mouse wheel with a gear-like mechanism we could feel how much we were sliding the volume up and down and keep track of it in order to make precise adjustments. Now we can't. And the mixer volume value doesn't have a type-able number like the panning has. So we are completely lost about how much we increase or decrease volume in the mixer.

FYI...
I've noticed this with the previous version of Musescore and this one also, when using the application my cpu% increases about 25%, I've closed all other applications and restarted the computer, with the same result. I can end the application and the cpu% drops back down to the 5-7% range.

Selecting a measure that has a dynamic marking like piano or forte and changing it to something else just puts it over the previous marking, not removing it and replacing it.

Still hadn't fixed the "m" Dynamic marker? ;w;

This Version causes occasional notes to hang sounding indefinitely, until playback is stopped.
When notes are affected, the repro is 100%. Removing the offending note removes the hanging sound.
Recreating the note, recreates the hanging sound.
I even tried deleting the bar and scoring it from scratch, but problem persists.
Seems to be short notes marked staccato.
Rolling back to 4.4.3 cured the problem, so sticking with that for now.

Regarding the corruption of saved scores. I have had this happen a few times, (many years ago).
I use a well known DAW which provides an automatic backup facility, which is also useful for providing history of file changes.
Everytime you save your work, the file on disk is renamed *.ext.bak01 (say) before the save is written to disk.
Any existing backups have their numeral incremented by one, until the maximum number of backups is reached, then they are deleted from disk.
Depth of backup can be specified in Preferences.

Just want to thank you for keeping it current - you guys are great - I wish I could code better. <3

When will the synthesizer be reincorporated?

♥️💪🏻
Thank you musescore team!