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 %{r
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
CTED] 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?
gt; 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 follow
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
\onc
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
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 1
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 modes
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]
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
#'(
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,
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
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
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
pro
On 22-Aug-05, at 10:07 AM, Hans de Rijck wrote:
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
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
w
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
ould 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:
Sent: Monday, August 22, 2005 5:12 PM
Subject: Re: o
ROTECTED]>
To: "Kris Shaffer" <[EMAIL PROTECTED]>
Cc:
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 = #'
ature,
Score.skipBars, TextScript, Score.BarNumber).
thanks,
Hans.
- Original Message -
From: "Mats Bengtsson" <[EMAIL PROTECTED]>
To: "Kris Shaffer" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, August 22, 2005 9:32 AM
Subject: Re: offset not working
> I don
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 Mul
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
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.
--
H
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 doulour
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, t
25 matches
Mail list logo
