Re: textSpanner at arbitrary positions independent of music

[Ryan Michael]

I figured it out, I had to make a spacer notes in a seperate voice to cover
the system break. e.g.

%
<<
\new Voice {
\once
\override TextSpanner.bound-details.left.text =
  \markup { \upright \huge "molto rit." }
s1\startTextSpan s1 s8 s8 s8 s8 s8 s8 s8 s8 s8\stopTextSpan %here is where
the system break occured

}
\new Voice {
r1 r1 r1
}
>>

r1\startTextSpan r1\stopTextSpan


On Sun, Oct 14, 2018 at 2:27 AM Ryan Michael 
wrote:

> THank you Pierre,
> exactly what i was looking for. However, how can i turn off the left
> textSpan property if i want to span four bars which is broken over two
> systems, and i don't wish to repeat the "molto rit" for the left attribute
> of the span in the second system?
>
> On Sun, Oct 14, 2018 at 1:34 AM Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> wrote:
>
>> Hi Ryan,
>> Your example does not compile.
>> How about putting the text into the sapnner ?
>> Cf.
>> http://lilypond.org/doc/v2.18/Documentation/notation/writing-text.html#text-spanners
>> Cheers,
>> Pierre
>>
>> Le dim. 14 oct. 2018 à 09:38, Ryan Michael  a
>> écrit :
>>
>>> Hi all
>>>
>>> So i have a scenario where I want a textSpanner to follow a heading i
>>> have
>>> over the treble clef of a system where there is only action in the left
>>> hand (Bass clef). e.g.
>>>
>>> %
>>> \version "2.18.2"
>>> up = \new Staff = "up" {
>>> r1/^\markup{\huge "molto rit."}  r1\startTextSpanner r1
>>> r1\stopTextSpanner
>>> }
>>>
>>> down = \new Staff = "down" {
>>> c,,4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4
>>> }
>>> {
>>>   \new PianoStaff <<
>>>  \up
>>>\down
>>>   >>
>>> }
>>> 
>>>
>>> my issues is that i want the spanner to really start immediately after
>>> the markup. do i have to make some fake notes in the right hand to anchor
>>> the spanner or can i just move it around by other means?
>>>
>>> best,
>>> ryan.
>>> --
>>> ॐ नमः शिवाय
>>> ___
>>> 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

Get NoteName as String

[SK]

Hello,

I try to find a way to get a notename as string, so that it can be
processed further. To be concrete, I want to build a scale task generator
that randomly selects a pitch and scale, then prints the scale as notes as
well as the tonic/root/finalis and the mode as lyrics (or other text). The
result should look like the file I attached, but it is important to insert
the pitch in the lyrics automatically.

I tried to get the text from a NoteNames context, but didn't come close to
what I need. Maybe someone out there has a better idea...

All the best!
\score {
 {
   \key #(ly:make-pitch 1 3 0) \dorian
   <<
   \transpose d f
   { d' e' f' g' a' b' c'' d'' }
   \new NoteNames {  } >>
 } \addlyrics { "f dorian" _ }
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Baseline align in TextSpanner

[Davide Liessi]

Dear Kieren,

Il giorno ven 5 ott 2018 alle ore 15:11 Kieren MacMillan
 ha scritto:
> This works for me:
[...]

your solution works well to keep all TextSpanners baseline-aligned,
but it still does not solve my real problem, which indeed was not
apparent in my first message.
I'm trying to make TextSpanners and tempo markings look the same,
including being aligned at the same baseline.
The reason is to follow the recommendations of Gould for tempo
alteration markings (example at page 184).

A slightly more realistic example follows: I would like to align
\tempo markings and TextSpanners to the same baseline.
As you can see using your trick on both does achieve the desired result.
I renamed the \test function to a more specific \baseline-align.
I'm cc-ing also Harm / Thomas Morley because I'm using his code, so he
may have some insights or suggestions.

Thanks for your help so far.
Best wishes!
Davide

%%% new example
\version "2.19.81"

#(define (lists-map function ls)
   "Apply @var{function} to @var{ls} and all of it sublists.
First it recurses over the children, then the function is applied to
@var{ls}."
   (if (list? ls)
   (set! ls (map (lambda (y) (lists-map function y)) ls))
   ls)
   (function ls))

#(define baseline-align-proc
   (lambda (e)
 (if (and (list? e) (member 'glyph-string e))
 (begin
  (for-each
   (lambda (x)
 (begin
  (set-car! (cadr x) 0)
  x))
   (cadr (last e)))
  e)
 e)))

#(define-markup-command (baseline-align layout props glyph-name)
   (markup?)
   (let* ((stil (interpret-markup layout props glyph-name))
  (new-stile-expr
   (lists-map
baseline-align-proc
(ly:stencil-expr stil

 (ly:make-stencil
  new-stile-expr
  (ly:stencil-extent stil X)
  ;(cons 0 (cdr (ly:stencil-extent stil Y)))
  (ly:stencil-extent stil Y)
  )))

startTempoSpan =
#(define-event-function
  (left-text)
  (markup?)
  #{
\tweak bound-details.left.text \markup {
  \combine \transparent "Tj"
  #left-text
}
\tweak font-shape #'upright
\tweak font-size 1
\tweak font-series #'bold
\startTextSpan
  #})
stopTempoSpan = \stopTextSpan

{
  R1 |
  \tempo \markup { \baseline-align \large "a" }
  R1 |
  \tempo \markup { \baseline-align \large "p" }
  R1 |
  <>\startTempoSpan "a"
  R1
  <>\stopTempoSpan |
  R1 |
  <>\startTempoSpan "p"
  R1
  <>\stopTempoSpan |
  R1
  \tempo \markup { \large \combine \transparent "Tj" "a" }
  R1 |
  \tempo \markup { \large \combine \transparent "Tj" "p" }
  R1 |
}

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

Re: GrandStaff vertical distance

[Thomas Morley]

Hi Lukas-Fabian,

Am So., 14. Okt. 2018 um 15:07 Uhr schrieb Lukas-Fabian Moser :

> Though, the whole thread mixes up different topics.
>
> I'm not sure, tbh. Of course, setting delimiters and setting spacing should 
> be thought of as mostly orthogonal aspects of setting up a score. The 
> problem, I think, arises because (I think) it's tempting to think that the 
> only way to get a braced sub-group of a StaffGroup is by nesting a new 
> GrandStaff (or PianoStaff), which is bad since this also affects spacing.

I would have said the affected spacing is because of different
spacing-values for each context.
Thus I've set up some test-code:

(1) Below reads and displays some spacing values from the StaffGrouper
in terminal

staffGrouperInfo =
\override StaffGrouper.after-line-breaking =
#(lambda (grob)
  (pretty-print
   (list
(cons 'staff-staff-spacing
  (ly:grob-property grob 'staff-staff-spacing))
(cons 'staffgroup-staff-spacing
  (ly:grob-property grob 'staff-staff-spacing)

mus = { c''1 }

\score {
  \new StaffGroup
<<
  \new Staff \mus
  \new GrandStaff
<<
  \new Staff \mus
  \new Staff \mus
>>
  \new Staff \mus
>>
  \layout {
\context {
  \StaffGroup
  \staffGrouperInfo
  }
\context {
  \GrandStaff
  \staffGrouperInfo
  }
  }
}

You'll get:
((staff-staff-spacing
   (basic-distance . 9)
   (minimum-distance . 7)
   (padding . 1)
   (stretchability . 5))
 (staffgroup-staff-spacing
   (basic-distance . 9)
   (minimum-distance . 7)
   (padding . 1)
   (stretchability . 5)))
((staff-staff-spacing
   (basic-distance . 9)
   (minimum-distance . 7)
   (padding . 1)
   (stretchability . 5))
 (staffgroup-staff-spacing
   (basic-distance . 9)
   (minimum-distance . 7)
   (padding . 1)
   (stretchability . 5)))

Four times the same numerical values, so far ok, I think.

(2) But using exactly those values like:

mus = { c''1 }

\score {
  \new StaffGroup
<<
  \new Staff \mus
  \new GrandStaff
<<
  \new Staff \mus
  \new Staff \mus
>>
  \new Staff \mus
>>
  \layout {
\context {
  \StaffGroup
  \override SystemStartBracket.color = #cyan

  \override StaffGrouper.staff-staff-spacing =
#'((basic-distance . 9)
   (minimum-distance . 7)
   (padding . 1)
   (stretchability . 5))
  \override StaffGrouper.staffgroup-staff-spacing =
#'((basic-distance . 9)
   (minimum-distance . 7)
   (padding . 1)
   (stretchability . 5))
  }

\context {
  \GrandStaff

  \override SystemStartBrace.color = #red

  \override StaffGrouper.staff-staff-spacing =
#'((basic-distance . 9)
   (minimum-distance . 7)
   (padding . 1)
   (stretchability . 5))

  \override StaffGrouper.staffgroup-staff-spacing =
#'((basic-distance . 9)
   (minimum-distance . 7)
   (padding . 1)
   (stretchability . 5))
  }
  }
}

returns a different image. See attached.
Did I fail to understand something, coded wrongly, or is this fishy??

>
> Hence my claim that foxfanfare's second approach using the 
> systemStartDelimiterHierarchy is the conceptual and right one - change only 
> what you want to change.

Iiuc, this means to refuse any usage of container-contexts, setting
systemStartDelimiterHierarchy always manually.
With the consequence of loosing the possibility to use the
StaffGrouper-properties at all, need to care about SpanBar and the
Keep_alive_together_engraver. To mention the first three things which
came to my mind.

>
> %%%
> (2) Changing the systemStartDelimiterHierarchy
> %%%
>
> As already mentioned in this the user-interface for
> systemStartDelimiterHierarchy is terrible. It always gives me a
> headache when I need to use it.
> So improvements in this regard would be highly welcome, imho.
> Maybe Lukas-Fabian's code is a step in this direction. So far I have
> not taken a closer look, though.
>
> Probably not, I'm far from convinced of the quality of my code 
> ("Montagsprogrammer", as one could say in German).

And I'm not a progammer at all ;)
I'm a musician.

> For me, there are the following issues with the systemStartDelimiterHierarchy 
> design:
[...]
> What do you think?

I need a break. Will look into it later.

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

Re: Markup and Score from scheme function

[Thomas Morley]

Am So., 14. Okt. 2018 um 12:57 Uhr schrieb Sebastian Käppler
:
>
> Finally, I found that the given answers satisfy all my needs as of now. Thank 
> you very much!

Glad you like it.

>
> Sebastian Käppler  schrieb am Sa., 13. Okt. 
> 2018, 09:26:
>>
>> Add-text is even better.

Well, 'add-text' is shorter. It's defined as (add-score (list text)), though.

>> Still curious if it's possible to get the "context" inside the function.

No.
Furthermore, my function is void-function, i.e. it _returns_ nothing!
Ofcourse it _does_ something. In this case text and score are added to
the current bookpart, book or toplevel

>> Isn't that what the location parameter is for?

Nope, it makes point-and-click work.
it's meant to point to a location in your input file. But you can
watch what it does.
See:
\version "2.19.82"

foo = #(define-void-function ()() (write (*location*)))

{ R1 \foo R1 }

In my case it display in terminal:
#
i.e. a certain line and column

Cheers,
  Harm

>> Thomas Morley  schrieb am Fr., 12. Okt. 2018, 
>> 10:29:
>>>
>>> Am Fr., 12. Okt. 2018 um 08:10 Uhr schrieb Jan-Peter Voigt 
>>> :
>>> >
>>> > Hello Sebastian,
>>> >
>>> > what do you mean with "return"? Do want to add the score immediatly or
>>> > do you want to return an object containing both?
>>> > You used the parser-location arguments in your scheme-function, so I
>>> > guess you are using stable (2.18). I created an example for 2.18
>>> > (incomplete) and one for 2.19.82. For three possible functions.
>>> >
>>> > HTH
>>> > Jan-Peter
>>>
>>> Hi,
>>>
>>> for immediate addings, why not the simpler:
>>>
>>> example =
>>> #(define-void-function (mrkp scr) (markup? ly:score?)
>>>   (add-text mrkp)
>>>   (add-score scr))
>>>
>>> \example
>>>  \markup \bold "Test"
>>>  \score { c'4 }
>>>
>>> \example
>>>  \markup \italic "Test"
>>>  \score { cis'4 }
>>>
>>> Cheers,
>>>   Harm
>>>
>>> ___
>>> 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: GrandStaff vertical distance

[Lukas-Fabian Moser]

Hi Harm,

thanks for your help in tidying up ;-).


Though, the whole thread mixes up different topics.
I'm not sure, tbh. Of course, setting delimiters and setting spacing 
should be thought of as mostly orthogonal aspects of setting up a score. 
The problem, I think, arises because (I think) it's tempting to think 
that the only way to get a braced sub-group of a StaffGroup is by 
nesting a new GrandStaff (or PianoStaff), which is bad since this also 
affects spacing.


Hence my claim that foxfanfare's second approach using the 
systemStartDelimiterHierarchy is the conceptual and right one - change 
only what you want to change.



%%%
(2) Changing the systemStartDelimiterHierarchy
%%%

As already mentioned in this the user-interface for
systemStartDelimiterHierarchy is terrible. It always gives me a
headache when I need to use it.
So improvements in this regard would be highly welcome, imho.
Maybe Lukas-Fabian's code is a step in this direction. So far I have
not taken a closer look, though.
Probably not, I'm far from convinced of the quality of my code 
("Montagsprogrammer", as one could say in German).


For me, there are the following issues with the 
systemStartDelimiterHierarchy design:


1) There's an overlap between systemStartDelimiter and 
systemStartDelimiterHierarchy, namely

systemStartDelimiterHierarchy = #'(SystemStartBrace)
is equivalent to (and in fact overrides, if there's a conflict)
systemStartDelimiter = #'SystemStartBrace
Might be ugly, might be convenient. Not sure.

2) The docs state that systemStartDelimiterHierarchy
"... takes an alphabetical list of the number of staves produced. Before 
each staff a system start delimiter can be given. It has to be enclosed 
in brackets and takes as much staves as the brackets enclose. Elements 
in the list can be omitted, but the first bracket takes always the 
complete number of staves. The possibilities are |SystemStartBar|, 
|SystemStartBracket|, |SystemStartBrace|, and |SystemStartSquare|."
First, this seems to be plain wrong ("brackets" instead of 
"parentheses"). Second, I have no idea what an "alphabetical list" is 
supposed to be. The example given in the docs uses a,b,c,d as 
placeholders for the staves, but in fact, any symbol (not equal to 
SystemStartBar etc.) may be used; they even may be identical. I use this 
heavily in my code (but tbh I did not look at the implementation of the 
systemStartDelimiterHierarchy interface).


3) systemStartDelimiterHierarchy allows for heavy nesting:

\new StaffGroup \with {
  systemStartDelimiterHierarchy = #'((a (a (SystemStartBrace a) a) a))
}
<<
  \new Staff a
  \new Staff a
  \new Staff a
  \new Staff a
  \new Staff a
  \new Staff a
  \new Staff a
  \new Staff a
>>

While this is neat (and I think the syntax is in fact quite well suited 
for constructions of this kind), I would assume that it is almost never 
used. Of course it should stay being supported, but I would expect 99% 
of all use cases comprise of <= 2 layers of nesting, most commonly one 
or several top-level Brackets with some sub-Braces/Squares.
The code I gave is tailored for a subset of this use-case, namely that 
in which there is only one top-lavel Bracket/Square/Bar... comprising 
the whole StaffGroup (and arbitrarily many first-order subgroups). If 
you want several disjunct top-level Brackets and still use my function, 
you have to create several StaffGroups - and hence you affect spacing. 
For the use cases I have in mind, this is fine, but maybe I'm wrong. Of 
course this might be changed.



So, basically I think we should
- keep systemStartDelimiterHierarchy as it is
- improve the docs for this (I could try and come up with an improved 
explanation)
- provide a simple function (like the \setDelimiters I proposed) that 
allows for easier setting of delimiters in the common use-case of <= 2 
nesting levels.


What do you think?

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

Re: GrandStaff vertical distance

[Thomas Morley]

Am Sa., 13. Okt. 2018 um 11:56 Uhr schrieb foxfanfare :
>
> Lukas-Fabian Moser wrote
> > I disagree that LP does not follow the standard engraving rules. It just
> > seems to me that \new GrandStaff etc. imply a certain semantics which is
> > perfectly alright for, e.g., an orchestral Piano part, but just does not
> > apply for the braces connecting Violin 1 and 2. - I do not own Gould's
> > book, but I would expect that this is discussed there.
>
> I have her book. About the curly braces, she says: "The curly bracket, also
> called a brace, connects the staves of instruments that use two staves: most
> commonly keyboard and harp. [...] The brace may connect two or more staves
> of like instruments (or like voices), but this is a traditional style now
> rarely used in orchestral music: it is more effective visually - and
> space-saving - to reserve it for joining the staves of a single instrument"
>
> The brace used for a single instrument should be written with PianoStaff. I
> see absolutely no reason of using the GrandStaff for that purpose! Or could
> someone explain me why two functions would do exactly the same thing?
>
> The GrandStaff connector should be reserved as a secondary demarcation (it
> is by the way how it is presented in the documentation and examples!) and
> that is why I think the default behaviour is wrong in this case (or the
> documentation misleading).
>
> I think it is the same with "square bracket" which should only apply to
> secondary demarcation. In the documentation
> (http://lilypond.org/doc/v2.19/Documentation/notation/displaying-staves#nested-staff-groups),
> the "square bracket" is used in the second example as a primary demarcation.
> I looked in different scores and cannot find this kind kind of use anywhere!
>
> I may be wrong, but in my opinion, that is what I would expect for the
> default behaviour of staff grouping:
> - PianoStaff for a single instrument, with a centered instrument name label
> (if needed, a staff label could be added). This group takes spaces on top
> and below itself.
> - StaffGroup for grouping different instruments in a same section with a
> main bracket. This group takes spaces on top and below itself.
> - GrandStaff (or something else) for secondary grouping. Like the function
> you have produced and which allow the user to choose whatever he wants as a
> secundary demaraction, but without adding any spaces.


Hi all,

sorry, I'm late to the party.

Though, the whole thread mixes up different topics.

%%%
(1) Setting of systemStartDelimiter in container-context
%%%

Which SytemStartGrob (SytemStartBrace, SystemStartBracket,
SystemStartSquare, SystemStartBar) is taken for container-contexts
like ChoirStaff, PianoStaff, GrandStaff, StaffGroup (did I miss one?)
will be determined which value the context-property
systemStartDelimiter takes.

Which SystemStartGrob is actually taken has no influence on spacing
(without doing other things as well).
Look at the example below demonstrating things with ChoirStaff.
You can switch to whatever SystemStartGrob, spacing will not change.
Comment my spacing-settings, which I only inserted to make things more
obvious, you'll observe a wider spacing ofcourse but no changes for
different SystemStartGrobs.

\score {
  <<
\new ChoirStaff
<<
  \new Staff R1
  \new Staff R1
>>
\new ChoirStaff
<<
  \new Staff R1
  \new Staff R1
>>
  >>
  \layout {
\context {
  \ChoirStaff
  systemStartDelimiter =
#'SystemStartBracket %% the default for ChoirStaff
%#'SystemStartBrace
%#'SystemStartSquare
%#'SystemStartBar
  \override StaffGrouper.staff-staff-spacing =
#'((basic-distance . 0)
   (minimum-distance . 0)
   (padding . 0)
   (stretchability . 0))
  \override StaffGrouper.staffgroup-staff-spacing =
#'((basic-distance . 0)
   (minimum-distance . 0)
   (padding . 0)
   (stretchability . 0))
}
  }
}

%%%
(2) Changing the systemStartDelimiterHierarchy
%%%

As already mentioned in this the user-interface for
systemStartDelimiterHierarchy is terrible. It always gives me a
headache when I need to use it.
So improvements in this regard would be highly welcome, imho.
Maybe Lukas-Fabian's code is a step in this direction. So far I have
not taken a closer look, though.
Nevertheless, adjusting systemStartDelimiterHierarchy has no impact on
spacing, without doing other things as well.

%%%
(3) Spacings
%%%

If you want to adjust spacing, then tackle spacing nothing else ;)

First look up the defaults. From IR:

StaffGrouper-defaults:

 staff-staff-spacing (list):
'((basic-distance . 9)
  (minimum-distance . 7)
  (padding . 1)
  (stretchability . 5))

 staffgroup-staff-spacing 

Re: Markup and Score from scheme function

[Sebastian Käppler]

Finally, I found that the given answers satisfy all my needs as of now.
Thank you very much!

Sebastian Käppler  schrieb am Sa., 13. Okt.
2018, 09:26:

> Add-text is even better. Still curious if it's possible to get the
> "context" inside the function. Isn't that what the location parameter is
> for?
>
> Thomas Morley  schrieb am Fr., 12. Okt. 2018,
> 10:29:
>
>> Am Fr., 12. Okt. 2018 um 08:10 Uhr schrieb Jan-Peter Voigt <
>> jp.vo...@gmx.de>:
>> >
>> > Hello Sebastian,
>> >
>> > what do you mean with "return"? Do want to add the score immediatly or
>> > do you want to return an object containing both?
>> > You used the parser-location arguments in your scheme-function, so I
>> > guess you are using stable (2.18). I created an example for 2.18
>> > (incomplete) and one for 2.19.82. For three possible functions.
>> >
>> > HTH
>> > Jan-Peter
>>
>> Hi,
>>
>> for immediate addings, why not the simpler:
>>
>> example =
>> #(define-void-function (mrkp scr) (markup? ly:score?)
>>   (add-text mrkp)
>>   (add-score scr))
>>
>> \example
>>  \markup \bold "Test"
>>  \score { c'4 }
>>
>> \example
>>  \markup \italic "Test"
>>  \score { cis'4 }
>>
>> Cheers,
>>   Harm
>>
>> ___
>> 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: textSpanner at arbitrary positions independent of music

[Ryan Michael]

THank you Pierre,
exactly what i was looking for. However, how can i turn off the left
textSpan property if i want to span four bars which is broken over two
systems, and i don't wish to repeat the "molto rit" for the left attribute
of the span in the second system?

On Sun, Oct 14, 2018 at 1:34 AM Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:

> Hi Ryan,
> Your example does not compile.
> How about putting the text into the sapnner ?
> Cf.
> http://lilypond.org/doc/v2.18/Documentation/notation/writing-text.html#text-spanners
> Cheers,
> Pierre
>
> Le dim. 14 oct. 2018 à 09:38, Ryan Michael  a
> écrit :
>
>> Hi all
>>
>> So i have a scenario where I want a textSpanner to follow a heading i
>> have
>> over the treble clef of a system where there is only action in the left
>> hand (Bass clef). e.g.
>>
>> %
>> \version "2.18.2"
>> up = \new Staff = "up" {
>> r1/^\markup{\huge "molto rit."}  r1\startTextSpanner r1 r1\stopTextSpanner
>> }
>>
>> down = \new Staff = "down" {
>> c,,4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4
>> }
>> {
>>   \new PianoStaff <<
>>  \up
>>\down
>>   >>
>> }
>> 
>>
>> my issues is that i want the spanner to really start immediately after
>> the markup. do i have to make some fake notes in the right hand to anchor
>> the spanner or can i just move it around by other means?
>>
>> best,
>> ryan.
>> --
>> ॐ नमः शिवाय
>> ___
>> 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: textSpanner at arbitrary positions independent of music

[Pierre Perol-Schneider]

Hi Ryan,
Your example does not compile.
How about putting the text into the sapnner ?
Cf.
http://lilypond.org/doc/v2.18/Documentation/notation/writing-text.html#text-spanners
Cheers,
Pierre

Le dim. 14 oct. 2018 à 09:38, Ryan Michael  a
écrit :

> Hi all
>
> So i have a scenario where I want a textSpanner to follow a heading i have
> over the treble clef of a system where there is only action in the left
> hand (Bass clef). e.g.
>
> %
> \version "2.18.2"
> up = \new Staff = "up" {
> r1/^\markup{\huge "molto rit."}  r1\startTextSpanner r1 r1\stopTextSpanner
> }
>
> down = \new Staff = "down" {
> c,,4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4
> }
> {
>   \new PianoStaff <<
>  \up
>\down
>   >>
> }
> 
>
> my issues is that i want the spanner to really start immediately after the
> markup. do i have to make some fake notes in the right hand to anchor the
> spanner or can i just move it around by other means?
>
> best,
> ryan.
> --
> ॐ नमः शिवाय
> ___
> 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: Edition Engraver suppress log files

[Urs Liska]

Am 14. Oktober 2018 09:29:44 MESZ schrieb Craig Dabelstein 
:
>Thanks Jan-Peter. Urs, same question for Scholarly -- can I turn off
>the
>log files?

IIRC scholarLY doesn't write log files, only oll-core. I'll look into it after 
the weekend.
Thinking of it I would even make the default *not* to write the log.

Urs

>
>All the best,
>
>Craig
>
>
>On Sun, 14 Oct 2018 at 16:32, Urs Liska  wrote:
>
>>
>>
>> Am 14. Oktober 2018 08:29:46 MESZ schrieb Jan-Peter Voigt
>> >:
>> >Hi Craig,
>> >
>> >not right now, but I will implement a switch ASAP!
>> >
>>
>> Please use the \setOption syntax for that.
>>
>> >Jan-Peter
>> >
>> >Am 14. Oktober 2018 07:30:44 MESZ schrieb Craig Dabelstein
>> >:
>> >>Hi all,
>> >>
>> >>Quick question: Is it possible to stop the edition-engraver
>creating
>> >>log
>> >>files?
>> >>
>> >>Craig
>> >>
>> >>
>> >>--
>> >>*Craig Dabelstein*
>> >>Maxime's Music
>> >>craig.dabelst...@gmail.com
>> >>*http://maximesmusic.com *
>>

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

textSpanner at arbitrary positions independent of music

[Ryan Michael]

Hi all

So i have a scenario where I want a textSpanner to follow a heading i have
over the treble clef of a system where there is only action in the left
hand (Bass clef). e.g.

%
\version "2.18.2"
up = \new Staff = "up" {
r1/^\markup{\huge "molto rit."}  r1\startTextSpanner r1 r1\stopTextSpanner
}

down = \new Staff = "down" {
c,,4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4 c4
}
{
  \new PianoStaff <<
 \up
   \down
  >>
}


my issues is that i want the spanner to really start immediately after the
markup. do i have to make some fake notes in the right hand to anchor the
spanner or can i just move it around by other means?

best,
ryan.
-- 
ॐ नमः शिवाय
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Edition Engraver suppress log files

[Craig Dabelstein]

Thanks Jan-Peter. Urs, same question for Scholarly -- can I turn off the
log files?

All the best,

Craig


On Sun, 14 Oct 2018 at 16:32, Urs Liska  wrote:

>
>
> Am 14. Oktober 2018 08:29:46 MESZ schrieb Jan-Peter Voigt  >:
> >Hi Craig,
> >
> >not right now, but I will implement a switch ASAP!
> >
>
> Please use the \setOption syntax for that.
>
> >Jan-Peter
> >
> >Am 14. Oktober 2018 07:30:44 MESZ schrieb Craig Dabelstein
> >:
> >>Hi all,
> >>
> >>Quick question: Is it possible to stop the edition-engraver creating
> >>log
> >>files?
> >>
> >>Craig
> >>
> >>
> >>--
> >>*Craig Dabelstein*
> >>Maxime's Music
> >>craig.dabelst...@gmail.com
> >>*http://maximesmusic.com *
>


-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Edition Engraver suppress log files

[Urs Liska]

Am 14. Oktober 2018 08:29:46 MESZ schrieb Jan-Peter Voigt :
>Hi Craig,
>
>not right now, but I will implement a switch ASAP!
>

Please use the \setOption syntax for that.

>Jan-Peter
>
>Am 14. Oktober 2018 07:30:44 MESZ schrieb Craig Dabelstein
>:
>>Hi all,
>>
>>Quick question: Is it possible to stop the edition-engraver creating
>>log
>>files?
>>
>>Craig
>>
>>
>>-- 
>>*Craig Dabelstein*
>>Maxime's Music
>>craig.dabelst...@gmail.com
>>*http://maximesmusic.com *

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

Re: Edition Engraver suppress log files

[Jan-Peter Voigt]

Hi Craig,

not right now, but I will implement a switch ASAP!

Jan-Peter

Am 14. Oktober 2018 07:30:44 MESZ schrieb Craig Dabelstein 
:
>Hi all,
>
>Quick question: Is it possible to stop the edition-engraver creating
>log
>files?
>
>Craig
>
>
>-- 
>*Craig Dabelstein*
>Maxime's Music
>craig.dabelst...@gmail.com
>*http://maximesmusic.com *

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user