Changing marker type should change text style too

• Dec 19, 2018 - 20:35
Reported version
3.0
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
Yes
Workaround
No
Project

Shockingly, a 19th century symphony has DS al Coda shenanigans, so I noticed that the jump happened a measure late. Here's a much shorter example piece for you. Should play to DS al coda, jump to sign, play to coda sign, jump to coda, but... it plays a measure after it hits the coda sign, and then jumps. Notation looks fine, though I'm a little baffled at the lack of a 'Coda' with a codab label in the palette. That doesn't matter much though, edited it to look right just fine.

Attachment Size
test.mscz 16.48 KB

Comments

In reply to by xavierjazz

I put the coda sign exactly where it's supposed to be. the jump is supposed to be at the coda sign, not after. Check the score.

If for whatever reason the jump is supposed to be after the measure you need to highlight to add the coda sign, and not before, then the coda sign is being added to the wrong side of the measure. Either way, notation doesn't match playback.

Status active needs info

I don't see any repeats or codas?

In general, codas do work correctly in my experience. A common mistake is trying to the use the plain coda sign in place of a "To Coda" instruction. Some publishers do that, and it's OK to want that look, but in order to achieve it, you will need to add the "To Coda" (to the last measure before the jump) to get the correct playback, and then edit the text to just have the coda sign.

Status needs info active

Lol, it was in MS3dev folder, mot MS3. Too many score folders now.

The To Coda -> Coda (codab) is fine, btw. It's just the sign. The coda sign, not the al Segno.

Attachment Size
test.mscz 12.21 KB

Marc, I suspect what you're talking about is the problem, but I can't figure out how to get the coda sign to look correct that way. If that's it, then maybe another palette element that is labeled 'To Coda' with tooltip, looks exactly like the regular coda sign, and orients to the correct barline?

Even set to the same font and size, just editing the 'To Coda' to a sign results in a too-fat coda sign. It looks odd. And getting it where it's supposed to be is a pain - if that's the workaround, I'm just leaving it so it plays back wrong and looks right, as opposed to lots of work to make it not look quite right and playback correctly.

Edit: Also, there appears to be no way to make DS al Coda placed below the staff instead of above?

In reply to by Laurelin

Here's my theory.

You inserted the coda symbol on the measure
Changed the type to "To Coda" and changed the Label from "codab" to "coda".

Problem, when you insert a "Coda" symbol it's attached to the beginning of a measure, but a "to Coda" is attached to the end of the measure.

This in theory should work properly, so this in my opinion is a bug.

The proper way to do what you want is to enter a "To Coda" at the end of the measure where you want a jump and change the text to the coda symbol using special characters or copy a paste from a coda symbol.

I suppose there's a regression. By changing the marker type of an Coda sign as "to coda" a small Coda sign should appear at the end of the measure.

The "To Coda" is definitely attached to the wrong measure - you need to attach it to last measure you want played, not the first measure you want not played. I think mike320's guess it probably right - you probably added the coda sign then tried to make it work like a "to coda", when the correct things to do is add a "to coda" then make it look like a coda sign.

ideally there would be a "text style" dropdown for these so you could easily change between "Repeat Left" and "Repeat Right" at the same point when you are changing the "Market type". And I tried to implement that a few weeks ago. but ran into a complication in that the text style actually can differ for different markers of the same type, which isn't handled well. So I had to leave that out when I added "text style" dropdowns to most other text elements.

Meanwhile, if you do add a coda sign (to the correct measure!) and then change the "Marker type" to make it work like a "To coda", set it to right aligned and now ti will display at the end of the measure. I don't know that having this happen automatically when you change the 'Marker type" is a good idea; generally it's not expected that changing one setting in the Inspector has a ripple effect on others.

Status by design active

Nope - I don't think it's by design. There's a different behavior of the appearance between MuseScore 2.3.2 and 3.0 by adding a coda sign and changing the marker type to "to coda". With MuseScore 2.3.2 it appears at the end, with 3.0 it stays at the beginning of the measure.

note: the term "to coda" isn't an international conversation. It should be possible to change a Coda sign easily as common as a "to coda" marker type as inside 2.3.2 before.

Priority P3 - Low

Well, I am pretty sure it's design, the design changed now that all these settings are in the Inspector. But OK, we'll leave it open as a possible thing to reconsider how we handle this.

Title Coda jump is one measure late Changing marker type should change text style too
Priority P3 - Low P2 - Medium

Well, I am pretty sure it's design, the design changed now that all these settings are in the Inspector. But OK, we'll leave it open as a possible thing to reconsider how we handle this.

My personal opinion: As mentioned in my note above, "to coda" is an English/American expression. Especially in German scores, but maybe in other too, there exist two Coda signs. My point is I don't wan't to have taking more settings inside the inspector, that it appears as expected, so that's more convenient as with MuseScore 2.3.2 (that means changing the marker type should also changing the appearance).

Sure, that's why I changed the issue title the way I did. If we automatically changed the text style.upon change of marker type, that should mimic the 2.3.2 behavior you describe, as far as I understand.

Note you can also simply customize your palette to sidestep the issue.

My intention is: A Coda sign in sense of "to coda" should work as default, without to have changing the placement inside the inspector or customizing it inside a palette manually. Therefore it's a regression for me.

But it never worked that way. The coda sign was always a coda sign; it never behaved by default as to coda. It's always been necessary to force that change manually. only difference is that previously this used to automatically change the text style and now it doesn't, so that's what I am suggesting changing.

The difference: changing the marker type with v2.3.2 changes the horizontal offset/position automatically (as expected), see:

tocoda.gif

Exactly, and as I keep saying, that's because it is change the text style from Repeat Left to Rpeat Right. And that is why I have made that explicit in the title of this issue.

But wouldn't it be better to not need to change anything - to just add it and have it both behave and position the way you want without needing to even touch the Inspector?. That is the advantage of adding this to a custom palette. Fifteen seconds spent doing that now means never having to deal with it again.

Yes, and interesting: if I change the marker type of a Coda symbol to "to coda", placing it in a custom palette and using this symbol from there again, it changes the text style automatically.

But in my opinion it shouldn't be necessary, that I have to create a custom workspace/palette before an customize the symbol, to using a Coda sign instead of "to coda". Using a Coda sign instead of "to coda" is a common way in music notation and I never understood, why it isn't available by default.

Yes, it's also possible to insert a "to coda" and exchanging the text with the Coda sign via special characters (also in this case it's affecting the text style automatically). Both, changing the text or using a custom palette therefore, are workarounds in my opinion.

So for me it's a regression concerning the title of this issue, above a suggestion for handle this way of music notation maybe easier by default in future.