Re: Y-offset not working for slurs

[Thomas Morley]

2016-09-04 0:01 GMT+02:00 Nao Nao :
> Hi,
> Does anybody know how to increase the slur vertical space without using
> control points?
> Tried this below with no success.
>
> \version "2.18.2"
> \relative c' {
>\override PhrasingSlur.direction = #UP
>\override PhrasingSlur.Y-offset = #10 %{removing this line is not making
> any difference,
>I want to make the slur higher than normal %}
>f8\( d f d g d f d\)
> }
>
> Cheers,
> Thiago


Hi Thiago,

go for positions and/or height-limit:

\version "2.18.2"

\relative c' {
   \override PhrasingSlur.direction = #UP
   \override PhrasingSlur.positions = #'(2.5 . 2.5)
   f8\( d f d g d f d\)
}

\relative c' {
   \override PhrasingSlur.direction = #UP
   \override PhrasingSlur.height-limit = #5
   f8\( d f d g d f d\)
}


Cheers,
  Harm

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

Y-offset not working for slurs

[Nao Nao]

Hi,
Does anybody know how to increase the slur vertical space without using
control points?
Tried this below with no success.

\version "2.18.2"
\relative c' {
   \override PhrasingSlur.direction = #UP
   \override PhrasingSlur.Y-offset = #10 %{removing this line is not making
any difference,
   I want to make the slur higher than normal %}
   f8\( d f d g d f d\)
}

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

RE: #'extra-offset not working

[Trevor Daniels]

Hi David

Text attached to a multimeasure rest is held in a
MultiMeasureRestText object which is created in the Voice
context.  So the override you need to move it is:

\once \override Voice.MultiMeasureRestText #'extra-offset =
#'(0 . 4)

Trevor D

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:lilypond-user-bounces+t.daniels=treda.co.u
 [EMAIL PROTECTED] Behalf Of
 David Bobroff
 Sent: 23 February 2008 00:13
 To: Lilypond-User
 Subject: #'extra-offset not working


 I'm having a weird problem.  In the following
 example I'm able to move a
 rehearsal mark but not a \markup.  Am I missing
 something or is this
 some sort of bug?

 -David

 %%* BEGIN LILYPOND *

 \version 2.11.40

 \score {
   \relative c {
   \set Score.skipBars = ##t
   \once \override Score.TextScript
 #'extra-offset = #'(0 . 4)
   R1*4^\markup{some text taking up space}
   \once \override Score.RehearsalMark
 #'extra-offset = #'(0 . -4)
   \mark \default
   R1*4
   }
 }

 \paper {
   ragged-right = ##t
 }


 %%* END LILYPOND *


 ___
 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: #'extra-offset not working

[David Bobroff]

Trevor Daniels wrote:

Hi David

Text attached to a multimeasure rest is held in a
MultiMeasureRestText object which is created in the Voice
context.  So the override you need to move it is:

\once \override Voice.MultiMeasureRestText #'extra-offset =
#'(0 . 4)


Aah...Ok.  I had already found one way around it using an anchor 
(\hspace #0) as indicated in section 1.8.1.2 of the manual, but this 
looks more like  what I'm after.


Thanks,

David


Trevor D


-Original Message-
From: [EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL PROTECTED] Behalf Of
David Bobroff
Sent: 23 February 2008 00:13
To: Lilypond-User
Subject: #'extra-offset not working


I'm having a weird problem.  In the following
example I'm able to move a
rehearsal mark but not a \markup.  Am I missing
something or is this
some sort of bug?

-David

%%* BEGIN LILYPOND *

\version 2.11.40

\score {
\relative c {
\set Score.skipBars = ##t
\once \override Score.TextScript
#'extra-offset = #'(0 . 4)
R1*4^\markup{some text taking up space}
\once \override Score.RehearsalMark
#'extra-offset = #'(0 . -4)
\mark \default
R1*4
}
}

\paper {
ragged-right = ##t
}


%%* END LILYPOND *


___
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





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

#'extra-offset not working

[David Bobroff]

I'm having a weird problem.  In the following example I'm able to move a 
rehearsal mark but not a \markup.  Am I missing something or is this 
some sort of bug?


-David

%%* BEGIN LILYPOND *

\version 2.11.40

\score {
\relative c {
\set Score.skipBars = ##t
\once \override Score.TextScript #'extra-offset = #'(0 . 4) 
R1*4^\markup{some text taking up space}
\once \override Score.RehearsalMark #'extra-offset = #'(0 . -4)
\mark \default
R1*4
}
}

\paper {
ragged-right = ##t
}


%%* END LILYPOND *


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

Re: offset not working

[Mats Bengtsson]

I would expect such marks to be left aligned with the bar lines instead
of centered over the multimeasure rest, to make it completely clear
exactly where in the music the change should happen. Here's one example:

\version 2.6.0
\score{
{ \set Score.skipBars = ##t
  \override Score.RehearsalMark #'self-alignment-X = #LEFT
  \override Score.RehearsalMark #'padding = #3
  c''1 \mark \markup{\bold Andante } |
  R1*4 \mark \markup{\bold Etwas langsamer } |
  R1*7 c''1 }
\layout{raggedright=##t}
}

   /Mats

Kris Shaffer wrote:
It's not always necessary, but regularly in orchestral parts, you will  
have a new tempo or expression mark over each of several adjacent  
multirests (especially with the overly verbose German composers like  
Strauss and Mahler).  So it would come in handy for me...


Kris

On Tue, 23 Aug 2005 18:36:57 -0400, Han-Wen Nienhuys 
[EMAIL PROTECTED]  wrote:



Kris Shaffer wrote:


Why can't LilyPond figure out the length of the text itself?
Maybe a new feature somebody wants to sponsor?

That would be a very helpful and time-saving feature, especially 
when   producing orchestral parts.  How much would it be worth?  I'd 
be  willing  to contribute a modest amount if a few others wanted to 
join  in as well.



It's not clear to me that the mm-rest text should be kept between the  
barlines. Of course, I can have a look into the cost of such a  
modification.








--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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

Re: offset not working

[Kris Shaffer]

Is ly/property-init.ly online somewhere?  I can't find a lilypond-doc  
package for Mac OS X, and I don't have any lilypond stuff in /usr/share/.


In the meantime, I tried \override MultiMeasureRestText #'no-spacing-rods  
= ##f in place of \fatText, but it did not work.  I also found in the  
program reference online that, though TextScript takes #'no-spacing-rods,  
MultiMeasureRestText does not.  Did I miss anything, or would this feature  
need to be added?


Kris


On Mon, 22 Aug 2005 23:25:17 -0400, Graham Percival [EMAIL PROTECTED]  
wrote:




On 22-Aug-05, at 6:15 PM, Kris Shaffer wrote:


One more question on this issue:
The commands \fatText and \emptyText have no effect on either

s1*0^\markup {whatever}
R1*4

or

R1*4^\markup {whatever}

How can I automatically apply the width of the markup string to the  
width of the multi-rest bar?


Take a look in ly/property-init.ly to find out what \fatText does, then  
change

the TextScript to MultiMeasureRestText.

ly/property.init.ly:
fatText = \override TextScript  #'no-spacing-rods = ##f
emptyText = \override TextScript  #'no-spacing-rods = ##t



I've added the following to the manual:

Warning!  This text is created by @code{MultiMeasureRestText}, not
@code{TextScript}.

{
\override TextScript #'padding = #5
R1^low
\override MultiMeasureRestText #'padding = #5
R1^high
}





--
Kris Shaffer
graduate student in music theory, Yale University
www.shaffermusic.com


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

Re: offset not working

[Mats Bengtsson]

It's one of the initialization files that LilyPond reads when started.
Call LilyPond with the extra flag
lilypond --verbose
to get a listing of all initialization files that are read, with the
full path.

The reason that no-spacing-rods doesn't work for MultiMeasureRestText
is that this object is a spanner, whereas TextScripts, for example are
Items. You can get some information on these issues if you look at
the program reference for spanner-interface and item-interface,
respectively (Program Reference - Backend - Graphical Object
Interfaces). If you want more details, I'm afraid one of the main
hackers have to explain.

   /Mats

Kris Shaffer wrote:
Is ly/property-init.ly online somewhere?  I can't find a lilypond-doc  
package for Mac OS X, and I don't have any lilypond stuff in /usr/share/.


In the meantime, I tried \override MultiMeasureRestText 
#'no-spacing-rods  = ##f in place of \fatText, but it did not work.  I 
also found in the  program reference online that, though TextScript 
takes #'no-spacing-rods,  MultiMeasureRestText does not.  Did I miss 
anything, or would this feature  need to be added?


Kris


On Mon, 22 Aug 2005 23:25:17 -0400, Graham Percival [EMAIL PROTECTED]  
wrote:




On 22-Aug-05, at 6:15 PM, Kris Shaffer wrote:


One more question on this issue:
The commands \fatText and \emptyText have no effect on either

s1*0^\markup {whatever}
R1*4

or

R1*4^\markup {whatever}

How can I automatically apply the width of the markup string to the  
width of the multi-rest bar?



Take a look in ly/property-init.ly to find out what \fatText does, 
then  change

the TextScript to MultiMeasureRestText.

ly/property.init.ly:
fatText = \override TextScript  #'no-spacing-rods = ##f
emptyText = \override TextScript  #'no-spacing-rods = ##t



I've added the following to the manual:

Warning!  This text is created by @code{MultiMeasureRestText}, not
@code{TextScript}.

{
\override TextScript #'padding = #5
R1^low
\override MultiMeasureRestText #'padding = #5
R1^high
}







--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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

Re: offset not working

[Kris Shaffer]

Mats,
Thanks for helping me find the init files.  Filename searches in Mac OS X  
Panther do not search the contents of *.app packages, which is why my  
searching came up empty.  But lilypond --verbose told me where to look.


So now I know why no-spacing-rods does not work, and thus why fatText does  
not work, however I still don't know how to get a multirest bar to  
accomodate the width of markup text.  I have gotten close with


   { R1*4 } \\ { \fatText s1*4^\markup { \override #'(baseline-skip  
. 0.5) \column { \line { etwas ruhiger } werdend } } \emptyText } 


The width of the bar expands to contain the text, but the multirest is too  
high by two staff lines.  And according to the manual, you cannot adjust  
the pitch of a multirest to move it up and down.  If there is another  
way to move the multirest up and down (and keep it centered), then this  
hack will work.  Is that possible?  Or is there another solution to this?   
Any help will be greatly appreciated.


Kris


On Tue, 23 Aug 2005 09:42:49 -0400, Mats Bengtsson  
[EMAIL PROTECTED] wrote:



It's one of the initialization files that LilyPond reads when started.
Call LilyPond with the extra flag
lilypond --verbose
to get a listing of all initialization files that are read, with the
full path.

The reason that no-spacing-rods doesn't work for MultiMeasureRestText
is that this object is a spanner, whereas TextScripts, for example are
Items. You can get some information on these issues if you look at
the program reference for spanner-interface and item-interface,
respectively (Program Reference - Backend - Graphical Object
Interfaces). If you want more details, I'm afraid one of the main
hackers have to explain.

/Mats

Kris Shaffer wrote:
Is ly/property-init.ly online somewhere?  I can't find a lilypond-doc   
package for Mac OS X, and I don't have any lilypond stuff in  
/usr/share/.
 In the meantime, I tried \override MultiMeasureRestText  
#'no-spacing-rods  = ##f in place of \fatText, but it did not work.  I  
also found in the  program reference online that, though TextScript  
takes #'no-spacing-rods,  MultiMeasureRestText does not.  Did I miss  
anything, or would this feature  need to be added?

 Kris
  On Mon, 22 Aug 2005 23:25:17 -0400, Graham Percival  
[EMAIL PROTECTED]  wrote:




On 22-Aug-05, at 6:15 PM, Kris Shaffer wrote:


One more question on this issue:
The commands \fatText and \emptyText have no effect on either

s1*0^\markup {whatever}
R1*4

or

R1*4^\markup {whatever}

How can I automatically apply the width of the markup string to the   
width of the multi-rest bar?



Take a look in ly/property-init.ly to find out what \fatText does,  
then  change

the TextScript to MultiMeasureRestText.

ly/property.init.ly:
fatText = \override TextScript  #'no-spacing-rods = ##f
emptyText = \override TextScript  #'no-spacing-rods = ##t



I've added the following to the manual:

Warning!  This text is created by @code{MultiMeasureRestText}, not
@code{TextScript}.

{
\override TextScript #'padding = #5
R1^low
\override MultiMeasureRestText #'padding = #5
R1^high
}









--
Kris Shaffer
graduate student in music theory, Yale University
www.shaffermusic.com


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

Re: offset not working

[Han-Wen Nienhuys]

Kris Shaffer wrote:

Mats,
Thanks for helping me find the init files.  Filename searches in Mac OS 
X  Panther do not search the contents of *.app packages, which is why 
my  searching came up empty.  But lilypond --verbose told me where to look.


So now I know why no-spacing-rods does not work, and thus why fatText 
does  not work, however I still don't know how to get a multirest bar 
to  accomodate the width of markup text.  I have gotten close with


   { R1*4 } \\ { \fatText s1*4^\markup { \override 
#'(baseline-skip  . 0.5) \column { \line { etwas ruhiger } werdend } } 
\emptyText } 


The width of the bar expands to contain the text, but the multirest is 
too  high by two staff lines.  And according to the manual, you cannot 
adjust  the pitch of a multirest to move it up and down.  If there is 
another  way to move the multirest up and down (and keep it centered), 
then this  hack will work.  Is that possible?  Or is there another 
solution to this?   Any help will be greatly appreciated.


Why don't you simply set the minimum-length property on 
MultiMeasureRest(Text)?


(If this tip helps you - please consider making a donation)

--
 Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen


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

Re: offset not working

[Mats Bengtsson]

Han-Wen Nienhuys wrote:
So now I know why no-spacing-rods does not work, and thus why fatText 
does  not work, however I still don't know how to get a multirest bar 
to  accomodate the width of markup text.  I have gotten close with


   { R1*4 } \\ { \fatText s1*4^\markup { \override 
#'(baseline-skip  . 0.5) \column { \line { etwas ruhiger } werdend } } 
\emptyText } 


The width of the bar expands to contain the text, but the multirest is 
too  high by two staff lines.  And according to the manual, you cannot 
adjust  the pitch of a multirest to move it up and down.  If there 
is another  way to move the multirest up and down (and keep it 
centered), then this  hack will work.  Is that possible?  Or is there 
another solution to this?   Any help will be greatly appreciated.



Why don't you simply set the minimum-length property on 
MultiMeasureRest(Text)?


Why can't LilyPond figure out the length of the text itself?
Maybe a new feature somebody wants to sponsor?

   /Mats


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

Re: offset not working

[Kris Shaffer]

That would be a very helpful and time-saving feature, especially when  
producing orchestral parts.  How much would it be worth?  I'd be willing  
to contribute a modest amount if a few others wanted to join in as well.


Kris

On Tue, 23 Aug 2005 15:00:44 -0400, Mats Bengtsson  
[EMAIL PROTECTED] wrote:





Han-Wen Nienhuys wrote:
So now I know why no-spacing-rods does not work, and thus why fatText  
does  not work, however I still don't know how to get a multirest bar  
to  accomodate the width of markup text.  I have gotten close with


   { R1*4 } \\ { \fatText s1*4^\markup { \override  
#'(baseline-skip  . 0.5) \column { \line { etwas ruhiger } werdend } }  
\emptyText } 


The width of the bar expands to contain the text, but the multirest is  
too  high by two staff lines.  And according to the manual, you cannot  
adjust  the pitch of a multirest to move it up and down.  If there  
is another  way to move the multirest up and down (and keep it  
centered), then this  hack will work.  Is that possible?  Or is there  
another solution to this?   Any help will be greatly appreciated.
  Why don't you simply set the minimum-length property on  
MultiMeasureRest(Text)?


Why can't LilyPond figure out the length of the text itself?
Maybe a new feature somebody wants to sponsor?

/Mats




--
Kris Shaffer
graduate student in music theory, Yale University
www.shaffermusic.com


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

Re: offset not working

[Han-Wen Nienhuys]

Kris Shaffer wrote:

Why can't LilyPond figure out the length of the text itself?
Maybe a new feature somebody wants to sponsor?

That would be a very helpful and time-saving feature, especially when  
producing orchestral parts.  How much would it be worth?  I'd be 
willing  to contribute a modest amount if a few others wanted to join in 
as well.


It's not clear to me that the mm-rest text should be kept between the 
barlines. Of course, I can have a look into the cost of such a modification.


--

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

Re: offset not working

[Kris Shaffer]

It's not always necessary, but regularly in orchestral parts, you will  
have a new tempo or expression mark over each of several adjacent  
multirests (especially with the overly verbose German composers like  
Strauss and Mahler).  So it would come in handy for me...


Kris

On Tue, 23 Aug 2005 18:36:57 -0400, Han-Wen Nienhuys [EMAIL PROTECTED]  
wrote:



Kris Shaffer wrote:

Why can't LilyPond figure out the length of the text itself?
Maybe a new feature somebody wants to sponsor?

That would be a very helpful and time-saving feature, especially when   
producing orchestral parts.  How much would it be worth?  I'd be  
willing  to contribute a modest amount if a few others wanted to join  
in as well.


It's not clear to me that the mm-rest text should be kept between the  
barlines. Of course, I can have a look into the cost of such a  
modification.






--
Kris Shaffer
graduate student in music theory, Yale University
www.shaffermusic.com


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

Re: offset not working

[Mats Bengtsson]

I don't think you understood Han-Wen's answer. Everything will work
fine if you do
\override MultiMeasureRestText #'extra-offset = #'(0 . 2.0)
or (preferably)
\override MultiMeasureRestText #'padding = #2.0

As you can read in section 8.2.1, texts attached to multi
measure rests are handled by MultiMeasureRestText layout
objects in contrast to texts attached to normal notes, which
are handled by TextScript layout objects.

The comment on using a skip note are only relevant if you want
to place something at the beginning of the bar instead of in
the middle (which is where the multimeasure rest is placed).

   /Mats

Kris Shaffer wrote:

Since the manual (section 8.2.1, page 173) mentions the need to use

s1*0^\markup {whatever }
R1*4

instead of

R1*4^\markup

to control markup alignment on a multirest, I figured it was not an  
unknown bug.  But it sounds like something I should submit, though, so  
I'll send it.  Sorry about any confusion.




--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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

Re: offset not working

[Hans de Rijck]

Kris and Mats,

thanks for your answers, I think I understand now.

Mats, is there a list somewhere of objects that can be overridden? In the
manual some (but I'm sure not all) are mentioned but only in examples. It
certainly would be helpfull to have such a list (eg. Staff.TimeSignature,
Score.skipBars, TextScript, Score.BarNumber).

thanks,

Hans.


- Original Message -
From: Mats Bengtsson [EMAIL PROTECTED]
To: Kris Shaffer [EMAIL PROTECTED]
Cc: lilypond-user@gnu.org
Sent: Monday, August 22, 2005 9:32 AM
Subject: Re: offset not working


 I don't think you understood Han-Wen's answer. Everything will work
 fine if you do
 \override MultiMeasureRestText #'extra-offset = #'(0 . 2.0)
 or (preferably)
 \override MultiMeasureRestText #'padding = #2.0

 As you can read in section 8.2.1, texts attached to multi
 measure rests are handled by MultiMeasureRestText layout
 objects in contrast to texts attached to normal notes, which
 are handled by TextScript layout objects.

 The comment on using a skip note are only relevant if you want
 to place something at the beginning of the bar instead of in
 the middle (which is where the multimeasure rest is placed).

 /Mats

 Kris Shaffer wrote:
  Since the manual (section 8.2.1, page 173) mentions the need to use
 
  s1*0^\markup {whatever }
  R1*4
 
  instead of
 
  R1*4^\markup
 
  to control markup alignment on a multirest, I figured it was not an
  unknown bug.  But it sounds like something I should submit, though, so
  I'll send it.  Sorry about any confusion.
 

 --
 =
 Mats Bengtsson
 Signal Processing
 Signals, Sensors and Systems
 Royal Institute of Technology
 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



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

Re: offset not working

[Mats Bengtsson]

Read 9.2 The \override command in the manual with all subsections
to learn how to find the relevant information.

   /Mats

Hans de Rijck wrote:

Kris and Mats,

thanks for your answers, I think I understand now.

Mats, is there a list somewhere of objects that can be overridden? In the
manual some (but I'm sure not all) are mentioned but only in examples. It
certainly would be helpfull to have such a list (eg. Staff.TimeSignature,
Score.skipBars, TextScript, Score.BarNumber).

thanks,

Hans.


- Original Message -
From: Mats Bengtsson [EMAIL PROTECTED]
To: Kris Shaffer [EMAIL PROTECTED]
Cc: lilypond-user@gnu.org
Sent: Monday, August 22, 2005 9:32 AM
Subject: Re: offset not working




I don't think you understood Han-Wen's answer. Everything will work
fine if you do
\override MultiMeasureRestText #'extra-offset = #'(0 . 2.0)
or (preferably)
\override MultiMeasureRestText #'padding = #2.0

As you can read in section 8.2.1, texts attached to multi
measure rests are handled by MultiMeasureRestText layout
objects in contrast to texts attached to normal notes, which
are handled by TextScript layout objects.

The comment on using a skip note are only relevant if you want
to place something at the beginning of the bar instead of in
the middle (which is where the multimeasure rest is placed).

   /Mats

Kris Shaffer wrote:


Since the manual (section 8.2.1, page 173) mentions the need to use

   s1*0^\markup {whatever }
   R1*4

instead of

   R1*4^\markup

to control markup alignment on a multirest, I figured it was not an
unknown bug.  But it sounds like something I should submit, though, so
I'll send it.  Sorry about any confusion.




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

Re: offset not working

[Hans de Rijck]

Mats,

I've read that. It describes how it works, but not on what objects.

From examples all over the manual one can extract some objects (Staff, Stem,
Voice) and some properties (skipBars, MetronomeMark, Stem etc) but there is
no list of all these. At least, I can't find one. It would be handy to have
such a list, so its easier to see what can be overridden.

thanks,

Hans.

- Original Message -
From: Mats Bengtsson [EMAIL PROTECTED]
To: Hans de Rijck [EMAIL PROTECTED]
Cc: lilypond-user@gnu.org
Sent: Monday, August 22, 2005 5:12 PM
Subject: Re: offset not working


 Read 9.2 The \override command in the manual with all subsections
 to learn how to find the relevant information.

 /Mats

 Hans de Rijck wrote:
  Kris and Mats,
 
  thanks for your answers, I think I understand now.
 
  Mats, is there a list somewhere of objects that can be overridden? In
the
  manual some (but I'm sure not all) are mentioned but only in examples.
It
  certainly would be helpfull to have such a list (eg.
Staff.TimeSignature,
  Score.skipBars, TextScript, Score.BarNumber).
 
  thanks,
 
  Hans.
 
 
  - Original Message -
  From: Mats Bengtsson [EMAIL PROTECTED]
  To: Kris Shaffer [EMAIL PROTECTED]
  Cc: lilypond-user@gnu.org
  Sent: Monday, August 22, 2005 9:32 AM
  Subject: Re: offset not working
 
 
 
 I don't think you understood Han-Wen's answer. Everything will work
 fine if you do
 \override MultiMeasureRestText #'extra-offset = #'(0 . 2.0)
 or (preferably)
 \override MultiMeasureRestText #'padding = #2.0
 
 As you can read in section 8.2.1, texts attached to multi
 measure rests are handled by MultiMeasureRestText layout
 objects in contrast to texts attached to normal notes, which
 are handled by TextScript layout objects.
 
 The comment on using a skip note are only relevant if you want
 to place something at the beginning of the bar instead of in
 the middle (which is where the multimeasure rest is placed).
 
 /Mats
 
 Kris Shaffer wrote:
 
 Since the manual (section 8.2.1, page 173) mentions the need to use
 
 s1*0^\markup {whatever }
 R1*4
 
 instead of
 
 R1*4^\markup
 
 to control markup alignment on a multirest, I figured it was not an
 unknown bug.  But it sounds like something I should submit, though, so
 I'll send it.  Sorry about any confusion.
 



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

Re: offset not working

[Kris Shaffer]

One more question on this issue:
The commands \fatText and \emptyText have no effect on either

s1*0^\markup {whatever}
R1*4

or

R1*4^\markup {whatever}

How can I automatically apply the width of the markup string to the width  
of the multi-rest bar?


Kris Shaffer


On Mon, 22 Aug 2005 03:32:31 -0400, Mats Bengtsson  
[EMAIL PROTECTED] wrote:



I don't think you understood Han-Wen's answer. Everything will work
fine if you do
\override MultiMeasureRestText #'extra-offset = #'(0 . 2.0)
or (preferably)
\override MultiMeasureRestText #'padding = #2.0

As you can read in section 8.2.1, texts attached to multi
measure rests are handled by MultiMeasureRestText layout
objects in contrast to texts attached to normal notes, which
are handled by TextScript layout objects.

The comment on using a skip note are only relevant if you want
to place something at the beginning of the bar instead of in
the middle (which is where the multimeasure rest is placed).

/Mats

Kris Shaffer wrote:

Since the manual (section 8.2.1, page 173) mentions the need to use
 s1*0^\markup {whatever }
R1*4
 instead of
 R1*4^\markup
 to control markup alignment on a multirest, I figured it was not an   
unknown bug.  But it sounds like something I should submit, though, so   
I'll send it.  Sorry about any confusion.








--
Kris Shaffer
graduate student in music theory, Yale University
www.shaffermusic.com


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

Re: offset not working

[Graham Percival]

On 22-Aug-05, at 6:15 PM, Kris Shaffer wrote:


One more question on this issue:
The commands \fatText and \emptyText have no effect on either

s1*0^\markup {whatever}
R1*4

or

R1*4^\markup {whatever}

How can I automatically apply the width of the markup string to the 
width of the multi-rest bar?


Take a look in ly/property-init.ly to find out what \fatText does, then 
change

the TextScript to MultiMeasureRestText.

ly/property.init.ly:
fatText = \override TextScript  #'no-spacing-rods = ##f
emptyText = \override TextScript  #'no-spacing-rods = ##t



I've added the following to the manual:

Warning!  This text is created by @code{MultiMeasureRestText}, not
@code{TextScript}.

{
\override TextScript #'padding = #5
R1^low
\override MultiMeasureRestText #'padding = #5
R1^high
}



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

offset not working

[Hans de Rijck]

Hi group,

I've tried all afternoon to get a text moved a little higher. I tried '\once
\override' with extra-offset and padding in at least five different syntaxes
but nothing works. I also tried a separate \mark \markup for the text but
with no effect. I get no errors or warnings from LilyPond, the text just
seems to be glued firmly to the staff.

See bar 2, text 'No.1 Lent et douloureux'.

If anyone could help, I'd be much obliged.

kind regards,

Hans de Rijck.
%File generated by MusicCVT, a music converter by Hans de Rijck.
%(original file: satiegy1_3.nwc, size: 24581 bytes.
% produced by [NoteWorthy Composer], version 1.75)

#(set-global-staff-size 18)
\paper
{
	#(set-paper-size a4)
	topmargin = 1.0\cm
	leftmargin = 1.0\cm
	rightmargin = 1.0\cm
	bottommargin = 1.0\cm
	raggedlastbottom = ##f
}

\version 2.6.3
\header
{
	title = Trois Gymnopédies
	composer = Erik Satie
	copyright = \markup \teeny Made with NoteWorthy Composer ®  
	tagline = \markup \teeny Typesetting by Hans de Rijck and LilyPond
	footer = 
	%{ Tempo and expression inspired by Reinbert de Leeuw. The score is public domain. %}
}

\score
{
	
	\new Staff
	{
		#(set-accidental-style 'default)
		\new Voice \relative c
		{
			% Staff 1	(Flute)

			\set Staff.instrument = #Flute
			\set Score.skipBars = ##t

			
	%MPC instruction ignored
		%\tempo 4=60  
\clef treble 
  
			\key d \major % or b \minor 
			\time 3/4
			
			R1*3/4  _\markup {\small \italic \bold {legato}} | 

			% Bar 2

\once \override TextScript #'extra-offset = #'(0 . 2.0)
			R1*3/4 ^\markup {\override #'(padding . 2.0) No.1 Lent et douloureux}|  

			% Bar 3

			R1*3/4  | 

			% Bar 4

			R1*3/4  | 

			% Bar 5

			r4  fis''(\pp   a\ |

			% Bar 6

			g fis cis | 

			% Bar 7

			b  cis\mp   d\ | 

			% Bar 8

			a2. | 

			% Bar 9

			 fis)~\pp  | 

			% Bar 10

			fis~ | 

			% Bar 11

			fis~ | 

			% Bar 12

			fis | 

			% Bar 13

			r4 fis'(  a\ | 

			% Bar 14

			g fis cis | 

			% Bar 15

			b cis  d\mp  | 

			% Bar 16

			a2.  | 

			% Bar 17

			cis\ | 

			% Bar 18

			fis | 

			% Bar 19

			 e,)~\pp  | 

			% Bar 20

			e~ | 

			% Bar 21

			e | 

			% Bar 22

			a4(  b\ c! | 

			% Bar 23

			e d b | 

			% Bar 24

			 d\mp  c! b | 

			% Bar 25

			d2.~ | 

			% Bar 26

			 d2)\pp  d4(  | 

			% Bar 27

			e\ f! g | 

			% Bar 28

			a c,!  d\mp   | 

			% Bar 29

			e\ d b | 

			% Bar 30

			d2.~ | 

			% Bar 31

			 d2)\pp  d4 | 

			% Bar 32

			g2.(  | 

			% Bar 33

			fis\ | 

			% Bar 34

			b,4 a b | 

			% Bar 35

			 cis\mp   d\ e | 

			% Bar 36

			cis d e | 

			% Bar 37

			fis,2. | 

			% Bar 38

			  a c ) | 

			% Bar 39

			 a d  | 

			% Bar 40

			R1*3/4  | 

			% Bar 41

			R1*3/4  | 

			% Bar 42

			R1*3/4  | 

			% Bar 43

			R1*3/4  | 

			% Bar 44

			r4  \stemNeutral fis'(\pp   a\ | 

			% Bar 45

			g fis cis | 

			% Bar 46

			b  cis\mp   d\ | 

			% Bar 47

			a2. | 

			% Bar 48

			 fis)~\pp  | 

			% Bar 49

			fis~ | 

			% Bar 50

			fis~ | 

			% Bar 51

			fis | 

			% Bar 52

			r4 fis'(  a\ | 

			% Bar 53

			g fis cis | 

			% Bar 54

			b cis  d\mp  | 

			% Bar 55

			a2.  | 

			% Bar 56

			cis\ | 

			% Bar 57

			fis | 

			% Bar 58

			 e,)~\pp  | 

			% Bar 59

			e~ | 

			% Bar 60

			e | 

			% Bar 61

			a4(  b\ c! | 

			% Bar 62

			e d b | 

			% Bar 63

			 d\mp  c! b | 

			% Bar 64

			d2.~ | 

			% Bar 65

			 d2)\pp  d4(  | 

			% Bar 66

			e\ f! g | 

			% Bar 67

			a c,!  d\mp   | 

			% Bar 68

			e\ d b | 

			% Bar 69

			d2.~ | 

			% Bar 70

			 d2)\pp  d4 | 

			% Bar 71

			g2.(  | 

			% Bar 72

			f!\ | 

			% Bar 73

			b,4 c! f! | 

			% Bar 74

			e d  c!\mp   | 

			% Bar 75

			e\ d c! | 

			% Bar 76

			a!2. | 

			% Bar 77

			 a c  | 

			% Bar 78

			   a d ) | 

			% Bar 79

			r\fermata \bar |. \break

			% Bar 80

			\key c \major % or a \minor 
			
r4 r2  ^\markup {\override #'(padding . 3.0) No.2  Lent et triste}| 

			% Bar 81

			r4 r2 | 

			% Bar 82

			r4 r2 | 

			% Bar 83

			r4 r2 | 

			% Bar 84

			 \stemNeutral g'2.(\p   | 

			% Bar 85

			a4\ g  f\mf   | 

			% Bar 86

			e\ f  g\p  | 

			% Bar 87

			d2.) | 

			% Bar 88

			g(  | 

			% Bar 89

			a4\ g  f\mf   | 

			% Bar 90

			e\ f  g\p  | 

			% Bar 91

			d c2) | 

			% Bar 92

			r4 r2 | 

			% Bar 93

			r4 r2 | 

			% Bar 94

			 c'2.(\mf   | 

			% Bar 95

			f,4\ g a | 

			% Bar 96

			g2. | 

			% Bar 97

			c,) | 

			% Bar 98

			f(~ | 

			% Bar 99

			 f4\f   e\ d | 

			% Bar 100

			f2.~ | 

			% Bar 101

			f4 g b | 

			% Bar 102

			a g  f\mf  | 

			% Bar 103

			g2. | 

			% Bar 104

			f) | 

			% Bar 105

			r4 r2 | 

			% Bar 106

			r4 r2 | 

			% Bar 107

			c'2.  | 

			% Bar 108

			a4\ g f | 

			% Bar 109

			g2. | 

			% Bar 110

			f~ | 

			% Bar 111

			 f4\f   e\ d | 

			% Bar 112

			f2. | 

			% Bar 113

			d~ | 

			% Bar 114

			 d4\mf  e a | 

			% Bar 115

			b2. | 

			% Bar 116

			f | 

			% Bar 

Re: offset not working

[Kris Shaffer]

I ran into this problem a couple weeks ago.  You can't move text assigned  
to a multirest (or any single full-bar rest produced by R).  Here's the  
fix:


\once \override TextScript #'extra-offset = #'(0 . 2.0) %you can use  
padding here, instead if you like

s1*0^\markup {No.1 Lent et douloureux}|
R1*3/4

The downside to this is that you cannot get \fatText to apply the width of  
the text attached to s1*0 to the R1 bar.  But in your case, that should  
not matter.


--
Kris Shaffer
graduate student in music theory, Yale University
www.shaffermusic.com


On Sun, 21 Aug 2005 13:13:06 -0400, Hans de Rijck [EMAIL PROTECTED] wrote:


Hi group,

I've tried all afternoon to get a text moved a little higher. I tried  
'\once
\override' with extra-offset and padding in at least five different  
syntaxes

but nothing works. I also tried a separate \mark \markup for the text but
with no effect. I get no errors or warnings from LilyPond, the text just
seems to be glued firmly to the staff.

See bar 2, text 'No.1 Lent et douloureux'.

If anyone could help, I'd be much obliged.

kind regards,

Hans de Rijck.



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

Re: offset not working

[Han-Wen Nienhuys]

Kris Shaffer wrote:
I ran into this problem a couple weeks ago.  You can't move text 
assigned  to a multirest (or any single full-bar rest produced by R).  


huh? bugreport please?  The grob is MultiMeasureRest{Text,Number} 
depending on whether you have to move the text or the number.


--
 Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen


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

Re: offset not working

[Kris Shaffer]

Since the manual (section 8.2.1, page 173) mentions the need to use

s1*0^\markup {whatever }
R1*4

instead of

R1*4^\markup

to control markup alignment on a multirest, I figured it was not an  
unknown bug.  But it sounds like something I should submit, though, so  
I'll send it.  Sorry about any confusion.


--
Kris Shaffer
graduate student in music theory, Yale University
www.shaffermusic.com


On Sun, 21 Aug 2005 16:39:22 -0400, Han-Wen Nienhuys [EMAIL PROTECTED]  
wrote:



Kris Shaffer wrote:
I ran into this problem a couple weeks ago.  You can't move text  
assigned  to a multirest (or any single full-bar rest produced by R).


huh? bugreport please?  The grob is MultiMeasureRest{Text,Number}  
depending on whether you have to move the text or the number.





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