Creating book of separate pieces

Hi, I want to create a songbook of different songs, from various composers.Eacht piece should begin at a new page, with an own, compete, header I've looked at a number of places in the doc's, e.g. http://lilypond.org/doc/v2.22/Documentation/notation/multiple-scores-in-a-book, bu no luck so

Re: Achieving Certain Combination with Multiple Voices

Hi Omid, Am 05.10.21 um 15:20 schrieb Omid Mo'menzadeh: Hi all, The photo I attached is from Fernando Sor's "A la bonne heure" (No. 1), which I am engraving using Lilypond for a readable score. The following is how I did it, which

Re: Grace note too close

On Tue, 5 Oct 2021 at 21:06, Mahanidhi wrote: > > Your code works on all the notes but I want more room only beetween the grace note. > Here the minimal exemple. > Thank you. > > \version "2.22.1" > \language "english" > global = { > \key gf \major > \time 4/4 > \override Glissando.style =

Re: Achieving Certain Combination with Multiple Voices

Well, the notation already violates the idea of two voices. That said, I managed to generate similar output using only two voices like this: \new Staff = "guitar traditional" << \clef "treble_8" \time 3/8 \key e \minor % \mergeDifferentlyHeadedOn % \mergeDifferentlyDottedOn

Achieving Certain Combination with Multiple Voices

Hi all, The photo I attached is from Fernando Sor's "A la bonne heure" (No. 1), which I am engraving using Lilypond for a readable score. The following is how I did it, which certainly looks similar to the original photo: \version "2.22.1"

Re: Lilypond is now on Homebrew for macOS Mojave or higher (Intel or M1)

No problem, I was just pointing out the reasons why Guile 1.8.8 was not approved by the homebrew core. I even believe this will help advance Guile 2 compatibility, and certainly the Lilypond development community will pick up on any bugs. > To follow up on Jeans remarks: Maybe (if it's not

Re: Export from LilyPond to MusicXML (Thomas Morley)

Agreed, but it's possible that someone here might know more about this project and now it's getting on. Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com - Tuesday, October 5, 2021, 12:53:43 PM, m.tarensk...@kpnmail.nl wrote: > lilypond-to-musicxml export is

Re: Export from LilyPond to MusicXML (Thomas Morley)

lilypond-to-musicxml export is a frequentlly asked, but easier said than done, feature request, that pops up from time to time. And everytime it doesn't reach a point beyond discussions and experimental or quite incomplete implementations. Apparently both MusicXML and LilyPond are complex beasts -

Re: Tweaking glissando timing stems

Now with the attached example: When editing the example for the last time before sending it I noticed the second problem was only in the code I had written myself, and that the reproduction of it with your code had to do with another issue. In my case it probably have to do with some flaw in

Re: Tweaking glissando timing stems

Dear Harm and list! After almost two years I’m back using this code and found some things I would need help with. (I have done some additions to it, so it can hackishly handle additional noteheads on the stems/notecolumns and also tweaks rests passed by the glissando line, byt as I’m not very

Re: Lilypond is now on Homebrew for macOS Mojave or higher (Intel or M1)

Am 05.10.21 um 11:48 schrieb Jefferson Felix: I asked lilypond-devel before merging lilypond into homebrew, and they didn't notice known bugs with guile 2 - they already fixed all known issues. The strict homebrew core rules don't agree on using guile 1.8, unless severe bugs exist and make

Re: Export from LilyPond to MusicXML (Thomas Morley)

Sorry - edited subject to get the linking correct    Harm,     https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706  has a discussion about this as well. I've started looking at the OpenLilyLib solution at the bottom of the thread but it doesn't work on later

Re: Lilypond is now on Homebrew for macOS Mojave or higher (Intel or M1)

Le 05/10/2021 à 11:48, Jefferson Felix a écrit : I asked lilypond-devel before merging lilypond into homebrew, and they didn't notice known bugs with guile 2 - they already fixed all known issues. The Guile 2 transition is an effort that has spanned 10 years or so and taken a lot of pain.

Re: lilypond-user Digest, Vol 226, Issue 139

 Harm,     https://music.stackexchange.com/questions/42315/lilypond-to-musicxml-to-sibelius#73706  has a discussion about this as well. I've started looking at the OpenLilyLib solution at the bottom of the thread but it doesn't work on later versions of LilyPond.   It would seem to me that using

Re: Lilypond is now on Homebrew for macOS Mojave or higher (Intel or M1)

I asked lilypond-devel before merging lilypond into homebrew, and they didn't notice known bugs with guile 2 - they already fixed all known issues. The strict homebrew core rules don't agree on using guile 1.8, unless severe bugs exist and make it impossible to use (they don't have this version,

Re: Lilypond is now on Homebrew for macOS Mojave or higher (Intel or M1)

The Homebrew version will probably not be officially supported by the Lilypond team as it uses Guile 2, but it is a simple and elegant new way to install Lilypond. I'm not authorised to speak for the Lilypond team (which I'm not really a part of anyway), but maybe I can elaborate a bit:

Lilypond is now on Homebrew for macOS Mojave or higher (Intel or M1)

I am pleased to announce that Lilypond has just been added to the Homebrew package manager. >From now on, 64-bit macOS users (Intel or M1 processors) can install the latest stable version of Lilypond with the command: *brew install lilypond* This is a command-line version, similar to what