Re: Making notes have no presence at all (horizontal brackets)

Hi Kevin, > I need to add a voice with notes that are a) invisible and b) have no effect > on the spacing of other music on the staff. I haven't found a way to do this What about: \score { \new Staff << \mark \markup "rests, omitted" \global \new Voice \relative { bes,8-\twe

Good style sheet for hymnal?

I'm possibly going to be taking on a hymnal project, and would like to know if anyone has come up with a good style-sheet for lilypond engraving at small sizes in hymnals! Thanks! ​Sincerely, Josh ___ lilypond-user mailing list lilypond-user@gnu.org ht

Making notes have no presence at all (horizontal brackets)

Dear All, I frequently need to have overlapping horizontal brackets. This means that I have to add hidden notes to my scores to attach them to. (Brackets won't attach to spacer rests unless they live in a Staff context, in which case you can't have more than one at a time. Adding brackets to both

Re: Outliner markup command

2016-01-13 16:17 GMT+01:00 Paul Morris : >> 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

Re: Overriding tie-configuration & \shape breaks custom Scheme function since 2.19.24

David Kastrup writes: > Malte Meyn writes: > >> Am 10.01.2016 um 02:50 schrieb Peter Crighton: >>> (if (or (music-is-of-type? mus 'rest-event) >>> (music-is-of-type? mus 'multi-measure-rest)) >> >> The overrides fall into the ‘else’ case and th

Re: Outliner markup command

Thank you Simon for this clear explanation. Pierre 2016-01-13 20:17 GMT+01:00 Simon Albrecht : > On 13.01.2016 13:24, Pierre Perol-Schneider wrote: > >> Hi David, >> >> 2016-01-12 23:52 GMT+01:00 David Kastrup mailto:d...@gnu.org >> >>: >> >> \override #`(color . ,red) >> >> And yes, I us

Re: Repeat 8va

On 13.01.2016 20:02, John Gourlay wrote: There it is! I don’t know why I missed it the first time. I”m sorry to be a bother. Never mind, the docs _are_ difficult to penetrate sometimes… Yours, Simon ___ lilypond-user mailing list lilypond-user@gnu.

Re: Outliner markup command

On 13.01.2016 13:24, Pierre Perol-Schneider wrote: Hi David, 2016-01-12 23:52 GMT+01:00 David Kastrup >: \override #`(color . ,red) And yes, I use a backward tick here. The forward tick will not cooperate with the comma later. I'm not sure to clearly unders

Re: Behavior of non-flag side with strictBeatBeaming

The second is simply the easiest to read. HTH Pierre 2016-01-13 18:59 GMT+01:00 Kieren MacMillan : > Hi Urs, > > > which of the attached engravings do you prefer, LilyPond's current or > the modified? > > The second. > And Gould agrees. =) > > Hope this helps! > Kieren. > ___

Re: Repeat 8va

There it is! I don’t know why I missed it the first time. I”m sorry to be a bother. > On Jan 13, 2016, at 1:50 PM, Trevor Daniels wrote: > > > John, you wrote Wednesday, January 13, 2016 6:18 PM > >> I’m still puzzled by the lack of documentation for \transposition, however. >> How have you

Re: Repeat 8va

John, you wrote Wednesday, January 13, 2016 6:18 PM > I’m still puzzled by the lack of documentation for \transposition, however. > How have you all learned to use it, by word of mouth? No :), you'll find it here: http://www.lilypond.org/doc/v2.19/Documentation/notation/displaying-pitches#inst

Re: Repeat 8va

Using \unfoldRepeats in a separate \score for the midi output works. Thank you, Malte. I’m still puzzled by the lack of documentation for \transposition, however. How have you all learned to use it, by word of mouth? John Gourlay ___ lilypond-user m

Re: Behavior of non-flag side with strictBeatBeaming

Hi Urs, > which of the attached engravings do you prefer, LilyPond's current or the > modified? The second. And Gould agrees. =) Hope this helps! Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info __

Re: Behavior of non-flag side with strictBeatBeaming

> given the following input > > \relative a' { > \time 6/8 > \set strictBeatBeaming = ##t > a8.. a32 a16 a > } > > which of the attached engravings do you prefer, LilyPond's current or > the modified? [Both images are called `document.png', which is not optimal :-)] I prefer the second on

Re: Behavior of non-flag side with strictBeatBeaming

Am 13.01.2016 um 18:23 schrieb Urs Liska: > > > Am 13.01.2016 um 18:09 schrieb Urs Liska: >> Hi all, >> >> one more beaming question, >> >> given the following input >> >> \relative a' { >> \time 6/8 >> \set strictBeatBeaming = ##t >> a8.. a32 a16 a >> } >> >> which of the attached engravin

Re: Behavior of non-flag side with strictBeatBeaming

Am 13.01.2016 um 18:09 schrieb Urs Liska: > Hi all, > > one more beaming question, > > given the following input > > \relative a' { > \time 6/8 > \set strictBeatBeaming = ##t > a8.. a32 a16 a > } > > which of the attached engravings do you prefer, LilyPond's current or > the modified? > Wou

Behavior of non-flag side with strictBeatBeaming

Hi all, one more beaming question, given the following input \relative a' { \time 6/8 \set strictBeatBeaming = ##t a8.. a32 a16 a } which of the attached engravings do you prefer, LilyPond's current or the modified? Would it make sense to add a beaming option (e.g. "strictBeatBeamingNonFl

RE: Microtonal notation - arrows up and down

Dear Graham, I tried to find information on how to do it on internet, but I am unable to find anything. I am sorry to continuously asking, but can you give me any hint on how to do it? (I tried to update all the software in Ubuntu, but I am already the newest version) Kind regards, Luca >

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) > > \markup \stencil > #(ste

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 “\whiteout" markup com

Re: Outliner markup command

OK thanks David. 2016-01-13 13:45 GMT+01:00 David Kastrup : > Pierre Perol-Schneider writes: > > > Hi David, > > > > 2016-01-12 23:52 GMT+01:00 David Kastrup : > > > > > >> \override #`(color . ,red) > >> > >> And yes, I use a backward tick here. The forward tick will not > >> cooperate with th

Re: Outliner markup command

Pierre Perol-Schneider writes: > Hi David, > > 2016-01-12 23:52 GMT+01:00 David Kastrup : > > >> \override #`(color . ,red) >> >> And yes, I use a backward tick here. The forward tick will not >> cooperate with the comma later. >> > > I'm not sure to clearly understand what I can do here but i'l

Re: Outliner markup command

Hi David, 2016-01-12 23:52 GMT+01:00 David Kastrup : > \override #`(color . ,red) > > And yes, I use a backward tick here. The forward tick will not > cooperate with the comma later. > I'm not sure to clearly understand what I can do here but i'll investigate anyhow. Thanks for the tip. Pierre

Re: Outliner markup command

Hi Harm, 2016-01-13 0:09 GMT+01:00 Thomas Morley : > You can't hope a markup-command will accept an override for a > property, if said property isn't declared in any way. > Well, I thought it *was *declared since the code description says : "This function works by creating a series of white or

Re: Beaming over a rest before a subdivision

Am 13.01.2016 um 10:08 schrieb Mark Knoop: > At 22:57 on 12 Jan 2016, Urs Liska wrote: >> Am 12.01.2016 um 20:59 schrieb Werner LEMBERG: What should the behavior of the *last* one be here? >>> No beams over the rest. >> Well, default behaviour is to break the beam at all rests here (see

Re: Beaming over a rest before a subdivision

At 22:57 on 12 Jan 2016, Urs Liska wrote: >Am 12.01.2016 um 20:59 schrieb Werner LEMBERG: >>> What should the behavior of the *last* one be here? >> No beams over the rest. > >Well, default behaviour is to break the beam at all rests here (see >attached). Not sure if this is relevant to your c

Re: startGraceMusic

On 13.01.2016 07:27, Andrew Bernard wrote: There are startGraceMusic and stopGraceMusic functions that are helpful for adjusting the appearance of grace notes. Are there startAfterGraceMusic etc functions for \afterGrace? Currently I have to manually adjust afterGrace notes to be the same as th