Arpeggio style editor seems to be newly broken in 4.5.0
I'm now finding, new to 4.5.0, that I cannot drag an arpeggio symbol relative to the notes that it is attached to, nor can I use the style editor to increase Distance to note.
This is important for guitar notation, because normally one places the arpeggio symbol outside of the fingering - but now I cannot move the arpeggio symbol away from the notes to make room for the fingering numbers. Example shown below, which I call "fingeris obscuris." :)
In fact, NONE of the arpeggio style editor functions has any effect: not Distance to note, nor line thickness, nor Hook length.
I'm running: OS: Ubuntu 24.10, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250721848, revision: 7c55023
Comments
mac OS Sequoia 15.3.2
It works very well for me, see the attachment.
Sorry for my english but I don't know the language.
Just thought I'd bump this with a comment. It's really annoying that I can't slide the arpeggio symbol to the left any more to make room for the fingering notation! :) In the Linux app. Apparently not a problem on other platforms.
In reply to Just thought I'd bump this… by sammyjava
"I'm now finding, new to 4.5.0, that I cannot drag an arpeggio symbol [...] In the Linux app. Apparently not a problem on other platforms."
1. It's not a platform issue; I can reproduce it with Windows (and most likely with Mac as well).
2. For the record, this is indeed a regression. I just checked. But it's not since version 4.5.0, but since version 4.4.0. With version 4.3.2, it was still possible to drag arpeggios.
3. Please report it on GitHub: https://github.com/musescore/MuseScore/issues
In reply to "I'm now finding, new to 4.5… by cadiz1
Will do. I thought that I couldn't even use the positioning dropdowns under Properties -> Appearance, but I guess I didn't try those before. I marked up a little image above showing that the Arpeggios attributes don't work. I'll hit GitHub issues, thanks for confirming on Windows.
In reply to Will do. I thought that I… by sammyjava
Ahhh actually it was reported on GitHub on 25 December 2025.
https://github.com/musescore/MuseScore/issues/25920