Polyphony clarification
A couple of questions about polyphony:
1. In this excerpt should I use "\new Voice" twice or can I just use
"\voiceTwo" the second time?
2. Could \voiceOne be assumed?
3. \upper and \lower as mentioned in 6.3.4 in the manual aren't
really commands are they.
Charles
\relative c {
\clef bass
\key a \minor
\time 2/2
| r2 e | r f4( d) | ees f g aes | r1 |
r2. << { \voiceOne b,8^\markup { div.} c \oneVoice }
\new Voice { \voiceTwo b8 c } >> |
<< { \voiceOne c1( e) c ~ c e \oneVoice }
\new Voice { \voiceTwo e,1( b') e, ~ e b' } >> }
--
http://www.campdeadly.com
http://www.campdeadly.com/blog
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Issue 34: Grace synchronization
Of course, most LilyPond users and hackers agree that this is a major issue. The problem is that solving it will require lots of hacking, as far as I can understand. /Mats Peter Mogensen wrote: Hi, Am I the only one who is sad to see Issue 34 at low priority? I guess it's about the bug mentioned at the bottom of: http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Grace-notes I write a lot of scores with drum flams (*) and this bug makes it a lot harder to write and maintain. regards, Peter ___ 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: GDP: NR Specification
Eyolf Østrem wrote:
On 08.11.2007 (15:44), Graham Percival wrote:
Based on the recent discussions, what should change in the written policy?
I'd say: the following sentence:
However, they should be familiar with the material in the Learning
Manual (particularly ``Fundamental Concepts''), so do not repeat
that material in this book. Also, you should assume that users
Huh. On first reading, that looks exactly opposite of what I intended
to say...
... oh wait, I remember now! I was trying to say "don't explain that
{}() don't need to be nested... or that you can make a \new Staff{}
wherever you want... or that you can define variables ... etc".
Fundamental concepts should be explained in the NR also, but in a different
style than in the LM: in the NR in a precise, technical man page-like way,
in the LM in a tutorial style. There should not be *information* in the LM
which is not also available from the NR, it should just be presented
differently.
Agreed... ok, I guess I'd better do this sooner rather than later. I'll
add a NR 3 that discusses the same stuff as LM 2-3. Then the policy can
say "assume that readers are familiar with the material in NR 3".
It might seem a bit weird to assume that people know NR 3 when they're
reading NR 1, but I think we should start the NR with notation stuff,
not basic "lilypond is whitespace-insensitive"-type stuff.
Cheers.
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: chordmode chord question
On Nov 11, 2007, at 8:13 PM, Jay Hamilton wrote:
\version "2.10.25"
In chordmode I am trying to get in some kind of spelling
(I'm assuming that one can't put a chord like I just did in
chordmode).
\chordmode { g:m6-^5 }
Everything I've tried so far has either produced errors or no effect
at all.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: octava line broken in polyphony
Actually the problem seems to be with the PDF viewer that comes with the LilyPondTool plugin for JEdit (2.10.4, JEdit 4.3pre11, windows xp sp2). The octava line displays differently than with acrobat or gsview. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
chordmode chord question
\version "2.10.25" In chordmode I am trying to get in some kind of spelling (I'm assuming that one can't put a chord like I just did in chordmode). Everything I've tried so far has either produced errors or no effect at all. Yours- Jay Jay Hamilton www.soundand.com 206-328-7694 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: octava line broken in polyphony
Well, I just ran this on another machine and it looks fine, so I'll have to fool around on my end and see if I can't fix it. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Issue 34: Grace synchronization
Hi, Am I the only one who is sad to see Issue 34 at low priority? I guess it's about the bug mentioned at the bottom of: http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Grace-notes I write a lot of scores with drum flams (*) and this bug makes it a lot harder to write and maintain. regards, Peter ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: partcombine/drummode
Thanks Ole,
I missed that \rest command in the manual.
With this input, the output is fine:
ly input -
\version "2.10.29"
SNARE = \drummode { sn8-> \notemode {b'8 \rest b'4 \rest } }
BASSDRUM = \drummode { bd8 s s4 }
\score{
<<
\new DrumStaff <<
\set Staff.instrumentName = "Drums"
\new DrumVoice { \voiceOne \SNARE }
\new DrumVoice { \voiceTwo \BASSDRUM }
>>
>>
\layout {}
}
thanks again,
Bert
Op Sunday 11 November 2007, schreef Ole Schmidt:
> I don't know if there are better solutions but you can suppress the
> rest in one voice using s instead of r and center the rest from the
> other voice by changing temporarily to \notemode and using the \rest
> feature:
>
> sn4 \notemode {c''2. \rest}
> %% the c'' makes the position of the rest %%%
>
> also you can override the position of the rest:
>
> \once \override Rest #'staff-position = #1 r2.
>
> hope that helps
>
> ole
> > ly input -
> >
> > \version "2.10.29"
> >
> > SNARE = \drummode { sn8-> r r4 }
> > BASSDRUM = \drummode { bd8 r r4 }
> >
> > \score{
> > <<
> > \new DrumStaff <<
> > \set Staff.instrumentName = "Drums"
> > \new DrumVoice { \voiceOne \SNARE }
> > \new DrumVoice { \voiceTwo \BASSDRUM }
> >
> >
> >
> > \layout {}
> > }
> >
> >
> > ___
> > lilypond-user mailing list
> > lilypond-user@gnu.org
> > http://lists.gnu.org/mailman/listinfo/lilypond-user
--
M.vr.gr.
Bert Verbeek
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: the snippets vs. texinfo
On 10 Nov 2007, at 06:02, Graham Percival wrote: Consider NR 1.2.1 Tuplets, for example. (if you haven't already, please see the "LSR->lilypond docs" email) Currently, the "Commonly tweaked properties" contains five examples. These demonstrate a number of neat tricks you can do with tuplets... but what happens if something needs to be updated? (ie a property name changes, somebody thinks of a better explanation, there's a nicer way to achieve a particular tweak, etc) Personally, I don't care were stuff is put, if only the main document is having certain keyword to search for and an indication of where to read more about it. If I type a keyword in Preview (Mac OS X), I can see all occurrences. So, for example, suppose I want to typeset less common meters. These are called by names such as "irregular", "asymmetrical", "compound", "complex", "aksak", "limping", etc. I could search for a few of those names to get a hit. If there is a line in the document that this is discussed in more detail elsewhere, it would be fine with me. In this context, I have found examples in the main document to be useful because sometimes I have some LilyPond code, and then I can search for occurrences of some keywords in that code. This way, I can get places where the topic I am looking for might be discussed. Hans Aberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: the snippets vs. texinfo
On 10 Nov 2007, at 06:02, Graham Percival wrote: PDF vs. HTML: pdf readers generally prefer to have consecutive documentation, with few links. HTML readers generally prefer to have links everywhere. Those that produce both seem to choose a format that can produce both automatically by some program. For example the texinfo format. But that might unsuitable for LilyPond. So you might need you own format. Stable docs vs. wiki: some people want an unchanging, complete, finished set of docs, particularly if they print them out. Other people like the constant flux of web 2.0 stuff. These do different things. The docs should be designed to lower the need ask questions on the lists, I think. A wiki can in fact be used to replace the LilyPond site altogether. One example is http://haskell.org/ which nowadays expand to http://haskell.org/haskellwiki/Haskell So it is possibly the whole Haskell site. Once upon the time, the Haskell wiki was a separate project. Hans Åberg ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: partcombine/drummode
I don't know if there are better solutions but you can suppress the
rest in one voice using s instead of r and center the rest from the
other voice by changing temporarily to \notemode and using the \rest
feature:
sn4 \notemode {c''2. \rest}
%% the c'' makes the position of the rest %%%
also you can override the position of the rest:
\once \override Rest #'staff-position = #1 r2.
hope that helps
ole
Am 11.11.2007 um 13:08 schrieb Bert Verbeek:
Hello All,
First of all, thanks for this wonderfull program.
I'm using lilypond version 2.10.29 on Debian Linux testing.
I'm using lilypond for the first time for a complete BigBand score,
every
thing is going great, but I'm stuck with one minor problem.
Is it possible to use \partcombine and \drummode together in order
to print
common rests of snare and bassdrum voices only once in the normal
position of
the \DrumStaff?
If not, how should I fake this?
Thanks in advance,
Bert Verbeek
ly input -
\version "2.10.29"
SNARE = \drummode { sn8-> r r4 }
BASSDRUM = \drummode { bd8 r r4 }
\score{
<<
\new DrumStaff <<
\set Staff.instrumentName = "Drums"
\new DrumVoice { \voiceOne \SNARE }
\new DrumVoice { \voiceTwo \BASSDRUM }
\layout {}
}
___
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
partcombine/drummode
Hello All,
First of all, thanks for this wonderfull program.
I'm using lilypond version 2.10.29 on Debian Linux testing.
I'm using lilypond for the first time for a complete BigBand score, every
thing is going great, but I'm stuck with one minor problem.
Is it possible to use \partcombine and \drummode together in order to print
common rests of snare and bassdrum voices only once in the normal position of
the \DrumStaff?
If not, how should I fake this?
Thanks in advance,
Bert Verbeek
ly input -
\version "2.10.29"
SNARE = \drummode { sn8-> r r4 }
BASSDRUM = \drummode { bd8 r r4 }
\score{
<<
\new DrumStaff <<
\set Staff.instrumentName = "Drums"
\new DrumVoice { \voiceOne \SNARE }
\new DrumVoice { \voiceTwo \BASSDRUM }
>>
>>
\layout {}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line-width in \markuplines
Le 10 nov. 07 à 21:14, Monk Panteleimon a écrit :
Hello.
According to the 2.11 docs (8.1.9), I should be able to change the
line width in
\markuplines using \override #'(line-width . X)
but it doesn't seem to work.
example:
http://www.tcgalaska.com/kliros/ly/esauWood.ly
In 8.1.9, you can read:
\override-lines new-prop (pair) args (list of markups)
Like \override, for markup lists.
This is the command that you want to use.
The description of \justified-lines and \wordwrap-lines, recommending
using
\override, is a copy-paste mistake that I'm going to fix.
\markuplines {
\override-lines #'(line-width . 40) \justified-lines {
...
}
}
nicolas
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Concept for Newbies
Le mardi 06 novembre 2007 à 21:37 +0100, Francisco Vila a écrit : > I think some things you can do are: > - Promote this list, invite potential users and answer their questions. > - Build CD-ROMs complete with binaries and documentation, and give > them to interested people, as a gift > - Write your own tutorials and publish them in the LilyPondWiki. > - Share printed examples and web links with your friends. > - Offer yourself to retranscribe existing music thus improving its look > - Learn yourself as much as you can, to quickly resolve problems from > others, write "how to turn yourself into a lilypond guru in ten > lessons" > - Retain the complete manuals in your memory, if you can (CAUTION: not > before the GDP is finished :-) I'd like to add one item to this list: - Organize LilyPond one- or two-day learning sessions, animated by LilyPond experienced users and translators. Encouraged by several requests on the French list, we're working on setting this up in France (see topics "stage de formation" and "MAO libre à Avignon" on lilypond-user-fr list). Cheers, John ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
