Color parenthesized accidentals with \accidentalStyle teaching

Just in case anyone is wondering, `AccidentalCautionary` is the GROB to override to color the parenthesized accidentals you get with `\accidentalStyle teaching`. -Paul %%% \version "2.21.0" \new Staff {   \key g \major   \accidentalStyle teaching   \override AccidentalCautionary.color =

Template for flexible vertical spacing \paper variables

I got tired of looking up the flexible vertical spacing \paper variables: http://lilypond.org/doc/v2.19/Documentation/notation/flexible-vertical-spacing-paper-variables So I put together some boilerplate (below) that I can use as a snippet in Frescobaldi.  Just un-comment the lines and tweak

Re: Please test new lilypond installers

On 1/29/19 1:24 PM, David Kastrup wrote: Paul Morris writes: On 1/29/19 4:19 AM, Knut Petersen wrote: lilypond-2.21.0-1.linux-64.sh Installed on Ubuntu 18.04.1 LTS and tested with a couple of pieces. Everything appears to be working fine. Thanks to all for the work on GUB and the next

Re: Please test new lilypond installers

On 1/29/19 4:19 AM, Knut Petersen wrote: lilypond-2.21.0-1.linux-64.sh Installed on Ubuntu 18.04.1 LTS and tested with a couple of pieces. Everything appears to be working fine. Thanks to all for the work on GUB and the next stable LilyPond release! -Paul

Re: lilypond.org Productions page

On 12/10/18 5:07 PM, Federico Bruni wrote: I've just remembered another one, Paul Morris' Clairnote sheets: https://clairnote.org/sheet-music/ Oh, I like that one! :-) This free "Anthology of Melodies for Sight-Singing" would be good to include: http://www.lightandmatter

Re: Automatically set the page size to fit the music

Hi Robert, On 04/15/2018 11:56 AM, Robert Hickman wrote: I'm using 2.18 but -dpreview seems to do what I want. Okay, yeah that works as long as the music fits on the first system on the page.  These other features will work when the music is longer than that. -Paul

Automatically set the page size to fit the music

Hi, On 04/15/2018 10:56 AM, Robert Hickman wrote: > I'm trying to set the page size so that it automatically > matches the size of the staff with zero margins. Take a look at "One-page page breaking" and "One-line-auto-height page breaking":

Re: calling lilybin (or similar) as a service triggered from a [JavaScript?] form in a web page

On 03/13/2018 11:54 AM, Kieren MacMillan wrote: Hello all, Has anyone tried to set up a form (e.g., Javascript) in a web page which, when submitted, triggers a Lilypond-on-server (LoS?) application/environment (e.g., lilybin.com) and returns a PDF? I'd like to offer some music and music

Re: SVG output - Group multiple grobs together

Hi James,  I'm cc'ing the user list, as per the usual custom. On 01/11/2018 08:13 AM, James Opstad wrote: Thanks. I will work through David's example. It seems it isn't possible to embed more than one item within a group and one group per grob is the only approach for the time being. If

Re: Non-standard ledger lines and articulations collisions

On 01/11/2018 04:20 AM, David Kastrup wrote: Or let grob-transformer do all of the work. Thanks for the tip!  That's the perfect tool for the job.  And I can also use it for other cases where I have been using before-line-breaking.  For the archives, below is the example expanded to show

Re: Non-standard ledger lines and articulations collisions

On 01/10/2018 10:57 AM, David Kastrup wrote: You are missing the difference between ly:side-position-interface::y-aligned-side and side-position-interface::y-aligned-side . The latter is defined in scm/output-lib.scm as (define-public side-position-interface::y-aligned-side

Re: SVG output - Group multiple grobs together

On 01/10/2018 06:51 AM, James Opstad wrote: How would I include multiple grobs within the same group e.g. all the grobs associated with a single note (NoteHead, Stem, Accidental etc.)? Hi, I don't think there is currently a way to do that.  You could give each grob you want to group together

Non-standard ledger lines and articulations collisions

Hi all,  I'm working on a work-around for a collision between ledger lines and articulations, for Clairnote an alternative notation system: http://clairnote.org/sn/  LilyPond does not currently take non-standard 'extra' ledger lines into account when positioning articulations.  Here's a

Re: Choice of pitch input mode

> On May 1, 2016, at 8:38 AM, Paul Morris <p...@paulwmorris.com> wrote: > > I just tried it and it requires the explicit reference pitch like: \fixed > c’’ { … } …and that makes sense because the first note may not be in the b

Re: Choice of pitch input mode

> On May 1, 2016, at 3:46 AM, Johan Vromans wrote: > > Can this also be written as: > > \fixed { > \key a \major > \time 6/8 > cis''8. d16 cis8 e4 e8 | > b,8. cis16 b,8 d4 d8 | > } > > just like \relative? No, I just tried it and it requires the explicit reference

Re: Choice of pitch input mode

> On Apr 29, 2016, at 6:56 PM, Jeff Olson wrote: > > And for the limited range of a guitar (3.5 octaves) I can \transpose c c' > to minimize the number of octave marks in absolute mode (so range is e, to > b''). > Thus I never encounter long high runs of 32nds above c'''.

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

> On Apr 24, 2016, at 11:15 AM, David Kastrup <d...@gnu.org> wrote: > > Paul Morris <p...@paulwmorris.com> writes: > >> IIUC, wouldn’t the first step be, in any case, to get LilyPond’s >> python scripts working on python 2.7? > > Which ones _aren't

Re: Python 3, was Re: ANN: Frescobaldi 2.19.0

IIUC, wouldn’t the first step be, in any case, to get LilyPond’s python scripts working on python 2.7? Then at that point we could discuss and decide about whether it’s better to switch to python 3 or to support both 2.7 and 3. Searching the LilyPond source code for files with extension “.py”

Re: What is the proper way of programmatically generating markup?

> On Apr 23, 2016, at 11:00 PM, Matt Hood wrote: > > **So my second question is: How do I programmatically generate markup from > information taken from a list, and then put it into a single markup > variable?** Hi again, I’d suggest looking at snippets in the LSR,

Re: What is the proper way of programmatically generating markup?

> On Apr 23, 2016, at 11:00 PM, Matt Hood wrote: > > does anyone know where can I find the source (scm or otherwise) for > \compoundMeter? You’ll find it in ly/music-functions-init.ly Hope that helps, -Paul___ lilypond-user

Re: ANN: Frescobaldi 2.19.0

Hi Andrew, > On Apr 22, 2016, at 8:12 PM, Andrew Bernard wrote: > > The 2.19 release seems premature. The contents of the tar file have code that > clearly refers to Qt4. Um, so... 2.19 still uses Qt4. In the future, version 3.0 will require Qt5 (and Python3).

Re: I'm not smart enough to figure out the math for this.

> On Mar 9, 2016, at 6:27 PM, David Kastrup wrote: > > \version "2.19.28" > > show = > #(define-music-function (mup item) (markup? symbol-list-or-music?) > (propertyTweak 'stencil > (lambda (grob) >(grob-interpret-markup grob mup)) > item)) > > \relative c' \new Staff {

Re: Lilypond structure / implicit - explicit / with statement

> On Apr 4, 2016, at 6:46 AM, Bernard wrote: > > I have attached some more real live code using /with and and example I tried > to skip the /with section and assign properties directly, which fails. Here’s how to fix your example (without \with) that was not

Re: Lilypond structure / implicit - explicit / with statement

> On Apr 3, 2016, at 11:53 AM, Paul Morris <p...@paulwmorris.com> wrote: > > This should help: > http://lilypond.org/doc/v2.18/Documentation/notation/changing-context-default-settings#index-_005cwith-3 See also: http://lilypond.org/doc/v2.18/Documentation/notation/modifying-co

Re: Lilypond structure / implicit - explicit / with statement

Hi Bernard, > On Apr 3, 2016, at 10:59 AM, Bernard wrote: > > All boils down to what is the \with statement. This should help: http://lilypond.org/doc/v2.18/Documentation/notation/changing-context-default-settings#index-_005cwith-3 I found that section by looking

Re: Fonts from the former fonts.openlilylib.org

> On Mar 27, 2016, at 4:13 AM, tisimst wrote: > > I have considered Patreon before, but before I jump into that, does anyone > else have any other suggestion? Gratipay (formerly Gittip) is worth considering: https://gratipay.com/ It is more radical than Patreon

Re: Piano_Tab Notation; Tie customization

Hi Philip, > On Mar 10, 2016, at 3:40 PM, Philip Bergwerf > wrote: > > i was thinking about tweaking > the ties. Is it possible in lilypond to make a horizontal straight line > between tied notes? I’m pretty sure tie shapes can be customized. Maybe take a look at

Re: Piano_Tab Notation; questions ;-)

Hi Philip, Glad you found the information on the MNP site helpful. I’ve been down many of these paths in order to get LilyPond to support Clairnote music notation (http://clairnote.org). (At some point you might want to look at my clairnote-code.ly file (http://clairnote.org/software/).)

Re: Accessing Context Properties

Hi Abraham, > On Feb 25, 2016, at 12:28 PM, tisimst wrote: > > I'm asking this because I know that if I can get my hands on a grob, I know > how to access its properties (with ly:grob-property) and use that property's > value to make a change if I want (e.g., with

Re: Using path expressions to override stencils

Hi Paul, If you are using 2.19 you might want to use "make-path-stencil” instead. (It is not in 2.18 and so not in the LSR yet. Although maybe we should add it commented out?) It calculates the extents of the stencil for you so you don’t have to specify them. See below. Cheers, -Paul

Re: Using path expressions to override stencils

> On Feb 16, 2016, at 8:35 AM, Paul Booker wrote: > > I've only narrowed the problem down to the function Hi Paul, Can you send a full but tiny example that we can run/test with LilyPond? See: http://lilypond.org/tiny-examples.html That will make it easier to see what’s

Re: Detect slurred notes in callback function

> On Feb 7, 2016, at 5:42 PM, David Nalesnik wrote: > > Slur grobs store a pointer to an array of NoteColumns they encompass. So, > expanding on Paul's solution, you could do something like this: Very nice solution! Might be worth an LSR snippet as a good example of

Re: list of thicknesses affected by changing StaffSymbol.thickness

> On Jan 31, 2016, at 5:15 PM, Simon Albrecht wrote: > > I do think that it should be easier to override staff line thickness in a > style sheet without changing other line thicknesses. This would indeed be a good thing. In the meantime, this snippet shows a possible

Re: list of thicknesses affected by changing StaffSymbol.thickness

> On Feb 8, 2016, at 11:33 AM, Paul Morris <p...@paulwmorris.com> wrote: > > To make things easier, I can imagine a user function that returns a list of > line positions based on a thickness argument (and maybe optionally a line > pattern list). So for a staff with a si

Re: Detect slurred notes in callback function

Hi Jakub, FWIW, here’s another approach that starts from slurs and goes to note heads. (Adapted from some code for tied notes where this works a little more cleanly since ties connect to note heads directly rather than to note columns…) Unfortunately, this one also doesn’t color notes in

Re: Super and sub

> On Feb 7, 2016, at 8:50 AM, Phil Holmes wrote: > > I wasn't aware that git-cl "always fails". Could you describe the problem > and provide a traceback? > > Is everyone having the same problem? It has been working fine for me. (I think I remember once where it didn’t

Re: Removing white space from svg output

> On Feb 1, 2016, at 8:00 PM, Paul Booker wrote: > > Interesting! > I had a go, guessing with > >paper-height=#(one-line-auto-height-breaking) Try this: % \version "2.19.36" \paper { page-breaking = #ly:one-line-auto-height-breaking } { c1 }

Re: Removing white space from svg output

> On Feb 1, 2016, at 10:15 PM, Paul Booker wrote: > > Ok, that wasn't clear, got it now, thanks > Works for one-line parts but also converts two line pieces to one line, > ignoring the \break. Can I reinstate that somehow, without the white-space? Not with this function. It

Re: Removing white space from svg output

Hi Paul, > On Feb 1, 2016, at 7:36 AM, paul booker wrote: > > Can anyone see this becoming a scheme function which could sit in my > defs.ily file and save this ugly step? > I guess I mean an internal to Lilypond rather than external solution. > I'm not at all familiar with

no-ledgers not working with NoteHead.before-line-breaking

Any ideas why this doesn’t work? Thanks, -Paul \version “2.19.35" % works: { \override NoteHead.no-ledgers = ##t c c c c } % nope: { \override NoteHead.before-line-breaking = #(lambda (grob) (ly:grob-set-property! grob 'no-ledgers #t)) c c c c }

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 5:35 AM, Chris Yate wrote: > > BTW, is there a standard term for non-accidental notes? You would think it > would be “natural notes” but sometimes natural notes are also accidental > notes. > > In a chromatic scale, what are the accidental notes?

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 4:35 AM, David Kastrup wrote: > > CBA player here. The problem I see is more one that such "even > notation" doesn't match well with our standard tonalities. Play a C > major scale. Now do an accompaniment in "Küchenmädchenterzen", namely > just play the

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 5:40 AM, Chris Yate wrote: > > Unless they spend their lives playing on their own at home, musicians have > eventually to play with other people who will have learnt a method of > notation that's been good for 400 years. Yikes, it’s not that grim.

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 7:35 AM, Chris Yate wrote: > > As it is, when I mark up confusing music I sometimes use an upside-down "V" > to indicate semitones, "=" to indicate 'same note' and a square bracket (like > upside down "|__|") between notes to indicate a tone. This is

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 7:45 AM, David Kastrup wrote: > > Sharon Rosner writes: > >> But seriously, I see no reason to change a system which works so well >> for so many different kinds of music. All these alternative systems, I >> don't see what advantage they

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 8:18 AM, Sharon Rosner wrote: > > Of all alternative systems discussed on this thread, the only one which is > really appropriate for transposition is the "Lines a Whole Step Apart" > system (http://musicnotation.org/systems/gallery/). There it is just a

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 4:49 AM, musicus wrote: > > I really admire the effort and courage of alternative notation systems, but I > cannot see a reasonable improvement in this case. I don't think it's a good > idea to remove all great advantages, which our standard notation

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 11:24 AM, David Kastrup wrote: > > "in-key"? Hmmm, yeah, that works and is clear. I think I’ll start using that. Thanks, -Paul ___ lilypond-user mailing list lilypond-user@gnu.org

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 12:01 PM, Sharon Rosner wrote: > > So you see, it's quite a straight-forward a technique. Yes, accidental > translation can be tricky, but with practice it becomes second nature. And > again, 300 years ago it was considered a basic skill for any musician

Re: simplifying chromatic scale notation

> On Jan 26, 2016, at 11:12 AM, Chris Yate wrote: > > Yes, you're probably right. > > Though whatever you choose would have to be: > > 1) equally easy to read in all keys (which is demonstrably NOT the case for > traditional notation) > 2) easy to manage when key changes

Re: simplifying chromatic scale notation

> On Jan 25, 2016, at 4:19 PM, musicus wrote: > > See attached. Comments, suggestions are very welcome ;) Hi musicus, I think you’re right that standard notation is not as good as it could be for such chromatic music, and you have an interesting approach for improving

Re: Accessing Grob properties

> Am 22.01.2016 um 21:54 schrieb David Kastrup: >>> However, from there I don't get any further, and it seems I totally don't understand how the Scheme types are matched in C++. Any attempt to compare the content of beam_count_prop with a set of predefined values seems to fail, and

Re: Access a stem’s notehead

On January 22, 2016 7:47:11 AM EST, Simon Albrecht wrote: >How do I retrieve the >NoteHead from the Column? Hi Simon, this snippet should help: http://lsr.di.unimi.it/LSR/Item?id=621 It shows how to get a Stem from a NoteHead, using ly:grob-object That way may be

Re: Access a stem’s notehead

> On 22.01.2016 16:11, Simon Albrecht wrote: >> The feature is designed for a very specific case: Renaissance vocal music, >> one voice per staff, no chords, no dynamics etc. With this callback, I crop >> those stems which protrude beyond the staff, such as to allow for still >> closer vertical

Re: ly:one-page-breaking (was: ly:one-line-breaking)

> On Jan 19, 2016, at 4:02 AM, Richard Shann wrote: > > That's great news! For the application to Denemo taglines and footnotes > are not wanted anyway as it is for creating a score to play from > on-screen. > I guess it will be some time before this code gets into a

ly:one-page-breaking (was: ly:one-line-breaking)

> On Jan 9, 2016, at 1:30 PM, Richard Shann wrote: > > I was wondering if it would be possible to develop a variant of "all on > one line", namely "all on one page", where the page height would be > automatically adjusted to fit the music, leaving the width as set. I’m

ly:one-page-breaking (was: ly:one-line-breaking)

> On Jan 9, 2016, at 1:30 PM, Richard Shann wrote: > > I was wondering if it would be possible to develop a variant of "all on > one line", namely "all on one page", where the page height would be > automatically adjusted to fit the music, leaving the width as set. I’m

Re: Outliner markup command

Hi Harm, > On Jan 15, 2016, at 5:58 PM, Thomas Morley wrote: > > The only way I've found, is to delete all color-settings from the > stencil-expr. > Anyone with a better idea? > > Below you'll find what I did. > Fixes `stencil-whiteout-outline' by applying newly

Re: Outliner markup command

> On Jan 13, 2016, at 7:45 AM, David Kastrup wrote: > > This is the correct version of the \override #'(color . red) you wrote > which does not work. Whether the above works depends on whether the > following markup actually uses the color property, of course. Indeed, the

Re: Outliner markup command

> On Jan 12, 2016, at 6:09 PM, Thomas Morley wrote: > > Though, there might be a bug in `stencil-whiteout-outline', Paul cc-ed. > > Look at: > > \markup \stencil > #(stencil-whiteout-outline > (make-filled-box-stencil '(-1 . 1) '(-1 . 1)) > 0.5 > red > 16 > 1) >

Re: ly:one-line-breaking

> On Jan 9, 2016, at 1:30 PM, Richard Shann wrote: > > I was wondering if it would be possible to develop a variant of "all on > one line", namely "all on one page", where the page height would be > automatically adjusted to fit the music, leaving the width as set.

Re: ly:one-line-breaking

> On Jan 9, 2016, at 1:30 PM, Richard Shann wrote: > > I could not see where the ly:one-line-breaking algorithm was written > however (looking in the .scm and .ly files) is it in C++ ? Yes, see: lily/page-breaking-scheme.cc lily/one-line-page-breaking.cc HTH, -Paul

Rewriting an expression that uses ly:make-simple-closure

Hi all, Here’s a tricky one… I’m working on updating a piece from the Mutopia Project[1] (from LilyPond 2.16.1 to 2.19.35) and it uses the following: centermarkup = { \once \override TextScript.self-alignment-X = #CENTER \once \override TextScript.X-offset =#(ly:make-simple-closure

Re: Staff customization question.

> On Jan 5, 2016, at 11:03 AM, Hwaen Ch'uqi wrote: > > Yes, I had seen this snippet before. It appears though that this > function assumes a certain regularity - i.e., by semitones, whole > tones, etc. In this case, the intervals between pitches are not > uniform, varying

Re: turn off tab double half note stems

> On Jan 3, 2016, at 3:11 PM, Marc Hohl wrote: > > I am responsible for the double stems in tablature, but I did not invent them > ;-) > > AFAIK, there is no common standard for tablature with stems. > > I found the double-stemmed variant in some examples and found it quite >

Re: Staff customization question.

> On Jan 4, 2016, at 8:48 PM, Hwaen Ch'uqi wrote: > > Is there a way to create a specific calibration of pitch > to line/space where the lowest and highest notes align with the lowest > and highest lines? Briefly, here’s a small hint: setting “staffLineLayoutFunction” in

Re: adding a markup ("sim.") to the end of a SustainPedalBracket

> On Dec 27, 2015, at 7:25 PM, David Kastrup wrote: > >> (2) >> The doc-string for `stencil-whiteout' implies that @var{thickness} is >> optional. As far as I understand it's not. You’re right that the doc-string is misleading. @var{thickness} is required as an argument but if

Re: Strings as variable names

> On Jan 3, 2016, at 10:06 AM, David Wright wrote: > > Recognising the lack of this construct, python is currently adding string > interpolation to the language. Looks like a trend as Javascript also got it in the ECMAscript 2015 specification:

Re: guileV2 and Lilypond (was: Strings as variable names)

> On Jan 3, 2016, at 11:14 AM, Menu Jacques wrote: > > A newbie question: what are the expected benefits and challenges of moving > from guile 1.8.x to guile 2.y? As I understand it, guile 2.0 introduced significant performance improvements, mainly for compiled scheme, but

Re: turn off tab double half note stems

> On Dec 29, 2015, at 11:02 AM, Steve Fullerton wrote: > > In tab, lilypond draws a double stem for half notes. This is done > intentionally to distinguish half notes from quarter notes. I’m curious about these double stems. Does anyone know if they are a common/standard

converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

Hi Andrew, > On Dec 12, 2015, at 10:38 AM, N. Andrew Walsh > wrote: > > I've been doing some background work on my just-intonation accidentals, and I > was hoping you could give me some advice on the svg-to-path translation. I > know what the stencils should look

Re: converting svg glyph to path data for use in scheme (was: accidentals for just intonation)

> On Dec 12, 2015, at 3:34 PM, Johan Vromans wrote: > > If I understand the procedure correctly, wouldn't it be easier to use a > tool like fontforge add/adjust font glyphs? Maybe so, but the result is less portable because (if I understand correctly) you'd have to have a

Re: accidentals for just intonation

> On Dec 1, 2015, at 5:38 AM, Urs Liska wrote: > > You have a rather small number of individual components (vertical, > horizontal and diagonal elements) that can all represented by a > postscript path. A function should be able to determine from the input > ratio which of

Re: Introducing "LilyPond HTML Live Score"

> On Nov 29, 2015, at 1:08 PM, Mathieu Demange > wrote: > > http://www.mathieudemange.fr/lilypond-html-live-score-demo/ Nice work! This is great stuff, and I’d probably be interested in using it at some point. (Another case where the ability to automatically

Re: RFC: new location for openLilyLib repository

> On Nov 13, 2015, at 5:58 AM, Urs Liska wrote: > Regaring the location of the individual libraries, what would you consider > best: > > adding all beside oll-core > (keeping the option that anyone creates libraries in their own place) > creating a new openlilylib sibling

Re: RFC: new location for openLilyLib repository

> On Nov 13, 2015, at 5:58 AM, Urs Liska wrote: > renaming the "openlilylib" repository to "snippets" > -> https://github.com/openlilylib/snippets > > NOTE: This may require users to adapt their repository set-ups and LilyPond >

Re: LilyPond-aware text editors

> On Nov 5, 2015, at 10:18 AM, Urs Liska wrote: > > Is there *any* tool around that offers more than a notepad application > but doesn't try to be an IDE? There’s a bundle that provides LilyPond syntax highlighting for TextMate:

Re: My finances for working on LilyPond

> On Oct 27, 2015, at 8:19 PM, Bruno Ruviaro wrote: > > It seems to me that Patreon (https://www.patreon.com/ > ) might be a good system in your case. Or maybe Gratipay (https://gratipay.com/) (formerly known as “gittip") which is based on

Re: My finances for working on LilyPond

> On Oct 22, 2015, at 2:55 PM, ciconia wrote: > > I'm sure many would agree with me that your hard work (and indeed that of > all lilypond contributors) is greatly appreciated. +1 I hope this appeal will lead to a more financially viable situation that will allow you to

Re: Updating library code

> On Oct 23, 2015, at 6:43 AM, Urs Liska wrote: > > How are you dealing with keeping code working and consistent? One simple thing I do, FWIW, is to add a short prefix to all my own functions. For example, instead of "do-something", I'd call it "cn-do-something". That

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

> On Oct 19, 2015, at 1:56 AM, David Kastrup wrote: > > I think your main problem is that you are using \applyContext here at > Voice level where it does not really do anything worthwhile. Ah, I see. > Try \context Staff \applyContext … That did the trick and now it works,

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

> On Oct 19, 2015, at 10:59 AM, David Kastrup <d...@gnu.org> wrote: > > Paul Morris <p...@paulwmorris.com> writes: >> >> That did the trick and now it works, thanks! >> >> \version “2.19.22” >> >> myfunc = >> #(define-music-fu

Re: \applyContext, StaffSymbol, and \stopStaff \startStaff

I found another way to do what I was trying to do. (I used \applyContext in a music function to access and then modify a custom staff context property, and then used a custom StaffSymbol engraver to access that context property and change the grob properties of any new StaffSymbol grob

\applyContext, StaffSymbol, and \stopStaff \startStaff

Greetings lilyponders, I’m trying to figure out how to use \applyContext to modify StaffSymbol grob properties. The examples here http://www.lilypond.org/doc/v2.19/Documentation/extending/context-evaluation are very helpful, but I haven’t been able to get things working with StaffSymbol

Re: OT: Beauty of programming languages

I’m in my early 40s, and started using LilyPond in early 2011. I love LilyPond’s flexibility and extensibility which lets me create sheet music in alternative notation systems that have a “chromatic staff” – especially “Clairnote”[1]. LilyPond is in a league of its own for this kind of

Re: OT: Beauty of programming languages

Forgot to say I use Frescobaldi. -Paul ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Alda "a music programming language for musicians" inspired by LilyPond

I thought this might be of interest. Alda is a LilyPond-inspired programming language for musicians to use to produce music, i.e. audio (midi, etc.). I wonder why he didn’t just use LilyPond syntax, or at least follow it more closely?

Re: Analysis brackets with text [was: how to get notes without tails?]

Hi David, > On Aug 31, 2015, at 8:20 AM, David Nalesnik wrote: > > Which of course makes them unsuitable for showing phrase elision. > > Getting a TextSpanner to begin on a note and another to start on the same > note requires some sleight-of-hand (you can see this

Analysis brackets with text [was: how to get notes without tails?]

Hi David,On Aug 30, 2015, at 3:16 PM, David Nalesnik david.nales...@gmail.com wrote:LilyPond already has the ability to make analysis brackets, which are attached to note columns and can nest as in the link (HorizontalBracket). I have an old patch for adding text to these that I will finish up and

Re: Analysis brackets with text [was: how to get notes without tails?]

Oh, one other thing I noticed. There seems to be no way to have one bracket end at a note and another bracket start at that same note. (warning: conflicting note group events”) I tried spacer rests, but no luck. It seems the start or end of a group cannot be a spacer rest. Anyway, I thought

Re: Analysis brackets with text [was: how to get notes without tails?]

Hi David, That’s great that markups already work (I should have tried it before assuming they didn’t). The plan for HorizontalBracketText sounds even better. Thanks again, -Paul ___ lilypond-user mailing list lilypond-user@gnu.org

Re: vertical spacing of rests

On Aug 23, 2015, at 4:29 PM, Peter Selinger selin...@mathstat.dal.ca wrote: - (ly:grob-set-property! rest 'stencil #f) + (ly:grob-set-property! rest 'Y-offset offset) I wonder if this might work instead: (ly:grob-set-property! rest 'stencil empty-stencil) Just an untested idea…

Re: Coloring of key signature accidentals based on their pitch

Hi David, On Aug 21, 2015, at 9:57 AM, David Nalesnik david.nales...@gmail.com wrote: You're welcome. Just for kicks, I've attached a .cc file which you could drop into the lily subdirectory and build. It makes Line_interface::line available to Scheme. You'd just need to replace the two

Re: Coloring of key signature accidentals based on their pitch

Hi David, On Aug 19, 2015, at 10:27 PM, David Nalesnik david.nales...@gmail.com wrote: Thanks for doing this! (I should have thought to write it this way in the first place!) Glad to! Thanks for leading the way on how to convert these C++ functions to Scheme. By the way, later in the

Scheme version of ly:ledger-line-spanner::print

Recently I looked into trying to rewrite ly:ledger-line-spanner::print in Scheme, in order to do some customization of ledger lines. I didn’t get very far... I then tried to wrap it in my own function in order to post-process the stencil it produced. But I found it produces one stencil per

Re: Coloring of key signature accidentals based on their pitch

On Aug 18, 2015, at 9:31 PM, David Nalesnik david.nales...@gmail.com wrote: (Not long ago I was looking at the C++ function that draws ledger lines (ly:ledger-line-spanner::print in ledger-line-spanner.cc http://ledger-line-spanner.cc/), thinking about overriding it with a custom

Re: Coloring of key signature accidentals based on their pitch

On Aug 18, 2015, at 7:13 PM, Thomas Morley thomasmorle...@gmail.com wrote: I wonder if this function would better be defined in Scheme than C++. If someone wanted to do something like you're doing, it wouldn't be a trivial matter to first redo the function in Scheme to make the necessary

Re: Centering a stencil on another stencil

Here’s another possibility that uses an optional axis argument. -Paul \version 2.19.22 #(define* (center-stencil-on-stencil stil-a stil-b #:optional axis) Return a copy of stencil @var{stil-b} that has been moved so it is centered on stencil @var{stil-a} on @var{axis}. When @var{axis}

Re: Centering a stencil on another stencil

Hi Harm, On Aug 13, 2015, at 3:43 PM, Thomas Morley thomasmorle...@gmail.com wrote: I like this best and would go for it. Sounds good ...and done: http://lsr.di.unimi.it/LSR/Item?id=1009 Regretable my vacations ended. Meaning I've reasonable less time :( I suppose all good things must

Re: Centering a stencil on another stencil

On Aug 11, 2015, at 8:23 PM, Thomas Morley thomasmorle...@gmail.com wrote: I'm still not happy with the example, because the second stencil, the circle, is centered already. Ah, right, so your two squares example is better than the circle one. Lets use it for the LSR snippet. As a

  1   2   3   4   5   6   7   >