Re: Slur.ms (version 1.0)
Reply #2 –
It feels funny to be posting a bug report on my own object, but this is a sort of "heads up" to let people know that I may be making a fix soon, that could affect how slurs behave in other peoples' scores.
I've noticed that the default end point positions for certain types of notes are not "optimal". Generally, this happens with chords that have adjacent noteheads, both for normal and split-voice chords. It is most noticeable when the slur direction is explicitly set to Upward or Downward. Following is a clip that demonstrates both correct and incorrect placement.
There is logic in the object to detect the stem and slur directions of the starting and ending notes, that attempts to determine the best default end point placement. However, that logic isn't working correctly for the note types mentioned, so the user needs to use the start and end offset values to correct things.
I could leave the object as is, and let users adjust the slurs manually in these circumstances, but that doesn't seem like the correct course of action to me. However, I realize that if I change any of the rules, then users who have already tweaked slurs to look correct for these situation may need to "untweak/retweak" them.
If you use this object and have any feedback, comments or suggestions, I'd very much appreciate them.