lilypond-devel
[Top][All Lists]
Advanced

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

Re: Cleaning up auto-beaming


From: Trevor Daniels
Subject: Re: Cleaning up auto-beaming
Date: Fri, 9 Jan 2009 09:28:12 -0000

Thanks Carl.   I deliberately  avoided making any changes
to ly/music-init.ly in this first commit.  My intention was
(still is) to make a second commit which did the changes you
suggest.  The reason was these will also require a doc change.
I'm hoping the docs can be simplified quite a bit, as most
beaming changes will be able to be made with beatGrouping then.

I hadn't gone through them to work out what was needed yet,
and your note makes it easy for me now :)  Thanks again!

Trevor

----- Original Message ----- From: "Carl D. Sorensen" <address@hidden> To: "Trevor Daniels" <address@hidden>; "lily-devel" <address@hidden>
Sent: Friday, January 09, 2009 5:00 AM
Subject: Cleaning up auto-beaming


Trevor,

In your commit b3f08b20010f377fb56de90053c2a245dc99d4d5 you cleaned up
the beam settings in autobeam.scm.

I think there are couple in there that could still be eliminated, by setting
beatGrouping in ly/music-init.ly (in the alist constant for
standard-beat-grouping).

+    ;; in 3 4 time:
+    ;;   override beatLength which would end beams at 1 4 beats
+    ;;   end beams with 16th notes each 1 4 beat
+    ;;   end beams with 32nd notes each 1 8 beat

+    ((end * * 3 4) . ,(ly:make-moment 3 4))

I think this one could be eliminated by means of an entry

((3 . 4) . (3))


+    ;;   override beatLength which would end beams at 1 4 beats
+    ;;   end all beams at 1 2 beat
+    ;;   end beams with 8th triplets each 1 4 beat
+    ;;   end beams with 16th notes each 1 4 beat
+    ;;   end beams with 32nd notes each 1 8 beat

    ((end * * 4 4) . ,(ly:make-moment 1 2))


And this one could be eliminated by means of an entry

((4 . 4) . (2 2))


IMO, this would be preferable, because it's easier to change, but
I'll accept your decision, since you're the one who's been working
this whole issue.

Thanks,

Carl






reply via email to

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