Menu

#2453 Long syllables shouldn't be centered under notes

Accepted
nobody
Enhancement
2016-05-31
2012-03-30
Anonymous
No

Originally created by: *anonymous

Originally created by: janek.li...@gmail.com
Originally owned by: janek.li...@gmail.com

I suggest that long lyric syllabes shouldn't begin further than 2 or 3 staffspaces to the left of the note, i.e. they shouldn't be centered (unless user explicitly specifies alignment).

See examples from engraved scores: http://lilypond-stuff.1065243.n5.nabble.com/examples-for-Lyric-report-long-syllabes-examples-td5607319.html

In addition to aesthetically better results, this would allow automatic placement of long recitatives sung to one note - currently user has to manually override lyric alignment each time such situation occurs.

This issue is a part of the Lyrics Project.  See related entries:
issue 2450
issue 2451
issue 2452
issue 2453
issue 2454
issue 2455
issue 2456
issue 2457
issue 2458
issue 2459
issue 2460
issue 2461
issue 2462

1 Attachments

Related

Issues: #2450
Issues: #2451
Issues: #2452
Issues: #2453
Issues: #2454
Issues: #2455
Issues: #2456
Issues: #2457
Issues: #2458
Issues: #2459
Issues: #2460
Issues: #2461
Issues: #2462
Issues: #2463
Issues: #3979

Discussion

  • Google Importer

    Google Importer - 2012-03-31

    Originally posted by: PhilEHol...@googlemail.com

    This enhancement is supported by Elaine Gould (although she's not told me directly...).  Page 439.  "Centre each syllable directly under its note.  For very long syllables, place only the first two or three letters to the left of the note so that the syllable does not start too far before its sung note."

    Summary: Long syllables shouldn't be centered under notes

     
  • Google Importer

    Google Importer - 2012-07-08

    Originally posted by: janek.li...@gmail.com

    (No comment was entered for this change.)

    Status: done

     
  • Google Importer

    Google Importer - 2012-07-14

    Originally posted by: PhilEHol...@googlemail.com

    (No comment was entered for this change.)

    Status: Fixed

     
  • Google Importer

    Google Importer - 2012-07-14

    Originally posted by: PhilEHol...@googlemail.com

    Sorry - used wrong status in my change.

    Status: Accepted

     
  • Google Importer

    Google Importer - 2013-05-07

    Originally posted by: janek.li...@gmail.com

    (No comment was entered for this change.)

    Blockedon: lilypond:3239
    Status: Started

     
  • Google Importer

    Google Importer - 2014-06-28

    Originally posted by: janek.li...@gmail.com

    (No comment was entered for this change.)

    Blockedon: -lilypond:3239 lilypond:3979
    Status: Accepted

     
  • Google Importer

    Google Importer - 2014-08-09

    Originally posted by: janek.li...@gmail.com

    (No comment was entered for this change.)

    Labels: Janek_alignment_changes

     
  • Google Importer

    Google Importer - 2015-07-18

    Originally posted by: simon.al...@mail.de

    Workaround:

    \version "2.19.23"
    selfAl =
    #(define-music-function (al) (number?)
       (once (override '(LyricText self-alignment-X) al)))

    \lyricmode { \selfAl #-0.5 straight }

     
  • Google Importer

    Google Importer - 2015-07-18

    Originally posted by: simon.al...@mail.de

    Issue 808 has been merged into this issue.

     
  • Google Importer

    Google Importer - 2015-07-18

    Originally posted by: dak@gnu.org

    Oh shiver me timbers.

    The commit message for issue 4498 states:

        Issue 4498: Provide music functions property{Override,Revert,Set,Unset}
       
        The previous music functions `override' and `revert' (intentionally
        colliding with the respective keywords) are removed.  It would have been
        too confusing to have collisions for `set' and `unset' as well which are
        just too similar to existing Scheme constructs.
       
        A convert-ly rule for the previous calls override/revert is not
        attempted: they have not yet been documented and have been available
        only for one unstable version.  Whoever happened to use them already is
        capable of replacing them.

    So the code in comment #8 will _only_ work in version 2.19.23.  On the positive side, assuming that issue 4505 will also make it into 2.19.24, you'll be able to write

    \version "2.19.24"
    selfAl = \once \override LyricText.self-alignment-X = \etc

    \lyricmode { \selfAl #-0.5 straight }

    However, you are likely better off with a tweak anyway.  So that would be

    \version "2.19.24"
    \selfAl = \tweak self-alignment-X \etc

    \lyricmode { \selfAl #-0.5 straight }

    Except that this does not work unless you write

    \lyricmode { \selfAl #-0.5 \markup straight }

    since otherwise the "override mode" of \tweak triggers and tries doing this as
    \override straight.self-alignment-X = #-0.5

    Ouch.  Lyric mode and symbols as potential music function arguments are icky.  So one probably wants a manually defined \selfAl function after all, one that does _only_ accept a music argument to tweak, not a grob specification.

     

    Related

    Issues: #4498
    Issues: #4505

  • Trevor Daniels

    Trevor Daniels - 2015-09-29
    • labels: Janek_alignment_changes --> Janek_alignment_changes, BlockedOn 3979
    • Description has changed:

    Diff:

    
    
    • Needs: -->
    • Patch: -->