Re: Doc: Improve documentation of \glissando. (issue 6529043)
A new patch has been uploaded to a new issue, number 6567059, as I do not own this one. Werner: could you close this issue please. http://codereview.appspot.com/6529043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
Benkő Pál wrote Wednesday, September 26, 2012 1:31 PM > I made some Bartók and Xenakis scans, see > https://docs.google.com/folder/d/0B7AjGy5hUKtAeWtkdHdfN0l4bm8/edit > such beams can be seen in 0162.jpeg and 0164.jpeg > (the former has examples for avoiding such stems too, using flags). Many thanks, Pál, very helpful! I now see the point of inserting these markers in long glissandi, and the need for beams and flags. I'll try to make realistic examples to show this. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
> This example shows a beam extending from a stem to the > final note of the glissando. Is this correct, or would > it be better to suppress the beam? I made some Bartók and Xenakis scans, see https://docs.google.com/folder/d/0B7AjGy5hUKtAeWtkdHdfN0l4bm8/edit such beams can be seen in 0162.jpeg and 0164.jpeg (the former has examples for avoiding such stems too, using flags). ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely File Documentation/notation/expressive.itely (right): http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely#newcode1059 Documentation/notation/expressive.itely:1059: @lilypond[verbatim,quote,relative=2] On 2012/09/25 21:07:06, Trevor Daniels wrote: This example shows a beam extending from a stem to the final note of the glissando. Is this correct, or would it be better to suppress the beam? just like ordinary duration display: either a beam or a flag. Bartók's String Quartet no. 4. has examples for both. I find your example fine. is it mentioned that glissando is not standardised? e.g. Bartók wanted all glissandi start immediately, while others use the headless stem notation, reserving full headed notes to mean fixed pitch through the whole duration. http://codereview.appspot.com/6529043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
One more question (sorry, I'm not familiar with this notation, and I'd like to be sure it's right.) Trevor http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely File Documentation/notation/expressive.itely (right): http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely#newcode1059 Documentation/notation/expressive.itely:1059: @lilypond[verbatim,quote,relative=2] This example shows a beam extending from a stem to the final note of the glissando. Is this correct, or would it be better to suppress the beam? http://codereview.appspot.com/6529043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely File Documentation/notation/expressive.itely (right): http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely#newcode1074 Documentation/notation/expressive.itely:1074: @lilypond[verbatim,quote,relative=2,line-width=4.0\cm] http://www.iannis-xenakis.org/partitions/Syrmos.jpg http://codereview.appspot.com/6529043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely File Documentation/notation/expressive.itely (right): http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely#newcode1074 Documentation/notation/expressive.itely:1074: @lilypond[verbatim,quote,relative=2,line-width=4.0\cm] On 2012/09/25 15:31:17, Trevor Daniels wrote: In this example and the previous one the skipped notes have durations, so the visible notes in a bar don't add up to the measure length. Is this the usual practice? I'm just singing Xenakis' Nuits, and it's notated this way. And a second point: it would be better to use \hideNotes and then make the stem visible, otherwise ledger lines and dots remain visible. ugh, I don't have the score at hand; I think I haven't seen ledger lines; I'm absolutely unsure about dots. will check tonight. http://codereview.appspot.com/6529043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
I'm reworking these examples ready for insertion in the NR, but I'd like to see responses to my comment below first. Trevor http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely File Documentation/notation/expressive.itely (right): http://codereview.appspot.com/6529043/diff/1/Documentation/notation/expressive.itely#newcode1074 Documentation/notation/expressive.itely:1074: @lilypond[verbatim,quote,relative=2,line-width=4.0\cm] In this example and the previous one the skipped notes have durations, so the visible notes in a bar don't add up to the measure length. Is this the usual practice? And a second point: it would be better to use \hideNotes and then make the stem visible, otherwise ledger lines and dots remain visible. http://codereview.appspot.com/6529043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
On Thu, Sep 20, 2012 at 09:05:51PM +, thomasmorle...@googlemail.com wrote: > On 2012/09/20 18:08:15, Graham Percival wrote: > >We normally do not include \override in most sections of the Notation > manual. > >Instead, we ask users to submit LSR snippets showing the \override, > then we > >include those snippets in the docs. This allows us to improve the > documentation > >with minimal effort on the part of developers. > > glissando-skip was introduced somewhere in 2.15.x, so no snippet using > it can make into LSR. ok. The Documentation/snippets/new/ directory was created for exactly this situation. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
On 2012/09/20 18:08:15, Graham Percival wrote: We normally do not include \override in most sections of the Notation manual. Instead, we ask users to submit LSR snippets showing the \override, then we include those snippets in the docs. This allows us to improve the documentation with minimal effort on the part of developers. If there's a special reason to include \override directly, then we can -- we do this when discussing automatic beaming, for example, because there's no sense in mentioning this without having overrides. But I'm not certain if this applies in this case? glissando-skip was introduced somewhere in 2.15.x, so no snippet using it can make into LSR. Thinking of an LSR-update, David recently suggested to wait a bit: http://lists.gnu.org/archive/html/lilypond-devel/2012-09/msg00715.html http://codereview.appspot.com/6529043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
Reviewers: Graham Percival,
Message:
I agree with your argumentation. However, I don't have time to fix the
patch. Maybe a good soul from the documentation team can improve this.
Description:
Doc: Improve documentation of \glissando.
Based on work from Tiresia GIUNO .
Please review this at http://codereview.appspot.com/6529043/
Affected files:
M Documentation/notation/expressive.itely
Index: Documentation/notation/expressive.itely
diff --git a/Documentation/notation/expressive.itely
b/Documentation/notation/expressive.itely
index
25dbc81d798c75a3b3b1fef709d6fb2b7b66c2e8..528cdb2047c56e75470673e535f57d7b8a3849c4
100644
--- a/Documentation/notation/expressive.itely
+++ b/Documentation/notation/expressive.itely
@@ -1038,15 +1038,88 @@ g2\glissando g'
c2\glissando c,
@end lilypond
+It is possible to place an expression mark at a certain point within
+the glissando, usually indicated by a stem without a notehead:
+
+@lilypond[verbatim,quote,relative=2]
+f4\glissando\<
+\once \override NoteColumn #'glissando-skip = ##t
+\once \override NoteHead #'transparent = ##t
+a4\f\> a8\! r4.
+@end lilypond
+
+@noindent
+Setting @code{glissando-skip} to @code{#t} makes the glissando skip the
+inserted @code{NoteColumn} grob. To hide the notehead, the
+@code{transparent} property is set to @code{#t}. If the stem doesn't
+align well with the glissando, it may need repositioning.
+
+The same works with more than one inserted grob:
+
+@lilypond[verbatim,quote,relative=2]
+r8 f2\glissando a8 r4 |
+r8 f8\glissando
+\override NoteColumn #'glissando-skip = ##t
+\override NoteHead #'transparent = ##t
+g4 a8
+\revert NoteColumn #'glissando-skip
+\revert NoteHead #'transparent
+a8 r4
+@end lilypond
+
+Setting the @code{breakable} property to @code{#t} in combination with
+@code{after-line-breaking} allows to break a glissando if it occurs
+at a line break:
+
+@lilypond[verbatim,quote,relative=2,line-width=4.0\cm]
+\override Glissando #'breakable = ##t
+\override Glissando #'after-line-breaking = ##t
+
+f1\glissando | \break
+a4 r2. |
+f1\glissando \break
+\once \override NoteColumn #'glissando-skip = ##t
+\once \override NoteHead #'transparent = ##t
+a2 a4 r4 |
+@end lilypond
+
+A glissando can connect notes across staves:
+
+@lilypond[verbatim,quote]
+\new PianoStaff <<
+ \new Staff = "right" {
+e'''2\glissando
+\change Staff = "left"
+a,,\glissando
+\change Staff = "right"
+b''8
+ }
+ \new Staff = "left" {
+\clef bass s1 s8
+ }
+>>
+@end lilypond
+
+A glissando can occur between chords:
+
+@lilypond[verbatim,quote,relative=2]
+c1\glissando g'
+1\glissando \break
+
+\set glissandoMap = #'((0 . 1) (1 . 0))
+1\glissando
+\set glissandoMap = #'((0 . 0) (0 . 1) (0 . 2))
+c1\glissando
+\set glissandoMap = #'((2 . 0) (1 . 0) (0 . 1))
+1\glissando
+@end lilypond
+
Different styles of glissandi can be created. For details, see
@ref{Line styles}.
@snippets
@lilypondfile[verbatim,quote,texidoc,doctitle]
-{glissandi-can-skip-grobs.ly}
-
-@lilypondfile[verbatim,quote,texidoc,doctitle]
{contemporary-glissando.ly}
@seealso
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Improve documentation of \glissando. (issue 6529043)
Am 20.09.2012 20:08, schrieb gra...@percival-music.ca: We normally do not include \override in most sections of the Notation manual. Instead, we ask users to submit LSR snippets showing the \override, then we include those snippets in the docs. This allows us to improve the documentation with minimal effort on the part of developers. If there's a special reason to include \override directly, then we can -- we do this when discussing automatic beaming, for example, because there's no sense in mentioning this without having overrides. But I'm not certain if this applies in this case? So this means that the first, second and third example should go into a LSR snippet to be included in the documentation, the latter examples do not have any \override and can stay unchanged? At least this would make sense for me. Regards, Marc http://codereview.appspot.com/6529043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
