Re: lilypond-book executable
How did you install it? Here is what I get on my system: [david@Hopper ~]$ ll /usr/bin/lilypond-book -rwxr-xr-x. 1 root root 27690 Jan 20 19:01 /usr/bin/lilypond-book As you can see, it is executable. /David. On Fri, 12 Feb 2021 at 00:29, Luke Bang wrote: > Hi, > I just installed lilypond and according to the website I see that there's > a lilypond-book executable I can run in the Windows version. > I don't see this in the /usr/bin directory, but I do see some other file > by the name lilypond-book which is not an executable. Am I missing > something? > > Thanks, > Luke >
Re: Mass file linting
On Thu, 17 Dec 2020 at 21:59, Fr. Samuel Springuel wrote: > I’ve developed a large collection of music files over several years have > recently noticed that there are some stylistic formatting deviations in > some of them and so I’m looking for a tool that will check all my files for > these problems (and ideally fix them). I can do this in Frescobaldi using > Tools->Code Formatting->Format, but I’m looking for a command-line option > that I can use to fix my files en masse (and eventually incorporate into a > check-in hook on my git repositories to prevent this from happening > again). Does anyone have any suggestions for how to pull this off? > pip install python-ly ly "reformat" input.ly > output.ly That runs exactly the same that Frescobaldi does. More documentation: https://pypi.org/project/python-ly/ I found it poking around the Frescobaldi source, found something called reformat https://github.com/frescobaldi/frescobaldi/blob/f01cdbe2baee93f3ab361647a42885a1cfab6b40/frescobaldi_app/reformat.py#L46 That calls ly.reformat.reformat https://github.com/frescobaldi/python-ly/blob/master/ly/reformat.py#L102 /David.
Re: Poster for music engraving conference
On Thu, 5 Dec 2019, 1:41 am Andrew Bernard, wrote: > Hi All, > > I have seen lots of A0 posters for medical and scientific research > congresses. Here's an article that summarizes exactly what I think > about conference posters. > > https://colinpurrington.com/tips/poster-design/ That is a great article. I think it is a good idea to gather some statistics on what drew people to Lilypond, so I have made a quick and informal survey: https://docs.google.com/forms/d/e/1FAIpQLScAhjveMwqAD50YXLsWnclPILT2j20xaroeZ3QolAUFWRA_vA/viewform Hopefully, we can converge on a few things that make people start and stick to highlight on the poster. I am sure I am missing things, that is why I called it informal, so please add suggestions. I will add them to the options. > > >
Re: Poster for music engraving conference
Hi, I have some experience making posters for conferences, so I will share in case anyone is up for stepping up. For a conference, you want to focus the poster in one single idea that you want the reader to take home. What drew me to Lilypond was the essay, so that is what I would turn into a poster: http://lilypond.org/doc/v2.18/Documentation/essay-big-page.html It is visual, straightforward, and a good case for Lilypond. Once you have grabbed someone's attention, you may include one or two side stories. This must be short and sweet, but feel free to go into technical details. For example, the ability to engrave Gregorian chant, the possibility of arbitrarily expand it with Scheme code, or that you can write the notes in any language (yay! I don't have to spend time thinking what note D is!). The poster shouldn't necessarily stand on its own if someone is willing to be there during the poster session to explain and expand. You definitely don't want to put a cheat sheet or a manual because no one is going to learn Lilypond at the poster session, the goal is to make it memorable so they go home and learn it. Snippets are fine, but completeness is not required nor desirable. A personal workflow can be useful on the side, for someone already familiar with Lilypond or convinced of its coolness. Re-reading my email I realised I may sound a bit too harsh, so please do not take it badly, it wasn't meant like that. I have been to plenty of conferences with professional scientists, that are supposed to do this for a living, with terrible terrible posters. The result is that people just gloss over, and only the two people that were already interested (and likely knew the project) ever talk about it. Also, in an engineering students recruiting fair, I saw plenty of posters that seemed aimed at investors, so recruiters seem to be bad at this too. There are very few good examples to learn from in the wild. I hope this helps. /David. On Wed, 4 Dec 2019 at 15:10, wrote: > Werner: > > the music engraving conference in Salzburg (January 17.-19.) aims to > > present as much note engraving programs as possible. While some > > companies send representatives (e.g., Dorico, Capella, Finale) – some > > even with talks – we don't have something similar for LilyPond in the > > main part of the conference. > > > > Instead, we would like to have a poster (in A0 format) that shows how > > LilyPond works, together with some showcase results. > > > > Now my question: Are there people who are willing to produce such a > > poster? Has anyone already done something similar for other > > conferences? > > I could do a poster about my workflow and what features it brings me. > I'd also much like to attend but I cannot afford the travel expenses. > > Regarding lilypond in general I dont know what that kind of poster > would contain, the lerning manual in a poster format ? > > Regards, > /Karl Hammar > > > >
Re: Has LSR moved?
In the meantime, The Wayback machine has snapshots: https://web.archive.org/web/20190510220444/http://lsr.di.unimi.it/LSR/Browse I think the search functionality is broken, though. On Sat, 16 Nov 2019 at 09:39, Manuela wrote: > Do you know who owns LSR? > > Greetings, > Manuela > > > > -- > Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html > >
Re: Macro with
On Thu, 14 Nov 2019 at 12:47, Aaron Hill wrote: > Secondly, there's a quirk in variable substitution syntax. You need to > use the $var form, so the parser will see the ly:pitch? and ly:duration? > tokens as indicating a single note. > Ah, right. I understand now the manual means with "normal LilyPond input, using $ (in places where only Lilypond constructs are allowed) or # (to use it as a Scheme value or music function argument or music inside of music lists) to reference arguments (eg. ‘#arg1’)." So, every time the input type is ly:something, it should be with $, right? Thank you so much, now my source is almost readable, and so much quicker!
Re: Macro with
On Thu, 14 Nov 2019 at 10:05, Malte Meyn wrote:
> Am 14.11.19 um 10:02 schrieb David Menéndez Hurtado:
> > I am transcribing a piece that is filled with the rhythmic motif "8. 16
> > 8" at different pitches. Being a LaTeX user, I want to write a macro
> > like \myrithm{c a g}.
>
> Maybe http://lsr.di.unimi.it/LSR/Item?id=465 or
>
That seems to only allow the same note in the pattern.
> http://lsr.di.unimi.it/LSR/Item?id=654 is the right thing for you?
>
That looks more flexible, I think it would solve my immediate problem,
thank you very much.
The downside is that it looks more complicated, so I would also like to
learn to write the function myself. I think the docs can use a few more
examples, and I am happy to contribute them.
/David.
P.S.: sorry for the unfinished subject line.
Macro with
I am transcribing a piece that is filled with the rhythmic motif "8. 16 8"
at different pitches. Being a LaTeX user, I want to write a macro like
\myrithm{c a g}. I found the documentation for Scheme functions, and how to
edit whole music sections, but nothing on how to insert a fixed number of
pitches. As I understand it, ly:music is an arbitrary music expression, so
I cannot restrict it to just three pitches.
This is what I managed to put together, but doesn't quite work. Anyone can
suggest how to fix it?
/David.
\version "2.19.83"
\language "english"
myrithm =
#(define-music-function
(parser location first second third)
(first second third)
(ly:pitch? ly:pitch? ly:pitch?)
#{
#first 8. #second 16 #third 8
#})
\score {
<<
%\new Staff {\relative do' {\myrithm{c, d, e}}}
\new Staff {\time 6/8 \relative c' {c4. c \myrithm a' b e \myrithm {e
d c} c c c }} %Two different ways of calling it, neither works.
>>
\layout {
}
}
Re: Very weird output on any compilation
On Tue, 12 Nov 2019 at 20:24, Carl Sorensen wrote: > > > > > *From: *David Menéndez Hurtado > *Date: *Tuesday, November 12, 2019 at 12:18 PM > *To: *Carl Sorensen > *Cc: *"lilypond-user@gnu.org" > *Subject: *Re: Very weird output on any compilation > > > > > > > > Carl, you are correct. Changing it to 1200 fixes the problem. I will > investigate more and see if there is a good permanent fix. > > > > I think if you just leave it out (don’t have it set at all), it will take > the application default. Please give that a try. > > > > Thanks, > > > > Carl > You are correct. Now let's hope it doesn't mess anything else, it does say DO NOT EDIT at the top... Thank you all. > > >
Re: Very weird output on any compilation
On Tue, 12 Nov 2019 at 16:00, Carl Sorensen wrote: > > > > > *From: *David Menéndez Hurtado > *Date: *Tuesday, November 12, 2019 at 6:40 AM > *To: *Carl Sorensen > *Cc: *"lilypond-user@gnu.org" > *Subject: *Re: Very weird output on any compilation > > > > Thanks for all the tips. > > > > On Mon, 11 Nov 2019 at 22:13, Carl Sorensen wrote: > > Here’s a solution that worked in the past -- it describes how DPI settings > get set in fonconfig to 96 dpi, instead of 1200 (the lilypond default): > > https://lists.gnu.org/archive/html/bug-lilypond/2017-01/msg00022.html > > Carl > > > > My fontconfig already has it set to 96. I have another machine with the > same operative system and general settings, equally up to date, and there, > lilypond works fine (they are not a perfect mirror of each other). > > > > If I understand correctly, having it set to 96 is the exact problem. In > the link I posted, that 96 dpi setting is what needed to be done to > reproduce the problem. > > > > You could try eliminating the 96 dpi setting and see if that helps. > > > > Carl > > > > Carl, you are correct. Changing it to 1200 fixes the problem. I will investigate more and see if there is a good permanent fix.
Re: Very weird output on any compilation
Thanks for all the tips. On Mon, 11 Nov 2019 at 22:13, Carl Sorensen wrote: > Here’s a solution that worked in the past -- it describes how DPI settings > get set in fonconfig to 96 dpi, instead of 1200 (the lilypond default): > > https://lists.gnu.org/archive/html/bug-lilypond/2017-01/msg00022.html > > Carl > My fontconfig already has it set to 96. I have another machine with the same operative system and general settings, equally up to date, and there, lilypond works fine (they are not a perfect mirror of each other). To clarify my situation, anything I compile has that error, even if the version declared is the current one, and the failure happens from both frescobaldi and the command line. /David.
Very weird output on any compilation
I am having trouble compiling even the simplest of scores. For example, this is the template from Frescobaldi, compiled with lilypond from the command line: [image: Untitled.png] The output is the same for PNG and PDF. The same problem happens with any other score from Mutopia. Does anyone know what is going on? I have installed lilypond 2.19.83 from the Fedora repositories, and I am sure that is what is being used: $ which lilypond /bin/lilypond I have not messed with dynamic linking: $ echo $LD_LIBRARY_PATH (that is an empty string) I am attaching the compilation log when using loglevel DEBUG. For completeness, the template I used is also attached. Can anyone spot what is wrong here? Is there a way to keep the temporary files? That may hint what is wrong. Thank you /David. Log level set to 287 GNU LilyPond 2.19.83 Relocation: from PATH=/home/david/.virtualenv/py36/bin:/home/david/.local/bin:/home/david/bin:/usr/libexec/python3-sphinx:/home/david/.virtualenv/py36/bin:/home/david/.local/bin:/home/david/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/var/lib/snapd/snap/bin argv0=lilypond PATH=/usr/bin (prepend) Setting PATH to /usr/bin:/home/david/.virtualenv/py36/bin:/home/david/.local/bin:/home/david/bin:/usr/libexec/python3-sphinx:/home/david/.virtualenv/py36/bin:/home/david/.local/bin:/home/david/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/var/lib/snapd/snap/bin Relocation: compile datadir=, new datadir=/usr/share/lilypond//2.19.83 Relocation: framework_prefix=/usr/bin/.. Setting INSTALLER_PREFIX to /usr/bin/.. PATH=/usr/bin/../bin (prepend) Setting PATH to /usr/bin/../bin:/usr/bin:/home/david/.virtualenv/py36/bin:/home/david/.local/bin:/home/david/bin:/usr/libexec/python3-sphinx:/home/david/.virtualenv/py36/bin:/home/david/.local/bin:/home/david/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/var/lib/snapd/snap/bin Setting GUILE_MIN_YIELD_1 to 65 Setting GUILE_MIN_YIELD_2 to 65 Setting GUILE_MIN_YIELD_MALLOC to 65 Setting GUILE_INIT_SEGMENT_SIZE_1 to 10485760 Setting GUILE_MAX_SEGMENT_SIZE to 104857600 LILYPOND_DATADIR="/usr/share/lilypond/2.19.83" LOCALEDIR="/usr/share/locale" Effective prefix: "/usr/share/lilypond/2.19.83" PATH="/usr/bin/../bin:/usr/bin:/home/david/.virtualenv/py36/bin:/home/david/.local/bin:/home/david/bin:/usr/libexec/python3-sphinx:/home/david/.virtualenv/py36/bin:/home/david/.local/bin:/home/david/bin:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/var/lib/snapd/snap/bin" [] Guile 1.8 [/usr/share/lilypond/2.19.83/scm/lily-library.scm] [/usr/share/lilypond/2.19.83/scm/output-lib.scm] [/usr/share/lilypond/2.19.83/scm/markup-macros.scm] [/usr/share/lilypond/2.19.83/scm/parser-ly-from-scheme.scm] [/usr/share/lilypond/2.19.83/scm/file-cache.scm] [/usr/share/lilypond/2.19.83/scm/define-event-classes.scm] [/usr/share/lilypond/2.19.83/scm/define-music-callbacks.scm] [/usr/share/lilypond/2.19.83/scm/define-music-types.scm] [/usr/share/lilypond/2.19.83/scm/define-note-names.scm] [/usr/share/lilypond/2.19.83/scm/c++.scm] [/usr/share/lilypond/2.19.83/scm/chord-entry.scm] [/usr/share/lilypond/2.19.83/scm/skyline.scm] [/usr/share/lilypond/2.19.83/scm/markup.scm] [/usr/share/lilypond/2.19.83/scm/define-markup-commands.scm] [/usr/share/lilypond/2.19.83/scm/stencil.scm] [/usr/share/lilypond/2.19.83/scm/modal-transforms.scm] [/usr/share/lilypond/2.19.83/scm/chord-generic-names.scm] [/usr/share/lilypond/2.19.83/scm/chord-ignatzek-names.scm] [/usr/share/lilypond/2.19.83/scm/music-functions.scm [/usr/share/lilypond/2.19.83/scm/define-music-display-methods.scm] ] [/usr/share/lilypond/2.19.83/scm/part-combiner.scm] [/usr/share/lilypond/2.19.83/scm/autochange.scm] [/usr/share/lilypond/2.19.83/scm/define-music-properties.scm] [/usr/share/lilypond/2.19.83/scm/time-signature.scm] [/usr/share/lilypond/2.19.83/scm/time-signature-settings.scm] [/usr/share/lilypond/2.19.83/scm/auto-beam.scm] [/usr/share/lilypond/2.19.83/scm/chord-name.scm] [/usr/share/lilypond/2.19.83/scm/bezier-tools.scm] [/usr/share/lilypond/2.19.83/scm/define-context-properties.scm] [/usr/share/lilypond/2.19.83/scm/translation-functions.scm] [/usr/share/lilypond/2.19.83/scm/script.scm] [/usr/share/lilypond/2.19.83/scm/midi.scm] [/usr/share/lilypond/2.19.83/scm/layout-beam.scm] [/usr/share/lilypond/2.19.83/scm/parser-clef.scm] [/usr/share/lilypond/2.19.83/scm/layout-slur.scm] [/usr/share/lilypond/2.19.83/scm/font.scm] [/usr/share/lilypond/2.19.83/scm/encoding.scm] [/usr/share/lilypond/2.19.83/scm/bar-line.scm] [/usr/share/lilypond/2.19.83/scm/flag-styles.scm] [/usr/share/lilypond/2.19.83/scm/fret-diagrams.scm] [/usr/share/lilypond/2.19.83/scm/tablature.scm] [/usr/share/lilypond/2.19.83/scm/harp-pedals.scm] [/usr/share/lilypond/2.19.83/scm/define-woodwind-diagrams.scm]
