Slurs lost on exchange voices (if no note in other voice at anchor point)

• Dec 23, 2014 - 17:14
S3 - Major

Ubuntu 14.04, GIT commit: bf97799

1) open attached score
2) select all
3) edit / voices / exchange 1-2

Result: first slur remains, but second is lost. Actually, "lost" is a good word. It is apparently still in the score, but no longer attached properly. Certain operations performed on the score afterward yields console errors about "zero slur", although I don't know exactly how to reproduce that.


This is off topic marc but I was wondering whether your simply forgot to attach the score, or whether something went wrong with the website. The latter happened in the past, hence my question.

Ok, Marc, I can easily reproduce this issue.
I am trying to locate. At the moment, works on August 21, but fails on August 28. Yet a little while, and I may clarify.

So, after investigation, this issue appears on August 22

- Works from this Nightly:
August 22 3d172d7.jpg
- Failure with this one:
August 22 b4dbb5a failure.jpg

So, the cause is most likely a side effect of these commits (the one or other, or both?)



Attachment Size
August 22 3d172d7.jpg 10.66 KB
August 22 b4dbb5a failure.jpg 10.77 KB

"narrowing it down" is an English expression for the sort of thing you do so well - we initially have a problem where we don't know where to begin looking, but you make the problem "narrower" by restricting the number of places we need to look :-)

The problem appears to be that in cmdExchangeVoice, we need to go through the spanners and fix the track info for all and/or slur segments. However, the details of how this all works - including making sure the slur segments match the slurs - is pretty tricky and not something I am very familiar with, so I will leave it to someone else.