Re: Determining what parameters exist for an item

Kieren MacMillan writes: > Hi Carl, > >> 4) Going to one of these interfaces […] >> provides a list of user-settable properties for that interface > > Yes, but unless I’m missing something, you can’t find the default > value(s) there, right? Interfaces don't have

Re: Blank bars for scribbling in

Hi Richard, You can use 'proportionalNotationDuration' e.g.: \version "2.19.35" \relative { %% example 1 c' d e f \set Score.proportionalNotationDuration = #(ly:make-moment 1/64) \hideNotes %% Notes are kwnown but won't be shown g a b c \unset Score.proportionalNotationDuration

Blank bars for scribbling in

In some contexts people want music interspersed with blank bars to be filled in later by hand. Spacer rests achieve this, but I can't track down any straight-forward way of controlling the size of the blank bar. Anyone any ideas on this? Richard ___

Re: Blank bars for scribbling in

e.g. : \version "2.19.35" blankBar = #(define-music-function (my-duration notes) (integer? ly:music?) #{ \set Score.proportionalNotationDuration = #(ly:make-moment 1 my-duration) \hideNotes #notes \unHideNotes \unset Score.proportionalNotationDuration #}) \relative { %% example 1

Re: Blank bars for scribbling in

... and of course, this can be included in a music function: http://www.lilypond.org/doc/v2.19/Documentation/extending/intermediate-substitution-functions.html ~Pierre -- View this message in context: http://lilypond.1069038.n5.nabble.com/Blank-bars-for-scribbling-in-tp186334p186336.html Sent

Re: Blank bars for scribbling in

Am 24.01.2016 um 10:55 schrieb Richard Shann: > In some contexts people want music interspersed with blank bars to be > filled in later by hand. Spacer rests achieve this, but I can't track > down any straight-forward way of controlling the size of the blank bar. > Anyone any ideas on this? > >

Re: Edition-engraver: Multiple editions in same file

Thank you Jan-Peter and Kieren, That helps clear up a lot of my confusion. Ben > On Jan 24, 2016, at 2:24 PM, Jan-Peter Voigt wrote: > > Hi Ben, > > I was about to write about the three dimension to watch. But I have to think > about it, if I can change this. > For now

Re: Controlling hairpin length

On Sat, 2016-01-23 at 13:27 +0100, Thomas Morley wrote: > 2016-01-21 16:54 GMT+01:00 David Sumbler : > > > > > Unfortunately I am still getting some over-long hairpins. I think that > > perhaps this has nothing to do with myHairpinMinimumLength, because I > > was getting

Re: Determining what parameters exist for an item

Hi David, > Interfaces don't have default values. Grobs have. That’s my point. > You mean, something like > 3.1.24 ChordName Well, that’s *those* values… Those are the ones Charles and I (and, I assume, others) know how to find easily. What, though, is the default value for

Re: Determining what parameters exist for an item

Kieren MacMillan writes: > Hi David, > >> Interfaces don't have default values. Grobs have. > > That’s my point. > >> You mean, something like >> 3.1.24 ChordName > > Well, that’s *those* values… > Those are the ones Charles and I (and, I assume, others) know how

Slashed grace with long slur

Hi, All - I'm running Ly 2.19.33 under Win7. I'm trying to transcribe a slashed grace note with a long slur, as in the attachment slur.png. I've been unable to get the slur to stay up. I've tried \slurUp in conjunction with both \slashedGrace and \acciaccatura with no success. The attached .ly

Re: Slashed grace with long slur

It worked for me to move the \slurUp command inside the \shlashedGrace, as in: \slashGrace { \slurUp e8( } d b) Kristin On Sun, Jan 24, 2016, at 08:51 AM, Ralph Palmer wrote: > Hi, All - > > I'm running Ly 2.19.33 under Win7. > > I'm trying to transcribe a slashed grace note with a long slur,

Re: Blank bars for scribbling in

On Sun, 2016-01-24 at 03:29 -0700, Schneidy wrote: > Hi Richard, > > You can use 'proportionalNotationDuration' e.g.: > > \version "2.19.35" > > \relative { > %% example 1 > c' d e f > \set Score.proportionalNotationDuration = #(ly:make-moment 1/64) Thanks - that works well. I've found

Re: Blank bars for scribbling in

Richard Shann-2 wrote > [...] > Thanks - that works well. I've found this too: > > \newSpacingSection > \override Score.SpacingSpanner.spacing-increment = #4 > [...] Yep! Much smarter!! blankBarAlter = #(define-music-function (span-lgth notes) (number? ly:music?) #{ \newSpacingSection

Re: Determining what parameters exist for an item

Hi David, > \new ChordNames > \chordmode > { > \applyOutput ChordNames.ChordName #(lambda (g c p) (display > (ly:grob-property g 'baseline-skip))) > c1 > } That’s a helpful funcion — thanks! > Those are, unless overriden by a grob, global. Exactly. As far as the user cares, the setting has

Re: Slashed grace with long slur

I'm sorry, I typoed the command both places: \slashedGrace { \slurUp e8( } d b) K. -- Kristin Rollins kris...@verumsolum.com Portsmouth, VA On Sun, Jan 24, 2016, at 09:08 AM, Kristin Rollins wrote: > It worked for me to move the \slurUp command inside the \shlashedGrace, as in: > >

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: Determining what parameters exist for an item

Hi David, > it would be easier if you did not do creative editing in order to > let everything disappear not meeting your preconceptions. It’s not clear what you’re talking about… but anyway… It’s still perfectly clear to me — and, it seems, Charles and others — that Lilypond has grobs, and

Re: Determining what parameters exist for an item

On 24.01.2016 18:22, Kieren MacMillan wrote: Lilypond has grobs, and those grobs have properties, and those properties have values, I think the point is that some properties either do not have values at all, or those values are determined during compilation, depending on other

Re: Determining what parameters exist for an item

Kieren MacMillan writes: > At that point, I say, "Let the user beware.” > > My question is: Is there a way to iterate your property display > function (or similar) through all available properties of a grob, and > output as a single list (alphabetically, if

Re: Slashed grace with long slur

On Jan 24, 2016 9:09 AM, "Kristin Rollins" wrote: > > It worked for me to move the \slurUp command inside the \shlashedGrace, as in: > > \slashGrace { \slurUp e8( } d b) > > Kristin Thanks, Kristin- I'm not at my computer now, but I'll try it as soon as possible. I

Re: Slashed grace with long slur

On 24.01.2016 15:08, Kristin Rollins wrote: It worked for me to move the \slurUp command inside the \slashedGrace, as in: \slashedGrace { \slurUp e8( } d b) Even easier: { \slashedGrace { e8^( } d b) } And, astoundingly this minimal example works here: (but your larger example doesn’t)

Re: Determining what parameters exist for an item

Kieren MacMillan writes: > Hi David, > >> it would be easier if you did not do creative editing in order to >> let everything disappear not meeting your preconceptions. > > It’s not clear what you’re talking about… but anyway… > > It’s still perfectly clear to me —

Re: Determining what parameters exist for an item

Hi again, Here’s a perfect example of what I’m talking about… For KeyCancellation, the output of Harm’s function includes GROB-INTERFACE X-extent: (0.0 . 5.82) But if I look on http://www.lilypond.org/doc/v2.19/Documentation/internals/keycancellation, there is no entry

Re: Edition-engraver: Multiple editions in same file

Hi Ben, I was about to write about the three dimension to watch. But I have to think about it, if I can change this. For now there will one set of editiontags per compilation. So every call to \addEdition and \removeEdition will affect the list of active modification-layers for the whole run.

Re: Determining what parameters exist for an item

2016-01-24 20:03 GMT+01:00 Kieren MacMillan : > Hi Harm, > >> If you really want to see all of the default properties and their >> values for a certain grob, try the code below. > > Now THIS… this is EXACTLY what I wanted; and, I infer, what Charles also > wanted. >

Re: Determining what parameters exist for an item

Hi Kieren, 2016-01-24 18:22 GMT+01:00 Kieren MacMillan : > Hi David, > >> it would be easier if you did not do creative editing in order to >> let everything disappear not meeting your preconceptions. > > It’s not clear what you’re talking about… but anyway… > >

Re: Determining what parameters exist for an item

Hi Harm, > If you really want to see all of the default properties and their > values for a certain grob, try the code below. Now THIS… this is EXACTLY what I wanted; and, I infer, what Charles also wanted. Thank you. > 1. I think you'll agree that we don't want to put it in the docs, >

Font of accidentals changes after line break

Dear Lilyponders, I usually engrave jazz lead sheets using LilyJazz, and I've noticed the following odd behaviour: If I tie a note across a manual line break, and the note has an accidental, then the LilyJazz font is not applied to the accidental of the continued note after the line break.

Re: Font of accidentals changes after line break

Am 24. Januar 2016 22:56:56 MEZ, schrieb Robert Schmaus : >Dear Lilyponders, > >I usually engrave jazz lead sheets using LilyJazz, and I've noticed the > >following odd behaviour: If I tie a note across a manual line break, >and >the note has an accidental, then the

Re: Determining what parameters exist for an item

2016-01-24 22:22 GMT+01:00 Thomas Morley : > Btw, I tested it with 2.18.2, doesn't work with \applyOutput, but with > \override Grob.after-line-breaking http://lsr.di.unimi.it/LSR/Item?u=1=1017 Best, Harm ___ lilypond-user

Re: Font of accidentals changes after line break

On 24.01.2016 22:56, Robert Schmaus wrote: If it can't be fixed easily, how can I turn off the accidental after break? I tried \override Staff.Accidental.after-line-breaking = ##f but that didn't change anything. The after-line-breaking property can be set to a procedure, which will then be

Re: Font of accidentals changes after line break

Am 24.01.2016 um 23:01 schrieb Urs Liska: > > Am 24. Januar 2016 22:56:56 MEZ, schrieb Robert Schmaus > : >> Dear Lilyponders, >> >> I usually engrave jazz lead sheets using LilyJazz, and I've noticed the >> >> following odd behaviour: If I tie a note across a manual line

Re: Determining what parameters exist for an item

On 24.01.2016 21:28, Simon Albrecht wrote: On 24.01.2016 21:15, Thomas Morley wrote: Now, if I want to reduce or enlarge KeyCancellation.X-extent, knowing that default is (0.0 . 5.82)*** gives me critical information that I can actually use as a reference point; without that information,

Re: Determining what parameters exist for an item

2016-01-24 21:32 GMT+01:00 Simon Albrecht : > On 24.01.2016 21:28, Simon Albrecht wrote: >> >> On 24.01.2016 21:15, Thomas Morley wrote: Now, if I want to reduce or enlarge KeyCancellation.X-extent, knowing that default is (0.0 . 5.82)*** gives me

Re: Determining what parameters exist for an item

Hi Harm, > Well, it is the _actual_ default. KeyCancellation _can't_ have > a general default of X-extent for all possible KeyCancellations… Obviously. =) But the benefits of the function are both general (“Get a list of every settable property for this grob.”) and specific (“Get the property

Re: Determining what parameters exist for an item

2016-01-24 20:15 GMT+01:00 Kieren MacMillan : > Hi again, > > Here’s a perfect example of what I’m talking about… > > For KeyCancellation, the output of Harm’s function includes > > GROB-INTERFACE > X-extent: > (0.0 . 5.82) > > But if I look on

Re: Determining what parameters exist for an item

On 24.01.2016 21:15, Thomas Morley wrote: Now, if I want to reduce or enlarge KeyCancellation.X-extent, knowing that default is (0.0 . 5.82)*** gives me critical information that I can actually use as a reference point; without that information, the trial-and-error factor increases

RE: Determining what parameters exist for an item

Gentlemen, Thanks for all your replies. I had no idea such a simple request would stir up such a hornet's nest. I have some good ideas to follow up on now. Charles -Original Message- From: Kieren MacMillan [mailto:kieren_macmil...@sympatico.ca] Sent: Sunday, January 24, 2016 2:04

Re: Determining what parameters exist for an item

2016-01-24 22:03 GMT+01:00 Kieren MacMillan : > Hi Harm, > >> Well, it is the _actual_ default. KeyCancellation _can't_ have >> a general default of X-extent for all possible KeyCancellations… > > Obviously. =) > > But the benefits of the function are both general

Re: Font of accidentals changes after line break

Hi Simon, thanks for your repy - I'll keep that in mind as a last resort if I can't get any other solution to work ... Cheers, Robert Am 24/01/16 um 23:22 schrieb Simon Albrecht: On 24.01.2016 22:56, Robert Schmaus wrote: If it can't be fixed easily, how can I turn off the accidental after

Re: Font of accidentals changes after line break

Hi Urs, You seem to have sent two mails - only got the second one ... strange. Anyway, thank you for your solution. I did instal openlilylib during the "Trunkne Lied" project, but haven't used it outside of that. I'll try that out asap, but I won't be able to do it tonight ... Best, Robert

Re: Determining what parameters exist for an item

On Sun, Jan 24, 2016 at 2:32 PM, Simon Albrecht wrote: > On 24.01.2016 21:28, Simon Albrecht wrote: > >> On 24.01.2016 21:15, Thomas Morley wrote: >> >>> Now, if I want to reduce or enlarge KeyCancellation.X-extent, knowing that default is (0.0 . 5.82)*** gives