Can't have single number when adding custom time signature
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
Came up in http://notensatz.forumprofi.de/index.php?topic=1934.msg13094#msg13094
In 2.x it was possible to have a time signature with a single number only, only a numerator, without a denominator, this is no longer possible in 3.0, there, even if entering nothing into the denominator field, it gets interpreted and shown as 4:
Fix version
3.5.0
Comments
Workaround seems to be to enter a space into the denominator field
In the master palette, not in the timsig properties
In reply to Workaround seems to be to… by Jojo-Schmitz
ALT+0216 deals with my first symbol, but it gets a denominator. I can't get a space into the denominator box.
I'm using Windows 10.
What is a time signature of a single number expected to mean?
It is historical, for early music mostly IIRC
In reply to It is historicall, for early… by Jojo-Schmitz
But what does it mean? To be honest, I often use musescore to get rid of unclear notation like this.
Ask an early music specialist. That music often is unmetered, at least doesn't have the modern western music style numerator/denominator time signatures
In reply to Ask an early music… by Jojo-Schmitz
I now know that it can be done in MS3. Don't use Time Signature Properties, but create a signature under Master Palette, where a space can be put in the denominator field. Other special characters can be entered if you know the keyboard or ALT code.
Here is a snippet from the facsimile of Susato's Danserye (1551).
And here is how I represent it in my "urtext" edition - see www.johnkilpatrick.co.uk/music/Danserye/
If you view the .mscz version in MS2 it will look right, but in MS3 the unusual time signatures don't load correctly (and maybe some other features). The reason I have used MuseScore is that anyone can download it and learn to use it, and is thereby free to use my edition as they wish, including modernising clefs, times, etc., and transposing to suit various instruments.
Um, yes, this was what confused me when I was doing https://github.com/musescore/MuseScore/pull/5313. Perhaps the cause is line 302-303 in timesig.cpp, if I have time later I can test it.
~~Actually if I remember this correctly the empty denominator isn't replaced by 4 -- it's replaced by the denominator figure in the previous time signature. Say if you have a 3/8 before then the following empty denominator is replaced by 8.~~ (musescore.org doesn't support strikethrough?? see #295271: Writing on musescore.org doesn't support strikethrough)
EDIT: I was wrong, see the commit message for https://github.com/musescore/MuseScore/pull/5370/commits/c583d8ca9cfac4….
See https://github.com/musescore/MuseScore/pull/5370.
I noticed if the numerator string is empty and denominator string is not, the denominator string gets placed at the bottom of the clef, not at the middle. I don't know if that's an issue, but whatever it is, I don't think it needs to be taken care of by this particular PR.
If there is only 1 number it needs to be centered or allowing only 1 number to be displayed is not very useful, though you can move the number manually.
In reply to If there is only 1 number it… by mike320
This is still a different issue, isn't it?
Not in my opinion. Allowing only a denominator to be shown where people don't expect it is only a half fix.
In reply to Not in my opinion. Allowing… by mike320
OK, fixed.
The complete fix is in https://github.com/musescore/MuseScore/pull/5370, but https://github.com/musescore/MuseScore/pull/5315 also fixes a part of it, only for the case when numeratorString is empty.
the former got closed, the latter merged
So is this issue here fixed?
If so, how does it relate to #308139: Time signatures created pre-3.5 need special handling to avoid unintended loss of denominator?
In reply to the former got closed, the… by Jojo-Schmitz
The problem the latter PR wanted to fix was not this one, I just assumed it fixed it too. Turns out I was wrong.
So #308139: Time signatures created pre-3.5 need special handling to avoid unintended loss of denominator is a duplicate of this one.
Actually now we can have a single number, by accident, that's the problem of the other issue...
Well, no, it is the exact opposite
Oh yeah. So I was mistaken this time and not that time.
Automatically closed -- issue fixed for 2 weeks with no activity.