Re: odd choral score problem
I was afraid you would ask for this, so here goes:
my "soprano" file (shortened to just what would produce the error).
\version "2.10.0"
SopranoMusic=\relative
{
\key es \major
\time 5/2 b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 |
b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 |
\time 5/4 R1*5/4 |
\time 3/4 R1*3/4 |
\time 5/2 b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 \bar "||"
R1*10/2
b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 |
\time 5/4 R1*5/4 |
\time 3/4 R1*3/4 |
\time 5/2 b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 \bar "||"
}
my "soprano lyrics" file (again, shortened to just what produced the
error).
\version "2.8.8"
sopranolyrics=\lyricmode {
\set associatedVoice = #"SopranoMusic"
Lo,2 how4 a Rose e’er bloom2 -- ing from ten4 -- der2 stem hath4
sprung!2
Of Jes4 -- se’s line -- age com2 -- ing, as men4 of2 old have4 sung.2
\skip 1*5/4 \skip 2. a2 -- mid4 the cold of win2 -- ter,
When half4 spent2 was the4 night.2
\skip 1*10/2
With2 Ma4 -- ry we be -- hold2 it, the vir4 -- gin2 moth -- er4 kind.2
\skip 1*5/4 \skip 2. she2 bore4 to men a Sav2 -- ior,
When half4 spent2 was the4 night.2
}
my " closed score file. this is what has the problem
\version "2.10.0"
\include "deutsch.ly"
\include "01_soprano.ly"
\include "01_sopranolyrics.ly"
\score
{
\new ChoirStaff
<<
\new Lyrics = sopranos { s1 }
\new Staff = women <<\new Voice = "sopranos" { \voiceOne <<
\SopranoMusic >> }
\new Voice = "altos" { \voiceTwo << >> }
>>
\new Lyrics = "altos" { s1 }
\new Lyrics = "tenors" { s1 }
\new Staff = men
<<
\clef bass
\new Voice = "tenors" { \voiceOne }
\new Voice = "basses" { \voiceTwo }
>>
\new Lyrics = basses { s1 }
\context Lyrics = sopranos \lyricsto sopranos \sopranolyrics
>>
}
and my "open score" file, this does not have the problem.
\include "deutsch.ly"
\include "01_soprano.ly"
\include "01_sopranolyrics.ly"
\score
{
\new ChoirStaff
<<
\new Staff \SopranoMusic
\new Lyrics \sopranolyrics
>>
}
I had to take out the references to the other parts in the open score
version, becuase it generated erros.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: odd choral score problem
It seems that you use the \lyricsto feature in your "closed score" file but
not in the "open score" file. Since you have taken the effort to specify
the
durations explicitly in your lyrics part, I guess you could just as well
skip the \lyricsto feature also in the "closed score". However, you may want
to set the associateVoice property to get better alignment to the note
heads,
see "Another way of entering lyrics" in the manual.
/Mats
James Bailey wrote:
I was afraid you would ask for this, so here goes:
my "soprano" file (shortened to just what would produce the error).
\version "2.10.0"
SopranoMusic=\relative
{
\key es \major
\time 5/2 b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 |
b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 |
\time 5/4 R1*5/4 |
\time 3/4 R1*3/4 |
\time 5/2 b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 \bar "||"
R1*10/2
b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 |
\time 5/4 R1*5/4 |
\time 3/4 R1*3/4 |
\time 5/2 b'2 b4 b c b b2 g |
as g4 f~ f es~ es d es2 \bar "||"
}
my "soprano lyrics" file (again, shortened to just what produced the
error).
\version "2.8.8"
sopranolyrics=\lyricmode {
\set associatedVoice = #"SopranoMusic"
Lo,2 how4 a Rose e’er bloom2 -- ing from ten4 -- der2 stem hath4 sprung!2
Of Jes4 -- se’s line -- age com2 -- ing, as men4 of2 old have4 sung.2
\skip 1*5/4 \skip 2. a2 -- mid4 the cold of win2 -- ter,
When half4 spent2 was the4 night.2
\skip 1*10/2
With2 Ma4 -- ry we be -- hold2 it, the vir4 -- gin2 moth -- er4 kind.2
\skip 1*5/4 \skip 2. she2 bore4 to men a Sav2 -- ior,
When half4 spent2 was the4 night.2
}
my " closed score file. this is what has the problem
\version "2.10.0"
\include "deutsch.ly"
\include "01_soprano.ly"
\include "01_sopranolyrics.ly"
\score
{
\new ChoirStaff
<<
\new Lyrics = sopranos { s1 }
\new Staff = women <<\new Voice = "sopranos" { \voiceOne <<
\SopranoMusic >> }
\new Voice = "altos" { \voiceTwo << >> }
>>
\new Lyrics = "altos" { s1 }
\new Lyrics = "tenors" { s1 }
\new Staff = men
<<
\clef bass
\new Voice = "tenors" { \voiceOne }
\new Voice = "basses" { \voiceTwo }
>>
\new Lyrics = basses { s1 }
\context Lyrics = sopranos \lyricsto sopranos \sopranolyrics
>>
}
and my "open score" file, this does not have the problem.
\include "deutsch.ly"
\include "01_soprano.ly"
\include "01_sopranolyrics.ly"
\score
{
\new ChoirStaff
<<
\new Staff \SopranoMusic
\new Lyrics \sopranolyrics
>>
}
I had to take out the references to the other parts in the open score
version, becuase it generated erros.
___
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: uniform-stretching
Hi Trevor,
The mailserver of my ISP was down for 14 hours, sorry for the late
response. Thanks a lot for all your time and effort! The last example
you sent works pretty well here now except for the first measure
(4/4). It takes about the same amount of space as the following 3/8
measure.
Replacing that line with "\time 4/4 r4 r4 r4 r4" instead of the r1
will stretch out the measure but that shouldn't be necessary, right?
Does that have something to do with it being the initial measure?
--
Orm
Am 04. Dezember 2006, 19:13 Uhr (-0600) schrieb Trevor Bača:
> Hi Orm,
>
> OK, and overriding PaperColumn used to ##t (together with uniform
> stretching) evens out the last two measures in 5/8 perfectly (with no
> need to resort to the transparent Rest workaround).
>
> %%% BEGIN %%%
>
> \version "2.11.0"
>
> \layout {
> ragged-right = ##t
> }
>
> \score {
> \new Staff \with {
> \remove Separating_line_group_engraver
> } {
> \relative {
> \override Score.SpacingSpanner #'uniform-stretching = ##t
> \set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
>\override Score.PaperColumn #'used = ##t
> \time 4/4 r1
> \time 3/8 r4.
> \time 5/4 r1 r4
> \time 5/16 r4 r16
> \time 5/8 s2 s8
> \time 5/8 r2 r8
> }
> }
> }
>
> \score {
> \new Staff \with {
> \remove Separating_line_group_engraver
> } {
> \relative c' {
> \override Score.SpacingSpanner #'uniform-stretching = ##t
> \set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
>\override Score.PaperColumn #'used = ##t
> \time 4/4 r1
> \time 3/8 r4.
> \time 5/4 r1 r4
> \time 5/16 r4 r16
> \time 5/8 s2 s8
> \time 5/8 r2 r8
> }
> }
> }
>
> %%% END %%%
>
> I still don't understand why that initial measure in 4/4 is so short,
> though ...
>
> So the list of settings to use so far is:
>
>
> 1. \set proportionalNotationDuration = #(ly:make-moment n d) (in the Score)
> 2. \override SpacingSpanner #'uniform-stretching = ##t (in the Score)
> 3. \override PaperColumn #'used = ##t (in the Score)
> 4. \remove Separating_line_group_engraver (in the Staff)
>
> In addition, if you want "true" proportional notation (where time
> signatures and clefs and accidentals consume no space), then set
>
> 5. \override SpacingSpanner #'strict-note-spacing = ##t (in the Score)
>
> This should now be much closer.
>
> Also, some other contemporary best practices I use almost all the time are:
>
> Score:
> 6. allowBeamBreak = ##t
> 7. autoBeaming = ##f
> 8. tupletFullLength = ##t
> 9. \override Beam #'break-overshoot = #'(-0.5 . 1.0)
> 10. \override SpacingSpanner #'strict-grace-spacing = ##t
> 11. \override TupletBracket #'bracket-visibility = ##t
>
> Voice:
> 12. \remove Forbid_line_break_engraver
>
> Most of these additional settings aid in letting tuplet brackets and
> beams break across two or even three lines, and so may not be as
> useful in your current score. But if you do have sections with many
> measured spanners, consider the settings above for a starting point.
>
>
> --
> Trevor Bača
> [EMAIL PROTECTED]
> ___
> 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
Spanbar problem when avoiding collision between barline and lyrics
Hi all, I had a question about the following: I want to render the score of a choir piece of M. Praetorius and I want to do that in the old fashion of only having barlines between the staves. At the same time however I want to avoid the collision of Lyrics and those barlines. The score I want to create consists of four staves with the lyrics of each voice placed directly under each staff. I already figured out that by creating a normal StaffGroup and setting the BarLine transparency to ##t I can get the barlines to appear between the staves only. But when I follow the example on the web site on how to avoid the collision between Lyrics and Barlines (by adding the Barline_engraver to the Lyrics context and making the barlines transparent) something happens that I am unable to correct. It seems that, by adding the barline engraver to the Lyrics context an extra event is generated that triggers the spanbar engraver to connect to the tranparent Barline in the last Lyrics line. This obviously is invisible in the other Lyric lines, but this results in a line drawn from the lowest staff line to the baseline of the lowest lyrics line. I tried a few things like making the spanbar transparent but this results in loosing the barlines between staves alltogether. My question: how to solve this in such a way that the span bar is drawn between each staff but not to the lowest lyrics line while keeping the transparent bar line to the Lyrics context (as to have the same kind of alignment in comparison to the other lyric lines)? Is it possible to prevent the span bar engraver connecting to the lowest lyrics line? Thanks in advance! regards Maurits Lamers This message was sent using IMP, the Internet Messaging Program. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Number of pages output
Is it possible to print out the number of pages that Lilypond has output to a PDF. Or even better, can you add a check in the code that you are on the page you expect (a bit like barNumberCheck). So I could put \pageNumberCheck 2 at the end of part and if it has spilled onto 3 pages I can investigate. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Extracting parts from a .ly file?
On 04/12/06, Eduardo Vieira <[EMAIL PROTECTED]> wrote:
Hello users, does anybody have a Python or Perl script to extract parts from a
.ly file and save them into a different file?
It is not pretty and it doesn't to a great deal of syntax checking but
below is a perl script I've just thrown together which extract the
parts as you require. It should pick out things like 'soprano' while
ignoring things like '\soprano'. You should save it in a file called
ly-extract and call it with:
$ ly-extract infile.ly outfile.ly label
where label is soprano, alto, etc.
I don't know how perl works with Windows, but I would guess that you
would need to change the first line in some way.
Regards,
Joe
#!/usr/bin/perl
# ly-extract
#
# Extract a named section from a lilypond file
use strict;
my($fin,$fout,$label)[EMAIL PROTECTED];
if (!$label) {
print "Please supply input file, output file and label\n";
exit 0;
}
open(FIN,'<',$fin) or die "Cannot find input file";
open(FOUT,'>',$fout) or die "Cannot open output file";
my($line);
my($notfound)=1;
# Find start of the required block
while($notfound and chomp($line=)) {
# This will match:
# $label
# $label =
# $label = {
# $label = {
# but it will ignore completely any mistakes, such as
# $label {
# $label =
if ($line =~ /((?>)(.*)/) {
print FOUT $1;
if ($2 eq '{' or $2 eq '<<') {
$notfound=0;
$parcount++;
print FOUT $2;
} elsif ($2 eq '}' or $2 eq '>>') {
$parcount--;
print FOUT $2;
if ($parcount < 0) {
die "Something has gone horribly wrong!";
}
}
$line=$3;
} else {
chomp($line);
print FOUT $line;
$line='';
}
if (!$line) {
print FOUT "\n";
$line=;
}
}
close FIN;
close FOUT;
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uniform-stretching
On 12/5/06, Orm Finnendahl <[EMAIL PROTECTED]> wrote:
Hi Trevor,
The mailserver of my ISP was down for 14 hours, sorry for the late
response. Thanks a lot for all your time and effort! The last example
you sent works pretty well here now except for the first measure
(4/4). It takes about the same amount of space as the following 3/8
measure.
Replacing that line with "\time 4/4 r4 r4 r4 r4" instead of the r1
will stretch out the measure but that shouldn't be necessary, right?
Does that have something to do with it being the initial measure?
Hi Orm,
I'm not sure why the first 4/4 measure is short, even with all the
settings in the last mail. I've attached an example at the end that
maybe Han-Wen can take one last look at; perhaps there remains one
final setting for your music.
(As an observational aside, there seems to be a special class of
wildly difficult off-by-one difficulties in music notation. Take the
example of needing to \override PaperColumn #'used = ##t which we
discovered yesterday incrementally getting your example to work. On
the face of it, it seems utterly bizarre that some "abstract grob"
setting like PaperColumn should be necessary to make measure-initial
skips obey proportional spacing. But when I was thinking about
Han-Wen's explanation of uniform-stretching it all suddenly made
sense: uniform-stretching makes distances *AFTER* musical events
uniform; and what happens at the beginning of a measure? No musical
event, so nothing to make uniform. Makes sense, but wow. Anyway, I've
noticed that some of the most complex things in Lily's input happen
right at the *beginnings* of measures, lines, or parts, and so this
one remaining longish measure in 4/4 at least fits that pattern.)
Testing your hunch the r4 r4 r4 r4 will space differently (and
correctly) than r1, we see that you're right. And we also discover one
last very odd thing.
Here's a comparison between r4 r4 r4 r4 and r1 with your original music:
%%% BEGIN EXAMPLE 1 %%%
\version "2.10.0"
\layout {
ragged-right = ##t
}
\score {
\new Staff \with {
\remove Separating_line_group_engraver
} {
\relative c' {
\override Score.SpacingSpanner #'uniform-stretching = ##t
\set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
\override Score.PaperColumn #'used = ##t
\time 4/4 r1 % BUG? Measure is way too short, apparently
because of following music
\time 3/8 r4.
\time 5/4 r1 r4
\time 5/16 r4 r16
\time 5/8 s2 s8
\time 5/8 r2 r8
}
}
}
\score {
\new Staff \with {
\remove Separating_line_group_engraver
} {
\relative c' {
\override Score.SpacingSpanner #'uniform-stretching = ##t
\set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
\override Score.PaperColumn #'used = ##t
\time 4/4 r4 r4 r4 r4 % This measure's length is OK
\time 3/8 r4.
\time 5/4 r1 r4
\time 5/16 r4 r16
\time 5/8 s2 s8
\time 5/8 r2 r8
}
}
}
%%% END EXAMPLE 1 %%%
The first measure in 4/4 in the first score is too short, as we've
observed. But look what happens when we make a minimal example by
simply deleting all measures after the first; the "bug" vanishes:
%%% BEGIN EXAMPLE 2 %%%
\version "2.10.0"
\layout {
ragged-right = ##t
}
\score {
\new Staff \with {
\remove Separating_line_group_engraver
} {
\relative c' {
\override Score.SpacingSpanner #'uniform-stretching = ##t
\set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
\override Score.PaperColumn #'used = ##t
\time 4/4 r1 % Bug has vanished! Perhaps because no following music
}
}
}
\score {
\new Staff \with {
\remove Separating_line_group_engraver
} {
\relative c' {
\override Score.SpacingSpanner #'uniform-stretching = ##t
\set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
\override Score.PaperColumn #'used = ##t
\time 4/4 r4 r4 r4 r4
}
}
}
%%% END EXAMPLE 2 %%%
These two one-measure scores are *exactly* the same length (see attachment.)
So what's going on here? Why does more music on the line in example 1
score 1 cause Lily to scrunch up the very first measure??
--
Trevor Bača
[EMAIL PROTECTED]
even-initial-measures.png
Description: PNG image
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uniform-stretching
Trevor Bača escreveu: > (As an observational aside, there seems to be a special class of > wildly difficult off-by-one difficulties in music notation. Take the > example of needing to \override PaperColumn #'used = ##t which we > discovered yesterday incrementally getting your example to work. On > the face of it, it seems utterly bizarre that some "abstract grob" > setting like PaperColumn should be necessary to make measure-initial > skips obey proportional spacing. But when I was thinking about > Han-Wen's explanation of uniform-stretching it all suddenly made > sense: uniform-stretching makes distances *AFTER* musical events > uniform; and what happens at the beginning of a measure? No musical > event, so nothing to make uniform. Makes sense, but wow. Yes, this makes sense, but it's actually not a completely correct explanation. Normally, space between 2 columns (two left-edges of notes/rests) is thought to be composed of (FIXED + STRETCHABLE) space, where FIXED is the size of the symbol, and STRETCHABLE determines how things scale up for shorter or longer lines. uniform-stretching sets FIXED to 0.0, and refrains from optical tweaks to STRETCHABLE un#'used columns are normally thrown out of the spacing problem, because they distort things. In this case, they should stay. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uniform-stretching
Trevor Bača escreveu:
> \relative c' {
> \override Score.SpacingSpanner #'uniform-stretching = ##t
> \set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
> \override Score.PaperColumn #'used = ##t
> \time 4/4 r1 % BUG? Measure is way too short, apparently
> because of following music
> \time 3/8 r4.
> \time 5/4 r1 r4
> \time 5/16 r4 r16
> \time 5/8 s2 s8
> \time 5/8 r2 r8
> }
> }
> }
>
> So what's going on here? Why does more music on the line in example 1
> score 1 cause Lily to scrunch up the very first measure??
The measure length bounds the spacing (think of what would happen for a R1*33
without this).
However, the length used was the 3/8 rather than 4/4. Fixed in GIT.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uniform-stretching
On 12/5/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Trevor Bača escreveu: > (As an observational aside, there seems to be a special class of > wildly difficult off-by-one difficulties in music notation. Take the > example of needing to \override PaperColumn #'used = ##t which we > discovered yesterday incrementally getting your example to work. On > the face of it, it seems utterly bizarre that some "abstract grob" > setting like PaperColumn should be necessary to make measure-initial > skips obey proportional spacing. But when I was thinking about > Han-Wen's explanation of uniform-stretching it all suddenly made > sense: uniform-stretching makes distances *AFTER* musical events > uniform; and what happens at the beginning of a measure? No musical > event, so nothing to make uniform. Makes sense, but wow. Yes, this makes sense, but it's actually not a completely correct explanation. Normally, space between 2 columns (two left-edges of notes/rests) is thought to be composed of (FIXED + STRETCHABLE) space, where FIXED is the size of the symbol, and STRETCHABLE determines how things scale up for shorter or longer lines. uniform-stretching sets FIXED to 0.0, and refrains from optical tweaks to STRETCHABLE un#'used columns are normally thrown out of the spacing problem, because they distort things. In this case, they should stay. Perfect. Will put this into a HOWTO that I'm planning on putting together after Orm's piece with very detailed explanations of the different proportional parameters. Thanks very much. -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uniform-stretching
On 12/5/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Trevor Bača escreveu:
> \relative c' {
> \override Score.SpacingSpanner #'uniform-stretching = ##t
> \set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
> \override Score.PaperColumn #'used = ##t
> \time 4/4 r1 % BUG? Measure is way too short, apparently
> because of following music
> \time 3/8 r4.
> \time 5/4 r1 r4
> \time 5/16 r4 r16
> \time 5/8 s2 s8
> \time 5/8 r2 r8
> }
> }
> }
>
> So what's going on here? Why does more music on the line in example 1
> score 1 cause Lily to scrunch up the very first measure??
The measure length bounds the spacing (think of what would happen for a R1*33
without this).
However, the length used was the 3/8 rather than 4/4. Fixed in GIT.
Awesome.
Note to Orm then that we should remember to try the sample score
example on 2.11.2 when it releases.
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uniform-stretching
hello Orm, Trevor...
Sorry I have not been helping here. I had not checked my lilypond mail
for weeks! Thankfully we have Trevor, the sponsor of proportional
notation!
So, coincidentally, I just finished a piece for flute where I do
*exactly* the same thing Orm is trying to do: align a lilypond score
with some other graph above. My alignment came out almost perfect. There
are a couple of places where the score is just slightly off and I'm not
sure why this is, but you can barely notice it.
Trevor has pointed out the main elements to adjust for strict
proportional notation:
1. \set proportionalNotationDuration = #(ly:make-moment n d) (in the
Score)
2. \override SpacingSpanner #'uniform-stretching = ##t (in the Score)
3. \override PaperColumn #'used = ##t (in the Score)
4. \remove Separating_line_group_engraver (in the Staff)
5. \override SpacingSpanner #'strict-note-spacing = ##t (in the Score)
Out of these I only used no. 1,2 and 5.
Staffs in my score do have Separating_line_group_engraver, and I didn't
know about PaperColumn.
So are these two strictly necessary? In what cases would they be? Could
removing Separating_line_group_engraver have unwanted secondary
consequences... this creates the StaffSpacing grob correct?
Not sure I understand what PaperColumn #'used does...
I will try applying numbers 3 and 4 to my score and see what happens.
(and will be checking my email more often :| )
Trevor, I'm happy to help put together a tutorial on proportional
notation and temporal spacing issues in general.
Victor.
On Tue, 5 Dec 2006 09:44:15 -0600, "Trevor Bača"
<[EMAIL PROTECTED]> said:
> On 12/5/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> > Trevor Bača escreveu:
> > > \relative c' {
> > > \override Score.SpacingSpanner #'uniform-stretching = ##t
> > > \set Score.proportionalNotationDuration = #(ly:make-moment 8 50)
> > > \override Score.PaperColumn #'used = ##t
> > > \time 4/4 r1 % BUG? Measure is way too short, apparently
> > > because of following music
> > > \time 3/8 r4.
> > > \time 5/4 r1 r4
> > > \time 5/16 r4 r16
> > > \time 5/8 s2 s8
> > > \time 5/8 r2 r8
> > > }
> > > }
> > > }
> >
> > >
> > > So what's going on here? Why does more music on the line in example 1
> > > score 1 cause Lily to scrunch up the very first measure??
> >
> > The measure length bounds the spacing (think of what would happen for a
> > R1*33 without this).
> > However, the length used was the 3/8 rather than 4/4. Fixed in GIT.
>
> Awesome.
>
> Note to Orm then that we should remember to try the sample score
> example on 2.11.2 when it releases.
>
> --
> Trevor Bača
> [EMAIL PROTECTED]
--
V!ctor [EMAIL PROTECTED]
[EMAIL PROTECTED]
--
http://www.fastmail.fm - Does exactly what it says on the tin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uniform-stretching
On 12/5/06, V!ctor [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: hello Orm, Trevor... Sorry I have not been helping here. I had not checked my lilypond mail for weeks! Thankfully we have Trevor, the sponsor of proportional notation! So, coincidentally, I just finished a piece for flute where I do *exactly* the same thing Orm is trying to do: align a lilypond score with some other graph above. My alignment came out almost perfect. There are a couple of places where the score is just slightly off and I'm not sure why this is, but you can barely notice it. Trevor has pointed out the main elements to adjust for strict proportional notation: 1. \set proportionalNotationDuration = #(ly:make-moment n d) (in the Score) 2. \override SpacingSpanner #'uniform-stretching = ##t (in the Score) 3. \override PaperColumn #'used = ##t (in the Score) 4. \remove Separating_line_group_engraver (in the Staff) 5. \override SpacingSpanner #'strict-note-spacing = ##t (in the Score) Out of these I only used no. 1,2 and 5. Staffs in my score do have Separating_line_group_engraver, and I didn't know about PaperColumn. So are these two strictly necessary? In what cases would they be? Could removing Separating_line_group_engraver have unwanted secondary consequences... this creates the StaffSpacing grob correct? Not sure I understand what PaperColumn #'used does... Hi Víctor, Great to see you on the list again. Han-Wen put together a great explanation of PaperColumn this morning that's probably further down in your inbox, but I'll paste it in here anyway: %%% PaperColumn explanation %%% Normally, space between 2 columns (two left-edges of notes/rests) is thought to be composed of (FIXED + STRETCHABLE) space, where FIXED is the size of the symbol, and STRETCHABLE determines how things scale up for shorter or longer lines. uniform-stretching sets FIXED to 0.0, and refrains from optical tweaks to STRETCHABLE un#'used columns are normally thrown out of the spacing problem, because they distort things. In this case, they should stay. %%% END %%% So prior to looking at Orm's piece I was thinking exactly what you're thinking, ie, that PaperColumn doesn't matter because in the last piece I put together I left PaperColumn out completely and got absolutely fabulous proportional results anyway. (The piece for Carin that I mailed to you earlier.) BUT, if you check the flurry of mail I sent out yesterday, there is in fact a situation under which we need #'used PaperColumns: if there are skips at the beginning of a measure. Try it; run a proportional testfile with a measure-initial skip and watch how the spacing collapses. The solution is to \override PaperColumn #'used = ##t. (And so I bet that if you check over your flute piece you'll find that you have no measure-initial skips and can therefore get away without the PaperColumn stuff.) I will try applying numbers 3 and 4 to my score and see what happens. (and will be checking my email more often :| ) As far as \remove Separating_line_group_engraver goes ... it definitely moves stuff around in some of Orm's music that I was looking at yesterday, but I haven't yet had time to sit down and work out a minimal set of permutations to show the exact effect. That sounds like a good task to put on the list for the proportional HOWTO. Trevor, I'm happy to help put together a tutorial on proportional notation and temporal spacing issues in general. OK, good. I want the thing to wind up as one, solid, well laid-out PDF with the notation and Lily input side-by-side that we can then post on the Lily wiki (or just email out to whoever's interested). I'm almost at stopping point before the next piece so maybe we can Skype and draw up a table of contents to divide up the work. (Is the flute piece done? Mail me a copy if it's gone to the printers. And if you have a nice snippet at 400 x 600 or less, send it over and I'd love to post it on the blog.) -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
dynamic markings
Is there anyway to use different dynamic markings for different verses of a choral piece? For example, if verses 1 & 3 are to be forte, while 2 is to be mezzo forte (in all voices), is there a way of marking this. The easiest thing would be to be able to put the markings before the number of the verse, but I haven't figured out a way to do that. -- ° Chris° ° ><°> Christopher A. LaFond [EMAIL PROTECTED] http://www.celticharper.net Evolution is a harsh mistress. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
archives
Is there an archive anywhere to search for answers to certain questions, so as not to repeat the same questions all the time? -- ° Chris° ° ><°> Christopher A. LaFond [EMAIL PROTECTED] http://www.celticharper.net One tentacle, one vote. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: archives
Hi > Is there an archive anywhere to search for answers to certain questions, > so as not to repeat the same questions all the time? A little bit more sense of adventure and you could have found out ;) If you have a look on the bottom of the mails you get from the list you can find this link: http://lists.gnu.org/mailman/listinfo/lilypond-user There you can find a link to the archives. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uniform-stretching
Hi Trevor, Han-Wen, > Note to Orm then that we should remember to try the sample score > example on 2.11.2 when it releases. Thanks a lot for the fix Han-Wen! When will be the release of 2.11.2? I'm a little reluctant to compile myself and would rather do the spacing part of the work with the fixed engine. If I get to understand the details of the engine better, I'll definitely volunteer to help with the howto! -- Orm ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: archives
Franz Fellner wrote: Hi Is there an archive anywhere to search for answers to certain questions, so as not to repeat the same questions all the time? http://lists.gnu.org/mailman/listinfo/lilypond-user I also encourage people to contribute to LSR and suggest documentation improvements. http://lsr.dsi.unimi.it/ http://lilypond.org/web/devel/participating/documentation-adding Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Wikis [was: Re: Tutorial]
Valentin Villenave wrote:
> Hello everybody,
>
> I may be out-topic, but I would like to talk about how useful Wiki
> applications might be to Lily...
>
> For instance, Christophe Dang Ngoc Chan has started writing a quite
> good Wikibook, based on the official tutorial.
>
> http://fr.wikibooks.org/wiki/Introduction_%C3%A0_LilyPond
>
> Currently it is only in French, but as he told me, he would be ready
> to start another one in English. I find it would be a very good idea
> to open some Wiki-based Lilypond tutorial, or unofficial
> Documentation. This would make corrections much easier and simpler,
> and moreover this could help promoting Lilypond, since the
> Wikibooks-Wikipedia community is huge and very active.
>
> And if you like the Wiki idea, I'd like to add that there may be
> several opportunities to combine Wiki and Lilypond typesetting ; for
> instance one could imagine some extension like LaTex-oriented
> Wikipublisher ( http://www.wikipublisher.org/wiki/ ), but especially
> designed for Lilypond...
There is already an unofficial wiki on
http://lilypondwiki.tuxfamily.org/index.php?title=Main_Page
It's easy to start a new wiki, a new documentation, a new whatever, but
it's much harder to develop it on a long timescale.
Before reinventing the wheel, we should first look for what already
exists (or has existed). To be more precise:
1) you may find it instructive to read previous discussions on the
lilyond-{devel,usr} lists by searching the lists with the keyword
"wiki".
2) Johannes Schindelin has already developped a Mediawiki extension that
can run LilyPond.
3) In the past, there was in the footer of each HTML page of the
documentation a link to a dedicated wiki page, where users could add
comments. As long as an available LilyPond wiki exists, it might be good
to add this footer back. In that case, it would avoid duplicating the
official documentation, and still allow making comments/corrections
easily.
As Graham and others have already pointed out, it'd be very cumbersome
for the user to look for documentation at a dozen of places. Computer
music engraving, and thus LilyPond, are so specialized that cluttered
and concurrent sources of informations would really be a pain.
IMHO everyone should think twice about it before creating a new source
of information.
Cheers,
--
John Mandereau <[EMAIL PROTECTED]>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Wikis [was: Re: Tutorial]
John Mandereau escreveu: > 3) In the past, there was in the footer of each HTML page of the > documentation a link to a dedicated wiki page, where users could add > comments. As long as an available LilyPond wiki exists, it might be good > to add this footer back. this didn't work: we had the links for a year or so, and didn't get any input via the wiki to mention. regarding the current wiki, the info on translating the website is out of date -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Wikis [was: Re: Tutorial]
Han-Wen Nienhuys wrote: > John Mandereau escreveu: > > 3) In the past, there was in the footer of each HTML page of the > > documentation a link to a dedicated wiki page, where users could add > > comments. As long as an available LilyPond wiki exists, it might be good > > to add this footer back. > > this didn't work: we had the links for a year or so, and didn't get any input > via the wiki to mention. So if there weren't people to comment the docs, there may be likely not enough people to improve wiki-based docs. > regarding the current wiki, the info on translating the website is out of date Right. I put that on my to-do list. -- John Mandereau <[EMAIL PROTECTED]> ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
hiding time signatures
There are three helpful teaching aids that I see included in my current lilypond instructions. But my students would benefit by having the time signatures partially or completely hidden for quizzes/drills. I don't know much about coding etc. is this a task my coding friends might consider equal to a favor or is it much more complicated than that? Any suggestions? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
new here
I just read the "archive" string and have answered my own question, sorry for the already answered question! Glad this exists. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
