Re: New Musescore

Le 24/10/2021 à 08:02, Brent Annable a écrit : Hi Everyone, Can anybody tell me how to actually use the new Leland font in lilypond? I went to the GitHub link and downloaded all the files, but as far as I can tell there are no Leland-11, Leland-13, Leland-14, etc. files. I downloaded the availab

Re: Multiple versions of Lilypond?

Kira Garvie writes: > What I was told is that there are some features on the back-end of the > program that turns the Lilypond scores into manipulatable scores for the > company that doesn't play well with some of the newer updates to Lilypond. Frankly that sounds like the company should budget

Re: New Musescore

Thanks Jean! Brent. On Sun, 24 Oct 2021 at 18:52, Jean Abou Samra wrote: > Le 24/10/2021 à 08:02, Brent Annable a écrit : > > Hi Everyone, > > > > Can anybody tell me how to actually use the new Leland font in lilypond? > I > > went to the GitHub link and downloaded all the files, but as far as

Re: Multiple versions of Lilypond?

Am So., 24. Okt. 2021 um 12:29 Uhr schrieb David Kastrup : > > Kira Garvie writes: > > > What I was told is that there are some features on the back-end of the > > program that turns the Lilypond scores into manipulatable scores for the > > company that doesn't play well with some of the newer upd

Re: Multiple versions of Lilypond?

Thomas Morley writes: > Am So., 24. Okt. 2021 um 12:29 Uhr schrieb David Kastrup : >> >> Kira Garvie writes: >> >> > What I was told is that there are some features on the back-end of the >> > program that turns the Lilypond scores into manipulatable scores for the >> > company that doesn't play

Re: Start, end, gradient of Glissando

Am So., 24. Okt. 2021 um 01:18 Uhr schrieb Aaron Hill : > > On 2021-10-23 5:17 am, Thomas Morley wrote: > > Any hints? > > normalized-endpoints > > Your Y-left and Y-right are the extreme values that have not been > interpolated using the values from normalized-endpoints. Borrowing > logic from Li

Re: Multiple versions of Lilypond?

On Sat, Oct 23, 2021 at 3:38 PM Kira Garvie wrote: > > Hi all, > I saw this referenced in the Frescobaldi manual, but is it possible to have > multiple versions of Lilypond installed on my computer at once? Many of you > know I have to use version 2.16.2 for my work (don't ask me why, I honestly

Re: Start, end, gradient of Glissando

On 2021-10-24 6:22 am, Thomas Morley wrote: Though, how could I have found it myself? My lack of C++-knowledge hinders me to understand the "logic from Line_spanner::print". I usually learn things from looking at scheme-codings. Not sure it would have been clear without digging into the print

Putting finger substitution in the LilyPond manual

In this thread (1) we discussed how to notate the piano technique of holding down one note and changing fingers without releasing the note. Wikipedia calls this "substitution." (2) I would like to put a section in the manual that explains how to notate this. It seems to be a fairly common thing i

Re: Multiple versions of Lilypond?

Op 24-10-2021 om 15:51 schreef Knute Snortum: On Sat, Oct 23, 2021 at 3:38 PM Kira Garvie wrote: Hi all, I saw this referenced in the Frescobaldi manual, but is it possible to have multiple versions of Lilypond installed on my computer at once? Many of you know I have to use version 2.16.2 fo

Re: Start, end, gradient of Glissando

Am So., 24. Okt. 2021 um 16:35 Uhr schrieb Aaron Hill : > > On 2021-10-24 6:22 am, Thomas Morley wrote: > > Though, how could I have found it myself? > > My lack of C++-knowledge hinders me to understand the "logic from > > Line_spanner::print". I usually learn things from looking at > > scheme-cod

Re: Putting finger substitution in the LilyPond manual

> Any thoughts on this? Just provide a patch on the development repository at this point. It is easier to discuss specifics with concrete material. The contributor's guide has all you need to know, and feel free to ask for assistance with Git, Texinfo or anything. Thanks in advance. Jean

Re: Start, end, gradient of Glissando

> Let me take a stab at converting the print routine to Scheme. The workaround on issue #6198 may provide a useful start. Best, Jean

RE: Putting finger substitution in the LilyPond manual

Knute, Some instructions are here https://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff#fingering-instructions although it refers mainly to stringed instrument. Mark -Original Message- From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Be

Re: Start, end, gradient of Glissando

On 2021-10-24 8:05 am, Thomas Morley wrote: Am So., 24. Okt. 2021 um 16:35 Uhr schrieb Aaron Hill Let me take a stab at converting the print routine to Scheme. Would be great !! Sorry for the delay... took me some time to figure out why there was an error with cross-staff right-side Y coord

Re: Putting finger substitution in the LilyPond manual

On Sun, Oct 24, 2021 at 8:46 AM Mark Stephen Mrotek wrote: > > Knute, > > Some instructions are here > https://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff#fingering-instructions > although it refers mainly to stringed instrument. Thank you Mark. So no need for a new section, b

Re: Putting finger substitution in the LilyPond manual

Actually the discussed solutions here are arguably better than the documentation example, because that one simply uses a markup event instead of a fingering event, which will cause problems in positioning. Cheers, Valentin 24.10.2021 18:32:32 Knute Snortum : > On Sun, Oct 24, 2021 at 8:46 AM M

Re: Putting finger substitution in the LilyPond manual

On 10/24/21, 10:33 AM, "lilypond-user on behalf of Knute Snortum" wrote: On Sun, Oct 24, 2021 at 8:46 AM Mark Stephen Mrotek wrote: > > Knute, > > Some instructions are here > https://lilypond.org/doc/v2.22/Documentation/notation/inside-the-staff#fingering-instruc

Markup with long notes spacing

I've been struggling with spacing issues. In my example below, the second measure shows the default behavior, where the two markups are placed on top of each other. (If I was playing this, I would find it very confusing.) I would like to stretch the long note in the beginning of second measure,

Re: Placing text on multi-voice part

On Sat 23 Oct 2021 at 12:24:34 (+0200), Jogchum Reitsma wrote: > Op 23-10-2021 om 03:10 schreef David Wright: > > On Fri 22 Oct 2021 at 17:22:16 (+0200), Jogchum Reitsma wrote: > > > > > I get the attached screenshot. > > > > > > But I would expect (and want...) the text snippet "ste"placed on th

Re: Multiple versions of Lilypond?

On Sat 23 Oct 2021 at 16:33:59 (-0700), Aaron Hill wrote: > On 2021-10-23 3:58 pm, Kira Garvie wrote: > > What I was told is that there are some features on the back-end of the > > program that turns the Lilypond scores into manipulatable scores > > for the > > company that doesn't play well with s

Re: Markup with long notes spacing

It may be a cheat, but in that sort of situation I just add invisible notes to put the space where necessary. In your example I removed the TextLength directives and changed your "othernotes" to: othernotes = \relative c'{ e8 f g a g2 << c2 \\ { \hideNotes a8 a a a } >> b2 } The hidden quavers

Re: Putting finger substitution in the LilyPond manual

On Sun, Oct 24, 2021 at 10:22 AM Carl Sorensen wrote: > > I think this should be a snippet, rather than text in a section. Rather than > telling, just show (and one can show three different methods in one snippet). > > The snippet could be as simple as: > > \version "2.21" > > \header { > lsrt

Re: Putting finger substitution in the LilyPond manual

Just add the snippet to Documentation/snippets/New Carl Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone Get Outlook for Android From: Knute Snortum Sent: Sunday, October 24, 2021 12:27:47 PM To: Carl Sorensen Cc: Mark St

Re: Start, end, gradient of Glissando

Am So., 24. Okt. 2021 um 18:19 Uhr schrieb Aaron Hill : > > On 2021-10-24 8:05 am, Thomas Morley wrote: > > Am So., 24. Okt. 2021 um 16:35 Uhr schrieb Aaron Hill > >> Let me take a stab at converting the print routine to Scheme. > > > > Would be great !! > > Sorry for the delay... Delay? I noticed

Re: Multiple versions of Lilypond?

On 2021-10-24 11:06 am, David Wright wrote: Perhaps this is one example where drag-and-drop comes into its own, rather than double-clicking documents. You just drag the LP document onto the appropriate icon representing a specific version of LP. Do you know how that is configured, again not distu

Re: Markup with long notes spacing

Sure, using "hideNotes" to obtain better spacing is a cheat, but it works better than anything I tried. (I actually tried a similar thing but with spacer rests which did not produce the wanted result.) Thanks! Erika

Re: Markup with long notes spacing

On 2021-10-24 10:56 am, Erika Pirnes wrote: I thought "textLenghtOn" would solve my problems but it seemingly just moves them somewhere else, here the other part (see first measure of the example). I also tried experimenting with "SpacingSpanner.base-shortest-duration" but it doesn't solve the pr

Re: Markup with long notes spacing

I changed Paul's solution with "hideNotes" to use rests instead of notes, to avoid the warning for clashing note columns. Aaron's solution works well for the score, but my problem came up when I tried to write the individual parts. The updated example below illustrates the problem and my solutio

Re: Markup with long notes spacing

Actually, it seems that my previous solution with "hideNotes" and rests leads to collisions as well, and it also shifts down any dynamic markings below the staff, which is not a desirable effect. I'm grateful for any suggestions on how to solve the problem. Again, the issue is that using textLe

Re: Tweaking glissando timing stems

Dear Harm! I am very thankful for and moved by the effort you’re putting into this! One feature I would find useful would be the ability to make chords with one ”gliss-note” and one regular notehead. I implemented this (not entirely successfully) on top of an earlier version of your code by mak

Re: Markup with long notes spacing

On 2021-10-24 2:44 pm, Erika Pirnes wrote: Again, the issue is that using textLengthOn works well with score, but in the individual parts either the short notes get stretched weirdly (if I use textLengthOn with those) or markups above long notes are positioned on top of each other (if I don't use