Re: Tagging Troubles
Thanks for the response. Now I'm running into a different problem.
I revised my score.ly and my piece.ly. Here's what they look like:
% piece.ly
woodwinds = {
% 2 flutes
\tag #'fl \new Staff {
\tag #'fl \set Staff.midiInstrument = flute
\set Staff.instrumentName = \markup { \center-align { 2 \line {
Flutes
} } }
\set Staff.shortInstrumentName = \markup { \center-align { 2 \line {
Fl. } } }
\tag #'fl \Key \global \partcombine \fluteOne \fluteTwo }
% 2 oboes
\tag #'ob12 \new Staff {
\tag #'ob12 \set Staff.midiInstrument = oboe
\set Staff.instrumentName = \markup { \center-align { 2 \line {
Oboes }
} }
\set Staff.shortInstrumentName = \markup { \center-align { 2 \line {
Ob. } } }
\tag #'ob12 \Key \global \partcombine \oboeOne \oboeTwo }
% 2 clarinets in bb
\tag #'bbcl \new Staff {
\tag #'bbcl \set Staff.midiInstrument = clarinet
\set Staff.instrumentName = \markup { \center-align { 2 \line {
Clarinets } \line { in B \smaller \flat } } }
\set Staff.shortInstrumentName = \markup { \center-align { 2 \line {
Clar. } \line { in B \smaller \flat } } }
\tag #'bbcl \transpose bes c \Key \global \transpose bes c
\partcombine
\clarinetBbOne \clarinetBbTwo }
% 2 bassoons
\tag #'bn12 \new Staff {
\tag #'bn12 \set Staff.midiInstrument = bassoon
\set Staff.instrumentName = \markup { \center-align { 2 \line {
Bassoons } } }
\set Staff.shortInstrumentName = \markup { \center-align { 2 \line {
Bsns. } } }
\tag #'bn12 \Key \global \partcombine \bassoonOne \bassoonTwo }
}
brass = {
% 4 horns in f
\new GrandStaff
% 2 horn in f
\tag #'fhn12 \new Staff {
\tag #'fhn12 \set Staff.midiInstrument = french horn
\tag #'fhn12 \Key \global \partcombine \hornFOne \hornFTwo
}
% 2 horns in f
\tag #'fhn34 \new Staff {
\tag #'fhn34 \set Staff.midiInstrument = french horn
\tag #'fhn34 \transpose f c \Key \global \transpose f c
\partcombine
\hornFThree \hornFFour }
}
% score.ly
\include piece.ly
#(set-global-staff-size 14)
%\set Score.skipBars = ##t
\score {
\new StaffGroup \woodwinds
\new StaffGroup \brass
\layout { }
\midi { }
}
When I try and compile score.ly I recieve a syntax error - unexpected \new,
referring to the \new preceding StaffGroup \brass. Can you think of a
solution to this problem. As an aside question is it possible to give an
instrumentName to the grandstaff?
Thanks.
Mats Bengtsson-4 wrote:
I'm not sure that you have correctly understood the syntax of \tag.
For example in
\tag #'woodwinds
...
the tag applies to the full music expression ... , not only to the
end of the line.
/Mats
mojocojo2000 wrote:
I'm trying to create a grand staff around two oboe parts when score.ly is
compiled. The files I'm using are belowed.
% piece.ly
music = {
% oboe I.II
\tag #'woodwinds \new GrandStaff
\tag #'woodwinds \tag #'ob12 \new Staff {
\tag #'woodwinds \tag #'ob12 \set Staff.midiInstrument = oboe
\tag #'woodwinds \set Staff.instrumentName = Oboe I.II
\tag #'woodwinds \set Staff.shortInstrumentName = Ob.I.II
\tag #'woodwinds \tag #'ob12 \global \partcombine \oboeOne \oboeTwo
}
% oboe III.IV
\tag #'woodwinds \tag #'ob34 \new Staff {
\tag #'woodwinds \tag #'ob34 \set Staff.midiInstrument = oboe
\tag #'woodwinds \set Staff.instrumentName = Oboe III.IV
\tag #'woodwinds \set Staff.shortInstrumentName = Ob.III.IV
\tag #'woodwinds \tag #'ob34 \global \partcombine \oboeThree \oboeFour
}
\tag #'woodwinds
}
% ob12.ly
\version 2.10.0
\include piece.ly
\header {
instrument = Oboe I.II
}
\score {
\keepWithTag #'ob12 \music
\layout { }
\midi { }
}
% score.ly
\version 2.10.0
\include piece.ly
#(set-global-staff-size 14)
\score {
\new StaffGroup \keepWithTag #'woodwinds \music
\new StaffGroup \keepWithTag #'brass \music
\new StaffGroup \keepWithTag #'percussion \music
\new StaffGroup \keepWithTag #'strings \music
\layout { }
\midi { }
}
The problem is when I compile score.ly I get an error about unexpected
.
This of course comes from the line -- \tag #'woodwinds in piece.ly.
Is
there anyway to make this work?
--
=
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
Re: Take the Grand Documentation Project challenge!
On 17/10/2007, Graham Percival [EMAIL PROTECTED] wrote: I am calling for people to pledge time towards improving the LilyPond documentation. This pledge is valid until the end of 2007. We'll re-evaluate how things look in Jan 2008. Recommended donation: 1 hour per week. Hi Graham, A late reply, but: I'd like to help with the GDP :) I will probably have a couple of hours a week. Perhaps it's best for me to start with some of the formatting/trivial tasks to get a feel for working with the docs. -- Groeten, Alard. Ceterum censeo MS Word esse delendam. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Take the Grand Documentation Project challenge!
Alard de Boer wrote: On 17/10/2007, Graham Percival [EMAIL PROTECTED] wrote: I am calling for people to pledge time towards improving the LilyPond documentation. This pledge is valid until the end of 2007. We'll re-evaluate how things look in Jan 2008. Recommended donation: 1 hour per week. Hi Graham, A late reply, but: I'd like to help with the GDP :) I will probably have a couple of hours a week. Perhaps it's best for me to start with some of the formatting/trivial tasks to get a feel for working with the docs. Great! Start reading the text files on the GDP website, particularly helper-begin.txt and the texinfo-*.txt files. Then download tutorial.itely, make a few small changes (could be anything, even a completely made-up Alard was here) and send me the new file. Once you've done that, I'll give you a second assignment. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Tagging Troubles
Please read section Score is a single musical expression in the manual.
/Mats
mojocojo2000 wrote:
Thanks for the response. Now I'm running into a different problem.
I revised my score.ly and my piece.ly. Here's what they look like:
% piece.ly
woodwinds = {
% 2 flutes
\tag #'fl \new Staff {
\tag #'fl \set Staff.midiInstrument = flute
\set Staff.instrumentName = \markup { \center-align { 2 \line {
Flutes
} } }
\set Staff.shortInstrumentName = \markup { \center-align { 2 \line {
Fl. } } }
\tag #'fl \Key \global \partcombine \fluteOne \fluteTwo }
% 2 oboes
\tag #'ob12 \new Staff {
\tag #'ob12 \set Staff.midiInstrument = oboe
\set Staff.instrumentName = \markup { \center-align { 2 \line {
Oboes }
} }
\set Staff.shortInstrumentName = \markup { \center-align { 2 \line {
Ob. } } }
\tag #'ob12 \Key \global \partcombine \oboeOne \oboeTwo }
% 2 clarinets in bb
\tag #'bbcl \new Staff {
\tag #'bbcl \set Staff.midiInstrument = clarinet
\set Staff.instrumentName = \markup { \center-align { 2 \line {
Clarinets } \line { in B \smaller \flat } } }
\set Staff.shortInstrumentName = \markup { \center-align { 2 \line {
Clar. } \line { in B \smaller \flat } } }
\tag #'bbcl \transpose bes c \Key \global \transpose bes c
\partcombine
\clarinetBbOne \clarinetBbTwo }
% 2 bassoons
\tag #'bn12 \new Staff {
\tag #'bn12 \set Staff.midiInstrument = bassoon
\set Staff.instrumentName = \markup { \center-align { 2 \line {
Bassoons } } }
\set Staff.shortInstrumentName = \markup { \center-align { 2 \line {
Bsns. } } }
\tag #'bn12 \Key \global \partcombine \bassoonOne \bassoonTwo }
}
brass = {
% 4 horns in f
\new GrandStaff
% 2 horn in f
\tag #'fhn12 \new Staff {
\tag #'fhn12 \set Staff.midiInstrument = french horn
\tag #'fhn12 \Key \global \partcombine \hornFOne \hornFTwo
}
% 2 horns in f
\tag #'fhn34 \new Staff {
\tag #'fhn34 \set Staff.midiInstrument = french horn
\tag #'fhn34 \transpose f c \Key \global \transpose f c
\partcombine
\hornFThree \hornFFour }
}
% score.ly
\include piece.ly
#(set-global-staff-size 14)
%\set Score.skipBars = ##t
\score {
\new StaffGroup \woodwinds
\new StaffGroup \brass
\layout { }
\midi { }
}
When I try and compile score.ly I recieve a syntax error - unexpected \new,
referring to the \new preceding StaffGroup \brass. Can you think of a
solution to this problem. As an aside question is it possible to give an
instrumentName to the grandstaff?
Thanks.
Mats Bengtsson-4 wrote:
I'm not sure that you have correctly understood the syntax of \tag.
For example in
\tag #'woodwinds
...
the tag applies to the full music expression ... , not only to the
end of the line.
/Mats
mojocojo2000 wrote:
I'm trying to create a grand staff around two oboe parts when score.ly is
compiled. The files I'm using are belowed.
% piece.ly
music = {
% oboe I.II
\tag #'woodwinds \new GrandStaff
\tag #'woodwinds \tag #'ob12 \new Staff {
\tag #'woodwinds \tag #'ob12 \set Staff.midiInstrument = oboe
\tag #'woodwinds \set Staff.instrumentName = Oboe I.II
\tag #'woodwinds \set Staff.shortInstrumentName = Ob.I.II
\tag #'woodwinds \tag #'ob12 \global \partcombine \oboeOne \oboeTwo
}
% oboe III.IV
\tag #'woodwinds \tag #'ob34 \new Staff {
\tag #'woodwinds \tag #'ob34 \set Staff.midiInstrument = oboe
\tag #'woodwinds \set Staff.instrumentName = Oboe III.IV
\tag #'woodwinds \set Staff.shortInstrumentName = Ob.III.IV
\tag #'woodwinds \tag #'ob34 \global \partcombine \oboeThree \oboeFour
}
\tag #'woodwinds
}
% ob12.ly
\version 2.10.0
\include piece.ly
\header {
instrument = Oboe I.II
}
\score {
\keepWithTag #'ob12 \music
\layout { }
\midi { }
}
% score.ly
\version 2.10.0
\include piece.ly
#(set-global-staff-size 14)
\score {
\new StaffGroup \keepWithTag #'woodwinds \music
\new StaffGroup \keepWithTag #'brass \music
\new StaffGroup \keepWithTag #'percussion \music
\new StaffGroup \keepWithTag #'strings \music
\layout { }
\midi { }
}
The problem is when I compile score.ly I get an error about unexpected
.
This of course comes from the line -- \tag #'woodwinds in piece.ly.
Is
there anyway to make this work?
--
=
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
RE: GDP: pitches second draft
I see the note on the lowest staff has now been changed to a
C, but this is the bass C, not middle C.
Trevor
-Original Message-
From: [EMAIL PROTECTED]
[mailto:lilypond-user-bounces+t.daniels=treda.co.u
[EMAIL PROTECTED] Behalf Of
Risto Vaaraniemi
Sent: 17 October 2007 08:58
To: lilypond-user@gnu.org
Subject: Re: GDP: pitches second draft
Dear Graham,
The job you've done looks very nice.
One thing caught my eye, though. I don't quite
get the idea of one image
under 1.1.3 Displaying pitches namely Clef.
If the image tries to point out the location of
the middle C on each staff /
clef why there is an F on the lowest staff?
Should it be like this?
%
\new Staff {
% treble clef by default
c'1^middle C
}
\new Staff {
\clef alto
c'1^middle C
}
\new Staff {
\clef bass
c'1^middle C
}
-Risto
Graham Percival-2
This is the second draft of Pitches. Please
have a look; it's been
significantly updated. Remaining items are
Please let us known if there are any other
issues that should be
addressed.
Cheers,
- Graham
--
View this message in context:
http://www.nabble.com/GDP%3A-pitches-second-draft-tf4638551.
html#a13248776
Sent from the Gnu - Lilypond - User mailing list archive at
Nabble.com.
___
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: tutorial @seealso links
Definitely an improvement Trevor -Original Message- From: [EMAIL PROTECTED] [mailto:lilypond-user-bounces+t.daniels=treda.co.u [EMAIL PROTECTED] Behalf Of Graham Percival Sent: 20 October 2007 07:58 To: lilypond-user Mailinglist Subject: GDP: tutorial @seealso links Hi all, I updated Learning Manual 2.1.2 to use the same @seealso format as the notation reference. You can see the old method in 2.2.1, and actually the rest of the section for now. I'd like to change all the @seealso sections to match 2.1.2. Does anybody have a huge objection to this? Cheers, - Graham ___ 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: ReheasalMark in Staff context is broken - sponsorship of fix?
Did you try my fix, to move the Break_align_engraver to the Staff context?
\layout {
\context {
\Staff
\consists Mark_engraver
\consists Break_align_engraver
}
\context { \Score
\remove Mark_engraver
\remove Break_align_engraver
}
}
I have tried it on a couple of examples and cannot see that it
introduces any
other problems.
/Mats
Adam James Wilson wrote:
Hi Mats et al,
(RE: this bug: http://code.google.com/p/lilypond/issues/detail?id=432)
Moving Break_align_engraver to the Staff context works to get the
correct alignment of RehearsalMarks, but the side effect is that if
there is a mid-system Clef change in one Staff and not another, you
get a broken system barline - the Clef pushes aside the bar in its
Staff only, because a multiple-staff column is not created when the
engraver is removed from the Score context.
I tried a workaround of putting hidden clefs in the other staves to
pad them, but this seems impossible - making a Clef transparent or
breaking its visibility is equal to removing its width.
Unless you know another workaround, it seems the best to just get a
fix in place for the problem.
I'm willing to sponsor a fix to this bug; the idea is to be able to 1)
duplicate the default behavior of a Score-living RehearsalMark when it
is moved to the Staff context (at the beginning of a system it should
align to the clef, and then align to staff bars for the rest of the
system), and 2) to be able to explicitly modify the break-align symbol
for the Clef in each Staff at any position in the score.
On 10/19/07, Mats Bengtsson [EMAIL PROTECTED] wrote:
The bug has already been reported, see
http://code.google.com/p/lilypond/issues/detail?id=432
In your simple example, it helps to move also the Break_align_engraver
from the Score to the Staff context, but I have no idea if such an operation
will work well also for multi-stave scores or if something else will break.
/Mats
Adam James Wilson wrote:
There is a problem when moving the RehearsalMark to the Staff
context. In the case where the RehearsalMark remains in the Score
context (comment out the layout block below), the first RehearsalMark
aligns to a Clef and the rest align to staff-bars. This is the
correct behavior.
But if you move the RehearsalMark to the Staff context (retain the
layour block below), the opposite (and incorrect) behavior occurs: the
first RehearsalMark aligns to a staff-bar and the rest seem to align
to Clefs.
\version 2.11.34
%%{
\layout {
\context { \Score
\remove Mark_engraver
}
\context { \Staff
\consists Mark_engraver
}
}
%%}
\new Staff {
\bar |
\mark \default
\clef bass
c'4 c'4
\bar |
\mark \default
\clef treble
c'4 c'4
}
Should this be filed as a bug?
Best,
Adam
___
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: Rhythm marks / play style indication
That's (kind of) a feature! The new handling of vertical placement in version 2.11 will only move the rehearsal marks when absolutely necessary, in contrast to earlier versions. It admittedly looks a bit funny in this particular example, but the intention is to avoid collisions with the clef symbols (which is what the marks are attached to at the beginning of a line). /Mats Luc wrote: Hi When you compile the snippet about _Rhythm marks / play style indication_ with Version *2.11.33* (Windows XP) the result differs considerably from that in http://lsr.dsi.unimi.it/LSR/Item?id=204 (vertical alignment)! Rgds Luc ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: pitches second draft
On 22.10.2007 (11:56), Trevor Daniels wrote:
I see the note on the lowest staff has now been changed to a
C, but this is the bass C, not middle C.
Arrghh. Corrected in next update. Thanks.
eyolf
GDP helper and typo-(ir)responsible
--
_/I\_o__o___/I\ l * //_/ * __ ' .* l
I_l__l___I\ l *// _l__l_ . *. l
[__][__][(**)__][__](**)[__][] \l l-\ ---//---*(oo)--l
[][__][__(**)][__][_(**)_][__] l l \\ // -()-/ l
[__][__][_ll[__][__][ll][__][] l l \\)) .__.(..) .@@@:::l
[][__][__]l .l_][__][__] .l__][__] l l ll _(o_o)_(@*_*@ l
[__][__][/ _)[__][__]/ _)][__][] l l ll ( / \ ) / / / ) l
[][__][ /..,/][__][__][/..,/_][__][__] l l / \\ _\ \_ / _\_\ l
[__][__(__/][__][__][_(__/_][__][__][] l l__l
[__][__]] l , , . [__][__][] l
[][__][_] l . i. '/ , [][__][__] l/\**/\ season's
[__][__]] l O .\ / /, O[__][__][] l ( o_o )_) greetings
_[][__][_] l__l==='=l[][__][__] l___,(u u ,),__
[__][__]]/ /l\---/l\ [__][__][]/ {}{}{}{}{}{}R
In Ellen's house it is warm and toasty while fuzzies play in the snow outside.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Metronome mark interfers with note spacing
Hello,
is there a way to get the metronome mark not to interfere with note
spacing?
if I remove the metronome mark in the following snippet, all eight notes
are spaced evenly, with the metronome mark, the space between the first
and the second note is much larger.
thanks
rene
8 --- SNIPPET --- 8
\version 2.11.33
\include italiano.ly
\paper {
ragged-right = ##t
}
\relative do' {
\time 2/4
\tempo 4 = 100
\key re \major
\clef treble
la'8 la si si |
}
8 --- SNIPPET --- 8
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Metronome mark interfers with note spacing
Just add
\override Score.MetronomeMark #'extra-spacing-width = #'(+inf.0 . -inf.0)
before the first note.
/Mats
René Brandenburger wrote:
Hello,
is there a way to get the metronome mark not to interfere with note
spacing?
if I remove the metronome mark in the following snippet, all eight notes
are spaced evenly, with the metronome mark, the space between the first
and the second note is much larger.
thanks
rene
8 --- SNIPPET --- 8
\version 2.11.33
\include italiano.ly
\paper {
ragged-right = ##t
}
\relative do' {
\time 2/4
\tempo 4 = 100
\key re \major
\clef treble
la'8 la si si |
}
8 --- SNIPPET --- 8
___
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: Metronome mark interfers with note spacing
Hi Mats,
works fine ... thanks
rene
ps: by the way, that was the fastest solution I ever had from a
mailinglist
Am Montag, den 22.10.2007, 14:43 +0200 schrieb Mats Bengtsson:
Just add
\override Score.MetronomeMark #'extra-spacing-width = #'(+inf.0 . -inf.0)
before the first note.
/Mats
René Brandenburger wrote:
Hello,
is there a way to get the metronome mark not to interfere with note
spacing?
if I remove the metronome mark in the following snippet, all eight notes
are spaced evenly, with the metronome mark, the space between the first
and the second note is much larger.
thanks
rene
8 --- SNIPPET --- 8
\version 2.11.33
\include italiano.ly
\paper {
ragged-right = ##t
}
\relative do' {
\time 2/4
\tempo 4 = 100
\key re \major
\clef treble
la'8 la si si |
}
8 --- SNIPPET --- 8
___
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: Rhythm marks / play style indication
Hm... - interesting! And are there any plans to re-establish normal play style indications or at least hints how to do this? Thanks Luc Mats Bengtsson schrieb: That's (kind of) a feature! The new handling of vertical placement in version 2.11 will only move the rehearsal marks when absolutely necessary, in contrast to earlier versions. It admittedly looks a bit funny in this particular example, but the intention is to avoid collisions with the clef symbols (which is what the marks are attached to at the beginning of a line). /Mats Luc wrote: Hi When you compile the snippet about _Rhythm marks / play style indication_ with Version *2.11.33* (Windows XP) the result differs considerably from that in http://lsr.dsi.unimi.it/LSR/Item?id=204 (vertical alignment)! Rgds Luc ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Rhythm marks / play style indication
How do you define normal play style indications? If you want indication left aligned above the time signature instead of over the clef, then you can add the line \override Score.RehearsalMark #'break-align-symbols = #'( time-signature ) In the example in LSR, this will only help on the first line of the score, since there is no time signature indication on the following lines. However, in any realistic example, I guess you would have a new time signature anyway. /Mats Luc wrote: Hm... - interesting! And are there any plans to re-establish normal play style indications or at least hints how to do this? Thanks Luc Mats Bengtsson schrieb: That's (kind of) a feature! The new handling of vertical placement in version 2.11 will only move the rehearsal marks when absolutely necessary, in contrast to earlier versions. It admittedly looks a bit funny in this particular example, but the intention is to avoid collisions with the clef symbols (which is what the marks are attached to at the beginning of a line). /Mats Luc wrote: Hi When you compile the snippet about _Rhythm marks / play style indication_ with Version *2.11.33* (Windows XP) the result differs considerably from that in http://lsr.dsi.unimi.it/LSR/Item?id=204 (vertical alignment)! Rgds Luc ___ 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: Rhythm marks / play style indication
I would be happy to get all the notes on the same height - also those with different beams, brackets, stems and slurs! Luc Mats Bengtsson schrieb: How do you define normal play style indications? If you want indication left aligned above the time signature instead of over the clef, then you can add the line \override Score.RehearsalMark #'break-align-symbols = #'( time-signature ) In the example in LSR, this will only help on the first line of the score, since there is no time signature indication on the following lines. However, in any realistic example, I guess you would have a new time signature anyway. /Mats Luc wrote: Hm... - interesting! And are there any plans to re-establish normal play style indications or at least hints how to do this? Thanks Luc Mats Bengtsson schrieb: That's (kind of) a feature! The new handling of vertical placement in version 2.11 will only move the rehearsal marks when absolutely necessary, in contrast to earlier versions. It admittedly looks a bit funny in this particular example, but the intention is to avoid collisions with the clef symbols (which is what the marks are attached to at the beginning of a line). /Mats Luc wrote: Hi When you compile the snippet about _Rhythm marks / play style indication_ with Version *2.11.33* (Windows XP) the result differs considerably from that in http://lsr.dsi.unimi.it/LSR/Item?id=204 (vertical alignment)! Rgds Luc ___ 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: Rhythm marks / play style indication
Sorry, I didn't realize until now that you were talking about the vertical alignment within each indication, whereas I was talking about the vertical position of the full indication. You are lucky, since this problem has already been fixed in the next development version 2.11.35 that should appear soon. (It turns out to be related to the bug report http://code.google.com/p/lilypond/issues/detail?id=445can=1start=400 ) /Mats Luc wrote: I would be happy to get all the notes on the same height - also those with different beams, brackets, stems and slurs! Luc Mats Bengtsson schrieb: How do you define normal play style indications? If you want indication left aligned above the time signature instead of over the clef, then you can add the line \override Score.RehearsalMark #'break-align-symbols = #'( time-signature ) In the example in LSR, this will only help on the first line of the score, since there is no time signature indication on the following lines. However, in any realistic example, I guess you would have a new time signature anyway. /Mats Luc wrote: Hm... - interesting! And are there any plans to re-establish normal play style indications or at least hints how to do this? Thanks Luc Mats Bengtsson schrieb: That's (kind of) a feature! The new handling of vertical placement in version 2.11 will only move the rehearsal marks when absolutely necessary, in contrast to earlier versions. It admittedly looks a bit funny in this particular example, but the intention is to avoid collisions with the clef symbols (which is what the marks are attached to at the beginning of a line). /Mats Luc wrote: Hi When you compile the snippet about _Rhythm marks / play style indication_ with Version *2.11.33* (Windows XP) the result differs considerably from that in http://lsr.dsi.unimi.it/LSR/Item?id=204 (vertical alignment)! Rgds Luc ___ 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
three polyphonic voices on three systems and (at the same time) on PianoStaff
Hello everybody,
I am addicted to LilyPond since only a few days.
So first let me say big Thank you to those who invented this powerful program
with beautiful output!
I want to type a three-part fugue in two ways:
first as a tree-staff score,
and then as piano-score.
For convenience I want to type the voices only once.
I thought I could apply the Autochange-feature.
But it does not work as I expected. (I know. It would be a miracle.)
So, if it can be done, how can it be done?
See the example:
%%% BEGIN 3-part-Polyphony with AutoChange EXAMPLE
\version 2.10.33
global = {
\key c \minor
\time 2/2
}
firstvoice = {
\global
\relative c' {
es2 f |
g as |
bes c |
bes2. a4 |
bes1
}
}
secondvoice = {
\global
\relative c' {
g4 c bes as |
g es' d c |
bes g' f es |
d g8 f es2 |
d1
}
}
bassvoice = {
\global
\relative c {
c2 d |
es f |
g as |
bes c |
bes1
}
}
\header {
title = Autochange Staff
subtitle = applied on polyphonic piece
}
\score {
\new Staff \new Voice { \clef treble \firstvoice }
\new Staff \new Voice { \clef alto \secondvoice }
\new Staff \new Voice { \clef bass \bassvoice }
\header {
opus = This works fine
}
}
\score {
\new PianoStaff
\autochange {
\override Staff.NoteCollision #'merge-differently-headed = ##t
\override Staff.NoteCollision #'merge-differently-dotted = ##t
\secondvoice
}
\context Staff = up \new Voice { \firstvoice }
\context Staff = down \new Voice { \bassvoice }
\header{
breakbefore = ##t
opus = Can this be made working in an automatic way?
}
}
%%% END 3-part-Polyphony with AutoChange EXAMPLE
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Fw: three polyphonic voices on three systems and (at the same time) on PianoStaff
Which is the most convenient (possilby automatic) way to change the beaming
of triplets in a allabreve-piece without changing the beaming
of normal eighth notes (quavers)?
See the example (or if more convenient, the attachment):
%%% BEGIN Triplet-Beaming EXAMPLE
\version 2.10.33
\paper{ ragged-right=##t }
\score {
{
\time 2/2
\relative c' {
c4 d8 e f g a b |
c8 d16 c \set tupletSpannerDuration = #(ly:make-moment 1 4) \times 2/3 {
b8 c a g a f e f d } |
c1
}
}
}
\markup {
The result is as expected.
}
\markup {
But I would prefer the following default beaming,
}
\markup {
without being forced to manually enforce it, even in Alla Breve:
}
\score {
{
\time 2/2
\relative c' {
c4 d8 e f g a b |
c8 d16 c \set tupletSpannerDuration = #(ly:make-moment 1 4) \times 2/3 {
b8[ c a] g[ a f] e[ f d] } |
c1
}
}
}
\markup {
By the way: Why do the brackets disappear? Is this behaviour intented?
}
%%% END Triplet-Beaming EXAMPLE
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com \version 2.10.33
\paper{ ragged-right=##t }
\score {
{
\time 2/2
\relative c' {
c4 d8 e f g a b |
c8 d16 c \set tupletSpannerDuration = #(ly:make-moment 1 4) \times 2/3 { b8 c a g a f e f d } |
c1
}
}
}
\markup {
The result is as expected.
}
\markup {
But I would prefer the following default beaming,
}
\markup {
without being forced to manually enforce it, even in Alla Breve:
}
\score {
{
\time 2/2
\relative c' {
c4 d8 e f g a b |
c8 d16 c \set tupletSpannerDuration = #(ly:make-moment 1 4) \times 2/3 { b8[ c a] g[ a f] e[ f d] } |
c1
}
}
}
\markup {
By the way: Why do the brackets disappear? Is this behaviour intented?
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
line break in headers
How can I get two line in a header? Like:
\header {
copyright = First line \\ Second line
}
Charles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ReheasalMark in Staff context is broken - offer for sponsorship of fix
Hi Mats,
Yes I tried it, thanks for the idea, but in my score other things break as a
result of moving the Break_align_engraver to the Staff context.
Specifically, if there is a clef change in one staff but not another, the
system barline is broken - see the png I attached.
Also note that failing to set Timing.defaultBarType = produces crazy
barlines all over the place.
It is quite frustrating - when one problem is pushed down, another pops up
(frustrating mostly because I have an end of October deadline for completing
my piece, and I'm spending most of my time on typesetting.) Here's the
snippet that produces the attached image:
\version 2.11.34
\layout {
\context { \Score
\remove Break_align_engraver
\remove Mark_engraver
\remove Bar_number_engraver
\remove Metronome_mark_engraver
\remove Timing_translator
\remove Time_signature_engraver
\remove Default_bar_line_engraver
\override SpacingSpanner #'uniform-stretching = ##t
\override SpacingSpanner #'strict-note-spacing = ##t
proportionalNotationDuration = #(ly:make-moment 1 64)
}
\context { \Staff
\consists Break_align_engraver
\consists Timing_translator
\consists Mark_engraver
\consists Time_signature_engraver
\consists Default_bar_line_engraver
}
}
\new Score
\new StaffGroup
\new Staff {
\set Timing.defaultBarType =
\bar | \mark \default
\clef treble
\time 2/16
c'16[ c'16]
\bar | \mark \default
\clef treble
\time 3/16
c'16[ c'16 c'16]
\bar | \mark \default
\clef bass
\time 3/32
c'16 c'32
\bar |
}
\new Staff {
\bar | \mark \default
\clef treble
\time 3/16
c'16[ c'16 c'16]
\bar | \mark \default
\clef treble
\time 2/16
c'16[ c'16]
\bar | \mark \default
\time 3/32
c'16 c'32
\bar |
}
On 10/22/07, Mats Bengtsson [EMAIL PROTECTED] wrote:
Did you try my fix, to move the Break_align_engraver to the Staff context?
\layout {
\context {
\Staff
\consists Mark_engraver
\consists Break_align_engraver
}
\context { \Score
\remove Mark_engraver
\remove Break_align_engraver
}
}
I have tried it on a couple of examples and cannot see that it
introduces any
other problems.
/Mats
Adam James Wilson wrote:
Hi Mats et al,
(RE: this bug: http://code.google.com/p/lilypond/issues/detail?id=432 )
Moving Break_align_engraver to the Staff context works to get the
correct alignment of RehearsalMarks, but the side effect is that if
there is a mid-system Clef change in one Staff and not another, you
get a broken system barline - the Clef pushes aside the bar in its
Staff only, because a multiple-staff column is not created when the
engraver is removed from the Score context.
I tried a workaround of putting hidden clefs in the other staves to
pad them, but this seems impossible - making a Clef transparent or
breaking its visibility is equal to removing its width.
Unless you know another workaround, it seems the best to just get a
fix in place for the problem.
I'm willing to sponsor a fix to this bug; the idea is to be able to 1)
duplicate the default behavior of a Score-living RehearsalMark when it
is moved to the Staff context (at the beginning of a system it should
align to the clef, and then align to staff bars for the rest of the
system), and 2) to be able to explicitly modify the break-align symbol
for the Clef in each Staff at any position in the score.
On 10/19/07, Mats Bengtsson [EMAIL PROTECTED] wrote:
The bug has already been reported, see
http://code.google.com/p/lilypond/issues/detail?id=432
In your simple example, it helps to move also the Break_align_engraver
from the Score to the Staff context, but I have no idea if such an
operation
will work well also for multi-stave scores or if something else will
break.
/Mats
Adam James Wilson wrote:
There is a problem when moving the RehearsalMark to the Staff
context. In the case where the RehearsalMark remains in the Score
context (comment out the layout block below), the first RehearsalMark
aligns to a Clef and the rest align to staff-bars. This is the
correct behavior.
But if you move the RehearsalMark to the Staff context (retain the
layour block below), the opposite (and incorrect) behavior occurs: the
first RehearsalMark aligns to a staff-bar and the rest seem to align
to Clefs.
\version 2.11.34
%%{
\layout {
\context { \Score
\remove Mark_engraver
}
\context { \Staff
\consists Mark_engraver
}
}
%%}
\new Staff {
\bar |
\mark \default
\clef bass
c'4 c'4
\bar |
\mark \default
\clef treble
c'4 c'4
}
Should this be filed as a bug?
Re: line break in headers
Use a \markup field, and arrange them with \column and the like.
Cheers,
- Graham
Charles Gran wrote:
How can I get two line in a header? Like:
\header {
copyright = First line \\ Second line
}
Charles
___
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: line break in headers
Borrowing from
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/More-about-
stanzas#More-about-stanzas
Lilypond 2.10.33 doesn't accept this:
\header {
copyright = \markup { \column{
\line{ Verse 2. }
\line{ All the children laughed and played }
\line{ To see a lamb at school. }
}
}
Charles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
\fermata and \markup over a note
I need to have booth a fermata and a div. sign over a diad, how do I
get this?
a, e2\fermata\markup { div. }
gives me an error message.
Charles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \fermata and \markup over a note
\markup wants a direction, either ^ - _
Cheers,
- Graham
Charles Gran wrote:
I need to have booth a fermata and a div. sign over a diad, how do I
get this?
a, e2\fermata\markup { div. }
gives me an error message.
Charles
___
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: line break in headers
Get rid of the
Cheers,
- Graham
Charles Gran wrote:
Borrowing from
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/More-about-
stanzas#More-about-stanzas
Lilypond 2.10.33 doesn't accept this:
\header {
copyright = \markup { \column{
\line{ Verse 2. }
\line{ All the children laughed and played }
\line{ To see a lamb at school. }
}
}
Charles
___
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: \fermata and \markup over a note
This works:
{
a, e2\fermata-\markup { div. }
}
You have to attach the markup with the '-' just like an articulation.
2007/10/22, Charles Gran [EMAIL PROTECTED]:
I need to have booth a fermata and a div. sign over a diad, how do I
get this?
a, e2\fermata\markup { div. }
gives me an error message.
Charles
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line break in headers
Charles Gran wrote:
Lilypond 2.10.33 doesn't accept this:
\header {
copyright = \markup { \column{
\line{ Verse 2. }
\line{ All the children laughed and played }
\line{ To see a lamb at school. }
}
}
You've got the quotes at the wrong place. \markup itself returns a music
expression, as far as I understand, and should not be interpreted as a
string. In contrast, the arguments of the \line command aren't commands
but strings to be quoted.
And, by the way, you forgot one closing bracket.
\header {
copyright = \markup { \column{
\line{ Verse 2. }
\line{ All the children laughed and played }
\line{ To see a lamb at school. }
}
}
}
should work fine.
Alexander
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line break in headers
How can I get two line in a header? Like:
\header {
copyright = First line \\ Second line
}
Hi,
I guess that something like this should work
(sorry I'm at work at the moment and can't test):
\header {
copyright = \markup { \column {First line Second line } }
}
Regards,
Ralph
-
For ideas on reducing your carbon footprint visit Yahoo! For Good this month.___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line break in headers
On 22 Oct 2007 at 22:31, Ralph Little wrote:
How can I get two line in a header? Like:
\header {
copyright = First line \\ Second line
}
This works. Thank you.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: line break in headers
On 22 Oct 2007 at 23:29, Alexander Kobel wrote:
\header {
copyright = \markup { \column{
\line{ Verse 2. }
\line{ All the children laughed and played }
\line{ To see a lamb at school. }
}
}
}
This works as well. Thank you.
--
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: Rhythm marks / play style indication
That sounds good - thanks! Luc Mats Bengtsson schrieb: Sorry, I didn't realize until now that you were talking about the vertical alignment within each indication, whereas I was talking about the vertical position of the full indication. You are lucky, since this problem has already been fixed in the next development version 2.11.35 that should appear soon. (It turns out to be related to the bug report http://code.google.com/p/lilypond/issues/detail?id=445can=1start=400 ) /Mats Luc wrote: I would be happy to get all the notes on the same height - also those with different beams, brackets, stems and slurs! Luc Mats Bengtsson schrieb: How do you define normal play style indications? If you want indication left aligned above the time signature instead of over the clef, then you can add the line \override Score.RehearsalMark #'break-align-symbols = #'( time-signature ) In the example in LSR, this will only help on the first line of the score, since there is no time signature indication on the following lines. However, in any realistic example, I guess you would have a new time signature anyway. /Mats Luc wrote: Hm... - interesting! And are there any plans to re-establish normal play style indications or at least hints how to do this? Thanks Luc Mats Bengtsson schrieb: That's (kind of) a feature! The new handling of vertical placement in version 2.11 will only move the rehearsal marks when absolutely necessary, in contrast to earlier versions. It admittedly looks a bit funny in this particular example, but the intention is to avoid collisions with the clef symbols (which is what the marks are attached to at the beginning of a line). /Mats Luc wrote: Hi When you compile the snippet about _Rhythm marks / play style indication_ with Version *2.11.33* (Windows XP) the result differs considerably from that in http://lsr.dsi.unimi.it/LSR/Item?id=204 (vertical alignment)! Rgds Luc ___ 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
lyrics and polyphony
[I tried resarching this topic on the list archive but most related
topics are too extensive for me to sort out.]
In a choral piece, I have a part that tempoarily divides into (single-
line) polyphony. How do I handle lyrics at this point?
Charles
The format of the score is outlined below:
\version 2.10.33
\header {...}
}
global = {
\key a \minor
\time 4/4
}
sopranonotes = \relative c' {...}
sopranowords = \lyricmode {...}
altonotes = \relative c' {...}
altowords = \lyricmode {...}
tenornotes = \relative c' {...}
tenorwords = \lyricmode {...}
bassnotes = \relative c' {...}
basswords = \lyricmode {...}
\score{
\context ChoirStaff
\context Staff = soprano
\context Voice = sop { \global \sopranonotes }
\lyricsto sop \new Lyrics \sopranowords
\context Staff = alto
\context Voice = alt { \global \altonotes }
\lyricsto alt \new Lyrics \altowords
\context Staff = tenor
\context Voice = ten { \global \tenornotes }
\lyricsto ten \new Lyrics \tenorwords
\context Staff = bass
\context Voice = bas { \global \bassnotes }
\lyricsto bas \new Lyrics \basswords
\layout {
\context {
% a little smaller so lyrics can be closer to the staff.
\Staff
\override VerticalAxisGroup #'minimum-Y-extent = #'(-3 . 3)
}
}
}
--
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: lyrics and polyphony
This example attached:
\version 2.10.33
\header { }
}
global = {
\key a \minor
\time 4/4
}
sopranonotes = \relative c' { r1 r r r r }
sopranowords = \lyricmode { }
altonotes = \relative c' { r1 r r r r}
altowords = \lyricmode { }
tenornotes = \relative c' { \clef G_8 r1 | r4 { c4^\markup {
div. } c } \\ { c8 b a4 } r | r2^\markup { unis. } a2\fermata |
a4( g fis8 f) e( b') | a1 | }
tenorwords = \lyricmode { Not yet, not yet, not __ yet! }
bassnotes = \relative c' { \clef bass r1 r r r r }
basswords = \lyricmode { }
\score{
\context ChoirStaff
\context Staff = soprano
\context Voice = sop { \global \sopranonotes }
\lyricsto sop \new Lyrics \sopranowords
\context Staff = alto
\context Voice = alt { \global \altonotes }
\lyricsto alt \new Lyrics \altowords
\context Staff = tenor
\context Voice = ten { \global \tenornotes }
\lyricsto ten \new Lyrics \tenorwords
\context Staff = bass
\context Voice = bas { \global \bassnotes }
\lyricsto bas \new Lyrics \basswords
\layout {
\context {
% a little smaller so lyrics can be closer to the staff.
\Staff
\override VerticalAxisGroup #'minimum-Y-extent = #'(-3 . 3)
}
}
}
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
File information ---
File: post.ly
Date: 22 Oct 2007, 19:44
Size: 1351 bytes.
Type: Unknown
post.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
hyphens and spacing
I'm copying a choral piece and am finding the spacing too tight, I want to open it up and also have all hyphens in the lyrics print. Can anyone help or direct me to the appropriate sections in docs? I did find: \override Lyrics.LyricSpace #'minimum-distance = #5.0 in 7.3.8 Spacing lyrics but wanted to check if there were other methods (I'm especially intereted in the hyphen issue). Thanks! Charles ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
