Double click uses ottava symbol in Emmentaler whereas drag & drop does not
Nightly fbd255f / Windows7
1) Open this file (same font issue with single standard staff) : ottavas file.mscz
2) Duplicate the ottavas input of the first three measures in the measures 4, 5, 6.
Results: unexpected
First, the font (size, style) in the standard staff is wrong (correct in linked staff).
If you go in Line properties (standard staff), you see this:
Second: the hook of the 8 ottavas works as expected , but not those of 15 and 22 ottavas (with an empty measure by default). However, it works as expected, if you add a note, as in measures 7-9 in the test file.
3) Now, generate Parts -> New all -> Ok
4) View in Part
Result:
The ottavas overlap in the two staves of the first three measures:
but not in the last three (so, not empty)
Finally, notice that with in 2.0.1, there is no issue with the fonts, but there is the same issue of overlapping in parts (with ottavas in empty measures always, and 15 and 22 ottavas hooks)
Comments
After investigation, the font issue occurs only (in standard staff)) when adding the ottavas by double-clicking from the palette, not with drag and drop.
![ottavas 1.jpg]( "ottavas 1.jpg")
![font 3 juillet e42e883.jpg]( "font 3 juillet e42e883.jpg")
Recent issue.
- This Nightly on July 3 works (excepted the 15 ottava hook): e23cc50
- Not this one: e42e883
After seeing, seems be a side effect of this commit: https://github.com/musescore/MuseScore/commit/6a7fa155e466dadfed7d21403…
But this commit was merged on June 30 (so, don't understand very well, maybe related to merged in master branch, or 2.0.2 branch?)
If not, this one may also be invoked? : https://github.com/musescore/MuseScore/commit/2d041c931d1a451d365fb773b…
PS: the issue or the two issues (?), more investigation necessary, with ottavas hooks and overlap (in parts), is not related to this font issue. I go probably fill an other issue (or two) later.
Title change to highlight the specific nature of this issue as described at the beginning of the original message.
As already said in the previous comment (P.S.), the two other issues - of lesser importance - are definitively not related, and date back much further in time.
Interesting! Did you add those ottavas using the new double-click method? I can confirm that if you add an ottava using the old drag & drop method, it gets added with a simple "8", but if you add it via the new double click method, it gets added with the special ottava symbol. And when adding via double click to an instrument that has linked staves, you get one of each.
As far as I can tell, everything is fine if you simply change the text manually - there is no corruption or anything like that. Just an inconsistency in the defaults when adding lines by different methods. I believe the issue is that it is *supposed* to display with the (bold) ottava symbol, but Emmentaler lacks that symbol, so it gets changed to a plain 8 when using that font. I kind of think of that as a bug, and think the behavior we see on double click now is actually more correct - not that I did it on purpsoe. But for consistency, I guess I will try to change it to duplicate the drag & drop behavior. Note if you change to Bravura, you get the (bold) symbol no matter what, which is what I personally think should happen with Emmentaler too.
The lack of hook on the very short 15 and 22 lines is not a bug - they only display if there is room. If the line is too short, no hook displays.
You might want to open a separate issue for the overlapping lines in parts. I'm not sure there is anything we can reasonably do about that - there is no way to know what the user actually intends for the layout of those lines. But maybe we could refuse to create the multiplemeasure rest in the first place. For now, the workaround is to set the "Break multimeasure rest" flag for those meausres yourself, assuming that's what you wanted to see.
Sorry, our posts overlapped, I'm resetting the title again.
1) "Did you add those ottavas using the new double-click method?"
Absolutely, and this why I had changed the title! :)
2) "The lack of hook on the very short 15 and 22 lines is not a bug - they only display if there is room. If the line is too short, no hook displays."
![lignes de texte.jpg]( "lignes de texte.jpg")
![ottavas 22 august.jpg]( "ottavas 22 august.jpg")
Ok, it's just a little unexpected. In an empty measure, there is room, and e.g. the text line has a different behaviour.
In my memory and after checking, the change occured just before the 2.0 release (EDIT:Beta 1 of course!)
Probably this commit ? https://github.com/musescore/MuseScore/commit/cd7d50143ed7768c784e36a8e… To fix this:
That said, unexpected display for me, but with minor importance, because it works as expected after entering a note or notes (that is logically the goal!)
3) "You might want to open a separate issue for the overlapping lines in parts. I'm not sure there is anything we can reasonably do about that - there is no way to know what the user actually intends for the layout of those lines."
![issue.jpg]( "issue.jpg")
![19 mai bis.jpg]( "19 mai bis.jpg")
Well, I may open a separate issue for that. But I see different behaviours in the time, and I don't know what is the expected result?
With the Nigthly on May 19, 2014. I see this, first,
and then, in parts. Better (no overlap) but no really expected also?
Yes, exactly, it was the "backwards" hooks we needed to fix, and we did so by not displaying them at all for short lines. Ottavas have different rules than other text lines in terms of where the start and end points are by default, so that's why you see that difference. Of course, an ottava over a single *rest* makes no sense at all, so it really won't be an issue in practice. For an ottava over a single *note, then the current heavior is definitely correct.
Regarding the display of lines over multimeasure rests, I'm not sure there is going to be any answer that wil do what is expected for all cases. I think you should just file the issue just to remind us to look at this and try to decide later what makes the most sense.
Meanwhile, I'm looking at the font issue. I see why this happens, so it's just a matter of time before I have a fix. Kind of a shame, though, as It would be nice if it were easier to get the nice ottava symbol even in Emmentaler.
https://github.com/musescore/MuseScore/pull/2114
Kind of a hack, but it gets the job done. I do still think it worth considering whether we should really be sliently replacing the ottava symbols with plain text when using Emmentaler, but I am not going to worry about that right now.
Fixed in branch master, commit c81b5bbde0
fix #68271: ottava added differently for double click than drag & drop
Fixed in branch master, commit d45cc192e5
better fix #68271
Brilliant! Just this morning I was coming up against this issue in a job I'm doing. The rest of the job will now be that much easier. (I'm already using a nightly because of [Shift]+[V].)
Automatically closed -- issue fixed for 2 weeks with no activity.