Re: Padding paper setting not honored
Le 31/08/2022 à 01:33, Knute Snortum a écrit :
Hi everyone,
I have a problem that is unfortunately very difficult to reproduce.
It seems in some circumstances that the padding setting in the paper
block is not honored. I've attached a screenshot. In the middle you
can see that the slur from the bottom stave is going through the pedal
marking of the top stave. It looks like the padding is measured from
the ottava bracket and not the slur, but that's just a guess.
I have tried and failed to create a MWE. I've attached my attempt but
unfortunately it does not reproduce the problem. (I couldn't get the
ottava bracket below the slur which may be why the MWE fails.)
For the brave, I have uploaded my source files to GitHub:
https://github.com/ksnortum/chopin-opus-25/tree/main
If anyone is willing to tackle this problem, it would be much appreciated.
Well, here is a reasonably minimal example:
\version "2.23.12"
veryHigh =
\shape #'((0 . 0) (0 . 10) (0 . 10) (0 . 0)) \etc
<<
\new Staff {
R1
\break
% OK
c'''2\veryHigh ( 2)
\break
% KO
c'''2\veryHigh ( \change Staff = down 2)
}
\new Staff = down {
s1*3
}
>>
Unfortunately, this is hard to fix. The second is cross-staff. Because of
this, its shape, and consequently its height, depend on the exact distance
between the staves (inside one system). But that distance depends itself
on everything else that is on the page (other systems), as LilyPond will
try to find a good fit for the page globally. So LilyPond needs to space
the staves before it can know how tall the slur it is.
(*Maybe* it would be possible to let LilyPond reuse the pure height
estimation
in this case. I'm not sure, and I haven't tried.)
For now, I am afraid you need to resort to manual system positioning,
as described on
https://lilypond.org/doc/v2.22/Documentation/notation/explicit-staff-and-system-positioning
Best,
Jean
Padding paper setting not honored
Hi everyone,
I have a problem that is unfortunately very difficult to reproduce.
It seems in some circumstances that the padding setting in the paper
block is not honored. I've attached a screenshot. In the middle you
can see that the slur from the bottom stave is going through the pedal
marking of the top stave. It looks like the padding is measured from
the ottava bracket and not the slur, but that's just a guess.
I have tried and failed to create a MWE. I've attached my attempt but
unfortunately it does not reproduce the problem. (I couldn't get the
ottava bracket below the slur which may be why the MWE fails.)
For the brave, I have uploaded my source files to GitHub:
https://github.com/ksnortum/chopin-opus-25/tree/main
If anyone is willing to tackle this problem, it would be much appreciated.
--
Knute Snortum
\version "2.22.2"
slurShapeA = \shape #'(
((0 . 4) (0 . 4) (0 . 4) (0 . 4))
((0 . 4) (0 . 4) (0 . 4) (0 . 4))
((0 . 4) (0 . 4) (0 . 4) (0 . 4))
) Slur
rightHand = {
\ottava 1
\slurShapeA g4( 4 4 4
\repeat unfold 12 { g4 4 4 4 }
g4 4 4 4)
}
leftHand = {
\clef bass
\magnifyMusic #3/4 {
\stemDown
\repeat unfold 14 {
\once \normalsize \offset positions #'(-1 . -1) Beam
g,,8_5\sustainOn 8 8 8 8 8 8 8\sustainOff
}
}
}
\layout {
\context {
\Score
\override Slur.details.free-head-distance = 1
}
}
\score {
\new PianoStaff <<
\new Staff \rightHand
\new Staff \leftHand
>>
}
Re: Barre grob - appearance
Am Mo., 29. Aug. 2022 um 23:24 Uhr schrieb Jean Abou Samra : > > Le 27/08/2022 à 13:55, Thomas Morley a écrit : > > I foresee some hard to solve problems, though. I'm currently not sure > > about the success. > > > IUUC, you have a problem to draw the grob with both a vertical and a > horizontal > line, because the usual way to make the vertical line place itself > against the > notes with some padding would be Y-offset = > side-position-interface::y-aligned-side, > but this requires the Y-extent + vertical-skylines, and those depend on > the full > stencil, and the vertical part of the line depends on the Y-offset, so > you have > a cyclic dependency. Yeah... > > Tricky, yes. OTOH, would it work to have two separate grobs, one for the > horizontal > line and one for the vertical one? Say, > > BarreVerticalLine > >- an Item >- has 'horizontal-line pointer to a BarreHorizontalLine >- stencil = a function that takes the coordinate of the > 'horizontal-line, and draws a vertical line up to that > height >- X-extent = a function that essentially does > >(symmetric-interval thickness) > > (it can't be computed from the stencil, since as BarreVerticalLine > is an Item its X-extent will be asked for before line breaking) > >- Y-extent = an unpure-pure container (ask me for details if > needed) > > BarreHorizontalLine > >- a Spanner >- has horizontal-line-spanner-interface, uses it for bound-details. > Uses ly:line-spanner::print for stencil. This is all quite similar > to TextSpanner. > > Just in case that helps. > > Jean > > Ofcourse this helps! Not that I have understood all parts yet...and it's already about step (3) Coding Up to now I only tried to collect all varieties of possible barré-signs, i.e. step (1) For step, (2) Requirements, I think about what should be tweakable: - horizontal line (y/n), with hook (y/n) - vertical line (y/n), with hook (y/n) - bottom end of the vertical line must be settable - make multiple barré per chord possible - line-style(s): solid/dashes/dotted/none - script-priority for horizontal and vertical line, this value may be different (not sure about it yet) - which defaults for text (italic?, arabic/roman numbers? etc) So far my current thoughts, with no warranties for completeness (did I miss something?). Best, Harm
Re: Controlling Slur Marks
Thank-you to Leo Correia de Verdier for excellent instructions. I'm pleased
with the results. I see later in the documentation there is a snippet on
how to merge voices, so that's next on my list.
[image: image.png]
<<
{s8 s16^"ossia" s16 a16(g f e)| g16(f e d) s4|}
\\
{f16(e f g) a(f c a)| g16(a bf g) c(bf a g)|}
>>
On Tue, Aug 30, 2022 at 12:37 PM Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:
> The easiest way would be to use \voiceOne and \voiceTwo instead of \stemUp
> and \stemDown (recommended anyway in most cases). Otherwise _( and ^( works
> too.
>
> HTH
> /Leo
>
> 30 aug. 2022 kl. 19:30 skrev Greg Lindstrom :
>
>
> I am finishing up engraving my first full score. It's a piece for brass
> band where we could not find a score anywhere and the one we've ordered has
> been backordered for 6 months! I took it upon myself to pull all the parts
> and engrave away. Eventually, I will hook up a midi keyboard to enter stuff
> like this, but I'm as quick, if not quicker, typing it in and
> controlling just about everything the first time through.
>
> Lilypond is an impressive system and I use it over the 2 "big" commercial
> engraving packages because I think the final product just looks better.
>
> But, to my question...
>
> I have a very short Ossia that I would like to add to a chart I'm
> engraving. I'd rather not break it out onto its own staff (just to save
> space in the score) so I'm adding it as a CueVoice. The problem is the slur
> marks on the main line are above and the slurs on the ossia are below (see
> snippet). Is there a way to control where the slur marks appear, in the
> same spirit as stems up and down? Is it preferred to break the ossia out in
> its own staff:?
>
> Thanks!
> --greg
>
> [image: image.png]
>
> And the code to generate it
>
> <<{f16(e f g\!) a(f c a)|
> \stemDown{g16(a bf g)\> c(bf a g\!}|
> }
> {
> \new CueVoice{
> \stemUp s16 s8^\markup\small{ossia} s16 a'16(g f e)|
> g16(f e d) s4|
> }
> }
> >>
>
>
Re: Barre grob - appearance
Am Mo., 29. Aug. 2022 um 23:20 Uhr schrieb Jeff Olson :
>
>
> On 8/27/2022 5:36 AM, Thomas Morley wrote:
> > Ofcourse, one can find several
> > codings here on the list, in LSR, I have some own as well. All are
> > (ab)using spanners like TextSpanner or hijacking other grobs like
> > Arpeggio.
>
> As an old amateur guitarist, I'm looking forward to a better barre
> solution. Thank you, Harm, for taking this on!
>
> In the mean time there are existing solutions that are NOT based on
> spanners.
>
> The system I've been using for years is based on the similarities of
> barres and position indicators. Both are indicators for overall
> placement of the hand along the neck. Both typically use Roman
> numerals. Both occupy the same visual space above the staff, and hence
> both are read by the eye like the different words in the same sentence
> about "Where do I put my hand?". The more detailed question of "Where
> do I put my fingers?" is handled as a separate issue using Arabic
> numerals within the staff.
>
> The system is easily described, as in this footnote to the reader:
>
> Roman numerals above the staff indicate hand positions on the
> fretboard and remain in effect until the
> next such indication. A barre is indicated by prefixing the Roman
> numeral with a small “b_” for a small
> barre or a large “B_” for a large barre at that position.
>
> Admittedly, this system alone isn't going to express all the nuances in
> your inner barre examples, but my arrangements are for intermediate
> guitarists, and they seem to catch on to it quickly (and most, like me,
> can scarcely do an inner barre).
>
> Implementation in lilypond is trivial, by including definitions like these:
>
> % guitar neck position indicators
> pI= ^\markup { "I" }
> pII = ^\markup { "II" }
> pIII = ^\markup { "III" }
> pIV = ^\markup { "IV" }
>
> % large barre
> BpI= ^\markup { "B_I" }
> BpII = ^\markup { "B_II" }
> BpIII = ^\markup { "B_III" }
> BpIV = ^\markup { "B_IV" }
>
> % small barre
> bpI= ^\markup { "b_I" }
> bpII = ^\markup { "b_II" }
> bpIII = ^\markup { "b_III" }
> bpIV = ^\markup { "b_IV" }
>
> The resulting code is very compact and stands out nicely in
> Frescobaldi's color highlighting, as shown in the attached image
> alt-barre-frescobaldi.png.
>
> The output appearance from this same example is shown in the attached
> alt-barre-appearance.png. This is from a lengthy arrangement for two
> guitars I published five years ago, which is why it was intentionally
> crowded to reduce the page count. In some of the cases shown, I had to
> cheat on the placement of the position indicators, e.g. in m44.
>
> I'm hoping that whatever solution you create will play well with other
> grobs in crowded situations. As you mentioned two weeks ago, "Notation
> of classical guitar is one of the most complex ones". There's already a
> lot of other important visual clutter, even in the simple example I've
> attached (e.g. slurs and beams on the same notes under the barre).
> Reminds me of Alice's Restaurant
> "... with circles
> and arrows and a paragraph on the back ... explaining what each one was
> ...". We just don't want our creations "... to be used as evidence
> against us". :-)
>
> Jeff
>
Hi Jeff,
thanks for your input.
Your barre-signs are a valid method and should be possible to be
printed (and indeed missing in the image I sent with the initial
mail).
Simply by omitting all lines, vertically and horizontally, likely by
setting (sub)properties, just giving the text-part.
Best,
Harm
Re: Controlling Slur Marks
The easiest way would be to use \voiceOne and \voiceTwo instead of \stemUp and
\stemDown (recommended anyway in most cases). Otherwise _( and ^( works too.
HTH
/Leo
> 30 aug. 2022 kl. 19:30 skrev Greg Lindstrom :
>
>
> I am finishing up engraving my first full score. It's a piece for brass band
> where we could not find a score anywhere and the one we've ordered has been
> backordered for 6 months! I took it upon myself to pull all the parts and
> engrave away. Eventually, I will hook up a midi keyboard to enter stuff like
> this, but I'm as quick, if not quicker, typing it in and controlling just
> about everything the first time through.
>
> Lilypond is an impressive system and I use it over the 2 "big" commercial
> engraving packages because I think the final product just looks better.
>
> But, to my question...
>
> I have a very short Ossia that I would like to add to a chart I'm engraving.
> I'd rather not break it out onto its own staff (just to save space in the
> score) so I'm adding it as a CueVoice. The problem is the slur marks on the
> main line are above and the slurs on the ossia are below (see snippet). Is
> there a way to control where the slur marks appear, in the same spirit as
> stems up and down? Is it preferred to break the ossia out in its own staff:?
>
> Thanks!
> --greg
>
>
>
> And the code to generate it
>
> <<{f16(e f g\!) a(f c a)|
> \stemDown{g16(a bf g)\> c(bf a g\!}|
> }
> {
> \new CueVoice{
> \stemUp s16 s8^\markup\small{ossia} s16 a'16(g f e)|
> g16(f e d) s4|
> }
> }
> >>
Controlling Slur Marks
I am finishing up engraving my first full score. It's a piece for brass
band where we could not find a score anywhere and the one we've ordered has
been backordered for 6 months! I took it upon myself to pull all the parts
and engrave away. Eventually, I will hook up a midi keyboard to enter stuff
like this, but I'm as quick, if not quicker, typing it in and
controlling just about everything the first time through.
Lilypond is an impressive system and I use it over the 2 "big" commercial
engraving packages because I think the final product just looks better.
But, to my question...
I have a very short Ossia that I would like to add to a chart I'm
engraving. I'd rather not break it out onto its own staff (just to save
space in the score) so I'm adding it as a CueVoice. The problem is the slur
marks on the main line are above and the slurs on the ossia are below (see
snippet). Is there a way to control where the slur marks appear, in the
same spirit as stems up and down? Is it preferred to break the ossia out in
its own staff:?
Thanks!
--greg
[image: image.png]
And the code to generate it
<<{f16(e f g\!) a(f c a)|
\stemDown{g16(a bf g)\> c(bf a g\!}|
}
{
\new CueVoice{
\stemUp s16 s8^\markup\small{ossia} s16 a'16(g f e)|
g16(f e d) s4|
}
}
>>
Re: Configuration problems following new installation of Frescobaldi
Le 30/08/2022 à 16:40, David Wright a écrit : On Tue 30 Aug 2022 at 09:27:03 (+0200), Jean Abou Samra wrote: Le 30/08/2022 à 08:56, Michael Hendry a écrit : I stopped using Frescobaldi and Lilypond at the beginning of the Covid pandemic and since then I have bought a new iMac with Monterey and transferred files across, [ … etc … ] Just a note, if you're unaware, that your valuable contributions to lilypond-user are no longer available to people who rely on the text digest emails, now that you post HTML only (this morning, your time). They will receive, eg: -- Message: 7 Date: Tue, 30 Aug 2022 09:27:03 +0200 From: Jean Abou Samra To: Michael Hendry , LilyPond User Subject: Re: Configuration problems following new installation of Frescobaldi Message-ID: <3da23e00-7994-691a-0b35-2b0c624f2...@abou-samra.fr> Content-Type: text/plain; charset="utf-8" An HTML attachment was scrubbed... URL: <https://lists.gnu.org/archive/html/lilypond-user/attachments/20220830/97c36d37/attachment.htm> -- They do get to see the sections that other people quote. Oops, thanks for letting me know. I had switched my mailer to HTML for one message that needed it, and forgot to switch it back. It should be fine again now.
Re: Export to XML
Le 30/08/2022 à 12:55, nitra...@posteo.net a écrit : A MusicXML export integrated into LilyPond has been discussed repeatedly, and everybody agrees that it is desirable, but it has not been implemented so far because, well, it's quite easier said than done. In a free (libre) / open source project, the only way to be sure something will get done is to do it yourself. I didn't want to sound like complaining! I understand it should be a lot of work to provide. I wasn't sure it was not implemented for technical or ethical reasons. I understand. I would say it is unimplemented not for ethical reasons, nor even for technical reasons, but simply resource reasons — unlike most of the other problems that are discussed frequently (grace synchronization, cross-voice spanners), it isn't made hard by the way LilyPond is designed, it's just a big chunk of work that needs people with all of time, motivation and competence to tackle it.
Re: Configuration problems following new installation of Frescobaldi
On Tue 30 Aug 2022 at 09:27:03 (+0200), Jean Abou Samra wrote: > > > > > > Le 30/08/2022 à 08:56, Michael Hendry a > écrit : > >cite="mid:f07d2e1c-86fb-4b51-8cb9-dff22577c...@gmail.com"> > I stopped using Frescobaldi and > Lilypond at the beginning of the Covid pandemic and since then I have bought > a new iMac with Monterey and transferred files across, > [ … etc … ] Just a note, if you're unaware, that your valuable contributions to lilypond-user are no longer available to people who rely on the text digest emails, now that you post HTML only (this morning, your time). They will receive, eg: -- Message: 7 Date: Tue, 30 Aug 2022 09:27:03 +0200 From: Jean Abou Samra To: Michael Hendry , LilyPond User Subject: Re: Configuration problems following new installation of Frescobaldi Message-ID: <3da23e00-7994-691a-0b35-2b0c624f2...@abou-samra.fr> Content-Type: text/plain; charset="utf-8" An HTML attachment was scrubbed... URL: <https://lists.gnu.org/archive/html/lilypond-user/attachments/20220830/97c36d37/attachment.htm> -- They do get to see the sections that other people quote. Cheers, David.
Re: bookpart without pagebreak?
> Dear community,
> I would like to know how the pagebreak could be avoided between the two
> "movements" in the below quoted snippet:
It is because bookparts automatically do this behaviour. To make separate
movements fit into the same page, you have to do \score block instead.
\version "2.22.0"
MusicI = \relative c' {c4 d e f g1 }
MusicII = \relative g' { \time 2/4 g4 e8 f g4 e c1 }
\bookpart {
\header {
title = "My great Work"
composer ="Stefan Thomas"
}
\score {
\new Staff \MusicI
\header {
piece = "First Movement"
}
}
\score {
\new Staff \MusicII
\header {
piece = "Second Movement"
}
}
}
bookpart without pagebreak?
Dear community,
I would like to know how the pagebreak could be avoided between the two
"movements" in the below quoted snippet:
\version "2.22.0"
\header { title = "My great Work"
composer ="Stefan Thomas"
}
Music = \relative c' {c4 d e f g1 }
titleI = \header {
title = ""
subtitle = "First Movement"
}
\bookpart {
\titleI
\score { \new Staff \Music }
}
Music = \relative g' { \time 2/4 g4 e8 f g4 e c1 }
titleII = \header {
title = ""
composer=""
subtitle = "Second Movement"
}
\bookpart {
\titleII
\score { \new Staff \Music }
}
Re: Export to XML
> A MusicXML export integrated into LilyPond has been discussed repeatedly, > and everybody agrees that it is desirable, but it has not been implemented > so far because, well, it's quite easier said than done. In a free (libre) > / open source project, the only way to be sure something will get done > is to do it yourself. I didn't want to sound like complaining! I understand it should be a lot of work to provide. I wasn't sure it was not implemented for technical or ethical reasons.
Re: Export to XML
Le 30/08/2022 à 11:59, nitra...@posteo.net a écrit : Dear all, [...] 2) I tried the OpenLilylib package. I wasn't familiar with that tool and had to struggle a bit with the installation. But still, with the export-example.ly seen in the manual, I get this error message: | GNU LilyPond 2.22.2 | Traitement de « export-example.ly » | Analyse... | | oll-core: library infrastructure successfully loaded. | Interprétation en cours de la musique... | init exportHumdrum: "export-example.krn" | init Staff 1 | init Voice 1/1 (1) | init Voice 1/2 (2) | init Staff 2 | init Voice 1/ (3) | init Voice 2/ (1) | init Voice 2/mel (2)/home/remy/.config/lilypond/openlilylib/lilypond-export/api.scm:278:48: In _expression_ (ly:grob-properties grob): | /home/remy/.config/lilypond/openlilylib/lilypond-export/api.scm:278:48: Unbound variable: ly:grob-properties And I only get the PDF as an output. I don't know what I missed here? This sounds like this OLL package has not been updated for LilyPond version 2.22. 6) Last point: I made some month ago, a short presentation and introduction to LilyPond for my colleagues in my music institution. Beyond the fact it was quite a challenge to try and convince them of the utility to take some time and learn that great tool, I received that question I couldn't answer at the time: is it possible to import or export in XML? I haven't have a use for that kind of feature until now, and I don't know how the commercial softwares handle that, but still, wouldn't that be a great argument to convince the people to go for it? Final thought, I don't know how Urs did manage to convince publishers about LilyPond and what responses he got (I would be curious though), but I am pretty sure that kind of limitation in importing/exporting in XML would be nowdays a dealbreaker for publishing companies, don't you agree? A MusicXML export integrated into LilyPond has been discussed repeatedly, and everybody agrees that it is desirable, but it has not been implemented so far because, well, it's quite easier said than done. In a free (libre) / open source project, the only way to be sure something will get done is to do it yourself. Regards, Jean
Re: Configuration problems following new installation of Frescobaldi
Le 30/08/2022 à 12:10, Michael Hendry a écrit : On 30 Aug 2022, at 08:27, Jean Abou Samra wrote: Le 30/08/2022 à 08:56, Michael Hendry a écrit : I stopped using Frescobaldi and Lilypond at the beginning of the Covid pandemic and since then I have bought a new iMac with Monterey and transferred files across, Trying to get back up and running, I’ve installed Frescobaldi 3.1.3, which appears to be functioning perfectly, but I get these error reports: Starting lilypond 2.23.3 [dorothy.ly]... Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity Thanks, Jean. I know about dot-files, but overlooked the fact that in the Mac Finder directories are displayed before filenames, and I was looking among the dot-files! fonts.conf reads: I am also getting similar warnings on Fedora with LilyPond 2.22.2 (“unknown element reset-dirs”). They seem to be harmless. Apparently, the system's font configuration file for Fontconfig uses features that were not supported in the older version of Fontconfig that ships with LilyPond. For me, these warnings don't appear in 2.23.12, which is also the latest (unstable) version. Could you try upgrading to 2.23.12? Processing `/Users/michaelhendry/git_stuff/lilyjazz/examples/dorothy.ly' Parsing... Interpreting music...[8][16] fatal error: cannot find font: `lilyjazz-11' Exited with return code 1. when trying to compile the sample file “dorothy,ly”. Similar errors occur when I try to compile some of my existing Jazz leadsheets. That means you didn't install the LilyJazz font. It doesn't come with LilyPond, you had certainly installled it on your previous computer. Download it from here: https://github.com/OpenLilyPondFonts/lilyjazz (use Code > Download ZIP). How to install the files is described in the file LilyPond-Fonts-Installation-And-Usage.txt that you will find in your download. I found I don’t have /Applications/Lilypond.app directory. My copy of the lilypond executable was compiled by MacPorts. Googling for a way to create an App, I found: https://macappstore.org/lilypond/ And having gone through the whole process I’ve ended up with a 32-bit executable, which won’t work in the 64-bit-only Monterey environment. No need to have a LilyPond.app! This path /Applications/LilyPond.app is just what you have if you download LilyPond 2.22 from the official website, but any installation of LilyPond (not necessarily a .app installed through a .dmg) has a directory for fonts. You could just as well install the font in the path where MacPorts installed LilyPond (not sure where that is exactly, I don't know MacPorts well). I haven’t found a way to force Homebrew to compile a 64-bit executable so far. Is there a ready-built .DMG image file for version 2.23.12 that I can download? See the official download page: https://lilypond.org/development.html It's not a .dmg, but in fact simpler. The learning manual has a tutorial on installing it (it's the same link as in the other thread to see screenshots of how to tell Apple that it's malware-free): https://lilypond.org/doc/v2.23/Documentation/learning/graphical-setup-under-macos
Re: Configuration problems following new installation of Frescobaldi
On 30 Aug 2022, at 08:27, Jean Abou Samra wrote: > > Le 30/08/2022 à 08:56, Michael Hendry a écrit : >> >> I stopped using Frescobaldi and Lilypond at the beginning of the Covid >> pandemic and since then I have bought a new iMac with Monterey and >> transferred files across, >> >> Trying to get back up and running, I’ve installed Frescobaldi 3.1.3, which >> appears to be functioning perfectly, but I get these error reports: >> >> Starting lilypond 2.23.3 [dorothy.ly]... >> Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line >> 2: XML or text declaration not at start of entity >> Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line >> 2: XML or text declaration not at start of entity >> Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line >> 2: XML or text declaration not at start of entity >> Thanks, Jean. I know about dot-files, but overlooked the fact that in the Mac Finder directories are displayed before filenames, and I was looking among the dot-files! fonts.conf reads: > > > I am also getting similar warnings on Fedora with LilyPond 2.22.2 (“unknown > element reset-dirs”). They seem to be harmless. Apparently, the system's font > configuration file for Fontconfig uses features that were not supported in > the older version of Fontconfig that ships with LilyPond. For me, these > warnings don't appear in 2.23.12, which is also the latest (unstable) version. > Could you try upgrading to 2.23.12? > > >> >> Processing `/Users/michaelhendry/git_stuff/lilyjazz/examples/dorothy.ly' >> Parsing... >> Interpreting music...[8][16] >> fatal error: cannot find font: `lilyjazz-11' >> Exited with return code 1. >> >> when trying to compile the sample file “dorothy,ly”. Similar errors occur >> when I try to compile some of my existing Jazz leadsheets. >> > > > That means you didn't install the LilyJazz font. It doesn't > come with LilyPond, you had certainly installled it on your > previous computer. Download it from here: > > https://github.com/OpenLilyPondFonts/lilyjazz > > (use Code > Download ZIP). > > How to install the files is described in the file > LilyPond-Fonts-Installation-And-Usage.txt that you will find in > your download. I found I don’t have /Applications/Lilypond.app directory. My copy of the lilypond executable was compiled by MacPorts. Googling for a way to create an App, I found: https://macappstore.org/lilypond/ And having gone through the whole process I’ve ended up with a 32-bit executable, which won’t work in the 64-bit-only Monterey environment. I haven’t found a way to force Homebrew to compile a 64-bit executable so far. Is there a ready-built .DMG image file for version 2.23.12 that I can download? > >> There is no /Users/michaelhendry/.config directory on my computer, Of course there is! See my first paragraph above. Michael > > > It does exist, but since the name starts with a dot, it is a "hidden > directory". Those are reserved for things non-technically-savvy users > don't need/want to know about, and aren't displayed in the Finder by > default (but you can show them: > https://nordlocker.com/blog/how-to-show-hidden-files-mac/). > > Best, > Jean > >
Re: Export to XML
Dear all, Thank you for your comments about that situation. I tried what Jean suggested : 1) The XML export in Frescobaldi did work but the result was very unsatisfactory. I even tried to simplify as much as I could (erased all tweaks, custom commands, fingerings) and only kept the music notes. But still, the result when imported in Finale (2014) was terrible (some voices were displaced!). 2) I tried the OpenLilylib package. I wasn't familiar with that tool and had to struggle a bit with the installation. But still, with the export-example.ly seen in the manual, I get this error message: | GNU LilyPond 2.22.2 | Traitement de « export-example.ly » | Analyse... | | oll-core: library infrastructure successfully loaded. | Interprétation en cours de la musique... | init exportHumdrum: "export-example.krn" | init Staff 1 | init Voice 1/1 (1) | init Voice 1/2 (2) | init Staff 2 | init Voice 1/ (3) | init Voice 2/ (1) | init Voice 2/mel (2)/home/remy/.config/lilypond/openlilylib/lilypond-export/api.scm:278:48: In expression (ly:grob-properties grob): | /home/remy/.config/lilypond/openlilylib/lilypond-export/api.scm:278:48: Unbound variable: ly:grob-properties And I only get the PDF as an output. I don't know what I missed here? 3) I tried in the same old Finale version to import my PDF and I have to admit the result was for now the most satisfactory... I am pretty convinced now that Schott uses Sibelius as I read those fonts in some PDF examples they put online (maybe this will be of interest for some of you): | SchottMusicSibeliusStandard | SchottMusicSibeliusText | CenturySchoolbook-Bold | TimesNewRoman | OpusText | OpusFiguredBassStd | LinotypeSyntaxCom-Regular 4) I don't know if the fact I could not provide a workable file for them would be a deal breaker... I hope not as I "imagined" the work of a publishing company to be able to engrave from scratch any score... I could also mimic their own house styling in LilyPond, but I would be very surprised they ask for that and agree with Andrew, something would be wrong if so. So if I can't export in XML, my best bet would be for them to typeset from scratch, or to import the PDF in their own software and see if that can provide a good initial base... 5) To answer Andrew about the copyright and financial deal, I haven't received a concrete proposal yet and cannot say how it would appear. I know the incomes won't be very substantial, but still I see that as on opportunity to reach more people. But I would be curious to know what you meant by self-publishing? I, for sure, like to buy my scores on paper and that is an aspect I like in those old publishing companies... 6) Last point: I made some month ago, a short presentation and introduction to LilyPond for my colleagues in my music institution. Beyond the fact it was quite a challenge to try and convince them of the utility to take some time and learn that great tool, I received that question I couldn't answer at the time: is it possible to import or export in XML? I haven't have a use for that kind of feature until now, and I don't know how the commercial softwares handle that, but still, wouldn't that be a great argument to convince the people to go for it? Final thought, I don't know how Urs did manage to convince publishers about LilyPond and what responses he got (I would be curious though), but I am pretty sure that kind of limitation in importing/exporting in XML would be nowdays a dealbreaker for publishing companies, don't you agree?
Re: Export to XML
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: Configuration problems following new installation of Frescobaldi
Le 30/08/2022 à 08:56, Michael Hendry a écrit : I stopped using Frescobaldi and Lilypond at the beginning of the Covid pandemic and since then I have bought a new iMac with Monterey and transferred files across, Trying to get back up and running, I’ve installed Frescobaldi 3.1.3, which appears to be functioning perfectly, but I get these error reports: Starting lilypond 2.23.3 [dorothy.ly]... Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity I am also getting similar warnings on Fedora with LilyPond 2.22.2 (“unknown element reset-dirs”). They seem to be harmless. Apparently, the system's font configuration file for Fontconfig uses features that were not supported in the older version of Fontconfig that ships with LilyPond. For me, these warnings don't appear in 2.23.12, which is also the latest (unstable) version. Could you try upgrading to 2.23.12? Processing `/Users/michaelhendry/git_stuff/lilyjazz/examples/dorothy.ly' Parsing... Interpreting music...[8][16] fatal error: cannot find font: `lilyjazz-11' Exited with return code 1. when trying to compile the sample file “dorothy,ly”. Similar errors occur when I try to compile some of my existing Jazz leadsheets. That means you didn't install the LilyJazz font. It doesn't come with LilyPond, you had certainly installled it on your previous computer. Download it from here: https://github.com/OpenLilyPondFonts/lilyjazz (use Code > Download ZIP). How to install the files is described in the file LilyPond-Fonts-Installation-And-Usage.txt that you will find in your download. There is no /Users/michaelhendry/.config directory on my computer, It does exist, but since the name starts with a dot, it is a "hidden directory". Those are reserved for things non-technically-savvy users don't need/want to know about, and aren't displayed in the Finder by default (but you can show them: https://nordlocker.com/blog/how-to-show-hidden-files-mac/). Best, Jean
Configuration problems following new installation of Frescobaldi
I stopped using Frescobaldi and Lilypond at the beginning of the Covid pandemic and since then I have bought a new iMac with Monterey and transferred files across, Trying to get back up and running, I’ve installed Frescobaldi 3.1.3, which appears to be functioning perfectly, but I get these error reports: Starting lilypond 2.23.3 [dorothy.ly]... Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity Fontconfig error: "/Users/michaelhendry/.config/fontconfig/fonts.conf", line 2: XML or text declaration not at start of entity Processing `/Users/michaelhendry/git_stuff/lilyjazz/examples/dorothy.ly' Parsing... Interpreting music...[8][16] fatal error: cannot find font: `lilyjazz-11' Exited with return code 1. when trying to compile the sample file “dorothy,ly”. Similar errors occur when I try to compile some of my existing Jazz leadsheets. There is no /Users/michaelhendry/.config directory on my computer, and I suspect there is a configuration option which will deal with this error. Can anyone advise? Thanks in advance, Michael Hendry
