> [CVS 2004-01-19 18:06]
>
> I get the error below while `make all' processes
> generate-documentation.ly. [...]
I proceeded with the following patch; since I don't know for sure
that it is the right fix I post it here instead of applying it
directly to the CVS.
Werner
> In the past making smaller staffs was so painful that noone actually
> did it. As a result, we have been rather lax with doing calculations
> relative to the current staff symbol. I think that you are looking
> at bugs. (reports welcome :-)
Uh, oh. It was my hope to avoid this...
Werner
> ok, so
>
>
> > not this:
> >
> >8--
> > |
> > o
> > |
> >
>
> <->
>
> should be bigger than the ledger, no?
Just a small amount, yes. In tight situations, it is even possible to
center the `8' directly below the note, dropping the ottava line
complete
[CVS 2004-01-19 18:06]
I get the error below while `make all' processes
generate-documentation.ly.
Werner
==
Writing lilypond-internals.texi ... Backtrace:
In unknown file:
...
?: 19 (begin (set-cdr! p (list (f
[EMAIL PROTECTED] writes:
> > > #--
> > > #
> >
> > can you show a scan (how much bigger, how thick should the lines be,
> > etc.)
>
> Sorry, I don't have a scanner. A look into, say, the solo violin part
> of the Sibelius vio
[EMAIL PROTECTED] writes:
>
> > > % . The padding between the notes/staves and the ottava line must
> > > % not take into account the final vertical dashed line.
> > >
> >
> > huh? You want the vertical line to bump into the ledgers (3rd line) ?
>
> Perhaps a misunderstanding. I want this:
>
[EMAIL PROTECTED] writes:
>
> [mftrace 1.0.26
> potrace 1.3
> autotrace 0.30.2]
>
> I've just compared the files cmbxti8.pfa as produced with lilypond CVS
> 2004-01-18 23:13 MET (with autotrace) and CVS 2004-01-19 09:31 MET
> (with potrace).
>
> It seems to me that the results of potrace+mftra
[EMAIL PROTECTED] writes:
>
> fontSize = #-4
> StaffSymbol \set #'staff-space = #(magstep -4)
>
> within the \with { ... } group is not sufficient: In the smaller
> staff, rests under beams are incorrectly positioned; the stem length
> under beams is not correct, the dynamic marks are too big
[mftrace 1.0.26
potrace 1.3
autotrace 0.30.2]
I've just compared the files cmbxti8.pfa as produced with lilypond CVS
2004-01-18 23:13 MET (with autotrace) and CVS 2004-01-19 09:31 MET
(with potrace).
It seems to me that the results of potrace+mftrace are wrong. All
glyphs have zero depth; the
> > % . The padding between the notes/staves and the ottava line must
> > % not take into account the final vertical dashed line.
> >
>
> huh? You want the vertical line to bump into the ledgers (3rd line) ?
Perhaps a misunderstanding. I want this:
8--
o |
|
not this:
> > #
> > #--
> > #
> > #
> >
> > #
> > #
> > --
[CVS 2004-01-18 23:13 MET]
I want to do the following:
\score {
<<
\new Staff \with { #(set-staff-size 5) }
{
\viol
}
\new PianoStaff \klav
>>
}
But this doesn't work. Using
fontSize = #-4
StaffSymbol \set #'staff-space = #(magstep -4)
within t
> > % . Since tuplet lines are far thinner than beams, the standard
> > % quantization algorithm for vertical start and end positions
> > % gives bad results if the slope of the spanner is small. I
> > % suggest to increase the angle threshold at which tuplet
> > % spanners have a non-zero
[CVS 2004-01-19 09:31 MET]
> * For things with many bugs, eg. the ottava bracket, I would prefer
> a complete description of how things should look, if possible with
> a scan from a printed edition.
I don't have a scanner, sorry. For crowded piano music with all bells
and whistles have a loo
[EMAIL PROTECTED] writes:
> %
> % . The octavation in the fourth line misses vertical padding to the note
> % head.
> %
> % . A default horizontal offset to the right of the `8' should be
> % dependent on the length of the created octavation spanner. With other
> % words, even if the octavat
[EMAIL PROTECTED] writes:
> % . The algorithm to choose the direction of the ties doesn't work
> % properly. I suggest the following for applying ties sequentially
> % from top to bottom:
> %
> % + The topmost tie is always `up'.
> %
> % + If there is a vertical gap to the last note ab
[EMAIL PROTECTED] writes:
> %
> % . The octavation in the fourth line misses vertical padding to the note
> % head.
this is a silly bug.
> % . A default horizontal offset to the right of the `8' should be
> % dependent on the length of the created octavation spanner. With other
> % words,
[EMAIL PROTECTED] writes:
> % . Looking at the third tuplet I believe that the beam spanner code is
> % not appropriate for tuplet lines at all. It seems best to follow
> % the note head positions only, ignoring stems for computing the slope.
I think this is wrong, and will lead to large gaps
> http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Rehearsal-marks.html#Rehearsal%20marks
Thanks. It works as expected (except the bug with a rehearsal mark
at the start of a line which is not fixed yet).
> One thing I'm not sure about yet: markFormatter as a
> calling-conventio
See the third quintuplet.
Werner
==
%
% This file shows a problem with tuplet spanners in lilypond
% CVS 2004-01-18 23:13 MET.
%
% . Since tuplet lines are far thinner than beams, the standard
% quantization algorithm fo
> text-spanner.cc cannot deal with all your wishes. I rewrote some
> things for 2.1 CVS. Can you check how it fares?
See another mail with a new report.
> Also, I don't know everything of ottava brackets. I'd appreciate it
> if you could write a regression test that tests all of the features?
>
The following is something which I would really like to see corrected
as soon as possible. I can't say how difficult it is to fix, but it
is essential to piano music. Unfortunately, it is virtually
impossible to apply workarounds for the start and end problem of ties
-- if there is one please te
Han-Wen,
we are getting nearer. Again, thanks for your work on this.
Werner
==
%
% This file shows problems with octavation in lilypond
% CVS 2004-01-18 23:13 MET.
%
% . The octavation in the fourth line misses vertic
23 matches
Mail list logo
