Re: Possible Bug with \partcombine?
Joshua Nichols gmail.com> writes:
> I was recently typesetting a song, using part combine, from a hymnal. I ran
into a problem: everytime I ran \partcombine, I found that "unterminated
slur" and "cannot end slur," were common warnings. I was confused, and so I
created this small snippet that should reproduce the same issues.\version
"2.18.2"
>
I would call it a limitation of the design \partcombine.
\partcombine takes its two inputs and combines them when possible
into one LilyPond Voice. The resulting music goes through the
rest of LilyPond as usual, and in this case a pair of slurs starts
when \partcombine has produced two Voices, and ends when it only
has one (differnt) Voice holding the chords, so the slurs are left
dangling.
\partcombine on its own is smart enough to avoid switching from
separate stems to chords in the middle of a slur, but when we need
to override its choices, we need to take over completely.
The simplest solution here is to keep the voices separate through
the slurs
two = {
b a b \partcombineApart c'( b) \partcombineAutomaticOnce a b( c')
\partCombineAutomatic }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: would 'gn' for G-natural be useful in \language "english" ?
Ralph Palmer gmail.com> writes:
> On Sun, Nov 16, 2014 at 11:31 PM, Keith OHara oco.net>
wrote:Dear list,
> In English, pronouncing the 'natural' in 'C-natural' is required if the
note is out-of-key. LilyPond does not consider the key when reading note-
input, but could easily accept 'cn' as a name for the pitch C-natural. There
was a feature request on the bug-list, that LilyPond do so.
> Among those responding to the proposal, the Americans were in favor, while
the British Germans Dutch and Flemish opposed.
> I have started using English note-entry with 'cn', etc., for naturals when
I would say "natural" and I find it helpful. If anyone else will use it,
I'll push for it and put it in LilyPond.
>
> Hmm. . . . I am an American and I am opposed, for the reasons given in the
previous discussion(s). My 2 cents.
>
Then I'll propose that LilyPond accept 'cn' only when the user requests
that input style, and I won't call that style 'American'.
Another inconvenience with \language"english" is that its default names
are the long forms, so
\displayLilyMusic \transpose c e {fs as cs}
is not as helpful for rearranging music as it could be.
I'm proposing \language"abbreviated" for people who want to use
\displayLilyMusic to generate brief english, and/or want to type
'cn' for the same reasons that we sometimes pronounce 'natural'
in English.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Note name to markup
> On 27 Nov 2014, at 08:56, Pierre Perol-Schneider > wrote: > > Maybe this snippet could help : http://lsr.di.unimi.it/LSR/Item?id=856 It looks great, though it does not work with with microtonal pitches. I will see if I can fix that. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Chapter 3 of "LilyPond Extending" document
This chapter headed "LilyPond Scheme Interfaces" would be most useful to the tyro since it would help to get information into and out of music streams. However it is missing from the 2.18.2 documentation which relates to the 2.16.2 release. Inside the 2.18.2 source download there is a file scheme-tutorial.itely which refers to the 2.17.11 unstable version. This is somewhat different from the above but still has no chapter "LilyPond Scheme Interfaces" Is there an intention to provide this chapter or is it a low priority for the experts? Still battling on to fathom a way to recover key signature details for mods to enharmonic.ly - currently pondering key-signature-interface.cc regards Peter Gentry ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chapter 3 of "LilyPond Extending" document
On Thu, Nov 27, 2014 at 6:34 AM, Peter Gentry wrote: > > This chapter headed "LilyPond Scheme Interfaces" would be most useful to > the tyro since it would help to get information into and > out of music streams. > > However it is missing from the 2.18.2 documentation which relates to the > 2.16.2 release. > > Inside the 2.18.2 source download there is a file scheme-tutorial.itely > which refers to the 2.17.11 unstable version. This is > somewhat different from the above but still has no chapter "LilyPond > Scheme Interfaces" > > Is there an intention to provide this chapter or is it a low priority for > the experts? > I think it would be very useful, I don't know of anybody actively working on it. Speaking as somebody who could contribute to this section, I wouldn't know where to begin! One issue here is that there is much to work on in LilyPond and a rather small pool of contributors. > Still battling on to fathom a way to recover key signature details for > mods to enharmonic.ly - currently pondering > key-signature-interface.cc > As far as I can tell, enharmonic.ly is not a file in the distribution--where are you getting this? From other threads of yours which include the code, it seems you are referring to the snippet http://lilypond.org/doc/v2.18/Documentation/snippets/pitches#pitches-transposing-pitches-with-minimum-accidentals-_0028_0022smart_0022-transpose_0029 As far as your quandary, what are you trying to do? Maybe I or someone else can provide some insight. Best, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Registrations on organ and harpsichord
Hi! I have one question. It is possible to type to the lilypond notations the registration marks for Harpsichord, or organ? Thank You. Marco Oros ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Beaming and grace notes
I want to start a run of grace notes with a note with a normal head. So
like this:
\version "2.19.15"
\relative c' {
c32 \grace { d32 e f g a b } c8
}
...but with the c' beamed to the d'.
Knute Snortum
(via Gmail)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Chapter 3 of "LilyPond Extending" document
You are spot on David. I spend a lot of time transposing music for a small band of amateur wind players. I use the said snippet as an include file "enharmonic.ly" to tidy up the accidentals. My issue is that the tidy up takes no account of the current key signature and so sometimes you are left with a Gb say when there is F# in the key signature. I am trying to get at the list of sharps and flats from the keysignature interface use to force the Gb to F# (and adjust any other unpleasant accidentals). I can see that there is such data lurking about but so far I haven't been able to extract it. This has lead me into a crash course of C++ and Scheme which at 73 is proving interesting but time consuming - (I was brought up on Basic and Fortran) _ From: David Nalesnik [mailto:david.nales...@gmail.com] Sent: Thursday, November 27, 2014 3:17 PM To: Peter Gentry Cc: lilypond-user Subject: Re: Chapter 3 of "LilyPond Extending" document On Thu, Nov 27, 2014 at 6:34 AM, Peter Gentry wrote: This chapter headed "LilyPond Scheme Interfaces" would be most useful to the tyro since it would help to get information into and out of music streams. However it is missing from the 2.18.2 documentation which relates to the 2.16.2 release. Inside the 2.18.2 source download there is a file scheme-tutorial.itely which refers to the 2.17.11 unstable version. This is somewhat different from the above but still has no chapter "LilyPond Scheme Interfaces" Is there an intention to provide this chapter or is it a low priority for the experts? I think it would be very useful, I don't know of anybody actively working on it. Speaking as somebody who could contribute to this section, I wouldn't know where to begin! One issue here is that there is much to work on in LilyPond and a rather small pool of contributors. Still battling on to fathom a way to recover key signature details for mods to enharmonic.ly - currently pondering key-signature-interface.cc As far as I can tell, enharmonic.ly is not a file in the distribution--where are you getting this? From other threads of yours which include the code, it seems you are referring to the snippet http://lilypond.org/doc/v2.18/Documentation/snippets/pitches#pitches-transposing-pitches-with-minimum-accidentals-_0028_0022smart_00 22-transpose_0029 As far as your quandary, what are you trying to do? Maybe I or someone else can provide some insight. Best, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Registrations on organ and harpsichord
Hi Marco,
> It is possible to type to the lilypond notations the registration marks
for Harpsichord, or organ?
I think I know what you are trying to do. Could you give me a little more
detail?
For example, I have done this with lilypond:
\markup { \general-align #Y #0.5 \left-brace #50
\general-align #X #LEFT
\column{
\line{I. 8' Flute; II/I;}
\line{II: 8' String;}
\line{Ped. 16' Flute, String; II/Ped.}
}
}
You put this right before your score block. Make sense? Am I missing
something?
HTH,
Josh
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Possible Bug with \partcombine?
> The simplest solution here is to keep the voices separate through the slurs... Thanks, this is helpful. Is there talk about improving this feature? Or do you know of a hack for getting the desired output? Your solution will be a solid work around from here on out. Thanks. Josh ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chapter 3 of "LilyPond Extending" document
Hi Peter, On Thu, Nov 27, 2014 at 11:35 AM, Peter Gentry wrote: > You are spot on David. I spend a lot of time transposing music for a > small band of amateur wind players. I use the said snippet as an include > file "enharmonic.ly" to tidy up the accidentals. My issue is that the > tidy up takes no account of the current key signature and so sometimes you > are left with a Gb say when there is F# in the key signature. I am trying > to get at the list of sharps and flats from the keysignature interface use > to force the Gb to F# (and adjust any other unpleasant accidentals). > > I can see that there is such data lurking about but so far I haven't been > able to extract it. This has lead me into a crash course of C++ and Scheme > which at 73 is proving interesting but time consuming - (I was brought up > on Basic and Fortran) > The trouble here is that details about the key signature are stored as context properties which, as far as I know, are not directly accessible from within a music function. You could search the music expression for context modifications. Don't think it will be pretty. A simpler solution would be to add an argument which specifies the key you want to "naturalize" against. This could be annoying if you have multiple key signatures in the course of the piece--you'd need to call \naturalizeMusic each time. Hope this is somewhat helpful, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Chapter 3 of "LilyPond Extending" document
Hi again,
On Thu, Nov 27, 2014 at 2:39 PM, David Nalesnik
wrote:
>
>
> You could search the music expression for context modifications.
>
Try running this to see what kind of information would be accessible to you
from the music expression you'd be running \naturalizeMusic on:
\displayMusic {
\key e \major
cis''1
\key c \major
c''1
}
Comparing the output you can see (thankfully) that the 'KeyChangeEvent
reflects the transposition:
\displayMusic {
\transpose c d {
\key e \major
cis''1
\key c \major
c''1
}
}
You'd have to make sure that the expression on which you run
\naturalizeMusic contains the initial key, though.
HTH,
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: anti-alias-factor kills the transparency (pngalpha)
> lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts \ > -dpixmap-format=pngalpha --png myfile.ly … > -danti-alias-factor=4 > > That removes the transparency and reverts to the white background. No answers up to now. I suppose this means it is just not implemented in a way that the pixmap-format and the anti-alias-factor can work together. I.e. that the downscaling of anti-alias method does not care about transparancy and as it is done after the creation of a transparent png, the transparancy is lost. Could that be added as a bug (or a wish for an enhancement)? Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming and grace notes
Knute Snortum gmail.com> writes:
> I want to start a run of grace notes with a note with a normal head.
> ...but with the c' beamed to the d'.
If these notes all happen before the beat, then
\relative c' {
\grace { <\tweak #'font-size #0 c>32 d e f g a b } c8 }
This looks like it might be a situation where the first note is on the beat.
In these cases, even though we call them 'grace-notes' LilyPonds \grace
is not what I want to use. I just make the notes small and grace-style
and tell LilyPond their actual (as opposed to printed) duration so she
understands how I want them to fit in the music.
\relative c' {
c16[
\teeny
\override Stem #'no-stem-extend = ##t
\override Stem #'length-fraction = #0.7
d32*1/3 e f g a b]
\normalsize
\revert Stem #'no-stem-extend
\revert Stem #'length-fraction
c8
r4 r2 }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming and grace notes
2014-11-27 23:08 GMT+01:00 Keith OHara :
> Knute Snortum gmail.com> writes:
>
>> I want to start a run of grace notes with a note with a normal head.
>
>> ...but with the c' beamed to the d'.
>
> If these notes all happen before the beat, then
> \relative c' {
>\grace { <\tweak #'font-size #0 c>32 d e f g a b } c8 }
>
>
> This looks like it might be a situation where the first note is on the beat.
> In these cases, even though we call them 'grace-notes' LilyPonds \grace
> is not what I want to use. I just make the notes small and grace-style
> and tell LilyPond their actual (as opposed to printed) duration so she
> understands how I want them to fit in the music.
>
> \relative c' {
> c16[
> \teeny
> \override Stem #'no-stem-extend = ##t
> \override Stem #'length-fraction = #0.7
> d32*1/3 e f g a b]
> \normalsize
> \revert Stem #'no-stem-extend
> \revert Stem #'length-fraction
> c8
> r4 r2 }
Maybe
http://lsr.di.unimi.it/LSR/Item?id=193
is of some help as well.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Possible Bug with \partcombine?
Joshua Nichols gmail.com> writes: > Is there talk about improving this feature? Yes. Someone recently gave \partcombine an option to double-stem unisons http://code.google.com/p/lilypond/issues/detail?id=4112 The example at the top of this follow-up might make more sense http://code.google.com/p/lilypond/issues/detail?id=4198 In the next experimental version (available on Windows and macOS after the one person currently practiced at cross-compiling is back from a trip) you can tell LilyPond just once to double-stem unisons, and then any notes slurred to those unisons are also kept in separate Voices so the slurs have a place to go. The basic mechanism of \partcombine, distributing your music into Voices and letting the rest of LilyPond work on those, will almost certainly stay. That is awkward sometimes, because we are thinking of two voices in the input whether set as chords or double-stemmed. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Happy Thanksgiving!!!
Happy Thanksgiving to all Lilyponders! I am grateful that such a community as this exists, in which there is so much good will and friendliness, while still holding everyone to a high standard. And that this community works toward the constant attainment and improvement of, as the blog title says, "scores of beauty." God bless you all, and be well! ~Conor Cook > On Nov 27, 2014, at 1:38 AM, Abraham Lee wrote: > > I realize that Thanksgiving is an American holiday, but I thought I'd just > say, "Thank you!" to everyone that is or has been involved in the > development, usage, support, etc. of LilyPond. There are so many talented > individuals on this and other related mailing lists that provide help and > insight into a marvelous piece of software, making it, and the people they > help, better. > > I look forward to my continued interactions with all of you and I hope that > all the upcoming holidays are filled with joy and peace. > > If there is anything I can do for any of you, please let me know! > > Regards, > Abraham > > Sent from my iPhone > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
