Piano pedal mark collision (\sustainOn, \sustainOff)
Hi! I have a problem with \sustainOn and \sustainOff colliding each other in some cases. I use following pattern s32*31\sustainOn s32\sustainOff instead of s1\sustainOff\sustainOn to achieve a bit better pedalling in MIDI, but it often looks bad on the paper. Is there any way to improve it globally? Is there any way to fine tune horizontal position of the pedal indication? Or maybe there is even a way to use some Scheme magic that would allow writing simpler form (s1\sustainOff\sustainOn), yet modifying it for MIDI (changing off placement by given duration, 32 in the example)? Exemplary source file and PDF: http://paste.przemoc.net/lilypond/piano-pedal-mark-collision/ Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano pedal mark collision (\sustainOn, \sustainOff)
Hi! No one played with positions of \sustainOn and \sustainOff? On Sat, Jan 23, 2016 at 1:33 PM, Przemyslaw Pawelczyk wrote: > I have a problem with \sustainOn and \sustainOff colliding each other > in some cases. > I use following pattern > > s32*31\sustainOn s32\sustainOff [...] > but it often looks bad on the paper. You can see the problem below: http://paste.przemoc.net/lilypond/piano-pedal-mark-collision/piano-pedal-mark-collision.pdf http://paste.przemoc.net/lilypond/piano-pedal-mark-collision/piano-pedal-mark-collision.ly BTW Isn't it a bug that those collisions happen at all? > > Is there any way to improve it globally? > Is there any way to fine tune horizontal position of the pedal indication? I came up with: \override SustainPedal.X-offset = -1 which improves the situation globally, but doesn't avoid collisions in case of denser pedaling like: s32*15\sustainOn s32\sustainOff s32*15\sustainOn s32\sustainOff I can mitigate such issues by correcting X-offset manually then, e.g.: \once \override SustainPedal.X-offset = -2 (finding value looking appropriately in the context is trial and error process, though) If there is any smarter way, then I will replace it instantly. Example of above workarounds: http://paste.przemoc.net/lilypond/piano-pedal-mark-collision/piano-pedal-mark-collision-workaround.pdf http://paste.przemoc.net/lilypond/piano-pedal-mark-collision/piano-pedal-mark-collision-workaround.ly > > Or maybe there is even a way to use some Scheme magic that would allow > writing simpler form (s1\sustainOff\sustainOn), yet modifying it for > MIDI (changing off placement by given duration, 32 in the example)? This would be super handy. Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano pedal mark collision (\sustainOn, \sustainOff)
Hi, Mark! On Wed, Jan 27, 2016 at 9:45 PM, Mark Stephen Mrotek wrote: > If acceptable, the use of "bracket" style can eliminate the conflict. Going in my pedal definition with: \set pedalSustainStyle = #'bracket is other kind of workaround, but text style is much more visually appealing to me. There is also mixed style, which visual "goodness" is inbetween to me, but then Ped. is too close to or even collides with closing bracket, so if it isn't fine out-of-the-box (in my case), then I can as well play with SustainPedal.X-offset globally and in some cases locally (as I've shown in my previous mail) and have IMHO better effect in the end. Anyway, thanks for your suggestion. Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano pedal mark collision (\sustainOn, \sustainOff)
Hi, Kieren! On Wed, Jan 27, 2016 at 10:25 PM, Kieren MacMillan wrote: >> No one played with positions of \sustainOn and \sustainOff? > > Well, I took a couple of seconds, and failed. > > Then, just now, I realized there’s a possible solution: > <http://lists.gnu.org/archive/html/lilypond-user/2008-09/msg00480.html> > > I don’t know if markup (or even “fake markup”) support in pedalSustainStrings > has been added officially… but it certainly could be, if you (or someone > else) sends the appropriate patch. > > Hope this helps! I'm sorry, but I don't understand what you actually suggest as a workaround. Do you perhaps indirectly suggest something like replacing closing asterisk "*" with asterisk with some space padding "* "? That could work too, I guess, if it's possible. Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Piano centered dynamics - dealing with bar collisions
Hi! There is a piano centered dynamics template that was present in Lilypond Learning Manual for v2.14, but is not available in recent versions: http://www.lilypond.org/doc/v2.14/Documentation/learning/piano-templates If we take it (w/o midi part, which is not needed here) and add s1 in everything (i.e. upper, lower, dynamics, pedal) at the beginning, then we can see that \fff overlaps the piano staff bar: http://paste.przemoc.net/lilypond/piano-centered-dynamics/ How to make dynamic text not overlap the bar, yet shift the note column (not sure if I'm using the correct term here) appropriately, so the text would remain centered? (This mostly works when \dynamics are put into particular Staff [only mostly, because \fff remains then too close to the bar, almost touching it], but I want to have one \dynamics in separate Dynamics between upper and lower Staff within PianoStaff.) My half-workaround is setting DynamicText.X-offset (which in this particular example seems ok with value -0.3, but it doesn't work that well in general), but then DynamicText stops being centered and depending on width of the dynamic text, it may be almost unnoticeable or looks awfully wrong. I hope there are some better solutions. Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano centered dynamics - dealing with bar collisions
Hi, Abraham! On Fri, Jan 29, 2016 at 6:49 PM, Abraham Lee wrote: > On Thu, Jan 28, 2016 at 6:02 PM, Przemyslaw Pawelczyk [via Lilypond] < > ml-node+s1069038n186599...@n5.nabble.com> wrote: >> There is a piano centered dynamics template that was present in >> Lilypond Learning Manual for v2.14, but is not available in recent >> versions: >> http://www.lilypond.org/doc/v2.14/Documentation/learning/piano-templates >> >> If we take it (w/o midi part, which is not needed here) and add s1 in >> everything (i.e. upper, lower, dynamics, pedal) at the beginning, then >> we can see that \fff overlaps the piano staff bar: >> http://paste.przemoc.net/lilypond/piano-centered-dynamics/ >> >> How to make dynamic text not overlap the bar, yet shift the note >> column (not sure if I'm using the correct term here) appropriately, so >> the text would remain centered? >> >> (This mostly works when \dynamics are put into particular Staff [only >> mostly, because \fff remains then too close to the bar, almost >> touching it], but I want to have one \dynamics in separate Dynamics >> between upper and lower Staff within PianoStaff.) >> >> My half-workaround is setting DynamicText.X-offset (which in this >> particular example seems ok with value -0.3, but it doesn't work that >> well in general), but then DynamicText stops being centered and >> depending on width of the dynamic text, it may be almost unnoticeable >> or looks awfully wrong. >> >> I hope there are some better solutions. >> > > I, too, have been trying to figure this one out and it appears that we now > have a solution (though it appears to not be documented in the IR, for some > reason--CC-ing the bug-list). It turns out that all you need to add the > following to the appropriate context (Dynamics, in your case): > > \override DynamicText.extra-spacing-height = #'(-inf.0 . +inf.0) Yeah, it works now like when \dynamics are put in Staff. Great! This is the magic sauce to "glue" dynamic text in Dynamics with the notes in Staff. > > That should get you on your way! I've always been puzzled that > extra-spacing-width doesn't change this at all (maybe I just don't know how > to use it properly). The LyricText grob does this SpanBar collision > avoidance by default, so I was confused as to why DynamicText couldn't do > the same. >From my tests it looks that changing DynamicText.extra-spacing-width normally works only when dynamics are put on Staff, not if they are on their separate Dynamics. But thanks to "glueing" (i.e. using above mentioned infinite extra-spacing-height trick), extra-spacing-width works too! So now I can also fix dynamic text touching the bar: \override DynamicText.extra-spacing-width = #'(-0.2 . 0.2) Here is the PDF with both overrides: http://paste.przemoc.net/lilypond/piano-centered-dynamics/piano-centered-dynamics-workaround.pdf > > BTW, this does NOT work with 2.18.2, but it does with 2.19.35 at least. > Haven't checked the other devel versions. I usually try to use the latest Lilypond available, but good to know that such "glueing" is moderately recent feature. > > Anyway. There you go. Thank you very much! Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Piano centered dynamics - dealing with bar collisions
On Fri, Jan 29, 2016 at 11:31 PM, Przemyslaw Pawelczyk
wrote:
> On Fri, Jan 29, 2016 at 6:49 PM, Abraham Lee
> wrote:
>> \override DynamicText.extra-spacing-height = #'(-inf.0 . +inf.0)
> \override DynamicText.extra-spacing-width = #'(-0.2 . 0.2)
>
> Here is the PDF with both overrides:
> http://paste.przemoc.net/lilypond/piano-centered-dynamics/piano-centered-dynamics-workaround.pdf
Here is the PDF w/o overrides:
http://paste.przemoc.net/lilypond/piano-centered-dynamics/piano-centered-dynamics.pdf
I've noticed another thing just now, after zooming in.
Regardless of the overrides, first half note in the lower staff
actually does not line up with quater note in the upper staff.
Adding \override SpacingSpanner.uniform-stretching = ##t into \layout
{ \context { ... } } does not change anything.
I'm not sure, though, whether this slight displacement can be
considered as a bug or whether it's within acceptable boundaries.
>>
>> BTW, this does NOT work with 2.18.2, but it does with 2.19.35 at least.
>> Haven't checked the other devel versions.
>
> I usually try to use the latest Lilypond available, but good to know
> that such "glueing" is moderately recent feature.
I've checked mentioned earlier overrides with 2.18.2 (on Windows 7 Pro
64-bit), and they actually can work here too, but only if they're used
together! :)
Regards.
--
Przemyslaw Pawelczyk
Cross-site thinker, rookie composer, Linux apprentice
https://soundcloud.com/przemoc86
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hymn Repository
Hi. On Mon, Oct 14, 2013 at 1:22 PM, Emil Salim wrote: > Is there a database of .ly files for hymnals somewhere? I'm looking for "For > All the Saints" (Sine Nomine). Thank you for your help. English Hymnal entry in Wikipedia links to: - eHymnal: A project to digitize the English Hymnal in Lilypond format http://ehymnal.wikispaces.com/ - Index of The English Hymnal, 1906, 1933 http://www.oremus.org/hymnal/eh.html You can find that "For all the saints who from their labors rest" is 641th, but it's not yet done in eHymnal project. There is also: Distributed Proofreaders English Hymnal - Wiki Music Experiment http://www.pgdp.net/wiki/The_English_Hymnal_-_Wiki_Music_Experiment where the work is somehow controlled, so there are more sheets, not only using LilyPond, but LilyPond is meant to be used for final product. But no 641th hymn there either, unfortunately. I know that these links aren't much of help, but maybe they'll be helpful for someone anyway. Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hymn Repository
Side note: The English hymnal (January 1, 1906) is archived and is available at: http://archive.org/details/theenglishhymnal00milfuoft in PDF, djvu and text, but 641th hymn is not present there, as it lacks pages: 826-829. Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hymn Repository
Just in case, but Emil, have you visited following Wikipedia entry? https://en.wikipedia.org/wiki/For_All_the_Saints I'm almost sure you did, but if you haven't seen it, then there is a link to: http://www.hymntime.com/tch/htm/f/a/l/fallthes.htm where you can find following files: MIDI: http://www.hymntime.com/tch/mid/s/i/n/sine_nomine.mid NWC: http://www.hymntime.com/tch/nwc/s/i/n/e/Sine%20Nomine.nwc PDF: http://www.hymntime.com/tch/pdf/s/i/n/e/Sine%20Nomine.pdf You have 3 options: 1) converting .midi to .ly - I haven't used midi2ly on this file myself, so I don't know how good the outcome is, 2) converting .nwc to .ly - there is nwc2ly tool [1], but I have never used it, so cannot tell how good it is, 3) writing .ly down yourself according to .pdf - it's short, so unless you're interested in combining the lyrics there, then it won't take more than several minutes, I guess. [1] http://nwc2ly.sourceforge.net/ Regards. -- Przemyslaw Pawelczyk Cross-site thinker, rookie composer, Linux apprentice https://soundcloud.com/przemoc86 ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
