Re: Automatic beaming behaviour

On Sun, 2024-11-24 at 16:57 +0100, David Kastrup wrote: > David Sumbler writes: > > > What I don't understand is why I need both the 8th-note and 16th- > > note > > entries.  The name "beamExceptions" implies that one only needs to > > specify the exceptional beaming - but the 16th note version

Re: Automatic beaming behaviour

What I don't understand is why I need both the 8th-note and 16th-note entries.  The name "beamExceptions" implies that one only needs to specify the exceptional beaming - but the 16th note version is already the default.  Is it the case that if /any/ exception is described, then one has to de

Re: Automatic beaming behaviour

David Sumbler writes: > What I don't understand is why I need both the 8th-note and 16th-note > entries.  The name "beamExceptions" implies that one only needs to > specify the exceptional beaming - but the 16th note version is already > the default.  Is it the case that if any exception is descr

Re: Automatic beaming behaviour

On Sun, 2024-11-24 at 15:25 +0100, David Kastrup wrote: > David Sumbler writes: > > > I am setting a piece in 2/4 time.  Lilypond's default beaming > > pattern > > is to break beams at the mid-bar point, which is what one would > > generally expect.  However, I would like it to use a single beam

Re: Automatic beaming behaviour

David Sumbler writes: > I am setting a piece in 2/4 time.  Lilypond's default beaming pattern > is to break beams at the mid-bar point, which is what one would > generally expect.  However, I would like it to use a single beam for > the whole bar if, and only if, the bar consists of 4 quavers/hal

Re: Automatic beaming behaviour

On 24/11/2024 13:50, David Sumbler wrote: \version "2.24.3" \language "english" \new Staff \relative {   \time 2/4   \set Timing.baseMoment = #(ly:make-moment 1/4)   \set Timing.beatStructure = 1,1   \set Timing.beamExceptions = #'()   \set Timing.beamExceptions = \beamExceptions { 8[ 8 8 8] } c

Re: Automatic beaming with rest

-- Forwarded message -- >> From: David Kastrup >> To: Kieren MacMillan >> Cc: foxfanfare , Lilypond-User Mailing List < >> lilypond-user@gnu.org> >> Bcc: >> Date: Tue, 02 Apr 2019 17:33:07 +0200 >> Subject: Re: Automatic beaming with rest &g

Re: Automatic beaming with rest

> -- Forwarded message -- > From: David Kastrup > To: Kieren MacMillan > Cc: foxfanfare , Lilypond-User Mailing List < > lilypond-user@gnu.org> > Bcc: > Date: Tue, 02 Apr 2019 17:33:07 +0200 > Subject: Re: Automatic beaming with rest > Ki

Re: Automatic beaming with rest

Hi Carl, > I think that if we can get smarter autobeaming (like we need to do to get > subdivision and tuplets done right) we can do beaming over rests. Probably > we need to do a two-pass beam check to get the autobeaming right for > subdivision, and if we do two-pass, we can beam over rests.

Re: Automatic beaming with rest

On 4/2/19, 9:41 AM, "Kieren MacMillan" wrote: >Hi David, >> What is the "beat" as defined for the beam? > Perhaps I should use the word "moment"… Example: In 3/4, one can set the autobeamer to beam sub-quarter notes as 3, or 2+1, or 1+2, or 1+1+1 (or even other options,

Re: Automatic beaming with rest

Hi David, > What is the "beat" as defined for the beam? Perhaps I should use the word "moment"… Example: In 3/4, one can set the autobeamer to beam sub-quarter notes as 3, or 2+1, or 1+2, or 1+1+1 (or even other options, I suppose). The moment an auto-beam encompasses (as a result of the curre

Re: Automatic beaming with rest

Hi David, > So if we have > { \time 4/4 c'8 r4 c'8 8 8 8 8 } > will there be a beam across r4? Would there be a beam across c'8 c'4 c'8 ? If yes, then yes; if no, then no. > What if we have r8 r8 instead? Would there be a beam across c'8 c'8 c'8 c'8 ? If yes, then yes; if no, then no.

Re: Automatic beaming with rest

Kieren MacMillan writes: > p.s. > > Before you ask: Yes, it would be great to include the option/parameter > to extend across *all* rests that fall within the "beat" as defined > for the beam, What is the "beat" as defined for the beam? > even if they fall outside the compass of the two "bounda

Re: Automatic beaming with rest

Kieren MacMillan writes: > Hi David, > >> So if you have a bar containing only rests, the autobeamer places > beams over them? > > LOL > Sure, we can play this game… It's not a game to work out specs. It's not optional. Computers don't do handwaving. > An automatic beam must start from a note

Re: Automatic beaming with rest

Hi there, > I don't think it's quite that simple as rests that begin or end beam groups > wouldn't have beams over them, only ones in the middle. Not strictly true: in modern scores, the beam could easily extend over those rests (especially if stemlets are used). We just need to give the user

Re: Automatic beaming with rest

p.s. Before you ask: Yes, it would be great to include the option/parameter to extend across *all* rests that fall within the "beat" as defined for the beam, even if they fall outside the compass of the two "boundary notes" for the auto beam. Kieren. Kieren Ma

Re: Automatic beaming with rest

On 2019-04-02 11:05 AM, Kieren MacMillan wrote: The auto-beamer should beam according to the settings that it would apply if there were no rests. I don't think it's quite that simple as rests that begin or end beam groups wouldn't have beams over them, only ones in the middle. It might be m

Re: Automatic beaming with rest

Hi David, > So if you have a bar containing only rests, the autobeamer places beams over > them? LOL Sure, we can play this game… An automatic beam must start from a note and end at a second note. Cheers, Kieren. Kieren MacMillan, composer ‣ website: www.kiere

Re: Automatic beaming with rest

Kieren MacMillan writes: > Hi David, > >> It is not clear what that option would be supposed to do when. > > The auto-beamer should beam according to the settings that it would > apply if there were no rests. > > Seems perfectly clear to me… but maybe that’s because I want the feature. =) So if

Re: Automatic beaming with rest

Hi David, > It is not clear what that option would be supposed to do when. The auto-beamer should beam according to the settings that it would apply if there were no rests. Seems perfectly clear to me… but maybe that’s because I want the feature. =) Cheers, Kieren. ___

Re: Automatic beaming with rest

Kieren MacMillan writes: > Hey there, > >> But in my case, it is a typical engraving rule and I was wondering if I >> wasn't missing a little option like >> \set BeamOverRest = ##t > > I would love that option. Maybe submit it as a formal request? Too much handwaving. It is not clear what tha

Re: Automatic beaming with rest

Hey there, > But in my case, it is a typical engraving rule and I was wondering if I > wasn't missing a little option like > \set BeamOverRest = ##t I would love that option. Maybe submit it as a formal request? Cheers, Kieren. Kieren MacMillan, composer ‣ web

Re: Automatic beaming with rest

Kieren MacMillan wrote > The documentation explicitly says “the autobeamer will not put beams over > rests or bar lines” > (;). > I hope someone [with real Scheme-fu] offers you a function/callback/hack > that will do it autom

Re: Automatic beaming with rest

Hi there! > is there a way to make the second line of my example to look like my > third line without writing manually the brackets each time? The documentation explicitly says “the autobeamer will not put beams over rests or bar lines” (

Re: automatic beaming of tuplets only - is this possible ?

"Christopher R. Maden" writes: > On 11/21/2017 09:57 AM, David Kastrup wrote: >> "The repos" for what distribution? 2.18.0 was released in December >> 2013. What repos carry software that has been replaced 4 years ago? > > Distros released 4 years ago, like Ubuntu 14.04 LTS (Trusty, supported >

Re: automatic beaming of tuplets only - is this possible ?

On 11/21/2017 09:57 AM, David Kastrup wrote: "The repos" for what distribution? 2.18.0 was released in December 2013. What repos carry software that has been replaced 4 years ago? Distros released 4 years ago, like Ubuntu 14.04 LTS (Trusty, supported through April 2019) and its derivatives,

Re: automatic beaming of tuplets only - is this possible ?

Eby Mani writes: > Many thanks Urs. > > 2.16.2 is what is available on the repos, thus sticking to. "The repos" for what distribution? 2.18.0 was released in December 2013. What repos carry software that has been replaced 4 years ago? -- David Kastrup ___

Re: automatic beaming of tuplets only - is this possible ?

On 11/21/2017 9:26 AM, Eby Mani wrote: Many thanks Urs. 2.16.2 is what is available on the repos, thus sticking to. Eby On Tue, 21/11/17, Urs Liska wrote: >I'm on lilypond 2.16.2 on ubuntu This is *really* outdated. 2.18 has been the st

Re: automatic beaming of tuplets only - is this possible ?

Hi Ben, is there a similar snippet available for ly 2.16. ?. Thanks. On Tue, 21/11/17, Ben wrote: Subject: Re: automatic beaming of tuplets only - is this possible ? To: lilypond-user@gnu.org Date: Tuesday, 21 November, 2017, 11:36 AM On

Re: automatic beaming of tuplets only - is this possible ?

Many thanks Urs. 2.16.2 is what is available on the repos, thus sticking to. Eby On Tue, 21/11/17, Urs Liska wrote: Subject: Re: automatic beaming of tuplets only - is this possible ? To: "Eby Mani" , lilypond-user@gnu.org Date: T

Re: automatic beaming of tuplets only - is this possible ?

On 11/21/2017 1:14 AM, Eby Mani wrote: Hi All, I couldn't find how achieve the following, i tried fiddling with \set Timing and \overrideTimeSignatureSettings related commands for beaming. 1, Automatically replace tuplet bracket with a slur. https://lists.gnu.org/mailman/listinfo/lilypond-use

Re: automatic beaming of tuplets only - is this possible ?

Am 21. November 2017 07:14:01 MEZ schrieb Eby Mani : >Hi All, I couldn't find how achieve the following, i tried fiddling >with \set Timing and \overrideTimeSignatureSettings related commands >for beaming. > >1, Automatically replace tuplet bracket with a slur. > >2, Automatically break beaming o

Re: Fwd: re: automatic beaming behavior

Reilly Farrell writes: > Thank you for your responses. In this case, we're looking to set up > beaming rules that LilyPond does not follow by default (such as grouping > consecutive eighth notes in pairs of two when in 4/4 time, rather than > groups of four). > > David, your solution seems just

Re: Fwd: re: automatic beaming behavior

Thank you for your responses. In this case, we're looking to set up beaming rules that LilyPond does not follow by default (such as grouping consecutive eighth notes in pairs of two when in 4/4 time, rather than groups of four). David, your solution seems just like what we need based on what I've

Re: Fwd: re: automatic beaming behavior

On Thu 20 Jul 2017 at 11:24:25 (-0700), Reilly Farrell wrote: > We are compiling several hundred melody and rhythm examples. Each example > references the same .ily file where global settings and formatting are > handled. Is there code for setting automatic behavior of beams that we can > put in th

Re: re: automatic beaming behavior

, July 20, 2017 7:24 PM Subject: Fwd: re: automatic beaming behavior We are compiling several hundred melody and rhythm examples. Each example references the same .ily file where global settings and formatting are handled. Is there code for setting automatic behavior of beams that we can put in

Fwd: re: automatic beaming behavior

We are compiling several hundred melody and rhythm examples. Each example references the same .ily file where global settings and formatting are handled. Is there code for setting automatic behavior of beams that we can put in the .ily file (not within a \relative { } block) to resolve the issue?

Re: Automatic beaming in polymetric (scaled) context

Simon Albrecht writes: > Hello Urs, > > you need to change the beamExceptions for that, see > http://lilypond.org/doc/v2.19/Documentation/notation/beams#setting-automatic-beam-behavior. > The > syntax for that has changed recently, I see with surprise :-) If you compare http://lilypond.org/doc/

Re: [SPAM] Re: Automatic beaming in polymetric (scaled) context

Hallo Simon, Am 06.05.2014 19:53, schrieb Simon Albrecht: Hello Urs, you need to change the beamExceptions for that, see http://lilypond.org/doc/v2.19/Documentation/notation/beams#setting-automatic-beam-behavior. The syntax for that has changed recently, I see with surprise :-) So we get: \ver

Re: Automatic beaming in polymetric (scaled) context

Hello Urs, you need to change the beamExceptions for that, see http://lilypond.org/doc/v2.19/Documentation/notation/beams#setting-automatic-beam-behavior. The syntax for that has changed recently, I see with surprise :-) So we get: \version "2.19.3" \relative c' { \time 9/8 c8 c c c c c c

Re: Automatic beaming in vocal cadenzas

Colin Campbell writes: > I D/L the patch and applied it, ran make with no errors. I then > re-compiled my sample file, but saw no difference in behaviour. I > gather your patch should have prevented the melisma created in a > cadenza by manual beaming, but they still seem to happen. Do you make

Re: Automatic beaming in vocal cadenzas

On 13-10-26 02:39 AM, David Kastrup wrote: Colin Campbell writes: After wrestling with a transcription of an unmetered piece by Mark Sirett (Thou Shalt Know Him), my wife and I were going bonkers trying to get lyrics aligned to the notes. The piece has no time signature and bars of uneven leng

Re: Automatic beaming in vocal cadenzas

"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: > Sent: Saturday, October 26, 2013 4:49 AM > Subject: Re: Automatic beaming in vocal cadenzas > > >> Matthew Collett writes: >> >>> On 26/10/20

Re: Automatic beaming in vocal cadenzas

- Original Message - From: "David Kastrup" To: Sent: Saturday, October 26, 2013 4:49 AM Subject: Re: Automatic beaming in vocal cadenzas Matthew Collett writes: On 26/10/2013, at 4:10 pm, Colin Campbell wrote: We tried using \cadenzaOn to get the unmetered aspec

Re: Automatic beaming in vocal cadenzas

- Original Message - From: "Matthew Collett" To: "Colin Campbell" Cc: "LilyPond User Group" Sent: Saturday, October 26, 2013 4:28 AM Subject: Re: Automatic beaming in vocal cadenzas On 26/10/2013, at 4:10 pm, Colin Campbell wrote: We tried using \

Re: Automatic beaming in vocal cadenzas

Colin Campbell writes: > After wrestling with a transcription of an unmetered piece by Mark > Sirett (Thou Shalt Know Him), my wife and I were going bonkers trying > to get lyrics aligned to the notes. The piece has no time signature > and bars of uneven length. We tried using \cadenzaOn to get t

Re: Automatic beaming in vocal cadenzas

On 26/10/2013, at 6:58 pm, Colin Campbell wrote: We tried using \cadenzaOn to get the unmetered aspect, but the fundamental problem is that \cadenzaOn turns off autoBeam, which in turn means that manual beaming in a cadenza creates unwanted melismata. > > The aim was to get v

Re: Automatic beaming in vocal cadenzas

On 13-10-25 09:49 PM, David Kastrup wrote: Matthew Collett writes: On 26/10/2013, at 4:10 pm, Colin Campbell wrote: We tried using \cadenzaOn to get the unmetered aspect, but the fundamental problem is that \cadenzaOn turns off autoBeam, which in turn means that manual beaming in a cadenza

Re: Automatic beaming in vocal cadenzas

Matthew Collett writes: > On 26/10/2013, at 4:10 pm, Colin Campbell wrote: > >> We tried using \cadenzaOn to get the unmetered aspect, but the >> fundamental problem is that \cadenzaOn turns off autoBeam, which in >> turn means that manual beaming in a cadenza creates unwanted >> melismata. > >

Re: Automatic beaming in vocal cadenzas

On 26/10/2013, at 4:10 pm, Colin Campbell wrote: > We tried using \cadenzaOn to get the unmetered aspect, but the fundamental > problem is that \cadenzaOn turns off autoBeam, which in turn means that > manual beaming in a cadenza creates unwanted melismata. So turn the autobeaming back on. I

Re: Automatic beaming in melismas

2012/3/21 Kieren MacMillan : > 1. The default auto-beaming should produce scores which represent the current > best practice in the engraving industry, which is to ignore lyrics (inside > and outside melismas) and beam as if it were instrumental music. And using slurs for melismas (which are int

Re: Automatic beaming in melismas

Kieren MacMillan wrote Wednesday, March 21, 2012 12:50 PM Here's my opinion: 1. The default auto-beaming should produce scores which represent the current best practice in the engraving industry, which is to ignore lyrics (inside and outside melismas) and beam as if it were instr

Re: Automatic beaming in melismas

Hi Janek, > \relative c'' { > r2 d4 g,8 g > c8 c c c b16 \melisma a b c b c a b > g16 fis g a g b a b c b c d c d b c > a4 \melismaEnd r r2 > } > \addlyrics { For un -- to us a child is born, __ } > > should produce the same output as now. The cool thing would be that this: > > \relative c'

Re: Automatic beaming in melismas

On Wed, Mar 21, 2012 at 9:10 AM, Xavier Scheuer wrote: > 2012/3/21 Janek Warchoł : >> >> The cool thing would be that this: >> >> (snip) >> >> would produce automatic beaming inside the melisma.  Of course, it >> should be possible to turn this off. >> >> Is this acceptable to you? > > Maybe I'm m

Re: Automatic beaming in melismas

2012/3/21 Janek Warchoł : > > The cool thing would be that this: > > (snip) > > would produce automatic beaming inside the melisma. Of course, it > should be possible to turn this off. > > Is this acceptable to you? Maybe I'm missing an important point but AFAIK you can get automatic beaming insi

Re: Automatic beaming in melismas

On Tue, Mar 20, 2012 at 11:30 PM, Kieren MacMillan wrote: > My 2¢: > >>> I'd like to easily make choral scores with automatic beaming >>> inside melismas and none outside. > >> I 100% support your wish. > > While I 100% the idea that Lilypond should do everything for everybody > (within reason), I

Re: Automatic beaming in melismas

My 2¢: >> I'd like to easily make choral scores with automatic beaming >> inside melismas and none outside. > I 100% support your wish. While I 100% the idea that Lilypond should do everything for everybody (within reason), I ***100% oppose*** this "feature" as default: There is a very good re

Re: Automatic beaming in melismas

Hi Ben On Sun, Mar 18, 2012 at 9:48 PM, Ben Rudiak-Gould wrote: > > \version "2.15.32" > > I'd like to easily make choral scores with automatic beaming inside > melismas and none outside. Inspired by > https://code.google.com/p/lilypond/issues/detail?id=1308, I wrote a > Lilypond Guile function t

Re: Automatic beaming in 2/2

Hi me, sorry, should have read more carefully. Try: \version "2.14.2" music = \relative c'' { c16 c c c c c c c c8 c16 c c8 c16 c | r8 c c c c c c c | \break } \new Staff { \overrideTimeSignatureSettings #'(2 . 2) % timeSignatureFraction #'(1 . 4) % baseM

Re: Automatic beaming in 2/2

On 10/30/11 11:41 AM, "me" wrote: > > >I want the piece to be in 2/2 time, but with the 4/4 beamExceptions. >What's the best way to do this? Probably find the beamExceptions from 4/4 time in scm/time-signature-settings.scm and copy them into your source file. HTH, Carl

Re: Automatic beaming in 2/2

Hi me, 2011/10/30 me > (...) > > > I want the piece to be in 2/2 time, but with the 4/4 beamExceptions. > What's the best way to do this? > > which version? With "2.14.2" try: \version "2.14.2" \new Voice \relative c'' { \overrideTimeSignatureSettings #'(2 . 2) % timeSign

Re: Automatic beaming global settings

On Sep 10, 2010, at 7:44 PM, Carl Sorensen wrote: This problem is now fixed in git. If you don't build your own executable, you can get the new functionality easily by downloading scm/time-signature-settings.scm from the git repository and copying it to your scm/ directory. Otherwise, you c

Re: Automatic beaming global settings

This problem is now fixed in git. If you don't build your own executable, you can get the new functionality easily by downloading scm/time-signature-settings.scm from the git repository and copying it to your scm/ directory. Otherwise, you can wait for 2.13.33 to be released. Thanks for the bug

Re: Automatic beaming global settings

On 9/10/10 7:35 AM, "James Worlton" wrote: > Hello, > > I'm trying to define the set of default automatic beamings for a score. The > new beaming function is nice, but it won't let me set multiple rules in a > global variable. Here is what I'm trying to do--I have a rule for 4/4 and a > rule for

Re: Automatic beaming global settings

On Fri, Sep 10, 2010 at 11:52 AM, Nick Payne wrote: > On 10/09/10 23:35, James Worlton wrote: > >> Hello, >> >> I'm trying to define the set of default automatic beamings for a score. >> The new beaming function is nice, but it won't let me set multiple rules in >> a global variable. Here is what

Re: Automatic beaming global settings

On 10/09/10 23:35, James Worlton wrote: Hello, I'm trying to define the set of default automatic beamings for a score. The new beaming function is nice, but it won't let me set multiple rules in a global variable. Here is what I'm trying to do--I have a rule for 4/4 and a rule for 3/4 that li

Re: Automatic beaming of dotted quavers

On 6/1/10 10:13 AM, "Phil Holmes" wrote: > Carl, > > I spent a while trying to get this to work. It looks like the code possibly > ignores the numerator, and then treats the dotted 1/8 note as having a > minimum value of 1/16 and so applies the 1/16 override to the beaming. Yes, that's how I r

Re: Automatic beaming of dotted quavers

: "Carl Sorensen" To: "Richard Sabey" ; "Lilypond-user" Sent: Tuesday, June 01, 2010 4:59 PM Subject: Re: Automatic beaming of dotted quavers On 6/1/10 2:28 AM, "Richard Sabey" wrote: How can I get Lilypond to beam dotted quavers in 12/16 as 2 pairs pe

Re: Automatic beaming of dotted quavers

On 6/1/10 2:28 AM, "Richard Sabey" wrote: > How can I get Lilypond to beam dotted quavers in 12/16 as 2 pairs per bar > automatically, while retaining its default behaviour of beaming semiquavers in > 4 threes per bar? I've tried what I thought was the correct syntax, but it > fails. > > %%% beg

Re: Automatic beaming of tuplets

On Sun, Oct 11, 2009 at 7:33 PM, Nick Payne wrote: > I'm trying to get tupletted sixteenth notes automatically beamed in groups > of three in 3/4 time. The following beams the 16th notes in twos outside the > tuplet, but inside the \times 2/3 {} it doesn't work. Can it be done without > using manu

Re: Automatic beaming

\consists "Measure_grouping_engraver" } } } Trevor - Original Message - From: "Helge Kruse" To: "Trevor Daniels" Cc: Sent: Sunday, April 05, 2009 9:10 AM Subject: Re: Automatic beaming Trevor Daniels wrote: Helge Kruse wrote Sunday, April 05, 2009 7:22 AM I

Re: Automatic beaming

>> } \layout { \context { \Staff \consists "Measure_grouping_engraver" } } } Trevor - Original Message - From: "Helge Kruse" To: "Trevor Daniels" Cc: Sent: Sunday, April 05, 2009 9:10 AM Subject: Re: Automatic beaming Trevor Daniels wrote: Helge Kruse wrote Su

Re: Automatic beaming

Trevor Daniels wrote: Helge Kruse wrote Sunday, April 05, 2009 7:22 AM I write a piece with where are a lot of triplets in one variation. It looks nice to have the beaming in the same length as the triplets as it is done in the hand writing original. I found in the manual (1.2.4 Beams) that I

Re: Automatic beaming

Helge Kruse wrote Sunday, April 05, 2009 7:22 AM I write a piece with where are a lot of triplets in one variation. It looks nice to have the beaming in the same length as the triplets as it is done in the hand writing original. I found in the manual (1.2.4 Beams) that I can manually set b

Re: automatic beaming in tuplets

The list of predefined beaming patterns is far from complete, as you have noticed. The default rules are also a mix of general rules, for example that a beam is always ended on the third beat in 4/4 meter, and specific rules for certain note lenghts, for example that beams with 32nd notes are alwa

Re: Automatic beaming

On 27-May-06, at 1:54 PM, Stewart Holmes wrote: Hmm... I think I may have misunderstood the documentation originally. If I use -snip- it works. The trick must be to define each point in the bar at which you want the beams to break. If you have any suggested clarifications for the documentat

Re: Automatic beaming

Hello list, hello Stewart, You wrote: > Hmm... I think I may have misunderstood the documentation originally. Me too. :) > If I use > > #(override-auto-beam-setting '(end * * * *) 1 4 'Staff) > #(override-auto-beam-setting '(end * * * *) 1 2 'Staff) > #(override-auto-beam-setting '(end *

Re: Automatic beaming

s. The trick must be to define each point in the bar at which you want the beams to break. Stewart - Original Message - From: "Roland Goretzki" <[EMAIL PROTECTED]> To: Sent: Saturday, May 27, 2006 8:39 PM Subject: Re: Automatic beaming Hello list, hello Stewart, conv

Re: Automatic beaming

Hello list, hello Stewart, convert-ly and the documentation say, that You can get what You want with \set Staff.beatLength = #(ly:make-moment 1 4) instead of #(override-auto-beam-setting '(end * * * *) 1 4) But this doesn't seem to work, whereas the following does work: \set Staff.bea

Re: automatic beaming within tuplets

On Monday 05 January 2004 20.37, Vaclav Smilauer wrote: > Hello, > > I am unable to find the right duration fraction for autoBeamSettings so > that it would work in triplets. (end * * * *) works fine, but that is > not what I want as it affects everything. Pasted example shows what I > mean; I want