Re: Wanting to parenthesize (b5) superscript

[John Helly]

It certainly does. Mahalo nui.
J.

On 3/19/24 19:26, Aaron Hill wrote:

On 2024-03-19 10:13 pm, John Helly wrote:

Aloha.

I'm trying to improve a score that my colleagues find confusing since 
they mis-interpret A(b5) as Ab5; that is, when cis1:5- is transposed 
to A(b5).


The transpose (cis to a) is not applied in the example below and that 
may further complicate things as I'm not sure whether parentheses 
could/should be added before the transpose or after. So, this may 
actually be two problems.


So I'm seeking a way to put parentheses around the (b5) superscript.  
I found this related snippet in the docs but can't seem to apply it 
usefully to this situation.


Suggestions would be much appreciated.



Does this help?


\version "2.22.0"

% Exception music is chords with markups.
% Specifically, chords rooted on C.
chExceptionMusic = {
  1-\markup \super { ( \flat 5 ) }
}

% Convert music to list and prepend to existing exceptions.
chExceptions = #(append
  (sequential-music-to-chord-exceptions chExceptionMusic #t)
  ignatzekExceptions)

theMusic = \chordmode {
  \set chordNameExceptions = #chExceptions
  cis1:5-
  des1:5-
}

\layout {
  ragged-right = ##t
}

\new ChordNames { \theMusic }



-- Aaron Hill


--
John Helly / San Diego Supercomputer Center / Scripps Institution of 
Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660

Re: Wanting to parenthesize (b5) superscript

[Aaron Hill]

On 2024-03-19 10:13 pm, John Helly wrote:

Aloha.

I'm trying to improve a score that my colleagues find confusing since 
they mis-interpret A(b5) as Ab5; that is, when cis1:5- is transposed to 
A(b5).


The transpose (cis to a) is not applied in the example below and that 
may further complicate things as I'm not sure whether parentheses 
could/should be added before the transpose or after. So, this may 
actually be two problems.


So I'm seeking a way to put parentheses around the (b5) superscript.  I 
found this related snippet in the docs but can't seem to apply it 
usefully to this situation.


Suggestions would be much appreciated.



Does this help?


\version "2.22.0"

% Exception music is chords with markups.
% Specifically, chords rooted on C.
chExceptionMusic = {
  1-\markup \super { ( \flat 5 ) }
}

% Convert music to list and prepend to existing exceptions.
chExceptions = #(append
  (sequential-music-to-chord-exceptions chExceptionMusic #t)
  ignatzekExceptions)

theMusic = \chordmode {
  \set chordNameExceptions = #chExceptions
  cis1:5-
  des1:5-
}

\layout {
  ragged-right = ##t
}

\new ChordNames { \theMusic }



-- Aaron Hill

Wanting to parenthesize (b5) superscript

[John Helly]

Aloha.

I'm trying to improve a score that my colleagues find confusing since 
they mis-interpret A(b5) as Ab5; that is, when cis1:5- is transposed to 
A(b5).


The transpose (cis to a) is not applied in the example below and that 
may further complicate things as I'm not sure whether parentheses 
could/should be added before the transpose or after. So, this may 
actually be two problems.


So I'm seeking a way to put parentheses around the (b5) superscript.  I 
found this related snippet in the docs but can't seem to apply it 
usefully to this situation.


Suggestions would be much appreciated.

= MWE Below ===
\version "2.24.2"

% modify maj9 and 6(add9)
% Exception music is chords with markups
chExceptionMusic = {
   1-\markup { \super "maj9" }
  1-\markup { \super "6(add9)" }
  1-\markup { \super "(-)" }
}

% Convert music to list and prepend to existing exceptions.
chExceptions = #(append
  (sequential-music-to-chord-exceptions chExceptionMusic #t)
  ignatzekExceptions)

theMusic = \chordmode {
  g1:maj9 g1:6.9
  \set chordNameExceptions = #chExceptions
  g1:maj9 g1:6.9
  cis1:5-
}

\layout {
  ragged-right = ##t
}

<<
= MWE Above ===
--
John Helly / San Diego Supercomputer Center / Scripps Institution of 
Oceanography

https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660

Troubles with StaffGrouper

[Ben Bradshaw]

Hello,
I think I must not be understanding how the StaffGrouper works. I'm doing a
score with instrument and piano accompaniment, and have the piano music in
a PianoStaff. I'm trying to get more space between the solo staff and the
piano staff. This is what I tried...

\layout{
\context {
\Score
\override VerticalAxisGroup.staff-staff-spacing.minimum-distance = #14
\override StaffGrouper.staff-staff-spacing.minimum-distance = #6
}

But it seems the StaffGrouper spacing isn't applied, and what I get is big
space between all three lines. I thought that the StaffGrouper was supposed
to override settings in the VerticalAxisGroup, but maybe I have to do it a
different way? Any help would be greatly appreciated.

Thanks,
Ben

Re: New package implementing support for The Helmholtz-Ellis Just Intonation (HEJI) pitch notation system

[Gregory Evans]

Hi masterbuilder/Gylfi,
This looks like a cool package. Designing the user interface, I think,
really is a matter of taste. My abjad-ext-microtones is meant specifically
to work with the abjad API, so I only implemented a set of accidental
overrides. I also thought it was important to design the stylesheets so
that a different font could be swapped out if desired. The real goal of the
python aspect of my program was to allow tones to be composed numerically
(i.e. as transpositions above a fundamental) so if you had the ability to
model something like \ji-multiplication c' 7/4 (which would result in a
septimally lowered bf') that would be my preferred interface. I’m certain
the two interface systems could even collaborate with one another.
Unfortunately I personally don’t know how to do this in scheme, thus: my
python system. Conveniently, I already compose mainly with python so I am
not in desperate need of the interface I just described. However, I think
the true ratio-based system is what a lot of composers want from JI. And a
software system is great for automatically calculating transpositions.

again: the project is very nice.

warm regards,
gregory rowland evans

On Tue, Mar 19, 2024 at 11:30 AM Gylfi  wrote:

> Greetings everyone,
>
> I want to share with the community some work I've been doing on
> implementing proper support for the HEJI notation system in LilyPond. I
> wouldn't call it stable quite yet, as I'm still open to making breaking
> changes to the interface based on feedback. However, I would say it has
> (hopefully) reached the point where it is usable in real projects. You can
> find the repository here:
>
> https://github.com/BridgeTheMasterBuilder/heji-ly
>
> (let me know if you are opposed to using GitHub, I can also host it
> somewhere else)
>
> The differences between this package and existing packages that also
> implement HEJI support (I am personally only aware of two:
> https://github.com/levinericzimmermann/ekme-heji.ily and
> https://github.com/GregoryREvans/abjad-ext-microtones) are the following:
>
>- Complete support for all accidentals, with the exception of
>"enharmonic schismas" and equal-tempered accidentals which are planned for
>future releases.
>- Modular interface for arbitrary combinations of accidentals (this is
>perhaps what I'm most interested in getting feedback on - to me it's a
>reasonable interface but I don't know what other people's opinion will be)
>- Full playback support, even for chords, which I believe is just
>about as accurate as MIDI will allow. Sounds pretty good to my ears in any
>case.
>
> I've included some example scores in the repository, including: Recreating
> the otonal and utonal harmonic series examples found here
> https://marsbat.space/pdfs/HEJI2_legend+series.pdf; some other examples
> related to the harmonic series; a classic Ben Johnston chord from the song
> Quietness; a Barbershop quartet arrangment of Kentucky Babe notated with
> the exact harmonies that could plausibly appear in a performance (but still
> highly theoretical and pure, it's not a transcription of any real
> performance) and a traditional bagpipe tune Sweet Maid of Glendaruel. These
> last two examples are a bit out there as far as using HEJI notation is
> concerned. I only chose them because they are "natural" examples of 7-limit
> just intonation that happen to be public domain (if anybody knows of any
> other examples of public domain music in extended just intonation please
> let me know).
>
> Before starting this project I had virtually no exposure to the Scheme API
> (though I've been a semi-casual LilyPond user for a long time), so I might
> be doing some things inefficiently or violating some best practices, let me
> know if you see something particularly egregious. There are some hacks in
> there that I want to properly address at some point, they should be marked
> with TODO.
>
> I hope this will be useful to others.
>
> Best regards,
> masterbuilder
>


-- 
gregory rowland evans
http://www.gregoryrowlandevans.com
https://github.com/GregoryREvans
https://soundcloud.com/gregory-rowland-evans

Re: Footer text from header

[Aaron Hill]

On 2024-03-19 1:50 pm, Johannes Roeßler wrote:

thx again Aaron,

I tried it with
%%%
 \line  {\fromproperty #'header:composer " - "  \as-string 
\fromproperty #'header:title }

%%%
- then the title (in the footnote) was empty.

But you gave so many valuable insights, that I'll use it to make it in 
a better way - very instructive,

thank you very much!



Aha!  \as-string (as I defined it) is not going to work with 
\fromproperty.  The problem is that \fromproperty needs to be 
interpretted to get its contents.  \as-string is processing too soon, so 
it will not work.  Also, once markup is interpretted, it becomes a 
stencil.  And that is basically useless for our purposes.


One solution would be to customize \fromproperty itself:


\version "2.22.0"

%% Based on code from define-markup-commands.scm:
#(define-markup-command
  (frompropertystring layout props symbol) (symbol?)
  (let ((m (chain-assoc-get symbol props)))
(if (markup? m)
(interpret-markup
  layout
  (cons (list (cons symbol `(,property-recursive-markup 
,symbol))) props)

  (markup->string m))
empty-stencil)))

\header {
  asdf = \markup \with-color #red \bold \line { "Hello," "World!" }

  title = \markup \fromproperty #'header:asdf
  subtitle = \markup \frompropertystring #'header:asdf
}

\score { { b'1 } }


Again, this is probably not the best approach.  For instance, a nested 
\fromproperty within a field is going to fail much the same way.  So, 
then we are looking at redefining \fromproperty itself to be able to 
call markup->string as needed.  Doable, but it really starts to feel 
like a clunky hack.


I think the best approach is to avoid putting markup around data that 
needs to be accessed in different ways.  Keep the fields as simple text, 
so there is no need for an \as-string or \frompropertystring command.



-- Aaron Hill

Re: Tremolo with staccato

[Ralph Palmer]

On Tue, Mar 19, 2024 at 12:18 PM Xavier Scheuer  wrote:
>
> On Tue, 19 Mar 2024 at 16:08, Ralph Palmer  wrote:
> >
> > Hello, again!
> >
> > This list has been a great help on numerous occasions.
> >
> > I have a new problem - how to combine staccato with tremolo. I'm
> > attaching an example from the score I'm trying to transcribe. The
> > problem is similar to
> >
> > Adding double and triple tonguing indications for woodwind
> >
> > from the LSR, but without the "tuplet number". I don't know how to
> > adjust the code.
>
> Hello,
>
> You could adapt the "jeté" from this thread:
> https://lists.gnu.org/archive/html/lilypond-user/2023-01/msg00452.html
>
> The trem-mod.ly file from Valentin is impressive as well, but maybe a little 
> bit overkill for this case.
> https://lists.gnu.org/archive/html/lilypond-user/2023-01/msg00461.html
>
> Kind regards,
> Xavier

Thanks, Xavier! Works very nicely. The "articulation" could be closer
to the note, but it is completely understandable.

All the best,

Ralph
__
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com

Re: Footer text from header

[Johannes Roeßler]

thx again Aaron,

I tried it with
%%%
 \line  {\fromproperty #'header:composer " - "  \as-string 
\fromproperty #'header:title }

%%%
- then the title (in the footnote) was empty.

But you gave so many valuable insights, that I'll use it to make it in a 
better way - very instructive,

thank you very much!

Best
Joei


On 2024-03-19 11:15 am, Johannes Roeßler wrote:
And I aim to separate content from style - but in order to have the 
right (and changing) footer text for each piece in a book 
environment, I need to get this information from the header and can't 
define it in the common \paper env - or do I miss something?


You should be able to define oddFooterMarkup in a suitably generic 
manner.  All of the related markup paper variables are intended to 
work this way, so anything specific to a score lives in a \header block.



And defining and adding your idea with the \as-string command seems 
not to work:


The idea is that \as-string strips any commands for the markup you 
provide it.  But the usage you wrote is not what was intended. 
\as-string would be used just before the \fromproperty commands. 
Something closer to this:



  oddFooterMarkup = \markup {
    \fill-line {
  \tiny {
   { "Edited by Joei" }
   \line {
 \as-string \fromproperty #'header:composer " - "
 \as-string \fromproperty #'header:title
   }
   "Copyright 2024"
  }
    }
  }


NOTE: You should probably be using \header fields for copyright and 
editor.


Here's a more complete example with the goal of keeping the \header 
blocks free of \markup commands:




\version "2.22.0"

\paper {
  bookTitleMarkup = \markup
    \override #'(baseline-skip . 1.75) \column {
  \fill-line {
    \override #'(font-name . "Lobster") \line {
  \fontsize #6 \fromproperty #'header:title
  \fontsize #3 \fromproperty #'header:subtitle
    }
    \bold \fromproperty #'header:composer
  }
  \override #'(thickness . 2) \draw-hline
    }

  oddFooterMarkup = \markup \tiny \fill-line {
    \line { Edited by \fromproperty #'header:editor }
    \line {
  \fromproperty #'header:composer
  – % en-dash
  \fromproperty #'header:title
    }
    \fromproperty #'header:copyright
  }
}

\header {
  editor = "Anon E. "
}

%% - - -

\header {
  title = "Lorem Ipsum"
  subtitle = "(dolor sit amet)"
  composer = \markup { "John Doe" \smallCaps (asdf) }
  copyright = "© 2024 John Doe Music"
}

\score { { b'1 } }



In this case, the composer's affiliation with the fictitious ASDF 
group is written in small caps.  This markup command belongs in the 
\header block as we would ideally want it included anywhere that field 
is referenced.  Now, that is only one way to achieve things, as we 
could have just as easily defined a new header field instead:



\header {
  title = "Lorem Ipsum"
  subtitle = "(dolor sit amet)"
  composer = "John Doe"
  affiliation = "ASDF"
  copyright = "© 2024 John Doe Music"
}


Of course, the \paper block would need to be updated to support this 
new field.  (I'll leave that as an exercise for the reader.)


It will be up to you to determine where you are going to strike the 
balance between markup in the \paper block versus the \header block.  
As in the example above, I think that it is perfectly fine to mix a 
little bit of useful formatting in the metadata, especially if such a 
thing is going to be relatively rare across the majority of your 
scores.  Otherwise, anything that is shared should ideally be defined 
once, in some globally-referenced resource.


It can be a little tricky to plan out how to build your \paper markup 
variables, so that they function well when fields are defined or left 
undefined.  In the example I provided, the subtitle can be safely 
omitted.  However, note that I opted to put the parentheses within the 
subtitle field itself.  Had I put them in the \paper block, then you'd 
find an empty set of parens next to any title that did not also 
include a subtitle; not really what you'd want.  So, either one would 
need some clever custom \markup commands to automatically do the work, 
or we just "cheat" and put the parens in the header field.  Again, it 
comes back to that balancing act.


(The careful reader should observe that due to how the footer was 
defined, editor is effectively not an optional field.  The text 
"Edited by" will still appear even when the editor field is 
undefined.  I would encourage you to consider how you could improve 
this, assuming such flexibility is necessary.  The advanced exercise 
involves showing "Edited by" only when the editor field is defined 
without moving such text to the field itself.  Of course, consider 
your own real-world scenario.  Are you the editor for all of your 
scores?  If so, there may be no need to add complexity where it is 
otherwise wasted effort.)



-- Aaron Hill




--
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft.
www.avast.com

Re: Footer text from header

[Aaron Hill]

On 2024-03-19 11:15 am, Johannes Roeßler wrote:
And I aim to separate content from style - but in order to have the 
right (and changing) footer text for each piece in a book environment, 
I need to get this information from the header and can't define it in 
the common \paper env - or do I miss something?


You should be able to define oddFooterMarkup in a suitably generic 
manner.  All of the related markup paper variables are intended to work 
this way, so anything specific to a score lives in a \header block.



And defining and adding your idea with the \as-string command seems not 
to work:


The idea is that \as-string strips any commands for the markup you 
provide it.  But the usage you wrote is not what was intended.  
\as-string would be used just before the \fromproperty commands.  
Something closer to this:



  oddFooterMarkup = \markup {
    \fill-line {
  \tiny {
   { "Edited by Joei" }
   \line {
 \as-string \fromproperty #'header:composer " - "
 \as-string \fromproperty #'header:title
   }
   "Copyright 2024"
  }
    }
  }


NOTE: You should probably be using \header fields for copyright and 
editor.


Here's a more complete example with the goal of keeping the \header 
blocks free of \markup commands:




\version "2.22.0"

\paper {
  bookTitleMarkup = \markup
\override #'(baseline-skip . 1.75) \column {
  \fill-line {
\override #'(font-name . "Lobster") \line {
  \fontsize #6 \fromproperty #'header:title
  \fontsize #3 \fromproperty #'header:subtitle
}
\bold \fromproperty #'header:composer
  }
  \override #'(thickness . 2) \draw-hline
}

  oddFooterMarkup = \markup \tiny \fill-line {
\line { Edited by \fromproperty #'header:editor }
\line {
  \fromproperty #'header:composer
  – % en-dash
  \fromproperty #'header:title
}
\fromproperty #'header:copyright
  }
}

\header {
  editor = "Anon E. "
}

%% - - -

\header {
  title = "Lorem Ipsum"
  subtitle = "(dolor sit amet)"
  composer = \markup { "John Doe" \smallCaps (asdf) }
  copyright = "© 2024 John Doe Music"
}

\score { { b'1 } }



In this case, the composer's affiliation with the fictitious ASDF group 
is written in small caps.  This markup command belongs in the \header 
block as we would ideally want it included anywhere that field is 
referenced.  Now, that is only one way to achieve things, as we could 
have just as easily defined a new header field instead:



\header {
  title = "Lorem Ipsum"
  subtitle = "(dolor sit amet)"
  composer = "John Doe"
  affiliation = "ASDF"
  copyright = "© 2024 John Doe Music"
}


Of course, the \paper block would need to be updated to support this new 
field.  (I'll leave that as an exercise for the reader.)


It will be up to you to determine where you are going to strike the 
balance between markup in the \paper block versus the \header block.  As 
in the example above, I think that it is perfectly fine to mix a little 
bit of useful formatting in the metadata, especially if such a thing is 
going to be relatively rare across the majority of your scores.  
Otherwise, anything that is shared should ideally be defined once, in 
some globally-referenced resource.


It can be a little tricky to plan out how to build your \paper markup 
variables, so that they function well when fields are defined or left 
undefined.  In the example I provided, the subtitle can be safely 
omitted.  However, note that I opted to put the parentheses within the 
subtitle field itself.  Had I put them in the \paper block, then you'd 
find an empty set of parens next to any title that did not also include 
a subtitle; not really what you'd want.  So, either one would need some 
clever custom \markup commands to automatically do the work, or we just 
"cheat" and put the parens in the header field.  Again, it comes back to 
that balancing act.


(The careful reader should observe that due to how the footer was 
defined, editor is effectively not an optional field.  The text "Edited 
by" will still appear even when the editor field is undefined.  I would 
encourage you to consider how you could improve this, assuming such 
flexibility is necessary.  The advanced exercise involves showing 
"Edited by" only when the editor field is defined without moving such 
text to the field itself.  Of course, consider your own real-world 
scenario.  Are you the editor for all of your scores?  If so, there may 
be no need to add complexity where it is otherwise wasted effort.)



-- Aaron Hill

Re: Tremolo with staccato

[Xavier Scheuer]

On Tue, 19 Mar 2024 at 16:08, Ralph Palmer 
wrote:
>
> Hello, again!
>
> This list has been a great help on numerous occasions.
>
> I have a new problem - how to combine staccato with tremolo. I'm
> attaching an example from the score I'm trying to transcribe. The
> problem is similar to
>
> Adding double and triple tonguing indications for woodwind
>
> from the LSR, but without the "tuplet number". I don't know how to
> adjust the code.

Hello,

You could adapt the "jeté" from this thread:
https://lists.gnu.org/archive/html/lilypond-user/2023-01/msg00452.html

The trem-mod.ly file from Valentin is impressive as well, but maybe a
little bit overkill for this case.
https://lists.gnu.org/archive/html/lilypond-user/2023-01/msg00461.html

Kind regards,
Xavier

Re: Footer text from header

[Johannes Roeßler]

Hi Aaron,

thx for your input - I'm aware of separating those information in 
include files, just tried to make a minimal example :)


And I aim to separate content from style - but in order to have the 
right (and changing) footer text for each piece in a book environment, I 
need to get this information from the header and can't define it in the 
common \paper env - or do I miss something?


And defining and adding your idea with the \as-string command seems not 
to work:


-8<--
\version "2.24.0"

#(define-markup-command
  (as-string layout props arg) (markup?)
  (interpret-markup layout props (markup->string arg)))


{a4}

\header {

  title =
  \markup
  \fill-line {
    \override #'(font-name . "Calluna")
    \abs-fontsize #22 "Title"
    \null
  }

  composer = "Composer"

}

\paper {

  oddFooterMarkup = \markup \as-string {
    \fill-line {
  \tiny {
    {"Edited by Joei"}
    \line  {\fromproperty #'header:composer " - " \fromproperty 
#'header:title }

   "Copyright 2024"
  }
    }
  }
}
-8<--


Best regards
Joei




On 2024-03-19 9:35 am, Johannes Roeßler wrote:

Hi,

I'd like to make an automatic footer, using infos from the header block.

What do I have to change, to get rid of (or override) the format from 
the title?


-8<--

\version "2.24.0"

{a4}

\header {

  title =
  \markup
  \fill-line {
    \override #'(font-name . "Calluna")
    \abs-fontsize #22 "Title"
    \null
  }

  composer = "Composer"

}

\paper {

  oddFooterMarkup = \markup {
    \fill-line {
  \tiny {
    {"Edited by Joei"}
    \line  {\fromproperty #'header:composer " - " \fromproperty 
#'header:title }

   "Copyright 2024"
  }
    }
  }
}

-->8---


It should be possible to strip markup down to a simple string with the 
Scheme function markup->string.



\version "2.22.0"

foo = \markup \huge \bold "Hello"

#(define-markup-command
  (as-string layout props arg) (markup?)
  (interpret-markup layout props (markup->string arg)))

\markup \foo

\markup \as-string \foo


However, the best approach would be to separate content from styling.  
When you define things like title, specify only the simple string 
value.  Place all formatting/styling commands instead within the paper 
variables like bookTitleMarkup, scoreTitleMarkup, oddHeaderMarkup, etc.


Reference the file titling-init.ly within your LilyPond installation 
to see what the default values are for these markup paper variables.  
Copy-and-paste the default definitions and adjust to your needs.  
NOTE: These are the sort of things that are best put into include 
files, so you can reuse them and easily standardize your formatting 
across many scores.



-- Aaron Hill




--
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft.
www.avast.com

Re: Footer text from header

[Aaron Hill]

On 2024-03-19 9:35 am, Johannes Roeßler wrote:

Hi,

I'd like to make an automatic footer, using infos from the header 
block.


What do I have to change, to get rid of (or override) the format from 
the title?


-8<--

\version "2.24.0"

{a4}

\header {

  title =
  \markup
  \fill-line {
    \override #'(font-name . "Calluna")
    \abs-fontsize #22 "Title"
    \null
  }

  composer = "Composer"

}

\paper {

  oddFooterMarkup = \markup {
    \fill-line {
  \tiny {
    {"Edited by Joei"}
    \line  {\fromproperty #'header:composer " - " \fromproperty 
#'header:title }

   "Copyright 2024"
  }
    }
  }
}

-->8---


It should be possible to strip markup down to a simple string with the 
Scheme function markup->string.



\version "2.22.0"

foo = \markup \huge \bold "Hello"

#(define-markup-command
  (as-string layout props arg) (markup?)
  (interpret-markup layout props (markup->string arg)))

\markup \foo

\markup \as-string \foo


However, the best approach would be to separate content from styling.  
When you define things like title, specify only the simple string value. 
 Place all formatting/styling commands instead within the paper 
variables like bookTitleMarkup, scoreTitleMarkup, oddHeaderMarkup, etc.


Reference the file titling-init.ly within your LilyPond installation to 
see what the default values are for these markup paper variables.  
Copy-and-paste the default definitions and adjust to your needs.  NOTE: 
These are the sort of things that are best put into include files, so 
you can reuse them and easily standardize your formatting across many 
scores.



-- Aaron Hill

Footer text from header

[Johannes Roeßler]

Hi,

I'd like to make an automatic footer, using infos from the header block.

What do I have to change, to get rid of (or override) the format from 
the title?


-8<--

\version "2.24.0"

{a4}

\header {

  title =
  \markup
  \fill-line {
    \override #'(font-name . "Calluna")
    \abs-fontsize #22 "Title"
    \null
  }

  composer = "Composer"

}

\paper {

  oddFooterMarkup = \markup {
    \fill-line {
  \tiny {
    {"Edited by Joei"}
    \line  {\fromproperty #'header:composer " - " \fromproperty 
#'header:title }

   "Copyright 2024"
  }
    }
  }
}

-->8---

Best regards
Joei


--
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft.
www.avast.com

New package implementing support for The Helmholtz-Ellis Just Intonation (HEJI) pitch notation system

[Gylfi]

Greetings everyone,

I want to share with the community some work I've been doing on
implementing proper support for the HEJI notation system in LilyPond. I
wouldn't call it stable quite yet, as I'm still open to making breaking
changes to the interface based on feedback. However, I would say it has
(hopefully) reached the point where it is usable in real projects. You can
find the repository here:

https://github.com/BridgeTheMasterBuilder/heji-ly

(let me know if you are opposed to using GitHub, I can also host it
somewhere else)

The differences between this package and existing packages that also
implement HEJI support (I am personally only aware of two:
https://github.com/levinericzimmermann/ekme-heji.ily and
https://github.com/GregoryREvans/abjad-ext-microtones) are the following:

   - Complete support for all accidentals, with the exception of
   "enharmonic schismas" and equal-tempered accidentals which are planned for
   future releases.
   - Modular interface for arbitrary combinations of accidentals (this is
   perhaps what I'm most interested in getting feedback on - to me it's a
   reasonable interface but I don't know what other people's opinion will be)
   - Full playback support, even for chords, which I believe is just about
   as accurate as MIDI will allow. Sounds pretty good to my ears in any case.

I've included some example scores in the repository, including: Recreating
the otonal and utonal harmonic series examples found here
https://marsbat.space/pdfs/HEJI2_legend+series.pdf; some other examples
related to the harmonic series; a classic Ben Johnston chord from the song
Quietness; a Barbershop quartet arrangment of Kentucky Babe notated with
the exact harmonies that could plausibly appear in a performance (but still
highly theoretical and pure, it's not a transcription of any real
performance) and a traditional bagpipe tune Sweet Maid of Glendaruel. These
last two examples are a bit out there as far as using HEJI notation is
concerned. I only chose them because they are "natural" examples of 7-limit
just intonation that happen to be public domain (if anybody knows of any
other examples of public domain music in extended just intonation please
let me know).

Before starting this project I had virtually no exposure to the Scheme API
(though I've been a semi-casual LilyPond user for a long time), so I might
be doing some things inefficiently or violating some best practices, let me
know if you see something particularly egregious. There are some hacks in
there that I want to properly address at some point, they should be marked
with TODO.

I hope this will be useful to others.

Best regards,
masterbuilder

Re: B.A.C.H. motif

[Raphael Mankin]

That is so silly that I love it.

On 19/03/2024 13:27, Xavier Scheuer wrote:
On Tue, 19 Mar 2024 at 13:57, Peter Mayes > wrote:

 >
 > Being relatively new to this forum, I suspect I am not the first person
 > to ask this.
 >
 > And it is more out of curiosity than necessity.
 >
 > But does anybody have lilypond code to engrave the famous B.A.C.H. motif
 > in the attached image?

Hello,

Years ago, Pierre Perol-Schneider had contributed the following code on 
the French-speaking mailing list.
https://lilypond.community/t/est-ce-possible/3672/2 



\version "2.18.2"

\markup {
   \combine
   \score {
     {
   \key f\major
   \tweak extra-offset #'(-2 . 0) bes'1
   \clef C
   \override Staff.Clef.stencil =
     #(lambda (grob) (grob-interpret-markup grob
   #{ \markup\rotate #180 \musicglyph 
#"clefs.C" #}))

   \bar ""
     }
     \layout {
   \context {
     \Staff
     \hide TimeSignature
   }
     }
   }
   \rotate #90
   \translate #'(1 . 0)
   \score {
     {
   \key f\major
   \hide bes'1
   \clef mezzosoprano
   \override Staff.Clef.stencil =
     #(lambda (grob) (grob-interpret-markup grob
   #{ \markup\rotate #180 \musicglyph 
#"clefs.C" #}))

   \bar ""
     }
     \layout {
   \context {
     \Staff
     \hide TimeSignature
     \override KeySignature.stencil =
     #(lambda (grob) (grob-interpret-markup grob
   #{ \markup\musicglyph 
#"accidentals.natural" #}))

   }
     }
   }
}

Kind regards,
Xavier



--
https://saturday-october-seven.com/

Tremolo with staccato

[Ralph Palmer]

Hello, again!

This list has been a great help on numerous occasions.

I have a new problem - how to combine staccato with tremolo. I'm
attaching an example from the score I'm trying to transcribe. The
problem is similar to

Adding double and triple tonguing indications for woodwind

from the LSR, but without the "tuplet number". I don't know how to
adjust the code.

I would, as usual, greatly appreciate any help.

All the best,

Ralph
__
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com


halfNoteTremolo.pdf
Description: Adobe PDF document

Re: B.A.C.H. motif

[Aaron Hill]

On 2024-03-19 5:55 am, Peter Mayes wrote:
Being relatively new to this forum, I suspect I am not the first person 
to ask this.


And it is more out of curiosity than necessity.

But does anybody have lilypond code to engrave the famous B.A.C.H. 
motif in the attached image?


I did not check for prior work, so here is what I just put together:


\version "2.22.0"
\language deutsch

\layout { \context { \Score
  \omit SystemStartBar
  \omit TimeSignature
  \omit BarLine
} }

%% Offsets
#(define x1 -0.88)
#(define y1 0.062)
#(define x2 0.438)
#(define y2 0.88)
#(define x3 -0.15)
#(define y3 0.03)

accLeft = \once \override
  Accidental.extra-offset = #'(-1 . 0)
noNH = \once \hide NoteHead

\markup \overlay {

  \translate #(cons (+ x1 x3) (+ y1 y3))
  \general-align #X #CENTER \vcenter
  \score { { \clef treble \accLeft b'1 } }

  \translate #(cons (- x2 x3) (- y2 y3))
  \general-align #X #CENTER \vcenter
  \rotate #-90
  \score { { \clef tenorvarC \noNH a1 } }

  \translate #(cons (- x3 x1) (- y3 y1))
  \general-align #X #CENTER \vcenter
  \rotate #180
  \score { { \clef altovarC \noNH c'1 } }

  \translate #(cons (- 0 x2 x3) (- 0 y2 y3))
  \general-align #X #CENTER \vcenter
  \rotate #90
  \score { { \clef treble \accLeft \noNH h'! 1 } }

}



-- Aaron Hill

B.A.C.H. motif

[Jean Louis Thiry]

Here: https://lilypond.community/t/est-ce-possible/3672

-- 

Jean Louis Thiry
thir...@ramierou.eu

390A rue du Ramiérou à Montauban

Re: B.A.C.H. motif

[Xavier Scheuer]

On Tue, 19 Mar 2024 at 13:57, Peter Mayes  wrote:
>
> Being relatively new to this forum, I suspect I am not the first person
> to ask this.
>
> And it is more out of curiosity than necessity.
>
> But does anybody have lilypond code to engrave the famous B.A.C.H. motif
> in the attached image?

Hello,

Years ago, Pierre Perol-Schneider had contributed the following code on the
French-speaking mailing list.
https://lilypond.community/t/est-ce-possible/3672/2

\version "2.18.2"

\markup {
  \combine
  \score {
{
  \key f\major
  \tweak extra-offset #'(-2 . 0) bes'1
  \clef C
  \override Staff.Clef.stencil =
#(lambda (grob) (grob-interpret-markup grob
  #{ \markup\rotate #180 \musicglyph #"clefs.C"
#}))
  \bar ""
}
\layout {
  \context {
\Staff
\hide TimeSignature
  }
}
  }
  \rotate #90
  \translate #'(1 . 0)
  \score {
{
  \key f\major
  \hide bes'1
  \clef mezzosoprano
  \override Staff.Clef.stencil =
#(lambda (grob) (grob-interpret-markup grob
  #{ \markup\rotate #180 \musicglyph #"clefs.C"
#}))
  \bar ""
}
\layout {
  \context {
\Staff
\hide TimeSignature
\override KeySignature.stencil =
#(lambda (grob) (grob-interpret-markup grob
  #{ \markup\musicglyph #"accidentals.natural"
#}))
  }
}
  }
}

Kind regards,
Xavier

B.A.C.H. motif

[Peter Mayes]

Being relatively new to this forum, I suspect I am not the first person 
to ask this.


And it is more out of curiosity than necessity.

But does anybody have lilypond code to engrave the famous B.A.C.H. motif 
in the attached image?


Thanks in advance.

--
Best wishes -- Peter
--
Peter Mayes
07460 890503

a small correction in arithmetic expressions

[Silvain Dupertuis]

Here is a small correction in the documentation which does not affect the use of Lilypond, 
just for the sake of correctness of the formulas...


On this page  
about the syntonic comma,the arithmetic expressionscontains a mistake and some 
inconsistency. Addition and subtraction of intervals should be represented in the 
arithmetic expression by multiplication and division operators.


So the first expression should be written “(9:8)^2 / (5:4) = 81:80” rather than “(9:8)^2 - 
5:4 = 81:80”.


For the second one, there is also a missing pair of parenthesis (or a sign 
error):

It is written as “(3:2)^4 - (2:1)^2 + (5:4)”, but should rather be written “(3:2)^4 - 
((2:1)^2 + (5:4))”. Then, replacing the addition/subtraction signs, one gets “(3:2)^4 / 
((2:1)^2 * (5:4))” as the correct arithmetic expression corresponding to the textual 
definition — which is equal to “(3:2)^4 / (2:1)^2 / (5:4)”, if we write it without the 
additional pair of parenthesis.


--
Silvain Dupertuis
Route de Lausanne 335
1293 Bellevue (Switzerland)
tél. +41-(0)22-774.20.67
portable +41-(0)79-604.87.52
web: silvain-dupertuis.org 

Re: coloring notes with more voices in a staff

[Go77]

Dear William, Aaron and Pierre,

thank you so much for your quick reply.

I ended up writing it using the hint by Aaron like this (which I find 
makes writing the individual voices easier and also 'flipping' the color 
over to the other voice):


/\version "2.24.3"
\relative c'
  {
 f2( g4.)
 << { \override NoteHead.color = #red
  g8 | f4 f4 g8 a a4 | a2. } \\
    { d,8 | d4 d4 e8 f f4 | f2( e4) } >>
 a8 r

   }
/

which gives:

Thanks again,
Joop


On 18-03-2024 19:06, Pierre Perol-Schneider wrote:

Hi Joop,

I'd forget voices and do:

\version "2.24.3"

nr = \tweak color #red \etc

\relative c
  {
       f'2( g4.)
       8 |
       <\nr d f>4 q <\nr e g>16 <\nr f a>
        a8 r4
  }

HTH, cheers,
Pierre

Le lun. 18 mars 2024 à 18:44, Go77  a écrit :

Hi,

I'm trying to color the note heads of a single voice in a staff. I
tried to do that with the following code:

/\version "2.24.3"
\relative c
  {
   f'2( g4.)
    << { d8 | f4 f4 g16 a }
   { \override NoteHead.color = #red
 g8 | d4 d4 e16 f
 \revert NoteHead.color } >>
    a8 r4
  } /

This results in the noteheads of /both /voices being colored
instead of only the upper one (in this case):

So, is there any way to achieve my goal of coloring only the upper
notes?

Joop