L.V. and slur ambiguity
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
needs info
Regression
No
Workaround
Yes
Project
This is a general problem. When entering an l.v. (let-ring in the lines palette), Musescore simply generates a slur connected to the following note or rest. This is very ambiguious, and we can't distinguish it from slur, especially there are a series of these without any rest in between, such as a set of rining notes in piano or harp score. Musescore's code always shows slurs, and so does Musicxml export and braille conversion. Is it possible to change this to a tie with a let-ring property like Musicxml's tie element? This will ease both Musescore's coding and braille output.
Haipeng
| Attachment | Size |
|---|---|
| lv.mscz | 6.97 KB |
Comments
Those are not let ring indicators, those are slurs. True let ring indicators are different. I'm not sure what went wrong when you tried to add them, but I just tried it myself using 3.3.3 and accessing the palette by keyboard, and it worked fine for me. Maybe you are working with a customized palette that lacks the true symbols? I have attached my version of your score, where I deleted the slurs and add actual LV markings.
een reader other than NVDA, which constantly crashes Musescore. The screen reader always puts the focus on the first thing. I'll try it again.
Haipeng
Thanks. Perhaps this is because I used another scr
Just a wrong input, as I said, the cursor is put at slur although I navigate to l.v., perhaps a setting or accessibility problem. Anyway, NVDA always crashes Musescore, and it seems that the big general palette is not so accessible, thus pressing enter will not work there. I can't find let ring easily through the F9 palette. Strange!
Haipeng
Right now NVDA crashes when using the palette search, that seems to be a Qt 5.9 problem. You can find the LV by going to the Lines palette and expanding the More button. I believe you may need to use Tab to get there.
Thanks!
Haipeng