Issue 305: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Comment #4 by lemzwerg:
Well, this `normally' isn't true for more complicated music, cf.
hairpin-dynamic2.png
-- how would `break-alignment' work? The name of this property implies
that there
Issue 302: bad shape for tied notes in different clefs
http://code.google.com/p/lilypond/issues/detail?id=302
Comment #4 by wbsoft:
In music composed or edited by Marcel Dupré, I have seen that a tie between two
notes with a clef change in between is rendered as two ties: a l.v. tie from the
first
Issue 302: bad shape for tied notes in different clefs
http://code.google.com/p/lilypond/issues/detail?id=302
Comment #3 by lemzwerg:
Hmm, a tie into nothing is very common for Debussy (i.e., a l.v. tie),
but if the
music continues in a different clef, I can't see an alternative to
convert it t
Issue 458: handling ties from different voices
http://code.google.com/p/lilypond/issues/detail?id=458
Comment #3 by lemzwerg:
I generally prefer solutions which don't need tweaks. Sometimes, I
agree, using
\tweak is an acceptable workaround, but in this case I have the feeling
a general
solut
2008/5/1 Neil Puttock <[EMAIL PROTECTED]>:
> > > "If the value is #X (or equivalently 1), the object is placed
> > > horizontally next to the other object. If the value is #Y or 0, it is
> > > placed vertically."
> >
> > Like most quantities in lily, we start counting axes at 0.
>
> Now
Issue 591: Left edge of hairpin aligns with arpeggio
http://code.google.com/p/lilypond/issues/detail?id=591
Comment #1 by hanwenn:
when I debug, and set a breakpoint in Hairpin::print() it turns out
that the left
bound of the hairpin has been messed with in mysterious ways,
(gdb) ps b->object_
Issue 305: positioning of hairpins and dynamics
http://code.google.com/p/lilypond/issues/detail?id=305
Comment #3 by hanwenn:
Actually, there is just one line of dynamics per voice, and they
normally should be
aligned. I can add a special 'break-alignment' event to support this though.
Issue
Issue 143: \setTextCresc incorrectly applied only once
http://code.google.com/p/lilypond/issues/detail?id=143
Comment #3 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_46
--
You received this message because you a
Issue 298: Ties do not appear when shortened because of an accidental
http://code.google.com/p/lilypond/issues/detail?id=298
Comment #3 by n.puttock:
I encounter this issue all the time (also with ties avoiding flags);
would it be
considered bad style if the tie ignored the accidental in this ca
Issue 298: Ties do not appear when shortened because of an accidental
http://code.google.com/p/lilypond/issues/detail?id=298
Comment #2 by v.villenave:
Yes indeed. IIUC:
%%%
\version "2.11.45"
\relative {
s2. 4~ | ~ 4 s2 |
}
% The upper tie does not appear, though the accidental
% is not pla
Issue 397: collision pitchedTrill and tie
http://code.google.com/p/lilypond/issues/detail?id=397
Comment #1 by hanwenn:
pitched trills are not that common; I suggest manual tweak for the tie
in this case.
Issue attribute updates:
Labels: -Priority-Low Priority-Postponed
--
You receiv
Issue 302: bad shape for tied notes in different clefs
http://code.google.com/p/lilypond/issues/detail?id=302
Comment #2 by hanwenn:
From what I understand, in several pieces (I remember seeing debussy),
it is common
for the tied note to remain in the old clef.
What is your suggestion for hand
Issue 458: handling ties from different voices
http://code.google.com/p/lilypond/issues/detail?id=458
Comment #2 by hanwenn:
Treating all the ties together would make the number of different formatting
combinations explode.
Wouldn't it be more productive to provide tools to tweak endpoints for
Issue 298: ties, polyphonic, articulation collision
http://code.google.com/p/lilypond/issues/detail?id=298
Comment #1 by hanwenn:
this is too much text. Need .ly snippet.
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fie
Issue 455: wanted: vertical slur instead of arpeggio
http://code.google.com/p/lilypond/issues/detail?id=455
Comment #1 by hanwenn:
Added some bare bones code in git. Please polish until it suits you.
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_46
--
You received
Issue 521: \repeatTie direction depends on next note (?)
http://code.google.com/p/lilypond/issues/detail?id=521
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_46
--
You received this message because you
Issue 143: \setTextCresc incorrectly applied only once
http://code.google.com/p/lilypond/issues/detail?id=143
Comment #2 by v.villenave:
Once this issue is addressed, it will make more sense to rename these
commands in
\xxxOn \xxxOff, for better consistency with the newly renamed commands
-- ho
Issue 434: unwanted direction change of broken tie
http://code.google.com/p/lilypond/issues/detail?id=434
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_46
--
You received this message because you are l
Issue 592: Regression: Tie direction reverse incorrectly on a
middle-staff note
http://code.google.com/p/lilypond/issues/detail?id=592
Comment #1 by hanwenn:
Fixing this is hairy; ties normally go on the other side of the stem.
To fix this,
we would have to link the formatting of both ties tog
Issue 141: harmonizing vertical tie positions
http://code.google.com/p/lilypond/issues/detail?id=141
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Priority-Low Priority-Postponed
--
You received this message because you are listed in
Issue 440: Tie direction reverse incorrectly between whole notes tied
across line breaks
http://code.google.com/p/lilypond/issues/detail?id=440
Comment #4 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_46
--
You
2008/5/1 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> 2008/5/1 Neil Puttock <[EMAIL PROTECTED]>:
>
> > "If the value is #X (or equivalently 1), the object is placed
> > horizontally next to the other object. If the value is #Y or 0, it is
> > placed vertically."
>
> Like most quantities in lily,
Issue 585: Regression: Bass figures collapsing
http://code.google.com/p/lilypond/issues/detail?id=585
Comment #2 by hanwenn:
don't forget to pull first; I cleaned a couple of the files relating to this.
--
You received this message because you are listed in the owner
or CC fields of this issue
Issue 585: Regression: Bass figures collapsing
http://code.google.com/p/lilypond/issues/detail?id=585
Comment #1 by hanwenn:
Joe, can you have a look? I get stuck debugging a bunch of skylines.
\paper { line-width = 10\cm }
<<
\new FiguredBass \figuremode{
\set useBassFigureExtenders = ##
[moved from lilypond-devel to bug-lilypond]
On 2008/04/26, Till Rettig wrote:
> I needed immediately to try the new command line option with xelatex,
> and there are some smaller issues that might be interesting: for some
> reason xelatex when called by lilypond-book dosn't find the font index,
Issue 578: Regression: Completion heads mess up lyrics
http://code.google.com/p/lilypond/issues/detail?id=578
Comment #3 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_46
--
You received this message because you a
Issue 615: lilypond-book 'relative' fragment option should imply 'fragment'
http://code.google.com/p/lilypond/issues/detail?id=615
New issue report by john.mandereau:
As 'relative' fragment option does not work without 'fragment', I made the
former option automatically imply the latter.
Issue a
2008/5/1 Neil Puttock <[EMAIL PROTECTED]>:
> > huh? X=0, Y=1
>
> Ah, no wonder I'm confused; it's just the descriptions for side-axis
> and direction that are topsy-turvy:
> "If the value is #X (or equivalently 1), the object is placed
> horizontally next to the other object. If the value i
2008/5/1 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> 2008/4/30 Neil Puttock <[EMAIL PROTECTED]>:
>
>
> > Hi there,
> >
> > For some reason I can't fathom, the autogenerated docs for layout
> > objects display the wrong values for the properties 'axes and
> > side-axis whenever the Y-axis is set.
2008/4/30 Neil Puttock <[EMAIL PROTECTED]>:
> Hi there,
>
> For some reason I can't fathom, the autogenerated docs for layout
> objects display the wrong values for the properties 'axes and
> side-axis whenever the Y-axis is set. For example, in
> define-grobs.scm, TextScript has the the follow
On Thu, 1 May 2008 03:41:43 + (UTC)
Mike Morrison <[EMAIL PROTECTED]> wrote:
> Hi all, let me know if this is the wrong place to report this. I
> think there is a small typo on
> http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Simple-notation
> There appears to be an errant parenthes
On Thu, 1 May 2008 09:46:45 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> (So far only the Learning Manual and the first chapter of Notation
> Reference are (almost) finished)
NR 1 is nowhere near almost finished. NR 1.1 Pitches is finished.
If we finish NR 1 in the next two months, it
2008/5/1 Mike Morrison <[EMAIL PROTECTED]>:
> Hi all, let me know if this is the wrong place to report this. I think there
> is
> a small typo on
> http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Simple-notation
> There appears to be an errant parenthesis where it says "The time signa
33 matches
Mail list logo
