Re: An invitation to a LilyPond powered concert
Am 2013-11-26 um 23:57 schrieb Marcos Press tdy.p...@gmail.com: I'm completly with you! The thing is Trade Treaties means there are ownership discussion. I do respect Authors but Ownership is a little different. Corporates rats exist everywhere and from any origen. Even here in Argentina (South-East American continent). To get back to music: Corporate snakes in „Canto General“ (https://en.wikipedia.org/wiki/Canto_General) by Pablo Neruda / Mikis Theodorakis. I only know the 1975 version, and that’s still one of my favorite choir pieces, I would be very happy and proud if I were to sing that... And good luck with SCORA! Greetlings, Hraban --- fiëé visuëlle Henning Hraban Ramm http://www.fiee.net http://angerweit.tikon.ch/lieder/ https://www.cacert.org (I'm an assurer) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond and midi
Il 26/nov/2013 07:43 Federico Bruni fedel...@gmail.com ha scritto: Il 26/nov/2013 05:19 Stephanie Mitchell sim.musicsch...@gmail.com ha scritto: Hi all, How do I create midi playback using the mac version of lilypond? I am a blind musician and would like to check my scores using midi before printing. Thanks, Steph Mitchell Piano Studio Phone: 0450354342 Web: www.mitchellpianostudio.com Hi Stephanie Please read this page: http://lilypond.org/doc/v2.16/Documentation/notation/midi-block And come back here in case you have any problem. In case your question is about the application for MIDI playback, I suggest installing Frescobaldi and fluidsynth, as described here: https://github.com/dliessi/ports/blob/master/INSTALL-Frescobaldi.md Hope it helps Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: invert the colors (to print white score on black paper)
Il 25/nov/2013 22:33 ryanmichaelmcclure ryanmichaelmccl...@gmail.com ha
scritto:
Give this a try. I used some snippets in the LSR to apply a giant markup
black background and changed everything to white.
\version 2.17.29
#(define (override-color-for-all-grobs color)
(lambda (context)
(let loop ((x all-grob-descriptions))
(if (not (null? x))
(let ((grob-name (caar x)))
(ly:context-pushpop-property context grob-name 'color color)
(loop (cdr x)))
\relative c'' {
\applyContext #(override-color-for-all-grobs (x11-color 'white))
c4\pp\ d e f
\grace { g16[( a g fis]) } g1\ff\!
% place in bottom layer
-\tweak #'layer #-1
-\markup {
\with-dimensions #'(0 . 0) #'(0 . 0)
% specify color
\with-color #(rgb-color 0 0 0)
% specify size
\filled-box #'(-1000 . 1000) #'(-1000 . 4000) #0
}
}
Thanks, it works fine. Even if I can't make it work in my file, which has
two voices stored in two variables.
Anyway, I needed it to print a score on a t-shirt, but my friends
eventually decided printing black on white.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Discussion: automatic engraving and single-source publishing
Hi, 2013/11/27 Noeck noeck.marb...@gmx.de: Hi Just a quick but honest thank you from my side to all of you for improving the out-of-the-box quality, tweaking-possibilities (e.g. \shape) and simplifications for users (e.g. the.dot.syntax instead of #')! You're welcome! And i join the acknowledgements for the stuff that was contributed by others :-) I think, the blog posts show that there is still room for improvements to the automatic typesetting (I am thinking about vertical and horizontal spacing, the latter especially for triplets and many other points Janek mentioned). I would be interested, if you could classify the tweaks needed for the Fried songs? Something like: note-spacing, default slurs, broken slurs, very special slurs, lyrics shifts, … How many did you need for every kind? And how many could (in principle) be solved by a more clever automatic behaviour (just a rough guess)? There are two posts with statistics in the pipelines :-) In general, i think that at least in half of the cases that needed tweaking it should be possible to improve automatic formatting so that LilyPond would solve these problems herself (but it may not be easy). best, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problems with LilyJAZZ.ily
2013/11/26 Federico Bruni fedel...@gmail.com: 2013/11/25 Janek Warchoł janek.lilyp...@gmail.com If you'd like to help with getting bend stuff and LilyJAZZ into openlilylib/snippets that would be absolutely awesome! We accept pull requests on github, or you could send us patches. If you don't feel comfortable with such workflows, It would be enough if you just told us what exactly to put there. In other words, we need: - the latest version of the stuff to put into the repostory - up-to-date description, including known issues, TODOs, nonstandard dependencies etc. In other words, the description should contain all important informations about the package (so that one doesn't have to sift through mailing list archives or tracker issue comments). I have an account on github and I'm ok with that workflow. In the weekend I'll send a pull request for bend.ly, including a commit for each version of bend.ly (from original 2.14 by Marc to 2.16 adapted by Harm). *excellent!* I'm looking forward to this :-) ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Workarounds for issue 1127?
My problem is the one documented at
http://code.google.com/p/lilypond/issues/detail?id=1127. Looking over that
issue, I see that multiple people have offered monies on multiple occasions (as
recently as a month ago, in fact) for it to be resolved, but that no one has
taken it up yet. What's the best workaround in the meantime?
Here's a tiny example:
\version 2.17.29
\new PianoStaff
\new Staff \relative c'' { a4 c c d }
\new Dynamics { s2\fff s\pp }
\new Staff \relative c'' { \clef bass a2 c,, }
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Workarounds for issue 1127?
Daniel Rosen drosen27 at gmail.com writes:
My problem is the one documented at http://code.google.com/p/lilypond/
issues/detail?id=1127.
Looking over that issue, I see that multiple people have offered monies on
multiple occasions (as
recently as a month ago, in fact) for it to be resolved, but that no one
has taken it up yet. What's the best
workaround in the meantime?
Often each staff has different dynamics in piano music.
I leave out the Dynamics context, indicating dynamics on notes or
spacer rests in a temporary parallel sequence
{ c1\p d2 {s4.\ s8\ \!} e2 }
To space the dynamics form the staff,
\override PianoStaff.DynamicLineSpanner #'staff-padding = #2.5
and in the lower staff
\dynamicUp
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Workarounds for issue 1127?
Hi Keith,
Often each staff has different dynamics in piano music.
I leave out the Dynamics context, indicating dynamics on notes or
spacer rests in a temporary parallel sequence
{ c1\p d2 {s4.\ s8\ \!} e2 }
To space the dynamics form the staff,
\override PianoStaff.DynamicLineSpanner #'staff-padding = #2.5
and in the lower staff
\dynamicUp
I used to do this (many versions ago), but found that the dynamics never
centered exactly (i.e., didn’t line up when they were supposed to”), and the
extra space never compressed effectively (as per, for example,
http://lilypond.googlecode.com/issues/attachment?aid=11270008000name=1127.pngtoken=7jjWNibfdyccg8_IvIQbJ63ZJ-w%3A1385569691324inline=1).
Has this changed in recent versions?
i.e., are you now 100% satisfied with the output you’re getting with regard to
spacing/centering?
Thanks,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RehearsalMark and MetronomeMark together… again…
Hello all,
Given the snippet below, what do I need to do to have RehearsalMark and
MetronomeMark grobs sit on the same plane (“as expected)?
I’ve asked this question several times before, and believe that I’ve
incorporated the most recent “best practices”… but clearly not.
In the Do The Right Thing™ Department, I would think Lilypond should
automatically slide the [first] MetronomeMark slightly to the right, allowing
it to sit on the same baseline as the RehearsalMark. In the Perfect World™
Department, I would love to have a setting to “lock” a grob to a musical moment
(so that horizontal sliding is forbidden), and another to indicate that any
colliding grob(s) should slide left or right as necessary to avoid the
collision (the RehearsalMark and MetronomeMark, respectively, in this case).
Thanks for any assistance.
Kieren.
_
\version “2.17.96
\layout {
\context {
\type Engraver_group
\name ScoreMarks
\consists Staff_collecting_engraver
\consists Axis_group_engraver
\override VerticalAxisGroup.staff-affinity = #DOWN
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.padding = #1
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.minimum-distance
= #1
\override VerticalAxisGroup.nonstaff-relatedstaff-spacing.stretchability =
#0.5
\consists Metronome_mark_engraver
\override MetronomeMark.font-size = #2
\override MetronomeMark.font-series = #'normal
\override MetronomeMark.Y-offset = #3
\override MetronomeMark.extra-spacing-width = #'(-0.5 . 0.5)
\override MetronomeMark.outside-staff-padding = #0.8
\override MetronomeMark.break-align-symbols = #'(time-signature
key-signature)
\override MetronomeMark.non-break-align-symbols = #'(paper-column-interface)
\consists Text_spanner_engraver
\override TextSpanner.font-size = #2
\consists Mark_engraver
\override RehearsalMark.outside-staff-priority = #75
\override RehearsalMark.font-size = #2
\override RehearsalMark.break-align-symbols = #'(time-signature
key-signature)
\consists Time_signature_engraver
\override TimeSignature.stencil = #point-stencil
}
\context {
\Score
\remove Metronome_mark_engraver
\remove Mark_engraver
\accepts ScoreMarks
}
}
test_global = {
\mark \default
\tempo \markup This is a really long tempo mark
s1
\mark \default
\tempo 4=60
s1
}
someMusic = {
c''4 d'' e'' f''
g'' 1
}
\score {
\new ScoreMarks \test_global
\new Staff \someMusic
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RehearsalMark and MetronomeMark together… again…
Hello again, To be clear, \markLengthOn does not solve the problem. Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
automatic chord splitting in piano staff
Hi There!
I’m writing a reduction of a big band part. The saxes have to be printed into a
piano staff. For now I have written everything in one music expression. For
instance:
{g e c a,8 q8 f d b, g,4 ef c a, gf, d b, af, f,8 c a, g, e,8 r8 q4.
~ q4 r4}
I would like that every note below c automatically gets in the lower staff, and
the rest in the upper staff.
Any suggestions?
I might a bit of scheme to do that. Any snippet that iterates through chord
notes?
Thanks,
Jean-Alexis
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: automatic chord splitting in piano staff
Jean-Alexis Montignies-2 wrote
Hi There!
I’m writing a reduction of a big band part. The saxes have to be printed
into a piano staff. For now I have written everything in one music
expression. For instance:
{
g e c a,
8 q8
f d b, g,
4
ef c a, gf,
d b, af, f,
8
c a, g, e,
8 r8 q4. ~ q4 r4}
I would like that every note below c automatically gets in the lower
staff, and the rest in the upper staff.
Any suggestions?
I might a bit of scheme to do that. Any snippet that iterates through
chord notes?
one approach could be http://lsr.dsi.unimi.it/LSR/Item?id=545
then you could look for snippets where notes are colored according to their
pitch
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/automatic-chord-splitting-in-piano-staff-tp154549p154550.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
Consistency of engraving of hairpin
See below. In bar 1, where the starting point of the hairpin in the top
voice is a rest, the hairpin starts at a point midway between that rest
and the following note. If the hairpin starts on a note, or if the
hairpin is move to another voice consisting of only spacer rests, then
the behaviour is different.
The difference in behaviour is the same if there is only a single voice,
though then it doesn't make sense to start the hairpin on the rest.
\version 2.17.96
\relative c'' {
\time 2/4
{
r16\ a a a a a a a\!
r16 a a a a a a a
a16\ a a a a a a a\!
}
\\
{
a,2
a
a
}
\\
{
s2
s16\ s s s s s s s\!
s2
}
}
attachment: test.png___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Consistency of engraving of hairpin
Nick Payne-3 wrote
See below. In bar 1, where the starting point of the hairpin in the top
voice is a rest, the hairpin starts at a point midway between that rest
and the following note. If the hairpin starts on a note, or if the
hairpin is move to another voice consisting of only spacer rests, then
the behaviour is different.
The difference in behaviour is the same if there is only a single voice,
though then it doesn't make sense to start the hairpin on the rest.
\version 2.17.96
\relative c'' {
\time 2/4
{
r16\ a a a a a a a\!
r16 a a a a a a a
a16\ a a a a a a a\!
}
\\
{
a,2
a
a
}
\\
{
s2
s16\ s s s s s s s\!
s2
}
}
___
lilypond-user mailing list
lilypond-user@
https://lists.gnu.org/mailman/listinfo/lilypond-user
test.png (6K)
lt;http://lilypond.1069038.n5.nabble.com/attachment/154551/0/test.pnggt;
I don't follow what you're saying. What behavior are you expecting w/ the
hairpins? I saw the PNG but I can't figure out what you're after. Sorry.
-
composer | sound designer
LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Consistency-of-engraving-of-hairpin-tp154551p154552.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
Horizontal alignment of MultiMeasureRest markups
Hello List,
why is it not possible to horizontal align markups attached to a
MultiMeasureRest in the positive direction (i.e. left)?
I expected this code to work, but the \halign seems to be ignored (#-5
would work):
\version 2.17.29
\new Staff
{
R1^\markup { \null \halign #5 text }
}
I used the following workaround:
\version 2.17.29
\new Staff
{
R1
}
\new Voice
{
s1^\markup { text }
}
With that I didn’t even need any kind of alignment in my special case, but
all alignments would work with this.
It keeps me wondering, though, why it does not work on a MultiMeasureRest.
Is that intentional?
--
Peter Crighton | Musician Music Engraver based in Mainz/Wiesbaden, Germany
http://www.petercrighton.de
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Horizontal alignment of MultiMeasureRest markups
Hi Peter,
why is it not possible to horizontal align markups attached to a
MultiMeasureRest in the positive direction (i.e. left)?
It is:
\version 2.17.96
\paper { ragged-right = ##f }
\new Staff
{
R1-\tweak #'self-alignment-X #LEFT ^\markup { text }
}
Hope this helps!
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Workarounds for issue 1127?
On Wed, 27 Nov 2013 12:34:12 -0800, Kieren MacMillan
kieren_macmil...@sympatico.ca wrote:
I leave out the Dynamics context, indicating dynamics on notes or
spacer rests in a temporary parallel sequence
{ c1\p d2 {s4.\ s8\ \!} e2 }
\override PianoStaff.DynamicLineSpanner #'staff-padding = #2.5
I used to do this (many versions ago), but found that the dynamics never centered
exactly (i.e., didn’t line up when they were supposed to”), and the extra
space never compressed effectively
Right. This just attaches dynamics to one staff or the other. I just find the
result less-bad than having all dynamics on one horizontal line.
The right- and left- staves within a PianoStaff don't stretch from each other
very much to help fill the page, so setting their 'staff-padding' to each staff
at about half the gap, puts the dynamics nearly in the center, most of the
time, unless notes pry the staves apart.
I guess you can put a Dynamics between the staves anyway, and use it for the
occasional dynamic that really should be centered between staves.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RehearsalMark and MetronomeMark together…again…
Kieren MacMillan kieren_macmillan at sympatico.ca writes: Given the snippet below, what do I need to do to have RehearsalMark and MetronomeMark grobs sit on the same plane (“as expected)? In the Do The Right Thing™ Department, I would think Lilypond should automatically slide the [first] MetronomeMark slightly to the right, allowing it to sit on the same baseline as the RehearsalMark. Xavier asked for the same behavior when he was reviewing the addition of \markLenghtOn. Your input tells LilyPond to align both MetronomeMark and RehearsalMark over the time-signature, if there is one. Specifying this uses the break-alignable-interface, which is rather flexible, but does not have a way to specify which of the marks should move right if they both want to align at the same point. (By default, the RehearsalMark goes just right of the Clef, which happens to leave room for MetronomeMark to fit in-line.) You could use David Nalesnik's \offset #'X-offset ... command to move whichever mark, whenever you have a tempo mark, rehearsal mark, and time-signature all at the same time. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RehearsalMark and MetronomeMark together…again…
Kieren MacMillan kieren_macmillan at sympatico.ca writes:
To be clear, \markLengthOn does not solve the problem.
Just for anybody searching the archives, what \markLengthOn *does* do
is space the music out to give room for the marks. So it helps when
the RehearsalMark and tempo are on different notes, barlines, etc:
\version 2.17.19
{ \markLengthOn
\mark\default
\tempo This is a really long tempo mark
c''4 d'' e'' f''
\mark\default \tempo 4=60
g'' 1 }
A lot of people writing score-and-parts use Shevek's MarkLine context,
in which case it makes sense to include the essential bit of
\markLengthOn in the definition of MarkLine context:
\score {
\new MarkLine {
\mark \default
\tempo \markup This is a really long tempo mark
s1
\mark \default
\tempo 4=60
s1 }
\new Staff {
c''4 d'' e'' f''
g'' 1
}
\layout {
\context {
\name MarkLine
\type Engraver_group
\consists Axis_group_engraver
\consists Output_property_engraver
\consists Mark_engraver
\consists Metronome_mark_engraver
\consists Text_spanner_engraver
\consists Time_signature_engraver
\override TimeSignature #'stencil = #point-stencil
\override MetronomeMark #'Y-offset = #0
\override RehearsalMark #'Y-offset = #0
\override RehearsalMark #'extra-spacing-width = #'(0 . 0.5)
\override MetronomeMark #'extra-spacing-width = #'(0 . 1.5)
\override VerticalAxisGroup #'staff-staff-spacing = #'((padding . 1))
}
\context {
\Score
\remove Metronome_mark_engraver
\remove Mark_engraver
\accepts MarkLine } } }
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Consistency of engraving of hairpin
Nick Payne nick.payne at internode.on.net writes: See below. In bar 1, where the starting point of the hairpin in the top voice is a rest, the hairpin starts at a point midway between that rest and the following note. If the hairpin starts on a note, or if the hairpin is move to another voice consisting of only spacer rests, then the behaviour is different. Apparently hairpins are expected to *end* differently on notes versus rests, and it seems the fix for that issue http://code.google.com/p/lilypond/issues/detail?id=154 also changed where the hairpins begin. Presumably you expect the hairpins to begin on the left edge, whether there is a rest or not. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
