Harp_pedal_engraver: an overengineered solution to a niche problem

Hello friends, I’ve found that one of the more cumbersome tasks in Lilypond is engraving chromatic music for concert harp. When entering markups manually for each pedal change, it’s difficult to achieve clean and consistent formatting, and very easy to make errors. I’d like to share my solution

Re: Staff switch over page break spoils vertical spacing

Jean, please don't apologize for the constraints on your time. You contribute so much to the project and the community. Your efforts are appreciated. On Sat, Jul 8, 2023 at 8:11 PM Jean Abou Samra wrote: > Le samedi 08 juillet 2023 à 17:44 +1000, Vaughan McAlley a écrit : > > When a

Re: LilyPond 2.25.6

Hooray! I can finally compile my whole symphony draft on Windows! Thanks devs for all the work that went into this. On Sat, Jun 24, 2023 at 6:42 AM Jonas Hahnfeld via LilyPond user discussion wrote: > We are happy to announce the release of LilyPond 2.25.6. This is termed > a development

Re: Anybody else playing with GPT4 and Lilypond?

A practical follow up question: what is currently the largest repertoire of publicly available Lilypond scores? Ideally, something like the complete Bach chorales or Mozart piano sonatas. On Wed, Mar 29, 2023 at 3:43 PM Saul Tobin wrote: > I've seen some examples of other people succeed

Re: Anybody else playing with GPT4 and Lilypond?

On the upper left corner. when i asked for clarification >> instead of admitting it was mistaken it said it was white and next to >> another button. Twice it doubled down before admitting it was wrong. >> >> On Wed, Mar 29, 2023, 6:44 PM Saul Tobin >> wrote: >> >>

Anybody else playing with GPT4 and Lilypond?

I've seen some examples of other people succeeding in getting ChatGPT with GPT4 to compose simple music in other text based music formats. I've had limited success getting it to output Lilypond code. It is able to correctly structure the code with a score block, nested contexts, and appropriately

Re: Change event properties before sending to engraver

Is your idea to have a second engraver at the Voice level to prepare the events? You should be able to have an engraver listen to the event and modify it before it's listened by the Staff level engraver, as long as they are \consist'ed in the right order. On Mon, Mar 20, 2023, 1:40 PM Valentin

Re: Variables and Bookpart

That really only addresses the full score, not the parts, since in the parts multiple movements share the same bookpart. On Sun, Mar 12, 2023 at 5:19 PM Jean Abou Samra wrote: > Le dimanche 12 mars 2023 à 17:06 -0700, Saul Tobin a écrit : > > For what it's worth my use case was t

Re: Variables and Bookpart

fine for me. On Sun, Mar 12, 2023 at 4:45 PM Jean Abou Samra wrote: > Le dimanche 12 mars 2023 à 16:34 -0700, Saul Tobin a écrit : > > A slightly nicer syntax to workaround this limitation is to use the > function: > parserDefine = > #(define-void-function (name v

Re: Variables and Bookpart

A slightly nicer syntax to workaround this limitation is to use the function: parserDefine = #(define-void-function (name val)(symbol? scheme?) (ly:parser-define! name val)) Then instead of var = { ... } you can write \parserDefine var { ... }. I believe this was posted on the list a few

Re: Message size limit

Hard disagree on plain text emails. I didn't really have a strong opinion re the whole discussion about message boards vs. email, but IMO the world has moved on to rich text email with embedded media. I think the reliance on plain text email as the standard for this mailing list detracts

Re: Tips for code reusability

I concur on entering all music in concert pitch. You may find the auto-transpose snippet from OpenLilyLib helpful ( https://github.com/openlilylib/oll-misc/tree/master/pitch), as you can simply write "\transposition bf" instead of wrapping all transposed blocks in "\transpose x y { }". This is

Re: Tips for code reusability

https://lilypond.org/doc/v2.24/Documentation/notation/writing-parts#quoting-other-voices may help with the second question. On Tue, Feb 28, 2023 at 5:08 PM TJ Kolev wrote: > Greetings, > > I've decided to notate a brass band piece from a paper copy into some > digital format that would be

Re: LilyPond 2.25.2

Surprised to see that the http versions of those pages are accessible. Shouldn't they redirect to https? On Sat, Feb 18, 2023 at 12:13 PM Jonas Hahnfeld via LilyPond user discussion wrote: > On Sat, 2023-02-18 at 14:43 -0500, Shane Brandes wrote: > > That is great, but where can one find a list

Re: Landscape output displays sideways

Channel wrap around can also occur if you assign midi channels per Voice and instantiate more than 16 Voice contexts, for example if you have used \new Voice at the beginning of each polyphonic passage. On Sat, Feb 18, 2023, 7:04 AM wrote: > On 17 Feb 2023 at 19:11, Jean Abou Samra wrote: > > >

Re: Documentation: Should we possibly have aliases for current stable and current devel?

Many users have old projects on very old versions of Lilypond, and sometimes you just want to make a small edit, not update your whole project to use the new version. It's important for documentation to be available. On Mon, Feb 13, 2023, 8:41 AM Kevin Cole wrote: > On Mon, Feb 13, 2023 at

Re: nested \relative ?

This seems more or less equivalent to religiously putting \resetRelativeOctave at the beginning of every phrase IMO. On Sat, Feb 11, 2023 at 2:15 PM Simon Albrecht wrote: > On 10/02/2023 19:22, Saul Tobin wrote: > > What is the reasoning behind having smaller relative blocks? &g

Re: nested \relative ?

The downsides seem to me like they would be very specific to a given user's workflow. On Sat, Feb 11, 2023 at 6:53 AM Kieren MacMillan < kie...@kierenmacmillan.info> wrote: > Hi Saul, > > > What is the reasoning behind having smaller relative blocks? Generally I > structure my variables as a

Re: nested \relative ?

What is the reasoning behind having smaller relative blocks? Generally I structure my variables as a single \relative block per variable and just use \resetRelativeOctave at the beginning of every passage. On Fri, Feb 10, 2023 at 3:09 AM Simon Albrecht wrote: > Hi Darren, > On 10/02/2023 11:46,

Re: Duplicate marks with removed Staves (frenched)

oirStaff << \new Staff << \marks \A >> >> \new ChoirStaff << \new Staff << \marks \B >> >> >> Maybe I'm missing a way to do this while keeping the mark engravers in the ChoirStaff context. Saul On Thu, Feb 9, 2023 at 1:29 AM Simon A

Re: Duplicate marks with removed Staves (frenched)

Hi Simon, Is there a reason to have the marks in a child context rather than just a simultaneous music variable? Saul On Wed, Feb 8, 2023 at 10:24 AM Simon Albrecht wrote: > Hello everyone, > > I am working on a large score with several ChoirStaves and want to have > BarNumbers and Marks in

OLL autotranspose feature release

Hi all, Just want to let everyone know, auto-transpose in OpenLilyLib now has automatically inserted key signatures. https://github.com/openlilylib/oll-misc/tree/master/pitch/auto-transpose Please let me know if you run into any bugs using it. Saul

Re: Error in Extending Lilypond example

results for Lilypond questions, at least for me. On Wed, Feb 1, 2023 at 2:12 AM Jean Abou Samra wrote: > Saul, > > > Le 1 févr. 2023 à 04:16, Saul Tobin a écrit : > > The fourth example engraver here: > > https://extending-lilypond.readthedocs.io/en/latest/extending

Error in Extending Lilypond example

The fourth example engraver here: https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example Running this code in 2.24 crashes on initializing the engraver with In procedure ly:spanner-set-bound!: Wrong type argument in position 3 (expecting Item): ().

Re: \stopStaff \startStaff spacing & line continuity

I believe this may be a case where you need to use \applyOutput, as documented here: https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#tweaking-grobs-during-translation . On Tue, Jan 31, 2023 at 5:57 PM Ahanu Banerjee wrote: > I am trying to modify the color of the

Re: Understanding marks in 2.24

On Tue, Jan 31, 2023 at 1:32 PM Jean Abou Samra wrote: > On 31/01/2023 22:07, Saul Tobin wrote: > > I have a few questions: > > 1. How to achieve horizontal alignment and avoid vertical overlap of > RehearsalMarks and MetronomeMarks at the beginning of a system, or when >

Re: Understanding marks in 2.24

s1 \textMark "foo" s1 } music = \relative c'' { bf4 a c b bf4 a c b bf''4 a,, c b bf4 a c b } \score { << \new MarkLine \global \new StaffGroup << \new Staff << \global \music >> \new Staff << \global \music >>

Re: Understanding marks in 2.24

IMO deduplication wouldn't really be semantically contradictory, because the goal of allowing multiple simultaneous marks is to allow for multiple *different* marks at the same moment. And you could always have a context property to switch deduplication on/off. The scheme evaluation challenges

Understanding marks in 2.24

Hi all, I'm in the process of updating my scores from 2.18 to 2.24 (yes I skipped a bunch of versions), and I'm trying to understand the intended use of the new types of marks. Take the following small example: \version "2.24.0" \language "english" markGroup = \with { \consists Mark_engraver

Re: Snippet: automatic reminder text for mutes/techniques

case. On Thu, Jan 26, 2023 at 6:10 PM Andrew Bernard wrote: > 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 remin

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: Auto-transpose engraver progress

require the ability to "listen ahead" or "listen behind" to all the events happening at the same moment. Is that even possible? On Thu, Jan 19, 2023 at 5:48 PM Saul Tobin wrote: > Hi all, > > I managed to add functionality to the auto-transpose engraver snippet fro

Auto-transpose engraver progress

Hi all, I managed to add functionality to the auto-transpose engraver snippet from OLL so that it prints key signatures at transposition changes. It also doesn't do so if the transposition change is only octave transposition. The one thing I'd like to fix is the behavior when an actual key

Re: irrational meters

Doesn't "Night Fantasies" by Elliott Carter use an extremely obscure structural polyrhythm? Not an actual irrational meter but similar idea. On Tue, Jan 17, 2023 at 4:47 PM H. S. Teoh via LilyPond user discussion < lilypond-user@gnu.org> wrote: > On Tue, Jan 17, 2023 at 07:08:41PM -0500, David

Re: Help understanding event listeners

thought but I'm just as confused. On Tue, Jan 17, 2023 at 1:15 PM Jean Abou Samra wrote: > Le 17/01/2023 à 10:10, Saul Tobin a écrit : > > What I can't figure out is why when my autoKeysigEngraver broadcasts a > > KeyChangeEvent, it gets picked up by t

Help understanding event listeners

I've been tinkering with the auto-transpose engraver from OLL, trying to automatically print key signatures if the transposition has been changed. In the original code it looks like the plan was to have the engraver broadcast a KeyChangeEvent, but when I tried that it ended up in an infinite loop

Re: Unicode accidentals vs. Markup accidentals

Lilypond ships with a text font as well as a music font. I agree that I suspect that currently Lilypond's text font does not actually define these Unicode music characters, so it falls back on the OS to find them. Why not just add copies of Emmentaler glyphs to the Lilypond text fonts for

Re: Unicode accidentals vs. Markup accidentals

ece of text came up in the future. You could > definitely make the text using lilypond accidentals look right by > changing the font size of either the text or the accidental, it's just a > matter of the size and alignment. > > -William > > On 1/15/23 01:05, Saul Tobin wrot

Unicode accidentals vs. Markup accidentals

Surprisingly, typing the Unicode characters for accidental symbols does not produce the same font output as using the markup commands: << \new Staff { c'1^"B♭" c'1^"C♯" c'1^"D♮" } \new Staff { c'1^\markup { B \flat } c'1^\markup { C \sharp } c'1^\markup { D \natural

Re: Removing staves when using remove-layer

} \removeWithTag #'combined \I \new Staff = "2" \with { instrumentName = "2" shortInstrumentName = "2" \override VerticalAxisGroup.remove-empty = ##t \override VerticalAxisGroup.remove-first = ##t \override VerticalAxisGroup.remove-layer

Removing staves when using remove-layer

Hi all, When condensing staves using remove-layer as described here https://lilypond.org/doc/v2.24/Documentation/notation/modifying-single-staves#hiding-staves, what is the best way to temporarily hide the combined staff as well as the individual staves? E.g. for a particularly crowded system

Re: ANN: Spontini-Editor 1.0 released

, >> so you can have a few definitions that can simply be removed for 2.18. >> >> But is there any reason for using such an old Lilypond version? >> >> Cheers, >> Valentin >> >> 19.10.2021 01:39:59 Saul Tobin : >> >> > Any possibility of using this with a Lilypond 2.18 project? >> > >> >>

Re: ANN: Spontini-Editor 1.0 released

Any possibility of using this with a Lilypond 2.18 project? On Sun, Oct 17, 2021 at 6:21 PM Jon Arnold wrote: > Looks promising. The ability to edit slurs with a mouse is huge. > > On Sun, Oct 17, 2021 at 2:07 PM Paolo Prete wrote: > >> Hello all, >> >> I just drafted a new release (1.0) of

How to use shapeII in 2.18 on Windows 10?

s/Saul Tobin/.lily;') \include "oll-core/internal/os-path.ily" C:/Users/Saul Tobin/.lily/openlilylib/oll-core/package.ily:57:2 <1>: error: GUILE signaled an error for the expression beginning here # (if (not (defined? 'openlilylib-root)) A quick search showed me a previous

Re: Running LilyPond on Amazon Linux 2

I'm curious to know about your use case/workflow for running Lilypond in AWS Lambda. Seems interesting. Saul On Tue, Jan 14, 2020, 6:34 AM Peter Anglea wrote: > I think I got it fixed… recording this here for anyone else who stumbles > upon the same issue as I did. > > I downloaded an RPM

Lilypond/Frescobaldi on Catalina using Docker

Hi all, I've come to the conclusion that the best workaround for the lack of 64-bit builds on Mac and Windows is to run Lilypond in a Docker container. Based on the number of Lilypond images on Docker Hub, it would seem I'm fairly late to this party, though if it's been discussed on the user

2.18 for Catalina?

Hi all and happy holidays What is currently the easiest way to get a working install of Lilypond 2.18 on Catalina? I have old projects that require 2.18 and will not work on 2.19. Ideally, I'd like to have control over the install directory, since I typically have multiple Lilypond versions

Re: LSR management

Could LSR be functionally mirrored as a GitHub repo? On Sat, Nov 16, 2019, 5:17 PM Andrew Bernard wrote: > It may not be a good thing that nobody seems to know who runs and > manages LSR. Should we devote any time to making this a more robust > situation. given how much people refer to it, and

Re: flats and sharps as symbols in a lyric text

insert a unicode > character (for example U+266D) in a lyric text, if I do not have a > corresponding > font etc? Do you have eny example? > > many thanks, again > Karsten > > On Tue, 2019-11-05 at 15:53 -0800, Saul Tobin wrote: > > I usually just type the accidental

Re: flats and sharps as symbols in a lyric text

On Tue, Nov 5, 2019, 5:08 PM Andrew Bernard wrote: > HI Saul, > > What is correct? I believe this is a highly subjective matter. > > Andrew > Sure, agreed. But the default should at least be reasonable without tweaking, right? > > > On Wed, 6 Nov 2019 at

Re: flats and sharps as symbols in a lyric text

The breaking-ness seems like an obstacle. On Tue, Nov 5, 2019, 5:05 PM Kieren MacMillan wrote: > Hi Saul, > > > It bugs me a bit that macros are needed to tweak the spacing of > accidental symbols in markup. Shouldn't the default markup commands for > accidental symbols have correct size and

Re: flats and sharps as symbols in a lyric text

It bugs me a bit that macros are needed to tweak the spacing of accidental symbols in markup. Shouldn't the default markup commands for accidental symbols have correct size and spacing? On Tue, Nov 5, 2019 at 4:02 PM Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Saul (et al.), >

Re: flats and sharps as symbols in a lyric text

I usually just type the accidental signs as Unicode characters. I find the sizing and alignment works better than with the Lilypond markup commands. On Tue, Nov 5, 2019, 3:32 PM Karsten Reincke wrote: > Dear friends; > > does anyone know how I could insert a (double) flat or a (double) sharp in

Re: Frescobaldi, improve support for audio export

Would the bundled VLC be redundant to an existing system install of VLC? Would it be usable instead of a system install? Would the bundled VLC get updates? I normally have VLC installed anyway, but I'd rather not have to keep a separate copy on disk just for Frescobaldi. On Sun, Oct 20, 2019,

Re: Frescobaldi, improve support for audio export

On Thu, Oct 17, 2019 at 3:20 PM Urs Liska wrote: > 17. Oktober 2019 22:19, "Saul Tobin" schrieb: > > > The biggest killer-feature for me would be the ability to playback > multiple midi files > > simultaneously in sync (to work around the 16 track limitatio

Re: Frescobaldi, improve support for audio export

The biggest killer-feature for me would be the ability to playback multiple midi files simultaneously in sync (to work around the 16 track limitation). Audio format-wise, I think mp3 is fine. I doubt anyone particularly cares about lossless quality for their general midi soundfont playback. On

Re: \transposedQuoteDuring

I usually use \ottava and \omit the OttavaBracket. On Wed, May 1, 2019, 6:54 AM Pierre-Luc Gauthier wrote: > Hi there, > > Is there a way to transpose a quotation, say, an octave higher ? > > m.e.g.: > > \version "2.19.83" > > quoted = {c'4 d' e' f' g'} > \addQuote "quoted" \quoted > > quoting

Re: Automatic beaming with rest

I agree with this, but I can imagine the following distinct engraving styles: 1. Beam over rests only when the beam both begins and ends with a note. 2. Also beam over initial rests. 3. Also beam over final rests. Further, I can imagine wanting e.g. c16[ r c r], rather than c16[ r c] r, but in

Re: Guile for building lilypond on Ubuntu18.10

> > On Sat, 23 Mar 2019 at 12:36, Saul Tobin > wrote: > >> I followed the process described above to compile Guile 1.8 and Lilypond >> on Windows Subsystem for Linux. I found that it only worked when installing >> guile to /usr, not /usr/local. >> >> _

Re: Guile for building lilypond on Ubuntu18.10

I followed the process described above to compile Guile 1.8 and Lilypond on Windows Subsystem for Linux. I found that it only worked when installing guile to /usr, not /usr/local. Saul On Fri, Mar 22, 2019, 6:24 PM David Wright wrote: > On Sat 23 Mar 2019 at 11:12:29 (+1100), Andrew Bernard

Re: Markup wrap at the end of the line

I agree that when a long markup stretches the measure at the end of a line, it suggests that there may be better ways of laying out the line breaks. Perhaps there should be a penalty for stretched measures due to markup in Lilypond's line breaking algorithm? Saul On Sat, Mar 16, 2019, 6:34 PM

Possible bug: MMRs and keepAliveInterfaces

If any of the interfaces for MultiMeasureRests (e.g. rest-interface, spanner-interface, multi-measure-rest-interface) are included in keepAliveInterfaces (useful if you want to condense some systems in a score, but not others), then when an MMR occurs on either side of a system break it can cause

lilypond.org error 500

Currently getting Internal Server Error 500 on Lilypond.org. Also looks like the site is only on http, no https. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Reducing top margin for a single page in a score

The size reduction for a single system strategy is simple to do within a single Lilypond score using \magnifyStaff and maybe a couple additional overrides. On Mon, Feb 4, 2019, 8:04 AM David Wright On Mon 04 Feb 2019 at 16:40:57 (+1100), Andrew Bernard wrote: > > I am doing a long string

Order of process-music between Contexts

Hi all, I'm trying to figure out the workings of engravers and contexts. Can anyone point me to the relevant code, or better yet explain the order in which the process-music step happens between engravers in child vs. parent contexts? Is this set in stone, or can it be modified? Like, suppose I

Re: Dynamic next to espressivo

Below is the snippet I use for dynamics with expressive text. I believe I've posted it to the mailing list before, a few years ago maybe. \version "2.18.2" dynText = #(define-event-function (parser location dyn expr) (markup? markup?) (let* ( (mark #{ \markup {

Re: Organization of the piese part by part, not staff by staff

Fundamentally, the data model of Lilypond is horizontal, even when you delve into the guts of how the program works (iterators, streams, engravers). My advice is to embrace that and adapt your workflow and thinking to take advantage of Lilypond's strengths, rather than fighting against it. In my

Re: Attempt at divisi automating engraver

Still working on this... The new version attached sets make-dead-when so that staves with fewer parts have priority over those that they can be merged into. (Disregard what I wrote previously about remove-layers — I got a bit confused.) The engraver now does mainly what it is supposed to, namely

Re: Attempt at divisi automating engraver

#t c'8 8 8 8 8 8 8 8 \set Staff.combineWithNext = ##f c'8 8 8 8 8 8 8 8 8 } \new Staff = "4" \with { sharingParts = #'(4) shortInstrumentName = "4" keepAliveInterfaces = #'() } \repeat unfold 8 { c'8 8 8 8 8 8 8 8 } >> On Sat, Dec 29, 2018

Attempt at divisi automating engraver

Hi all, Attached is my latest attempt to make progress toward an automatic mechanism for n-parts that may share a staff or not. The idea is that if the context property combineNext = ##t, then that part can share a staff with the next part down. The engraver is supposed to set

Re: Possible bug with tempo mark spacing

ves. Staves shouldn't be affecting spacing on systems where they are dead. On Fri, Dec 28, 2018 at 6:47 AM Malte Meyn wrote: > > > Am 28.12.18 um 04:54 schrieb Saul Tobin: > > > > When using a context like MarkLine for tempo marks, if the staff > > immediately below the M

Possible bug with tempo mark spacing

Happy holidays all, Below is a demonstration of an odd behavior I noticed. When using a context like MarkLine for tempo marks, if the staff immediately below the MarkLine is hidden but contains rhythmic activity, and if BOTH Y-offset and extra-spacing-width are overridden for MetronomeMark, the

Re: Tuplets in Metric Modulations

Notice that in my example I included spacer rests in the tuplet. This allow room for the bracket. On Fri, Dec 21, 2018 at 2:47 PM Ld2020 wrote: > Thank you - this is extremely helpful. > > One issue I am still trying to solve: how to get tuplet brackets to > appear as part of the metronome

Re: Tuplets in Metric Modulations

I've attached the snippet I use for metric modulation markings. Hopefully others find it useful. To use it you would write something like: \metricMark { \tuplet 3/2 { r8*2 c8 } } { c16 r16*3 } "Più tranquillo" #108 FYI – there are some issues with spacing if the marking is at a line break. On

Re: Fatal error compiling large project (Win10/2.19.82)

I'd be happy to help test as well. On Wed, Dec 19, 2018, 9:32 AM Michael Gerdau > > Indeed, it's not a real problem to compose a special command line for > WSL Windows - if we know exactly how it should look like. > > Testing would be a little bit awkward, though > > I‘d be happy to test it. > >

Re: Fatal error compiling large project (Win10/2.19.82)

Thanks so much for the confirmation. A couple questions: 1) Is there a technical obstacle or other reason preventing a Windows 64-bit build? 2) Is it possible to run Lilypond under WSL from Frescobaldi? On Tue, Dec 18, 2018 at 8:36 PM Aaron Hill wrote: > On 2018-12-18 7:24 pm, Saul Tobin wr

Re: Fatal error compiling large project (Win10/2.19.82)

at 4:14 PM Saul Tobin wrote: > Hi Ben, > > I did see that thread, but I don't think it can be directly related to my > issue, since in my case there is no single line of my code that is > triggering the compile error. Each score compiles correctly on its own and > in co

Re: Fatal error compiling large project (Win10/2.19.82)

it fails. I am also not using strftime anywhere. Saul On Sun, Dec 16, 2018 at 2:38 PM Ben wrote: > On 12/16/2018 5:32 PM, Saul Tobin wrote: > > Hi all, > > I'm getting a fatal error when I compile all of the movements of a large > project on 2.19.82 on Windows 10. I can com

Fatal error compiling large project (Win10/2.19.82)

Hi all, I'm getting a fatal error when I compile all of the movements of a large project on 2.19.82 on Windows 10. I can compile the movements individually and in smaller combinations with no problems. There is no Lilypond error in the debug output, just "FATAL: memory error in realloc." I had

Re: Should the LilyPond website mention financial support for contributors?

I support all of these suggestions. My own two cents: I would like to contribute monthly, but I'd personally prefer to contribute to the project as a whole or the core developers as a group, if possible. It seems like it could be helpful to set project-level finances up in the long run anyway,

Issue with make-dead-when (divisi, hara_kiri)

Hi all, Not sure if this should be on the User mailing list or one of the others. The attached code replicates a strange behavior I have encountered several different times, where seemingly random and irrelevant musical details cause staves to incorrectly disappear when using the divisi snippet

Lilypond website down?

Looks like Lilypond.org has been down since yesterday. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: New snippet: remove staff if another is alive (for wind divisi)

Super glad to see this conversation happening! David I'm so glad you've been working on the backend for divisi. Divisi staves have long been my biggest headache. Thomas, thanks for writing the improved version. I haven't had a chance to look at the code deeply yet — I will play around with it

Re: New snippet: remove staff if another is alive (for wind divisi)

other staves are alive on each system. On Fri, Aug 3, 2018 at 2:23 PM Ben wrote: > On 8/3/2018 5:14 PM, Saul Tobin wrote: > > Hi all, > > I just put together a snippet to make managing shared wind staves more > automatic, particularly with triple winds that may be com

New snippet: remove staff if another is alive (for wind divisi)

Hi all, I just put together a snippet to make managing shared wind staves more automatic, particularly with triple winds that may be combined in different ways. \version "2.19.82" #(define remove-if-sibling (lambda (offsets) (lambda (grob) (let* ( ;; The parent of

Re: \unset with modified default properties

Sure, define-music-function works fine. That part I just copied from the earlier snippet. That's a side issue, though. On Mon, Jul 2, 2018 at 2:36 PM David Kastrup wrote: > Saul Tobin writes: > > > Indeed, or StaffGroup level if I'm following correctly. > > And there is a St

Re: \unset with modified default properties

hat I'm trying to do with \unset? Thanks! Saul On Mon, Jul 2, 2018 at 12:24 AM David Kastrup wrote: > Saul Tobin writes: > > > Interesting. So if the default property is set at the Staff level, for > > instance, then changed and \unset at the Voice level, it goes back

Re: Toc with counter

.schneider.pa...@gmail.com> wrote: > Thank you Saul. > I understood that fill-with-pattern initiated the problem but could not > see why. So thank you for your detailed explanation. > Now, if someone has a workaround... > > Cheers, > Pierre > > 2018-07-02 21:12

Re: Toc with counter

If I understand correctly, counter gets incremented whenever interpret-markup is called on a markup containing the counter. If you look in define-markup-commands.scm, \fill-line calls interpret-markup only once, but \fill-with-pattern calls interpret-markup twice, first to find out the width of

Re: \unset with modified default properties

. On Sun, Jul 1, 2018 at 1:00 AM David Kastrup wrote: > Saul Tobin writes: > > > In both 2.18 and 2.19, \unset appears to set a context property to the > > built-in default, rather than the default set in the \with {} block: > > > > music = \relative c' { > >

Re: \unset with modified default properties

Unfortunately, for my use case, \once\set and \once\unset aren't enough. On Sat, Jun 30, 2018 at 8:31 PM Aaron Hill wrote: > On 2018-06-30 17:50, Saul Tobin wrote: > > In both 2.18 and 2.19, \unset appears to set a context property to the > > built-in default, rather than

\unset with modified default properties

In both 2.18 and 2.19, \unset appears to set a context property to the built-in default, rather than the default set in the \with {} block: music = \relative c' { \tuplet 3/2 { c8 c c d d d e e e f f f | } \set Staff.tupletSpannerDuration = #(ly:make-moment 1/2) \tuplet 3/2 { c8 c

Re: Combining full bar rests with omitted grobs in between

I wrote a function that does something similar to what you need. There may be newer or better ways to do it, but it's what I use. Saul On Fri, May 18, 2018 at 1:12 AM, Davide Liessi wrote: > Dear all, > is there a way to combine the two full bar rests in one

convert-ly path for Frescobaldi in Windows?

Hi all, I recently switched from Linux to Windows 10 and I'm trying to get convert-ly to work in Frescobaldi 3. The "OK" button is greyed out and "Run Again" seems not to do anything. What path should I be using for convert-ly? My Lilypond installations are C:\Program Files\LilyPond\2.xx.x\.

Re: Force Lilypond to preserve vertical order of TextScripts?

Is that the same scenario? By "encountered first" is the doc referring to the parser or to the moment in musical time? I can attempt turning off skylines, but I suspect the score will just explode. I haven't had time to construct a controlled example of the squished spacing. Seems hard to make it

Re: Force Lilypond to preserve vertical order of TextScripts?

I'm actually surprised that ordering behavior isn't documented. It's so consistent 99% of the time I just assumed it was officially defined behavior. On Sun, Feb 18, 2018 at 6:30 PM, Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Saul, > > > I probably will write such a function >

Re: Force Lilypond to preserve vertical order of TextScripts?

I probably will write such a function to deal with my immediate needs, but I raise the issue because this is a case where Lilypond has well defined behavior MOST of the time, and then sometimes violates it. Normally, when you write ^"one"^"two" you expect "two" to be displayed above "one." It

Re: Force Lilypond to preserve vertical order of TextScripts?

Sun, Feb 18, 2018 at 6:18 PM, Mason Hock <ma...@masonhock.com> wrote: > On 02/18, Saul Tobin wrote: > > This is exactly the sort of situation I'm talking about. You're correct > > that the order doesn't change the meaning, just as changing the vertical >

Re: Force Lilypond to preserve vertical order of TextScripts?

Indeed. However, the vertical order of expressions is part of content, not a purely graphical layout issue. On Sun, Feb 18, 2018 at 1:08 PM, David Kastrup <d...@gnu.org> wrote: > Saul Tobin <saul.james.to...@gmail.com> writes: > > > It seems very un-Lilypond-like

Re: Force Lilypond to preserve vertical order of TextScripts?

. IMO this workaround amounts to deprecating the use of multiple TextScripts as undefined behavior. On Sun, Feb 18, 2018 at 3:30 AM, David Kastrup <d...@gnu.org> wrote: > Saul Tobin <saul.james.to...@gmail.com> writes: > > > That's a reasonable workaround, but it's not s

  1   2   >