Re: Exact stem length?
Am 25.03.2014 13:25, schrieb Fredrik Wallberg: - How could I remove the gap between the first two stems? Maybe try with a temporary \set Score.proportionalNotationDuration = #(ly:make-moment 1 8) for that particular group of notes? Thanks, this seems to work perfectly. But it has the side effect that parallel music in other voices/staves is also spaced proportionally, which _may_ give undesirable results. However, I wouldn't want to completely move the Timing_translator to be able to make that change local to the voice context. For now this seems to be a working solution, but if someone has an idea how to achieve the effect without the mentioned side-effect it would be great. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Exact stem length?
Am 25.03.2014 13:25, schrieb Fredrik Wallberg: As for the beam lengths, I'm not sure what the best solution would be -- \override Stem.details.beamed-lengths = #'(10 20 3) works fine for controlling the_length_ of beams, of course (which I'm sure you aware of), But unfortunately it doesn't have any effect on my example. It seems the stems are _still_ attached to the invisible noteheads. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Exact stem length?
Am 25.03.2014 13:45, schrieb Fredrik Wallberg: ...a way to override the distance between notehead and stem... \override Stem.Y-offset = 2 (Sorry about the typos in my last message -- I wrote "beam lenghts"; I meant "stem lengths of beamed notes".) This works basically. The attached image is the result of manually offsetting the stem for every second note (i.e. any repeated pitch) by 0.25. Of course that's an inacceptable amount of manual work for a general solution. I think for a function it would be better to - print the initial pitch - print the last note at its pitch (without notehead of course) - repeat the initial pitch for all intermediate events and - calculate the offsets as a linear function. Urs <>___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
On Tue, 2014-03-25 at 09:14 +, Richard Shann wrote: > On Tue, 2014-03-25 at 09:07 +0100, Alexander Kobel wrote: > > On 03/25/2014 01:10 AM, Simon Albrecht wrote: > > > The following is completely off-topic, but I’d like to share some > > > observations I often make and thoughts I have and ask for your > opinion: > > > > Hi Simon, [...] > > > > Ugh. Ugly, but Denemo's fault. > > the Denemo user's fault (me, in this case), it would seem I should > have > written -- instead of - attached ... ignorance (sigh!). I did a search and replace "- " with " -- " and uploaded a new version http://imslp.org/wiki/Special:ImagefromIndex/278632 I left the long melismata as it is in the original print, because I don't know what else to do with it. And I took the opportunity to tweak the beaming and the line break at half-bar. I thought it was worth tweaking, as this is out there as an example of LilyPond typesetting. It is now LilyPond 2.18 Richard ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Help with music-function generating music
Hi all,
I'm completely at a loss and need to get some help and pushes in the
right direction.
I'm for the first time trying to write a music function that actually
gerenates music events on its own, i.e. that doesn't use #{ #} to output
music.
The sections in the "Scheme tutorial" in the Extending Manual don't
really help me, and trying to understand
http://lsr.di.unimi.it/LSR/Snippet?id=566 which seems to be quite
related to what I want is equally over my head.
Therefore I'd be happy if someone could give me a (commented?) example
of at least the first steps of what I try. From there I'd be able to go
forward or ask more concrete questions.
The initial thing my function should do is:
- take a pitch and a number
- repeat that pitch for the given number of times
- beam the whole group
- make that in a loop that allows me
to apply a new override for each note
I think that should be very basic, and it's actually quite far from what
I want to achieve, but it should be a good starting point for
understanding how it works.
Thanks in advance
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
- Original Message - From: "Richard Shann" To: "Alexander Kobel" Cc: "lilypond user list" Sent: Wednesday, March 26, 2014 9:25 AM Subject: Re: Discussing typographical standards On Tue, 2014-03-25 at 09:14 +, Richard Shann wrote: On Tue, 2014-03-25 at 09:07 +0100, Alexander Kobel wrote: > On 03/25/2014 01:10 AM, Simon Albrecht wrote: > > The following is completely off-topic, but I’d like to share some > > observations I often make and thoughts I have and ask for your opinion: > > Hi Simon, [...] > > Ugh. Ugly, but Denemo's fault. the Denemo user's fault (me, in this case), it would seem I should have written -- instead of - attached ... ignorance (sigh!). I did a search and replace "- " with " -- " and uploaded a new version http://imslp.org/wiki/Special:ImagefromIndex/278632 I left the long melismata as it is in the original print, because I don't know what else to do with it. And I took the opportunity to tweak the beaming and the line break at half-bar. I thought it was worth tweaking, as this is out there as an example of LilyPond typesetting. It is now LilyPond 2.18 Richard If you were setting this now, you would use a lyric extender. http://www.lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-vocal-music#extenders-and-hyphens Older typesetting often uses multiple dots (periods) for this: I always replace them with the horizontal line. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
Am 25.03.2014 01:10, schrieb Simon Albrecht:
Am 24.03.2014 13:33, schrieb Richard Shann:
An example of this, typeset using LilyPond is posted here:
http://imslp.org/wiki/Special:ImagefromIndex/278632
To do this I set tuplet timing around the entire bass part and used
doubled time signatures (one hidden IIRC)
Richard
The following is completely off-topic, but I'd like to share some
observations I often make and thoughts I have and ask for your opinion:
Looking at this score confirms me in my opinion that LilyPond default
output alone is no guarantee for a good-looking result in accordance
with typographical good use.
Let me throw in a few comments although many things have already been
discussed.
Of course LilyPond's default output is no guarantee for a perfect
result. Everybody is working towards it but there's still a long way to
go. On the other hand I'd say that no competitor so far reaches a
comparable level as LilyPond when it comes to the default output.
As have been discussed some of the issues you note are "user errors",
but I'd really stress that there are things where you simply can have
different styles/opinions or different solutions depending on the
historical period of your music.
So I think having a program produce perfect results by default isn't
completely achievable.
This may be partly due to an older lilypond
version used, but there are some basic issues I see with this:
-- For what I know of best practice in typography, it is normally
unnecessary to use slurs for indicating melismata. Beaming
It has been discussed but I'd like to repeat that this is a matter of
historical style and personal preference (of
composer/editor/engraver/publisher). Therefore a tool can't produce
"perfect" results by default, the question is rather whether your tool
provides convenient ways to realize what you chose to do. And LilyPond
does this.
-- The beginning of the first recitative is a good example where
inserting a line break at half-measure would significantly improve the
visual impression by a more even horizontal spacing. I found that it was
common in traditional hand-engraved scores to do such mid-measure breaks
(if measures aren't rather short), and thus I am often using \bar "" at
half-measure. Sometimes I even use an extra voice for something like
\repeat unfold 35 { s2 \bar "" s2 } and thus create more flexibility in
line-breaking. The disadvantage is that there is no possibility to
differ in likeliness between mid-measure and full-measure breaks, which
would then be desirable.
This can be argued about. But I think it is good that LilyPond by
default only breaks lines at barlines because when you start breaking
mid-bar it becomes an aesthetically very complex issue.
What I would find useful is an option with that you can allow LilyPond
to break mid-measure at certain points. For example that you say: "In
4/4 time you may also break in the middle", or "In 9/8 time you may
break also at the 4th and 7th quaver".
This would make it possible to have a more flexible breaking (on
request, not by default) without having to write and include a dedicated
extra voice.
-- As always, the default margins are too small. This is already being
discussed as issue 3808
and will
hopefully be changed soon. I once read a comprehensive article
(in German) on
this topic from the German Tex user group's magazine, and the author
pointed out that in medieval manuscripts and renaissance prints an
outstandingly pleasing appearance is achieved by page margins which
cover up half of the page's space! This is luxury, of course, and
usually unaffordable, but I find it evident that having "unusually"
large margins (and simple ratios between the measurements of the page
and margins, and the top-margin smaller than the bottom-margin and so
on...) much improves the look of the page. It might necessitate to
decrease staff size, though, but anyway 16 pt are no way too small.
As has been mentioned there are significant differences between text and
music typesetting. In particular I'd like to add that the "Satzspiegel"
discussion for text documents is very tightly tied to legibility issues
that circle around the number of characters per line and the leading
between them. The relation between these parameters is extremely
important for how the eye moves from one line to the next. Therefore it
is necessary to have large margins if the page is large and the font is
small, as it is with nowadays default arrangement of A4 paper and 11-12
point text fonts. It is more or less impossible to create "good" margins
from the readability POV that don't look ridiculous on A4 paper.
But this is a completely different thing with music.
That said, I also find the default margins too small ;-)
...
>
Using LilyPond unfortunately doesn't in itself guarantee "flawless"
typogra
Strange font in \markup {} with \Dynamics ?
Howdy!
I am fixing up one of my transcriptions for 2 guitars by centering
some dynamics between
the staves.
Seems to work fine except when I want to combine \dynamic with
text.. I can't the font to work correctly
http://www.gooeytar.com/projects/test/berceuse.pdf
see bar 18 - 19
bar 19 is done with
< b\harmonic >4 _\markup { \dynamic p \italic \tiny "sempre." } b
~ |
in guitarone
To centre this between the staves I am trying to use \Dynamic like
this
psempredyn = \markup {
\hspace #12
\dynamic p
\hspace #1
\tiny
\italic
sempre
}
psempre = #(make-dynamic-script psempredyn)
dynamics = {
s4\p s4
\repeat unfold 2 { s4 s4 }
\repeat unfold 6 { s4 s4 }
s4 \> s4 %10
s4\! s4
\repeat unfold 6 { s4 s4 }
s4\psempre s4
}
\score {
\new StaffGroup \with {
\override StaffGrouper #'staff-staff-spacing =
#'((basic-distance . 14)
(minimum-distance . 10)
(padding . 4))
}
<<
\new Staff << \global \guitarone >>
\new Dynamics \dynamics
\new Staff << \global \guitartwo >>
>>
\layout { }
}
\global is simply
global = {
\clef "G_8"
\key e \major
\time 2/4
}
Why do I get that weird font instead of \italic ? Doesn't matter
what I
change to font to, it is always the same.. fontsize works and hspace work
Ideas?
thanx - steve
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
- Original Message -
From: "Urs Liska"
To:
Sent: Wednesday, March 26, 2014 10:11 AM
Subject: Re: Discussing typographical standards
What I would find useful is an option with that you can allow LilyPond to
break mid-measure at certain points. For example that you say: "In 4/4
time you may also break in the middle", or "In 9/8 time you may break also
at the 4th and 7th quaver".
This would make it possible to have a more flexible breaking (on request,
not by default) without having to write and include a dedicated extra
voice.
No need for another voice if you want to do manual mid-bar breaking:
\relative c'' { c2 c | c c | c c | c c | c c | c c | c \break \bar "" c | c
c | c c | }
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: Discussing typographical standards
Am 26.03.2014 11:36, schrieb Phil Holmes:
- Original Message - From: "Urs Liska"
To:
Sent: Wednesday, March 26, 2014 10:11 AM
Subject: Re: Discussing typographical standards
What I would find useful is an option with that you can allow LilyPond
to break mid-measure at certain points. For example that you say: "In
4/4 time you may also break in the middle", or "In 9/8 time you may
break also at the 4th and 7th quaver".
This would make it possible to have a more flexible breaking (on
request, not by default) without having to write and include a
dedicated extra voice.
No need for another voice if you want to do manual mid-bar breaking:
\relative c'' { c2 c | c c | c c | c c | c c | c c | c \break \bar "" c
| c c | c c | }
Of course you can write it directly in the music. But it will be cleaner
to separate it out in an extra voice.
But the main point is to have an _automatic_ solution that allows more -
and more flexible - breaking patterns without having to specify possible
break points manually.
Urs
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange font in \markup {} with \Dynamics ?
- Original Message -
From:
To:
Sent: Tuesday, March 25, 2014 3:59 PM
Subject: Strange font in \markup {} with \Dynamics ?
Howdy!
I am fixing up one of my transcriptions for 2 guitars by centering
some dynamics between
the staves.
Seems to work fine except when I want to combine \dynamic with
text.. I can't the font to work correctly
[snip]
Why do I get that weird font instead of \italic ? Doesn't matter
what I
change to font to, it is always the same.. fontsize works and hspace work
From the NR where make-dynamic-script is introduced:
"In general, make-dynamic-script takes any markup object as its argument.
The dynamic
font only contains the characters f,m,p,r,s and z, so if a dynamic mark that
includes plain
text or punctuation symbols is desired, markup commands that reverts font
family and font
encoding to normal text should be used, for example \normal-text."
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
- Original Message -
From: "Urs Liska"
To:
Sent: Wednesday, March 26, 2014 10:39 AM
Subject: Re: [SPAM] Re: Discussing typographical standards
Am 26.03.2014 11:36, schrieb Phil Holmes:
- Original Message - From: "Urs Liska"
To:
Sent: Wednesday, March 26, 2014 10:11 AM
Subject: Re: Discussing typographical standards
What I would find useful is an option with that you can allow LilyPond
to break mid-measure at certain points. For example that you say: "In
4/4 time you may also break in the middle", or "In 9/8 time you may
break also at the 4th and 7th quaver".
This would make it possible to have a more flexible breaking (on
request, not by default) without having to write and include a
dedicated extra voice.
No need for another voice if you want to do manual mid-bar breaking:
\relative c'' { c2 c | c c | c c | c c | c c | c c | c \break \bar "" c
| c c | c c | }
Of course you can write it directly in the music. But it will be cleaner
to separate it out in an extra voice.
But the main point is to have an _automatic_ solution that allows more -
and more flexible - breaking patterns without having to specify possible
break points manually.
Urs
I was replying to your comment "possible to have a more flexible breaking
(...) without having to write and include a dedicated extra voice" by
showing that you don't need an extra voice. You might put one, but you
don't need one.
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
Am 26.03.2014 11:51, schrieb Phil Holmes:
- Original Message - From: "Urs Liska"
To:
Sent: Wednesday, March 26, 2014 10:39 AM
Subject: Re: [SPAM] Re: Discussing typographical standards
Am 26.03.2014 11:36, schrieb Phil Holmes:
- Original Message - From: "Urs Liska"
To:
Sent: Wednesday, March 26, 2014 10:11 AM
Subject: Re: Discussing typographical standards
What I would find useful is an option with that you can allow LilyPond
to break mid-measure at certain points. For example that you say: "In
4/4 time you may also break in the middle", or "In 9/8 time you may
break also at the 4th and 7th quaver".
This would make it possible to have a more flexible breaking (on
request, not by default) without having to write and include a
dedicated extra voice.
No need for another voice if you want to do manual mid-bar breaking:
\relative c'' { c2 c | c c | c c | c c | c c | c c | c \break \bar "" c
| c c | c c | }
Of course you can write it directly in the music. But it will be
cleaner to separate it out in an extra voice.
But the main point is to have an _automatic_ solution that allows more
- and more flexible - breaking patterns without having to specify
possible break points manually.
Urs
I was replying to your comment "possible to have a more flexible
breaking (...) without having to write and include a dedicated extra
voice" by showing that you don't need an extra voice. You might put
one, but you don't need one.
OK, OK, I wasn't completely clear then initially.
But my point was about explicitly specifying possible break points manually.
Urs
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Exact stem length?
Hi Urs, (sent this last night but I seem to have issues getting my messages to the list...) It should do what you want in terms of generating stems. It's a work in progress and still needs to be able to handle slurs, dynamics, articulations, different stem patterns etc... best wishes, piaras On 26 March 2014 08:38, Urs Liska wrote: > Am 25.03.2014 13:45, schrieb Fredrik Wallberg: > > ...a way to override the distance between notehead and stem... >>> >> >> \override Stem.Y-offset = 2 >> >> (Sorry about the typos in my last message -- I wrote "beam lenghts"; I >> meant "stem lengths of beamed notes".) >> >> > > This works basically. > The attached image is the result of manually offsetting the stem for every > second note (i.e. any repeated pitch) by 0.25. > > Of course that's an inacceptable amount of manual work for a general > solution. I think for a function it would be better to > > - print the initial pitch > - print the last note at its pitch (without notehead of course) > - repeat the initial pitch for all intermediate events and > - calculate the offsets as a linear function. > > Urs > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > > repeat-stems.ly Description: Binary data <>___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: Exact stem length?
Hi Piaras, I'm sorry, this has somehow slipped me. Your message had been posted last night. This is already _very_ close to what I had in mind, thank you very much. I'll definitely have a closer look and study it. There are two things I'd like to add: a) being able to explicitly define the beam shape. This can be manually done by once overriding Beam.positiony, but it should be an optional argument to the function. I would (without already knowing how) add this to the "props" argument either by changing this to a list and check if it has two or more elements or by checking if the pair is a pair of numbers (as used currently) or a pair of pairs (which would represent the current pair plus the pair of Beam.positions). b) Optionally add a slash because that gesture is often used with a slash. No idea yet, but I recall that Gilberto recently worked on that. I will modify your example so it can be included in the openLilyLib snippet repository. We can then go from there to improve and enhance it. BTW: Does anybody have a good name for that notation? Thank you very much again. Urs Am 26.03.2014 12:10, schrieb Piaras Hoban: Hi Urs, (sent this last night but I seem to have issues getting my messages to the list...) It should do what you want in terms of generating stems. It's a work in progress and still needs to be able to handle slurs, dynamics, articulations, different stem patterns etc... best wishes, piaras On 26 March 2014 08:38, Urs Liska wrote: Am 25.03.2014 13:45, schrieb Fredrik Wallberg: ...a way to override the distance between notehead and stem... \override Stem.Y-offset = 2 (Sorry about the typos in my last message -- I wrote "beam lenghts"; I meant "stem lengths of beamed notes".) This works basically. The attached image is the result of manually offsetting the stem for every second note (i.e. any repeated pitch) by 0.25. Of course that's an inacceptable amount of manual work for a general solution. I think for a function it would be better to - print the initial pitch - print the last note at its pitch (without notehead of course) - repeat the initial pitch for all intermediate events and - calculate the offsets as a linear function. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Exact stem length?
Am 26.03.2014 13:21, schrieb David Nalesnik: Hi, On Wed, Mar 26, 2014 at 6:25 AM, Urs Liska wrote: b) Optionally add a slash because that gesture is often used with a slash. No idea yet, but I recall that Gilberto recently worked on that. For slashed grace-note groups, see http://lsr.di.unimi.it/LSR/Snippet?id=721 --David Thanks for this hint. Initial snippet (without slash) is now available at https://github.com/openlilylib/snippets/tree/master/input-shorthands/fuzzy-scale There are lots of things to be done yet, but it's really a start. Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Exact stem length?
Am 26.03.2014 12:25, schrieb Urs Liska: BTW: Does anybody have a good name for that notation? pitchedGlissando pitchedStems fastScale fuzzyScale ??? I think the last one matches the intention quite well. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Exact stem length?
Hi Urs, On Wed, Mar 26, 2014 at 7:27 AM, Urs Liska wrote: > Am 26.03.2014 12:25, schrieb Urs Liska: > > BTW: Does anybody have a good name for that notation? >> >> > pitchedGlissando > pitchedStems > fastScale > fuzzyScale > > ??? > > I think the last one matches the intention quite well. > > Sure, that would work. Or what about "stemmedGlissando"? It seems to me that this is a special case of using stems to impose some sort of articulation (like bow changes) on a glissando, such as you see all over the place in Lutoslawski. Mike S. worked on this a while back, but unfortunately the patch is marked "abandoned". The issue is 1727, where he refers to them as "glissando stems." HTH, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: Exact stem length?
Hi, On Wed, Mar 26, 2014 at 6:25 AM, Urs Liska wrote: > b) > Optionally add a slash because that gesture is often used with a slash. No > idea yet, but I recall that Gilberto recently worked on that. For slashed grace-note groups, see http://lsr.di.unimi.it/LSR/Snippet?id=721 --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Exact stem length?
Am 26.03.2014 13:46, schrieb David Nalesnik: Hi Urs, On Wed, Mar 26, 2014 at 7:27 AM, Urs Liska mailto:u...@openlilylib.org>> wrote: Am 26.03.2014 12 :25, schrieb Urs Liska: BTW: Does anybody have a good name for that notation? pitchedGlissando pitchedStems fastScale fuzzyScale ??? I think the last one matches the intention quite well. Sure, that would work. Or what about "stemmedGlissando"? Also a very good suggestion. It seems to me that this is a special case of using stems to impose some sort of articulation (like bow changes) on a glissando, such as you see all over the place in Lutoslawski. Yes, or playing very fast scales without exact pitches (thus my naming). In the piece I got this from the first instance is commented as "quasi scales (non gliss.)" Mike S. worked on this a while back, but unfortunately the patch is marked "abandoned". The issue is 1727, where he refers to them as "glissando stems." It's a pity, but skimming through the review process doesn't indicate there's a good chance to get anything from there. So the Scheme-function approach taken by Piaras should be a good start. Urs HTH, David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user -- Urs Liska +49(0)179-4642905 u...@beautifulscores.net http://beautifulScores.net ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: Exact stem length?
Am 26.03.2014 14:38, schrieb Piaras Hoban: So a little more work this morning... I copied in David's slashStem code and it seems perfectly compatible which is great (though it would be nice to have to option of putting the slash at the end of the group). Also dynamic markings and spanners are handled now. That looks great! Please also have a look at the snippet's location I linked to. In the modified snippet file I have listed a number of issues that I encountered with your previous version (when using it with different musical contents. Additionally I see one issue with the ledger lines in the second instance of your example Things I'd like to add: 1) Variable horizontal distribution of stems... very useful for indicating jeté bow markings and the like. That would be nice. But once you'd make this variable you should have an idea how to define that. Or are you thinking of rather simple _functions_ (like "start fast and slow down")? 2) Variable vertical distribution of stems... easy to do I think. I have several ideas about this: - accept "music" as an argument and use the pitches as a reference - Allow more than two notes in the "chord" and use them as intermediate reference points - accept a "path" as an argument and use that (no idea how, though) 3) Slurs and articulations It seems so easy to set beam positions outside of the function that I haven't added it (it shouldn't be too difficult) as I tend to prefer functions that don't have long lists of arguments which I can never remember :) Good point. If I should feel the need for that regularyl it would be easy to create a wrapper function with the extra argument. There seems to be a lot of duplication in this kind of function which makes me feel a little like I'm reinventing the wheel... is there a better way to harvest dynamics, articulations, markup and so on from the input music and apply these directly to the generated music? If not perhaps there is a better conceptual approach to take to these kinds of problems? Sorry, I don't have the slightest clue about this :-( Urs best, piaras ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Strange font in \markup {} with \Dynamics ?
Thats it!! thanx - steve > - Original Message - > > > From the NR where make-dynamic-script is introduced: > > "In general, make-dynamic-script takes any markup object as its argument. > The dynamic > font only contains the characters f,m,p,r,s and z, so if a dynamic mark > that > includes plain > text or punctuation symbols is desired, markup commands that reverts font > family and font > encoding to normal text should be used, for example \normal-text." > > -- > Phil Holmes > > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: Exact stem length?
Piaras: looks wonderful, thanks for sharing. >> haven't added it (it shouldn't be too difficult) as I tend to prefer >> functions that don't have long lists of arguments which I can never >> remember :) It is *possible* to have optional arguments with default values: http://lilypond.org/doc/v2.19/Documentation/extending/scheme-function-definitions and http://lilypond.org/doc/v2.19/Documentation/extending/scheme-function-usage Though in this case, a wrapper (like Urs suggested) is probably not a bad idea. My scheme is a bit rusty (actually, it was never that good), but I'm going to take a closer look at it as soon as I have time. / Fredrik ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Help with music-function generating music
Urs Liska wrote > I'm completely at a loss and need to get some help and pushes in the right > direction. I would start here with \displayMusic http://lilypond.org/doc/v2.18/Documentation/extending/displaying-music-expressions HTH, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Help-with-music-function-generating-music-tp160833p160857.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Help with music-function generating music
Am 26.03.2014 16:08, schrieb Paul Morris:
Urs Liska wrote
I'm completely at a loss and need to get some help and pushes in the right
direction.
I would start here with \displayMusic
http://lilypond.org/doc/v2.18/Documentation/extending/displaying-music-expressions
HTH,
not too much, I'm afraid. That's where I actually got stuck already.
Fortunately there has been significant progress in the other thread
("Exact stem length"). But apart from a solution for the problem at hand
I'll of course want to learn to deal with this myself...
Urs
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Help-with-music-function-generating-music-tp160833p160857.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
--
Urs Liska
+49(0)179-4642905
u...@beautifulscores.net
http://beautifulScores.net
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
Am 26.03.2014 11:11, schrieb Urs Liska:
Am 25.03.2014 01:10, schrieb Simon Albrecht:
The following is completely off-topic, but I'd like to share some
observations I often make and thoughts I have and ask for your opinion:
Looking at this score confirms me in my opinion that LilyPond default
output alone is no guarantee for a good-looking result in accordance
with typographical good use.
Let me throw in a few comments although many things have already been
discussed.
Of course LilyPond's default output is no guarantee for a perfect
result. Everybody is working towards it but there's still a long way
to go. On the other hand I'd say that no competitor so far reaches a
comparable level as LilyPond when it comes to the default output.
I never put doubt to that. I’m as fond as anyone of what Lily can do.
As have been discussed some of the issues you note are "user errors",
but I'd really stress that there are things where you simply can have
different styles/opinions or different solutions depending on the
historical period of your music.
So I think having a program produce perfect results by default isn't
completely achievable.
That’s why I rather considered this an impulse for debate.
This may be partly due to an older lilypond
version used, but there are some basic issues I see with this:
-- For what I know of best practice in typography, it is normally
unnecessary to use slurs for indicating melismata. Beaming
It has been discussed but I'd like to repeat that this is a matter of
historical style and personal preference (of
composer/editor/engraver/publisher). Therefore a tool can't produce
"perfect" results by default, the question is rather whether your tool
provides convenient ways to realize what you chose to do. And LilyPond
does this.
-- The beginning of the first recitative is a good example where
inserting a line break at half-measure would significantly improve the
visual impression by a more even horizontal spacing. I found that it was
common in traditional hand-engraved scores to do such mid-measure breaks
(if measures aren't rather short), and thus I am often using \bar "" at
half-measure. Sometimes I even use an extra voice for something like
\repeat unfold 35 { s2 \bar "" s2 } and thus create more flexibility in
line-breaking. The disadvantage is that there is no possibility to
differ in likeliness between mid-measure and full-measure breaks, which
would then be desirable.
This can be argued about. But I think it is good that LilyPond by
default only breaks lines at barlines because when you start breaking
mid-bar it becomes an aesthetically very complex issue.
What I would find useful is an option with that you can allow LilyPond
to break mid-measure at certain points. For example that you say: "In
4/4 time you may also break in the middle", or "In 9/8 time you may
break also at the 4th and 7th quaver".
This would make it possible to have a more flexible breaking (on
request, not by default) without having to write and include a
dedicated extra voice.
This is exactly what I’d like to propose; it is important that the
mid-bar breaks get some demerit against full-bar breaks, though.
-- As always, the default margins are too small. This is already being
discussed as issue 3808
and will
hopefully be changed soon. I once read a comprehensive article
(in German) on
this topic from the German Tex user group's magazine, and the author
pointed out that in medieval manuscripts and renaissance prints an
outstandingly pleasing appearance is achieved by page margins which
cover up half of the page's space! This is luxury, of course, and
usually unaffordable, but I find it evident that having "unusually"
large margins (and simple ratios between the measurements of the page
and margins, and the top-margin smaller than the bottom-margin and so
on...) much improves the look of the page. It might necessitate to
decrease staff size, though, but anyway 16 pt are no way too small.
As has been mentioned there are significant differences between text
and music typesetting. In particular I'd like to add that the
"Satzspiegel" discussion for text documents is very tightly tied to
legibility issues that circle around the number of characters per line
and the leading between them. The relation between these parameters is
extremely important for how the eye moves from one line to the next.
Therefore it is necessary to have large margins if the page is large
and the font is small, as it is with nowadays default arrangement of
A4 paper and 11-12 point text fonts. It is more or less impossible to
create "good" margins from the readability POV that don't look
ridiculous on A4 paper.
But this is a completely different thing with music.
That said, I also find the default margins too small ;-)
I forgot one sentence there, in which I would have made cl
Re: Discussing typographical standards
Am 26.03.2014 16:32, schrieb Simon Albrecht: But in situations where one can afford it: why not allow oneself some luxury there ;-) At least I sometimes do. (bearing also in mind that paper costs are not a real argument nowadays, once you look at it…) I fully agree with you, but OTOH I find A4 paper somewhat too small for providing nice margins (in general). For that you often have to use smaller staff sizes - which isn't a bad thing in itself but has the risk of the score looking somewhat less impressive than possible. I recently made a style sheet mimicking a certain type of Universal Edition scores. They use a paper that is only a little bit larger than A4 (paper is 23.2x30.4cm, margins are 1.8/2.2 cm, top/bottom 1.6/1.7cm. And with that I could simply use LilyPond's default font/staff-size settings, and it looks wonderful. Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Help with music-function generating music
Ok, here are some next steps. Only dealing with specifying pitch so far.
The number of notes and their duration are both still hard-coded...
-Paul
\version "2.18.0"
% use this to see what the end result should look like:
% \displayMusic { c'4 d e f }
% ===>
% Here it is:
{
#(make-music
'SequentialMusic
'elements
(list (make-music
'NoteEvent
'duration
(ly:make-duration 2 0 1)
'pitch
(ly:make-pitch 0 0 0))
(make-music
'NoteEvent
'pitch
(ly:make-pitch -1 1 0)
'duration
(ly:make-duration 2 0 1))
(make-music
'NoteEvent
'pitch
(ly:make-pitch -1 2 0)
'duration
(ly:make-duration 2 0 1))
(make-music
'NoteEvent
'pitch
(ly:make-pitch -1 3 0)
'duration
(ly:make-duration 2 0 1
}
% a function that accepts three arguments that are used to determine pitch:
% octave note and alteration:
makeFourQuarterNotes =
#(define-music-function (parser location oct nt alt)
(number? number? number?)
(make-music
'SequentialMusic
'elements
(list (make-music
'NoteEvent
'duration
(ly:make-duration 2 0 1)
'pitch
(ly:make-pitch oct nt alt))
(make-music
'NoteEvent
'pitch
(ly:make-pitch oct nt alt)
'duration
(ly:make-duration 2 0 1))
(make-music
'NoteEvent
'pitch
(ly:make-pitch oct nt alt)
'duration
(ly:make-duration 2 0 1))
(make-music
'NoteEvent
'pitch
(ly:make-pitch oct nt alt)
'duration
(ly:make-duration 2 0 1)
{
\makeFourQuarterNotes #1 #1 #0
\makeFourQuarterNotes #1 #2 #0
\makeFourQuarterNotes #0 #1 #-1/2
\makeFourQuarterNotes #0 #2 #1/2
}
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Help-with-music-function-generating-music-tp160833p160861.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
Richard, Is the bracing correct? I would have expected something like: flute | | [violin 1 | [ & 2 | | [ soprano| [& bass | Where the [ is a single bracket. [ regards, Shane On Wed, Mar 26, 2014 at 5:25 AM, Richard Shann wrote: > On Tue, 2014-03-25 at 09:14 +, Richard Shann wrote: >> On Tue, 2014-03-25 at 09:07 +0100, Alexander Kobel wrote: >> > On 03/25/2014 01:10 AM, Simon Albrecht wrote: >> > > The following is completely off-topic, but I'd like to share some >> > > observations I often make and thoughts I have and ask for your >> opinion: >> > >> > Hi Simon, > [...] >> > >> > Ugh. Ugly, but Denemo's fault. >> >> the Denemo user's fault (me, in this case), it would seem I should >> have >> written -- instead of - attached ... ignorance (sigh!). > > I did a search and replace "- " with " -- " and uploaded a new version > > http://imslp.org/wiki/Special:ImagefromIndex/278632 > > I left the long melismata as it is in the original print, because I > don't know what else to do with it. And I took the opportunity to tweak > the beaming and the line break at half-bar. I thought it was worth > tweaking, as this is out there as an example of LilyPond typesetting. It > is now LilyPond 2.18 > > Richard > > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussing typographical standards
On Wed, 2014-03-26 at 12:41 -0400, Shane Brandes wrote: > Richard, > > Is the bracing correct? I just took that from the original print. Except that I should really have chosen PianoStaff not GrandStaff to be just like the original print. The GrandStaff gives more for LilyPond to do, avoiding hitting the bar lines drawn between the staffs ... Richard > I would have expected something like: > > flute | > | > [violin 1 | > [ & 2 | > | > [ soprano| > [& bass | > > > Where the [ is a single bracket. > [ > > > regards, > > Shane > > > On Wed, Mar 26, 2014 at 5:25 AM, Richard Shann > wrote: > > On Tue, 2014-03-25 at 09:14 +, Richard Shann wrote: > >> On Tue, 2014-03-25 at 09:07 +0100, Alexander Kobel wrote: > >> > On 03/25/2014 01:10 AM, Simon Albrecht wrote: > >> > > The following is completely off-topic, but I'd like to share some > >> > > observations I often make and thoughts I have and ask for your > >> opinion: > >> > > >> > Hi Simon, > > [...] > >> > > >> > Ugh. Ugly, but Denemo's fault. > >> > >> the Denemo user's fault (me, in this case), it would seem I should > >> have > >> written -- instead of - attached ... ignorance (sigh!). > > > > I did a search and replace "- " with " -- " and uploaded a new version > > > > http://imslp.org/wiki/Special:ImagefromIndex/278632 > > > > I left the long melismata as it is in the original print, because I > > don't know what else to do with it. And I took the opportunity to tweak > > the beaming and the line break at half-bar. I thought it was worth > > tweaking, as this is out there as an example of LilyPond typesetting. It > > is now LilyPond 2.18 > > > > Richard > > > > > > > > ___ > > lilypond-user mailing list > > lilypond-user@gnu.org > > https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: [SPAM] Re: Exact stem length?
Am 26.03.2014 21:38, schrieb Piaras Hoban: Urs and Fredrik, thanks for input on this -much appreciated. I'm going to think about stem-distribution for a few days and see if a good solution comes to mind. Urs you raised the issue of horizontal spacing in the snippet... perhaps just using a very short base duration for the stemmedGlissando will help here? I'll try that. The fundamental issue with it is that the stemmed glissando actually shouldn't be in any way linked to the timing of the main music. As for now, I've re-jigged this a bit to make it work more like \afterGrace, as I think they are sisters. Overall it should be more robust and it appears more in line with how I usually see these things notated in scores nowadays. The image looks absolutely marvelous - much more than what I initially wanted, can be used for a number of different notational uses. If we (that is probably mainly you) get this to a reasonably stable state it is definitely a worthwile enhancement of the LilyPond toolkit! Best and thanks so far Urs all best, piaras On 26 March 2014 14:45, Fredrik Wallberg wrote: Piaras: looks wonderful, thanks for sharing. haven't added it (it shouldn't be too difficult) as I tend to prefer functions that don't have long lists of arguments which I can never remember :) It is *possible* to have optional arguments with default values: http://lilypond.org/doc/v2.19/Documentation/extending/scheme-function-definitions and http://lilypond.org/doc/v2.19/Documentation/extending/scheme-function-usage Though in this case, a wrapper (like Urs suggested) is probably not a bad idea. My scheme is a bit rusty (actually, it was never that good), but I'm going to take a closer look at it as soon as I have time. / Fredrik ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Help with music-function generating music
Urs Liska wrote
> Hi all,
>
> I'm completely at a loss and need to get some help and pushes in the
> right direction.
>
> I'm for the first time trying to write a music function that actually
> gerenates music events on its own, i.e. that doesn't use #{ #} to output
> music.
> The sections in the "Scheme tutorial" in the Extending Manual don't
> really help me, and trying to understand
> http://lsr.di.unimi.it/LSR/Snippet?id=566 which seems to be quite
> related to what I want is equally over my head.
> Therefore I'd be happy if someone could give me a (commented?) example
> of at least the first steps of what I try. From there I'd be able to go
> forward or ask more concrete questions.
>
> The initial thing my function should do is:
> - take a pitch and a number
> - repeat that pitch for the given number of times
> - beam the whole group
> - make that in a loop that allows me
>to apply a new override for each note
>
> I think that should be very basic, and it's actually quite far from what
> I want to achieve, but it should be a good starting point for
> understanding how it works.
>
> Thanks in advance
> Urs
>
> ___
> lilypond-user mailing list
> lilypond-user@
> https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi,
as Paul Morris pointed out \displayMusic is the best starting point to learn
the scheme way of writing music.
For example \displayMusic { c8[ c c c] } will show you how to beam a group.
Also I don't really get your last point. What kind of override do you want
to apply to the notes?
Regards,
Tao
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Help-with-music-function-generating-music-tp160833p160866.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Help with music-function generating music
Hi Urs,
I had a chance to work on the iteration part. This one accepts a note as an
argument which is a better approach, following the examples here:
http://lilypond.org/doc/v2.18/Documentation/extending/doubling-a-note-with-slurs-_0028example_0029
http://lilypond.org/doc/v2.18/Documentation/extending/adding-articulation-to-notes-_0028example_0029
The iteration is done with a "named let" (which is just one option) see
these docs for Guile and Scheme:
https://www.gnu.org/software/mit-scheme/documentation/mit-scheme-ref/Iteration.html
https://www.gnu.org/software/guile/manual/guile.html#while-do
Cheers,
-Paul
\version "2.18.0"
myNotes =
#(define-music-function (parser location note num)
(ly:music? number?)
"Returns a series of notes. @var{note} is repeated @var{num} times.
@var{note} is supposed to be a single note."
;; iteration by named let
(let loop
;; two variables/arguments,
;; i is the iteration count
;; nts is the list of notes we're building
((i 0)
(nts '()))
;; conditional
(cond
((< i num)
;; call the loop again with modified values for i and nts
(loop
(+ i 1)
(append nts (list (ly:music-deep-copy note)
(else
;; when done, return the music
(make-music 'SequentialMusic 'elements nts)
{
\myNotes g'16 #8
}
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Help-with-music-function-generating-music-tp160833p160867.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Printing Title Pages; has it been a thought?
I am curious overall on what might be a useful enhancement:
Has anyone thought about writing a permanent title page feature for
lilypond? You know, something that I could invoke through the paper block?
I perused a very light search for this kind of thing, and I didn't find
anything.
I'm surprised why this hasn't been introduced into Lilypond's code. For
example, it could look something like this in the \paper block:
print-title-page = ##t
... and it could be set to be ##f by default. It would print all the
information inside the \header{} of course... I think this could be really
useful, but I wonder if I am missing something here as to why it hasn't
been done yet.
I am not familiar with scheme, nor a programmer by any means, but I would
be willing to pay for this feature. How hard could it be?
I know that with Sibelius, there is a default title page, perhaps we could
gleam from that as far as sizing, spacing, etc?
I'm wanting to get people's thoughts.
Sincerely,
Josh
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing Title Pages; has it been a thought?
I think that this would be an interesting feature, but the issue with this is
giving a default title page. It would require a user to adjust the title
page to fit the needs of the user. I have created a personal "title page
template," if you will. I'll attach it in the email to see what you think.
Note that my title page has my logo on it, so you'll have to change the .ly
file accordingly.
Ryan McClure
ryanmichaelmccl...@gmail.com
Music Education Major, Shepherd University
Luna Music Engraving
-Original Message-
From: Joshua Nichols
To: Mailinglist lilypond-user
Subject: Printing Title Pages; has it been a thought?
Date: Wednesday, 26 March 2014, 17:31:29
>I am curious overall on what might be a useful enhancement:
>
>Has anyone thought about writing a permanent title page feature for
>lilypond? You know, something that I could invoke through the paper block?
>
>I perused a very light search for this kind of thing, and I didn't find
>anything.
>
>I'm surprised why this hasn't been introduced into Lilypond's code. For
>example, it could look something like this in the \paper block:
>
>print-title-page = ##t
>
>... and it could be set to be ##f by default. It would print all the
>information inside the \header{} of course... I think this could be really
>useful, but I wonder if I am missing something here as to why it hasn't
>been done yet.
>
>I am not familiar with scheme, nor a programmer by any means, but I would
>be willing to pay for this feature. How hard could it be?
>
>I know that with Sibelius, there is a default title page, perhaps we could
>gleam from that as far as sizing, spacing, etc?
>
>I'm wanting to get people's thoughts.
>
>
>Sincerely,
>
>Josh TitlePage.ly
-
Ryan McClure
Music Education Major, Shepherd University
Luna Music Engraving
www.lunamusicengraving.com
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Printing-Title-Pages-has-it-been-a-thought-tp160868p160869.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing Title Pages; has it been a thought?
Here's the EPS file...oopsie - Ryan McClure Music Education Major, Shepherd University Luna Music Engraving www.lunamusicengraving.com -- View this message in context: http://lilypond.1069038.n5.nabble.com/Printing-Title-Pages-has-it-been-a-thought-tp160868p160870.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing Title Pages; has it been a thought?
This is something I would love to see implemented. I was trying to create a file a few days ago with a title page using suggestions in the documentation. It was convoluted and the results less than desirable. I finally scrapped the idea and decided it would be easier to create the page in a separate program and add it to the music file using pdfCreator. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Printing-Title-Pages-has-it-been-a-thought-tp160868p160872.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Printing Title Pages; has it been a thought?
I create a separate title page like this, for example:
\version "2.19.3"
\paper {
first-page-number = 0
print-first-page-number = ##f
}
\header {
title = \markup {
\lower #50 \left-align \center-column {
\fontsize #6 \bold "Gigue"
\lower #1 \fontsize #1 \bold "Suite 6, Dresden manuscript"
\lower #4 \fontsize #-1 "Silvius Leopold Weiss (1687--1750)"
}
}
tagline = ##f
}
\markup \null
\bookpart {
\header {
title = "Gigue"
subtitle = "Suite 6, Dresden manuscript"
composer = "Silvius Leopold Weiss"
}
\score {
% notes here
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
