Re: More problems with hor. alignment of button numbers when misusing lyrics (for accordion)
On Wed, Jul 27, 2016 at 2:50 PM, Mojca Miklavecwrote: >> On Tue, Jul 26, 2016 at 1:23 PM, David Nalesnik >> wrote: >> This is exactly what happens. Here, the topmost LyricText is >> interpreted as the end of a melisma, and so left-aligned. > > Ahem ... > > -- > On 16 July 2016 at 00:17, David Nalesnik wrote: >> >> BTW, you have numerous warnings about LyricText caused by using "" >> instead of an underscore for skips. Corrected. > -- > "out of the frying pan into the fire..." Sorry, I learned that I've been misusing the underscore myself. And I picked the most labor-intensive way possible to find that out... David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: More problems with hor. alignment of button numbers when misusing lyrics (for accordion)
On 26 July 2016 at 21:21, David Nalesnikwrote: > On Tue, Jul 26, 2016 at 1:23 PM, David Nalesnik > wrote: >> On Tue, Jul 26, 2016 at 1:01 PM, David Nalesnik >> wrote: >>> On Tue, Jul 26, 2016 at 12:52 PM, David Nalesnik >>> wrote: >>> Something is messed up. >>> >>> >>> Same results in 2.18.2 and 2.19.45 (Win10) >>> >> >> Adding >> >> \set Lyrics.lyricMelismaAlignment = #CENTER >> >> appears to do the trick. Have to do some more study of Lyric_engraver >> to understand why and if this makes any sense whatsoever. >> > > *Arghh* > > As we read in > http://lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics: > > "Note: do not use an underscore, _, to skip notes – an underscore > indicates a melisma, causing the preceding syllable to be > left-aligned." Thank you. I went through that page a couple of times, but at the time I read it I wasn't even sure what melisma was. > This is exactly what happens. Here, the topmost LyricText is > interpreted as the end of a melisma, and so left-aligned. Ahem ... -- On 16 July 2016 at 00:17, David Nalesnik wrote: > > BTW, you have numerous warnings about LyricText caused by using "" > instead of an underscore for skips. Corrected. -- > Use \skip instead of _ and your problem is solved. This solves the problem. Interesting enough though, the underscore keeps (mis)aligning the text even if put in the next bar. Not that this is a problem. I'll try to consistently enter skips instead of "_", at least until I find a way to enter bottom-aligned column in some "humane" way. Initially I was using empty strings, but I was told that this was bad :) (I still don't quite understand the logic behind LilyPond's determination of spacing between staves when some "lyrics" is missing. This was part of the problem that David K. was confused about at well. But that's a different question.) In any case ... the horizontal alignment works now. Thank you, Mojca buttons-in-text.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange font change in v2.19.45
At 13:27 on 27 Jul 2016, Patrick Karl wrote: >Consider the following MWE: > [snip] >It produces the attached two pdf outputs. Note the font change for >composer, poet, instrumentName, and piece in Score2, while the font >used for those fields looks normal in Score1. > >This phenomenon seems to occur for any "book" past the first one. > >This phenomenon did not occur in v2.19.38. > >Is there a fix? Is this a bug? Seems to be fixed in git. I think it was issue 4918. -- Mark Knoop ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Strange font change in v2.19.45
Consider the following MWE: \version "2.19.45" \header { title = "My Title" composer = "My Composer" poet = "My Poet" } \paper { ragged-right = ##t } A = \relative g' { c1 } \book { \bookOutputSuffix "Score1" \score { \new Staff \with { instrumentName = "Alto" } \A \header { piece = "Score1" } \layout {} } } \book { \bookOutputSuffix "Score2" \score { \new Staff \with { instrumentName = "Alto" } \A \header { piece = "Score2" } \layout {} } } It produces the attached two pdf outputs. Note the font change for composer, poet, instrumentName, and piece in Score2, while the font used for those fields looks normal in Score1. This phenomenon seems to occur for any "book" past the first one. This phenomenon did not occur in v2.19.38. Is there a fix? Is this a bug? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book: warning: cannot detect textwidth from LaTeX
On Wed 27 Jul 2016 at 08:57:26 (+0200), Federico Bruni wrote: > The libraries error was due to some path and relocation problem, > because if I use Fedora lilypond package (/usr/bin) everything works > correctly. > > Except that the .tex file generated by lilypond-book is saved in > /tmp and when the .ly file is included it cannot find it. > What's wrong in the below .lytex file? > > > > $ which lilypond-book > /usr/bin/lilypond-book > > $ lilypond-book --include=/home/fede/Documenti/spartiti/ly > --output=out --pdf file.lytex > lilypond-book (GNU LilyPond) 2.19.45 > Reading file.lytex... > Running `pdflatex' on file `/tmp/tmpw7DwQy.tex' to detect default > page settings. > > Dissecting... > lilypond-book: error: file not found: 23.10.63.ly > > > > Why it's creating a .tex file in /tmp and calling pdflated on it? > According to the Usage manual¹, that commmand should generate a .tex > file and then _I_ should launch pdflatex. At the point your process stopped, it's barely begun. The file in /tmp will contain something like \nonstopmode \documentclass[a4paper]{article} \begin{document} \typeout{textwidth=\the\textwidth} \typeout{columnsep=\the\columnsep} \makeatletter\if@twocolumn\typeout{columns=2}\fi\makeatother \end{document} and normally it disappears in a flash. (I had to run while : ; do cat /tmp/tmp*.tex ; done in a captured session just to find that out.) The clue as to why it gets no further is in the error message. The bash functions I actually use to run LP and TeX keep things simple by changing into the appropriate directories, so start with everything in /tmp. Then change one thing at a time. Here's an example run of mine, using just the naked commands. I've inserted blank lines before each prompt (which prints the current directory): /tmp $ cat boo.lytex \documentclass[a4paper]{article} \begin{document} Documents for \verb+lilypond-book+ may freely mix music and text. For example, \begin{lilypond} \relative { c'2 e2 \tuplet 3/2 { f8 a b } a2 e4 } \end{lilypond} \lilypondfile[quote,noindent,line-width=15\cm]{bigger.ly} \end{document} /tmp $ cat bigger.ly { c' d' e' f' g' a' b' c'' g c' e' g' c'' e'' g'' c''' } /tmp $ lilypond-book --output=out --pdf boo.lytex lilypond-book (GNU LilyPond) 2.18.2 Reading boo.lytex... Running `pdflatex' on file `/tmp/tmpZjkSDV.tex' to detect default page settings. Dissecting... Writing snippets... Processing... Running lilypond... GNU LilyPond 2.18.2 Processing `snippet-map--1217663831.ly' Parsing... Processing `boo.lytex' Parsing... Renaming input to: `bigger.ly' Interpreting music... Preprocessing graphical objects... Calculating line breaks... Drawing systems... Layout output to `5a/lily-42767417.eps'... Converting to `5a/lily-42767417.pdf'... Layout output to `5a/lily-42767417-1.eps'... Converting to `5a/lily-42767417-1.pdf'... Writing 5a/lily-42767417-systems.texi... Writing 5a/lily-42767417-systems.tex... Writing 5a/lily-42767417-systems.count... Processing `boo.lytex' Parsing... Interpreting music... Preprocessing graphical objects... Calculating line breaks... Drawing systems... Layout output to `ac/lily-941a492d.eps'... Converting to `ac/lily-941a492d.pdf'... Layout output to `ac/lily-941a492d-1.eps'... Converting to `ac/lily-941a492d-1.pdf'... Writing ac/lily-941a492d-systems.texi... Writing ac/lily-941a492d-systems.tex... Writing ac/lily-941a492d-systems.count... Success: compilation successfully completed Linking files... Compiling /tmp/out/boo.tex... Writing `/tmp/out/boo.tex'... /tmp $ cd out /tmp/out $ lualatex boo.tex This is LuaTeX, Version beta-0.79.1 (TeX Live 2015/dev/Debian) (rev 4971) restricted \write18 enabled. (./boo.tex LaTeX2e <2014/05/01> Babel <3.9l> and hyphenation patterns for 44 languages loaded. (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2014/09/29 v1.4h Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg) (/usr/share/texlive/texmf-dist/tex/latex/pdftex-def/pdftex.def (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifluatex.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty) (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/luatex-loader.sty (/usr/share/texlive/texmf-dist/scripts/oberdiek/oberdiek.luatex.lua) No file boo.aux. (/usr/share/texlive/texmf-dist/tex/context/base/supp-pdf.mkii [Loading MPS to PDF converter (version 2006.09.02).] )
Re: How to set the beam positions manually?
On Wed, Jul 27, 2016 at 10:17 AM, Peter Terpstra [via Lilypond] < ml-node+s1069038n193169...@n5.nabble.com> wrote: > To prevent the Beam slope warning i would like to set the beam positions > manually. > > As it is suggested here: > https://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00435.html > > Anyone knows how to do this? > How about: \override Beam.positions = #'(y1 . y2) where y1 and y2 are relative to the center staff line in staff-space units. HTH, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/How-to-set-the-beam-positions-manually-tp193169p193170.html Sent from the User mailing list archive at Nabble.com.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
How to set the beam positions manually?
Dear readers, To prevent the Beam slope warning i would like to set the beam positions manually. As it is suggested here: https://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00435.html Anyone knows how to do this? Most kind regards, Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Is it possible to do this without the warning?
imj-muz...@bluewin.ch wrote: > You can safely switch to 2.19.44 I guess. > Thank you but would be more interested in how to set set the beam positions manually as is several times online suggested . Like here: https://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00435.html Kindly, Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tuplets in compound meter
On Wed 27 Jul 2016 at 07:57:29 (+0200), Malte Meyn wrote: > > > Am 26.07.2016 um 20:34 schrieb David Wright: > >>>What I didn't take into account is tuplet's optional argument for the > >>>tuplet spanner duration. > >Can you do this in compound time? What would be the syntax? > > Of course, you can use scaled and dotted durations like > \time 6/8 \tuplet 7/6 2. { … } > \time 9/8 \tuplet 10/9 8*9 { … } OK, then in answer to your: > I don’t have an idea for a good syntax here, any suggestions? I would suggest an extension of the present syntax: \tuplet [] / [] { } in other words: \tuplet % No new command, so it doesn't % trample on any other definitions. [] % Optional, can be quoted in case % it includes / or whitespace. / % Syntactically unambiguous because % of the obligatory /. []% Optional duration as at present. { } % As at present. This would print tuplets as at present, but each tuplet would have the string written against it instead of the normal default. The string could be as simple as 3 or even "" for nothing. What do you think? Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Midi entry
On Wed, 2016-07-27 at 11:56 +0200, Mojca Miklavec wrote: > On 27 July 2016 at 10:22, Richard Shann wrote: > > On Wed, 2016-07-27 at 00:25 +0200, Mojca Miklavec wrote: > >> On 26 July 2016 at 17:01, Richard Shann wrote: [...] > I don't mind that much if I have to go through midi2ly -> (some manual > editing) -> lilypond -> denemo lilypond->denemo would likely also be problematic, only working for a constrained syntax. If Denemo gets a more useful MIDI import then visualizing the problems and cleaning up would be easier, before generating the LilyPond syntax into your templates. Richard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Midi entry
On 27 July 2016 at 10:22, Richard Shann wrote: > On Wed, 2016-07-27 at 00:25 +0200, Mojca Miklavec wrote: >> On 26 July 2016 at 17:01, Richard Shann wrote: >> >> I realized that Denemo comes as a binary for Mac, so I tested it now, > > I wonder on which file? The one I sent you / the one you mentioned below. >> but it doesn't seem to like the original MIDI file. Not being familiar >> with its GUI interface, I'm completely confused, but after importing >> the MIDI and pressing play, I get some semi-nonsense out of it. > > with the "Se kiklco prodala bom.MID" file you sent it would not load at > all, because it didn't like .MID, changing that to .mid it loaded and This wasn't a problem on Mac :) > then I got the semi-nonsense you describe here: OK, so at least we are on the same page :) > yes, it seems to have nothing for chord recognition, well, it must have > recognized the chords as it has ignored the higher notes rather than > linearizing them (MIDI does not represent chords, it just puts all the > notes of the chord in one after the other with hopefully the same or > similar timings - Denemo must be noticing the same timings and > over-writing the note, which surprises me). >> it linearizes stuff, so I get weird alterations between >> the basses and the main melody > > yes, I heard that - again it is not so much Denemo that is linearizing > something, just that the bass and melody notes are in alternating > positions on the same track I'm just saying that midi2ly did a much much better job. >> but there is something horribly wrong with the import. > > yes! I'm fairly sure it is cruder than midi2ly, just a few lines of C I > think. But it does occasionally do the job - as in the first example of > yours that I tested, where I only had to delete the top staff and change > the Tenor and Bass to Bass clef to get a plausible score. What I provided was output from midi2ly from exactly the same midi file. I don't mind that much if I have to go through midi2ly -> (some manual editing) -> lilypond -> denemo -> (more manual editing) -> lilypond. But I guess I'll try to finish a crude the parser for lilypond notation and then do my own trickery with it, to suit the needs of the current problem at hand. (Or I might try a few more midi readers / interpreters / converters.) Mojca ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Create a \bookpart in a Scheme function
Oops… thansk Urs, really getting old! JM > Le 27 juil. 2016 à 10:03, Urs Liskaa écrit : > > > > Am 27.07.2016 um 09:47 schrieb Jacques Menu Muzhic: >> Strangely enough, I get two scores after the title page, i.e. three pages >> altogether. >> Any hint? > > Of course: there is one explicit bookpart (with note c) and one through > \makeBookpart (with note d). > > Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Midi entry
On Wed, 2016-07-27 at 00:25 +0200, Mojca Miklavec wrote: > On 26 July 2016 at 17:01, Richard Shann wrote: > > On Tue, 2016-07-26 at 15:45 +0200, Mojca Miklavec wrote: > > > > I think the first track is just being used to vary the tempo. Whether > > that is because it originated in a human performance (it would be a > > sophisticated program that generated this in that case) > > Yes, I agree :) > I suspect computers ... > > > or some sort of > > human-modified MIDI performance (you could easily "conduct" a MIDI > > performance causing the tempo to vary throughout and record the modified > > MIDI by adding a track with the tempo changes that you conducted). > > > >> In any case, I got reasonable output for at least some midi files with > >> > >> midi2ly -a --duration-quant=16 --key=-1 --start-quant=16 file.midi > > > > Interestingly, Denemo creates reasonable output straight out of the box > > - in many ways a measure of its crudity - it ignores all those tempo > > changes and so you get one empty staff and then the four parts. If that > > was a hard as it got, you could write a script to output the parts into > > your own templates quite easily. > > I realized that Denemo comes as a binary for Mac, so I tested it now, I wonder on which file? > but it doesn't seem to like the original MIDI file. Not being familiar > with its GUI interface, I'm completely confused, but after importing > the MIDI and pressing play, I get some semi-nonsense out of it. with the "Se kiklco prodala bom.MID" file you sent it would not load at all, because it didn't like .MID, changing that to .mid it loaded and then I got the semi-nonsense you describe here: > It > doesn't seem to be able to handle chords at all (it just ignores the > upper pitch), yes, it seems to have nothing for chord recognition, well, it must have recognized the chords as it has ignored the higher notes rather than linearizing them (MIDI does not represent chords, it just puts all the notes of the chord in one after the other with hopefully the same or similar timings - Denemo must be noticing the same timings and over-writing the note, which surprises me). > it linearizes stuff, so I get weird alterations between > the basses and the main melody yes, I heard that - again it is not so much Denemo that is linearizing something, just that the bass and melody notes are in alternating positions on the same track > (with durations of 8. instead of 4 and > 2), but the timings are all wrong. Not wrong in the sense of wrong > quantisation, MIDI can provide hints about the notation to use (4/4, 3/4 etc), and Denemo seems to take some of it on board - without knowing what it should look like it is difficult to say. > but there is something horribly wrong with the import. yes! I'm fairly sure it is cruder than midi2ly, just a few lines of C I think. But it does occasionally do the job - as in the first example of yours that I tested, where I only had to delete the top staff and change the Tenor and Bass to Bass clef to get a plausible score. > > By picking a guided import it does something completely different, but > still completely useless. Yes, that would be quite useless in this case - you would have to guide the import note by note of each track. It does have the chords in that case, you can see them as a series of input pitches all piled up at the same time in the score, you would choose the duration (if it wasn't right) and install them into a chord with the Ins key. Richard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Create a \bookpart in a Scheme function
Am 27.07.2016 um 09:47 schrieb Jacques Menu Muzhic: > Strangely enough, I get two scores after the title page, i.e. three pages > altogether. > Any hint? Of course: there is one explicit bookpart (with note c) and one through \makeBookpart (with note d). Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Create a \bookpart in a Scheme function
Hello folks, I tried to make the use of identifiers easier to follow, « book » being used everywhere, with the code below. Strangely enough, I get two scores after the title page, i.e. three pages altogether. Any hint? JM \version "2.19.44" makeBookpart = #(define-void-function (theBook)(ly:book?) (ly:book-add-bookpart! theBook #{ \bookpart { \score { \new Staff { d' } } } #})) #(let* ((myBook #{ \book { \bookpart { \markup "This is the title page" } %\include "bookpart.ly" inlined below \bookpart { \score { \new Staff { c' } } } } #})) #{ \makeBookpart #myBook #} (ly:book-process myBook #{ \paper {} #} ; non-functional, placeholder #{ \layout {} #} ; non-functional, placeholder (ly:parser-output-name)) ) %% > Le 26 juil. 2016 à 22:33, Urs Liskaa écrit : > > Hi Harm, > > > Am 26.07.2016 um 20:58 schrieb Thomas Morley: >> 2016-07-26 20:03 GMT+02:00 Urs Liska : >>> Hi all, >>> >>> one more of my recent confusing ideas: I would like to generate a number of >>> \bookpart-s in a Scheme function. The reason is that I have to loop over a >>> number of works and create scores for them that are in a bookpart each. >>> >>> Attached is something that resembles the structure I have in my actual >>> files. >>> >>> I successfully factored out the bookpart to an includable file. With this I >>> can produce multiple scores. However, it would be better to have that >>> factored out to a function because I have to set some values to select which >>> score to create, and this would be more natural to do as function arguments >>> rather than setting global variables and reading that from the code that >>> generates the scores. >>> >>> As the files are they compile finely, but when I uncomment the \makeBookpart >>> call I get >>> >>> /home/uliska/Aktuell/lily/bookpart-in-scheme-function/main.ly:23:9: error: >>> bad expression type >>> >>> \makeBookpart >>> >>> /home/uliska/Aktuell/lily/bookpart-in-scheme-function/main.ly:14:2: error: >>> error in #{ ... #} >>> >>> # (let* errors. Any suggestions how I can make the outer construct handle a >>> bookpart returned from a function? Thanks Urs >> >> Not sure I understood what your aiming, but maybe: >> >> \version "2.19.45" >> makeBookpart = >> #(define-void-function (book)(ly:book?) >> (ly:book-add-bookpart! >>book >>#{ \bookpart { \score { \new Staff { d' } } } #})) >> >> #(let* ((book >> #{ >> \book { >> \bookpart { \markup "This will be a title page" } >> \include "bookpart.ily" >> \include "bookpart.ily" >> } >> #})) >> #{ \makeBookpart #book #} >> (ly:book-process >>book >>#{ \paper {} #} ; non-functional, placeholder >>#{ \layout {} #} ; non-functional, placeholder >>(ly:parser-output-name))) >> >> HTH, >> Harm > > Yes, at least in the MWE your proposal does exactly what I need. And I > think I will be able to incorporate it perfectly in my original context. > > Thanks a lot > Urs > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book: warning: cannot detect textwidth from LaTeX
The libraries error was due to some path and relocation problem, because if I use Fedora lilypond package (/usr/bin) everything works correctly. Except that the .tex file generated by lilypond-book is saved in /tmp and when the .ly file is included it cannot find it. What's wrong in the below .lytex file? $ which lilypond-book /usr/bin/lilypond-book $ lilypond-book --include=/home/fede/Documenti/spartiti/ly --output=out --pdf file.lytex lilypond-book (GNU LilyPond) 2.19.45 Reading file.lytex... Running `pdflatex' on file `/tmp/tmpw7DwQy.tex' to detect default page settings. Dissecting... lilypond-book: error: file not found: 23.10.63.ly Why it's creating a .tex file in /tmp and calling pdflated on it? According to the Usage manual¹, that commmand should generate a .tex file and then _I_ should launch pdflatex. ¹ http://lilypond.org/doc/v2.19/Documentation/usage/invoking-lilypond_002dbook Il giorno lun 25 lug 2016 alle 8:59, Federico Bruniha scritto: Hi folks I've searched the archives but couldn't find an answer to this problem. I have a file.lytex file which contains these lines: %% \documentclass[a4paper]{article} \usepackage[utf8]{inputenc} \begin{document} \lilypondfile[noindent,line-width=15\cm]{23.10.63.ly} \end{document} %% I compile it with the below command. What's wrong with it? I set the width of the lilypond file, while the document width is already set by \documentclass. What else is missing? Thanks Federico $ make lilypond-book --include=/home/fede/Documenti/spartiti/ly --output=out file.lytex; lilypond-book (GNU LilyPond) 2.19.45 Reading file.lytex... Running `latex' on file `/tmp/tmphleGw3.tex' to detect default page settings. lilypond-book: warning: Unable to auto-detect default settings: latex: /home/fede/.local/lilypond/usr/lib/libz.so.1: no version information available (required by /lib64/libpng16.so.16) latex: /home/fede/.local/lilypond/usr/lib/libjpeg.so.62: no version information available (required by /lib64/libpoppler.so.58) latex: /home/fede/.local/lilypond/usr/lib/libtiff.so.5: no version information available (required by /lib64/libpoppler.so.58) latex: /home/fede/.local/lilypond/usr/lib/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /lib64/libpoppler.so.58) lilypond-book: warning: cannot detect textwidth from LaTeX Dissecting... lilypond-book: error: file not found: 23.10.63.ly Traceback (most recent call last): File "/home/fede/.local/lilypond/usr/bin/lilypond-book", line 789, in ? main () File "/home/fede/.local/lilypond/usr/bin/lilypond-book", line 772, in main chunks = do_file (files[0]) File "/home/fede/.local/lilypond/usr/bin/lilypond-book", line 611, in do_file chunks = find_toplevel_snippets (source, global_options.formatter) File "/home/fede/.local/lilypond/usr/bin/lilypond-book", line 362, in find_toplevel_snippets snip = klass (type, m, formatter, line_number, global_options) File "/home/fede/.local/lilypond/usr/share/lilypond/current/python/book_snippets.py", line 825, in __init__ global_options.include_path, global_options.original_dir)).read () File "/home/fede/.local/lilypond/usr/share/lilypond/current/python/book_base.py", line 27, in find_file exit (1) TypeError: 'str' object is not callable Makefile:20: recipe for target 'file.pdf' failed make: *** [file.pdf] Error 1 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user