Originally created by: *anonymous
Originally created by: RalphBug...@gmail.com
Originally owned by: tdanielsmusic
Federico Bruni writes:
http://lilypond.org/doc/v2.15/Documentation/notation/long-repeats#index-repeat-and-slur
NR 1.4.1, Normal Repeats, Known issues and warnings
"Slurs that span from a \repeat block into an \alternative block will only work for the first alternate ending."
Why don't suggest a workaround?
I know, it's the usual workaround (\hideNotes + grace note), but it may be useful for beginners.
It's a bit tricky in polyphonic music, since you must be aware of the grace syncronization problem (it was called this way?).
Originally posted by: frederic...@polytechnique.org
is this issue still up to date. I see in the manual that we can use \repeatTie to do this with a nice example:
c1
\repeat volta 2 { c4 d e f ~ }
\alternative {
{ f2 d }
{ f2\repeatTie f, }
}
Originally posted by: fedel...@gmail.com
we are talking about slurs, not ties
there's no \repeatSlur command
Originally posted by: dak@gnu.org
As I mentioned before: it seems to me like using the kind of slur/tie that would be employed after a line break would seem like the right thing to use here, so it might make sense if the repeat constructs siphoned off unfinished spanners at the start of the first alternative and replicated them as post-break into every other alternative.
Originally posted by: tdanielsmusic
In comment 3 David suggested replicating slurs and ties into the second and
subsequent alternatives. As this would be a code change which is likely to
take some time I'll spawn a separate issue for this, and in the mean time
fix this issue with a doc change.
There are two possibilities: either suggest using \repeatTie even for slurs,
or add a new predef \repeatSlur which actually generates a RepeatTieEvent.
Both would have the same visual appearance, which looks acceptable to me.
Fixing glissandi is not so easy - they would need the usual hidden notes.
Comments?
Trevor
Originally posted by: bealings...@googlemail.com
If you use \repeatTie, how would it work if the slur started earlier in the music and not on the same note - so you already have a slur that spans a number of notes, and you want to show it going on to the repeat?
Originally posted by: tdanielsmusic
It would look like this:
\relative c'' {
c1
\repeat volta 3 { c4 d( e f }
\alternative {
{ g2) d }
{ g2\repeatTie f, }
{ e'2\repeatTie f, }
}
}
Trevor
Originally posted by: bealings...@googlemail.com
Thanks - sorry - was getting the wrong end of the stick (or slur, actually). I'd not realised you were talking about the end of the slur.
Originally posted by: fedel...@gmail.com
I don't have time to create an example (I have a plane to catch), but this is not going to work in TabStaff.
Because in TabStaff ties and slurs have a different behaviour.
Originally posted by: tdanielsmusic
Yes, \repeatTie does not work in TabStaff.
Perhaps the best approach is to generate another slur and move it by editing
the control points. This would work in TabStaff, although the control points
would be at different places:
\relative c'' {
c1
\repeat volta 3 { c4 d( e f }
\alternative {
{ g2) d }
{
\override Slur #'control-points = #'((-2 . 4) (-1 . 4) ( 0 . 4) (1 . 3))
g2( f,)
}
{
\override Slur #'control-points = #'((-2 . 3) (-1 . 3) ( 0 . 3) (1 . 2))
e'2( f,)
}
}
}
Trevor
Originally posted by: tdanielsmusic
Seems like the method in comment 9 is acceptable as a workaround. However,
it's a bit advanced for Chapter 1 of the NR, so I think I'll add this as an
example to the section in NR 5.5.4 Modifying ties and slurs with just a ref
to it from NR 1.4.1. But I need to wait until my fix for 2858, now under
review, is pushed before I can work on that section without incurring
conflicts.
Trevor
Owner: tdanielsmusic
Status: Started
Originally posted by: tdanielsmusic
The method of comment 9 is a good example where \override-ing the control
points is preferable to using \shape, as the control points all need to be
relative to the single note. I'll use this as an example in NR 5.5.4 showing
the use of \override for control points, so it will be included in the patch
for issue 2858.
This issue will then be resolved by a simple reference to that example,
plus something for glissandi.
Trevor
Originally posted by: tdanielsmusic
Do you think this is too hacky for a workaround showing a glissando
extending into several alternatives?
\relative c'' {
c1
\repeat volta 3 { c4 d e f\glissando }
\alternative {
{ g2 d }
{
g2
% create a straight slur and move it to a new position
-\tweak #'thickness #0
-\tweak #'line-thickness #1
-\tweak #'control-points #'((-2 . 2.2) (-1.4 . 2.3) (-0.8 . 2.4) (-0.2 . 2.5)) ( <> )
e
}
{
e2
% create a straight slur and move it to a new position
-\tweak #'thickness #0
-\tweak #'line-thickness #1
-\tweak #'control-points #'((-2 . 2.5) (-1.4 . 2.4) (-0.8 . 2.3) (-0.2 . 2.2)) ( <> )
d
}
}
}
Trevor
Originally posted by: fedel...@gmail.com
IMO it is too hacky; and, most importantly, control points work fine only in Staff, not in TabStaff.
I'd rather use \hideNotes and be aware of the grace syncronization problem in case of polyphonic music, as shown in these minimal examples:
http://lists.gnu.org/archive/html/bug-lilypond/2012-06/msg00045.html
Originally posted by: tdanielsmusic
Doc: Add example of extending glissandi over repeats (2591)
http://codereview.appspot.com/6814115
Labels: Patch-new
Originally posted by: pkx1...@gmail.com
Patchy the autobot says: passes tests.
Labels: -Patch-new Patch-review
Originally posted by: ColinPKC...@gmail.com
(No comment was entered for this change.)
Labels: -Patch-review Patch-countdown
Originally posted by: ColinPKC...@gmail.com
Counted down to 20121113, please push.
Labels: -Patch-countdown Patch-push
Originally posted by: tdanielsmusic
Pushed http://codereview.appspot.com/6814115
to staging as
[r784e1e7a6b4b5c086a54267aa2d1e34e5aaa254c]
With the earlier patch for issue 2858 (see comment 11)
this completes the fixes for this issue. Marking Fixed.
Trevor
Labels: -Patch-push Fixed_2_17_7
Status: Fixed
Originally posted by: Elu...@gmail.com
(No comment was entered for this change.)
Status: Verified