Re: markups and accents inside staff

2022-07-31 Thread David Kastrup
Aaron Hill  writes:

> On 2022-07-31 2:11 pm, Jim Cline wrote:
>>> Can you provide a MWE? (https://lilypond.org/tiny-examples.html)
>>> --
>>> Knute Snortum
>> Sure, here is one.  The vspace is ignored, no matter what value is
>> given.
>> %%%
>> \version "2.20.0"
>> \relative c {
>>   \time 3/4
>>   g'' e' d_\markup{\hspace #-4 \vspace #-7 x}
>> }
>
> I am not certain negative \hspace or \vspace is supported.  For
> \hspace, it probably only works by fluke.

Both are supported just fine.  But a \vspace in an (implicit) \line does
not do a whole lot.  It's essentially a "strut" but it does not affect
the skyline, just dimensions.

-- 
David Kastrup



Re: markups and accents inside staff

2022-07-31 Thread Kieren MacMillan
Hi Jim,

> I guess \vspace is not intended for use within markups?

Well… \vspace is not intended to be used within markups the way you were trying 
to use it.  :)

\markup \column {
  "this"
  \vspace #5
  "works"
}

If you want to move something down, you can use \lower:

  \markup { "this" \lower #12 "is lower" }

Hope that helps!
Kieren.


Re: markups and accents inside staff

2022-07-31 Thread Jim Cline
I am not certain negative \hspace or \vspace is supported.  For \hspace, it 
probably only works by fluke.


Hi Aaron, thanks for those examples!

To clarify, when I said that \vspace is disregarded no matter what the 
value, that includes positive values.  In fact, it is ignored regardless 
of whether \hspace is present.  I guess \vspace is not 
intended for use within markups?  --Jim




Re: markups and accents inside staff

2022-07-31 Thread Aaron Hill

On 2022-07-31 2:11 pm, Jim Cline wrote:

Can you provide a MWE? (https://lilypond.org/tiny-examples.html)

--
Knute Snortum


Sure, here is one.  The vspace is ignored, no matter what value is 
given.


%%%
\version "2.20.0"
\relative c {
  \time 3/4
  g'' e' d_\markup{\hspace #-4 \vspace #-7 x}
}


I am not certain negative \hspace or \vspace is supported.  For \hspace, 
it probably only works by fluke.


Regardless, in order to overlap the staff, you must disable 
outside-staff-priority.  Additionally, you may need to specify negative 
padding.  Consider:



\relative c {
  \time 3/4
  g'' e' d-\tweak outside-staff-priority ##f
  -\tweak X-offset -1.2 -\tweak Y-offset 1
  _\markup \with-color #red \vcenter x
}

\relative c {
  \time 3/4
  g'' e' d-\tweak outside-staff-priority ##f
  -\tweak padding #-5
  _\markup \translate #'(-1.2 . 3.5)
   \with-color #red \vcenter x
}



-- Aaron Hill



Re: markups and accents inside staff

2022-07-31 Thread Jim Cline

Can you provide a MWE? (https://lilypond.org/tiny-examples.html)

--
Knute Snortum


Sure, here is one.  The vspace is ignored, no matter what value is given.

%%%
\version "2.20.0"
\relative c {
  \time 3/4
  g'' e' d_\markup{\hspace #-4 \vspace #-7 x}
}

--Jim



Re: markups and accents inside staff

2022-07-31 Thread Knute Snortum
On Sun, Jul 31, 2022 at 8:08 AM Jim Cline  wrote:
>
> Hi Knute, thanks, that works.  I am also trying to figure out how to do
> the analogous thing with the placement of a markup text.  Putting the same
> tweaks within the markup does not compile.  Putting
>
> \markup{\hspace #4 \vspace #-2 text}
>
> applies the hspace but ignores the vspace.  --Jim

Can you provide a MWE? (https://lilypond.org/tiny-examples.html)

--
Knute Snortum



Re: markups and accents inside staff

2022-07-31 Thread David Kastrup
Jim Cline  writes:

>> You can always write something like
>>
>> %%%
>> \version "2.20.0"
>> \relative c {
>>  \time 3/4
>>  \mergeDifferentlyDottedOn
>>  <<{4\arpeggio e' d}\\{ g,8._\tweak extra-offset #'(0.5 . 3)  -> 
>> dis16 a2}>>|
>> }
>>
>> but frankly, it quite evades me why you would consider this desirable
>> over the default output.
>
> In the present example, the accent being so far away from the note leaves 
> the performer in doubt about whether it applies to the inside voice rather 
> than the whole chord, so I was trying to make that more clear. 
> thanks--jim

The solution to that, of course, is to just refrain from merging the
note heads.

-- 
David Kastrup



Re: markups and accents inside staff

2022-07-31 Thread Jim Cline

You can always write something like

%%%
\version "2.20.0"
\relative c {
 \time 3/4
 \mergeDifferentlyDottedOn
 <<{4\arpeggio e' d}\\{ g,8._\tweak extra-offset #'(0.5 . 3)  -> dis16 
a2}>>|
}

but frankly, it quite evades me why you would consider this desirable
over the default output.


In the present example, the accent being so far away from the note leaves 
the performer in doubt about whether it applies to the inside voice rather 
than the whole chord, so I was trying to make that more clear. 
thanks--jim




Re: markups and accents inside staff

2022-07-31 Thread Jim Cline
Hi Knute, thanks, that works.  I am also trying to figure out how to do 
the analogous thing with the placement of a markup text.  Putting the same 
tweaks within the markup does not compile.  Putting


\markup{\hspace #4 \vspace #-2 text}

applies the hspace but ignores the vspace.  --Jim


I believe you can do what you want by setting the
outside-staff-priority to ##f and then using Y-offset to move the
accent.

%%%
\version "2.20.0"

\relative c {
  \time 3/4
  \mergeDifferentlyDottedOn
  <<
{ 4\arpeggio e' d }
\\
{ g,8.
  -\tweak outside-staff-priority ##f
  -\tweak Y-offset -3
  _> dis16 a2
}
  >> |
}
%%%

--
Knute Snortum





Re: markups and accents inside staff

2022-07-31 Thread Knute Snortum
On Sun, Jul 31, 2022 at 7:01 AM Jim Cline  wrote:
>
> Apologies in advance; this seems like it must be simple, but I cannot find
> the answer.  I would like to be able to move an accent closer to the note
> head, possibly using markup since it would also be nice to know how to get
> markups to print over the staff lines.  Here is an example:
>
> %%%
> \version "2.20.0"
> \relative c {
>\time 3/4
>\mergeDifferentlyDottedOn
><<{4\arpeggio e' d}\\{ g,8._> dis16 a2}>>|
> }
>
> The accent prints below the beam, and I would like it higher, closer to
> the note head, even if there is some collision with the stem or the staff.
> But \vspace in markup does not allow me to do it.  --Jim

I believe you can do what you want by setting the
outside-staff-priority to ##f and then using Y-offset to move the
accent.

%%%
\version "2.20.0"

\relative c {
   \time 3/4
   \mergeDifferentlyDottedOn
   <<
 { 4\arpeggio e' d }
 \\
 { g,8.
   -\tweak outside-staff-priority ##f
   -\tweak Y-offset -3
   _> dis16 a2
 }
   >> |
}
%%%

--
Knute Snortum



Re: markups and accents inside staff

2022-07-31 Thread David Kastrup
Jim Cline  writes:

> Apologies in advance; this seems like it must be simple, but I cannot
> find the answer.  I would like to be able to move an accent closer to
> the note head, possibly using markup since it would also be nice to
> know how to get markups to print over the staff lines.  Here is an
> example:
>
> %%%
> \version "2.20.0"
> \relative c {
>   \time 3/4
>   \mergeDifferentlyDottedOn
>   <<{4\arpeggio e' d}\\{ g,8._> dis16 a2}>>|
> }
>
> The accent prints below the beam, and I would like it higher, closer
> to the note head, even if there is some collision with the stem or the
> staff.
> But \vspace in markup does not allow me to do it.  --Jim

You can always write something like

%%%
\version "2.20.0"
\relative c {
  \time 3/4
  \mergeDifferentlyDottedOn
  <<{4\arpeggio e' d}\\{ g,8._\tweak extra-offset #'(0.5 . 3)  -> 
dis16 a2}>>|
}

but frankly, it quite evades me why you would consider this desirable
over the default output.

-- 
David Kastrup



markups and accents inside staff

2022-07-31 Thread Jim Cline
Apologies in advance; this seems like it must be simple, but I cannot find 
the answer.  I would like to be able to move an accent closer to the note 
head, possibly using markup since it would also be nice to know how to get 
markups to print over the staff lines.  Here is an example:


%%%
\version "2.20.0"
\relative c {
  \time 3/4
  \mergeDifferentlyDottedOn
  <<{4\arpeggio e' d}\\{ g,8._> dis16 a2}>>|
}

The accent prints below the beam, and I would like it higher, closer to 
the note head, even if there is some collision with the stem or the staff.

But \vspace in markup does not allow me to do it.  --Jim