Re: beaming in tuplets

2018-04-14 Thread 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

2018-04-14 Thread 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

2018-04-13 Thread 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

2018-04-12 Thread 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

2018-04-12 Thread 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