On Feb 21, 2015, at 9:50 AM, Jacques Menu wrote:
> To be sure I get you right : you’d like the users of your site to able to
> adapt and complement an existing score according to their taste, is that it?
IMSLP supports uploading arrangements.
___
lil
On Jan 29, 2015, at 10:41 AM, Trevor Daniels wrote:
> Certainly the latter. But quite a lot of work has been done. More than a
> few of the examples of overrides in the earlier manuals have had to be
> removed, as LilyPond now does that particular right thing out of the box.
> There is alway
On Jan 29, 2015, at 9:52 AM, Trevor Daniels wrote:
> http://www.lilypond.org/doc/v2.19/Documentation/learning/real-music-example
This example actually nicely illustrates one of the things I've found
frustrating about working with Lilypond: why is it necessary to do so much
deliberate annotation
On Jan 24, 2015, at 10:44 AM, Peter Danemo wrote:
> I need it to be just one. I learned how to make a
> rest invisible, but that doesn't change the position for the remaining rest.
Use 's' instead of 'r' for one of the rests.
___
lilypond-user maili
On Jan 19, 2015, at 9:43 PM, Cynthia Karl wrote:
> You must have an intimate knowledge of LP source code to be able to say that.
> In the Learning Manual, there is a single mention of dotsDown, in a
> discussion of UP and DOWN. In the Notation Manual, there are five mentions,
> one saying sim
On Dec 25, 2014, at 10:50 AM, Kieren MacMillan
wrote:
> \override Arpeggio.stencil = ##f \barsSixToEight \revert Arpeggio.stencil
This will prevent it showing up in the output, but it'll still show up in the
midi, won't it?
___
lilypond-user maili
On Dec 24, 2014, at 12:52 PM, Paul Morris wrote:
> I wonder... Why are there so many different archives of the lilypond mailing
> list? Would there be a way to prevent some of them from showing up in
> google search results? (e.g. by having them indicate "no index" in
> robots.txt)
Attracting s
On Dec 23, 2014, at 5:46 PM, Jim Long wrote:
> Use the Google search tip above to search only the archive you
> want results from.
The beauty of Google Search is that it searches everywhere, not just one place,
so it'll return results from mailing lists, stack exchange, random blogs, etc.
So
On Dec 23, 2014, at 5:41 AM, Phil Holmes wrote:
> According to typesetting rules (see Behind Bars by Elaine Gould, for example)
> rests should remain consistently placed with respect to staff lines. This
> means that when they are moved, they should be moved in 2 pitch increments,
> not one.
On Dec 23, 2014, at 5:45 AM, Phil Holmes wrote:
> Definitive answers are frequently found by learning to use the manuals and
> their indices.
HAH! :)
Believe me, if I hadn't RTFM'd, you'd have had such a barrage of silly
questions from me yesterday you would have plotzed. But the manual is
Thanks to Kieran, David, Trevor and Klaus for all the help on this. If
anyone's curious, a reasonably final version of the score is available here:
https://github.com/Abhayakara/music/blob/master/romanza.pdf?raw=true
And the source is here:
https://github.com/Abhayakara/music/blob/master/roma
On Dec 22, 2014, at 5:30 PM, Ted Lemon wrote:
> I'm trying to typeset a rather complicated manuscript and I've run into two
> brick walls right at the end of the process. The first is that I can't for
> the life of me figure out how lilypond does staff fragments for
I'm trying to typeset a rather complicated manuscript and I've run into two
brick walls right at the end of the process. The first is that I can't for
the life of me figure out how lilypond does staff fragments for manuscript
annotation. If you look at the bottom of the first page of the fol
On Dec 22, 2014, at 4:26 PM, Garrett Fitzgerald wrote:
> It's actually been discussed on meta - consensus is that people should
> actually come over here for help. :-)
Yeah, so, this is intensely frustrating for anybody who tries to google for
help with lilypond, because there are several dozen
On Dec 22, 2014, at 10:04 AM, David Nalesnik wrote:
> I always thought the traditional "Ped." looked a bit like an elephant...
Heh! Yes, I can see that. Or perhaps like a Snuffleupagus, if that reference
makes any sense to you.
> Anyway, yes, Kieren's right. You can replace the drawing with
On Dec 22, 2014, at 9:55 AM, Kieren MacMillan
wrote:
> Unless you tell her otherwise, Lily will move things around to avoid
> collisions, maintain minimum padding values, etc.
>
> Hope this helps!
You have been tremendously helpful--thank you! I'm typesetting this for my
dad, who was really
As one might have seen from my previous question, I'm trying to re-typset a
manuscript that was published in 1919, and it has a way of marking pedals that
I hadn't seen before. You can see an example of this marking here:
http://www.dolmetsch.com/musicalsymbols.htm
search for "The Raindrop".
On Dec 22, 2014, at 9:26 AM, Kieren MacMillan
wrote:
> \new Voice = "bass-a" { \voiceOne \relative c \vba }
> \new Voice = "bass-b" { \voiceTwo \relative c \vbb }
> \new Voice = "bass-c" { \voiceThree \relative c \vbc }
Thanks, that fixed it. The placement of the rests isn't
I'm getting a puzzling error message when I try to typeset the following
lilypond source file. The error is being reported in measure 17 in the first
bass clef voice (\vba). The error that's reported is "romanza.ly:143:47:
warning: cannot resolve rest collision: rest direction not set". Ca
On Nov 24, 2014, at 7:21 AM, Thomas Morley wrote:
> An input like a | ( b) would mean "play legato from the BarCheck"
> Ofcourse nonsense and LilyPond complains.
> Even the error-message:
> syntax error, unexpected EVENT_IDENTIFIER
> is correct, because a BarCheck will not take any musical even
On Nov 24, 2014, at 1:03 AM, Pierre Perol-Schneider
wrote:
> Here both are ok; you simply omit to put any bar check: So a | (b c d) is
> wrong, and a( | b c d) is right.
So to be clear, I am asking whether the behavior we are seeing is intended for
some reason that I haven't understood yet.
On Nov 24, 2014, at 12:35 AM, Pierre Perol-Schneider
wrote:
> The answer is in your question : you're putting slurs at a wrong place and
> phrasing slurs at the right one.
Hm, okay. So a (b c d) is wrong, and a( b c d) is right? I tried putting
the regular slur at the end of the measure in
I've been learning lilypond this weekend, so forgive me if this is a question
with an obvious answer, but I am having trouble getting slurs to work with
\parallelMusic. If the slur marker is on the note at the beginning of the
line, I get a fun error. This:
\parallelMusic #'(va dynD vb) {
23 matches
Mail list logo
