Slurs not saved correctly

• Oct 26, 2014 - 10:43

I have a problem with slurs that don't connect to a second note. I can adjust them to look exactly what I expect them to look like (ending at some specific point on the canvas), but they are not saved correctly. Fortunately when directly exporting to a PDF file they are shown correctly, but reopening the MSCZ file in MuseScore results in what you see in the attached picture (slur_bug1.png).

slur_bug2.png shows the expected result.

Thanks for your reply!

Attachment Size
slur_bug1.png 1.81 KB
slur_bug2.png 6.03 KB


In reply to by cadiz1

Hi cadiz1,

thanks for your reply. That's exactly what I mean, your screenshot shows the problem very well.

Another similar thing: If you create a new document and insert a quaver note at the beginning, try to add a slur to this single note. Reopening this score makes the slur get lost.

In reply to by jschwalm

Ok, thank you for pointing this issue. I'll report as soon as possible in the Issue tracker and try to locate the moment when this issue has occurred.

For the second point ("similar thing"): confirmed also. But I would bet it is related to the first, since the slur is in the same way connected to a rest (to check)
slur rest.jpg

Attachment Size
slur rest.jpg 6.14 KB

BTW, what do you intend that notation to indicate? From the appearence of the example, it seems maybe tyou'd be better off using one of the symbols from the Arpeggios palette - falls, doits, etc. Unlikely slurs, these are intended to be one-sided and should work much better for most purposes for which I could imagine someone might try using a one-sided slur.

In reply to by Marc Sabatella

Are you referring to this, or not?
To fix this: #28106: Crash when pressing the "S" key
But as you can see, the issue reported is previous

NB: about the intend to notation, it may be useful in cases ("rather" common in a multi-voices context, "especially" in contemporary music), to indicate that the sound may extend beyond the rest (in the spirit of "l.v", let ring).

In reply to by cadiz1

Yes, these are basically horiztonal, so it makes sense to use something more like a one-sided slur. You *can* edit the shape of the falls, btw, the same as for slurs. But more direct support for one-side slurs (and ties!) would still be very welcome.

In reply to by Marc Sabatella

Adding to what cadiz1 has already said, I like to emphasize that slurs without a connecting second note, indicating a longer duration than expressed by the note value itself is a very common phenomenon in guitar literature, especially in modern music (modern in a wider sense, including music from the early 20th century). On the guitar and similar stringed instruments, contrary to most other instruments, notes have to be actively suppressed very often, otherwise you would often hear undesired open strings. Accordingly, indicating longer lasting notes by an "open slur" is a good and often used way to clarify that a specific note shall not (necessarily) be suppressed.

Another less guitar specific use is to indicate a composers intention that might not be practicable due to the instruments limitations. For example certain lines in multi-voice contexts are simply not possible to realize on a guitar - it might be sensible however to give a hint to the reading musician how this phrase was intended.

Anyway, I'd be very glad about a solution to the issue of slurs connected to rests losing their position already from a guitarists position. I have transcribed lots of guitar pieces in MuseScore already and have encountered this problem again and again.

Thank you very much!

Another interesting fact, although tablature-specific: Luis Miláns 'El Maestro', one of the earliest sources of all guitar (vihuela) literature, used some kind of "open tie". Its appearance is rather that of a special symbol than a tie, but its idea is that of a modern tie and it is one-sided as well, since no second note is written down. See the example of his third fantasy in 2/2.


Attachment Size
milan.png 39.84 KB

Do you still have an unanswered question? Please log in first to post your question.