Re: Vertical position of rests on a custom staff
Paul Morris writes: > I am working on adjusting the vertical position of rests on a custom > staff and have run into a problem. I basically want the rests to be > positioned as they are on the standard staff, but in my custom staff > there is no center line so the rests become oriented to the next line > above that (except for whole rests which stay the same). See the > attached files. > > I wrote an override function that moves the rests down to where I want > them. Half rests move down further, and I had to adjust the position > of the dots for dotted rests as well. > > So far so good. The problem I ran into is that when the music > includes \voiceOne and \voiceTwo, the rests appear in the right place > by default, and my adjustment then puts them in the wrong place. You > can see this on the right hand side of the PDF. > > Any thoughts on how to work around this? Make your function do different things depending on the value of (ly:grob-property-data 'direction grob) This will be +1 or -1 for \voiceOne and \voiceTwo (or their equivalents), and something else (0 or a function) when in \oneVoice mode. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Vertical position of rests on a custom staff
Paul Morris writes: > After getting that working I checked to see if anything changed > between v. 2.16 to 2.17.19 And I'm really glad to say that in 2.17.19 > the positioning of the rests was almost exactly what I wanted by > default! The only ones that needed re-positioning were the rarer ones > that were longer than a whole rest. Also the dots on about half of > the rests also still needed re-positioning. Could you elaborate? -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond blog! who wants to join?
Dear LilyPonder, this is awesome! :) Best, Gagi On 2 June 2013 16:17, Janek Warchoł wrote: > 2013/6/2 Nils Gey : > > On Sun, 2 Jun 2013 15:39:43 +0200 > > Janek Warchoł wrote: > >> However, i think that it should be just another category of posts (as > >> i've already said, i'd like this blog to be multi-authored and i'll be > >> happy to give contributor privileges to everyone, even if they write > >> one post per decade). That's simple and i'll make such a category > >> right away. > >> Would you like to write a post immediately? :) > > > > What about giving third party programs, not hosted in the lilypond code, > but which deal directly with Lilypond, a platform? > > For short announcements, not for marketing. > > Let's say the rule is as follows: anything that is a valid and > interesting blog post will be accepted. So you just have to wrap the > information you want to give into a blogpost form. > > For example, imagine that you want to announce Lily 2.17.1 release. > Instead of writing something like: > > We are proud to announce the release of GNU LilyPond 2.17.1. > This release contains the following improvements: >- bug 235234 was fixed, >- feature foobar was added, >- objects use skylines instead of boxes for calculating collisions. > > whis is boring, write something like this: > > After several months of intense development, an important improvement > is implemented in the newly released LilyPond 2.17.1: the program no > longer treats objects as if they were rectangles, but uses skylines to > approximate their shapes. Thanks to this feature, things that used to > look > like this: > > now look like this: > > There are several other improvements in this version - you can see > a full list here . > > I think you can see the difference immediately. > So, everyone's invited - just write in a way that can be interesting > to outsiders as well as long-time users. > > best, > Janek > > ___ > 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: LilyPond blog! who wants to join?
... Let's say the rule is as follows: anything that is a valid and interesting blog post will be accepted. So you just have to wrap the information you want to give into a blogpost form. For example, imagine that you want to announce Lily 2.17.1 release. Instead of writing something like: We are proud to announce the release of GNU LilyPond 2.17.1. This release contains the following improvements: - bug 235234 was fixed, - feature foobar was added, - objects use skylines instead of boxes for calculating collisions. whis is boring, write something like this: After several months of intense development, an important improvement is implemented in the newly released LilyPond 2.17.1: the program no longer treats objects as if they were rectangles, but uses skylines to approximate their shapes. Thanks to this feature, things that used to look like this: now look like this: There are several other improvements in this version - you can see a full list here. FWIW, I'd go for the boring one. PA ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Vertical position of rests on a custom staff
David Kastrup wrote > Make your function do different things depending on the value of > (ly:grob-property-data 'direction grob) > > This will be +1 or -1 for \voiceOne and \voiceTwo (or their > equivalents), and something else (0 or a function) when in \oneVoice > mode. Thank you! This will do the trick. -Paul Morris -- View this message in context: http://lilypond.1069038.n5.nabble.com/Vertical-position-of-rests-on-a-custom-staff-tp146537p146634.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: Vertical position of rests on a custom staff
> > The only ones that needed re-positioning were the rarer ones > > that were longer than a whole rest. Also the dots on about half of > > the rests also still needed re-positioning. > > Could you elaborate? See the attached files. This one makes it clearer than the previous one. The red rests and blue dots are the ones my function has moved. The 3 longest rests are lower on the custom staff than I wanted, so my function moves them up to where they usually are on the standard staff, but then the dots became centered vertically on the longest two rests. So my function moves those dots up where they usually appear. Dots were also centered vertically on quarter, 8th, and 16th rests on the custom staff, so my function moves them up to their usual position. I also show some staves with different line patterns where the Y-offset of the rests is manually set to 0. Sometimes the dots are centered on the rests, and sometimes they are in their usual position (half a staff space higher). This is odd since the dot position apparently depends on the staff line pattern. I suppose that the dots might be centered by default on the rest and then be shifted up to avoid a line through the middle of the rest. (However, on one of the staves they appear in their usual position even though there is no line to avoid.) -Paul Morris shiftRests3.pdf Description: Adobe PDF document shiftRests3.ly Description: Binary data ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Appoggiatura in Anacrusis
Good Day!
A piece begins with an anacrusis - see attached file "without.ly." When the
"g" is notated as an appoggiatura to the "f" - see attached file "with.ly" -
some dreck appears.
http://lsr.dsi.unimi.it/LSR/Item?id=183 states that the grace should appear
after the "\partial." Placing the appoggiatura before or after the
"\partial" produces the same dreck.
Where did I go wrong?
Thank you for your kind attention.
Mark
'
\version "2.16.2"
global = {
\key bes \major
\time 4/4
}
right = \relative c'' {
\global
\partial 4
g'16 f ees d |
}
left = \relative c' {
\global
\partial 4
r4 \clef treble |
}
\score {
\new PianoStaff
<<
\new Staff = "right" \right
\new Staff = "left" { \clef bass \left }
>>
\layout { }
}
\version "2.16.2"
global = {
\key bes \major
\time 4/4
}
right = \relative c'' {
\global
\appoggiatura g'16
\partial 4 f8 ees16 d |
}
left = \relative c' {
\global
r4 \clef treble |
}
\score {
\new PianoStaff
<<
\new Staff = "right" \right
\new Staff = "left" { \clef bass \left }
>>
\layout { }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Appoggiatura in Anacrusis
Le 03/06/2013 17:32, Mark Stephen Mrotek disait : Good Day! A piece begins with an anacrusis – see attached file “without.ly.” When the “g” is notated as an appoggiatura to the “f” – see attached file “with.ly” – some dreck appears. Both hands don't have the same duration since one of them (RH) begins before in order to give a grace note. Just have a \grace s16 in the left hand. Cheers, Jean-Charles ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Page formating for book layout
Howdy! I have a set of variations (BWV 988) that I have transcribed and engraved with lilypond version 2.16.2. It is printed on both sides of the page and reads like a book. I have a \bookpart for each variation. Each variation starts on the left page and has a title and other custom \header stuff. Each variation is either on 2 pages or 4 pages. I want the top system on the right hand page to line up with the top system on the left page when space allows. How to do this? I simply want to set the top-margin somehow only on these pages... is this possible without messing up top-margin on the "title" page? Or what is the correct way to do this? thanx - steve ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Aligning c1 |. with R1 |.
Le 02/06/2013 20:18, Thomas Morley disait :
2013/6/2 Jean-Charles Malahieude :
Only nitpicking, as you can notice, is that it is the right side of the
digits (9, 5 and 6) that get aligned on the center of the note and not the
"full box".
True, though regard the output of the following code:
You'll observe that the aligning in the _not_ affected measure 2 is
the same as in measure 4.
Perhaps a problem with figured Bass. Maybe a bug.
Something strange, for sure:
If you look at the "column" with the 12, it appears that the alignment
is the same (by the right of a one digit figure and some padding for the
double digit in order to "center" the 8 on the 12). Problem or bug? I
wont cut it.
As a comparison with lyrics, just observe
\score {
<<
\new Staff = "staff" \relative c'' \repeat unfold 2 { c4 c c c R1 }
\new Staff <<
\new Voice = "bla" \relative c'' { c1 c1 \break
c1 \centerNoteColumnOn c1 }
\new Lyrics \with { alignAboveContext = "staff" }
\lyricsto "bla"\lyricmode { "|" -- "|" "|" -- "|" }
\new Lyrics \lyricsto "bla"\lyricmode { "|" -- "|" "|" -- "|" }
\new FiguredBass \figuremode {
\set figuredBassAlterationDirection = #RIGHT
%\set figuredBassPlusDirection = #RIGHT
\bassFigureExtendersOn
<[12 _!] 8 [6 4]>1 <[_- 9\+] 5 [6+ 4]>
<[12 _!] 8 [6 4]>1 <[_- 9\+] 5 [6+ 4]> }
\new Lyrics \lyricsto "bla"\lyricmode { "4" -- "6" "6" -- "6" }
>>
>>
\layout {
\override Score.BarNumber #'break-visibility = ##(#f #t #t)
}
}
Chords and frets are OK, figures would probably appreciate the same
treatment as lyrics IMHO.
Cheers,
Jean-Charles
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
completion_heads_engraver within a bar
Relative newbie alert. I'd like to have the action of the completion_heads(rests)_engraver *within* a bar --- so that, for example, rhythms that cross over the start of the 3rd beat in a measure of 4/4 rewrite as two groups of two-beat rhythms with a tie between them. (Also, between bars as before). I had the idea of changing the time signature to 2/4 (in that example), calling the completion_heads_engraver and completion_rests_engraver, and then wrapping that back into a 4/4 time signature. But I'm not sure if that's the happy path to take. (I'd also, for example, like to handle 3/8 time signatures, by rewriting as 3 groups of 1/8 beat-long groups, with ties between them as needed. And etc...) I'm generating "random" rhythms from user input, so this will be a help. I've actually got a perl rewrite program that's mostly working, but then I found the completion_heads_engraver and realized that my needs might already be met by the lilypond system. Any built-in solution or sage advice would be much appreciated. Thanks for your help, and Peace, Jim ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: completion_heads_engraver within a bar
Am 03.06.2013 20:38, schrieb Jim Tisdall: Relative newbie alert. I'd like to have the action of the completion_heads(rests)_engraver *within* a bar --- so that, for example, rhythms that cross over the start of the 3rd beat in a measure of 4/4 rewrite as two groups of two-beat rhythms with a tie between them. (Also, between bars as before). I had the idea of changing the time signature to 2/4 (in that example), calling the completion_heads_engraver and completion_rests_engraver, and then wrapping that back into a 4/4 time signature. But I'm not sure if that's the happy path to take. (I'd also, for example, like to handle 3/8 time signatures, by rewriting as 3 groups of 1/8 beat-long groups, with ties between them as needed. And etc...) I'm generating "random" rhythms from user input, so this will be a help. I've actually got a perl rewrite program that's mostly working, but then I found the completion_heads_engraver and realized that my needs might already be met by the lilypond system. Any built-in solution or sage advice would be much appreciated. ( Thanks for your help, and Peace, Jim I don't really know about that (and don't have the time to investigate), but maybe a workaround could be: - use 2/4 time - display 4/4 time signature instead - hide default barlines - add a dummy voice containing manual barlines every four quarters. HTH 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: Page formating for book layout
2013/6/3
>
> Howdy!
>
> I have a set of variations (BWV 988) that I have transcribed
> and engraved
> with lilypond version 2.16.2. It is printed on both sides of the page and
> reads like a
> book. I have a \bookpart for each variation. Each variation starts on the
> left page
> and has a title and other custom \header stuff. Each variation is either
> on
> 2 pages or 4 pages. I want the top system on the right hand page to line
> up with
> the top system on the left page when space allows. How to do this? I
> simply
> want to set the top-margin somehow only on these pages... is this possible
> without
> messing up top-margin on the "title" page? Or what is the correct way to
> do this?
>
> thanx - steve
>
>
Hi Steve
the answer is top-system-spacing
see this example:
\version "2.16.2"
\paper {
top-system-spacing = #'((padding . 3.5))
}
\markup { \null }
\pageBreak
\bookpart {
\header {
title = "Part 1"
}
\repeat unfold 100 { c1*4 }
}
\bookpart {
\header {
title = "Part 2"
}
\repeat unfold 100 { d1*4 }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond blog! who wants to join?
I like the blog idea. (I also like the "LilyPonderings" name FWIW.) If you have questions about WordPress or need advice or help with it, I have set up and administered a handful of sites with it. (i.e. not on wordpress.com...) I would suggest figuring out the blog's permanent home (URL) sooner than later because people will link to it, and the longer you wait to move it, the more broken links you create, and that does not help when it comes to search engine results. Also running it on your own server gives you control of the software, data, etc. Ideally it could be at www.lilypond.org/blog/ on the lilypond.org domain and to some extent integrated into the main LilyPond website. (i.e. make it easy to navigate back and forth between the two sites seamlessly) -Paul Morris -- View this message in context: http://lilypond.1069038.n5.nabble.com/LilyPond-blog-who-wants-to-join-tp146575p146647.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: completion_heads_engraver within a bar
Jim Tisdall writes:
> Relative newbie alert.
>
> I'd like to have the action of the completion_heads(rests)_engraver
> *within* a bar --- so that, for example, rhythms that cross over the
> start of the 3rd beat in a measure of 4/4 rewrite as two groups of
> two-beat rhythms with a tie between them. (Also, between bars
> as before).
Something like
\new Voice \with { \remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
completionUnit = #(ly:make-moment 1/4)
}
{ c8 c\longa c1 c2 c4 c8 }
is presumably not enough?
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: completion_heads_engraver within a bar
Hi,
2013/6/4 David Kastrup :
> Jim Tisdall writes:
>
>> Relative newbie alert.
>>
>> I'd like to have the action of the completion_heads(rests)_engraver
>> *within* a bar --- so that, for example, rhythms that cross over the
>> start of the 3rd beat in a measure of 4/4 rewrite as two groups of
>> two-beat rhythms with a tie between them. (Also, between bars
>> as before).
>
> Something like
>
> \new Voice \with { \remove "Note_heads_engraver"
>\consists "Completion_heads_engraver"
>completionUnit = #(ly:make-moment 1/4)
>}
> { c8 c\longa c1 c2 c4 c8 }
>
> is presumably not enough?
Wouldn't
\new Voice \with {
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
completionUnit = #(ly:make-moment 1/2)
}
{ c8 c\longa c1 c2 c4 c8 }
be more like what Jim wants?
And btw, this is übercool. I didn't know that LilyPond has a setting for this!
Janek
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
