Re: Offset fermata problem

2015-10-05 Thread Jean Brefort
Hi

Use something like:
    <<
      {a2 r4}
      {s4 s16 \fermata s8.}
    >>

Regards,
Jean

Le lundi 05 octobre 2015 à 17:25 +0200, Menu Jacques a écrit :
> Hello folks,
> 
> I’d like to obtain the following from Poulenc, in which the fermata
> is in-between a2 and r4:
> 
> 
> 
> I tried with:
> 
> \version "2.19.28"
> 
> \score {
>   \relative c'' {
>     \key f \major \time 2/2 | % 147
> 
>     <<
>       {a2 r4}
>       {s2 s16 \fermata s8.}
>     >>
>     e16 -\markup{\dynamic "ff" \italic "librement"}  ^\markup{\bold
> "solo"} [ f16 g16 f16 ]
>   }
> }
> 
> 
> but then the fermata is right over the r4.
> 
> Thanks for the help!
> 
> JM
> 
> 
> 
> ___
> 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: Offset fermata problem

2015-10-05 Thread Phil Burfitt
- Original Message - 
From: "Jean Brefort" 
To: "Menu Jacques" ; "Lilypond-user Mailinglist" 


Sent: Monday, October 05, 2015 4:32 PM
Subject: Re: Offset fermata problem



Hi

Use something like:
<<
{a2 r4}
{s4 s16 \fermata s8.}
>>

Regards,
Jean

Le lundi 05 octobre 2015 à 17:25 +0200, Menu Jacques a écrit :

Hello folks,

I’d like to obtain the following from Poulenc, in which the fermata
is in-between a2 and r4:



I tried with:

\version "2.19.28"

\score {
\relative c'' {
\key f \major \time 2/2 | % 147

<<
{a2 r4}
{s2 s16 \fermata s8.}
>>
e16 -\markup{\dynamic "ff" \italic "librement"} ^\markup{\bold
"solo"} [ f16 g16 f16 ]
}
}


but then the fermata is right over the r4.

Thanks for the help!

JM





Or, ditch the second voice of rests and attach the fermata to a2 and 
override its position.


\once \override Script.extra-offset = #'(3 . 0) a2\fermata


Phil.






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


Re: Offset fermata problem

2015-10-05 Thread Pierre Perol-Schneider
Hi Jacques,

How about:

\version "2.19.28"

\score {
  \relative c'' {
\key f \major \time 2/2 | % 147
\set Score.proportionalNotationDuration = #(ly:make-moment 1/1)
<<
  { a2 r4 }
  { s4 s16 s8.\fermata s4 } %% <= e.g.
>>
\unset Score.proportionalNotationDuration
e16
-\markup{\dynamic "ff" \italic "librement"}
^\markup{\bold "solo"} [ f16 g16 f16 ]
  }

}


Cheers,
Pierre

2015-10-05 17:25 GMT+02:00 Menu Jacques :

> Hello folks,
>
> I’d like to obtain the following from Poulenc, in which the fermata is
> in-between a2 and r4:
>
>
> I tried with:
>
> \version "2.19.28"
>
> \score {
>   \relative c'' {
> \key f \major \time 2/2 | % 147
>
> <<
>   {a2 r4}
>   {s2 s16 \fermata s8.}
> >>
> e16 -\markup{\dynamic "ff" \italic "librement"}  ^\markup{\bold
> "solo"} [ f16 g16 f16 ]
>   }
> }
>
>
> but then the fermata is right over the r4.
>
> Thanks for the help!
>
> JM
>
>
>
>
> ___
> 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: Offset fermata problem

2015-10-05 Thread Menu Jacques
Hello Jean, Phil and Pierre,

Thanks for you help!

As the secondary voice doesn’t need to fill 3 quarter notes, I find that:

\score {
  \relative c'' {
\key f \major \time 2/2 | % 147

<<
  {a2 r4}
  {s4*5/4 s16 \fermata}
>>
e16 -\markup{\dynamic "ff" \italic "librement"}  ^\markup{\bold "solo"} [ 
f16 g16 f16 ]
  }
}

does what I need quite well.

JM

> Le 5 oct. 2015 à 19:42, Pierre Perol-Schneider 
>  a écrit :
> 
> Hi Jacques,
> 
> How about:
> 
> \version "2.19.28"
> 
> \score {
>   \relative c'' {
> \key f \major \time 2/2 | % 147
> \set Score.proportionalNotationDuration = #(ly:make-moment 1/1)
> <<
>   { a2 r4 }
>   { s4 s16 s8.\fermata s4 } %% <= e.g.
> >>
> \unset Score.proportionalNotationDuration
> e16 
> -\markup{\dynamic "ff" \italic "librement"}  
> ^\markup{\bold "solo"} [ f16 g16 f16 ]
>   }
>   
> }
> 
> 
> Cheers,
> Pierre
> 
> 2015-10-05 17:25 GMT+02:00 Menu Jacques  >:
> Hello folks,
> 
> I’d like to obtain the following from Poulenc, in which the fermata is 
> in-between a2 and r4:
> 
> 
> 
> I tried with:
> 
> \version "2.19.28"
> 
> \score {
>   \relative c'' {
> \key f \major \time 2/2 | % 147
> 
> <<
>   {a2 r4}
>   {s2 s16 \fermata s8.}
> >>
> e16 -\markup{\dynamic "ff" \italic "librement"}  ^\markup{\bold "solo"} [ 
> f16 g16 f16 ]
>   }
> }
> 
> 
> but then the fermata is right over the r4.
> 
> Thanks for the help!
> 
> JM
> 
> 
> 
> 
> ___
> 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

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


Re: Offset fermata problem

2015-10-05 Thread Simon Albrecht

Hello Jacques,

On 05.10.2015 17:25, Menu Jacques wrote:

Hello folks,

I’d like to obtain the following from Poulenc, in which the fermata is 
in-between a2 and r4:





based on an idea by David Kastrup I wrote a music function, which 
provides a nice interface for this kind of things:



\version "2.19.28"

after = #(define-music-function (t e m) (ly:duration? ly:music? ly:music?)
   #{ << #m { \skip $t <> -\tweak extra-spacing-width #empty-interval 
$e } >> #})


\score {
  \relative c'' {
\key f \major \time 2/2 | % 147
\after 4*5/4 \fermata a2 r4
e16 -\markup{\dynamic "ff" \italic "librement"}  ^\markup{\bold 
"solo"} [ f16 g16 f16 ]

  }
}
%

It has proved an invaluable tool, mostly with placing dynamics: no need 
to maintain extra <> constructs, much less typing, far easier 
readable code. Only drawback: point-and-click doesn’t work for the grobs 
created thus, it always points to the music function code.
In case you wonder about the order of arguments: I chose it that way 
round to keep it legible with multiple events during one note:

{ \after 4 \< \after 2 \> \after 2. \! c'1 }

Yours, Simon

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


Re: Offset fermata problem

2015-10-05 Thread Jacques Menu
Hello Simon,

Thanks a lot to DK and yourself, this « after » function is awesome!

JM

> Le 5 oct. 2015 à 20:38, Simon Albrecht  a écrit :
> 
> Hello Jacques,
> 
> On 05.10.2015 17:25, Menu Jacques wrote:
>> Hello folks,
>> 
>> I’d like to obtain the following from Poulenc, in which the fermata is 
>> in-between a2 and r4:
>> 
>> 
> 
> based on an idea by David Kastrup I wrote a music function, which provides a 
> nice interface for this kind of things:
> 
> 
> \version "2.19.28"
> 
> after = #(define-music-function (t e m) (ly:duration? ly:music? ly:music?)
>   #{ << #m { \skip $t <> -\tweak extra-spacing-width #empty-interval $e } >> 
> #})
> 
> \score {
>  \relative c'' {
>\key f \major \time 2/2 | % 147
>\after 4*5/4 \fermata a2 r4
>e16 -\markup{\dynamic "ff" \italic "librement"}  ^\markup{\bold "solo"} [ 
> f16 g16 f16 ]
>  }
> }
> %
> 
> It has proved an invaluable tool, mostly with placing dynamics: no need to 
> maintain extra <> constructs, much less typing, far easier readable code. 
> Only drawback: point-and-click doesn’t work for the grobs created thus, it 
> always points to the music function code.
> In case you wonder about the order of arguments: I chose it that way round to 
> keep it legible with multiple events during one note:
> { \after 4 \< \after 2 \> \after 2. \! c'1 }
> 
> Yours, Simon
> 
> ___
> 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: Offset fermata problem

2015-10-06 Thread David Kastrup
Simon Albrecht  writes:

> Hello Jacques,
>
> On 05.10.2015 17:25, Menu Jacques wrote:
>> Hello folks,
>>
>> I’d like to obtain the following from Poulenc, in which the fermata
>> is in-between a2 and r4:
>>
>>
>
> based on an idea by David Kastrup I wrote a music function, which
> provides a nice interface for this kind of things:
>
> 
> \version "2.19.28"
>
> after = #(define-music-function (t e m) (ly:duration? ly:music? ly:music?)
>#{ << #m { \skip $t <> -\tweak extra-spacing-width #empty-interval
> $e } >> #})
>
> \score {
>   \relative c'' {
> \key f \major \time 2/2 | % 147
> \after 4*5/4 \fermata a2 r4
> e16 -\markup{\dynamic "ff" \italic "librement"}  ^\markup{\bold
> "solo"} [ f16 g16 f16 ]
>   }
> }
> %
>
> It has proved an invaluable tool, mostly with placing dynamics: no
> need to maintain extra <> constructs, much less typing, far easier
> readable code. Only drawback: point-and-click doesn’t work for the
> grobs created thus, it always points to the music function code.

Issue 4630.

Folks, if you fail to report errors they will never get fixed.

-- 
David Kastrup

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


Re: Offset fermata problem

2015-10-06 Thread Simon Albrecht

On 06.10.2015 15:45, David Kastrup wrote:

Simon Albrecht  writes:


Hello Jacques,

On 05.10.2015 17:25, Menu Jacques wrote:

Hello folks,

I’d like to obtain the following from Poulenc, in which the fermata
is in-between a2 and r4:



based on an idea by David Kastrup I wrote a music function, which
provides a nice interface for this kind of things:


\version "2.19.28"

after = #(define-music-function (t e m) (ly:duration? ly:music? ly:music?)
#{ << #m { \skip $t <> -\tweak extra-spacing-width #empty-interval
$e } >> #})

\score {
   \relative c'' {
 \key f \major \time 2/2 | % 147
 \after 4*5/4 \fermata a2 r4
 e16 -\markup{\dynamic "ff" \italic "librement"}  ^\markup{\bold
"solo"} [ f16 g16 f16 ]
   }
}
%

It has proved an invaluable tool, mostly with placing dynamics: no
need to maintain extra <> constructs, much less typing, far easier
readable code. Only drawback: point-and-click doesn’t work for the
grobs created thus, it always points to the music function code.

Issue 4630.

Folks, if you fail to report errors they will never get fixed.


All the more thanks for addressing this nevertheless!
Yours, Simon

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