Natural Key Signature & Misc
Generally enjoying Musescore, but there are a few things I'm having a hard time doing.
Is there a way to create a key signature of naturals on in first bar? The only way I could get it to somewhat work was by adding a bar before, having a different key signature, making that bar invisible, and then changing to the C major in the second bar. But that's clunky and requires a lot of fiddling, so I was wondering if there was an easier way.
Edit: I found a workaround by adding a key signature to the master palette, but the spacing is wonky, so another way would still be good.
Also notes beamed across staves don't respect the key signature of the staff they were moved to, which adds accidentals and clutter. Plus the articulations are appearing too low with "Below Chord", and none of the options puts it right below the note. Both can be fixed manually by dragging/marking invisible each time, but would be very time consuming. Is there a way to fix the defaults?
|Screenshot 2022-05-16 170055.png||21.5 KB|
Key signatures wouldn't normally contain naturals, so whatever you are trying to do presumably counts as a custom key signature. I assume that;s what you mean about adding a key signature to the master palette. Spacing is under your control; that's part of what makes it custom.
It's true that cross-staff notes mostly act as though they are on the staff they "belong" too. Normally that wouldn't be an issue but would indeed if creating polytonal key signatures.
I couldn't reproduce the bad articulation placement in a simple test, but probably it has to do with other details of your score (e.g., some style setting). If you attach the actual score rather than just a picture, we can understand and assist better.
In reply to Key signatures wouldn't… by Marc Sabatella
Thanks for the answer. With a bit of trial and errort the custom key signature works well enough, and I understand why this very specific scenario doesn't justify adding a feature.
Is there a way to add cross-staff beams without cross-staff notes? Because while it makes sense that cross-staff notes belong to their original staff, it seems reasonable to want different staves alongside functional cross-staff beaming.
A fresh install and new score didn't change the spacing issues. The quickest way to replicate that issue is to add two eighth notes to the lower staff, add an accent or similar articulation to the first note, change its anchor to "Below Chord", and ctrl-shift-up the second note to the upper staff.
In reply to Thanks for the answer. With… by Max Pearce Basman
I'm not sure what distinction you'd make between when it makes sense for these notes to live on the same staff vs different, seems that would just confusion. I think it's just a bug that cross staff notes don't dis[play correctly in the presence of different key signatures. But if you have some other use case in mind where the distinction would matter, go ahead and post it for further discussion.
And again, with regarding to the spacing, definitely post the score with that problem. As mentioned, I couldn't reproduce it in a score I created, so it is probably something specific to something you are doing that's different from what I am doing.
In reply to I'm not sure what… by Marc Sabatella
Ah, I thought that the "belonging to lower staff, so using its settings" thing was intentional. I look forward to seeing the bug fixed, though I understand it's probably not at the top of the list.
Here's a score with the spacing issue, and what it looks like for me.
In reply to Ah, I thought that the … by Max Pearce Basman
As far as I know there is no issue in the official issue tracker for the local key signature issue, so be sure to create one - that's the first step in getting this looked at.
I can reproduce the issue with that specific file. I guess it depends on the specifics of the notes & intervals and stem length and beam position, as it worked fine in my test - try quarters instead of eighths, for example. This seems to be a case of #310125: Articulations misplace in cross-staff notation, so this one is already reported. And it seems to already be fixed for MuseScore 4.
Workround for now appears to be to force the stem up rather than leaving it as auto.