Re: Lilypond Terminates on Start-Up

[Jacques Menu]

Hello folks,

Fresco 3.3.0, which I appreaciate a lot, runs fine here on MacOS 13.5.2, in 
case that may help.

I’d like to contribute to maintaining Fresco on this platform. My current 
knowledge of its code base is close to zero, but I’m currently looking into Qt 
for my own needs.

So with some initial help, I could try delving into that.

JM

> Le 22 sept. 2023 à 06:21, Zone Dremik  a écrit :
> 
> I have attached the system report/dump from the Frescobaldi force-quit under 
> Mac OS Ventura. 
> 
> Also, selecting the option to not show the splash-screen during start-up made 
> no difference. It still froze during initial start-up and ran fine for each 
> successive start/quit cycle, until powering-off the computer. 
> 
> When Frescobaldi initially becomes unresponsive, it has no presence in the 
> user interface, (no menus or windows; only shows in the system monitor). 
> Clicking the icon does nothing, but if I subsequently go back and 
> double-click a .ly file, then the menus appear and the file opens in all the 
> usual Frescobaldi windows, however, everything is frozen and I must 
> force-quit. 
> 
> Thanks for your help. I appreciate all the work done to keep 
> Frescobaldi/Lilypond on the Mac OS all these years, and I understand that 
> much depends on available resources. 
> 
> 
> On Tuesday, September 19, 2023 at 06:16:20 AM EDT, Jean Abou Samra 
>  wrote: 
> 
> 
> Le lundi 18 septembre 2023 à 18:13 +, Zone Dremik a écrit :
>> Hello,
>> 
>> This is a follow-up concerning Frescobaldi start-up problems on Mac Ventura 
>> 13.5 (I should clarify that this is an issue that only occurs when I first 
>> start Frescobaldi after having powered-on the computer). 
>> 
>> I upgraded to Frescobaldi 3.3.0 via MacPorts. That worked very well, but the 
>> anomalous behavior is the same. 
>> 
>> If I double-click a .ly file icon in the Mac Finder, I get the start-up 
>> animation and Frescobaldi splash screen. No menus appear and the file is not 
>> opened. 
>> 
>> Mac system show Frescobaldi not responding. 
>> 
>> If I go back and double-click the .ly file icon,(while Frescobaldi is 
>> running, but not responding) the file opens in the usual Frescobaldi 
>> window-set, along with the menus at the top of the screen. However, 
>> everything is inoperative, and still shows Not Responding in Mac system 
>> activity monitor. 
>> 
>> There is no response when clicking menus, and I can not select and edit the 
>> code. I must force quit. 
>> 
>> I tried waiting up to ten minutes, so see if it was just busy or slow.
>> 
>> At this point, I can start Frescobaldi from the app icon and then 
>> double-click a .ly file-icon, and everything runs properly. I can quit and 
>> start again without problems, until I power-off the computer. 
> 
> 
> 
> Not sure why I didn't think about it earlier, but this may be
> https://github.com/frescobaldi/frescobaldi/issues/428
> or a variant of it.
> 
> When Frescobaldi freezes, if you click its icon on the dock, does it come 
> back?
> 
> As you can see, that issue is an old problem that remained a mystery to 
> everyone until I was able to find (after lots of searching) a plausible cause 
> last May. I haven't been able to produce a fix yet (though there was some 
> progress <https://github.com/frescobaldi/python-poppler-qt5/pull/60> towards 
> simplifying the creation of app bundles, which could help).
> 
> Historically, macOS has been a pain to support for Frescobaldi (and LilyPond) 
> because of the peculiar user interface and distribution requirements imposed 
> by the platform, but also and most importantly the acute lack of contributors 
> to Frescobaldi on macOS. (This has been a problem for LilyPond itself too, by 
> the way.) Most contributors, including the original Frescobaldi author and 
> most of the currently active people (like myself) are running Linux. That 
> Frescobaldi kept working on macOS was basically a heroic effort by Davide 
> Liessi, who however has little time for it. Some people like Jacques Menu 
> kindly offered to help building installers, from detailed instructions, which 
> is how the latest release has an installer for Apple Silicon machines. But 
> the set of people with both Python / PyQt skills plus familiarity with 
> Frescobaldi's source code, and a working macOS environment, is basically 
> reduced to Davide, who doesn't have time. There is also a remote machine on 
> MacStadium that I can use, but the connection is horrendously slow and breaks 
> frequently and the system is old. That doesn't really scale. I know that 
> there are repeated complaints about (non-blocking) oddi

Re: Problems with musicxml2ly

[Jacques Menu]

Well, well, it seems I’m getting too old to try and help other users, and that 
the only misleading thing is my environment being set to have ‘.mxl’ files 
opened by MuseScore...

Sorry for the (large) noise!

JM

Re: LilyPond 2.24.0 released!

[Jacques Menu]

Great job, thanks to the dev folks!

JM

Re: Changing Header Mid-Score

[Jacques Menu]

Thumbs up, Jean, this is worth being in the LPNR!

JM

> Le 11 déc. 2022 à 04:05, brin solomon  a écrit :
> 
> 
> 
> On Sat, Dec 10, 2022 at 6:09 AM Jean Abou Samra  > wrote:
>> Le 09/12/2022 à 23:04, Kieren MacMillan a écrit :
>> > As far as I know:
>> > 1. a separate bookpart is required to change the properties that the 
>> > titling mechanism can read; and
>> > 2. a bookpart will always force a page break.
>> >
>> > Cue Jean providing code to contradict my claim in 3… 2… 1…  ;)
>> 
>> 
>> [Although 2.23 is the unstable release series, the stable
>> release 2.24 is going to come out of it very soon, so I
>> will stick with it.]
>> 
>> 
>> For a start, you can use \if \on-page #2 to print some
>> text only on page 2, so you could get along manually with
>> 
>>\if \on-page #1 ...
>>\if \on-page #2 ...
>>...
>> 
>> 
>> Doing that automatically is ... not exactly straightforward,
>> but possible too.
>> 
>> 
>> \version "2.23.82"
>> 
>> sceneMark = \tweak details.is-scene-mark ##t \textMark \etc
>> 
>> \layout {
>>\context {
>>  \Score
>>  \consists
>>#(lambda (context)
>>   (let ((scene-text ""))
>> (make-engraver
>>  (acknowledgers
>>   ((text-mark-interface engraver grob source-engraver)
>>(when (assq-ref (ly:grob-property grob 'details)
>>'is-scene-mark)
>>  (set! scene-text (ly:grob-property grob 'text)
>>  ((stop-translation-timestep engraver)
>>   (let ((col (ly:context-property context 
>> 'currentCommandColumn)))
>> (ly:grob-set-nested-property!
>>  col
>>  '(details scene-text)
>>  scene-text))
>>}
>> }
>> 
>> #(define-markup-command (scene-text layout props gauge) (markup?)
>> (let ((page-number (chain-assoc-get 'page:page-number props))
>>   (gauge-stil (interpret-markup layout props gauge)))
>>   (ly:make-stencil
>>`(delay-stencil-evaluation
>>  ,(delay
>>(ly:stencil-expr
>> (interpret-markup
>>  layout
>>  props
>>  (hashv-ref (ly:output-def-lookup layout 
>> 'page-number-scene-text-table)
>> page-number)
>>(ly:stencil-extent gauge-stil X)
>>(ly:stencil-extent gauge-stil Y
>> 
>> \paper {
>>oddHeaderMarkup = \markup
>>\fill-line {
>>  ""
>>  \unless \on-first-page-of-part \fontsize #2 \concat {
>>\fromproperty #'header:title
>>": "
>>%% The argument to \scene-text is used to approximate the dimensions
>>%% of the final text.
>>\scene-text "Act X, Scene X"
>>  }
>>  \if \should-print-page-number \fromproperty #'page:page-number-string
>>}
>>evenHeaderMarkup = \markup
>>\fill-line {
>>  \if \should-print-page-number \fromproperty #'page:page-number-string
>>  \unless \on-first-page-of-part \fontsize #2 \concat {
>>\fromproperty #'header:title
>>": "
>>\scene-text "Act X, Scene X"
>>  }
>>  ""
>>}
>>#(use-modules (srfi srfi-1))
>>page-post-process =
>>  #(lambda (paper pages)
>> (for-each
>>  (lambda (page)
>>(let* ((page-number (ly:prob-property page 'page-number))
>>   (lines (ly:prob-property page 'lines))
>>   (table (or (ly:output-def-lookup paper 
>> 'page-number-scene-text-table #f)
>>  (let ((table (make-hash-table)))
>>(ly:output-def-set-variable! paper 
>> 'page-number-scene-text-table table)
>>table)))
>>   (first-system
>>(any (lambda (line)
>>   (ly:prob-property line 'system-grob #f))
>> lines))
>>   (scene-text
>>(if first-system
>>(let ((first-column (ly:spanner-bound 
>> first-system LEFT)))
>>  (assq-ref (ly:grob-property first-column 'details)
>>'scene-text))
>>"")))
>>  (hashv-set! table page-number scene-text)))
>>  pages))
>> }
>> 
>> 
>> %%% EXAMPLE
>> 
>> \header {
>>title = "Silly Opera"
>> }
>> 
>> {
>>\sceneMark "Act I, Scene i"
>>c'1 1 1
>>\pageBreak
>>c'1 1 1
>>\pageBreak
>>c'1 1 \sceneMark "Act I, Scene ii" 1
>>\pageBreak
>>c'1 1 1
>> }
>> 
>> 
>> 
>> 
>> Cheers,
>> Jean
>> 
> 
> 
> Hi Jean,
> 
> Wow, this is really phenomenal! Thank you so much for this code! This should 
> work perfectly for what I need.
> 
> Many many thanks,
> brin

Re: Page reference problem

[Jacques Menu]

Le 23 nov. 2022 à 15:27, David Kastrup  a écrit :
> 
>> My problem is : how can I get the last page number computed alright,
>> but without this extra staff for the label itself?
> 
> By putting the label into one of the existing staves rather than in a
> staff of its own?

Thanks David, good hint!

I use a dynamics voice to hold the structure of the piece, with repeats and all:

\book {
  \score {
{
  {
<<

  \new Dynamics {
\Structure
  }


  \new ChoirStaff <<

… … …

}


Structure = {
  \repeat segno 2 {
\partial 2 % 1
s2 |

… … …

  % 34
  s1*5 |
  \fine
}

Adding :

  \label #'DenierePage

at the end of Structure solves the issue.

A nice day!

JM

Re: Page reference problem

[Jacques Menu]

Hello David,

Thanks for your answer.

My problem is : how can I get the last page number computed alright, but 
without this extra staff for the label itself?

JM

> Le 23 nov. 2022 à 13:29, David Kastrup  a écrit :
> 
> Jacques Menu  writes:
> 
>> Hello folks,
>> 
>> The simple example in the doc works fine, but what if the score
>> contains parallel music? An extra staff is printed in my attempts.
> 
> I don't see an extra Staff.  You get one Staff for every independently
> started music in your \score.
> 
>> \book {
>>  \score {
>>{
>>  <<
>>a1
>>b1
>>>> 
>> 
>>  \label #'DenierePage %%% HERE
>>}
>>  }
>> }
>> 
> 
> One Staff for a1, one Staff for b1, and one Staff for \label #'DenierePage
> 
> You'll see the same when writing
> 
> \score {
>  {
><< a1 b >>
>c
>  }
> }
> 
> 
> -- 
> David Kastrup

Page reference problem

[Jacques Menu]

Hello folks,

The simple example in the doc works fine, but what if the score contains 
parallel music? An extra staff is printed in my attempts.

Thanks for the help!

JM




\version "2.23.80"

% disposition
% --

\header {
  title= "Kumbaya"
  composer = "Negro-spiritual"
}

\paper {
  print-page-number = ##t
  print-first-page-number = ##f

  oddHeaderMarkup = \markup {
DenierePage à la page \page-ref #'DenierePage "0" "?"
  }
  %  evenHeaderMarkup = \oddHeaderMarkup
  evenHeaderMarkup = \markup {
\unless \on-first-page
\fill-line {
  \line {
\fromproperty #'header:title
" - Page "
\concat {
  \fromproperty #'page:page-number-string
  "/"
  \page-ref #'DenierePage "0" "?"
  % "0": un chiffre suffit pour indiquer la largeur du chanmp à prévoir
  % "2' ou "3": devrait pouvoir être "?"
}
  }
  \line {
DenierePage à la page \page-ref #'DenierePage "0" "?"
  }
}
  }
}

\layout {
  \context {
\Score
% autoBeaming = ##f % to display tuplets brackets
  }

  \context {
\Voice
  }
}


\book {
  \score {
{
  <<
a1
b1
  >>

  \label #'DenierePage %%% HERE
}
  }
}

Re: Hiding lyrics extenders on empty measures

[Jacques Menu]

Hello Werner,

As it turns out, it’s Score.LyricHyphen.stencil I have to play with, since in 
my actual score, the end of the word 'Kum — ba — ya' occurs at the beginning of 
the coda :




But :

\override Score.LyricHyphen.stencil = ##f 
kum — ba --
\revert Score.LyricHyphen.stencil
ya

prevents the hyphen I need  after ‘ba’ at the end of measure 13 from being 
visible : it’s either all hyphens of none of them.

So I use :

Lo -- ord Kum --
\once  \override LyricText.X-offset = #-0.5
"ba  -"

instead, at the cost of this minus sign being slightly too thick.

Would be nice to be able to be able to hide all the hyphens except the first 
one in such a situation.

A nice day!

JM

Re: Hiding lyrics extenders on empty measures

[Jacques Menu]

Hello Werner,

Thanks for pointing this out, and sorry for the noice : I’ve done so many 
attempts that this escaped me.

A nice day!

JM

> Le 23 nov. 2022 à 08:05, Werner LEMBERG  a écrit :
> 
> 
>> Overriding Score.LyricExtender.stencil to hide the extenders seems
>> to be ineffective, as show below. OverridingScore.LyricText.stencil
>> works fine, though.
> 
> Well, you have
> 
> ```
>Lor -- d  -- |
> ```
> 
> If you replace this with
> 
> ```
>Lor -- d  __ |
> ```
> 
> it works as expected.  What am I missing?
> 
> 
>   Werner
> 

Hiding lyrics extenders on empty measures

[Jacques Menu]

Hello folks,

Overriding Score.LyricExtender.stencil to hide the extenders seems to be 
ineffective, as show below. OverridingScore.LyricText.stencil works fine, 
though.

Thanks for any help!

JM



\version "2.23.80"

#(set-global-staff-size 32)

\score {
  <<

\new Staff
<<
  \new Voice = "voixA"  {
\clef "treble"
\partial 2
a2 |
b16 c8. r4 r2 |
f8 g4. a2 ~ |
a2 r2
  }

  \new Lyrics \lyricsto "voixA"
  {
Oh   |
\override Score.LyricExtender.stencil = ##f %%% <-- HERE
Lor -- d  -- |
\revert Score.LyricExtender.stencil
Kum -- ba -- ya __
  }


>>
  >>
}

Re: A lyrics problem

[Jacques Menu]

Hello Valentin,

Thanks, that’s a great idea!

JM

> Le 22 nov. 2022 à 00:35, Valentin Petzel  a écrit :
> 
> Hi Jacques,
> there is also the option of doing something like this:
> 
> { c2 2 << R1*3 { s8 \grace { \once\omit NoteHead c1 } s4. s2 s1 s2 s4. \grace 
> { \once\omit NoteHead c1 } } >> c1 }
> \addlyrics { \set includeGraceNotes = ##t Kum -- ba -- "" "" -- ya }
> 
> I suppse a proper implementation would have somthing like \laissezVibrer and 
> \repeatTie just for Lyric-Hyphens.
> 
> Cheers,
> Valentin
> 
> Am Montag, 21. November 2022, 23:46:50 CET schrieb Jacques Menu:
>> With:
>> 
>>% (12)
>>Oh |
>>Lo -- rd Kum --
>>\once  \override LyricText.X-offset = #-0.5
>>"ba  -" -- |
>> 
>> I get this, which is not bad :
> 

Re: A lyrics problem

[Jacques Menu]

With:

% (12)
Oh |
Lo -- rd Kum --
\once  \override LyricText.X-offset = #-0.5
"ba  -" -- |

I get this, which is not bad :




> Le 21 nov. 2022 à 23:27, Jacques Menu  a écrit :
> 
> Hello folks,
> 
> I have a word across a measure and a coda placed farther ahead in the score, 
> as shown below.
> 
> Is there a way to hide the hyphens between "Kumba" and the measure starting 
> the coda?
> 
> This can be tested on the snippet at the end of this message.
> 
> Thanks if you can help!
> 
> JM
> 
> 
> 
> 
> 
> … … …
> 
> 
> 
> 
> 
> 
> 
> \version "2.23.80"
> 
> #(set-global-staff-size 32)
> 
> \score {
>  <<
> 
>\new Staff
><<
>  \new Voice = "voixA"  {
>\clef "treble"
>\partial 2
>a2 |
>b16 c8. r4 r2 |
>f8 g4. a2 ~ |
>a2 r2
>  }
> 
>  \new Lyrics \lyricsto "voixA"
>  {
>Oh   |
>Lor -- d  -- | %%% <-- Here
>Kum -- ba -- ya __
>  }
> 
> 
>>> 
>>> 
> }
> 
> 
> 

A lyrics problem

[Jacques Menu]

Hello folks,

I have a word across a measure and a coda placed farther ahead in the score, as 
shown below.

Is there a way to hide the hyphens between "Kumba" and the measure starting the 
coda?

This can be tested on the snippet at the end of this message.

Thanks if you can help!

JM





… … …







\version "2.23.80"

#(set-global-staff-size 32)

\score {
  <<

\new Staff
<<
  \new Voice = "voixA"  {
\clef "treble"
\partial 2
a2 |
b16 c8. r4 r2 |
f8 g4. a2 ~ |
a2 r2
  }

  \new Lyrics \lyricsto "voixA"
  {
Oh   |
Lor -- d  -- | %%% <-- Here
Kum -- ba -- ya __
  }


>>
  >>
}

Re: Terminology question

[Jacques Menu]

Hello Jean,

> Le 31 oct. 2022 à 09:04, Jean Abou Samra  a écrit :
> 
> Hi Jacques,
> 
> Le 31/10/2022 à 06:39, Jacques Menu a écrit :
>> Hello folks,
>> 
>> Is there a LilyPond-specific term for the position of an element in a 
>> measure, such a 7/16?
> 
> 
> Do you mean 7/16 as a fraction of the length of a whole note,

Yes.

> or a fraction of the length of a measure?
> 
> The former is called "measure position" by LilyPond and stored
> in the measurePosition context property. The latter has no specific
> name as far as I know, but could be computed as
> measurePosition / measureLength.
> 
> Both of these are of the type Moment that Aaron described. It's
> essentially a rational number plus an optional grace part
> (another rational number). The grace part of measurePosition
> can be nonzero, that of measureLength is always zero.

Thanks, that’s what I was looking for.

A nice day!

JM

Re: Terminology question

[Jacques Menu]

Hello Aaron,

> Le 31 oct. 2022 à 08:38, Aaron Hill  a écrit :
> 
> On 2022-10-30 10:39 pm, Jacques Menu wrote:
>> Is there a LilyPond-specific term for the position of an element in a 
>> measure, such a 7/16?
> 
> I believe "moment" is what you are looking for.

That was my first thought, but moment looks more like a duration, cf the uses 
of make-moment().

Terminology question

[Jacques Menu]

Hello folks,

Is there a LilyPond-specific term for the position of an element in a measure, 
such a 7/16? 

Thanks!

JM

Re: Problems with pdf output using Lilypond Version 2.20.0

[Jacques Menu]

Hello Ian,

You’re far better off moving to LilyPond 2.23.80 at once.

Here is how I installed it on my Mac Mini M1 some days ago.

HTH!

JM

—

LilyPond devel from MacPorts for Apple silicon

If not yet done, download MacPorts for your MacOS version from 
https://github.com/macports/macports-base/releases/tag/v2.8.0 and install it.

Check wether LilyPond devel is already installed:

jacquesmenu@macmini:/opt/local/bin > port installed lilypond-devel
The following ports are currently installed:
  lilypond-devel @2.23.13_0 (active)

If LilyPond devel is lready installed, uninstall it:

jacquesmenu@macmini:/opt/local/bin > sudo port uninstall lilypond-devel
--->  Deactivating lilypond-devel @2.23.13_0
--->  Cleaning lilypond-devel
--->  Uninstalling lilypond-devel @2.23.13_0
--->  Cleaning lilypond-devel

Install lilypond-devel:

jacquesmenu@macmini:/opt/local/bin > sudo port install lilypond-devel 
Warning: The macOS 13 SDK does not appear to be installed. Ports may not build 
correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.
Warning: If already installed, update with Software Update, or manually: 

Warning: The macOS 13 SDK does not appear to be installed. Ports may not build 
correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install'.
Warning: If already installed, update with Software Update, or manually: 

--->  Computing dependencies for libatomic_ops
--->  Fetching archive for libatomic_ops
--->  Attempting to fetch libatomic_ops-7.6.14_0.darwin_22.arm64.tbz2 from 
https://packages.macports.org/libatomic_ops
--->  Attempting to fetch libatomic_ops-7.6.14_0.darwin_22.arm64.tbz2 from 
https://nue.de.packages.macports.org/libatomic_ops
--->  Attempting to fetch libatomic_ops-7.6.14_0.darwin_22.arm64.tbz2 from 
https://fra.de.packages.macports.org/libatomic_ops
… … … …

Check that lilypond runs fine:

jacquesmenu@macmini:~ > /opt/local/bin/lilypond --version
GNU LilyPond 2.23.80 (running Guile 2.2)

Copyright (c) 1996--2022 by
  Han-Wen Nienhuys 
  Jan Nieuwenhuizen 
  and others.

This program is free software.  It is covered by the GNU General Public
License and you are welcome to change it and/or distribute copies of it
under certain conditions.  Invoke as `lilypond --warranty' for more
information.

Re: \chordMode question

[Jacques Menu]

Thanks Jean and Yagloops, I had overlooked the quarter note default length!

JM

> Le 20 oct. 2022 à 12:59, Jacques Menu  a écrit :
> 
> Hello folks,
> 
> Strangely enough, the first three chords in 
> Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES below are quater notes, and 
> not whole notes as I expected.
> 
> Any hint why is welcome!
> 
> JM
> 
> %%%
> 
> \version "2.23.13"
> 
> Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES = \chordmode {
>   \language "nederlands"
>   \key c \major
>   \numericTimeSignature \time 4/4
> 
>   \clef "treble"
>   c:m f:m7 g:maj7 cis4:aug/gis   % <- HERE
> }
> 
> Part_POne_Staff_One_Voice_One = \absolute {
>   \language "nederlands"
>   \key c \major
>   \numericTimeSignature \time 4/4
> 
>   \clef "treble"
>   f'4 e'8 [ c' ] d'4 g' | % 2
>   \barNumberCheck #2
> }
> 
> \book {
>   \score {
> <<
> 
>   \new PianoStaff
>   <<
> \context ChordNames = 
> "Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES"
> \Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES
> 
> \new Staff = "Part_POne_Staff_One"
> <<
>   \context Voice = "Part_POne_Staff_One_Voice_One" <<
> \Part_POne_Staff_One_Voice_One
>   >>
> >>
> 
>   >>
> 
> >>
> 
> \layout {
> }
>   }
> 
> }
> 
> 
> %%%
> 
> 
> 
> 

\chordMode question

[Jacques Menu]

Hello folks,

Strangely enough, the first three chords in 
Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES below are quater notes, and 
not whole notes as I expected.

Any hint why is welcome!

JM

%%%

\version "2.23.13"

Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES = \chordmode {
  \language "nederlands"
  \key c \major
  \numericTimeSignature \time 4/4

  \clef "treble"
  c:m f:m7 g:maj7 cis4:aug/gis   % <- HERE
}

Part_POne_Staff_One_Voice_One = \absolute {
  \language "nederlands"
  \key c \major
  \numericTimeSignature \time 4/4

  \clef "treble"
  f'4 e'8 [ c' ] d'4 g' | % 2
  \barNumberCheck #2
}

\book {
  \score {
<<

  \new PianoStaff
  <<
\context ChordNames = "Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES"
\Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES

\new Staff = "Part_POne_Staff_One"
<<
  \context Voice = "Part_POne_Staff_One_Voice_One" <<
\Part_POne_Staff_One_Voice_One
  >>
>>

  >>

>>

\layout {
}
  }

}


%%%

Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

[Jacques Menu]

> Le 15 oct. 2022 à 21:16, Jonas Hahnfeld  a écrit :
> 
> On Sat, 2022-10-15 at 21:09 +0200, Jacques Menu wrote:
>> Hello Jonas,
>> 
>>> Le 14 oct. 2022 à 20:05, Jonas Hahnfeld  a écrit :
>>> 
>>> (regarding "automatically" in the title, please see my other reply)
>>> 
>>> To be clear, I my self am not working on this due to lack of hardware.
>>> If somebody wants to give it a try, that would again be great. I can of
>>> course try to assist, but remote debugging only gets us that far…
>> 
>> 
>> In my first attempt, I installed software on my machine with Homebrew and
>> MacPorts, and you told me that was not the way to go.
>> 
>> I have the hardware and interest, but I’d need directives about how to
>> proceed till I get a first version built the way needed to integrate that
>> in the LilyPond production workflow.
>> 
>> Can someone provide that?
> 
> If you remember, we had a bit of discussion off list in September.
> Basically, you need to run the scripts in the release/binaries/
> directory. I just re-checked the log files you sent me back then, and
> it appears that Ghostscript didn't compile. That's what you need to
> solve as a first step, maybe looking at patches in MacPorts or
> Homebrew…


OK.

And one I get this done, how do I integrate the result in the Lily build chain?

JM

Re: Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

[Jacques Menu]

Hello Jonas,

> Le 14 oct. 2022 à 20:05, Jonas Hahnfeld  a écrit :
> 
> (regarding "automatically" in the title, please see my other reply)
> 
> To be clear, I my self am not working on this due to lack of hardware.
> If somebody wants to give it a try, that would again be great. I can of
> course try to assist, but remote debugging only gets us that far…


In my first attempt, I installed software on my machine with Homebrew and 
MacPorts, and you told me that was not the way to go.

I have the hardware and interest, but I’d need directives about how to proceed 
till I get a first version built the way needed to integrate that in the 
LilyPond production workflow.

Can someone provide that?

JM

Building Mac OS LilyPond versions automatically (Was : another 'wrong type argument' error )

[Jacques Menu]

Hello folks,

I’m a regular user of Mac OS, which I use for development, and will help with 
the creation of LilyPond versions with pleasure.

My last try at building LilyPond from the source code on my Mac Mini M1 failed 
due to a library not being ported yet to this architecture, but Jonas told me 
that this should come with the current efforts by the developers team.

Hope that helps!

JM

> Le 14 oct. 2022 à 06:30, Werner LEMBERG  a écrit :
> 
> 
>>> So you checked all of LilyPond's dependencies and can guarantee
>>> that it will stay like this forever?
>> 
>> I am on Big Sur (11.6) and I can still choose 10.9 as a deployment
>> target.  [...]
> 
>>> I'm not going to work on anything. I have been alone trying to get
>>> a build for macOS even though I don't even use Apple hardware and
>>> other core developers do. It will take somebody willing to work on
>>> this effort *and commit to maintaining it* because I don't think
>>> it's a good idea to release something half-working.
>> 
>> In the spirit of my first comments in this email I’ll directly ask
>> if the project needs help testing or working on the Mac build system
>> at all?
> 
> Yes, we need help – namely for taking *permanent* care of the MacOS
> releases in
> 
>  https://gitlab.com/lilypond/lilypond/-/releases
> 
> that have been built with the scripts in
> 
>  https://gitlab.com/lilypond/lilypond/-/tree/master/release
> 
> With 'permanent' I mean that the automatically created and released
> binaries should be regularly tested on actual Mac hardware to check
> whether they work as expected.  Jonas's fear is too real that some day
> deployment support for older OS versions will break out of the blue,
> unfortunately.
> 
> As Jonas writes: He isn't a MacOS users, and none of us main
> developers is either.  It was a heroic effort of him to set up the
> scripts, but details like handling deployment targets to make this
> work on older MacOS versions needs a dedicated specialist.
> 
> 
>Werner

Re: Lilypond to XML Conversion Help

[Jacques Menu]

I get errors in the Alto part :

Démarrage lilypond 2.23.13 [19f-Boieldieu-CalifeBagdad-09-Alto.ly]...
Traitement de « 
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19f-Boieldieu-CalifeBagdad-09-Alto.ly
 »
Analyse...
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19-Boieldieu-CalifeBagdad-Global.ily:25:71
 : Avertissement : 
deprecated: missing `.' in property path Score.RehearsalMark.padding
\override Score.RehearsalMark
#'padding = #2.0 }
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19-Boieldieu-CalifeBagdad-Global.ily:26:19
 : Erreur : chaîne 
d'échappement inconnue : « \compressFullBarRests »
silencesMulti = {
\compressFullBarRests
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19-Boieldieu-CalifeBagdad-Global.ily:26:19
 : Erreur : chaîne en 
dehors d'un script textuel ou de \lyricmode
silencesMulti = {
\compressFullBarRests
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19-Boieldieu-CalifeBagdad-Global.ily:27:100
 : Avertissement : 
deprecated: missing `.' in property path MultiMeasureRest.expand-limit
\override MultiMeasureRest
#'expand-limit = #1
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19-Boieldieu-CalifeBagdad-Global.ily:29:61
 : Erreur : chaîne 
d'échappement inconnue : « \fermataMarkup »
rFermata = { \tag #'partie \set restNumberThreshold = #1 R2.
\fermataMarkup \tag #'partie \set restNumberThreshold = #0 }
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19-Boieldieu-CalifeBagdad-Global.ily:29:61
 : Erreur : chaîne en 
dehors d'un script textuel ou de \lyricmode
rFermata = { \tag #'partie \set restNumberThreshold = #1 R2.
\fermataMarkup \tag #'partie \set restNumberThreshold = #0 }
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19-Boieldieu-CalifeBagdad-Global.ily:63:46
 : Erreur : GUILE a 
signalé une erreur pour l'expression débutant ici
\on-the-fly #
not-first-page \fromproperty #'header:instrumentHeader
Unbound variable: not-first-page
/Volumes/JMI_Volume/JMI_Musique/19-Boieldieu-CalifeBagdad-LYS/19-Boieldieu-CalifeBagdad-Global.ily:63:45
 : Erreur : type 
d'argument erroné pour 1.
Attendait procedure, # trouvé.
\on-the-fly
#not-first-page \fromproperty #'header:instrumentHeader
ERROR: In procedure ly:parse-file:
In procedure reverse!: Wrong type argument in position 1: (# . #f)
Arrêté avec le code de retour 1.

JM

> Le 5 oct. 2022 à 10:33, Jacques Menu  a écrit :
> 
> Thanks, I’ll try that!
> 
> JM
> 
>> Le 4 oct. 2022 à 23:58, Ella Yu > <mailto:ella...@gmail.com>> a écrit :
>> 
>> Link to source is here: 
>> https://le-concert.pagesperso-orange.fr/boieldieu/19-Boieldieu-CalifeBagdad-LYS.zip
>>  
>> <https://le-concert.pagesperso-orange.fr/boieldieu/19-Boieldieu-CalifeBagdad-LYS.zip>
>> 
>> Just need violin and viola parts. Thanks everyone for helping!
>> 
>> On Tue, Oct 4, 2022 at 2:56 PM Jacques Menu > <mailto:imj-muz...@bluewin.ch>> wrote:
>> Hello Ella,
>> 
>> I have some experience with MusicXML and I’m interested too in trying to 
>> export your .ly file to MusicXML using Fresco.
>> 
>> Thanks if you can send me this file.
>> 
>> JM
>> 
>>> Le 4 oct. 2022 à 22:16, Stephan Schöll mailto:mu...@gmx.ch>> 
>>> a écrit :
>>> 
>>> Tried to follow the thread and
>>> 
>>> <89v5MD16SNxJTYXF.png>
>>> 
>>> - exported an arbitrary ly file using Frescobaldi experimental feature as 
>>> Jean described -> *.xml
>>> 
>>> - open *.xml file in MuseScore 3.0
>>> 
>>> <2MHR5bs5tHo0qkAF.png>
>>> 
>>> (Translation: File xyz is no valid MusicXML file. Should I try to open 
>>> anyway?)
>>> 
>>> Error message:
>>> 
>>> Fatal error: Line 11 Column 29 element 'creator' is not defined in this 
>>> area/context (namespace?)
>>> 
>>> If I decide for "load anyway" I get a reasonable result in MuseScore (I 
>>> have to admit that I never used MuseScore before ;-) ) with only a few 
>>> header elements missing.
>>> 
>>> 
>>> 
>>> Am 04.10.2022 um 21:38 schrieb Jean Abou Samra:
>>>> Le 04/10/2022 à 21:15, Ella Yu a écrit : 
>>>>> Thanks Jean. So basically the resulting exported XML literally won't open 
>>>>> in MuseScore because it says it's not a valid XML file, so I went 
>>>>> and opened it in Finale Notepad and then re-exported it and the notes 
>>>>> were all wrong. [...] 
>>>> 
>>>> Interesting. Would you mind sending the .ly file to me? I would like to 
>>>> understand what is invalid about the generated MusicXML. 
>>>> 
>>>> Thanks, 
>>>> Jean 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> http://pomp-snip.ly/>>
>> 
> 

Re: Lilypond to XML Conversion Help

[Jacques Menu]

Thanks, I’ll try that!

JM

> Le 4 oct. 2022 à 23:58, Ella Yu  a écrit :
> 
> Link to source is here: 
> https://le-concert.pagesperso-orange.fr/boieldieu/19-Boieldieu-CalifeBagdad-LYS.zip
>  
> <https://le-concert.pagesperso-orange.fr/boieldieu/19-Boieldieu-CalifeBagdad-LYS.zip>
> 
> Just need violin and viola parts. Thanks everyone for helping!
> 
> On Tue, Oct 4, 2022 at 2:56 PM Jacques Menu  <mailto:imj-muz...@bluewin.ch>> wrote:
> Hello Ella,
> 
> I have some experience with MusicXML and I’m interested too in trying to 
> export your .ly file to MusicXML using Fresco.
> 
> Thanks if you can send me this file.
> 
> JM
> 
>> Le 4 oct. 2022 à 22:16, Stephan Schöll mailto:mu...@gmx.ch>> 
>> a écrit :
>> 
>> Tried to follow the thread and
>> 
>> <89v5MD16SNxJTYXF.png>
>> 
>> - exported an arbitrary ly file using Frescobaldi experimental feature as 
>> Jean described -> *.xml
>> 
>> - open *.xml file in MuseScore 3.0
>> 
>> <2MHR5bs5tHo0qkAF.png>
>> 
>> (Translation: File xyz is no valid MusicXML file. Should I try to open 
>> anyway?)
>> 
>> Error message:
>> 
>> Fatal error: Line 11 Column 29 element 'creator' is not defined in this 
>> area/context (namespace?)
>> 
>> If I decide for "load anyway" I get a reasonable result in MuseScore (I have 
>> to admit that I never used MuseScore before ;-) ) with only a few header 
>> elements missing.
>> 
>> 
>> 
>> Am 04.10.2022 um 21:38 schrieb Jean Abou Samra:
>>> Le 04/10/2022 à 21:15, Ella Yu a écrit : 
>>>> Thanks Jean. So basically the resulting exported XML literally won't open 
>>>> in MuseScore because it says it's not a valid XML file, so I went and 
>>>> opened it in Finale Notepad and then re-exported it and the notes were all 
>>>> wrong. [...] 
>>> 
>>> Interesting. Would you mind sending the .ly file to me? I would like to 
>>> understand what is invalid about the generated MusicXML. 
>>> 
>>> Thanks, 
>>> Jean 
>>> 
>>> 
>>> 
>>> 
>>> 
>> http://pomp-snip.ly/>>
> 

Re: Lilypond to XML Conversion Help

[Jacques Menu]

Hello Ella,

I have some experience with MusicXML and I’m interested too in trying to export 
your .ly file to MusicXML using Fresco.

Thanks if you can send me this file.

JM

> Le 4 oct. 2022 à 22:16, Stephan Schöll  a écrit :
> 
> Tried to follow the thread and
> 
> <89v5MD16SNxJTYXF.png>
> 
> - exported an arbitrary ly file using Frescobaldi experimental feature as 
> Jean described -> *.xml
> 
> - open *.xml file in MuseScore 3.0
> 
> <2MHR5bs5tHo0qkAF.png>
> 
> (Translation: File xyz is no valid MusicXML file. Should I try to open 
> anyway?)
> 
> Error message:
> 
> Fatal error: Line 11 Column 29 element 'creator' is not defined in this 
> area/context (namespace?)
> 
> If I decide for "load anyway" I get a reasonable result in MuseScore (I have 
> to admit that I never used MuseScore before ;-) ) with only a few header 
> elements missing.
> 
> 
> 
> Am 04.10.2022 um 21:38 schrieb Jean Abou Samra:
>> Le 04/10/2022 à 21:15, Ella Yu a écrit : 
>>> Thanks Jean. So basically the resulting exported XML literally won't open 
>>> in MuseScore because it says it's not a valid XML file, so I went and 
>>> opened it in Finale Notepad and then re-exported it and the notes were all 
>>> wrong. [...] 
>> 
>> Interesting. Would you mind sending the .ly file to me? I would like to 
>> understand what is invalid about the generated MusicXML. 
>> 
>> Thanks, 
>> Jean 
>> 
>> 
>> 
>> 
>> 
> 

Re: Lilypond

[Jacques Menu]

Hello Laurent, 

Fresco 3.1.3 is fine on Mac for me.

JM

Envoyé de mon iPhone

> Le 18 sept. 2022 à 16:22, pagani laurent  a écrit :
> 
> Hi Valentin,
> 
> I have macported Frescobaldi and started to play with it.
> I don’t find it very explicit for the errors, and while it complains there 
> are errors it still displays the result (more or less). The really positive 
> point is indeed to show the notes between the pdf and the .ly. It has also 
> the advantage to not duplicate the pdf file like Lily does each time one 
> compiles. One has quickly 10 or 20 copies of the same file opened in Preview…
> Unlike Latex editors (texstudio, or texshop e.g.), it does not have the list 
> of reserved words/commands in lateral menus to retrieve quickly something you 
> don’t remember. But I guess there are not so many things to remember at the 
> end though I find some combinations a bit tricky.
> 
> I met another problem which is that Lily forces chords to have the same 
> duration for all notes. Maybe it is because I have not read the advanced 
> manual yet.
> From what I’ve learned until now, I tried to guess a way out like : < c2 {e4 
> r}> but it does not work. It is possible ? It is very common to have notes of 
> different durations running in parallel in the same staff.
> 
> Best
> Laurent
> 
> PS: Thanks for the file.
> 
>> Le 18 sept. 2022 à 16:06, Valentin Petzel  a écrit :
>> 
>> Hi Laurent, Hi Pierre,
>> 
>> usually using Bar checks is the way to go, but this does have its own 
>> limitations. E.g. if we misspell
>> 
>> \time 3/4 c2 d4 |
>> 
>> as
>> 
>> \time 3/4 c2 d1 |
>> 
>> this will not throw an error. Of course we could make use of bar number 
>> checks. But then, bar number checks only work if you know what bar you are 
>> in, 
>> and bar checks only work if you know what time signature you’re in.
>> 
>> But it is not hard to add additional checks. The appended file defines a 
>> pseudoengraver that checks for each placed rhythmic head if there is 
>> sufficient 
>> remaining space left in the measure and issues a warnign otherwise.
>> 
>> Cheers,
>> Valentin
>> 
>> Am Sonntag, 18. September 2022, 11:15:20 CEST schrieb Pierre Perol-Schneider:
>>> Hi Laurent, Hi Jan,
>>> @Laurent, see:
>>> https://lilypond.org/doc/v2.22/Documentation/notation/bars.html#bar-and-bar->
>>>  number-checks e.g.:
>>> \version "2.22.0"
>>> { c' e' g' e'1 | 2  }
>>> Cheers,
>>> Pierre
>>> 
 Le dim. 18 sept. 2022 à 11:02, Jan Nieuwenhuizen  a écrit 
 :
 pagani laurent writes:
 
 Can someone answer Laurent?
 
> Hi Jan,
> 
> Sorry to disturb you (possibly I should have gone to some forum but
> this is so fundamental for me that if the answer is no, I won’t use
> Lilypond, so I don’t want to bother entering the forum if it is to
> leave it immediately).
> 
> I am having a look at Lilypond and I have a very simple question :
> I wrote a very simple test score :
> 
> \version "2.22.0"
> {
> c' e' g' e'1 2
> }
> 
> and the compilation ran without error :
> 
> Traitement de « /Users/laurent/Desktop/test.ly »
> Analyse...
> Interprétation en cours de la musique...
> Pré-traitement des éléments graphiques...
> Détermination du nombre optimal de pages...
> Répartition de la musique sur une page...
> Dessin des systèmes...
> Conversion à « test.pdf »...
> Compilation menée à son terme, avec succès.
> 
> However, there is an obvious error : the e’1.
> 
> 
> 
> 
> Does this mean that Lilypond will not report such errors when writing
> a score ? That would be worrysome because that means that after having
> written tons of pages, one has to go through the final product to
> check for such errors and then locate them in the input file (I guess
> there is no such interface as with some Latex editor where the pdf and
> the latex are linked so that clicking on the pdf text, you are
> directed to the corresponding latex code) which might not be very
> obvious. If this is explained further in the manual, just tell me to
> read the manual completely but again I won’t embark in this long task
> if it is to give up at the end...
> 
> Thanks
> Laurent
> 
> 
> 
> It’s tough to make predictions- especially about the future.
> Yogi Berra
 
 --
 Jan Nieuwenhuizen   | GNU LilyPond https://lilypond.org
 Freelance IT https://JoyOfSource.com | Avatar® https://AvatarAcademy.com
>> 
>> 
> 
> Vieux dicton des pharaons ”si tu rames, cesse !”
> Le Canard Enchaîné
> 

Re: A speed test on Apple's M1 processor

[Jacques Menu]

Hello Jonas and Jean,

I send you the details privately, not to clutter this list.

JM

> Le 12 sept. 2022 à 08:20, Jonas Hahnfeld via LilyPond user discussion 
>  a écrit :
> 
> On Sun, 2022-09-11 at 11:52 +0200, Jacques Menu wrote:
>> Native lilypond:
>> 
>> jacquesmenu@macmini:/Volumes/JMI_Volume/JMI_Developpement/lilypond/re
>> lease/binaries/lilypond/install/bin > time ./lilypond
>> Fischer_Suite_Sol_M_viola_II_2.23.12.ly
> 
> Based on the path, did you build with the scripts in release/binaries
> of the repository or did you build from scratch yourself? If the
> latter, did you compile the bytecode (make bytecode)?
> 
>> GNU LilyPond 2.23.12 (running Guile 2.2)
>> Processing `Fischer_Suite_Sol_M_viola_II_2.23.12.ly'
>> … … …
>> Preprocessing graphical objects...
>> Finding the ideal number of pages...
>> Fitting music on 54 or 55 pages...
>> Drawing systems...
>> Converting to `Fischer_Suite_Sol_M_viola_II_2.23.12.pdf'...
>> fatal error: failed files: "Fischer_Suite_Sol_M_viola_II_2.23.12.ly"
>> ./lilypond Fischer_Suite_Sol_M_viola_II_2.23.12.ly  7.52s user 0.75s
>> system 98% cpu 8.387 total
> 
> You have a "fatal error" when processing the converted file. Not sure
> where this happens, but maybe check that you are really compiling what
> you think you are...
> 
> Jonas

A speed test on Apple's M1 processor

[Jacques Menu]

Hello folks,

I ran this test with a 7.4Mb, 55 page score, to compare the binaries provided 
by lilypond.org and the natives ones I (finally) built locally on my 8 Gb RAM 
Mac Mini. 
The necessary libraries have been installed using both MacPorts and Homebrew, 
since not all of them are supplied by a single source.

Both versions are 2.23.12.
The speed increase is roughly 20 to 25%, thanks to the avoidance of Intel CPU 
instructions emulation.

I will send the test file privately to anyone interested with pleasure, and you 
can send me larger files for more tests.

A nice day!

JM

--

First convert the LilyPond file to version 2.23.12.

Native convert-ly:

jacquesmenu@macmini:/Volumes/JMI_Volume/JMI_Developpement/lilypond/release/binaries/lilypond/install/bin
 > time ./convert-ly Fischer_Suite_Sol_M_viola_II.ly > 
Fischer_Suite_Sol_M_viola_II_2.23.12.ly
convert-ly (GNU LilyPond) 2.23.12

convert-ly: Processing `Fischer_Suite_Sol_M_viola_II.ly'... 
Applying conversion: 2.20.0, 2.21.0, 2.21.2, 2.23.1, 2.23.2, 2.23.3, 2.23.4, 
2.23.5, 2.23.6, 2.23.7, 2.23.8, 2.23.9, 2.23.10, 2.23.11, 2.23.12


./convert-ly Fischer_Suite_Sol_M_viola_II.ly >   5.80s user 0.04s system 99% 
cpu 5.871 total
jacquesmenu@macmini:/Volumes/JMI_Volume/JMI_Developpement/lilypond/release/binaries/lilypond/install/bin
 > time ./convert-ly Fischer_Suite_Sol_M_viola_II.ly > 
Fischer_Suite_Sol_M_viola_II_2.23.12.ly
convert-ly (GNU LilyPond) 2.23.12

convert-ly: Processing `Fischer_Suite_Sol_M_viola_II.ly'... 
Applying conversion: 2.20.0, 2.21.0, 2.21.2, 2.23.1, 2.23.2, 2.23.3, 2.23.4, 
2.23.5, 2.23.6, 2.23.7, 2.23.8, 2.23.9, 2.23.10, 2.23.11, 2.23.12


./convert-ly Fischer_Suite_Sol_M_viola_II.ly >   5.72s user 0.04s system 99% 
cpu 5.801 total
jacquesmenu@macmini:/Volumes/JMI_Volume/JMI_Developpement/lilypond/release/binaries/lilypond/install/bin
 > time ./convert-ly Fischer_Suite_Sol_M_viola_II.ly > 
Fischer_Suite_Sol_M_viola_II_2.23.12.ly
convert-ly (GNU LilyPond) 2.23.12

convert-ly: Processing `Fischer_Suite_Sol_M_viola_II.ly'... 
Applying conversion: 2.20.0, 2.21.0, 2.21.2, 2.23.1, 2.23.2, 2.23.3, 2.23.4, 
2.23.5, 2.23.6, 2.23.7, 2.23.8, 2.23.9, 2.23.10, 2.23.11, 2.23.12


./convert-ly Fischer_Suite_Sol_M_viola_II.ly >   5.71s user 0.03s system 99% 
cpu 5.748 total


LilyPond-supplied convert-ly. Here, there are variations for some reason:

jacquesmenu@macmini:/Applications/JMI_Applications/LilyPond/lilypond-2.23.12/bin
 > time ./convert-ly Fischer_Suite_Sol_M_viola_II.ly > 
Fischer_Suite_Sol_M_viola_II_2.23.12.ly

convert-ly (GNU LilyPond) 2.23.12

convert-ly: Processing `Fischer_Suite_Sol_M_viola_II.ly'... 
Applying conversion: 2.20.0, 2.21.0, 2.21.2, 2.23.1, 2.23.2, 2.23.3, 2.23.4, 
2.23.5, 2.23.6, 2.23.7, 2.23.8, 2.23.9, 2.23.10, 2.23.11, 2.23.12


./convert-ly Fischer_Suite_Sol_M_viola_II.ly >   7.18s user 0.03s system 99% 
cpu 7.225 total
jacquesmenu@macmini:/Applications/JMI_Applications/LilyPond/lilypond-2.23.12/bin
 > time ./convert-ly Fischer_Suite_Sol_M_viola_II.ly > 
Fischer_Suite_Sol_M_viola_II_2.23.12.ly

convert-ly (GNU LilyPond) 2.23.12

convert-ly: Processing `Fischer_Suite_Sol_M_viola_II.ly'... 
Applying conversion: 2.20.0, 2.21.0, 2.21.2, 2.23.1, 2.23.2, 2.23.3, 2.23.4, 
2.23.5, 2.23.6, 2.23.7, 2.23.8, 2.23.9, 2.23.10, 2.23.11, 2.23.12


./convert-ly Fischer_Suite_Sol_M_viola_II.ly >   7.25s user 0.04s system 99% 
cpu 7.323 total
jacquesmenu@macmini:/Applications/JMI_Applications/LilyPond/lilypond-2.23.12/bin
 > time ./convert-ly Fischer_Suite_Sol_M_viola_II.ly > 
Fischer_Suite_Sol_M_viola_II_2.23.12.ly

convert-ly (GNU LilyPond) 2.23.12

convert-ly: Processing `Fischer_Suite_Sol_M_viola_II.ly'... 
Applying conversion: 2.20.0, 2.21.0, 2.21.2, 2.23.1, 2.23.2, 2.23.3, 2.23.4, 
2.23.5, 2.23.6, 2.23.7, 2.23.8, 2.23.9, 2.23.10, 2.23.11, 2.23.12


./convert-ly Fischer_Suite_Sol_M_viola_II.ly >   15.13s user 0.05s system 99% 
cpu 15.203 total


—

Then apply lilypond to the converted file. ‘… ... ...’ is used for the sake of 
compactness.

Native lilypond:

jacquesmenu@macmini:/Volumes/JMI_Volume/JMI_Developpement/lilypond/release/binaries/lilypond/install/bin
 > time ./lilypond Fischer_Suite_Sol_M_viola_II_2.23.12.ly
GNU LilyPond 2.23.12 (running Guile 2.2)
Processing `Fischer_Suite_Sol_M_viola_II_2.23.12.ly'
… … …
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 54 or 55 pages...
Drawing systems...
Converting to `Fischer_Suite_Sol_M_viola_II_2.23.12.pdf'...
fatal error: failed files: "Fischer_Suite_Sol_M_viola_II_2.23.12.ly"
./lilypond Fischer_Suite_Sol_M_viola_II_2.23.12.ly  7.52s user 0.75s system 98% 
cpu 8.387 total


jacquesmenu@macmini:/Volumes/JMI_Volume/JMI_Developpement/lilypond/release/binaries/lilypond/install/bin
 > time ./lilypond Fischer_Suite_Sol_M_viola_II_2.23.12.ly
GNU LilyPond 2.23.12 (running Guile 2.2)
Processing `Fischer_Suite_Sol_M_viola_II_2.23.12.ly'
… … …
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 54 or 55 

Re: Alternative to Frescobaldi

[Jacques Menu]

Hello folks,

> Le 2 sept. 2022 à 23:46, J Martin Rushton  a 
> écrit :
> 
> On Fri, 2022-09-02 at 16:17 -0500, David Wright wrote:
>> On Fri 02 Sep 2022 at 21:43:25 (+0100), J Martin Rushton wrote:
>>> I've just spent another couple of hours clearing out previous
>>> attempts
>>> to get Frescobaldi running and attempting to sort out its
>>> dependency
>>> hell.
>>> 
>>> Is there any alternative to Frescobaldi?
>> 
>> An editor (emacs) + LilyPond + PDF viewer (xpdf).
>> (My choices in parentheses.)
>> 
>>> I'm running AlmaLinux 8.6 if that helps.
>> 
>> Not a great deal; does it mean that F~ isn't part of the
>> distribution?
>> 
>> Cheers,
>> David.
> My preference is for vi, but yes, that's what I've been using for the
> last couple of years since F~ stopped working.  What I miss though is
> the back link from the score to the source, and the MIDI playback.

Is it known why F~ stopped working and wasn’t fixed?

JM

Re: Export to XML

[Jacques Menu]

Hello Andrew,

> In your workflow, why the double export? if the result is fine from Lilypond 
> why then export from MuseScore?

I’d say it is to refine the score with MuseScore to fix the imperfect 
Lily->MusicXML export.

JM

Re: Export to XML

[Jacques Menu]

Hello,

Maybe one way could be to mimic this publishers look as much as possible, 
supposing that’s OK for them… 

I did that once for a very small company : for our own performance needs, I had 
already typeset the score we were to play from their original, handwritten by 
the composer, in the first place.

JM

> Le 26 août 2022 à 08:59, Andrew Bernard  a écrit :
> 
> I have no idea what software Schott Music Group uses for engraving, but it's 
> disappointing nowadays that many of the larger publisher are demanding that 
> composers do their work for them and requesting finished work, at least 
> finished to the point they can apply their house style. I don't think any of 
> the big names use Lilypond, and as far as I recall various efforts to get 
> Lilypond to export MusicXML (with all its limitations)  have not come to any 
> fruition. Unless they accept a PDF from you and print that or reset from 
> scratch I think you are stuck. Sorry. I think the silence on the list re your 
> question is also confirmation that there is not an answer to this. I may be 
> wrong!
> 
> Andrew
> 
> 
> On 25/08/2022 10:43 pm, nitra...@posteo.net wrote:
>> I proposed to send them my LilyPond files but I have been confirmed yesterday
>> that they cannot process those... They told me an XML file might help them
>> though. I looked if it was possible to export in XML but I read the result 
>> was
>> bad and LilyPond wasn't made for that task... So here's my question: what 
>> would
>> you suggest I could do to export my scores and help them prepare the album?
>> 
>> Thanks for the advices!
>> 
> 

Re: LilyPond 2.23.12

[Jacques Menu]

Thanks a lot to all the Lily developers for their continuous work!

JM

> Le 24 août 2022 à 07:35, Jonas Hahnfeld via LilyPond user discussion 
>  a écrit :
> 
> We are happy to announce the release of LilyPond 2.23.12. This is
> termed a development release, but these are usually reliable. However,
> if you require stability, we recommend using version 2.22.2, the
> current stable release. Please refer to the Installing section in the
> Learning Manual for instructions how to set up the provided binaries:
> https://lilypond.org/doc/v2.23/Documentation/learning/installing
> 
> Starting with this version, the official binaries support the
> experimental Cairo backend. Please give it a try with the command line
> option -dbackend=cairo and see if it works for you. In case of
> problems, please report back to us so it can be worked on.

Re: [was: Re: ANN: Frescobaldi 3.2]

[Jacques Menu]

Hello Folks,

I’ve never heard about Xcode_11.3.1.xip.
The simple way to install Xcode is to take it from the App Store (needs about 
50 Mb these days).

JM

> Le 18 août 2022 à 08:48, Jean-Julien Fleck  a 
> écrit :
> 
> Hello Jean-Louis,
> 
> Le jeu. 18 août 2022 à 03:10, Jean Louis THIRY  a écrit :
> 
> I have a question about the installation. Could this erratic behavior be a 
> result of this .sdk file being installed in the wrong order? is it possible 
> to uninstall Frescobaldi using some magic formula like "sudo port uninstall 
> frescobaldi" and do an install again so that the installer finds the sdk 
> file. Especially will there be a difference. Just an idea...
> 
> Well, it’s unlikely. I happen to have frescobaldi installed via a fresh new 
> MacPort procedure (after upgrading to MacOs Monterey) just last week and the 
> missing sdk message I encountered was related to all the qt5 stuff that 
> frescobaldi needed in order to be built. You were lucky it was not a stopper 
> as it was in my case: I had to manually add `use_xcode yes` in the 
> corresponding PortFile of py310-poppler-qt5 in order to make it build 
> properly. Perhaps it has since been corrected so that if the «standard» way 
> for qt5 to find the sdk won't work, they try the `use_xcode yes` trick 
> (whatever it does) before giving up.
> 
> All these problems, even if triggered during frescobaldi install, are 
> unrelated to it. That's just the way Macport is doing the job: whenever you 
> add a package to MacPort, it asks you what should be present on the machine 
> to make your app work and then try to install it by itself, saving the user 
> the trouble to install all the extensions and preventing multiple installs of 
> the same tools whenever two different packages need the same first building 
> block.
> 
> But as a matter of fact, it won't help to uninstall frescobaldi to try to 
> correct for lilypond path (as for one reason is that MacPort don't throw away 
> uninstalled port but keep them somewhere, ready to reinstall it without 
> further building in case you change your mind). I would rather suspect that 
> the search for different lilypond locations was done after you first looked 
> there (perhaps triggered by one of your tinkering), was written down 
> somewhere so that the next frescobaldi startup shows it.
> 
> Happy that you finally managed to get it work and have fun coding with lily 
> on frescobaldi !
> 
> -- 
> JJ Fleck
> Physique et Informatique
> PCSI1 Lycée Kléber

Re: The problem of Lilypond changing instrument and the issue of .ly converting to MIDI with a custom setting

[Jacques Menu]

Hello Angie,

> Le 4 août 2022 à 04:48, 柊希里子  <mailto:starlitnight0...@gmail.com>> a écrit :
> 
> My workflow is needed to be an automation script, cause I want to create a 
> tool to generate the annotation of each note automatically. The process is 
> like the below:
> 
> Turn the .xml file into .ly,
> Ideally, I want to eliminate all the decorations, like accent, staccato, any 
> kind of ornament, and tempo-related expression.
> Such as --nd, do not convert directions (^, _ or -) for articulations, 
> dynamics, etc.
> Command example: musicxml2ly -v --nd --midi --output="1_Bach_Prelude1.ly 
> <http://1_bach_prelude1.ly/>" ./1_Bach_Prelude1.xml
> In the .ly file, convert the instrument into Violin or Cello, no matter what 
> kind of instrument the score was originally made for, because the String 
> instrument will get a more stable note duration of MIDI file than the 
> Woodwind or Piano.
> 
> In the .ly file, eliminate all the tempo expressions, and set the tempo to 
> BPM=60.
> For the same reason as 2nd step, this step aims to get a more stable note 
> duration.
> 
> The steps 2 and 3 I wrote a python code to replace the tempo and want to 
> change the instrument clef, see the attachment “replace_tempo.py”.
> Command example: `python replace_tempo.py --path ./1_Bach_Prelude1.ly 
> <http://1_bach_prelude1.ly/>`, then output the file named just add the 
> `_replace` afterward, like: `1_Bach_Prelude1_replace.ly 
> <http://1_bach_prelude1_replace.ly/>`

Automatising such steps thru options is what xml2ly, a part of the MusicFormats 
library, is about, maybe it can help you.

The user doc is at 
https://github.com/jacques-menu/musicformats/blob/master/documentation/MusicFormatsUserGuide/MusicFormatsUserGuide.pdf
 
<https://github.com/jacques-menu/musicformats/blob/master/documentation/MusicFormatsUserGuide/MusicFormatsUserGuide.pdf>
 .

HTH!

JM

Re: Non-printing notes

[Jacques Menu]

Hello Hans,

> Le 31 juil. 2022 à 16:22, Hans Aikema  a écrit :
> 
> Loking at the spec 
> https://w3c.github.io/musicxml/musicxml-reference/elements/note/
> 
> I would say the proper behaviour is that the entire note, including the stem, 
> is hidden for these cases (but taken into account for spacing), not just the 
> notehead

That’s the ambiguity I’ve bumped into, and you’re probably right. Thanks!

JM

> 
> 
> print-dot 
> Controls the printing of an augmentation dot separately from the rest of the 
> note or rest. This is especially useful for notes that overlap in different 
> voices, or for chord sheets that contain lyrics and chords but no melody. If 
> print-object is set to no, this attribute is also interpreted as being set to 
> no if not present.
> 
> print-leger
> Indicates whether leger lines are printed. Notes without leger lines are used 
> to indicate indeterminate high and low notes. It is yes if not present unless 
> print-object is set to no. This attribute is ignored for rests.
> print-lyric   yes-no  No  Controls the printing of a lyric separately 
> from the rest of the note or rest. This is especially useful for notes that 
> overlap in different voices, or for chord sheets that contain lyrics and 
> chords but no melody. If print-object is set to no, this attribute is also 
> interpreted as being set to no if not present.
> 
> print-object
> Specifies whether or not to print an object. It is yes if not specified.
> 
> print-spacing
> Controls whether or not spacing is left for an invisible note or object. It 
> is used only if no note, dot, or lyric is being printed. The value is yes 
> (leave spacing) if not specified.
> 
> 
> 

Re: Non-printing notes

[Jacques Menu]

Hello Timothy,

Thanks for the info. This version of Finale is old, and it does print the note 
heads, ignoring the print-object attribute.

I’ll complement xml2ly to hide the note head in this case.

A nice day!

JM

> Le 31 juil. 2022 à 00:06, Timothy Lanfear  a écrit :
> 
> On 30/07/2022 17:18, Jacques Menu wrote:
>> Hello folks,
>> 
>> MusicXML has the 'print-object' attribute to notes, among other markups:
>> 
>>  
>>  
>>  D
>>  3
>>  
>>  768
>>  6
>>  quarter
>>  down
>>  2
>>  
>> 
>> This value ‘no’ is ignored by MuseScore and musicxml2ly, and Finale 2014b 
>> displays such notes in light gray this way, like the Ds and Gs below:
>> 
>> 
>> 
>> What is the intended meaning, and how should this be displayed using 
>> LilyPond?
>> 
>> Thanks for your help!
>> 
>> JM
>> 
> MuseScore 3.2.3 also displays the note head in gray, but the stem normally. 
> When converting the file to PDF or printing, the note head is omitted and the 
> stem is printed. This behaviour is equivalent to LilyPond's \hide NoteHead.
> 
> -- 
> Timothy Lanfear, Bristol, UK.

Re: Generating a spiccato

[Jacques Menu]

Hello Werner,

Thanks for the clarification!

JM

> Le 13 juil. 2022 à 16:40, Werner LEMBERG  a écrit :
> 
> 
>>> In MusixXML, this sign is  (The  element |
>>> MusicXML 4.0 (w3.org)
>>> ),
>>> the same sign is named \staccatissimo in Lilypond.
>>> In MusixXML,  looks like this:  (The 
>>> element | MusicXML 4.0 (w3.org)
>>> ),
>>> but it seems there is no corresponding articulation in Lilypond and no
>>> glyph in the Emmentaler font.
>>> 
>>> So the question is: is there interest among the LilyPond community to
>>> add the latter glyph in some way?
> 
> I consider the distinction between these two glyphs completely
> arbitrary.  At normal size, the difference between a concave and a
> convex top is not really visible.
> 
> If you look at
> 
>  https://w3c.github.io/smufl/latest/tables/articulation.html
> 
> you can see that both glyph shapes in question are defined as variants
> of 'staccatissimo' – for spiccato, there doesn't exist a symbol.  And
> rightly so: I've never seen a symbol for spiccato except an ordinary
> staccato point with the word 'spicc.' (if at all).
> 
> 
> Werner

Re: Generating a spiccato

[Jacques Menu]

Hello folks,

Here is the info I’ve been supplied with about this:
In MusixXML, this sign  is  (The  element | MusicXML 4.0 
(w3.org) 
), 
the same sign is named \staccatissimo in Lilypond. 
In MusixXML,  looks like this:  (The  element | 
MusicXML 4.0 (w3.org) 
),
 but it seems there is no corresponding articulation in Lilypond and no glyph 
in the Emmentaler font.

So the question is: is there interest among the LilyPond community to add the 
latter glyph in some way?

JM

Re: Generating a spiccato

[Jacques Menu]

Hello Siomon & Hans,

I have to ask the person who suggested that xml2ly should generate spiccatos 
what they’d like them to look like.

Thanks for your answers!

JM

> Le 28 juin 2022 à 01:03, Simon Albrecht  a écrit :
> 
> Hi Jacques,
> 
> On 27/06/2022 22:13, Jacques Menu wrote:
>> Does anyone know of some way to generate spiccato articulations in the 
>> scores produced by Lily?
> 
> 
> what would you expect that to look like?
> 
> { a'4-! }
> 
> maybe?
> 
> Best, Simon
> 

Re: Musescore/musicxml questions

[Jacques Menu]

Hello Kira,

I’ve looked at the two files you posted, and the MusicXML export is actually 
not reflecting the exact layout of the original.Converting it to LilyPond with 
xml2ly gives the same layout as when the exported file is re-imported in 
Musecore.

This is a difficult issue at any rate, to be submitted to the MuseScore team at 
https://musescore.com/user/login?destination=%2Fcas%2Flogin.

HTH!

JM

> Le 30 juin 2022 à 18:50, Kira Garvie  a écrit :
> 
> Hey all,
> I know this is a bit off-topic but it's on-topic for me... also I don't know 
> who else to ask, the muse-score forums aren't very helpful.
> I use Lilypond, Musescore, and musicxml files for my work. Please, no 
> comments on the quality of Musescore, the decision to use it was above my 
> paygrade. I am having issues exporting an xml file and having it keep its 
> formatting. Is there anyone who has experience with this and can help me off 
> the list? Or should I just can it and keep googling stuff until I stumble on 
> an answer? 
> Here are the files.
> Thank you!
> 

Generating a spiccato

[Jacques Menu]

Hello folks,

Does anyone know of some way to generate spiccato articulations in the scores 
produced by Lily?

Thanks for your help!

JM

Re: not understanding the Al_Fine repeat feature of 2.23.9

[Jacques Menu]

Iour velkom!

JM

> Le 1 juin 2022 à 17:55, Kenneth Wolcott  a écrit :
> 
> Thank you!  I got this piece to work now.  I just need to study this a
> bit more, try another couple of pieces that have repeats like this.
> 
> On Wed, Jun 1, 2022 at 12:59 AM Jacques Menu  wrote:
>> 
>> Hello Kenneth,
>> 
>> Here is the way to do it. The :
>> 
>>   \volta 2 \fine
>> 
>> should precede the note it applies to.
>> 
>> JM
>> 
>> 
>> 
>> 
>> 
>>> Le 29 mai 2022 à 01:59, Kenneth Wolcott  a écrit :
>>> 
>>> Hi;
>>> 
>>> I tried to engrave a simple Tuba Duet that has a Fine+D.C. construct
>>> using Lilypond 2.23.9
>>> 
>>> I don't think I used the Al_Fine repeat feature correctly, as the
>>> "Fine" is displayed one bar later than I expected it to be.
>>> 
>>> Could someone be so kind as to explain what I did wrong or what I
>>> could do better?
>>> 
>>> Please see attachments (the original is from Rubank Intermediate
>>> Method for Tuba).
>>> 
>>> Thanks,
>>> Ken Wolcott
>>> 
>> 

Re: not understanding the Al_Fine repeat feature of 2.23.9

[Jacques Menu]

Hello Kenneth,

Here is the way to do it. The :

   \volta 2 \fine

should precede the note it applies to.

JM



Volta2Fine.ly
Description: Binary data




> Le 29 mai 2022 à 01:59, Kenneth Wolcott  a écrit :
> 
> Hi;
> 
>  I tried to engrave a simple Tuba Duet that has a Fine+D.C. construct
> using Lilypond 2.23.9
> 
> I don't think I used the Al_Fine repeat feature correctly, as the
> "Fine" is displayed one bar later than I expected it to be.
> 
>  Could someone be so kind as to explain what I did wrong or what I
> could do better?
> 
>  Please see attachments (the original is from Rubank Intermediate
> Method for Tuba).
> 
> Thanks,
> Ken Wolcott
> 

Re: LilyPond 2.23.6 *-tmp-* files

[Jacques Menu]

Hello everybody,

Thanks for you tests and information.

In fact, these *-tmp-* files remain when the PDF is produced within 
Frescobaldi, but not when using Lily on the command line.

It turns out this stems from Frescobaldi's LilyPond preferences: for some 
reason, the ‘remove intermediate files’ box was unselected… Don’t know how that 
happened.

Sorry for the noise!

JM

Re: vertical half-brackets

[Jacques Menu]

Thanks Dan!

JM

> Le 31 mai 2022 à 20:19, delfink .  a écrit :
> 
> 
>> On May 31, 2022, at 4:39 AM, Werner LEMBERG  wrote:
>> 
>> 
>> * Has someone coded this already?  I couldn't find code in the LSR.
>> 
> 
> I don't know if this is still the most ideal way, but it works. Someone on 
> this list coded all of this many years ago ... unfortunately, I'm unable to 
> remember who it was to give them proper attribution. I use this snippet all 
> the time to make various brackets in organ music. (The bracket names are my 
> own; I wanted to use something clear & descriptive.) The #s at the end of the 
> lines dictate the size (length) of the brackets. Like any markup, fine-tune 
> the positioning of the brackets with something like \once \override 
> TextScript.Y-offset = #5
> 
> The only drawback is when there is competing markup which needs to be 
> positioned separately ... getting that worked out takes some creativity.
> 
> Hope this helps.
> 
> — Dan
> 
> 
> \version "2.23.6"
> 
> %%% SINGLE BRACKET SNIPPET: 
> 
> #(define-markup-command (topNotchOpenBracket layout props heitgh) (number?)
>  (interpret-markup layout props
>(markup #:line (#:with-dimensions (cons 0 0) (cons 0 0)
>  (#:path 0.25
>(list (list (quote moveto) 0 0)
>(list (quote lineto) -1 0)
>(list (quote lineto) -1 (* heitgh -1))
>(list (quote lineto) -1 (* heitgh -1
> 
> #(define-markup-command (bottomNotchOpenBracket layout props heitgh) (number?)
>  (interpret-markup layout props
>(markup #:line (#:with-dimensions (cons 0 0) (cons 0 0)
>  (#:path 0.25
>(list (list (quote moveto) -1 0)
>(list (quote lineto) -1 0)
>(list (quote lineto) -1 (* heitgh -1))
>(list (quote lineto) 0 (* heitgh -1
> 
> #(define-markup-command (topNotchCloseBracket layout props heitgh) (number?)
>  (interpret-markup layout props
>(markup #:line (#:with-dimensions (cons 0 0) (cons 0 0)
>  (#:path 0.25
>(list (list (quote moveto) 1.3 0)
>(list (quote lineto) 2.3 0)
>(list (quote lineto) 2.3 (* heitgh -1))
>(list (quote lineto) 2.3 (* heitgh -1
> 
> #(define-markup-command (bottomNotchCloseBracket layout props heitgh) 
> (number?)
>  (interpret-markup layout props
>(markup #:line (#:with-dimensions (cons 0 0) (cons 0 0)
>  (#:path 0.25
>(list (list (quote moveto) 2.3 0)
>(list (quote lineto) 2.3 0)
>(list (quote lineto) 2.3 (* heitgh -1))
>(list (quote lineto) 1.3 (* heitgh -1
> 
> #(define-markup-command (openBracket layout props heitgh) (number?)
>  (interpret-markup layout props
>(markup #:line (#:with-dimensions (cons 0 0) (cons 0 0)
>  (#:path 0.25
>(list (list (quote moveto) 0 0)
>(list (quote lineto) -1 0)
>(list (quote lineto) -1 (* heitgh -1))
>(list (quote lineto) 0 (* heitgh -1
> 
> #(define-markup-command (closeBracket layout props heitgh) (number?)
>  (interpret-markup layout props
>(markup #:line (#:with-dimensions (cons 0 0) (cons 0 0)
>  (#:path 0.25
>(list (list (quote moveto) 1.3 0)
>(list (quote lineto) 2.3 0)
>(list (quote lineto) 2.3 (* heitgh -1))
>(list (quote lineto) 1.3 (* heitgh -1
> 
> \score {
>  \new Staff { \relative c' {
>a4_\markup\openBracket #6 
>a4^\markup\closeBracket #6
>s4
>4^\markup\topNotchOpenBracket #7
>s4
>4^\markup\topNotchCloseBracket #6 
>s4
>4^\markup\bottomNotchOpenBracket #8
>s4
>4^\markup\bottomNotchCloseBracket #6
>   }
>  }
> }
> 
> 

LilyPond 2.23.6 *-tmp-* files

[Jacques Menu]

Hello folks,

I get such temp files:

jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxmlfiles > ll Anacrusis*
600 -rw-r--r--  1 jacquesmenu  staff  303764 May 31 17:42:40 2022 
Anacrusis-tmp-5978322
  8 -rw-r--r--@ 1 jacquesmenu  staff2100 May 31 17:42:33 2022 Anacrusis.ly
  8 -rw-r--r--  1 jacquesmenu  staff 237 May 31 17:42:40 2022 Anacrusis.midi
 88 -rw-r--r--  1 jacquesmenu  staff   41440 May 31 17:42:40 2022 Anacrusis.pdf

The one above starts with:

%!PS-Adobe-3.0
%%Creator: LilyPond 2.23.5
%%Pages: 1
%%PageOrder: Ascend
%%Orientation: Portrait
%%DocumentMedia: a4 595.28 841.89 80 () ()
%%DocumentSuppliedResources: font C059-Bold
%%DocumentSuppliedResources: font C059-Roman
%%DocumentSuppliedResources: font Emmentaler-20
%%EndComments
%%BeginProlog

Is there a way to avoid keeping these files? lilypond doesn’t have an option 
for that AFAICT.

Thanks for your help!

JM

Re: Stanzas with different rhythms

[Jacques Menu]

Thanks Helge, quite elegant!

JM

> Le 21 mai 2022 à 18:46, Helge Kruse  a écrit :
> 
>  Weitergeleitete Nachricht 
> Betreff:  Re: Stanzas with different rythms
> Datum:Fri, 20 May 2022 13:01:10 -0600
> Von:  Carl Sorensen 
> An:   Helge Kruse 
> 
> 
> My way of doing it (based on the way it is done in the hymnals with
> which I am most familiar) is not to use small notes, but instead to use
> dashed ties.
> 
> \version "2.19.80"
> 
> \paper {
>ragged-right = ##f
> }
> 
> % First stanza with correct rythm.
> stanzaOneRhythm = \relative c' {
>\time 6/4
>\partial 4
>e4 |
>a2 a4  e4. 8 4 |
>f2. c2 4 |
>d2 e4 f2 d4
> }
> stanzaOneLyrics = \lyricmode {
>Es war ein Kö -- nig in Thu -- le gar treu bis an das
> }
> 
> % Second stanza omitted
> % Third stanza with correct rythm.
> stanzaThreeRhythm = \relative c' {
>\time 6/4
>\partial 4
>e4 |
>a2 a4 e2 4 |
>f2. c2 4 |
>d2 \autoBeamOff e8 8 f2 d4
> }
> stanzaThreeLyrics = \lyricmode {
>Und als er kam zu ster -- ben, zählt er sei -- ne Städt im
> }
> 
> displayedRhythm =  \relative c' {
>\time 6/4
>\partial 4
>e4 |
>a2 a4 \tieDashed e4.~8 \tieSolid 4 |
>f2. c2 4 |
>d2 \autoBeamOff \tieDashed e8~8 \tieSolid f2 d4
> }
> 
> <<
>   \new Staff <<
> \new Voice = "displayed" {\displayedRhythm}
> \new NullVoice = "stanzaOne" {\stanzaOneRhythm}
> \new NullVoice = "stanzaThree" {\stanzaThreeRhythm}
>   >>
>   \new Lyrics {
> \lyricsto "stanzaOne" \stanzaOneLyrics
>   }
>   \new Lyrics {
> \lyricsto "stanzaThree" \stanzaThreeLyrics
>   }
> >>
> 
> HTH,
> 
> %%%
> 
> Yes, indeed it helps.
> 
> The idea with the NullVoice and independent rhythms is great. All in
> all, there are 6 stanzas with 5 rhythm variants because of the diffent
> numbers of syllables. Defining one displayed voice with the (potential)
> shorter notes and individual rhythms for the stanzas gives me a very
> good replication of the original score.
> 
> That's also the reason I don't want to use the dashed tie. Probably it
> is a more readable form for rhythm variations in songs. But since I'm
> unexperience with songs, I try to keep near the original.
> 
> Thanks,
> Helge
> 
> Carl
> 
> 

Re: Jazz font and 2.23.6

[Jacques Menu]

Thanks Jean for marks formatting.

That leaves the font problem in 2.23.6 open.

JM

> Le 14 mai 2022 à 17:14, Jean Abou Samra  a écrit :
> 
> 
> 
> Le 14/05/2022 à 17:10, Jacques Menu a écrit :
>> Hello Jean,
>> 
>> Sorry, my example wasn’t overly minimal…
>> 
>> Here is one, attached.
>> 
>> JM
> 
> 
> OK, so it's an issue in 2.22, not in 2.23.6. That's expected: markFormatter 
> was renamed to rehearsalMarkFormatter. If you "backport" a 2.23.6 file to 
> 2.22, you need to change it back.
> 
> Best,
> Jean
> 

Re: Jazz font and 2.23.6

[Jacques Menu]

Hello Jean,

Sorry, my example wasn’t overly minimal…

Here is one, attached.

JM

\version “2.23.6":


\version “2.22.0”:





JazzFontProblem.ly
Description: Binary data

Re: Jazz font and 2.23.6

[Jacques Menu]

Another issue with 2.23.6 is that:

  \set Score.rehearsalMarkFormatter = #format-mark-box-letters

is ignored.

JM

> Le 14 mai 2022 à 09:00, Jacques Menu  a écrit :
> 
> Hello folks,
> 
> I have posted recently about a Jazz font problem, in which the chords names 
> didn’t use it. I’ve noticed since that bes was not output correctly, by the 
> way:
> 
> 
> 
> This is no Jazz font issue actually, since using \version “2.22.0” instead of 
> \version “2.23.6” gives correct results:
> 
> 
> Hope this helps!
> 
> JM
> 
> 
> 

Re: ANN: Frescobaldi 3.2

[Jacques Menu]

About Frescobaldi displays the version number as 3.1.3.

JM

> Le 5 mai 2022 à 16:31, Jacques Menu  a écrit :
> 
> Hello everybody,
> 
> Thanks Harban and Davide for the help.
> 
> Installing from MacPorts actually creates /opt/local/bin/frescobaldi, but 
> also:
> 
> jacquesmenu@macmini: /Applications/MacPorts > ls -sal
> total 24
>  0 drwxr-xr-x  10 jacquesmenu  admin   320 May  5 10:00 .
>  0 drwxrwxr-x  61 root admin  1952 May  5 09:50 ..
> 24 -rw-r--r--@  1 jacquesmenu  admin  8196 May  5 16:22 .DS_Store
>  0 drwxr-xr-x   3 jacquesmenu  admin96 Apr  3  2021 FontForge.app
>  0 drwxr-xr-x   3 root admin96 May  5 10:00 Frescobaldi.app
>  0 drwxr-xr-x   5 jacquesmenu  admin   160 Nov  6 23:13 Python 2.7
>  0 drwxr-xr-x   4 root admin   128 Apr  2 15:00 Python 3.10
>  0 drwxr-xr-x   5 jacquesmenu  admin   160 Nov  6 23:13 Python 3.8
>  0 drwxr-xr-x   5 jacquesmenu  admin   160 Nov  6 23:13 Python 3.9
>  0 drwxr-xr-x   8 root admin   256 May  5 09:56 Qt5
> 
> I didn’t know that.
> 
> Launching Frescobaldi.app from the Finder works as expected, with the 
> Preferences menu item under Frescobaldi.
> 
> There is a symptom that occurs sometimes with the 3.1.3 version: cliking on a 
> menu header  displays the menu’s contents, but hides it right away before any 
> item can be clicked on.
> 
> With 3.2, click followed by click-and-hold keeps the menu contents accessible 
> so as to select an item.
> 
> JM
> 
>> Le 5 mai 2022 à 15:31, Davide Liessi > <mailto:davide.lie...@gmail.com>> a écrit :
>> 
>> Dear Mario,
>> 
>> Il giorno gio 5 mag 2022 alle ore 15:25 Mario Bolognani
>> mailto:mario.bologn...@gmail.com>> ha scritto:
>>> many thanks for updating Frescobaldi but an inexperienced user like me gets 
>>> lost into the tricky steps fo obtaining a .dmg package to install as in 
>>> version 3.1.3.
>> 
>> the standalone .app bundle for Mac, distributed as .dmg package, has
>> not been prepared yet.
>> I'll try to do it soon, although there may be some difficulties (see
>> my answer to Omer Katzir
>> https://lists.gnu.org/archive/html/lilypond-user/2022-05/msg00065.html 
>> <https://lists.gnu.org/archive/html/lilypond-user/2022-05/msg00065.html>
>> a few minutes ago).
>> 
>> Best wishes.
>> Davide
>> 
> 

Re: ANN: Frescobaldi 3.2

[Jacques Menu]

Hello everybody,

Thanks Harban and Davide for the help.

Installing from MacPorts actually creates /opt/local/bin/frescobaldi, but also:

jacquesmenu@macmini: /Applications/MacPorts > ls -sal
total 24
 0 drwxr-xr-x  10 jacquesmenu  admin   320 May  5 10:00 .
 0 drwxrwxr-x  61 root admin  1952 May  5 09:50 ..
24 -rw-r--r--@  1 jacquesmenu  admin  8196 May  5 16:22 .DS_Store
 0 drwxr-xr-x   3 jacquesmenu  admin96 Apr  3  2021 FontForge.app
 0 drwxr-xr-x   3 root admin96 May  5 10:00 Frescobaldi.app
 0 drwxr-xr-x   5 jacquesmenu  admin   160 Nov  6 23:13 Python 2.7
 0 drwxr-xr-x   4 root admin   128 Apr  2 15:00 Python 3.10
 0 drwxr-xr-x   5 jacquesmenu  admin   160 Nov  6 23:13 Python 3.8
 0 drwxr-xr-x   5 jacquesmenu  admin   160 Nov  6 23:13 Python 3.9
 0 drwxr-xr-x   8 root admin   256 May  5 09:56 Qt5

I didn’t know that.

Launching Frescobaldi.app from the Finder works as expected, with the 
Preferences menu item under Frescobaldi.

There is a symptom that occurs sometimes with the 3.1.3 version: cliking on a 
menu header  displays the menu’s contents, but hides it right away before any 
item can be clicked on.

With 3.2, click followed by click-and-hold keeps the menu contents accessible 
so as to select an item.

JM

> Le 5 mai 2022 à 15:31, Davide Liessi  a écrit :
> 
> Dear Mario,
> 
> Il giorno gio 5 mag 2022 alle ore 15:25 Mario Bolognani
>  ha scritto:
>> many thanks for updating Frescobaldi but an inexperienced user like me gets 
>> lost into the tricky steps fo obtaining a .dmg package to install as in 
>> version 3.1.3.
> 
> the standalone .app bundle for Mac, distributed as .dmg package, has
> not been prepared yet.
> I'll try to do it soon, although there may be some difficulties (see
> my answer to Omer Katzir
> https://lists.gnu.org/archive/html/lilypond-user/2022-05/msg00065.html
> a few minutes ago).
> 
> Best wishes.
> Davide
> 

Re: ANN: Frescobaldi 3.2

[Jacques Menu]

Hello Hraban,

Yes, it did work, but with SimpleSynth, though, which is running alright on my 
machine.

JM

> Le 5 mai 2022 à 10:33, Henning Hraban Ramm  a écrit :
> 
> Am 05.05.22 um 10:13 schrieb Jacques Menu:
>> Hello Wilbert,
>> Thanks to you and to the people that contribute for everything you do for us!
>> I’ve installed Frescobaldi 3.2 with MacPorts on Mac OS Monterey (12.3.1), 
>> and the first tests show it works fine.
>> One problem, though: it’s name is displayed as “Python” in the menu bar, 
> 
> That’s normal if you start a Python program from the command line.
> 
>> and there’s no Preferences item. How can I set the MIDI output channel to 
>> hear the score being played?
> 
> Did it work for you in previous releases? You must install and start 
> freesynth/Qsynth, too.
> 
> Hraban
> 

Re: ANN: Frescobaldi 3.2

[Jacques Menu]

Just notices I get this message upon launch:

qt.qpa.fonts: Populating font family aliases took 118 ms. Replace uses of 
missing font family "Century Schoolbook L" with one that exists to avoid this 
cost. 

JM

> Le 5 mai 2022 à 10:13, Jacques Menu  a écrit :
> 
> Hello Wilbert,
> 
> Thanks to you and to the people that contribute for everything you do for us!
> 
> I’ve installed Frescobaldi 3.2 with MacPorts on Mac OS Monterey (12.3.1), and 
> the first tests show it works fine.
> 
> One problem, though: it’s name is displayed as “Python” in the menu bar, and 
> there’s no Preferences item. How can I set the MIDI output channel to hear 
> the score being played?
> 
> Thanks for your help!
> 
> JM
> 
>> Le 5 mai 2022 à 09:18, Martín Rincón Botero > <mailto:martinrinconbot...@gmail.com>> a écrit :
>> 
>> "Why the name? It’s short, sounds like ‘parse’, and has the meaning of 
>> “friend”, “buddy”, “bro.” :-)"
>> 
>> As a Colombian, I approve, parce ;-).
>> 
>> www.martinrinconbotero.com <http://www.martinrinconbotero.com/>
>> 
>> 
>>> On May 5, 2022 at 7:44 AM, mailto:w...@xs4all.nl>> 
>>> wrote:
>>> 
>>> Dear Friends,
>>> 
>>> Lots of people contributed to this new release of Frescobaldi 3.2,
>>> which actually has been in the works for quite a long time. Thanks!!
>>> Recently it became urgent to fix various issues that arose in
>>> Frescobaldi (and many programs that use Python-Qt bindings) with Python
>>> 3.10, where you no longer can give a floating point value to a function
>>> that requires an integer. Python releases are so quick :-)
>>> 
>>> So hopefully this new release[1] fixes those annoyances. But it brings
>>> also some nice new features; see for an overview[2]:
>>> 
>>> [1] https://github.com/frescobaldi/frescobaldi/releases/tag/v3.2 
>>> <https://github.com/frescobaldi/frescobaldi/releases/tag/v3.2>
>>> [2] https://github.com/frescobaldi/frescobaldi/blob/v3.2/ChangeLog 
>>> <https://github.com/frescobaldi/frescobaldi/blob/v3.2/ChangeLog>
>>> 
>>> Note that there is a dependency change: the qpageview module, thus far
>>> in frescobaldi_app/qpageview, is now, because of its generic nature, a
>>> separate project at http://qpageview.org/ <http://qpageview.org/> . This 
>>> package needs to be
>>> installed for Frescobaldi to work; it is used by the Music View and
>>> other viewers inside Frescobaldi. Because of this, be sure to remove
>>> Frescobaldi completely and then install qpageview and Frescobaldi,
>>> otherwise it still finds the old qpageview inside the frescobaldi_app
>>> folder.
>>> 
>>> In the meantime I worked on two new Python packages: parce[3] and
>>> quickly[4], which together will supersede python-ly. In the future they
>>> will help Frescobaldi with an even more thorough musical understanding
>>> of the LilyPond source text, making (probably) more interesting music
>>> manipulations possible.
>>> 
>>> [3] https://parce.info/ <https://parce.info/>
>>> [4] https://quick-ly.info/ <https://quick-ly.info/>
>>> 
>>> Enjoy!
>>> 
>>> --  
>>> Wilbert Berendsen (www.wilbertberendsen.nl 
>>> <http://www.wilbertberendsen.nl/>)
>>> 
>> 
> 

Re: ANN: Frescobaldi 3.2

[Jacques Menu]

Hello Wilbert,

Thanks to you and to the people that contribute for everything you do for us!

I’ve installed Frescobaldi 3.2 with MacPorts on Mac OS Monterey (12.3.1), and 
the first tests show it works fine.

One problem, though: it’s name is displayed as “Python” in the menu bar, and 
there’s no Preferences item. How can I set the MIDI output channel to hear the 
score being played?

Thanks for your help!

JM

> Le 5 mai 2022 à 09:18, Martín Rincón Botero  a 
> écrit :
> 
> "Why the name? It’s short, sounds like ‘parse’, and has the meaning of 
> “friend”, “buddy”, “bro.” :-)"
> 
> As a Colombian, I approve, parce ;-).
> 
> www.martinrinconbotero.com 
> 
> 
>> On May 5, 2022 at 7:44 AM, mailto:w...@xs4all.nl>> wrote:
>> 
>> Dear Friends,
>> 
>> Lots of people contributed to this new release of Frescobaldi 3.2,
>> which actually has been in the works for quite a long time. Thanks!!
>> Recently it became urgent to fix various issues that arose in
>> Frescobaldi (and many programs that use Python-Qt bindings) with Python
>> 3.10, where you no longer can give a floating point value to a function
>> that requires an integer. Python releases are so quick :-)
>> 
>> So hopefully this new release[1] fixes those annoyances. But it brings
>> also some nice new features; see for an overview[2]:
>> 
>> [1] https://github.com/frescobaldi/frescobaldi/releases/tag/v3.2
>> [2] https://github.com/frescobaldi/frescobaldi/blob/v3.2/ChangeLog
>> 
>> Note that there is a dependency change: the qpageview module, thus far
>> in frescobaldi_app/qpageview, is now, because of its generic nature, a
>> separate project at http://qpageview.org/ . This package needs to be
>> installed for Frescobaldi to work; it is used by the Music View and
>> other viewers inside Frescobaldi. Because of this, be sure to remove
>> Frescobaldi completely and then install qpageview and Frescobaldi,
>> otherwise it still finds the old qpageview inside the frescobaldi_app
>> folder.
>> 
>> In the meantime I worked on two new Python packages: parce[3] and
>> quickly[4], which together will supersede python-ly. In the future they
>> will help Frescobaldi with an even more thorough musical understanding
>> of the LilyPond source text, making (probably) more interesting music
>> manipulations possible.
>> 
>> [3] https://parce.info/
>> [4] https://quick-ly.info/
>> 
>> Enjoy!
>> 
>> --  
>> Wilbert Berendsen (www.wilbertberendsen.nl)
>> 
> 

Re: Layout issues in the jazz chord chart

[Jacques Menu]

Hello Gdaliy,Maybe this example helps.JM

LilyJazzTest.ly
Description: Binary data
Le 3 mai 2022 à 12:33, Gdaliy Garmiza  a écrit :I have found the answer to my third question:\markup \vspace #1I will be grateful for the help with the rest!-- Forwarded message -От: Gdaliy Garmiza Date: вт, 3 мая 2022 г. в 01:47Subject: Re: Layout issues in the jazz chord chartTo:  Sorry, here is the link to the files:https://drive.google.com/drive/folders/100IltqniC0fSsmcWvhIdPqTqVBurgAfY?usp=sharingвт, 3 мая 2022 г. в 01:34, Gdaliy Garmiza :Hello, everybody!I'm developing an app for my jazz educational project, which helps me to automate a lot of routine. It uses lilypond for rendering scores. I have recently added the export chord chart feature, and I attach an example of its output to this email in *.ly and in *.png. Though it doesn't look bad to me, I would like it to be a little closer to the similar output, generated by such software as iRealPro or Band-in-a-Box. Here are the questions:1. Is it possible to add the bar lines at the beginning of each line?I have tried with no result:\layout {\context {\Score\override SystemStartBar #'collapse-height = #5}\context {\ChordNames\consists "System_start_delimiter_engraver"}}2. Is it possible to make the measure widths equal or at least more aligned to each other so that they would look snapped to the vertical grid?The following code, which works in general, but the result is not perfect:\context {\ScoreproportionalNotationDuration = #(ly:make-moment 1 16)\override SpacingSpanner.uniform-stretching = ##t\override SpacingSpanner.strict-note-spacing = ##t\override SpacingSpanner.base-shortest-duration = #(ly:make-moment 1/16)}3. To add some space below the header(s)/title(s), I use the transparent text of the needed size:\markup \fontsize #7 \fill-line \transparent {space}This works, but the code looks a bit like a hack. Is there a more straightforward way to do this :-)?Many thanks in advance!Best,G.

Re: Having trouble with Coda sign placement

[Jacques Menu]

Hello Kenneth,

Does the attached example help you?

JM



CodaStartingInTheMiddleOfALineExample.ly
Description: Binary data


> Le 28 avr. 2022 à 23:51, Kenneth Wolcott  a écrit :
> 
> Hi;
> 
>   I am engraving a piece of music which has additional explanations
> of Coda and D.S. al Coda (etc)  which complicates the matter greatly.
> 
>  I have attached screenshots of the original (too big for the entire
> thing since it is a set of concatenated camera photos), my engraving
> and my Lilypond source.
> 
>  It would be easier to just not engrave the explanation parts, but
> I'd like to learn how to fix this, to be as faithful as possible to
> the origin.
> 
>  I did try a tweak to force the reversed position of the coda sign
> and the coda text, but I did not do that correctly, as Lilypond
> complained.  I can provide that output from Lilypond if needed.
> 
> Thanks,
> Ken Wolcott
> 

Re: Snippet

[Jacques Menu]

THANKS A LOT, Jean, that’s precisely what I’ve been struggling with for xml2ly 
these days…, solved!

I’ll use your solution this way:

\score {
  \context Staff = "staff1" {
c1
\mergeFullBarRests {
  \compressEmptyMeasures
  R1  R1  R1 % NO '|' bar mark here!
  \bar "||"
  | % bar mark is optional here
}
  }
}

JM

> Le 22 avr. 2022 à 09:35, Martín Rincón Botero  
> a écrit :
> 
> Thank you!
> 
> On abr. 21 2022, at 9:10 pm, Jean Abou Samra  wrote:
> Le 21/04/2022 à 19:50, Martín Rincón Botero a écrit :
> > Would it be possible to update it to work on Lilypond 2.22.1?
> 
> 
> The code contains spurious Unicode "zero-width space" characters, one among
> the newlines between the end of append-merge and "mergeSkips =", and another
> between the end of \mergeFullBarRests and \score. Try removing these.
> Updated
> snippet:
> 
> \version "2.22.2"
> 
> #(define (append-merge x l r)
> "Add x to the head of list l, merging skips,
> and if r is true also merging full measure rests."
>   (if (and (pair? l)
>(ly:music? x)
>(ly:music? (car l))
>(or (and (music-is-of-type? x 'skip-event)
> (music-is-of-type? (car l) 'skip-event))
>(and r
> (music-is-of-type? x 'multi-measure-rest)
> (music-is-of-type? (car l) 'multi-measure-rest)))
>(not (pair? (ly:music-property (car l) 'articulations
>  (let ((total
> (ly:moment-add
> (ly:music-duration-length (car l))
> (ly:music-duration-length x)
> )))
>(set! (ly:music-property x 'duration)
>   (make-duration-of-length total))
>(cons x (cdr l)))
> (cons x l)))
> 
> mergeSkips = #(define-music-function
>  (parser location rests-also music) ((boolean?) ly:music?)
>  "Merge successive skips in sequential music,
>   optionally merge full-measure rests as well."
>  (music-map
>(lambda (m)
>   (if (music-is-of-type? m 'sequential-music)
> (ly:music-set-property! m
>'elements
>(fold-right (lambda (x l)
>  (append-merge x l rests-also))
>  '()
>  (ly:music-property m 'elements
>  m)
>music))
> 
> mergeFullBarRests = #(define-music-function
>  (parser location music) (ly:music?)
>  #{ \mergeSkips ##t $music #})
> 
> \score {
>   \mergeFullBarRests {
> \context Staff = "staff1" {
>   \compressEmptyMeasures
>   c1 R1 R1 R1
> }
>   }
>   }
> 
> 
> Best,
> Jean
> 

Re: Musical questions

[Jacques Menu]

Thanks Hans!

JM

> Le 13 avr. 2022 à 10:10, Hans Åberg  a écrit :
> 
> 
>> On 11 Apr 2022, at 16:16, Jacques Menu  wrote:
>> 
>> Hello folks,
>> 
>> In Mendelssohn Bartholdy’s Ave maris stella, the soprano has this:
>> 
>> 
>> 
>> With LilyPond, I can obtain the ad lib cue notes with smaller note heads in 
>> a cadenza. Is that my best bet?
>> 
>> Also, what is the musicial signification of the ligatures above the staff?
> 
> Another score does not have them, so it might be (incorrect) phrase marks 
> added by the editor.
> 

Re: Musical questions

[Jacques Menu]

Thanks Simon!

JM

> Le 11 avr. 2022 à 17:31, Simon Albrecht  a écrit :
> 
> Hi Jacques,
> 
> On 11/04/2022 16:16, Jacques Menu wrote:
>> Also, what is the musical meaning of the ligatures above the staff?
> 
> 
> these are not standard notation and it’s impossible to tell. Maybe the larger 
> context might give some hint, but most likely you’d need an explanation in 
> foreword or critical apparatus (looks like a fairly recent edition…).
> 
> Best, Simon
> 

Re: Musical questions

[Jacques Menu]

Thanks Knute!

> Le 11 avr. 2022 à 16:37, Knute Snortum  a écrit :
> 
> On Mon, Apr 11, 2022 at 7:27 AM Jacques Menu  wrote:
>> 
>> Hello folks,
>> 
>> In Mendelssohn Bartholdy’s Ave maris stella, the soprano has this:
>> 
>> 
>> With LilyPond, I can obtain the ad lib cue notes with smaller note heads in 
>> a cadenza. Is that my best bet?
> 
> I would use \magnifyMusic #2/3 {  %{ cue notes here %} } in the cadenza.

Musical questions

[Jacques Menu]

Hello folks,

In Mendelssohn Bartholdy’s Ave maris stella, the soprano has this:



With LilyPond, I can obtain the ad lib cue notes with smaller note heads in a 
cadenza. Is that my best bet?

Also, what is the musicial signification of the ligatures above the staff?

Thanks for your help!

JM

Re: Lilyjazz font and Score.markFormatter problem with Lily 2.23.6

[Jacques Menu]

Hello Hans,

Installed the fonts from lilyjazz-master as system fonts with FontBook, 
rebooted, but to no avail.
That beats me…

JM

> Le 4 avr. 2022 à 00:07, Hans Aikema  a écrit :
> 
> IIRC on Mac it only works when you install them in the system fonts. Fontbook 
> installs them in the user-fonts.
> 
>> On 3 Apr 2022, at 23:33, Jacques Menu  wrote:
>> 
>> Hello Xavier,
>> 
>> Thanks for the suggestion!
>> 
>> Here are the LilyJAZZ fonts available to LilyPond:
>> 
>> jacquesmenu@macmini: ~/Desktop > lilypond -dshow-available-fonts  > 
>> lilypond_available_fonts.txt 2>&1
>> 
>> jacquesmenu@macmini: ~/Desktop > grep LilyJAZZ lilypond_available_fonts.txt 
>> family LilyJAZZ-Brace
>>  LilyJAZZ\-Brace:style=Brace
>> family LilyJAZZ-11
>>  LilyJAZZ\-11:style=11
>> family LilyJAZZ-13
>>  LilyJAZZ\-13:style=13
>> family LilyJAZZ-14
>>  LilyJAZZ\-14:style=14
>> family LilyJAZZ-16
>>  LilyJAZZ\-16:style=16
>> family LilyJAZZ-18
>>  LilyJAZZ\-18:style=18
>> family LilyJAZZ-20
>>  LilyJAZZ\-20:style=20
>> family LilyJAZZ-23
>>  LilyJAZZ\-23:style=23
>> family LilyJAZZ-26
>>  LilyJAZZ\-26:style=26
>> 
>> Adding the fonts from lilyjazz-master to Mac OS’s font book does not change 
>> the output of the   -dshow-available-fonts option shown above.
>> 
>> JM
>> 
>>  lilyjazz-master to Mac
>> 
>> OS’s FontBook does not change the output.
>> 
>>> Le 3 avr. 2022 à 21:48, Xavier Scheuer >> <mailto:x.sche...@gmail.com>> a écrit :
>>> 
>>> On Sun, 3 Apr 2022 at 12:44, Jacques Menu >> <mailto:imj-muz...@bluewin.ch>> wrote:
>>> >
>>> > Hello Knute,
>>> >
>>> > Same result replacing define fonts by direct includes.
>>> 
>>> Hello Jacques,
>>> 
>>> Have you properly installed the fonts lilyjazz-text and lilyjazz-chord on 
>>> your operating system?
>>> Do they appear in the list of fonts obtained via lilypond 
>>> -dshow-available-fonts ?
>>> 
>>> See NR 1.8.3 Fonts
>>> http://lilypond.org/doc/v2.23/Documentation/notation/fonts.html 
>>> <http://lilypond.org/doc/v2.23/Documentation/notation/fonts.html>
>>> 
>>> Cheers,
>>> Xavier
>>> 
>>> -- 
>>> Xavier Scheuer mailto:x.sche...@gmail.com>>
>>> 
>> 

Re: Lilyjazz font and Score.markFormatter problem with Lily 2.23.6

[Jacques Menu]

Hello Xavier,

Thanks for the suggestion!

Here are the LilyJAZZ fonts available to LilyPond:

jacquesmenu@macmini: ~/Desktop > lilypond -dshow-available-fonts  > 
lilypond_available_fonts.txt 2>&1

jacquesmenu@macmini: ~/Desktop > grep LilyJAZZ lilypond_available_fonts.txt 
family LilyJAZZ-Brace
 LilyJAZZ\-Brace:style=Brace
family LilyJAZZ-11
 LilyJAZZ\-11:style=11
family LilyJAZZ-13
 LilyJAZZ\-13:style=13
family LilyJAZZ-14
 LilyJAZZ\-14:style=14
family LilyJAZZ-16
 LilyJAZZ\-16:style=16
family LilyJAZZ-18
 LilyJAZZ\-18:style=18
family LilyJAZZ-20
 LilyJAZZ\-20:style=20
family LilyJAZZ-23
 LilyJAZZ\-23:style=23
family LilyJAZZ-26
 LilyJAZZ\-26:style=26

Adding the fonts from lilyjazz-master to Mac OS’s font book does not change the 
output of the   -dshow-available-fonts option shown above.

JM

 lilyjazz-master to Mac

OS’s FontBook does not change the output.

> Le 3 avr. 2022 à 21:48, Xavier Scheuer  a écrit :
> 
> On Sun, 3 Apr 2022 at 12:44, Jacques Menu  <mailto:imj-muz...@bluewin.ch>> wrote:
> >
> > Hello Knute,
> >
> > Same result replacing define fonts by direct includes.
> 
> Hello Jacques,
> 
> Have you properly installed the fonts lilyjazz-text and lilyjazz-chord on 
> your operating system?
> Do they appear in the list of fonts obtained via lilypond 
> -dshow-available-fonts ?
> 
> See NR 1.8.3 Fonts
> http://lilypond.org/doc/v2.23/Documentation/notation/fonts.html 
> <http://lilypond.org/doc/v2.23/Documentation/notation/fonts.html>
> 
> Cheers,
> Xavier
> 
> -- 
> Xavier Scheuer mailto:x.sche...@gmail.com>>
> 

Re: Lilyjazz font and Score.markFormatter problem with Lily 2.23.6

[Jacques Menu]

Hello Knute,

Same result replacing define fonts by direct includes.

JM

> Le 2 avr. 2022 à 16:30, Knute Snortum  a écrit :
> 
> On Sat, Apr 2, 2022 at 6:21 AM Jacques Menu  wrote:
> [snip]
>> \paper {
>>  #(define fonts
>> (set-global-fonts
>>  #:music "lilyjazz"
>>  #:brace "lilyjazz"
>>  #:roman "lilyjazz-text"
>>  #:sans "lilyjazz-chord"
>>  #:factor (/ staff-height pt 20)
>>  ))
>> }
> 
> Try removing  #(define fonts in the paper block and instead, add this
> near the top of your input file:
> 
> \include "jazzchords.ily"
> \include "lilyjazz.ily"
> \include "jazzextras.ily"
> 
> --
> Knute Snortum

Re: Lilyjazz font and Score.markFormatter problem with Lily 2.23.6

[Jacques Menu]

Hello Knute,

> Le 1 avr. 2022 à 16:31, Knute Snortum  a écrit :
> 
> How did you install the LilyJAZZ fonts?  If you go to this URL...
> 
> https://github.com/OpenLilyPondFonts/lilyjazz 
> 
> 
> ...and click on the green Code button, you can download the fonts as a Zip 
> file.  Unzip it somewhere, then follow the instructions in the 
> LilyPond-Fonts-and -Installation-Guide.txt file.  Note that where you put the 
> fonts must match the version of LilyPond you're using, if you have multiple 
> versions. 

Thanks for the link, much appreciated.

I now have Lily 2.23.6 installed in /Applications/LilyPond/lilypond-2.23.6:,

jacquesmenu@macmini: /Applications/LilyPond/lilypond-2.23.6 > ls -sal bin
total 21576
0 drwxr-xr-x  12 jacquesmenu  staff   384 Feb  7 10:45 .
0 drwxr-xr-x@  9 jacquesmenu  staff   288 Feb  8 17:59 ..
8 -rwxr-xr-x   1 jacquesmenu  staff93 Feb  7 10:45 abc2ly
8 -rwxr-xr-x   1 jacquesmenu  staff97 Feb  7 10:45 convert-ly
8 -rwxr-xr-x   1 jacquesmenu  staff93 Feb  7 10:45 etf2ly
8 -rwxr-xr-x   1 jacquesmenu  staff95 Feb  7 10:45 lilymidi
21504 -rwxr-xr-x   1 jacquesmenu  staff  11009976 Feb  7 10:45 lilypond
8 -rwxr-xr-x   1 jacquesmenu  staff   100 Feb  7 10:45 lilypond-book
8 -rwxr-xr-x   1 jacquesmenu  staff   241 Feb  7 10:45 
lilypond-invoke-editor
8 -rwxr-xr-x   1 jacquesmenu  staff95 Feb  7 10:45 lilysong
8 -rwxr-xr-x   1 jacquesmenu  staff94 Feb  7 10:45 midi2ly
8 -rwxr-xr-x   1 jacquesmenu  staff98 Feb  7 10:45 musicxml2ly

 with the lily jazz fonts files in ‘font’ sub-directory:

jacquesmenu@macmini: /Applications/LilyPond/lilypond-2.23.6 > find . -name 
"*lilyjazz*" -print
./share/lilypond/2.23.6/fonts/svg/lilyjazz-13.svg
./share/lilypond/2.23.6/fonts/svg/lilyjazz-11.svg
./share/lilypond/2.23.6/fonts/svg/lilyjazz-14.svg
./share/lilypond/2.23.6/fonts/svg/lilyjazz-16.svg
./share/lilypond/2.23.6/fonts/svg/lilyjazz-26.svg
./share/lilypond/2.23.6/fonts/svg/lilyjazz-18.svg
./share/lilypond/2.23.6/fonts/svg/lilyjazz-20.svg
./share/lilypond/2.23.6/fonts/svg/lilyjazz-brace.svg
./share/lilypond/2.23.6/fonts/svg/lilyjazz-23.svg
./share/lilypond/2.23.6/fonts/otf/lilyjazz-26.otf
./share/lilypond/2.23.6/fonts/otf/lilyjazz-18.otf
./share/lilypond/2.23.6/fonts/otf/lilyjazz-20.otf
./share/lilypond/2.23.6/fonts/otf/lilyjazz-brace.otf
./share/lilypond/2.23.6/fonts/otf/lilyjazz-23.otf
./share/lilypond/2.23.6/fonts/otf/lilyjazz-13.otf
./share/lilypond/2.23.6/fonts/otf/lilyjazz-11.otf
./share/lilypond/2.23.6/fonts/otf/lilyjazz-14.otf
./share/lilypond/2.23.6/fonts/otf/lilyjazz-16.otf

The default Lilypond in Frescobaldi is:

/Applications/LilyPond/lilypond-2.23.6/bin/lilypond

With:

\paper {
  #(define fonts
 (set-global-fonts
  #:music "lilyjazz"
  #:brace "lilyjazz"
  #:roman "lilyjazz-text"
  #:sans "lilyjazz-chord"
  #:factor (/ staff-height pt 20)
  ))
}

I get:



while I used to get:



Hence my OP...

JM

Re: Lilyjazz font and Score.markFormatter problem with Lily 2.23.6

[Jacques Menu]

Hello Knute,

Your example runs here too, giving:



What I’d like is to have the chord names such Em7 in the lilyjazz font too, 
though.

Thanks if you can help!

JM

> Le 1 avr. 2022 à 02:11, Knute Snortum  a écrit :
> 
>>> Any hint why the chord names don’t use the lilyjazz font?
>>> 
>>> 
> \paper {
> #(define fonts
>(set-global-fonts
> #:music "lilyjazz"
> #:brace "lilyjazz"
> #:roman "lilyjazz-text"
> #:sans "lilyjazz-chord"
> #:chords "lilyjazz-chord"
> 
> You don't need all the fonts defined in the \paper section, and I
> don't think you have needed them since 2.19.11.  The code below works
> for me:
> 
> %%%
> \version "2.23.6"
> 
> \include "jazzchords.ily"
> \include "lilyjazz.ily"
> \include "jazzextras.ily"
> 
> \markup { Some text }
> 
> myChordSequence = \chordmode {
>  \set chordChanges = ##t
>  %\set chordNameExceptions = #chExceptions
>  e2:m7 a:7 | e:m7 a:7 |
> }
> 
> Part_POne_Staff_One_Voice_One = \absolute {
>  \language "nederlands"
> 
>  \set Score.rehearsalMarkFormatter = #format-mark-box-letters
>  %  \set Score.rehearsalMarkFormatter = #format-mark-box-alphabet % pour le 
> "I"
>  \override Score.RehearsalMark.font-size = #+5
>  \textLengthOn
> 
>  \key d \major
> 
>  \mark \default
> 
>  \clef "treble"
>  b'8 [ a' b' a'  ~ ] a' b'4. | % 6
>  \barNumberCheck #2
>  r8 b'4. a'8 b'4. ^\markup {\musicglyph #"scripts.segno" } | % 7
>  \barNumberCheck #3
>  | % 7
> }
> 
> \score {
>  <<
> 
>\new ChordNames \myChordSequence
> 
>\new Staff = "Part_POne_Staff_One"
>\with {
>}
><<
>  \context Voice = "Part_POne_Staff_One_Voice_One" <<
>\Part_POne_Staff_One_Voice_One
>>> 
>>> 
> 
>>> 
> }
> %%%
> 
> --
> Knute Snortum

Re: Lilyjazz font and Score.markFormatter problem with Lily 2.23.6

[Jacques Menu]

> Le 30 mars 2022 à 21:06, Valentin Petzel  a écrit :
> 
> For me changing the font make no problems. You might want to check if you 
> have 
> the relevant font files in the font path. Are you on Linux or Windows? Maybe 
> are some point something about font-config has changed.
> 
> About markFormatter: This one changed to rehearsalMarkFormatter, along with 
> adding formatter options for the all kinds of marks.

Thanks Jean and Valentin, that solves this issue. I’ve probably used an 
outdated convert-ly.

Any hint why the chord names don’t use the lilyjazz font?



>> \paper {
>>  #(define fonts
>> (set-global-fonts
>>  #:music "lilyjazz"
>>  #:brace "lilyjazz"
>>  #:roman "lilyjazz-text"
>>  #:sans "lilyjazz-chord"
>>  #:chords "lilyjazz-chord"
>>  #:factor (/ staff-height pt 20)
>>  ))

JM

Lilyjazz font and Score.markFormatter problem with Lily 2.23.6

[Jacques Menu]

Hello folks,

The setting:

 \set Score.markFormatter = #format-mark-box-letters 

has no effect here from version 2.23 on, see attached

Also, the usual :

\paper {
  #(define fonts
 (set-global-fonts
  #:music "lilyjazz"
  #:brace "lilyjazz"
  #:roman "lilyjazz-text"
  #:sans "lilyjazz-chord"
  #:chords "lilyjazz-chord"
  #:factor (/ staff-height pt 20)
  ))

has no effect on chord names:



Thanks for your help!

JM

--

%%

\version "2.23.6"

\paper {
  #(define fonts
 (set-global-fonts
  #:music "lilyjazz"
  #:brace "lilyjazz"
  #:roman "lilyjazz-text"
  #:sans "lilyjazz-chord"
  #:factor (/ staff-height pt 20)
  ))
}

\markup { Some text }

myChordSequence = \chordmode {
  \set chordChanges = ##t
  %\set chordNameExceptions = #chExceptions
  e2:m7 a:7 | e:m7 a:7 |
}

Part_POne_Staff_One_Voice_One = \absolute {
  \language "nederlands"

  \set Score.markFormatter = #format-mark-box-letters
  %  \set Score.markFormatter = #format-mark-box-alphabet % pour le "I"
  \override Score.RehearsalMark.font-size = #+5
  \textLengthOn

  \key d \major

  \mark \default

  \clef "treble"
  b'8 [ a' b' a'  ~ ] a' b'4. | % 6
  \barNumberCheck #2
  r8 b'4. a'8 b'4. ^\markup {\musicglyph #"scripts.segno" } | % 7
  \barNumberCheck #3
  | % 7
}

\score {
  <<

\new ChordNames \myChordSequence

\new Staff = "Part_POne_Staff_One"
\with {
}
<<
  \context Voice = "Part_POne_Staff_One_Voice_One" <<
\Part_POne_Staff_One_Voice_One
  >>
>>

  >>
}


%%

Re: help

[Jacques Menu]

Hello Felix,

Not clear: what is it you call the lily extension program?

JM

> Le 25 mars 2022 à 17:25, Felix Maude  a écrit :
> 
>  Dear sirs: I'm not able to download lilypond extension , program, i have the 
> windows 10, I keep getting a message can't load is it safe, please inform 
> what I may do to resolve this really need the program.
> 
> Thanks, 
> Philip (928)344-4261

Re: problems with \tempo

[Jacques Menu]

Hello Mario,

The \midi block is your friend:

\book {
  \score {
<<

  \new Staff = "Part_POne_Staff_One"
  \with {
  }
  <<
\context Voice = "Part_POne_Staff_One_Voice_One" <<
  \Part_POne_Staff_One_Voice_One
>>
  >>

>>

\layout {
  \context {
\Score
autoBeaming = ##f % to display tuplets brackets
  }
  \context {
\Voice
  }
}

\midi {
  \tempo 16 = 360
}
  }

}


> Le 16 mars 2022 à 05:08, Mario Bolognani  a écrit :
> 
> I’m using LilyPomd 2.20 with Frescobaldi 3.1.3 on a MacBook M1 with  MacOSX 
> Monterey (last version). With \time 3)1 and \tempo \breve (or breve.) = xx 
> the midi output seems not responding to \tempo changes. Any suggestion?
> 
> Many thanks 
> 
> 
> Mario Bolognani
> mario.bologn...@gmail.com 
> 
> 
> 

Re: Displaying a fake key

[Jacques Menu]

Hello Valentin,

Thanks a lot for the solution!

I thought this markup could be placed right inside the staff, but that would be 
more confusing that useful, so I’ll use that.

A nice w-e!

JM

> Le 11 mars 2022 à 14:04, Valentin Petzel  a écrit :
> 
> Hello Jacques,
> 
> I’m not exactly sure what you want, but maybe something like this?
> 
> Cheers,
> Valentin
> 
> Am Freitag, 11. März 2022, 11:24:11 CET schrieb Jacques Menu:
>> Hello folks,
>> 
>> I’d like to display the following as though it were in C major using
>> \naturalizeMusic from the LSR (https://lsr.di.unimi.it/LSR/Item?id=266),
>> but still display the original key.
>> 
>> 
>> Original:
>> 
>> 
>> 
>> Naturalized, with \key commented out in the Lily code:
>> 
>> 
>> 
>> Is there a way to display the E major key as a markup as a reminder, i.e.
>> without it being taken into accout for the notes display?
>> 
>> Thanks for your help!
>> 
>> JM
> 
> 

Re: DAISY Music Braille Project: Webinar invitation - Introduction to music Braille transcription using the Sao Mai Braille software

[Jacques Menu]

Hello Calvin,

I don’t know, but you can check that with Sarah, who is in charge of the 
Webinar setup. I send the invitation privately.

JM

> Le 3 mars 2022 à 14:08, Calvin Ransom  a écrit :
> 
> Hi JM,
> Will we be able to watch a recording of the webinar? I'm not able to attend 
> it live because that's at 3:00AM local time. 
> 
> Thanks!
> 
> 
> Calvin Ransom

Displaying a fake key

[Jacques Menu]

Hello folks,

I’d like to display the following as though it were in C major using 
\naturalizeMusic from the LSR (https://lsr.di.unimi.it/LSR/Item?id=266), but 
still display the original key.


Original:



Naturalized, with \key commented out in the Lily code:



Is there a way to display the E major key as a markup as a reminder, i.e. 
without it being taken into accout for the notes display?

Thanks for your help!

JM

Re: web page comments

[Jacques Menu]

Hello Rich,

text-to-music toolchain : what is your use case? Creating scores with a 
text-based tool such as LilyPond, or converting existing texts such as MusicXML 
or MEI to scores?

The DAISY consortium (https://daisy.org) is currently financing two projects 
aiming at modern, powerful music scores tools for blind users.
One team is the MuseScore guys, and the other one is the Sao Mai foundation in 
Vietnam.

The latter will present a first demo of its tool in a webinar to held next 
March 1 2022 at 10:00-11:30 UTC, I send you the invitation privately.

A nice day!

JM

> Le 10 mars 2022 à 20:04, Jean Abou Samra  a écrit :
> 
> Hi Rich,
> 
> Le 10/03/2022 à 19:01, Rich Morin a écrit :
>> I just found out about LilyPond today and find it very interesting.  
>> However, I have a few issues to raise about the web site in general and the 
>> landing page in particular.
>> 
>> Looking over the site, I ran into a large number of very pretty graphics 
>> that demonstrate LilyPond's input and output formats.  Unfortunately, these 
>> would be completely inaccessible to blind users.  So, I'd like there to be 
>> some sort of accommodation made to give these users a way to understand what 
>> is being shown.
> 
> 
> The thing is, nobody in the current development team is blind.
> Thus it is difficult to know how a blind person will perceive
> the website. If you have detailed suggestions of how to improve
> it, they will be welcome on the bug-lilypond mailing list
> (http://lilypond.org/bug-reports.html). Even better, of course,
> would be to make the changes yourself and propose them as a
> source code patch (see
> http://lilypond.org/doc/v2.23/Documentation/contributor/working-with-source-code).
> 
> 
>> I'd also like the landing page to mention LilyPond's ability to generate 
>> MIDI files, etc.  Looking at the page, one could easily get the impression 
>> that it is only useful for generating scores.  However, it appears that it 
>> could easily be used as part of a text-to-music toolchain, which could be of 
>> interest to both blind and sighted users.
> 
> 
> To be honest, MIDI generation is not really LilyPond's forte.
> It works, but the audio rendering is not stellar, and not very
> customizable at the moment. Thus I would be a bit hesitating
> to put it forward on the website before it improves, as the
> graphical output is what LilyPond is most good at.
> 
> 
>> Finally, although I was able to find some discussion in various mailing 
>> lists about using braille with LilyPond, I couldn't find any official web 
>> pages on the topic.  This seems like a deficiency that should be addressed.
> 
> 
> What kind of usage do you mean? LilyPond itself has no dedicated
> support for Braille, but some external tools do. CCing Jacques
> who will certainly be able to tell you more about that.
> 
> Best,
> Jean
> 

Fwd: DAISY Music Braille Project: Webinar invitation - Introduction to music Braille transcription using the Sao Mai Braille software

[Jacques Menu]

Hello tutti,

Here is a first presentation of one of the two current projects aiming at a 
powerful tool for Braille music writing.

Sao Mai is a foundation in Vietnam, the other project is being done by the 
MuseScore team.

JM

> Début du message réexpédié :
> 
> De: Sarah Morley Wilkins  >
> Objet: DAISY Music Braille Project: Webinar invitation - Introduction to 
> music Braille transcription using the Sao Mai Braille software
> Date: 3 mars 2022 à 13:46:27 UTC+1
> À: "music-brai...@daisy.org " 
> mailto:music-brai...@daisy.org>>
> 
> Webinar Invitation: Introduction to music Braille transcription using the Sao 
> Mai Braille software for blind musicians and transcribers
>  
> Date and time:
> Thursday 17 March 2022, 10:00-11:30 UTC.
>  
> Description:
> We are happy to announce our upcoming webinar, introducing the Braille 
> translation features of Sao Mai Braille (SMB) software, with a special focus 
> on music Braille transcription. The tool is designed for use by blind 
> musicians as well as transcribers.
> 
> Organizers:
> This webinar is jointly organized by Sao Mai Center for the Blind and the 
> DAISY Music Braille project (which is funding the music Braille development). 
> For more information about the DAISY Music Braille project, please visit: 
> https://daisy.org/activities/projects/music-braille/ 
> 
> 
> Registration:
> Please complete the registration form at 
> https://us06web.zoom.us/webinar/register/WN_D8Le0FHRQr6IcrT1Oovo3w 
> 
> to register for the webinar and to receive joining instructions. If you have 
> any registration problems, please email us at: supp...@saomaicenter.org 
> 
> 
> Overview of event:
> Participants will get a quick tour of the main Braille translation features 
> of SMB, with a more detailed demonstration of how to transcribe music scores 
> into Braille using SMB. In addition, in the Q session we will be able to 
> answer your specific questions about the translation tool.
> 
> Speakers:
> • Dr. Sarah Morley Wilkins (DAISY Music Braille Project Manager),
> • Mr. Hu Haipeng (Technical Consultant of the DAISY Music Braille project), 
> and
> • Mr. Phúc Hoai Dang (SMB development team lead from Sao Mai Center for the 
> Blind).
> 
> Please help circulate the announcement to your network, especially to people 
> who are working in music Braille translation.
> 
> Many thanks and we look forward to meeting you in the webinar.

Re: musicxml2ly in python

[Jacques Menu]

Hello Sebastian,This can also be done with a make file, but maybe that is not your use case. Doing so offers means to place the generated files in sub-folders and to remove them seamlessly. Also, only the .xml files modified or created since the last ‘make’ execution are converted.Attached is an example Makefile, which I use to convert all the .xml files in a folder with my xml2ly.It can be used with musicxml2ly too: drop this Makefile in the given folder and use it as shown below. ‘OPTIONS=...‘ is neccesary in this case because there is otherwise a default ‘-q’ (quiet) to be used by xml2ly. It can be as simple as  ‘OPTIONS=‘.HTH!JM—jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxmlfiles/keys > make helpMakefile for converting MusicXML files to LilyPond scores.Supplied as part of the MusicFormats library, thanks to Dom Fober for providing it.Output files are written in sub-folders of the current folder.Available targets are:  'all' (default) : call the 'lily' target.  'lily'          : converts the set of MusicXML files to lilypond in folder   'pnglily'       : converts the output of 'lily' target to png in folder pnglily  'pdflily'       : converts the output of 'lily' target to pdf in folder pdflily  'midilily'      : converts the output of 'lily' target to pdf in folder midilily  'clean'         : removes the sub-folders containing the resultsOptions:  'XML2LY=/path/to/xml2ly  'OPTIONS=...  'LILYPOND=/path/to/lilypond  When those options are not specified, the tools are taken from the current PATH variable,  and OPTIONS contains '-q' (quiet mode) for xml2ly.jacquesmenu@macmini: ~/musicformats-git-dev/files/musicxmlfiles/keys > make XML2LY=musicxml2ly OPTIONS=--midiXML2LY   = musicxml2lyOPTIONS  = --midiLILYPOND = /Applications/LilyPond/lilypond-2.23.6/bin/lilypondmusicxml2ly version is: musicxml2ly (LilyPond) 2.22.1lilypond version is: GNU LilyPond 2.23.6 (running Guile 2.2)musicxml2ly --midi -o "lilypond/HumdrumScotKeys.ly" "HumdrumScotKeys.xml"musicxml2ly: Reading MusicXML from HumdrumScotKeys.xml ...musicxml2ly: Converting to LilyPond expressions...musicxml2ly: Output to `lilypond/HumdrumScotKeys.ly'musicxml2ly: Converting to current version (2.22.1) notations .../Applications/LilyPond/lilypond-2.23.6/bin/lilypond --pdf -l NONE -s -o "pdflily/HumdrumScotKeys" "lilypond/HumdrumScotKeys.ly"Contents of lilypond sub-folder:8 -rw-r--r--  1 jacquesmenu  staff  1708 Feb 25 16:14 lilypond/HumdrumScotKeys.lyContents of pdflily sub-folder:88 -rw-r--r--  1 jacquesmenu  staff  42039 Feb 25 16:14 pdflily/HumdrumScotKeys.pdfjacquesmenu@macmini: ~/musicformats-git-dev/files/musicxmlfiles/keys > ls -salRtotal 24 0 drwxr-xr-x    7 jacquesmenu  staff   224 Feb 25 16:14 . 0 drwxr-xr-x  108 jacquesmenu  staff  3456 Feb 25 07:46 ..16 -rw-r--r--@   1 jacquesmenu  staff  6148 Feb 25 12:51 .DS_Store 8 -rw-r--r--    1 jacquesmenu  staff  2634 Apr 22  2021 HumdrumScotKeys.xml 0 lrwxr-xr-x    1 jacquesmenu  staff    11 Feb 25 14:12 Makefile -> ../Makefile 0 drwxr-xr-x    3 jacquesmenu  staff    96 Feb 25 16:14 lilypond 0 drwxr-xr-x    4 jacquesmenu  staff   128 Feb 25 16:14 pdflily./lilypond:total 80 drwxr-xr-x  3 jacquesmenu  staff    96 Feb 25 16:14 .0 drwxr-xr-x  7 jacquesmenu  staff   224 Feb 25 16:14 ..8 -rw-r--r--  1 jacquesmenu  staff  1708 Feb 25 16:14 HumdrumScotKeys.ly./pdflily:total 96 0 drwxr-xr-x  4 jacquesmenu  staff    128 Feb 25 16:14 . 0 drwxr-xr-x  7 jacquesmenu  staff    224 Feb 25 16:14 .. 8 -rw-r--r--  1 jacquesmenu  staff    170 Feb 25 16:14 HumdrumScotKeys.midi88 -rw-r--r--  1 jacquesmenu  staff  42039 Feb 25 16:14 HumdrumScotKeys.pdfjacquesmenu@macmini: ~/musicformats-git-dev/files/musicxmlfiles/keys > make cleanjacquesmenu@macmini: ~/musicformats-git-dev/files/musicxmlfiles/keys > ls -saltotal 24 0 drwxr-xr-x    5 jacquesmenu  staff   160 Feb 25 15:57 . 0 drwxr-xr-x  108 jacquesmenu  staff  3456 Feb 25 07:46 ..16 -rw-r--r--@   1 jacquesmenu  staff  6148 Feb 25 12:51 .DS_Store 8 -rw-r--r--    1 jacquesmenu  staff  2634 Apr 22  2021 HumdrumScotKeys.xml 0 lrwxr-xr-x    1 jacquesmenu  staff    11 Feb 25 14:12 Makefile -> ../Makefile

Makefile
Description: Binary data

Re: Red dot before all notes

[Jacques Menu]

Hello,

Using ". “ instead of ". “ in the original solution moves the dot apart.

JM

> Le 17 févr. 2022 à 20:02, Jean Abou Samra  a écrit :
> 
> Hi,
> 
> One thing you may not be aware of is that when you reply
> to an existing thread, the reply appears in the same thread
> for others, even if you change the title. I saw your message
> under "Box around MeasureCounter". It is better to start
> a new topic instead.
> 
> 
> Le 17/02/2022 à 19:21, Rajesh Baskar a écrit :
>> 
>> Hi,
>> 
>> I'm trying to get a red dot placed before each note. I have tried using 
>> \tweak and
>> 
>> \set fingeringOrientations = #'(left)
>> 
>> \finger  \markup \with-color "#FF" "."
>> 
>> But nothing seems to give the desired results.
>> 
>> The below image is what I'm trying to get.
>> 
>> 
>> \version "2.22.0" \include "english.ly" \header { tagline = "" } \score 
>> {\new Staff \with {\remove "Time_signature_engraver" } {\set 
>> Staff.midiInstrument = #"Acoustic Grand Piano" \key c \major \time 5/1 \clef 
>> treble c'1 d' e' f' g' \bar "||"} \layout { } \midi { \tempo 4 = 168}}
>> 
>> Thanks for all the help,
>> 
> 
> 
> 
> This works for me:
> 
> \version "2.22.1"
> 
> {
>   \set fingeringOrientations = #'(left)
>   
> }
> 
> Perhaps you forgot the chord <>? It is necessary to be
> able to use fingeringOrientations (see
> https://lilypond.org/doc/v2.23/Documentation/notation/inside-the-staff#fingering-instructions
>  
> ).
> 
> I'd adjust the formatting a bit and use a real dot sign:
> 
> \version "2.22.1"
> 
> {
>   \set fingeringOrientations = #'(left)
>"dots.dot">
> }
> 
> Best,
> Jean

Re: Blind and visually impaired users learning LilyPond

[Jacques Menu]

Hello Hwaen,

The only templates section as far as I can say is the vocal ensembles templates 
section in the learning manual.

The LSR at https://lsr.di.unimi.it/LSR/Search?q=midi 
 is quite useful, but contains 
advanced examples regarding MIDI.

> Le 14 févr. 2022 à 06:47, Hwaen Ch'uqi  a écrit :
> 
> Greetings Jacques,
> 
> Admittedly, I cannot find it at the moment, but is there not already a
> Templates section? Perhaps these additions could be added to that?
> 

Re: Blind and visually impaired users learning LilyPond

[Jacques Menu]

Another approach could be to add a new first chapter, maybe named “Discovering 
LilyPond”, containing a handful of examples without much commentary. 

Those could illustrate various features such as <<…>> without a \score around, 
\score, \book, chords and lyrics, as well as PDF, SVG and MIDI output.

JM

> Le 14 févr. 2022 à 06:21, Werner LEMBERG  a écrit :
> 
> 
>> I rather like the idea of there being a section in the documentation
>> for visually impaired users; I would even be willing to help
>> contribute to such a section.
> 
> Excellent, and thanks for the offer.  If you find time to write such a
> section, simply send your suggested text to this list, indicating
> where to insert it.  We will then discuss it and do the integration
> into the documentation.
> 
> 
>Werner
> 

Re: LilyPond 2.23.6 released

[Jacques Menu]

Hello developers,

Thanks a lot for those excellent news!. I’ve switched to 2.23.6/guile 2.2 on 
MacOS and will report about my experience.

JM

> On 8 Feb 2022, at 14:07, Jonas Hahnfeld via LilyPond user discussion 
>  wrote:
> 
> We are happy to announce the release of LilyPond 2.23.6. This is termed
> a development release, but these are usually reliable. If you want to
> use the current stable version of LilyPond, we recommend using the
> 2.22.1 version.
> 
> This release also marks a transition towards Guile 2.2: The binaries
> available from http://lilypond.org/development are built using GUB with
> Guile 1.8, while the packages available from
> https://gitlab.com/lilypond/lilypond/-/releases/release%252F2.23.6-1
> were created with the new infrastructure developed over the past
> months, making use of Guile 2.2. We encourage testing with your scores
> to make sure that future releases of LilyPond will continue to work for
> you. If there are problems with the version using Guile 2.2 that cannot
> be reproduced with the binaries using Guile 1.8, we would love to hear
> about them as early as possible.
> 
> The binaries with Guile 2.2 are different in a number of ways, the two
> major changes being:
> 1. All binaries are 64-bit only and available for Linux, Windows (via
> mingw), and macOS. In particular, this finally means official binaries
> that work on macOS >= 10.15, which cannot run 32-bit programs anymore.
> 2. There is no installation, simply extract the downloaded tar or zip
> (for Windows) archive and run it. The binaries don't include a GUI
> anymore, we recommend using third-party editors such as Frescobaldi.

Re: Graphical rallentendo

[Jacques Menu]

Hello Lukas-Fabian,

Thanks, didnt’ think of the good old empty chord trick!

JM

> Le 2 févr. 2022 à 13:36, Lukas-Fabian Moser  a écrit :
> 
> Hi Jacques,
> 
>> Is there a more natural way of obtaining this result than with a sequence of 
>> shorter and shorter skips?
> 
> The following seems to work here:
> 
> \version "2.23.5"
> 
> \relative c''' {
>   \time 6/8
>   <<
> {
>   g8 ^\markup {\italic "rit." }  g4  g8
>   g4  | % 16
>   c8 [  bes8 (  g8 )
>   e8 (  c8 )  bes8 _\laissezVibrer ]
> }
> {
>   \once\override TextSpanner.style = #'trill % wave zigzag
>   \once\override TextSpanner.minimum-length = #8
>   \once\override TextSpanner.Y-offset = #-4
>   \once\override TextSpanner.springs-and-rods = 
> #ly:spanner::set-spacing-rods
>   { <> \startTextSpan s2.*2 <> \stopTextSpan }
> }
>   >>
> 
> }
> 
> If you want the stopTextSpan to happen before the next bar starts, feel free 
> to replace *2 in s2.*2 by a fraction slightly less than 2, for example 127/64.
> 
> In general, I never liked the technique of attaching events that occur at the 
> start of a timestep to spacer rests, and I already changed this in the 
> documentation at some points I think: To  me,
> 
> s2\f s2\> s1\p
> 
> always reads as "before skipping 2, put a \f; then, before skipping another 
> 2, start a diminuendo; then, before skipping a 1, put a \p" which feels like 
> mental roller coaster. It seems much more natural to do
> 
> <>\f s2 <>\> s2 <>\p
> 
> allowing us to read in the natural order: put a \f, then skip 2, then start a 
> diminuendo, etc.
> 
> And of course, with recent development versions, you can even do
> 
> <>\f \after 2 \> \after 1 \p s1*2
> 
> or something like that.
> 
> Lukas
> 

Graphical rallentendo

[Jacques Menu]

Hello folks,

Is there a more natural way of obtaining this result than with a sequence of 
shorter and shorter skips?

Thanks for your help!

JM


%%

\version "2.23.5"

\relative c''' {
  \time 6/8

  <<
{
  g8 ^\markup {\italic "rit." }  g4  g8
  g4  | % 16
  c8 [  bes8 (  g8 )
  e8 (  c8 )  bes8 _\laissezVibrer ]
}
{
  \once\override TextSpanner.style = #'trill % wave zigzag
  \once\override TextSpanner.minimum-length = #8
  \once\override TextSpanner.Y-offset = #-4
  \once\override TextSpanner.springs-and-rods = 
#ly:spanner::set-spacing-rods
  { s2. \startTextSpan s2 s8... s64 \stopTextSpan }
}
  >>
}

%%

Re: help!

[Jacques Menu]

Hello Виноградов,

It will be easier for the people on this list to help you if you provide a 
minial working example (MWE).

JM

> Le 31 janv. 2022 à 16:55, Виноградов Юрий  a écrit :
> 
> Hello. Help please. I have two volts of repetition. You need to put a segno 
> sign between them. Example on the screenshot.
> I am grateful to you in advance.
>  
>  
> С уважением,
> Виноградов Юрий.
>  
> 

Re: Lilypond's English Horn MIDI instrument is non-transposing?

[Jacques Menu]

And yes, the scores are written in the treble clef.

JM

> Le 15 janv. 2022 à 11:41, Jacques Menu  a écrit :
> 
> Hello Wol,
> 
>> Le 15 janv. 2022 à 11:38, Wols Lists > <mailto:antli...@youngman.org.uk>> a écrit :
>> 
>> On 13/01/2022 21:40, James B. Wilkinson wrote:
>>> If I make it with the English horn part correctly transposed, the MIDI 
>>> sounds terrible. If I make it with the English horn part untransposed, it 
>>> sounds fine. My conclusion is that the midiInstrument "english horn" reads 
>>> its part in C rather than in F. Shouldn't it play the notes that a real 
>>> English horn would?
>> 
>> Out of curiosity, and speaking as a Brit! what on earth is an "English 
>> Horn"? Is the instrument the English call a Cor Anglais?
> 
> Yes, it is an oboe alto in F, the modern evolution of Tribert’s instruments:
> 
> 
> 
> JM
> 
>> 
>> Cheers,
>> Wol
>> 
> 

Re: Ornament question

[Jacques Menu]

Hello Paul & al.

Here is the link that Vincent sent to me (didn’t notice is was privately), with 
the solution I mentioned in my answer to the list:


\version "2.22.1"

% scoops, thanks to v...@vintherine.org

#(define (scoop-stencil grob)
   (ly:stencil-add
(ly:note-head::print grob)
(grob-interpret-markup grob
   (markup #:with-dimensions '(0 . 0) '(0 . 0)
   #:translate '(-0.2 . -0.5)
   #:path 0.25 '((moveto -0.2 0.5)
 (curveto 0.2 2 -1.2 2.5 -1.7 
2.5))
scoopH = \once \override NoteHead #'stencil = #scoop-stencil

#(define (scoop-stencil grob)
   (ly:stencil-add
(ly:note-head::print grob)
(grob-interpret-markup grob
   (markup #:with-dimensions '(0 . 0) '(0 . 0)
   #:translate '(-0.2 . -0.5)
   #:path 0.25 '((moveto 0 0)
 (curveto 0.2 -1 -1.2 -1.5 -1.7 
-1.5))
scoopB = \once \override NoteHead #'stencil = #scoop-stencil

\relative c'' {
  \scoopH c2 \scoopB c2
}



JM

> Le 14 janv. 2022 à 11:44, Paul Hodges  a écrit :
> 
> 
> What is the name of the ‘up arc’ ornament on the first note in this score? 
> Then I’ll look it up in the LPNR.
> 
> That's a Scoop.  I don't think LilyPond supports it directly, but several 
> ways of faking it are shown in this thread (two links to different ways of 
> viewing it):
> https://lilypond-user.gnu.narkive.com/nbjxGoSy/scoop-before-note
> https://lists.gnu.org/archive/html/lilypond-user/2021-09/msg00429.html
> 
> Paul

Re: Ornament question

[Jacques Menu]

Hello Aaron,

Vincent’s solution might be taken over by Lily itself, IMHO.

JM

> Le 14 janv. 2022 à 09:58, Aaron Hill  a écrit :
> 
> On 2022-01-14 12:13 am, Jacques Menu wrote:
>> What is the name of the ‘up arc’ ornament on the first note in this
>> score? Then I’ll look it up in the LPNR.
> 
> I think "scoop" might be the term.  Did we ever get a \bendBefore as the 
> logical companion to \bendAfter?
> 
> 
> -- Aaron Hill

Re: CPU stress tests for LilyPond

[Jacques Menu]

Hello,

Here is what I get for this 102 page score:

jacquesmenu@macmini > time lilypond MSDM.ly
GNU LilyPond 2.22.1
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;   or pass the --no-auto-compile argument to disable.
… … … …
real0m39.590s
user0m37.119s
sys 0m2.285s

jacquesmenu@macmini > ls -sal MSDM.*
   8 -rw---@ 1 jacquesmenu  staff2695 Nov 17  2016 MSDM.ly
  88 -rw-r--r--  1 jacquesmenu  staff   42641 Nov 30 16:32 MSDM.mid
1888 -rw-r--r--  1 jacquesmenu  staff  963019 Nov 30 16:32 MSDM.pdf

The machine is a Mac Mini M1, 8GB RAM, 256 GB disk.

JM

> Le 30 nov. 2021 à 15:28, Hans Åberg  a écrit :
> 
> 
>> On 30 Nov 2021, at 14:26, Paolo Prete  wrote:
>> 
>> I need to buy a new PC, more powerful than the one I own. The CPU and RAM 
>> must be chosen on the time required to produce LilyPond output. Are there 
>> any test sheets with different CPUs and the time they take to output a score 
>> that takes a long time to compile? In case this doesn't exist specifically 
>> for LilyPond, is there anything equivalent I can use?
> 
> There are general benchmarks, like those below, maybe the single core ones 
> can be useful.
> 
> https://browser.geekbench.com
> https://browser.geekbench.com/mac-benchmarks
> 
> 
> 

Re: \chordmode question

[Jacques Menu]

Hello Valentin

Yes, that does the trick, thanks a lot!

JM

> Le 29 nov. 2021 à 19:42, Valentin Petzel  a écrit :
> 
> Hello Jacques,
> 
> Does this do the trick?
> 
> \new ChordNames \chordmode {
>  \language "nederlands"
>  \key f \major
>  \numericTimeSignature \time 6/8
> 
>  \clef "treble"
>  f4.:5.3 d:m | % 1
>  \barNumberCheck #2
>  | % 2
>  \barNumberCheck #2
> 
>  \once\override ChordName.text = "%"
>  \parenthesize d2.:m | % 2 HERE
> 
>  d2.:m | % 1
>  \barNumberCheck #4
>  | % 1
>  \barNumberCheck #4
> }
> 
> 
> Cheers,
> Valentin
> 
> Am Montag, 29. November 2021, 16:21:08 CET schrieb Jacques Menu:
>> Hello Folks,
>> 
>> I’d like to have the Dm in measure 2 displayed as ‘%’. Is that possible?
>> Thanks!
>> 
>> JM
>> 
>> —
>> 
>> Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES = \chordmode {
>>  \language "nederlands"
>>  \key f \major
>>  \numericTimeSignature \time 6/8
>> 
>>  \clef "treble"
>>  f4.:5.3 d:m | % 1
>>  \barNumberCheck #2
>> 
>>  | % 2
>> 
>>  \barNumberCheck #2
>> 
>>  \parenthesize d2.:m | % 2 HERE
>> 
>>  d2.:m | % 1
>>  \barNumberCheck #4
>> 
>>  | % 1
>> 
>>  \barNumberCheck #4
>> }

\chordmode question

[Jacques Menu]

Hello Folks,

I’d like to have the Dm in measure 2 displayed as ‘%’. Is that possible?
Thanks!

JM

—

Part_POne_HARMONIES_Staff_Voice_Eleven_HARMONIES = \chordmode {
  \language "nederlands"
  \key f \major
  \numericTimeSignature \time 6/8
  
  \clef "treble"
  f4.:5.3 d:m | % 1
  \barNumberCheck #2
  | % 2
  \barNumberCheck #2
  
  \parenthesize d2.:m | % 2 HERE
  
  d2.:m | % 1
  \barNumberCheck #4
  | % 1
  \barNumberCheck #4
}

Re: DynamicTextSpanner.style

[Jacques Menu]

Thanks Jean!

JM

> Le 22 nov. 2021 à 14:13, Jean Abou Samra  a écrit :
> 
> Le 22/11/2021 à 14:01, Jacques Menu a écrit :
>> Hello folks,
>> 
>> I can’t find the list of all possible values for DynamicTextSpanner.style in 
>> the LP internals reference.
>> Where is it to be found?
>> 
>> Thanks!
>> 
>> JM
> 
> 
> Hi Jacques,
> 
> Possible styles are usually documented in interfaces. In this case, it's in 
> the line-interface:
> 
> http://lilypond.org/doc/v2.23/Documentation/internals/line_002dinterface
> 
> There is also more user-level documentation of line styles:
> 
> http://lilypond.org/doc/v2.22/Documentation/notation/line-styles
> 
> Cheers,
> Jean

DynamicTextSpanner.style

[Jacques Menu]

Hello folks,

I can’t find the list of all possible values for DynamicTextSpanner.style in 
the LP internals reference.
Where is it to be found?

Thanks!

JM

Re: Stems question

[Jacques Menu]

> Le 16 nov. 2021 à 11:44, Павел  a écrit :
> 
> Sorry, my mistake:
> 
> \relative c' { \stemDown c8[ d] \stemUp e[  e'] }
> 
> 16.11.2021 13:41, Павел пишет:
>> Hello, Jacques Menu!
>> 
>> Since you did not specify the time signature, lilypond chose the default one 
>> — 4/4. In this signature, lilypond groups 1/8-notes by four. You can 
>> explicitly override it:
>> 
>> \relative c'[ { \stemDown c8] d \stemUp e[  e'] }
>> 
>> For additional information you can read the documentation: 
>> http://lilypond.org/doc/v2.22/Documentation/notation/displaying-rhythms 
>> <http://lilypond.org/doc/v2.22/Documentation/notation/displaying-rhythms>Thanks
>>  Павел!

JM

Stems question

[Jacques Menu]

Hello folks,

With this input:

%%
\version "2.22.1"

\relative c' { \stemDown c8 d \stemUp e  e' }
%%

I get this output:


Any help is welcome!

JM

Re: Pat Waing Notation

[Jacques Menu]

Hello Orm,Using jianpu-ly, you can get the following, i.e. numbers only.JM

MinimalScore.ly
Description: Binary data


MinimalScore.pdf
Description: Adobe PDF document
Le 15 nov. 2021 à 15:24, Werner LEMBERG  a écrit : I'm working on a piece for Pat Waing, a traditional instrument fromMyanmar consisting of 20 tuned drums. Musicians from Myanmar use aspecial form of notation, using numbers for the pitches with dotsunderneath or above indicating the octave.This notation is looks like jiǎnpǔ (簡譜); have a look at SilasBrown's page:  http://ssb22.user.srcf.net/mwrhome/jianpu-ly.html Werner

\compressMMRests, compressEmptyMeasures or \compressFullBarRests?

[Jacques Menu]

Hello folks,

I’m at a loss regarding that : \compressMMRests, compressEmptyMeasures are 
present in LPNR 2.23, but Frescobaldi 3.1.3 knows only \compressFullBarRests.

I remember there’s been a name change at some point in time. 

Sp which command should one use?

Thanks for your help!

JM

Re: Terminology question

[Jacques Menu]

Hello everybody,

Thanks for your answers, parts/staves/voices extraction will do for what I have 
in mind.

A nice w/e!

JM

> Le 13 nov. 2021 à 23:34, Leo Correia de Verdier 
>  a écrit :
> 
> I’ve just said writing parts (from a score) even if that, for most of my 
> musicwriting life, mostly meant layout. 
> 
>> 13 nov. 2021 kl. 23:23 skrev David Nalesnik :
>> 
>> On Sat, Nov 13, 2021 at 3:42 PM Kieren MacMillan
>>  wrote:
>>> 
>>> Hi all,
>>> 
 The *extraction* of parts is something that only
 makes sense in times of computer score representation, as you’d extract a 
 part
 of the information from a full score.
>>> 
>>> I know it’s a fine semantic point… but the dictionary gives the definition 
>>> “the action of taking out something”. What better word is there to describe 
>>> the action of taking a single instrumental part out of a full orchestral 
>>> score?
>>> 
>> 
>> "Extraction" somehow doesn't imply representation to me.  It's an
>> operation performed on data whether that data yields a score or not.
>> Or I'm just imagining things.  I do like the word.  What else
>> describes the activity which precedes writing out a part?
>> 
> 

Re: Terminology question

[Jacques Menu]

Bonsoir Kieren!

Yes, that helps, thanks.

Let’s wait for more suggestions if any!

JM

PS> Longing to meet you again at Salzburg or elsewhere for a nice music 
engraving conference, Covid permitting...

> Le 13 nov. 2021 à 19:30, Kieren MacMillan  a 
> écrit :
> 
> Bonjour Jacques!
> 
>> What is the english name for the process of creating invidual 
>> parts/staves/voices scores from a director’s score?
> 
> “Extraction” is the term that most engraving industry people would 
> immediately recognize… but that might be a post-computer-application term, so 
> I’d love to find out if there’s a more traditional term.
> 
> Hope that helps!
> Kieren.
> 
> 
> Kieren MacMillan, composer (he/him/his)
> ‣ website: www.kierenmacmillan.info
> ‣ email: kie...@kierenmacmillan.info
> 

Terminology question

[Jacques Menu]

Hello folks,

What is the english name for the process of creating invidual 
parts/staves/voices scores from a director’s score?

Thanks for your help!

JM

Re: How to add a horizontal line after every third verse?

[Jacques Menu]

Hello Matthew,

This was answered by Aaron in a recent post, see attached file.

JM



LyricsWithSeparatorLineBelow.ly
Description: Binary data


> Le 14 oct. 2021 à 05:13, Matthew Fong  a écrit :
> 
> Dear LilyPonders,
> 
> Continuing on my journey of typesetting hymns, would anyone have suggestions 
> on ways to add a short horizontal rule after every third verse? I tried 
> looking around, but wasn't able to find examples. The options I would like to 
> have is keep line spacing intact (with the rule), or add a little bit of 
> space between the verses. 
> 
> Please see attached image as an example.
> 
> 
> Many thanks in advance,
> mattfong
>