Re: beaming in tuplets

[David Kastrup]

Noeck  writes:

> Am 12.04.2018 um 22:48 schrieb Urs Liska:
>> Additionally remove the tuplet bracket
>> 
>>   \omit TupletBracket
>
> Or, if you want to keep them in case there is no beam (for quavers etc.):
>
> \override TupletBracket.bracket-visibility = #'if-no-beam
>
> Joram
>
>
> PS: Why is it "bracket-visibility" and not just "visibility" (it is
> already a property of a TupletBracket)?

Properties are always global and globally documented.  While
"visibility" alone is not yet taken, special values like #'if-no-beam
make this rather specific to tuplet brackets.  That's different from
things like break-visibility or transparent which work more or less
universally across grobs.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: beaming in tuplets

[Noeck]

Am 12.04.2018 um 22:48 schrieb Urs Liska:
> Additionally remove the tuplet bracket
> 
>   \omit TupletBracket

Or, if you want to keep them in case there is no beam (for quavers etc.):

\override TupletBracket.bracket-visibility = #'if-no-beam

Joram


PS: Why is it "bracket-visibility" and not just "visibility" (it is
already a property of a TupletBracket)?

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: beaming in tuplets

[David Kastrup]

Urs Liska  writes:

> Am 12.04.2018 um 20:45 schrieb Mark Stephen Mrotek:
>>
>> Marco,
>>
>> Got the 3’s on each group – see attached.
>>
>
> Finally you can tell LilyPond to automatically group consecutive tuplets:
>
>   \set tupletSpannerDuration = #(ly:make-moment 1 8)
>
> which removes the need to explicitly write so many \tuplet {} expressions.

In the mail you are replying to, Mark Stephen wrote a single \tuplet
expression.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: beaming in tuplets

[Marco Bagolin]

Thank you all :-)



2018-04-12 22:48 GMT+02:00 Urs Liska :

>
>
> Am 12.04.2018 um 20:45 schrieb Mark Stephen Mrotek:
>
> Marco,
>
>
>
> Got the 3’s on each group – see attached.
>
>
>
>
> Rather than manually counting beamlets you can set beam subdivisions:
>
>   \set subdivideBeams = ##t
>   \set baseMoment = #(ly:make-moment 1 8)
>
> and remove the manual beams.
>
> Additionally remove the tuplet bracket
>
>   \omit TupletBracket
>
> Finally you can tell LilyPond to automatically group consecutive tuplets:
>
>   \set tupletSpannerDuration = #(ly:make-moment 1 8)
>
> which removes the need to explicitly write so many \tuplet {} expressions.
>
> The full file now reads:
>
> \version "2.18.2"
>
> \relative {
>
>   % Activate beam subdivision
>   \set subdivideBeams = ##t
>   \set baseMoment = #(ly:make-moment 1 8)
>   \omit TupletBracket
>
>   % Automatically group tuplets
>   \set tupletSpannerDuration = #(ly:make-moment 1 8)
>
>   \clef bass
>   \time 4/4
>   \key bes \major
>   r8
>
>   \tuplet 3/2 {
> f16 \upbow -\markup {
>   \line { \concat { \dynamic p } \italic { accel. e cresc. }}}
> f f ges16 ges16 ges16  aes16 aes16 aes16
> bes16 bes16 bes16  c16 c16 c16
> d16 d16 d16  ees16 ees16 ees16
>   }
>   |
>   f1
> }
>
> HTH
> Urs
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: beaming in tuplets

[Urs Liska]

Am 12.04.2018 um 20:45 schrieb Mark Stephen Mrotek:


Marco,

Got the 3’s on each group – see attached.



Rather than manually counting beamlets you can set beam subdivisions:

  \set subdivideBeams = ##t
  \set baseMoment = #(ly:make-moment 1 8)

and remove the manual beams.

Additionally remove the tuplet bracket

  \omit TupletBracket

Finally you can tell LilyPond to automatically group consecutive tuplets:

  \set tupletSpannerDuration = #(ly:make-moment 1 8)

which removes the need to explicitly write so many \tuplet {} expressions.

The full file now reads:

\version "2.18.2"

\relative {

  % Activate beam subdivision
  \set subdivideBeams = ##t
  \set baseMoment = #(ly:make-moment 1 8)
  \omit TupletBracket

  % Automatically group tuplets
  \set tupletSpannerDuration = #(ly:make-moment 1 8)

  \clef bass
  \time 4/4
  \key bes \major
  r8

  \tuplet 3/2 {
    f16 \upbow -\markup {
  \line { \concat { \dynamic p } \italic { accel. e cresc. }}}
    f f ges16 ges16 ges16  aes16 aes16 aes16
    bes16 bes16 bes16  c16 c16 c16
    d16 d16 d16  ees16 ees16 ees16
  }
  |
  f1
}

HTH
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

beaming in tuplets

[Mark Stephen Mrotek]

Marco,

 

Got the 3's on each group - see attached.

 

Mark

\version "2.19.80"

\relative c {
 
\clef bass
\time 4/4
\key bes \major

r8
\tuplet 3/2 8 {f16 \upbow -\markup { \line {\concat { \dynamic p } \italic { accel. e cresc. }}}
 f f 
  ges16 ges16 
  \set stemRightBeamCount = #1
  ges16
  \set stemLeftBeamCount = #1
  aes16 aes16 aes16]
  bes16 bes16 
  \set stemRightBeamCount = #1
  bes16
  \set stemLeftBeamCount = #1
  c16 c16 c16
  d16 d16 
  \set stemRightBeamCount = #1
  d16
  \set stemLeftBeamCount = 1
  ees16 ees16 ees16 }|
f1|
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[David Kastrup]

"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
> through April 2019)

Supported by _Ubuntu_.

> and its derivatives, including Linux Mint 17.x.

Ubuntu 16.04 LTS has been out for over a year.  If you don't want to
upgrade, this has consequences for the amount of support upstream will
be able to provide for your old software.

> Like Eby, I’m generally reluctant to switch away from distro-provided
> software packages.  It’s frustrating — I wonder if there’s any way we
> can put pressure on Ubuntu to upgrade within a distro.

They'll say "use 16.04".  I doubt that they will feel that backports to
14.04 are a useful investment for anything but severe security fixes.

That being said, our packagers install (und uninstall) reasonably
smoothly.  But with 14.04, you might conceitably be hitting library
problems.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[Christopher R. Maden]

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, including Linux Mint 17.x.


Like Eby, I’m generally reluctant to switch away from distro-provided 
software packages.  It’s frustrating — I wonder if there’s any way we 
can put pressure on Ubuntu to upgrade within a distro.


(I recently switched to Linux Mint 18, and now am using LilyPond 2.18, 
which makes me very happy.)


~crism
--
Chris Maden, text nerd
http://crism.maden.org/ >
Emperor Norton had the right idea.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[David Kastrup]

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

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[Ben]

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

  stable release for years now, and you should switch at least
  to that version.
  
  Urs




Eby,

Please consider the advantages to upgrading to 2.18 - it's quite easy to 
install on Linux (regardless of what's in the repo).


sh lilypond-2.18.2 etc.

You'll find as you continue to engrave music in LilyPond that perhaps a 
lot of code you wish to use won't work properly (or at all) on older 
versions.

Lots of cool stuff has been added and enhanced significantly in 2.18 +

Good luck! :)


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[Eby Mani]

Hi Ben, is there a similar snippet available for ly 2.16. ?. Thanks.

On Tue, 21/11/17, Ben <soundsfromso...@gmail.com> 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 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.
 
 
 
 
 Eby,
 
 
 
 Does this help you? This code makes the bracket in
 tuplets into a
 curved slur.
 
 
 
 http://lilypond.1069038.n5.nabble.com/Tuplets-curved-brackets-td207326.html
 
 
 
 (image)
 
 http://lilypond.1069038.n5.nabble.com/attachment/207328/0/curved.png
 
 
 
 
 
  tupletBracketToSlur
   = {
 
    % Use slur-stencil
 
    \override TupletBracket.stencil
   = #ly:slur::print
 
    %% Use 'thickness from Slur
 
    \override TupletBracket.thickness
   = #1.2
 
    %% 'control-points need to be
 set
 
    \override TupletBracket.control-points
   =
 
      #(lambda (grob)
 
    (let* ((x-pos (ly:grob-property grob
 'X-positions))
 
   (pos (ly:grob-property
 grob 'positions))
 
   (x-ln (interval-length
 x-pos))
 
   (dir (ly:grob-property
 grob 'direction))
 
   ;; read out the height
 of the TupletBracket, may
 be
 
   ;; negative!
 
   (height (- (cdr pos)
 (car pos)))
 
   ;; height-corr is
 introduced because sometimes
   the shape
 
   ;; of the slur needs to
 be adjusted.
 
   ;; It is used in the
 2nd/3rd control-point.
 
   ;; The value of 0.3 is
 found by trial and error
 
   (height-corr (* 0.3 dir
 height))
 
   (edge-height
 (ly:grob-property grob 'edge-height
 
 
   
 '(0.7 . 0.7)))
 
   (pad 1.0))
 
      (list
 
    ;; first cp
 
    (cons
 
      (+ (car x-pos)
 0.5)
 
      (- (+ (* dir pad) (+ (car
 pos) (* -1 dir
 
   (car
 edge-height
 
    (if (= dir
 -1)
 
    (if (>
 height 3)
 
      (/ dir
 2.0)
 
     
 0.0)
 
    (if (<
 height -3)
 
      (/ dir
 2.0)
 
     
 0.0
 
    ;; second cp
 
    (cons
 
      (+ (car x-pos) (* x-ln
 1/4))
 
      (+ (* dir pad) (+ (car
 pos) (* dir (+ 0.5
   height-corr)
 
    ;; third cp
 
    (cons
 
      (+ (car x-pos) (* x-ln
 3/4))
 
      (+ (* dir pad) (+ (cdr
 pos) (* dir (- 0.5
   height-corr)
 
    ;; fourth cplilypond-u...@gnu.org,
 
    (cons
 
      (- (cdr x-pos)
 0.5)
 
      (+ (* dir pad) (+ (cdr
 pos) (* -1 dir (cdr
   edge-height)
 
      )))
 
    \override TupletBracket.staff-padding
   = #'()
 
    #(define (invert-direction x) (if (eq?
 UP
 
  (ly:tuplet-bracket::calc-direction
   x)) DOWN UP))
 
  \override TupletBracket.direction
   = #invert-direction
 
  }
 
  
 
  
 
  \layout { \tupletBracketToSlur
   }
 
  
 
  { a a \tuplet
   3/2 { a8 a a }  a4 } 
 
 
 
 
 
  
 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user
 
 -Inline Attachment Follows-
 
 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[Eby Mani]

Many thanks Urs.

2.16.2 is what is available on the repos, thus sticking to.

Eby

On Tue, 21/11/17, Urs Liska <li...@ursliska.de> wrote:

 Subject: Re: automatic beaming of tuplets only - is this possible ?
 To: "Eby Mani" <eby...@yahoo.com>, lilypond-user@gnu.org
 Date: Tuesday, 21 November, 2017, 7:55 AM
 
 
 
 Am 21. November 2017 07:14:01 MEZ schrieb Eby
 Mani <eby...@yahoo.com>:
 >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 of tuplets
 of value 16. If no tuplet,
 >then the
 beaming should default.
 >e.g. by default lilypond-user@gnu.org,
 lilypond beams tuplets {c16 d e} and f8 together. What
 >i want is the f8 should not be beamed
 together with tuplet. And if
 >there is {
 c16 d32 e f16 } in a tuplet, it should be beamed
 together.
 >
 >Is point
 number 2 possible without manual beam breaks ?.
 >
 
 Not yet.
 We have just started a discussion about how tuplets should
 affect beaming and the subdivision of secondary beams.
 Hopefully this will be fixed in the foreseeable
 future.
 Which leads to ...
  lilypond-user@gnu.org,
 >
 >I'm on lilypond
 2.16.2 on ubuntu 
 
 This is *really* outdated. 2.18 has been the
 stable release for years now, and you should switch at least
 to that version.
 
 Urs
 
 -- 
 Diese
 Nachricht wurde von meinem Android-Gerät mit K-9 Mail
 gesendet.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[Ben]

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-user


Eby,

Does this help you? This code makes the bracket in tuplets into a curved 
slur.


http://lilypond.1069038.n5.nabble.com/Tuplets-curved-brackets-td207326.html

(image)
http://lilypond.1069038.n5.nabble.com/attachment/207328/0/curved.png


tupletBracketToSlur = {
  % Use slur-stencil
  \override TupletBracket.stencil = #ly:slur::print
  %% Use 'thickness from Slur
  \override TupletBracket.thickness = #1.2
  %% 'control-points need to be set
  \override TupletBracket.control-points =
    #(lambda (grob)
  (let* ((x-pos (ly:grob-property grob 'X-positions))
 (pos (ly:grob-property grob 'positions))
 (x-ln (interval-length x-pos))
 (dir (ly:grob-property grob 'direction))
 ;; read out the height of the TupletBracket, may be
 ;; negative!
 (height (- (cdr pos) (car pos)))
 ;; height-corr is introduced because sometimes the shape
 ;; of the slur needs to be adjusted.
 ;; It is used in the 2nd/3rd control-point.
 ;; The value of 0.3 is found by trial and error
 (height-corr (* 0.3 dir height))
 (edge-height (ly:grob-property grob 'edge-height
   '(0.7 . 0.7)))
 (pad 1.0))
    (list
  ;; first cp
  (cons
    (+ (car x-pos) 0.5)
    (- (+ (* dir pad) (+ (car pos) (* -1 dir
 (car edge-height
  (if (= dir -1)
  (if (> height 3)
    (/ dir 2.0)
    0.0)
  (if (< height -3)
    (/ dir 2.0)
    0.0
  ;; second cp
  (cons
    (+ (car x-pos) (* x-ln 1/4))
    (+ (* dir pad) (+ (car pos) (* dir (+ 0.5 height-corr)
  ;; third cp
  (cons
    (+ (car x-pos) (* x-ln 3/4))
    (+ (* dir pad) (+ (cdr pos) (* dir (- 0.5 height-corr)
  ;; fourth cp
  (cons
    (- (cdr x-pos) 0.5)
    (+ (* dir pad) (+ (cdr pos) (* -1 dir (cdr edge-height)
    )))
  \override TupletBracket.staff-padding = #'()
  #(define (invert-direction x) (if (eq? UP
(ly:tuplet-bracket::calc-direction x)) DOWN UP))
\override TupletBracket.direction = #invert-direction
}


\layout { \tupletBracketToSlur }

{ a a \tuplet 3/2 { a8 a a }  a4 }


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

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

[Urs Liska]

Am 21. November 2017 07:14:01 MEZ schrieb Eby Mani <eby...@yahoo.com>:
>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 of tuplets of value 16. If no tuplet,
>then the beaming should default.
>e.g. by default lilypond beams tuplets {c16 d e} and f8 together. What
>i want is the f8 should not be beamed together with tuplet. And if
>there is { c16 d32 e f16 } in a tuplet, it should be beamed together.
>
>Is point number 2 possible without manual beam breaks ?.
>

Not yet. We have just started a discussion about how tuplets should affect 
beaming and the subdivision of secondary beams.
Hopefully this will be fixed in the foreseeable future.
Which leads to ...

>
>I'm on lilypond 2.16.2 on ubuntu 

This is *really* outdated. 2.18 has been the stable release for years now, and 
you should switch at least to that version.

Urs

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-beaming in tuplets?

[David Kastrup]

Graham Percival gra...@percival-music.ca writes:

 On Thu, Dec 29, 2011 at 04:18:04PM +0100, Rutger Hofman wrote:
 This is fixed in the latest development version.
 
 Is it strongly disadvised to upgrade to that for 'stable' usage?

 Yes.

The current version is an improvement in a number of ways, but you are,
for example, at the moment likely to get into a number of back-and-forth
iterations concerning spacing issues that are finally getting addressed
after years.  So you are getting snapshots that are improved in a number
of ways, but which it does not really make all that much sense to settle
on if you want to keep using them for a long time.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Auto-beaming in tuplets?

[Rutger Hofman]

Hello list,

the auto-beaming I get with a (8. 16 8) figure is fine for e.g. 6/8 
time, but if it is within a tuplet, the second beam at the 16/th extends 
to the wrong side. See attached .png and its .ly source.


Can you please point me how I can fix this, e.g. with an autobeaming 
rule/exception?


Thanks,

Rutger Hofman
Amsterdam
\version 2.14.2

\score {
\relative c'' {
	\time 1/4
	\times 2/3 { c8. c16 c8 }
	\time 3/8
	c8. c16 c8
}

\layout {
	raggedright = #'t
}
}
attachment: triplet-beam.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-beaming in tuplets?

[Phil Holmes]

- Original Message - 
From: Rutger Hofman rut...@cs.vu.nl

To: lilypond-user@gnu.org
Sent: Thursday, December 29, 2011 2:12 PM
Subject: Auto-beaming in tuplets?



Hello list,

the auto-beaming I get with a (8. 16 8) figure is fine for e.g. 6/8 
time, but if it is within a tuplet, the second beam at the 16/th extends 
to the wrong side. See attached .png and its .ly source.


Can you please point me how I can fix this, e.g. with an autobeaming 
rule/exception?


Thanks,

Rutger Hofman
Amsterdam



This is fixed in the latest development version.

--
Phil Holmes



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-beaming in tuplets?

[Rutger Hofman]

On 12/29/2011 03:18 PM, Phil Holmes wrote:

- Original Message - From: Rutger Hofman rut...@cs.vu.nl
To: lilypond-user@gnu.org
Sent: Thursday, December 29, 2011 2:12 PM
Subject: Auto-beaming in tuplets?



Hello list,

the auto-beaming I get with a (8. 16 8) figure is fine for e.g. 6/8
time, but if it is within a tuplet, the second beam at the 16/th
extends to the wrong side. See attached .png and its .ly source.

Can you please point me how I can fix this, e.g. with an autobeaming
rule/exception?

Thanks,

Rutger Hofman
Amsterdam



This is fixed in the latest development version.


Is it strongly disadvised to upgrade to that for 'stable' usage?

Rutger

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-beaming in tuplets?

[Xavier Scheuer]

On 29 December 2011 16:23, Graham Percival gra...@percival-music.ca wrote:

 Yes.

Thank you Graham for this raisoned and well-arhued answer.

Rutger, have a look at what 2 lead developers have recently said about
using development version:
http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00503.html
http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00505.html

Cheers,
Xavier

-- 
Xavier Scheuer x.sche...@gmail.com

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-beaming in tuplets?

[Graham Percival]

On Thu, Dec 29, 2011 at 04:18:04PM +0100, Rutger Hofman wrote:
 This is fixed in the latest development version.
 
 Is it strongly disadvised to upgrade to that for 'stable' usage?

Yes.

Cheers,
- Graham

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Auto-beaming in tuplets?

[Keith OHara]

Rutger Hofman rutger at cs.vu.nl writes:

 
 Hello list,
 
 the auto-beaming I get with a (8. 16 8) figure is fine for e.g. 6/8 
 time, but if it is within a tuplet, the second beam at the 16/th extends 
 to the wrong side. See attached .png and its .ly source.
 
 Can you please point me how I can fix this, e.g. with an autobeaming 
 rule/exception?
 

Given that this is a very specific bug,
http://code.google.com/p/lilypond/issues/detail?id=11
that will be fixed in the next stable version, I suggest a brute-force
override:

\version 2.14.2
bl = {
  \set stemLeftBeamCount = #2 
  \set stemRightBeamCount = #1
}
\score {
  \relative c'' {
\time 1/4
\times 2/3 { c8. \bl c16 c8 }
  }
}




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Default beaming with tuplets

[Carl Sorensen]

On 12/25/09 4:31 AM, Nick Payne nick.pa...@internode.on.net wrote:

 Notes in a tuplet by default are getting beamed with notes outside the
 tuplet. Should the default beaming rules be doing this?

No, they should not.

Ccing to bug list.

I'll look into this some more.


 
 \version 2.13.9
 
 \relative c'' {
  \time 3/4
  c4. c8 \times 2/3 { c aes g }
 }
 

Thanks for the report, Nick.

Carl



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Default beaming with tuplets

[Carl Sorensen]

On 12/25/09 4:31 AM, Nick Payne nick.pa...@internode.on.net wrote:

 Notes in a tuplet by default are getting beamed with notes outside the
 tuplet. Should the default beaming rules be doing this?
 
 \version 2.13.9
 
 \relative c'' {
  \time 3/4
  c4. c8 \times 2/3 { c aes g }
 }
 

Nick,

If you want to fix this, you can do so (as long as you aren't using the
measure_grouping_engraver) with the following:

\overrideBeamSettings #'Score #'(5 . 16) #'end #'((* . (1 1 1)))

HTH,

Carl



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Default beaming with tuplets

[Carl Sorensen]

On 12/26/09 5:47 AM, Carl Sorensen c_soren...@byu.edu wrote:

 
 
 
 
 On 12/25/09 4:31 AM, Nick Payne nick.pa...@internode.on.net wrote:
 
 Notes in a tuplet by default are getting beamed with notes outside the
 tuplet. Should the default beaming rules be doing this?
 
 \version 2.13.9
 
 \relative c'' {
  \time 3/4
  c4. c8 \times 2/3 { c aes g }
 }
 
 
 Nick,
 
 If you want to fix this, you can do so (as long as you aren't using the
 measure_grouping_engraver) with the following:
 
 \overrideBeamSettings #'Score #'(5 . 16) #'end #'((* . (1 1 1)))

Oops, I pasted the wrong thing.

 \overrideBeamSettings #'Score #'(3 . 4) #'end #'((* . (1 1 1)))


Sorry,

Carl



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Default beaming with tuplets

[Nick Payne]

Notes in a tuplet by default are getting beamed with notes outside the 
tuplet. Should the default beaming rules be doing this?


\version 2.13.9

\relative c'' {
\time 3/4
c4. c8 \times 2/3 { c aes g }
}

Nick
attachment: test.preview.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Automatic beaming of tuplets

[Nick Payne]

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 manual beaming?


\version 2.13.4

\relative c' {
   \time 3/4
   \overrideBeamSettings #'Voice #'(3 . 4) #'end #'((* . (3))
   ((1 . 16) . (2 2 2 2 2 2))
   ((1 . 32) . (8 8 8))
   ((1 . 64) . (16 16 16))
   ((1 . 128) . (32 32 32)))
   f16 a f a f a f a f a f a |
   \times 2/3 {
   e16 d' b' c,, e g e g a g c e a, c f f, c' a' |
   }
}

Nick


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Automatic beaming of tuplets

[Jay Anderson]

On Sun, Oct 11, 2009 at 7:33 PM, Nick Payne nick.pa...@internode.on.net 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 manual beaming?

\version 2.13.4

\relative c' {
  \time 3/4
  \overrideBeamSettings #'Voice #'(3 . 4) #'end #'((* . (3))
  ((1 . 16) . (2 2 2 2 2 2))
  ((1 . 24) . (3 3 3 3 3 3))
  ((1 . 32) . (8 8 8))
  ((1 . 64) . (16 16 16))
  ((1 . 128) . (32 32 32)))
  \set tupletSpannerDuration = #(ly:make-moment 1 8)
  f16 a f a f a f a f a f a |
  \times 2/3 {
  e16 d' b' c,, e g e g a g c e a, c f f, c' a' |
  }
}

Triplet sixteenths are  (1 . 24). Good default values for this and
triplet eights probably ought to be added. For 3/4 it's probably ((1 .
12) . (3 3 3)) for eights and the above for sixteenths.

-Jay


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: automatic beaming in tuplets

[Mats Bengtsson]

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 always
ended on every 8th note in 4/4.

For tuplets in general, there is only one specific rule included among the
default beaming patterns, namely that triplet 8ths should be ended on
each beat in 4/4.

Of course it would be possible to extend the list, but at least with the
current mechanism, this would make the list of default beaming patterns
extremely long (which even might influence the LilyPond processing time)
and still there will always be some user who wants a special case that's
not covered. The strategy chosen in LilyPond today is to let the default
settings cover the most common everyday music typesetting needs and
provide instructions on how each user can extend the beaming patterns
according to her/his needs and preferences.

For example, I have extended your example with the corresponding
auto-beam settings. Normally, you could enter all these at the top of the
piece, but here I inserted them in front of the bar where they are used.
\version 2.11.41


\relative c'' {
\time 4/4
% c1
c8 c c c c c c c
% c2
c16 c c c  c c c c  c c c c  c c c c
% c3
#(override-auto-beam-setting '(end 1 20 4 4) 1 4)
#(override-auto-beam-setting '(end 1 20 4 4) 3 4)
\times 4/5 { c16 c c c c } \times 4/5 { c16 c c c c } c8 c \times 4/5 { 
c16 c c c c }

% c4
#(override-auto-beam-setting '(end 1 24 4 4) 1 4)
#(override-auto-beam-setting '(end 1 24 4 4) 3 4)
\times 4/6 { c16 c c c c c } \times 4/6 { c16 c c c c c } c8 c \times 
4/6 { c16 c c c c c }

% c5
#(override-auto-beam-setting '(end 1 28 4 4) 1 4)
#(override-auto-beam-setting '(end 1 28 4 4) 3 4)
\times 8/7 { c32 c c c c c c } \times 8/7 { c32 c c c c c c } c32 c c c 
c c c c  c32 c c c c c c c

% c6
#(override-auto-beam-setting '(end 1 10 4 4) 1 4)
#(override-auto-beam-setting '(end 1 10 4 4) 3 4)
c8 c \times 4/5 { c8 c c c c } c4
}

   /Mats


luis jure wrote:

hello list,

i'm a beginner at lilypond, i know enough to enter music in a simple
way. i still don't know enough of the language to try elaborate tweaks,
but i find that usually lilypond is smart enough to produce good output
for music that's not too complex.

but i suspect that automatic beaming is not working correctly in
certain cases involving tuplets. i include a short snippet with the
corresponding image. i'm using a recently compiled 2.11.41 on linux.

in 4/4 time signature, eight notes are beamed every 4 notes (i. e. into
whole notes, m.1 in the example), which is of course correct; sixteenth
notes are also correctly beamed every 4 notes into quarter notes (m.2).
but 16th notes quintuplets and sextuplets are beamed into whole notes,
even if that means including a pair of eight notes (m3 and m4). the
same with 32nd septuplets (m5). normal 32nd notes, on the other hand,
are beamed every 4 notes into eight notes, while i find that beaming
every 8 notes is more standard. i find other anomalies, like the 8th
notes quintuplet beamed together with the preceding 8th notes (m6).

as a beginner, i don't know if these are bugs, my mistakes, or if that
is the intended behavior. in the last case, could i ask the authors to
reconsider the criteria used for automatic beaming? 


i know that you can adjust the beaming manually, or even change the
automatic beam behavior globally. but i think that the defaults should
be chosen in a way that requires as little manual tweaks as possible.

thank you for your attention.

best,

lj
  






___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
  


--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44  STOCKHOLM
Sweden
Phone: (+46) 8 790 8463 
   Fax:   (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

automatic beaming in tuplets

[luis jure]

hello list,

i'm a beginner at lilypond, i know enough to enter music in a simple
way. i still don't know enough of the language to try elaborate tweaks,
but i find that usually lilypond is smart enough to produce good output
for music that's not too complex.

but i suspect that automatic beaming is not working correctly in
certain cases involving tuplets. i include a short snippet with the
corresponding image. i'm using a recently compiled 2.11.41 on linux.

in 4/4 time signature, eight notes are beamed every 4 notes (i. e. into
whole notes, m.1 in the example), which is of course correct; sixteenth
notes are also correctly beamed every 4 notes into quarter notes (m.2).
but 16th notes quintuplets and sextuplets are beamed into whole notes,
even if that means including a pair of eight notes (m3 and m4). the
same with 32nd septuplets (m5). normal 32nd notes, on the other hand,
are beamed every 4 notes into eight notes, while i find that beaming
every 8 notes is more standard. i find other anomalies, like the 8th
notes quintuplet beamed together with the preceding 8th notes (m6).

as a beginner, i don't know if these are bugs, my mistakes, or if that
is the intended behavior. in the last case, could i ask the authors to
reconsider the criteria used for automatic beaming? 

i know that you can adjust the beaming manually, or even change the
automatic beam behavior globally. but i think that the defaults should
be chosen in a way that requires as little manual tweaks as possible.

thank you for your attention.

best,

lj


beams.ly
Description: Binary data
attachment: beams.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: odd beaming in tuplets

[Graham Percival]

This is issue #11; unfortunately it will likely remain for a while.

http://code.google.com/p/lilypond/issues/detail?id=11

Sorry,
- Graham

David Bobroff wrote:

I'm having a similar issue with v2.11.32:

%%% BEGIN LILYPOND %%%

\version 2.11.32

\score {
\relative c' {
\times 2/3 {c8 c16 c c8} c4 c c
}
}

%%% END LILYPOND %%%

BUG:

The two 16ths have beams, but they point in opposite directions rather 
than being joined between the two 16ths.


-David Bobroff


___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond





___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

odd beaming in tuplets

[andersvi]

[Sorry for doubles, but the image file wasnt included in the post sent
from the web-interface. AV.]

Hi there.

Is the strange beaming inside the tuplet in the first 4/8 measure of
this sniplet expected?  Right now im overriding with manually setting
stemBeamCount to correct values, but its very tedious.

attachment: lilypond-beaming-oddness.jpg

\version 2.10.20

\relative c' { 
 
 \time 2/4
 \times 4/5 { a32 a a16. } a8 a a |
 a32 a a16 a8 a a |

 \time 4/8 
 \times 4/5 { a32 a a16. } a8 a a |
 a32 a a16 a8 a a |
   }

   
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: odd beaming in tuplets

[Damian leGassick]

IMO the beaming should be the same for 2/4 or 4/8

i'd submit it as a bug unless someone chimes in...

d

(fwiw in 2.11.34 the spacing seems better)

On 1 Oct 2007, at 15:33, [EMAIL PROTECTED] wrote:


[Sorry for doubles, but the image file wasnt included in the post sent
from the web-interface. AV.]

Hi there.

Is the strange beaming inside the tuplet in the first 4/8 measure of
this sniplet expected?  Right now im overriding with manually setting
stemBeamCount to correct values, but its very tedious.

lilypond-beaming-oddness.jpg

\version 2.10.20

\relative c' {

 \time 2/4
 \times 4/5 { a32 a a16. } a8 a a |
 a32 a a16 a8 a a |

 \time 4/8
 \times 4/5 { a32 a a16. } a8 a a |
 a32 a a16 a8 a a |
   }


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: odd beaming in tuplets

[David Bobroff]

[EMAIL PROTECTED] wrote:

[Sorry for doubles, but the image file wasnt included in the post sent
from the web-interface. AV.]





Hi there.

Is the strange beaming inside the tuplet in the first 4/8 measure of
this sniplet expected?  Right now im overriding with manually setting
stemBeamCount to correct values, but its very tedious.










\version 2.10.20

\relative c' { 
 
 \time 2/4

 \times 4/5 { a32 a a16. } a8 a a |
 a32 a a16 a8 a a |

 \time 4/8 
 \times 4/5 { a32 a a16. } a8 a a |

 a32 a a16 a8 a a |
   }



I'm having a similar issue with v2.11.32:

%%% BEGIN LILYPOND %%%

\version 2.11.32

\score {
\relative c' {
\times 2/3 {c8 c16 c c8} c4 c c
}
}

%%% END LILYPOND %%%

BUG:

The two 16ths have beams, but they point in opposite directions rather 
than being joined between the two 16ths.


-David Bobroff


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: odd beaming in tuplets

[Hans Aberg]

On 1 Oct 2007, at 16:33, [EMAIL PROTECTED] wrote:


Is the strange beaming inside the tuplet in the first 4/8 measure of
this sniplet expected?  Right now im overriding with manually setting
stemBeamCount to correct values, but its very tedious.


I have similar problems with some irregular meters. See the Bug-Bison  
list, Beams not connecting. It worked in earlier versions, but  
Lilypond had a change of beams.


  Hans Åberg




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

odd beaming in tuplets

[Anders Vinjar]

Hi there.

Is the strange beaming inside the tuplet in the first 4/8 measure of
this sniplet expected?  Right now im overriding with manually setting
stemBeamCount to correct values, but its very tedious.

[2. image notation --- image/jpeg; lilypond-beaming-oddness.jpg]...



\version 2.10.20

\relative c' { 
 
 \time 2/4
 \times 4/5 { a32 a a16. } a8 a a |
 a32 a a16 a8 a a |

 \time 4/8 
 \times 4/5 { a32 a a16. } a8 a a |
 a32 a a16 a8 a a |
   }

   




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: beaming and tuplets

[Henrik Frisk]

  The tuplet bracket in the example below has to be manually adjusted when
  I beam the 16th note triplet with the rests. It has a slant in the wrong
  direction and collides with the beam.
 
  
  \version 2.9.11
 
  \new Staff \relative c' {
\times 2/3 { d16 [
e r16
  } r8 ]
  }
  
 
  /Henrik

 Any progress on this?  I also reported it several weeks ago.
 
 Thanks,
 
 Paul Scott

I didn't hear anything from the list, no. I just adjust it manually for
the time being.

best,

/henrik


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: beaming and tuplets

[Paul Scott]

Henrik Frisk wrote:

Hello again,

The tuplet bracket in the example below has to be manually adjusted when
I beam the 16th note triplet with the rests. It has a slant in the wrong
direction and collides with the beam.


\version 2.9.11

\new Staff \relative c' {
  \times 2/3 { 
d16 [

  e r16
} r8 ]
}


/Henrik
  

Any progress on this?  I also reported it several weeks ago.

Thanks,

Paul Scott



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

beaming and tuplets

[Henrik Frisk]

Hello again,

The tuplet bracket in the example below has to be manually adjusted when
I beam the 16th note triplet with the rests. It has a slant in the wrong
direction and collides with the beam.


\version 2.9.11

\new Staff \relative c' {
  \times 2/3 { 
d16 [
  e r16
} r8 ]
}


/Henrik


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

automatic beaming within tuplets

[Vaclav Smilauer]

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 all the c's beamed with two beams, not four.

Thanks for help. Vaclav. (LilyPond 2.1.0)

\score {
 \notes {
   \relative c' {
 \property Voice.autoBeamSettings \override #'(end 1 8 * *) = 
#(ly:make-moment 1 2)
 \times 2/3 { c'8 c c c c c c c c c c c} d d d d d d d d
   }
 }
}



___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user