Clef change at start of score converted to mid-measure on save/reload with modified system barline
Reported version
3.2
Priority
P2 - Medium
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
Yes
Workaround
No
Project
I've some scores with 8va treble clefs. It worked perfectly over the last months, but I have some recently created scores where the 8va treble clef is not saved correctly in staffs 2,3 and 4. It's shown correctly after editing (see screenshot), but after closing and re-opening the file it shows a regular treble clef, and a small 8va clef after the time signature.
| Attachment | Size |
|---|---|
| 8va-clef-before_saving.jpg | 18.27 KB |
| 8va-clef-after_saving.jpg | 29.08 KB |
| Aria_Sancti_Huberti.mscx | 93.65 KB |
Comments
You're using an old version of MuseScore 3.0.5. This has been fixed. Upgrade and the best way to fix this is to reenter them after you upgrade, it will not automatically fix the bad display.
In reply to You're using an old version… by mike320
this occurs on 3.2: OS: Fedora 29 (Server Edition), Arch.: x86_64, MuseScore version (64-bit): 3.2.3., revision: d2d863f
Did you follow the advice: reenter them after you upgrade, it will not automatically fix the bad display?
In reply to Did you follow the advice:… by Jojo-Schmitz
yes, I did re-enter them many times on the latest version. Trying pulling the 8va clef on the regular clef, and on the first measure. It's always the same, it looks correct after editing, but it is not saved when saving and re-opening the score.
Please attach the "corrected" score.
In reply to Please attach the "corrected… by mike320
@mike320 attached
Very strange score, claims to be 4 times Horn in Es (Eb), but is non-transposing.
Yet has settings for concert and sounding clef, both G8va, but not for the the instrument itself, instead in the first measure
In reply to Very strange score, claims… by Jojo-Schmitz
Maybe I'm doing something wrong, but it has worked that way for me in the past with Bb and Eb scores. It's for pless and parforce hunting horns. They're both noted in C. I create a new score with the number of instruments, and do adjust the transpose to 0, because it would show sharps otherwise. The pless horns are always in Bb, noted in C. The parforce either in Bb or Eb, also transposed to C, with the 8 below the clef. So i've pulled a clef with 8 from the left on the default clef, then marked all notes for the instrument and moved it back one octave.
Is that not the right approach?
Better leave them transposed and use the Concert Pitch button. Or dont use Eb Horns but C Horns
In reply to Please attach the "corrected… by mike320
did that help?
Rather a question to you
In reply to Rather a question to you by Jojo-Schmitz
@Jojo-Schmitz my question was regarding the score with the 8va clef saving issue. I've attached - as requested - the current edited score, edited with 3.2.3, which still shows the problem that should have been fixed.
Regading your inputs for transposing, thanks for the hints, I'll just use C Horns in the future. Thanks a lot. But the issue I was raising this ticket for still persists.
True. Your changes to transpositoning might contribute to the issue, but this really shouldn't cause this, if dealt with properly in the code I guess.
I don't understand though why it is behaving that way, hopefully someone else find out
Interesting enough I have a similar score started with 3.2.3, where the problem doesn't occur. But same basic setup, 4 Eb Horns, removed transposing, etc.
And I have about 35 scores with Horn in Bb, where the problem didn't occur on 3.0.x nor on 3.2.x.
Still you're the only one to report it
@Jojo-schmitz: I tried your recommended approach with 4 Eb Horns and using the concert pitch button. Exact same results. A fresh score created on 3.2.
I can "fix" the clefs, but as soon as I reopen the file after writing, it's broken again. I'd happily provide more score files if required. If you suppose that I do something wrong, please provide exact steps how this is assumed to work. But I'd call behaviour buggy if things are not saved and the score looks different after re-opening.
The problem can easily be reproduced:
1) create a new score, instruments do not matter, at least 2, e.g. with voices, keep the other settings at default
2) change the clef to 8va by pulling "treble clef 8va bassa" from the palette to the two existing clefs
3) select all barlines by right click on bar line -> select -> similar objects
4) uncheck and then check the box "span to next barline"
So far everything looks ok, but then:
5) save the file, close it
6) reopen the file
7) watch the broken clefs
So apparently this only triggers if all barlines from the score are being spanned.
I did compare the files before and after step 4), and apparently this causes the problem:
$ diff -u cleftest-broken.mscx cleftest-working.mscx
---- cleftest-broken.mscx 2019-08-05 11:05:54.870446861 +0200
+++ cleftest-working.mscx 2019-08-05 11:01:44.650979075 +0200
@@ -536,8 +536,6 @@
<Staff id="2">
<Measure>
<voice>
- <BarLine>
- </BarLine>
<Clef>
<concertClefType>G8vb</concertClefType>
<transposingClefType>G8vb</transposingClefType>
It doesn't matter if the Barline tag is empty or does contain anything. If it occurs in front of the <Clef>, the problem is triggered. Attaching both files for your reference.
Some further feedback: The problem also shows up if e.g.a TimeSig tag occurs before the Clef tag.
Are you able to reproduce with the given steps?
I was able to reproduce a problem on 3.2.3 following those steps. On reload, the top clef was fine, the bottom had the clef appear as a "mid-measure" clef rather than at the start of the measure.
The problem is indeed likely due to the modified barline. For the record, the process you used to change the barlines is not something one would normally do, for a number of reasons - most importantly, that it only affects the existing barlines. So if you add measures, they won't have their barlines extended. If the goal is to extend the barlines through the scores, simply double-click one then drag it. Or, change the span of one then hit the Save as staff default" button. Then it correctly changes the staff settings rather than the setting of existing barlines individually. The other downside of your approach is that it affects the system barlines but you don't actually want to modify those. And that's what triggered the bug.
In reply to I was able to reproduce a… by Marc Sabatella
Thanks for the hint, I'll use that approach to extend the barlines in the future. For my existing scores, is there a way to fix them without editing the xml manually?
Try selecting all barlines again, then pressing Delete, which removes your customizations, then delete the interior clef and re-add it to the beginning. That worked for me and survived save/reload
Thanks a lot @Marc Sabatella , that worked fine!
I don't understand how this forum thing works, I just added a comment and it's not showing up.
In reply to I don't understand how this… by donkerbot
And I added an image which is also not showing up.
In reply to And I added an image which… by donkerbot
So anyway, it's still happening and the problem is that Musescore automatically changes a clef to a treble clef in the instruments panel.
I'm not typing the whole thing again, just look at the attached image.
![musescorewrong.jpg]( "musescorewrong.jpg")
In reply to So anyway, it's still… by donkerbot
"it's still happening". That's why the status is still "Active". But you changed workaround from "yes" to "no". Do you mean the workaround is not now working? If it is still working please change that setting back to "yes"
In reply to "it's still happening". … by SteveBlower
If you are not familiar with how the issue tracker works, here is some explanation https://musescore.org/en/node/309537
In reply to If you are not familiar with… by SteveBlower
No, the workaround is not working. I selected all the barlines, deleted all the barlines, deleted the inserted clef, changed the treble clef back to a bass clef. Save, reload, clef is changed back to treble clef, and extra bass clef has been reinserted automatically.
I don't know how the barlines would have anything to do with it anyway, it's the clef in the instrument panel that's incorrectly changed to treble clef when I change the instrument name. I don't know how else I'm supposed to add a Bass Synthesizer instrument without a treble clef, other than deleting the treble staff, which then changes the clef to treble clef, and there's no way for me to change the default clef for any given staff.
In reply to No, the workaround is not… by donkerbot
Sorry, I should clarify. The reason I said "It's still happening" is because the last comment was made over two years ago by someone for whom the workaround did work. Maybe it's a different underlying problem.
It appears the problem how I see it is linked with https://musescore.org/en/node/278230 and https://musescore.org/en/node/325536 and https://musescore.org/en/node/300001 and https://musescore.org/en/node/272255
It's unusual but not unknown that a workaround stops working. The original issue was related to Version 3.2. Perhaps some fix between that and the current version broke the workaround. I suggest you bring this up in the Forum rather than the issue tracker as you will have a wider audience there who can perhaps help to tease out the underlying cause or find a working workaround.
Issues are better linked to as #278230: Looking at staff properties changes clef of instruments with multiple staves and #272255: single piano stave with bass clef turns to treble after property edit ([xxxxxxx]) Here easily reveals that one is closed
In reply to Issues are better linked to… by Jojo-Schmitz
All the more reason to discuss this latest report in the forum to see which, if any, active issues are related.
Are you sure what you are talking about is related? This is issue is about a very specific case involving modifying the system barline, and a clef being converted to a mid-measure clef. Your pictures appear to show something else entirely.
Best to ask on the support forum, attach your score, and then write up a nice simple description of the problem. Trying to piece together the from pictures is much harder - a simple set of steps to follow is much easier.