MuseScore Studio 4.5.2 patch now available
Hi everyone,
We're pleased to bring you a small update to MuseScore Studio: version 4.5.2.
This update brings stability improvements, bug fixes, and some minor feature improvements. It also introduces playback support for partial ties at repeats and jumps.
You can get the update right away via MuseHub or MuseScore.org, or via in-app notification that we'll push out to existing users of MuseScore Studio in the coming days.
Playback
- Support for partial ties at repeats and jumps (#26178)
- Support for arpeggios with swing rhythm (#22495)
- Fixed regressions in tie and portamento playback in repeated sections (#27472, #27661, #27287)
- Fixed regression where clicking the same measure would not return playback to the start of that measure (#27362)
- Fixed regression where jumps would be taken multiple times when system markings are enabled on multiple staves (#27647)
Engraving
- Improved slur layout across large time signatures (#27631)
- Chord symbols no longer collide with each other horizontally or vertically (#27229, #27139)
- Beat anchor visualizations (blue stripes) are no longer shown in printed or exported scores (#27454)
- Voltas and rehearsal marks only anchor to barlines, not to beat positions within a measure (#27471)
- Large time signatures added in the score no longer appear large in the parts (unless the large style is also enabled in the parts) (#27277)
- Length of 4-measure repeat extender lines is now calculated correctly (#27305)
- Time signatures changes at repeats are indicated after the barline when opening pre-4.5 scores (#27382)
- Irregular measures (excluded from the measure count) are recognized as such when opening MuseScore 1 scores (PR #27746)
- Visibility property of courtesy time and key signatures is preserved on saving and loading scores (#27381)
- Fixed creation of partial ties across repeats and jumps, and improved performance (#27303, PR #27356)
- Incoming partial slurs can now be created from clefs, time or key signatures to the first note of a system (#27325)
- Fixed regression creating incoming partial slurs from an end-repeat barline to a subsequent note (#27325)
- Fixed regression where empty lines added to header or footer text in Format > Style were not rendered on the page (#27519)
- Fixed regression where brass/woodwind falls collided with augmentation dots (#26086)
- Fixed regression where string data was missing for the Bass Viol (tablature) instrument (PR #27380)
Guitar
- Fixed regression where fretboard diagrams were undesirably modified to reflect changes made to chord symbol attached to the same note (#27284)
- Fixed regression where fret conflicts in were highlighted red in printed/exported tablature rather than in MuseScore Studio (#27605)
- Fixed regression where staff lines were not masked by fret numbers in the tablature staff settings dialog and continuous view (#27405, #27442)
- Fixed regression in the ability to extend barlines between linked and unlinked staves (#27455)
Percussion
- When entering notes with the mouse, the percussion note popup now only appears when Shift is held, not Ctrl or other modifiers (PR #27778)
- The Percussion panel no longer allows navigation keys or numbers to be used in pad shortcuts (#27355)
- The Percussion panel will start docked rather than undocked after updating from a pre-4.5 version (#27106)
Interaction
- System markings (e.g. tempos, voltas, rehearsal marks) are no longer duplicated when a time signature is changed (#27228, #27400)
- System markings are always added to an instrument's topmost staff when pasted (affects grand/multi-stave instruments) (#27690)
- Turning off multi-measure rests, or making a hidden staff visible, now unlocks systems that contained multi-measure rests (#27242)
- Text elements follow the mouse cursor more closely when dragged across staves and systems (#27101)
- Accidentals are retained when changing the duration of notes after leaving input by duration mode (#27460)
- Fixed regression where hiding a staff's voice in the Layout panel would remove the staff from the Layout panel altogether (#27752)
- Fixed regression where fingerings couldn't be nudged (i.e. moved) with the cursor keys immediately after being entered (#27219)
- Fixed regression where pressing Return on a text marking would create a system break instead of entering text edit mode (#27347)
- Fixed regression where accidentals attached to notes in the same chord could not be re-ordered horizontally (#27374)
- Fixed regression in ability to create ties across a 'gap' (i.e. between non-consecutive notes) (#27445)
- Fixed regression where right click > Select > Similar in range was unable to select spanner elements such as slurs (#27548)
- Fixed regression where right click > Select > More referred to the first element in the range rather than the right-clicked element (#27126)
- Fixed regression where switching from one VSTi to another wouldn't close the first VSTi's window (#27335)
- Fixed regression where resetting all preferences would not reset changes made in the same visit to the Preferences dialog (#27414)
- Fixed regression where the hyphen-minus (-) key didn't work for lyrics entry with non-English keyboards on Windows (issue still present on macOS) (#16314)
UI
- More detailed action descriptions are displayed in the History panel (PR #27236)
- Help > Online handbook now points to the new Handbook hosted in GitBook (#27234)
- Units like 'px' (pixels), 'mm' (millimetres) and 'in' (inches) have been made translatable (#27418)
- The ampersand ('&') character has been made translatable in the Layout panel (PR #27756)
- 'Swing' and 'Straight' markings have been made bold in the Tempo palette (#27188)
- Fixed regression where range selection rectangle was drawn in the wrong place when hidden staves are present (#27394)
- Fixed regression where undoing hiding of an instrument would not reopen the 'eye' visibility icon in the Layout panel (#27791)
- Small UI tweaks in various dialogs: Transpose (#26896, #26170), Preferences (#27388, #27365), Page Settings (PR #27373)
Accessibility
- Fixed regression where screen readers wouldn't announce the name and first item of a menu (e.g. "File, New") as it was opened (#27079)
- Fixed regression in keyboard control over the anacrusis / pickup measure dropdown in the New Score dialog (#27278)
- Fixed regression in 6-key braille input where it was not possible to type interval signs to create chords (#27581)
Stability
- Fixed crash on dragging the first measure of a score and dropping it back in its original position (#27575)
- Fixed crash when splitting a measure near a lyrics line and the end of a system (#26369)
- Fixed crash after replacing two single-measure repeats with one two-measure repeat (#27731)
- Fixed crashes after clearing (i.e. deleting the contents of) a measure with partial ties and attempting to undo (e.g. with Ctrl+Z) (#27618)
- Fixed crashes when closing a score after dragging or deleting a measure with partial ties (#27714, #27406, #27407)
- Fixed crash when closing a score after unchecking all options in the partial tie popup (#27738)
- Fixed crash when exchanging partially-tied notes between voices within a repeated section (#27252)
- Fixed crash after deleting a start-repeat barline with a partial tie and attempting to undo (e.g. with Ctrl+Z) (#27723)
- Fixed crash after creating a partial tie in the score and then selecting it in the parts (#27710)
- Fixed crash after making a partially-tied note invisible and attempting to undo (e.g. with Ctrl+Z) (#27718)
- Fixed crash when adding instrument change text from the More popup in the palettes (#27233)
- Fixed crash adding tie to a selected range that contains two non-consecutive notes of the same pitch (#27654)
- Fixed crash after entering an ornament with interval below (e.g. mordent) and changing style to Always show cue note (#27749)
- Fixed crash when opening the Layout panel while an empty system text element is present (and disabled creation of such elements) (#27448)
- Fixed crash when pasting in continuous view after copying and exchanging notes between voices in normal view (#27433)
- Fixed crash when accessing the Mixer's three-dots menu > View > Restore the default layout on macOS (#26976)
- Fixed crash on pasting multi-voice passage in continuous view (#27433)
- Fixed crash when dragging a note-anchored line (found in the Lines palette; once entered, it's no longer possible to drag these lines) (#27663)
- Fixed crash and disappearing clef triggered when hidden staves are present in the Layout panel (#27443)
- Fixed freeze when opening MuseScore 3 files with invalid notes on TAB staves (#27736)
- Fixed regression in performance when pasting spanner elements (e.g. lines, hairpins, slurs, etc.) (#27399)
For more information, see the 4.5.2 GitHub Project. And don't forget to check out the 4.5 release video!
Comments
Good work! I love this update.
In reply to Good work! I love this… by coderqc
Thanks! We're glad to hear it!
Awesome. Thank you so much for this update.
Thank You for the upgrade :)
Thanks for the update!😁
Very good update. Thank you.
The counter keeps resetting to zero after playback finishes and determines the end of the file's playback.
I just installed the update and was editing a score. When I saved, it turned the staffs black (lyric sections are fine). Any ideas on how I can fix this?
In reply to I just installed the update… by kottman
Please attach this .mscz file (not an image) for investigation.
In reply to Please attach this .mscz… by cadiz1
I figured out the problem and just tried to delete my comment. When adjusting the staff line thickness, I had inadvertently gotten the decimal point in the wrong place.
In reply to I figured out the problem… by kottman
"When adjusting the staff line thickness, I had inadvertently gotten the decimal point in the wrong place."
This shouldn't happen. I opened a request many weeks ago to set a lower limit for spin boxes to avoid situations like this. I'll update my report with your post. Thank you, kottman.
I need a new Flatpak method since it only installs Musescore 4.5.1, NOT 4.5.2 !!
AND, Musescore 4.5.2 will not run at all with either Snap or Appimage.
Please see the enclosed PDF file:
MuseScore_Appimage.pdf
In reply to I need a new Flatpak method… by caseyennis196
Looks like your OS for whatever reason is not providing a recent version of one of the standard libraries - is this a very old distribution, perhaps? Please start a new thread on the Support forum and say which distribution of Linux you are on - then we can advise better on how to install the library you need.
Musecore, My problem since updating to Musecore 4.5 is that the drums and percusion are not loud enough and they seem to have lost clarity and punch. Turning them up to full volume, using EQ, dynamics etc doesn't seem to make much difference. It is a pity because I love this program and have been using it for years to create my own backing tracks. In the past the drums have been good enough to use directly in my backing tracks but they are no longer useable. Doug
In reply to Musecore, My problem since… by dougjerrems
Nothing should have changed regarding the sounds of the sound libraries. Are you sure you didn't inadvertently change libraries? Check the Mixer, and if you still have trouble, be sure to open a new thread in the Support forum and attach a score where you are having problems - ideally one you have no yet saved in 4.5 so that it can be easily opened in an older version for comparson.
In reply to Nothing should have changed… by Marc Sabatella
Hello, Marc!
I generated this report 1 year ago, and it still hasn't been resolved—no updates, and I don't know if anyone has seen it.
https://musescore.org/en/node/364665
In reply to Hello, Marc! I generated… by sanipachenko
That's a forum post, not an actual issue report on GitHub, so while fellow users here have probably seen it, the developers almost certainly have not.
To me this is not a bug - after playback completes, the position is automatically reset to the beginning of the score, so it seems correct that this would be reflected in the toolbar display. If you're curious what the timing of the piece is, just select the end barline and the playback position will be set there, and that will update the toolbar display.
Glad to see an update with a lot of stability fixes. Personally I use to use Musescore a lot a few months ago but once update 4.5.0 was released is when I stopped using the app. The only reason so is because of how inconvenience the drum notations take up the screen space. While I do know I could just learn the shortcut commands, having the notations on the bottom left was very helpful and took little to no space. Would it be possible on the next update if you could customize the drum layout from the way it is right now and the one from 4.4.4 that I was previously using?
In the meantime, is there a reliable place I could go to download a previous version of Musescore? I've previous made a ticket about it but the response wasn't helpful.
In reply to Glad to see an update with a… by Nicholas Bahamon
You can still use the old percussion panel.
=> Edit => Preferences => Percussion => Use legacy percussion panel.
Previous releases on github: https://github.com/musescore/MuseScore/releases
In reply to Glad to see an update with a… by Nicholas Bahamon
Instead of reverting to the old panel - which is certainly possible as mentioned - I recommend simply setting the panel to only display on command (shortcut is “O”). Now that you can enter notes directly onto the staff, neither panel is actually needed in most cases, even when entering via mouse.
In reply to Instead of reverting to the… by Marc Sabatella
I'm not sure I understand. While I haven't done a lot of drums, the little I have done I simply entered notes directly onto the staff. I wasn't aware there was any other way before this new panel (that many seem to dislike so soundly :-)
In reply to I'm not sure I understand… by TheHutch
Entering notes for unpitched percussion directly onto the staff was never possible prior to 4.5. In the past, you always needed to first click an icon in the drum panel, then you could click onto the staff. Until you selected something in the panel, clicking in the staff would have no effect whatsoever. And every time you wanted to change which note you entered - like from snare to ride cymbal or whatever - you had to move your mouse back to the panel to select the new note, then back to the score, before you could start clicking to enter that note. 4.5 for the first time allows to skip the panel and just enter all notes directly onto the staff, simply by clicking the appropriate line or space just as you would for ordinary pitched staves. You can also leave your mouse in the panel and just click the pads there to enter notes if you prefer seeing the names of the instruments rather than thinking about which staff line is which. And you can also now define as many shortcuts as you like for percussion instruments, rather than being limited to just A-G as in previous releases.
So because of all these improvements, I recommend setting the percussion panel not to display automatically at all. You can now enter notes by clicking directly onto the staff or using a full set of keyboard shortcuts - which again was not possible before. And then for the cases where you want to enter a note you can remember the staff line or shortcut for, you can open the panel by pressing "O".
Thanks for sharing the update! I’m looking forward to exploring the new features and improvements in MuseScore Studio 4.5.2. Always great to see ongoing patches that enhance stability and performance. Can’t wait to see how this version improves the overall experience!
In reply to Thanks for sharing the… by Brian_Tompkin
Marc's quote: "I recommend setting the percussion panel not to display automatically at all. "
Can you expand on that, step by step. For the moment, the O shortcut makes it disappear, but as soon as I enter a new note, it comes back.
I must have missed something, or misunderstood how it works. :(
In reply to Marc's quote: "I recommend… by cadiz1
Sure, just go to Preferences / Percussion, and set the option "Open the panel automatically" to "Never":
The panel will now show up only when you explicitly open it via "O". I find I can do most percussion entry without the panel (drum kit and single-line percussion instruments) through shortcuts and/or direct entry onto the staff. I typically need to open the panel only for the new orchestral "mixed percussion" instrument, where I haven't memorized what's available or the staff line assignments or set up all the shortcuts I might want. Even then, I don't need it very often, since most passages I write are for a single instrument at a time, and once I've entered one note from the panel, I can then enter further notes by clicking the same line/space of the staff. Also, by holding Shift while hovering over the staff, you can see the current assignments for each line, so if I just need a quick reminder rather than a full palette, I can get it that way.
Bottom line, it's pretty impressive how much simpler & faster percussion entry is this way! I just wish the panel itself had been designed to take less space by default, so we didn't get so many people in a hurry to reject it without understanding just how powerful it is.
In reply to Sure, just go to Preferences… by Marc Sabatella
Ah indeed, I got it. I had missed the “Never” option in Preferences/Percussion. I knew about this dialog because several people absolutely wanted to go back to the Legacy panel :) What I had missed was this option... for the new panel!
"so we didn't get so many people in a hurry to reject it without understanding just how powerful it is."
Indeed, when faced with something new, it's a common reflex to want to return absolutely to something known and familiar :)
Nevertheless, this deserves to be explained more clearly, as you have done, because I myself (although I don't input much percussion) was on a wrong track...
This explanation deserves to be on the Handbook (in its own way of course). Unless it's already been done, I haven't yet check.