Some issues of 3.0-dev

• Sep 19, 2018 - 10:04
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Severity
S4 - Minor
Status
active
Regression
No
Workaround
No
Project

As I'm not sure, if it makes sense at the current state to tell about the issues of 3.0-dev (master), I collect here some of the things I noticed - some may be intentional (?):

  • Vertical formatting of note lines doesn't work (extra space above etc.)
  • Tablature signs of historical tab may overlap with notes, text etc., what they probably shouldn't; the seem to be ommitted from the automatism ...
  • The double repeat bar line is still missing :||:
  • Tempo doesn't work, if I set the Tempo text invisible ...

Comments

Thank you for your input. Generally, it is better to use the forum if you are unsure about anything, and then create a separate ticket in the tracker for each actual issue.

Vertical formatting of note lines doesn't work (extra space above etc.)
You are talking about staff spacers? I can confirm that they do not work.

The double repeat bar line is still missing :||:
A double repeat barline may be achieved by placing an end repeat barline and a start repeat barline side by side. This cannot be done via the inspector. You will have to use the Barlines palette.

Tempo doesn't work, if I set the Tempo text invisible
Hmm, the tempo still works for me if I set it to invisible. Can you provide any more information on how to get it to fail?

In reply to by mattmcclinch

Vertical formatting of note lines doesn't work (extra space above etc.)
You are talking about staff spacers? I can confirm that they do not work.

No, I don't mean staff spacers. I mean the additional or extra space above, that can be defined in notation line properties. And there is nothing happening ... what also means that scores look much different to 2.3.2.
Addition: I noticed, that this only happens with singular note lines. Within systems, it seems to work.

The double repeat bar line is still missing :||:
A double repeat barline may be achieved by placing an end repeat barline and a start repeat barline side by side. This cannot be done via the inspector. You will have to use the Barlines palette.

That's true, but anyway I think, it should be provided by the program, as it is in former versions!

Tempo doesn't work, if I set the Tempo text invisible
Hmm, the tempo still works for me if I set it to invisible. Can you provide any more information on how to get it to fail?

I tested it once again with the newest available appimage-version: It doesn't work for me.
I established a new melody line - some notes only. Then I attached the tempo text to the first note; and to be sure I set it to "50" for quarters. It works fine, but if I set the tempo text invisible it doesn't work anymore; the piece will play much faster ...

OS: LMDE 3 (cindy), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 161be58

vertical formatting of staves:
The property "extra space above" makes only sense for staves. For systems there is a special property "minimum system distance" which determines system distance. The staff extra space can be used to adjust the space for inidvidual staves for example to separate instruments groups.
I changed the logic for system distance to use the maximum of "extra space above staff" and "minimum system distance" as the minimum staff distance value. I am unsure if this is the right thing to do as changing one of this values may not have any effect depending on the other value. This may be confusing for users.

Regarding the two-sided repeat barline: while I agree it seems confusing at first to not have it, I would claim it never made in the first place. After all, this isn't really a single symbol in the same sense as the others. In particular, if a system break happens to occur right at that point, do you really want to see the two-sided repeat sign at the end of the system? And then again at the start of the next? Same question if a horizontal frame is inserted between the two measures. No, this really is just separate end and start repeats that just happen to be displayed as a single system if the measures happen to be adjacent. It was kind of misleading to suggest otherwise.

Not that we couldn't continue to mislead people, but maybe it's better to be more up front and this.

vertical formatting of staves:
The property "extra space above" makes only sense for staves. For systems there is a special property "minimum system distance" which determines system distance. The staff extra space can be used to adjust the space for inidvidual staves for example to separate instruments groups.
I changed the logic for system distance to use the maximum of "extra space above staff" and "minimum system distance" as the minimum staff distance value. I am unsure if this is the right thing to do as changing one of this values may not have any effect depending on the other value. This may be confusing for users.

This looks good, if it is used for singular notelines or top notelines, that have this extra space. This value is very important for tablature lines because of the flags above (they still can overlap with upper notelines, which seems to be a bug).

In reply to by Marc Sabatella

I think you are right, but anyway it would be good to have this combined sign in a palette. It worked that way always (?): at least in 2.3.2, it divided automatically at the end of a line.
Anyway it was very confusing to miss this sign, for me as a person, who is not a beginner ...
And unfortunately it is not possible to copy it as a combined sign to the palette.

In reply to by MLutz

Tempo doesn't work, if I set the Tempo text invisible
Hmm, the tempo still works for me if I set it to invisible. Can you provide any more information on how to get it to fail?
I tested it once again with the newest available appimage-version: It doesn't work for me.
I established a new melody line - some notes only. Then I attached the tempo text to the first note; and to be sure I set it to "50" for quarters. It works fine, but if I set the tempo text invisible it doesn't work anymore; the piece will play much faster ...
OS: LMDE 3 (cindy), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 161be58

It now also seems to work for me, at least on this computer, with the same linux and a newer version:
OS: LMDE 3 (cindy), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 34b892d