|Subject:||A slur across a line break with change of clef in another staff generates bad output|
|Date:||Sun, 4 Mar 2018 00:03:14 +0100|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0|
I stumbled across a bug where Lilypond generates a bad slur if the slur crosses a line break and there is a simultaneous clef change in a different staff. I found a previous report for this bug in the mailing list archives (2015-05-30, same subject, ), but with Google Code being archived and SourceForge currently in Disaster Recovery mode, I’m not sure if the bug is currently tracked anywhere (or even fixed in the development version), so I thought I could still post my tiny(ish) example along with a workaround, and perhaps it would be helpful to someone :)
Example (you can replace the 7 with other numbers), with workaround commented out:
Screenshots of the results are at . The control points aren’t perfect, since I couldn’t figure out how to get the automatically chosen control points (for the second half of the broken slur, we could just reuse these, since only the first half is bad, and the first half could be based on them as well), so I had to try to match them by eyeballing. Also, this unfortunately doesn’t work if you want double slurs, since AFAIK it’s not possible to set the control points in that case . But still, it’s better than nothing IMHO.
Hope this helps,
|[Prev in Thread]||Current Thread||[Next in Thread]|