Re: spurious second treble clef sign, what did I do wrong this time?

2023-02-20 Thread Kenneth Wolcott
Thank you, Leo. I already had "\grace {s16*3} s1" in the second lh voice, apparently needed in the the second rh voice? Thanks, Ken On Mon, Feb 20, 2023 at 11:42 PM Leo Correia de Verdier wrote: > > I haven’t been able to open your .ly file since I’m on the telephone, but > that should be a

Re: spurious second treble clef sign, what did I do wrong this time?

2023-02-20 Thread Leo Correia de Verdier
I haven’t been able to open your .ly file since I’m on the telephone, but that should be an issue 34. Add s8. right after the clef and time signature in the right hand, so that the grace note timing matches between the different staves and voices and the extra clefs and time signatures will d

Re: move chords closer to notes

2023-02-20 Thread Jean Abou Samra
Le mardi 21 février 2023 à 03:55 +0100, mi...@orbelanet.com a écrit : > Hi everyone, > when I write the chords together with one or several melodies, the > chords form a horizontal line, in such a way that if the range of the > melody is very wide, some chords end up being very far from the > notes

move chords closer to notes

2023-02-20 Thread mikel
Hi everyone, when I write the chords together with one or several melodies, the chords form a horizontal line, in such a way that if the range of the melody is very wide, some chords end up being very far from the notes. I attach a sample of the .ly file along with its pdf, where you can see

Re: Lilypond zip file doesn't include the lilypond app?

2023-02-20 Thread Jean Abou Samra
Hello Benjamin, Welcome to this list. So you know, your message was manually approved because you are not a list subscriber. Please subscribe on [https://lists.gnu.org/mailman/listinfo/lilypond-user](https://lists.gnu.org/mailman/listinfo/lilypond-user) in order to fix this (you can choose not t

Lilypond zip file doesn't include the lilypond app?

2023-02-20 Thread Benjamin Wilson
Dear GNU project, I recently downloaded Lilypond for Mac. It downloads as a zip file, but after I unzip the files I cannot locate an actual application that I can open. I see all kinds of supplements, but I can't actually find the application at all. I am running Ventura 13, so my system is up to

Re: Determining requested output files

2023-02-20 Thread Fr. Samuel Springuel
> On Feb 20, 2023, at 7:33 AM, Jean Abou Samra wrote: > > (Adding back the list) Sorry about losing the list. > > Le dimanche 19 février 2023 à 12:46 -0500, R. Padraic Springuel a écrit : > >> It’s part of my system for having make automatically figure out dependencies >> when running Lily

Re: Default value of top-margin setting

2023-02-20 Thread Paolo Prete
Thanks to you and Aaron! On Mon, Feb 20, 2023 at 10:37 PM Valentin Petzel wrote: > Hello Paolo, > > the default value for top-margin is set in > > ly/paper-defaults-init.ly > > Currently this is 10mm scaled to the selected paper size (so for the > default > paper size (A4) this is 10mm, for othe

Re: Default value of top-margin setting

2023-02-20 Thread Valentin Petzel
Hello Paolo, the default value for top-margin is set in ly/paper-defaults-init.ly Currently this is 10mm scaled to the selected paper size (so for the default paper size (A4) this is 10mm, for other sizes this is scaled accodingly). Cheers, Valentin Am Montag, 20. Februar 2023, 22:30:51 CET s

Re: Default value of top-margin setting

2023-02-20 Thread Aaron Hill
On 2023-02-20 1:30 pm, Paolo Prete wrote: Hello, Regarding the top-margin setting of the \paper block, where can I find its default value(s) for the various versions (2.20.x, 2.21.x, 2.22.x etc.) ? I think you are looking for top-margin-default defined in paper-defaults-init.ly. -- Aaron

Default value of top-margin setting

2023-02-20 Thread Paolo Prete
Hello, Regarding the top-margin setting of the \paper block, where can I find its default value(s) for the various versions (2.20.x, 2.21.x, 2.22.x etc.) ? Thanks!

Re: I did not previously realize that Lilypond would automatically update pre-existing scores

2023-02-20 Thread Jean Abou Samra
Le samedi 18 février 2023 à 22:19 +0100, Jean Abou Samra a écrit : > Le samedi 18 février 2023 à 22:09 +0100, Valentin Petzel a écrit : > > > I do think that even in this case Lilypond should > > issue a warning. > > https://www.mail-archive.com/lilypond-devel@gnu.org/msg78847.html [https://g

Re: Avoid double beaming

2023-02-20 Thread Valentin Petzel
Hello Jogchum, you will see that \partCombine does make very basic decisions, so often you will find yourself in need to manually intervene (often this is not a question about adding slurs to each voice). In case you want to force a particular behaviour use one of the commands \partCombineApar

Re: Avoid double beaming

2023-02-20 Thread Jogchum Reitsma
Op 20-02-2023 om 12:24 schreef Xavier Scheuer: On Mon, 20 Feb 2023 at 12:15, Jogchum Reitsma wrote: > > This gives the result I would like to see (well, almost: the first bar still has separated stems/beams, but that's nitpicking). > > I applied it to the piece the snippet was an excerpt from,

Re: Determining requested output files

2023-02-20 Thread Jean Abou Samra
(Adding back the list) Le dimanche 19 février 2023 à 12:46 -0500, R. Padraic Springuel a écrit : > It’s part of my system for having make automatically figure out dependencies > when running LilyPond:  > [https://github.com/rpspringuel/lilypond_make/tree/GNUmake_dependencies](https://github.com/r

Re: Avoid double beaming

2023-02-20 Thread Xavier Scheuer
On Mon, 20 Feb 2023 at 12:15, Jogchum Reitsma wrote: > > This gives the result I would like to see (well, almost: the first bar still has separated stems/beams, but that's nitpicking). > > I applied it to the piece the snippet was an excerpt from, and it renders beautifully. > > Thanks a lot! Hel

Re: Avoid double beaming

2023-02-20 Thread Jogchum Reitsma
Op 20-02-2023 om 11:13 schreef Xavier Scheuer: On Mon, 20 Feb 2023 at 10:44, Jogchum Reitsma wrote: > > Hi, > > In below snippet, lilypond renders two beams for the two voices, and, > because I want the stems to have the same direction, > the result for the 8th-notes is that they seem to be 16th

Re: Avoid double beaming

2023-02-20 Thread Jogchum Reitsma
Op 20-02-2023 om 11:59 schreef Valentin Petzel: Hi Jogchum, please keep it on the list! Not for the first time I stand corrected here, apologies! The first one does exactly what it states it does, it creates two voices. The second one does what you actually want, which is a single voice featu

Re: Avoid double beaming

2023-02-20 Thread Valentin Petzel
Hi Jogchum, please keep it on the list! The first one does exactly what it states it does, it creates two voices. The second one does what you actually want, which is a single voice featuring all notes as chords. If you have different rhythms you’ll need to combine these approaches and employ

Re: Avoid double beaming

2023-02-20 Thread Xavier Scheuer
On Mon, 20 Feb 2023 at 10:44, Jogchum Reitsma wrote: > > Hi, > > In below snippet, lilypond renders two beams for the two voices, and, > because I want the stems to have the same direction, > the result for the 8th-notes is that they seem to be 16th notes. > > Is there a way to avoid this, and to

Re: Avoid double beaming

2023-02-20 Thread Valentin Petzel
Hi Jogchum, the reason for your issues is that you are using voice 2 (i.e. lowest voice) with a \stemUp, which will cause issues to resolve collision. Generally you should avoid using \stemUp and \stemDown unless you really need to use it and rather use the correct Voice. If you were to use \v

Avoid double beaming

2023-02-20 Thread Jogchum Reitsma
Hi, In below snippet, lilypond renders two beams for the two voices, and, because I want the stems to have the same direction, the result for the 8th-notes is that they seem to be 16th notes. Is there a way to avoid this, and to join the two beams to one? Thanks in advance!, regards, Jogchum