Re: Rate this snippet | Repeat with volta marks in unfolded scores

Hi Lucas, I would not alter much beyond what you have if the current code works perfectly for your purpose (I think what you have is quite cool, though from the notational standpoint, instead of "[number]°v.:”, I would simply use “([number])” for simplicity’s sake, but that’s just my personal c

Re: Rate this snippet | Repeat with volta marks in unfolded scores

I've tried the snippet on some other code and found it faulty while working with multi part instrument system. So I've tried to change some of the \textMark and \textEndMark to \markup where it is useful. The snippet is discriminated with start and end in the example. Note to

Rate this snippet | Repeat with volta marks in unfolded scores

ors. So today I co-wrote (with ChatGPT's help) a snippet that does exactly what I wanted: the volta repetitions are indicated without the need for markups. I guess this isn't "vibe coding" (especially because I reviewed the code, making sure it runs), but my knowledge of

Re: History of an LSR snippet

Hi David, > IIRC, that snippet originally had a different purpose than it does now; I > think it began as a way to move each lyric syllable so that its first vowel > is centered on the notehead. For a contrived example, it would move the > syllable "Shhhow!" so that t

History of an LSR snippet

Hello There's a snippet at https://lsr.di.unimi.it/LSR/Snippet?id=888 IIRC, that snippet originally had a different purpose than it does now; I think it began as a way to move each lyric syllable so that its first vowel is centered on the notehead. For a contrived example, it would mov

New LSR snippet 1187 "New pitch language"

To the author of the new LSR snippet 1187 "New pitch language" https://lsr.di.unimi.it/LSR/Item?u=1&id=1187 You add your new language to "nederlands", thus \language "alpha" returns a warning: warning: Could not find language `alpha'. Ignoring. Please f

Re: Organ pedal marks in various styles, including pedal glides: new snippet 1184

-foot organ pedal substitutions; >- >https://lists.gnu.org/archive/html/lilypond-user/2016-11/msg00087.html, >follow-up: organ pedal toe-to-heel-shift. > > > I've created a snippet to address this. It allows you to pick the pedal > mark style: > >- Li

Organ pedal marks in various styles, including pedal glides: new snippet 1184

-user/2016-05/msg00206.html, question about same-foot organ pedal substitutions; * https://lists.gnu.org/archive/html/lilypond-user/2016-11/msg00087.html, follow-up: organ pedal toe-to-heel-shift. I've created a snippet to address this. It allows you to pick the pedal mark style: * L

Re: Snippet: Adding indicators to staves which split after a break

>> The easy question. The fourth line of the snippet reads: >>(PI_OVER_180 (/ (atan2 1 1) 34)) >> Surely that “34” should be “45”. > > Did you try changing it? ;) Yes. It breaks things slightly. I need to dive further down the rabbit-hole to work out why. >&g

Re: Snippet: Adding indicators to staves which split after a break

Hi Kevin, > I have two questions about this snippet: You forgot to include the snippet or a link! :) But I assume you mean https://lilypond.org/doc/v2.25/Documentation/snippets/vocal-music_003a-adding-indicators-to-staves-which-get-split-after-a-break > The easy question. The fourth l

Snippet: Adding indicators to staves which split after a break

I have two questions about this snippet: The easy question. The fourth line of the snippet reads: (PI_OVER_180 (/ (atan2 1 1) 34)) Surely that “34” should be “45”. The more difficult question. This snippet adds two arrows to the bar line at the end of the staff. I have a case where there is

Re: snippet

On 11/03/2024 16:54, Gian Paolo Renello wrote: HI, I searched on lilypond site a way to rewrite a SATB on 2 staves, but i am not able to got it... Does any one have a clue on it? Thanks a lot Gian Paolo Here is the image i got form the score. Look at \partCombine. I use it to generate a s

Re: snippet

Hello Gian, I believe this is what you are looking for: https://lilypond.org/doc/v2.24/Documentation/learning/satb-vocal-score Looking at your example, you might need to look at https://lilypond.org/doc/v2.24/Documentation/notation/multiple-voices, as you have more than two voices per staff

Re: LyricExtender snippet: still the best way?

> Le 22 juin 2023 à 19:03, Kieren MacMillan a > écrit : > > Now… Is there any benefit to this — or something similar — being rolled into > the main codebase? If so, maybe it’s the perfect size for my first MR > [finally!]? It should be rather easy, but the lyric extender code is in C++ (

Re: LyricExtender snippet: still the best way?

Hi Jean, > Indeed, you can put it in stencil: I just *knew* grob-transformer would be the thing! Now… Is there any benefit to this — or something similar — being rolled into the main codebase? If so, maybe it’s the perfect size for my first MR [finally!]? Thanks, Kieren. _

Re: LyricExtender snippet: still the best way?

Le jeudi 22 juin 2023 à 09:14 -0400, Kieren MacMillan a écrit : > Hi all, > > The callback shown in this snippet is something that is automatically > included in all my engravings that include lyrics; it is designed to remove > LyricExtenders that fall below a minimum-length thr

LyricExtender snippet: still the best way?

Hi all, The callback shown in this snippet is something that is automatically included in all my engravings that include lyrics; it is designed to remove LyricExtenders that fall below a minimum-length threshold. Is the given code still the best way to accomplish what I want? In particular, I

Re: question to generating random pitches snippet

Dear Jean, thanks for Your answer. I understand now! Am Di., 13. Juni 2023 um 16:43 Uhr schrieb Jean Abou Samra < j...@abou-samra.fr>: > Le mardi 13 juin 2023 à 16:34 +0200, Stefan Thomas a écrit : > > Exactly. Sorry I've forgotten to send the link. > > > The sn

Re: question to generating random pitches snippet

Le mardi 13 juin 2023 à 16:43 +0200, Jean Abou Samra a écrit : > Le mardi 13 juin 2023 à 16:34 +0200, Stefan Thomas a écrit : > > Exactly. Sorry I've forgotten to send the link. > > The snippet contains the expression > > (random 12 random-state) > > meaning th

Re: question to generating random pitches snippet

Le mardi 13 juin 2023 à 16:34 +0200, Stefan Thomas a écrit : > Exactly. Sorry I've forgotten to send the link. The snippet contains the expression (random 12 random-state) meaning that a random pitch between c' and 11 steps higher (i.e., g'') is chosen. You can change

Re: question to generating random pitches snippet

community, > >> I discovered the snippet that lets you generate random pitches in > Lilypond. > >> How does Lilypond "know" what are the lowest, what are the highest > pitches? > >> How could I change that? > > > > > > > >Which snip

Re: question to generating random pitches snippet

On 13 Jun 2023 16:12, Jean Abou Samra wrote: >Le mardi 13 juin 2023 à 15:56 +0200, Stefan Thomas a écrit : >> Dear community, >> I discovered the snippet that lets you generate random pitches in Lilypond. >> How does Lilypond "know" what are the lowest, what

Re: question to generating random pitches snippet

Le mardi 13 juin 2023 à 15:56 +0200, Stefan Thomas a écrit : > Dear community, > I discovered the snippet that lets you generate random pitches in Lilypond. > How does Lilypond "know" what are the lowest, what are the highest pitches? > How could I change that? Which s

question to generating random pitches snippet

Dear community, I discovered the snippet that lets you generate random pitches in Lilypond. How does Lilypond "know" what are the lowest, what are the highest pitches? How could I change that? Thanks for Your help Stefan

Re: Snippet: automatic reminder text for mutes/techniques

I assumed that if the instrument is playing continuously, no reminder text is needed. Did you have a scenario in mind where reminders would be useful even without measures of rest? Or, did you mean that instead of rests you are using spacers? I think this snippet should work fine for that use

Re: Snippet: automatic reminder text for mutes/techniques

What if you don't have any rests? Andrew On 27/01/2023 1:00 pm, Saul Tobin wrote: Attached is a snippet that keeps track of these instructions and automatically prints reminder text after a set number of measures of rest.

Snippet: automatic reminder text for mutes/techniques

Hi all, I have always felt one of the more annoying proofreading tasks for instrumental music is ensuring that technique instructions such as mutes are properly cancelled. Attached is a snippet that keeps track of these instructions and automatically prints reminder text after a set number of

Re: Error when compiling snippet "Parenthesize a group of notes using a Scheme function"

Kieren MacMillan wrote: Hi Joseph, If you use convert-ly on your files, it will update ParenthesesItem to Parentheses, which will eliminate the error. Yes, but: The LSR snippets don't have a \version statement. If convert-ly doesn't help, insert the line \version "2.22.0" and try again. C

Re: Error when compiling snippet "Parenthesize a group of notes using a Scheme function"

On Fri, Dec 16, 2022 at 11:48 AM Joseph Srednicki wrote: > I am running Lilypond 2.24.0 on Windows 11. > > I am trying the use the snippet entitled "Parenthesize a group of notes > using a Scheme function" located at > https://lsr.di.unimi.it/LSR/Snippet?id=902. &g

Re: Error when compiling snippet "Parenthesize a group of notes using a Scheme function"

Hi Joseph, If you use convert-ly on your files, it will update ParenthesesItem to Parentheses, which will eliminate the error. Hope that helps! Kieren.

Error when compiling snippet "Parenthesize a group of notes using a Scheme function"

I am running Lilypond 2.24.0 on Windows 11. I am trying the use the snippet entitled "Parenthesize a group of notes using a Scheme function" located at https://lsr.di.unimi.it/LSR/Snippet?id=902. I receive the following errors: :/Users/jossr/AppData/Local/Temp/frescobaldi-ml8etqod/t

Re: Snippet doesn't work in unstable version

Am Mi., 20. Juli 2022 um 18:43 Uhr schrieb Martín Rincón Botero < martinrinconbot...@gmail.com>: > Hello, > > I grabbed this snippet a while ago from somewhere™ which puts a box > around music (an "improvisation box"). It works perfectly in Lilypond > 2.22.1, bu

Re: Snippet doesn't work in unstable version

Am Mi., 20. Juli 2022 um 18:43 Uhr schrieb Martín Rincón Botero < martinrinconbot...@gmail.com>: > Hello, > > I grabbed this snippet a while ago from somewhere™ which puts a box > around music (an "improvisation box"). It works perfectly in Lilypond > 2.22.1, bu

Snippet doesn't work in unstable version

Hello, I grabbed this snippet a while ago from somewhere™ which puts a box around music (an "improvisation box"). It works perfectly in Lilypond 2.22.1, but not in Lilypond 2.23.3+. Does somebody know how to make it work in more recent versions? This is the snippet: \version "2

Re: Problem with a snippet "shorthand for triplets [0.21429]"

Thank you who replied. Sometime "soon" I will update Lilypond but I will not reply further unless this fails...

Re: Problem with a snippet "shorthand for triplets [0.21429]"

Aaron Hill writes: > On 2022-06-27 6:18 am, Jean Abou Samra wrote: >> The LSR runs LilyPond 2.22 and you have 2.18. You need to upgrade >> LilyPond. Frescobaldi makes it easy to use several versions in >> parallel. > > As far as I can see, the LSR only notes the current version in > Contributing

Re: Problem with a snippet "shorthand for triplets [0.21429]"

On 2022-06-27 6:18 am, Jean Abou Samra wrote: The LSR runs LilyPond 2.22 and you have 2.18. You need to upgrade LilyPond. Frescobaldi makes it easy to use several versions in parallel. As far as I can see, the LSR only notes the current version in Contributing [1]. [1]: https://lsr.di.unimi.

Re: Problem with a snippet "shorthand for triplets [0.21429]"

Le 27/06/2022 à 13:26, mark damerell a écrit : It came from: %% http://lsr.di.unimi.it/LSR/Item?id=328 Here is part of it: % First version, with a single argument, i.e. the % syntax is \triplet{ c d e } triplet = #(define-music-function (music) (ly:music?)   #{ \tuplet 3/2 $music #}) \score

Problem with a snippet "shorthand for triplets [0.21429]"

It came from: %% http://lsr.di.unimi.it/LSR/Item?id=328 Here is part of it: % First version, with a single argument, i.e. the % syntax is \triplet{ c d e } triplet = #(define-music-function (music) (ly:music?) #{ \tuplet 3/2 $music #}) \score{ \relative c'{ c4 \triplet {c d e} } } Thi

Re: Snippet

gt; Would it be possible to update it to work on Lilypond 2.22.1? > > > The code contains spurious Unicode "zero-width space" characters, one among > the newlines between the end of append-merge and "mergeSkips =", and another > between the end of \mergeFullBarRes

Re: Snippet

g > the newlines between the end of append-merge and "mergeSkips =", and another > between the end of \mergeFullBarRests and \score. Try removing these. > Updated > snippet: > > \version "2.22.2" > #(define (append-merge x l r) > "Add x to the head

Re: Snippet

r between the end of \mergeFullBarRests and \score. Try removing these. Updated snippet: \version "2.22.2" #(define (append-merge x l r) "Add x to the head of list l, merging skips, and if r is true also merging full measure rests."   (if (and (pair? l)    (l

Snippet

Hello, I have this snippet that combines subsequent multimeasure rests into a multiplied one that Lilypond can compress, that I grabbed from somewhere a while ago. It used to work without errors, if I remember well, in Lilypond 2.20. In 2.22.1 it still "works" but throws an error for

Re: Snippet only as PDF

Hi Jean, That works fine for PDF and EPS output already, but not for SVG. So I added #(ly:set-option 'backend 'svg) afterwards and that made the Lilypond command line options for SVG output work. I guess that overrides the EPS-backend defined in “ lilypond-book-preamble.ly”. I will try to modif

Re: Snippet only as PDF

Le 27/02/2022 à 10:40, Bophead 2000 a écrit : What is the simplest way to get snippets cut down to only content as only one file – be it PDF, EPS or SVG? Add #(ly:set-option 'aux-files #f) Best, Jean

Re: Snippet only as PDF

t; > > What is the simplest way to get snippets cut down to only content as only > > > one file – be it PDF, EPS or SVG? > Back to pure Lilypond: > > Nonetheless I would still like to know if there is a way to render a > snippet cut to its pure musical content in

Re: Snippet only as PDF

Hi Bophead, Am 27.02.22 um 14:16 schrieb Bophead 2000: Hi Hraban, I have seen that page in ConTeXtgarden. But as far as I understood the “filter” module works only in ConTeXt MkIV and the workaround to use it in ConTeXt LMTX has a security flaw (cannot remember where I read the latter). That

Re: Re: Snippet only as PDF

readers if rendered with LMTX). And of course I am willing to improve the ConTeXt-LilyPond integration together. Back to pure Lilypond: Nonetheless I would still like to know if there is a way to render a snippet cut to its pure musical content in only one file format. Me and others might have a

Re: Snippet only as PDF

Hi Bophead, welcome, fellow ConTeXt user! Do you know https://wiki.contextgarden.net/LilyPond ? I’m using only parts of lilypond-book-preamble.ly Maybe we can improve the ConTeXt-LilyPond integration together. Hraban Am 27.02.22 um 10:40 schrieb Bophead 2000: Hello all, I want to produce lil

Snippet only as PDF

Hello all, I want to produce lilypond snippets to be used within a text – but only in one graphics file format (PDF, EPS or SVG). In the moment I am using a method I copied from the examples in the HTML-manuals putting the following in front of the music: \include "lilypond-book-preamb

Re: Improving this "Markup anywhere" snippet

Hi Colin, I wonder whether any of you Lilypond wizards could help me work out how to improve my Lilypond scores. Most of my embellishments come from reading/copying bits of code from this forum - but I admit I don't always fully understand why things work. However, I have this 'snip

Improving this "Markup anywhere" snippet

I wonder whether any of you Lilypond wizards could help me work out how to improve my Lilypond scores. Most of my embellishments come from reading/copying bits of code from this forum - but I admit I don't always fully understand why things work. However, I have this 'snippet' which

Re: [OT] Re: Snippet does not work properly ?

On Tue, Feb 9, 2021 at 5:04 PM David Wright wrote: > On Tue 09 Feb 2021 at 14:22:39 (-0500), Freeman Gilmore wrote: > > On Sun, Feb 7, 2021 at 6:18 PM Thomas Morley wrote: > > > Am So., 7. Feb. 2021 um 22:48 Uhr schrieb Freeman Gilmore: > > > > > >> I am trying to open this in Frescobaldi. > > >>

[OT] Re: Snippet does not work properly ?

On Tue 09 Feb 2021 at 14:22:39 (-0500), Freeman Gilmore wrote: > On Sun, Feb 7, 2021 at 6:18 PM Thomas Morley wrote: > > Am So., 7. Feb. 2021 um 22:48 Uhr schrieb Freeman Gilmore: > > > >> I am trying to open this in Frescobaldi. > >> > >> Custom tuning and MIDI rendering > >> > >> http://lsr.di.un

Re: Unapproved LSR-snippet "Generating scores within a function"

Am Do., 2. Juli 2020 um 12:16 Uhr schrieb Valentin Petzel : > > Hello, > > While I cannot help you with this, I noticed that this snippet must have been > done in an older version of lilypond, thus it uses older music function calls. > I’ve updated the snippet to 2.20, so now it

Re: Unapproved LSR-snippet "Generating scores within a function"

Hello, While I cannot help you with this, I noticed that this snippet must have been done in an older version of lilypond, thus it uses older music function calls. I’ve updated the snippet to 2.20, so now it compiles at least locally. Regards, Valentin%% LSR originally contributed by Gilles

Re: Snippet "Clef change and repeat barline"

Hi Harm, Le lun. 29 juin 2020 à 09:59, Thomas Morley a écrit : > Hi Pierre, > > I've now approved it as > lsr.di.unimi.it/LSR/Item?u=1&id=1116 > with some slight changes. > > I deleted another instance of \hideNotes and changed > \once\override Staff.Clef.space-alist = > #'((key-canc

Re: Snippet "Clef change and repeat barline"

u rather want to update a single entry of said space-alist. Thus >> \once\override Staff.TimeSignature.space-alist.first-note = #'(fixed-space . >> 0) >> is preferable. > > > Ok > >> (b) Is there any reason for >> \once\hideNotes >> ? >> Deleting it s

Re: Snippet "Clef change and repeat barline"

. 0) > is preferable. > Ok (b) Is there any reason for > \once\hideNotes > ? > Deleting it seems to make no difference > No clue...:( Probably a forgotten trial... > (c) I'd not use two different overrides in the snippet to adjust > spacing. Thus I&

Re: Snippet "Clef change and repeat barline"

Am Fr., 26. Juni 2020 um 12:06 Uhr schrieb Pierre Perol-Schneider : > > Hi Harm, > Thank you for your suggestion. Definitly better. > Ultimately, I've created a new snippet: > http://lsr.di.unimi.it/LSR/Item?u=1&id=1116 > If you're ok with it, I'll delete

Re: Snippet "Clef change and repeat barline"

Hi Harm, Thank you for your suggestion. Definitly better. Ultimately, I've created a new snippet: http://lsr.di.unimi.it/LSR/Item?u=1&id=1116 If you're ok with it, I'll delete snippet #1110 Cheers, Pierre Le jeu. 25 juin 2020 à 22:21, Thomas Morley a écrit : > Am Do., 25.

Re: Snippet "Clef change and repeat barline"

Am Do., 25. Juni 2020 um 10:55 Uhr schrieb Pierre Perol-Schneider : > > Hi Harm, > > Le mer. 24 juin 2020 à 23:26, Thomas Morley a > écrit : >> >> To the author of said snippet. >> lsr.di.unimi.it/LSR/Item?u=1&id=1110 >> >> I will not approve it

Re: Snippet "Clef change and repeat barline"

Le mer. 24 juin 2020 à 23:26, Thomas Morley a écrit : ... > Please check whether there's an issue about it already, if not report > it on the bug-list. > Done: http://lilypond.1069038.n5.nabble.com/Clef-change-and-repeat-sign-td234226.html Cheers, Pierre

Re: Snippet "Clef change and repeat barline"

Hi Harm, Le mer. 24 juin 2020 à 23:26, Thomas Morley a écrit : > To the author of said snippet. > lsr.di.unimi.it/LSR/Item?u=1&id=1110 > > I will not approve it in it's current state. > Ok. This sounds like default LilyPond being wrong in this regard. If so, &g

Snippet "Clef change and repeat barline"

To the author of said snippet. lsr.di.unimi.it/LSR/Item?u=1&id=1110 I will not approve it in it's current state. It shows how to change BreakAlignment.break-align-orders, ok, though this is covered in the docs already. It's description says "Here's a workaround to get a

Unapproved LSR-snippet "Generating scores within a function"

Hi, said snippet waits to be approved. Alas, I think it will never work in the jail the lsr is running in. Could someone with experience in running LilyPond in a jail could have a look at the code: https://lsr.di.unimi.it/form.php?type=snippet;id=;rld=m_snippet ? Thanks, Harm

Crash due to internal memory limits (?) in lilypond (was: Crash with bars-per-line-engraver as of LSR snippet id=838)

> I doubt it's caused by any custom-engraver. > At least on my machine this code: > > \paper { > systems-per-page = #5 > } > > music = \absolute { > \repeat unfold 2000 { > d'8 f' a' g' d' f' b' d' d'8 f' a' g' d' f' b' d' \break > } > } > > \new Staff { \music } > > already f

Re: Crash with bars-per-line-engraver as of LSR snippet id=838

Am Mi., 8. Apr. 2020 um 16:13 Uhr schrieb Michael Gerdau : > > Hi Kieren, > > >> I'm playing with the bars-per-line-engraver as of LSR > >> http://lsr.di.unimi.it/LSR/Item?id=838 > >> > >> When I increase the number of bars in my piece beyond a certain amount > >> (3500-4000 in my MWE) lilypond cra

Re: Crash with bars-per-line-engraver as of LSR snippet id=838

Hi Kieren, >> I'm playing with the bars-per-line-engraver as of LSR >> http://lsr.di.unimi.it/LSR/Item?id=838 >> >> When I increase the number of bars in my piece beyond a certain amount >> (3500-4000 in my MWE) lilypond crashes with an access violation under linux. > > Does that also happen with

Re: Crash with bars-per-line-engraver as of LSR snippet id=838

Hi Michael, > I'm playing with the bars-per-line-engraver as of LSR > http://lsr.di.unimi.it/LSR/Item?id=838 > > When I increase the number of bars in my piece beyond a certain amount > (3500-4000 in my MWE) lilypond crashes with an access violation under linux. Does that also happen with David

Re: Crash with bars-per-line-engraver as of LSR snippet id=838

I can confirm the segmentation fault in the "Drawing systems" phase, using 2.20.0 in Ubuntu.    /Mats On 2020-04-08 09:41, Michael Gerdau wrote: Hi list, I'm playing with the bars-per-line-engraver as of LSR http://lsr.di.unimi.it/LSR/Item?id=838 When I increase the number of bars in my piec

Crash with bars-per-line-engraver as of LSR snippet id=838

Hi list, I'm playing with the bars-per-line-engraver as of LSR http://lsr.di.unimi.it/LSR/Item?id=838 When I increase the number of bars in my piece beyond a certain amount (3500-4000 in my MWE) lilypond crashes with an access violation under linux. I have this problem with both 2.19.83 and 2.20

Lyric Syllable Magnetic Snap snippet

Hello all, I came upon the Lyric Syllable Magnetic Snap snippet: https://lists.gnu.org/archive/html/lilypond-user/2019-05/msg00389.html And I noticed that a small space gets inserted after a multisyllabic word. Consider this example, including the .ily file from above link: \version "2

Re: key change at end of snippet

From: David Kastrup Subject: Re: key change at end of snippet Date: Sat, 25 Jan 2020 09:41:45 +0100 > \relative c' { > \key d \major > d1 > \key c \major > \grace s256 > } Thanks for the suggestion! I'm now trying Thomas's route. Werner

Re: key change at end of snippet

>> I have to typeset a snippet that is an excerpt of a longer piece, >> and this snippet ends with a key change: >> >> \relative c' { >> \key d \major >> d1 >> \key c \major >> } >> >> However, the staff stops righ

Re: key change at end of snippet

Werner LEMBERG writes: > I have to typeset a snippet that is an excerpt of a longer piece, and > this snippet ends with a key change: > > \relative c' { > \key d \major > d1 > \key c \major > } > > However, the staff stops right before the key

Re: key change at end of snippet

Am Sa., 25. Jan. 2020 um 06:31 Uhr schrieb Werner LEMBERG : > > > I have to typeset a snippet that is an excerpt of a longer piece, and > this snippet ends with a key change: > > \relative c' { > \key d \major > d1 > \key c \major > } > >

Re: key change at end of snippet

Am 25. Januar 2020 08:17:05 MEZ schrieb Werner LEMBERG : > >>> I think it is necessary to somehow keep the staff line alive – I >>> guess I can probably fake a solution by adding another bar with a >>> suppressed bar line that contains some invisible music. Not sure >>> yet whether this is sens

Re: key change at end of snippet

>> I think it is necessary to somehow keep the staff line alive – I >> guess I can probably fake a solution by adding another bar with a >> suppressed bar line that contains some invisible music. Not sure >> yet whether this is sensible, and if yes, how to make the width of >> this extra bar (alm

Re: key change at end of snippet

Am 25. Januar 2020 07:30:01 MEZ schrieb Werner LEMBERG : > >> \once \override Score.BreakAlignment #'break-align-orders = >> #(make-vector 3 '( staff-bar >> clef >> span-bar >> breathing-sign >> ... >>

Re: key change at end of snippet

> \once \override Score.BreakAlignment #'break-align-orders = > #(make-vector 3 '( staff-bar > clef > span-bar > breathing-sign > ... > key > time-signature)), > > To in

RE: key change at end of snippet

ypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Werner LEMBERG Sent: Friday, January 24, 2020 9:30 PM To: lilypond-user@gnu.org Subject: key change at end of snippet I have to typeset a snippet that is an excerpt of a longer piece, and this snippet ends with a key change: \relative c&#

key change at end of snippet

I have to typeset a snippet that is an excerpt of a longer piece, and this snippet ends with a key change: \relative c' { \key d \major d1 \key c \major } However, the staff stops right before the key change, see attached image. What can I do to avoid that? Werner

Re: A snippet for editing Beams using the mouse

On Tue, 17 Dec 2019, Paolo Prete wrote: Here's the fixed version: waiting for feedbacks! (Again and again: I write these snippets really in a hurry, in these days. A more "structured" collaboration is getting necessary for me, at this point) Put it in a little Github project? -- MT

Re: Indentation, was Re: A snippet for editing Beams using the mouse

Dec 17, 2019 at 2:17 AM David Wright wrote: > On Mon 16 Dec 2019 at 23:55:52 (+0100), Paolo Prete wrote: > > P.S) I don't know why the browser's viewer messes up the indentation of > > these attachments. > > If so, I ask if are there volunteers to fix that and re-pos

Re: A snippet for editing Beams using the mouse

te: > I'm just noting that there's a bug with more than one Beam. I'm fixing it. > Have a bit of patience please ;-) > > On Mon, Dec 16, 2019 at 11:55 PM Paolo Prete wrote: > >> Hello everybody, >> >> here is another snippet that uses the system th

Indentation, was Re: A snippet for editing Beams using the mouse

On Mon 16 Dec 2019 at 23:55:52 (+0100), Paolo Prete wrote: > P.S) I don't know why the browser's viewer messes up the indentation of > these attachments. > If so, I ask if are there volunteers to fix that and re-post the snippet (I > see correct indentation if I paste the

Re: A snippet for editing Beams using the mouse

I'm just noting that there's a bug with more than one Beam. I'm fixing it. Have a bit of patience please ;-) On Mon, Dec 16, 2019 at 11:55 PM Paolo Prete wrote: > Hello everybody, > > here is another snippet that uses the system that I previously > implemented. This

Re: A snippet for editing Beams using the mouse

On 12/16, Paolo Prete wrote: > Hello everybody, > > here is another snippet that uses the system that I previously > implemented. This time for the tuning of the beams. This is too a > very tedious operation to do with just the code and for this I believe > that this tool i

A snippet for editing Beams using the mouse

Hello everybody, here is another snippet that uses the system that I previously implemented. This time for the tuning of the beams. This is too a very tedious operation to do with just the code and for this I believe that this tool is also useful. As you can see, the code is not only shorter than

Re: how to implement the snippet in the attachment

On 31.10.19 15:32, DJF wrote: \relative c'' { \key f \major <<{bes2 ~ 8 4} \\ {r4 ~ \hideNotes 8 \unHideNotes s8 s4 } >> } Code formatting matters. The above may be legible to LilyPond, and maybe you’re used to that style, but if you’re sharing code, please stick to the standards evident f

Re: how to implement the snippet in the attachment

Hi Jinsong, > Thank you very much for the help. It works well. I’m glad! > I don't understand the \new Voice If you do a web search for \new Voice lilypond the first hit is: . > and \voiceTwo A web search for \vo

Re: how to implement the snippet in the attachment

On 2019/10/31 22:22, Kieren MacMillan wrote: Hi, I don't figure out a way to implement it. Something like this, maybe? \version "2.19.83" { \key f \major << { bes'2 ~ 8[ ] } \\ \new Voice { \voiceTwo r4 ~ \once \hideNotes q8 } >> 4 } Hope that helps! Kieren. Thank

Re: how to implement the snippet in the attachment

On Oct 31, 2019, at 10:02 AM, Jinsong Zhao wrote: > > hi there, > I am trying to transcribe a music sheet. I have encountered the snippet in > the attachment. I don't figure out a way to implement it. I am now using an > alternative way like: Use hidden notes in

Re: how to implement the snippet in the attachment

Hi, > I don't figure out a way to implement it. Something like this, maybe? \version "2.19.83" { \key f \major << { bes'2 ~ 8[ ] } \\ \new Voice { \voiceTwo r4 ~ \once \hideNotes q8 } >> 4 } Hope that helps! Kieren.

how to implement the snippet in the attachment

hi there, I am trying to transcribe a music sheet.  I have encountered the snippet in the attachment.  I don't figure out a way to implement it.  I am now using an alternative way like: \version "2.19.83" \relative c'' { \key f \major <<{bes2 ~ bes8 g a4} \\ {r4 <>

Re: Snippet for aligning markup inside another markup

Oops, here the missing snippet image... Am 01.10.2019 um 01:45 schrieb Kieren MacMillan: Hi Aaron, Here's my take: Nice work! This should be part of the base distro, IMO. Thanks, Kieren. Kieren MacMillan, composer (he/him/his) ‣ we

Re: Snippet for aligning markup inside another markup

Hi Aaron and Kieren, very nice! (I really should have read how the markup commands make use of ly:stencil-aligned-to...) Here my variant of the code with tweakable alignment. Personally I prefer the "scheme only-style" but I agree that the mixed style Aaron used would be shorter. \version

Re: LSR-snippet 1071 "Percussion example" incomplete

Am Do., 3. Okt. 2019 um 11:43 Uhr schrieb Thomas Morley : > > To the author of LSR-snippet 1071 "Percussion example", > > this snippet > lsr.di.unimi.it/LSR/Item?u=1&id=1071 > is obviously not complete (probably a copy/paste-error), please add > the missing parts

LSR-snippet 1071 "Percussion example" incomplete

To the author of LSR-snippet 1071 "Percussion example", this snippet lsr.di.unimi.it/LSR/Item?u=1&id=1071 is obviously not complete (probably a copy/paste-error), please add the missing parts. Otherwise I'll delete it so

  1   2   3   4   5   6   >