color in the manual (was: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices))
I'm not overly enthusiastic about adding color to the manual: I'm not
certain how it will look in a printed pdf (many people print the docs)
or in the info files. We obviously need to use color in the doc section
about color, and the red staff-lines in Ancient notation will show up as
black anyway in print, but I'm worried about adding color to the main
manual.
Would it be possible to find noteheads that are more easily
distinguishable? Or perhaps making the example bigger?
...
Actually, I think the best solution is to move the basic explanation
about polyphony out of the manual and into the tutorial. I have no
problem with using bigger staff sizes in the tutorial, and I have less
concerns about using color in there. Also, that's the place for the
basic explanations.
Anybody feel like writing a wordy explanation about polyphony? It could
either replace/add to 2.3.4, or we could add a new subsection after
2.3.5 for this explanation. Feel free to plunder material from 6.3.3.
(if you do, please let me know before you start writing)
I don't mind doing this myself; I'm just asking in case Kieren is
excited about this topic. It would be a nice way to start working on
the docs. :)
Cheers,
- Graham
Mats Bengtsson wrote:
Excellent idea! I will add something like this to the manual, extended
with
yet another example that shows how to manually specify \voiceOne and
so on.
/Mats
Kieren MacMillan wrote:
Hi Mark,
It looks like there is a solution to the problem
Glad it worked!
perhaps people in the past just didn't understand the questions of
the people asking properly . . .
Perhaps... that's why I kept trying to clarify what question you were
really asking, so that I could answer the question you were really
asking! =)
Graham: may I suggest one thing that might help the docs? In 6.3
(especially .4, Explicitly instantiating voices), maybe if the notes
in each Voice context were independently (i.e., differently)
coloured, the examples (and thus the constructs and internal Lilypond
mechanisms) would be even more clear immediately?
For an example, see the attached snippet.
Best regards,
Kieren.
___
\version "2.11.30"
\markup \wordwrap { At first it may be difficult to understand why
the three C notes are not tied in the following example: }
\score
{
\new Staff \relative c''
{
c ~ << { c ~ } \\ { a } >> c }
}
\markup \wordwrap { By colouring the main Voice red, the problem
becomes clear: }
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \\ { a } >> c
}
}
\markup \wordwrap
{
Within the \typewriter {"<< \\\ >>"} polyphony section, two
completely new Voice contexts, independent from the main Voice, have
been constructed automatically by Lilypond. There are several ways to
compensate for this instantiation, but the easiest is simply to avoid
the \typewriter { "\\\ " } construct entirely — within the "<< >>"
construct, any notes before an explicit \typewriter { "\\new Voice" }
command will belong to the main Voice context (i.e., the one
“outside” the polyphony):
}
\score
{
\new Staff \relative c''
{
\override Voice.NoteHead #'color = #red
c ~ << { c ~ } \new Voice { a } >> c
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: color in the manual
Graham Percival wrote: I'm not overly enthusiastic about adding color to the manual: I'm not certain how it will look in a printed pdf (many people print the docs) or in the info files. We obviously need to use color in the doc section about color, and the red staff-lines in Ancient notation will show up as black anyway in print, but I'm worried about adding color to the main manual. As you may already have noticed, I added colors according to Kieren's suggestion in GIT. Based on my experience from writing research articles, colors in the figures is just positive, as long as you make sure that - No colors are too light so the figure is readable also when printed in B/W. - You use also other methods to distinguish between different cases, as we do here with the note head shapess, so no information is lost when you print in B/W. For this specific case, I expect the printed version to be just as readable as the old purely black version, since all the colors are dark enough. For the on-line version it's a clear impovement, in my opinion. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
I'm new to lilypond
Hi,
I've just started trying out Lilypond and I'm amazed at the quality.
I'm still trying to figure out how to put staves together.
Can anyone help with a problem?
I want to generate piano sheet music with treble and bass.
The treble contains both a melody line and an accompaniment,
with lyrics between the staves following the melody line.
melodyline = \relative c' { ... }
accompaniment = \relative c' { ... }
bass = \relative c' { ... }
lyrics = \lyricmode { ... }
How do I put these together? I've tried looking at the templates
but nothing seems to match a fairly standard sheet music format.
I've pottered around without fully understanding what I'm doing.
Eeither the lyrics disappear or a third stave showing the melody
line appears between the piano staves.
Help!
Raichu.
--
Raichu's Web Page http://home.iprimus.com.au/vpolitis/raichu/
Sick of deleting your inbox? Yahoo!7 Mail has free unlimited storage.
http://au.docs.yahoo.com/mail/unlimitedstorage.html
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: I'm new to lilypond
I highly recommend reading the tutorial for 2.11. Even though this is
the unstable branch, the material in the new tutorial will apply to 2.10
(or even 2.8 or 2.6), and the new tutorial explains many things much better.
As for the templates, isn't D.2.2 exactly what you want?
Cheers,
- Graham
Raichu wrote:
Hi,
I've just started trying out Lilypond and I'm amazed at the quality.
I'm still trying to figure out how to put staves together.
Can anyone help with a problem?
I want to generate piano sheet music with treble and bass.
The treble contains both a melody line and an accompaniment,
with lyrics between the staves following the melody line.
melodyline = \relative c' { ... }
accompaniment = \relative c' { ... }
bass = \relative c' { ... }
lyrics = \lyricmode { ... }
How do I put these together? I've tried looking at the templates
but nothing seems to match a fairly standard sheet music format.
I've pottered around without fully understanding what I'm doing.
Eeither the lyrics disappear or a third stave showing the melody
line appears between the piano staves.
Help!
Raichu.
--
Raichu's Web Page http://home.iprimus.com.au/vpolitis/raichu/
Sick of deleting your inbox? Yahoo!7 Mail has free unlimited storage.
http://au.docs.yahoo.com/mail/unlimitedstorage.html
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond Odd Jobs (mostly documentation)
Hi Graham, The one-shot jobs might have a better result/payoff ratio Well, I'm also happy to do that... I'll look at your updated list (separate thread) and go from there. There are three different levels you could pursue: Low: definitely. Medium: likely. High: maybe. you should have fink installed; you might want to look into that if you don't have it already. Had it on my PowerBook G3, but haven't installed it on this new machine (MacBook) yet... Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: color in the manual (was: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices))
Hi Graham, Anybody feel like writing a wordy explanation about polyphony? I think I can handle that. =) Best, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
triplet bracket disappear
Hello, I am using the following commands to get a short 6-measure, 9-staff piece to fit on one page: #(set-default-paper-size "letter" 'landscape) #(set-global-staff-size 13) At this size, I discovered some (not all) of by triplet brackets disappear. Has anyone experienced this? Is there a fix (other than using a larger global staff size)? Thank-you Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: triplet bracket disappear
Brackets that would be too short to print nicely are automatically removed. As far as I can remember, there is no possibility to specify the minimum width of a triplet and force LilyPond to modify the note spacing to get at least this width, but I may be wrong. There are such possibilities on some other objects, like slurs, for example. /Mats Nick Didkovsky wrote: Hello, I am using the following commands to get a short 6-measure, 9-staff piece to fit on one page: #(set-default-paper-size "letter" 'landscape) #(set-global-staff-size 13) At this size, I discovered some (not all) of by triplet brackets disappear. Has anyone experienced this? Is there a fix (other than using a larger global staff size)? Thank-you Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tweaking placement of rehearsal marks
Mats - LilyPond version 2.11.x solved my problem with no further intervention from me. Very nice! Nick Mats Bengtsson wrote: If you upgrade to the latest development version, 2.11.x, there is no need for any tweaking, since these kind of collisions are avoided automatically. If you want to stick to the stable version, read about how to modify the padding of different objects in section "Common Tweaks". Note that RehearsalMark is handled at the score level, just as the MetronomeMark object mentioned in that text. /Mats Nick Didkovsky wrote: Hello I am using \mark in my first measure to give instructions on the feel of the piece. The mark's text overlaps some beams and some notes on the various parts when they are printed individually. How can I tweak to avoid overlapping? The commands I am using are: \once \override Score.RehearsalMark #'self-alignment-X = #left \mark "Smooth, light, precise" Thanks Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book macros/variables
hello Mats,
thanks for your reply. I didn't know about m4 or cpp. Will take a look.
victor.
On 8/29/07, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>
> In any text editor, it's trivial to automatically replace all occurences
> of
> something like
> \lilystart
> by
> \begin[staffsize=12]{lilypond}
> \include "bookstyle.ly "
> or whatever, so I have personally not seen any need for this feature.
> Of course it's very clever to do what you did, namely to include a
> separate .ly file that contains all the necessary settings.
>
> If you have a large number of short snippets, I see that your solution
> might be
> convenient. Did you consider using a standard preprocessor like CPP or M4
> (search the mailing list archives for "preprocessor" for some related
> discussions
> on the use of preprocessors in pure .ly files)?
>
>/Mats
>
> v!ictor [EMAIL PROTECTED] wrote:
> >
> > hello lilyponders,
> >
> > I've been using lilypond-book for the first time. love it!
> >
> > There's one thing that I'd like to have though. I'd love to be able to
> > define macros in a similar way as in latex. Is this possible?
> >
> > From what I've read in the documentation, lilypond-book only knows to
> > look for \begin{lilypond} and \lilypond{ }, so no macros can be
> > defined *for lilypond-book* inside the latex file. If you try to do
> > this, lilypond-book ignores them and then latex tries to interpret
> > them and fails.
> >
> > So i wrote a little parser that looks for a lilypond delimiter,
> > specifically \lily{ [music] } and replaces that for whatever i define
> > in my parser, for example
> >
> > \begin[staffsize=12]{lilypond}
> > \include "bookstyle.ly "
> > [music]
> > \end{lilypond}
> >
> > Now compiling a lilypond-book becomes a three step process:
> > 1. parse book.tex to find \lily{ } and replace with arbitrary lilypond
> > stuff
> > 2. run lilypond-book on book.tex
> > 3. run latex on book.tex
> >
> > So if there is no way of doing this in lilypond-book, would anyone
> > else be interested in integrating something like this in the core
> > lilypond-book code? would it be useful for others?
> >
> > best,
> >
> > victor
> >
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > http://lists.gnu.org/mailman/listinfo/lilypond-user
> >
>
> --
> =
> Mats Bengtsson
> Signal Processing
> Signals, Sensors and Systems
> Royal Institute of Technology
> SE-100 44 STOCKHOLM
> Sweden
> Phone: (+46) 8 790 8463
> Fax: (+46) 8 790 7260
> Email: [EMAIL PROTECTED]
> WWW: http://www.s3.kth.se/~mabe
> =
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to deal with Time Signatures horizontal alignment?
Hi Valentin,
On 8/29/07, Valentin Villenave <[EMAIL PROTECTED]> wrote:
>
>
> OK, so just to sum up the situation: I now have TimeSignatures aligned
> with barlines, which is fine for the topmost TimeSig, but not for the
> "internals" ones between each StaffGroup (since, when occuring at the
> beginning of a system, they collide with the left barline).
>
> It sort of works, so I guess this thread is now closed.
Hopefully it's got a second wind. ;)
Whilst searching for a solution to a rehearsal mark problem, I stumbled upon
this interesting function in output-lib.scm, which might help:
(define-public (shift-right-at-line-begin g)
"Shift an item to the right, but only at the start of the line."
(if (and (ly:item? g)
(equal? (ly:item-break-dir g) RIGHT))
(ly:grob-translate-axis! g 3.5 X)))
It shifts rehearsal marks to the right at the beginning of a system.
You can use this for overriding the after-line-breaking property of
TimeSignature. Obviously, if you'd prefer a different offset, you can copy
this function and rename it.
\context {
\type "Engraver_group"
\consists "Time_signature_engraver"
\consists "Axis_group_engraver"
\name "TimeSig"
\override TimeSignature #'font-size = #3
\override TimeSignature #'break-align-symbol = ##f
\override TimeSignature #'X-offset
= #ly:self-alignment-interface::x-aligned-on-self
\override TimeSignature #'self-alignment-X = #0
\override TimeSignature #'after-line-breaking =
#shift-right-at-line-begin
}
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: triplet bracket disappear
Hello Mats Today I had the same problem appear on a piano part that I extracted with default staff size. I got an 8th note followed by a qtr note, with only the number "3" below them, with no bracket. Boo. This is a real problem, and as I understand there may not be a fix, how should I proceed to ensure that this issue is addressed in future version of LilyPond? Thank-you Nick Mats Bengtsson wrote: Brackets that would be too short to print nicely are automatically removed. As far as I can remember, there is no possibility to specify the minimum width of a triplet and force LilyPond to modify the note spacing to get at least this width, but I may be wrong. There are such possibilities on some other objects, like slurs, for example. /Mats Nick Didkovsky wrote: Hello, I am using the following commands to get a short 6-measure, 9-staff piece to fit on one page: #(set-default-paper-size "letter" 'landscape) #(set-global-staff-size 13) At this size, I discovered some (not all) of by triplet brackets disappear. Has anyone experienced this? Is there a fix (other than using a larger global staff size)? Thank-you Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Mats Bengtsson wrote:
. . .
Mark, what do you say? Is the current example in the manual too complex so
that the main points are not clear enough? Should we replace that example
by Kieren's?
I didn't mean to imply anything about the documentation earlier.
But, since you asked . . .
Perhaps Kieren's example would be helpful instead. I'm not exactly sure. I'm
colorblind, though (slightly), so I don't know how much adding the color would
help me specifically. I think hints like color, size, and shape only help some
people, and only in some circumstances. For me, in this case, I think a
detailed explanation would be better.
It's not 'usually' the complexity of the documentation that causes problems for
me. It's normally just matters of syntax, what relates to what, and what means
what that I need clarification on (i.e. little specific details of how things
are implemented). I like details and specifics a lot (so a detailed
explanation isn't something I consider complicated, though I'm sure that's not
what you meant). A nested explanation might be something I'd consider
complicated.
For instance, the documentation says this:
. . .
<< \upper \\ \lower >>
is equivalent to
<<
\new Voice = "1" { \voiceOne \upper}
\new Voice = "2" { \voiceTwo \lower}
I think the \upper and \lower thing in the documentation is syntactically
confusing, without specifically saying they represent the notes there, seeing
as \upper and \lower are also used in the piano staff context, as people will
actually try to put \upper and \lower in their code (without instantiating
them).
I would recommend either replacing these with notes directly, or showing their instantiation above
the example (and explaining the significance of the voice names "1" and "2";
plus, a mention of when/why it is good to leave them out would be nice—maybe it's already mentioned
somewhere else, and if so, perhaps I might recommend pointing us there from here).
I might recommend adding an example like this somewhere below that:
<<{\voiceOne (upper notes here)} \new Voice {\voiceTwo (lower notes here)}>>
\oneVoice
is the preferred way over
<<{(upper notes here)} \\ {(lower notes here)}>>
for polyphonic chords used with lyrics, since the \\ method automatically gives the names "1" and
"2" to the voices, which are not the names of the voice the lyrics are following (i.e.
"sopranos", etc.)
Where to look for what, in the documentation generally, is also an issue at
times. I might recommend giving us some tips on how to find things (generally
speaking), and how to glean information, as it seems to be easier for you.
All in all, though, I didn't mean to bring up the documentation, myself. It
normally works well for me in connection with the forums—lately, at least. I
understand if you don't want to put this in the documentation (that's fine with
me)—after all, it is on the forums now in a way people who think like me could
find it.
(For the record, there are plenty of answers to similar questions in the
mailing list
archives, that show exactly the same construct. I'm surprised that you
didn't find them.)
I only found such as the links I included in one of the earlier posts of this
thread (but I only made a few different search criteria: i.e. polyphony lyrics,
and . . . I forgot what else). I didn't bother to look further since one of
the threads I saw made it look like a known issue that we just had to deal with
(and that's another reason I didn't look at the manual further; I had no reason
to believe I could find anything more on the subject there, because of what I
saw in the threads).
It's possible that I saw the answers/questions you mentioned, but thought they
were talking about something else, or something irrelevant. I mean, it could
have been a matter of semantics. People are easy to misunderstand (especially
when they talk about familiar things with unfamiliar terminology).
As long as I know what I want, though, the clarity of the documentation isn't a
'huge' deal for me, seeing as I don't view documentation in the same light as a
tutorial (I mean, it seems more for advanced reference than a teaching aid for
new and semi-intermediate users). I'm at a point where things are becoming
more clear and using the documentation for reference isn't that bad
(understanding how voices works helps a lot for this; I think this is probably
one of the most important sections to make clear, and add detail). I mean, the
documentation seems to require a certain amount of knowledge about LilyPond in
order to learn (some sections more than others) as sometimes answers are given
using principles the learner may not have learned yet.
Documentation isn't something I generally expect to read through in a linear
fashion (usually I use it more on a want/need-to-know basis), while a tutorial
or a textbook is. Is one supposed to read the documentation in a linear
fashion? I don't know, personally, but the
Re: How to deal with Time Signatures horizontal alignment?
2007/8/30, Neil Puttock <[EMAIL PROTECTED]>: > Hopefully it's got a second wind. ;) Great! I didn't expect that this problem was manageable... > Whilst searching for a solution to a rehearsal mark problem, I stumbled > upon this interesting function in output-lib.scm, which might help: > > It shifts rehearsal marks to the right at the beginning of a system. Awesome! You're my savior :) > You can use this for overriding the after-line-breaking property of > TimeSignature. Obviously, if you'd prefer a different offset, you can copy > this function and rename it. Nah, it's already perfect! Not only will I use it (in all my scores, starting right now) but I'll add it to the LSR as well. Thank you so much Neil; you've made at least one person happy today :) Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: triplet bracket disappear
Hi all, I know two solutions to this problem. Tuplet brackets disappear when the spacing gets tight, and seems to be a Lilypond "feature" rather than a bug. The first solution is to manually increase the spacing between notes in a tuplet: \once \override Score.SeparationItem #'padding = #0.7 or something like that - you may need to increase the 0.7. The second is an ugly hack, which prints the bracket under all circumstances but doesn't look particularly good: \once \override Score.TupletNumber #'X-extent = #'(0 . 0) Because Lilypond uses the ratio between the TupletNumber X-extent and the TupletBracket X-extent to decide whether to print the TupletBracket, by setting the TupletNumber X-extent to ) you always get a bracket, but the bracket runs into the number. (I'm sure you gave that to me at some point, Mats.) I would agree that this is a problem that should be resolved, at least to give users the option of always having a bracket printed. Hope this helps, Vivian. On Aug 30, 2007, at 7:26 PM, Nick Didkovsky wrote: Hello Mats Today I had the same problem appear on a piano part that I extracted with default staff size. I got an 8th note followed by a qtr note, with only the number "3" below them, with no bracket. Boo. This is a real problem, and as I understand there may not be a fix, how should I proceed to ensure that this issue is addressed in future version of LilyPond? Thank-you Nick Mats Bengtsson wrote: Brackets that would be too short to print nicely are automatically removed. As far as I can remember, there is no possibility to specify the minimum width of a triplet and force LilyPond to modify the note spacing to get at least this width, but I may be wrong. There are such possibilities on some other objects, like slurs, for example. /Mats Nick Didkovsky wrote: Hello, I am using the following commands to get a short 6-measure, 9-staff piece to fit on one page: #(set-default-paper-size "letter" 'landscape) #(set-global-staff-size 13) At this size, I discovered some (not all) of by triplet brackets disappear. Has anyone experienced this? Is there a fix (other than using a larger global staff size)? Thank-you Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to deal with Time Signatures horizontal alignment?
Hi Valentin, On 8/30/07, Valentin Villenave <[EMAIL PROTECTED]> wrote: > > > Nah, it's already perfect! Not only will I use it (in all my scores, > starting right now) but I'll add it to the LSR as well. I'm glad you like it; I've found it quite useful myself, though at first it led me to a dead-end. I thought it could be adapted for overriding RehearsalMark #'text after a line break when break-visibility is set to all-visible, but it only seems to work for more trivial properties like #'color. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alignment problem with RehearsalMark
Hi Mats,
On 8/28/07, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>
>
> Here's an example, which I also send to bug-lilypond.
>
> \relative { \mark "C" c1 | \mark "D" d | \clef alto
> \mark "E" e | \mark "F" f |
> }
>
> % Uncommenting this layout block, causes both the C and the E marks
> % to move to the left!
> %{
> \layout {
> \context { \Score
> \remove "Staff_collecting_engraver"
> \remove "Mark_engraver"
> }
> \context { \Staff
> \consists "Staff_collecting_engraver"
> \consists "Mark_engraver"
> }
> }
> %}
I don't mean to hassle you, but nothing's appeared on bug-lilypond yet. If
you like, I'll post a report myself.
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alignment problem with RehearsalMark
Quoting Neil Puttock <[EMAIL PROTECTED]>: I don't mean to hassle you, but nothing's appeared on bug-lilypond yet. If you like, I'll post a report myself. I don't know where you looked, but it's certainly in the mailing list archives, http://lists.gnu.org/archive/html/bug-lilypond/2007-08/msg00235.html If you are subscribed to both lists, you will only receive one copy of emails that are addressed to both. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alignment problem with RehearsalMark
On 8/30/07, Mats Bengtsson <[EMAIL PROTECTED]> wrote: > > Quoting Neil Puttock <[EMAIL PROTECTED]>: > > > > > I don't mean to hassle you, but nothing's appeared on bug-lilypond yet. > If > > you like, I'll post a report myself. > > I don't know where you looked, but it's certainly in the mailing list > archives, > http://lists.gnu.org/archive/html/bug-lilypond/2007-08/msg00235.html > If you are subscribed to both lists, you will only receive one copy of > emails that are addressed to both. > >/Mats > > > Oops! Sorry about that - I checked bug-lilypond a few days ago but must've missed it. Thanks, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
piano with lyrics (was I'm new to lilypond)
> I highly recommend reading the tutorial for 2.11.
OK thanks I'll have a look at it.
> As for the templates, isn't D.2.2 exactly what you want?
Not quite. I want it to come out like typical pop sheet music,
two staves with lyrics between. The treble stave contains
(polyphonically) both the melody line and an accompaniment.
melodyline = \relative c' { ... }
accompaniment = \relative c' { ... }
bass = \relative c' { ... }
lyrics = \lyricmode { ... }
score {
\new GrandStaff <<
\new Staff = upper {
\clef treble
<< \melodyline \\ \accompaniment >>
}
\new Lyrics \lyricsto ???
\new Staff = lower { \clef bass \lower }
>>
}
How do I get the lyrics to follow melodyline but without a third
music stave repeating melodyline appearing?
Regards,
Raichu.
--
Raichu's Web Page http://home.iprimus.com.au/vpolitis/raichu/
Sick of deleting your inbox? Yahoo!7 Mail has free unlimited storage.
http://au.docs.yahoo.com/mail/unlimitedstorage.html
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: piano with lyrics (was I'm new to lilypond)
2007/8/31, Raichu <[EMAIL PROTECTED]>:
> Not quite. I want it to come out like typical pop sheet music,
> two staves with lyrics between. The treble stave contains
> (polyphonically) both the melody line and an accompaniment.
>
> melodyline = \relative c' { ... }
> accompaniment = \relative c' { ... }
> bass = \relative c' { ... }
> lyrics = \lyricmode { ... }
>
> score {
> \new GrandStaff <<
> \new Staff = upper {
> \clef treble
> << \melodyline \\ \accompaniment >>
> }
> \new Lyrics \lyricsto ???
> \new Staff = lower { \clef bass \lower }
> >>
> }
It would look more like this:
\score {
\new GrandStaff <<
\new Staff = "upper" <<
\new Voice = "melody" \melodyline
\new Voice = "accompaniment" \accompaniment
>>
\new Lyrics \lyricsto melodyline \yourLyrics
\new Staff = "lower" { \clef bass \lower }
>>
}
Notice the two Voice contexts I added inside the upper Staff context;
this way I can give each one a name, and align the lyrics only with
the one I want.
Hope this helps,
Valentin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tip: lyrics with polyphony / stem directions (without specifically instantiated voices)
Mark Dewey wrote: I think the \upper and \lower thing in the documentation is syntactically confusing, without specifically saying they represent the notes there, I would recommend either replacing these with notes directly, or showing their instantiation above the example (and explaining the significance of the voice names "1" and "2"; plus, a mention of when/why it is good to leave them out would be nice—maybe it's already mentioned somewhere else, and if so, perhaps I might recommend pointing us there from here). Let me preface my remarks by stating that the tutorial has been completely rewritten in 2.11; if you haven't seen the 2.11 docs, you'll have missed this. See 2.5.4 Organizing pieces with identifiers. We can't explain all the material in the tutorial throughout the rest of the manual; chapter 3 and onwards (especially chapter 6 and up!) assumes that you are familiar with the material in chapter 2. Where to look for what, in the documentation generally, is also an issue at times. I might recommend giving us some tips on how to find things (generally speaking), and how to glean information, as it seems to be easier for you. 1.6 is a bit out of date, but it's still a good start. I'll update that later tonight. 2.5.6 How to read the manual doesn't discuss where to find things, although such material could be added there. I'm not certain it's worth adding stuff to 2.5.6, though. If people don't notice 1.6, then... All in all, though, I didn't mean to bring up the documentation, myself. It normally works well for me in connection with the forums—lately, at least. I understand if you don't want to put this in the documentation (that's fine with me)—after all, it is on the forums now in a way people who think like me could find it. People don't search the mailist archives. In addition, if everybody has to ask stuff here, we have to explain everything all the time. That's the reason I started working on the docs: I was answering the same questions again and again. I decided that I would never answer a question directly (with anything other than a polite RTFM); instead, I would spend that time improving the docs so that the next person didn't have to ask. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: piano with lyrics (was I'm new to lilypond)
> > Not quite. I want it to come out like typical pop sheet music,
> > two staves with lyrics between. The treble stave contains
> > (polyphonically) both the melody line and an accompaniment.
>
> It would look more like this:
>
> \score {
> \new GrandStaff <<
> \new Staff = "upper" <<
> \new Voice = "melody" \melodyline
> \new Voice = "accompaniment" \accompaniment
> >>
> \new Lyrics \lyricsto melodyline \yourLyrics
> \new Staff = "lower" { \clef bass \lower }
> >>
> }
Thanks that's much better.
However the music looks wrong. The stem direction is as if
each voice had the stave to itself. I am getting repeated
warnings about this:
warning: ignoring too many clashing note columns
I need the melody stems pointing up and the accompaniment
stems pointing down.
--
Raichu's Web Page http://home.iprimus.com.au/vpolitis/raichu/
Sick of deleting your inbox? Yahoo!7 Mail has free unlimited storage.
http://au.docs.yahoo.com/mail/unlimitedstorage.html
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: piano with lyrics (was I'm new to lilypond)
Quoting Raichu <[EMAIL PROTECTED]>:
Thanks that's much better.
However the music looks wrong. The stem direction is as if
each voice had the stave to itself. I am getting repeated
warnings about this:
warning: ignoring too many clashing note columns
I need the melody stems pointing up and the accompaniment
stems pointing down.
Try:
\score {
\new GrandStaff <<
\new Staff = "upper" <<
\new Voice = "melody" {\voiceOne \melodyline }
\new Voice = "accompaniment" { \voiceTwo \accompaniment }
>>
\new Lyrics \lyricsto melodyline \yourLyrics
\new Staff = "lower" { \clef bass \lower }
>>
}
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Autobeaming problem in 12/16
Hi everybody,
I'm trying to set the autobeaming behaviour in 12/16 so that the semiquavers
are beamed as two sets of 6/16 with a subdivision of 3/16 (see picture
below). So far, I've come up with the following code , which doesn't work
properly:
\version "2.11.30"
\paper { ragged-right = ##t }
\relative { \time 12/16
#(override-auto-beam-setting '(end * * 12 16) 6 16 'Score)
c'16 c c c c c c c c c c c %correct autobeaming without subdivision
\set beatLength = #(ly:make-moment 3 16)
\set subdivideBeams = ##t
c16 c c c c c c c c c c c %autobeaming breaks down, subdivision
incorrect for first beat
c16[ c c c c c] c c c c c c %works, but would rather avoid manual beams
}
Is there something I'm missing here?
Thanks,
Neil
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Alignment problem with RehearsalMark
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=432
Cheers,
- Graham
Mats Bengtsson wrote:
Neil Puttock wrote:
Just to clarify this, are you saying that this happens as a result of
the default setting of break-align-symbols combined with moving the
mark engraver to the staff context?
No, I was just speculating, without having really tested my hypothesis.
Sorry about that. Now that I have made some experiments, it seems that
something else is going on when you move the engraver to the staff
context.
Here's an example, which I also send to bug-lilypond.
\relative { \mark "C" c1 | \mark "D" d | \clef alto
\mark "E" e | \mark "F" f |
}
% Uncommenting this layout block, causes both the C and the E marks
% to move to the left!
%{
\layout {
\context { \Score
\remove "Staff_collecting_engraver"
\remove "Mark_engraver"
}
\context { \Staff
\consists "Staff_collecting_engraver"
\consists "Mark_engraver"
}
}
%}
/Mats
___
bug-lilypond mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
LSR: score for diatonic accordion
Is the creator of this snippet on this list? The snippet includes a script for jedit; I'm not certain if that makes sense on LSR. Although many people use jedit, it's by no means universal. Would it be possible to place that script somewhere else (on a website, on the wiki, whatever) and remove it from the snippet? Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: triplet bracket disappear
Thank-you very much Vivian The "ugly hack" has become my default as I cannot chase these cases down individually and stay sane. It's very unpredictable. Best Nick Vivian Barty-Taylor wrote: Hi all, I know two solutions to this problem. Tuplet brackets disappear when the spacing gets tight, and seems to be a Lilypond "feature" rather than a bug. The first solution is to manually increase the spacing between notes in a tuplet: \once \override Score.SeparationItem #'padding = #0.7 or something like that - you may need to increase the 0.7. The second is an ugly hack, which prints the bracket under all circumstances but doesn't look particularly good: \once \override Score.TupletNumber #'X-extent = #'(0 . 0) Because Lilypond uses the ratio between the TupletNumber X-extent and the TupletBracket X-extent to decide whether to print the TupletBracket, by setting the TupletNumber X-extent to ) you always get a bracket, but the bracket runs into the number. (I'm sure you gave that to me at some point, Mats.) I would agree that this is a problem that should be resolved, at least to give users the option of always having a bracket printed. Hope this helps, Vivian. On Aug 30, 2007, at 7:26 PM, Nick Didkovsky wrote: Hello Mats Today I had the same problem appear on a piano part that I extracted with default staff size. I got an 8th note followed by a qtr note, with only the number "3" below them, with no bracket. Boo. This is a real problem, and as I understand there may not be a fix, how should I proceed to ensure that this issue is addressed in future version of LilyPond? Thank-you Nick Mats Bengtsson wrote: Brackets that would be too short to print nicely are automatically removed. As far as I can remember, there is no possibility to specify the minimum width of a triplet and force LilyPond to modify the note spacing to get at least this width, but I may be wrong. There are such possibilities on some other objects, like slurs, for example. /Mats Nick Didkovsky wrote: Hello, I am using the following commands to get a short 6-measure, 9-staff piece to fit on one page: #(set-default-paper-size "letter" 'landscape) #(set-global-staff-size 13) At this size, I discovered some (not all) of by triplet brackets disappear. Has anyone experienced this? Is there a fix (other than using a larger global staff size)? Thank-you Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Suppress Staff.shortInstrumentName printing for parts?
Hello I am using Staff.instrumentName and Staff.shortInstrumentName. Works great for full ensemble scores. As expected the first system shows the long name and subsequent systems show short name. However I then print parts and get undesired effect of having a part with the long name on the top line and the short name on every subsequent line. Of course I don't want the short name to be printed at all when I print a part. Other than editing the staff's .ly file after printing the full ensemble score and removing the short name for part printing, is there a switch I can set in the part printing file to suppress short name printing? Something I can specify before the following block for example, which prints one of my staves, that would suppress short name printing? << \new Staff \opusStaffAA >> Thank-you Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Suppress Staff.shortInstrumentName printing for parts?
See 8.2.8 Different editions from one source. 8.2 is even called "Preparing parts". I highly recommend browsing through the manual. Later on, you'll remember that you saw something in the docs about whatever you want to find. - Graham Nick Didkovsky wrote: Hello I am using Staff.instrumentName and Staff.shortInstrumentName. Works great for full ensemble scores. As expected the first system shows the long name and subsequent systems show short name. However I then print parts and get undesired effect of having a part with the long name on the top line and the short name on every subsequent line. Of course I don't want the short name to be printed at all when I print a part. Other than editing the staff's .ly file after printing the full ensemble score and removing the short name for part printing, is there a switch I can set in the part printing file to suppress short name printing? Something I can specify before the following block for example, which prints one of my staves, that would suppress short name printing? << \new Staff \opusStaffAA >> Thank-you Nick Didkovsky ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
