lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: “SubdivideBeams” problem


From: Carl Sorensen
Subject: Re: “SubdivideBeams” problem
Date: Sun, 31 Oct 2021 22:27:41 +0000
User-agent: Microsoft-MacOutlook/10.10.1b.201012


On 10/31/21, 3:42 PM, "lilypond-user on behalf of Knute Snortum" 
<lilypond-user-bounces+carl.d.sorensen=gmail.com@gnu.org on behalf of 
ksnortum@gmail.com> wrote:

    When you see this:
    
        (\break)
    
    something is wrong.  You can't attach a slur to a break; it has to be
    on some sort of note.  Also, do yourself a favor and use bar line
    checks, one line per measure.  I have a feeling you're getting off
    somewhere in the piece and that will clear up your beaming problem.

While these suggestions are good suggestions, it's also important to note that 
beam subdivision is incorrect in many instances.

See https://sourceforge.net/p/testlilyissues/issues/5547/

If automatic subdivision is not working in your use case, and one wants  to fix 
the problems with subdivision right now it is somewhat painful. It requires 
overrides that describe the number of beams on each side of the stem.  IIRC, it 
is the Stem.beaming property, which has two lists, the first saying which beams 
are on the left side of the stem, and the second saying which beams are on the 
right side of the stem.

Here's a sample:


%%%  
\version "2.22"
{
  c'32
  \once \override Stem.beaming = #'((0 1 2) . (0  1))
 c'
  \once \override Stem.beaming = #'((0 1) . (0 1 2))
  c'
  \once \override Stem.beaming = #'((0 1 2) . (0))
  c'
  \once \override Stem.beaming = #'((0) . (0 1 2))
  c'
  c'
  c'
  c'
}
%%%%

Notice that you must override the stem before and after the place you want the 
subdivision to occur.




Thanks,

Carl

    
    


reply via email to

[Prev in Thread] Current Thread [Next in Thread]