Re: Laissez vibrer direction
Kieren MacMillan wrote:
Hi, Marcus:
Until the bug is fixed, perhaps you can use #'rotation as a workaround
option...?
Hi Kieren,
Thanks for the suggestion! I hadn't thought of that. Unfortunately, it
looks like it would be a bit of a pain to tweak the second two arguments
of the #'rotation setting: the relative coordinates of point around which
to rotate. The appropriate point varies depending on whether the note has
ledger lines, whether it's on or between ledger lines, and perhaps other
factors.
So I'm doing this instead:
\compressMusic #'(1 . 2) { e'''4~ \hideNotes e'''4 \unHideNotes } r4 r4
% in place of:
% e'''4\laissezVibrer r4 r4
There are other ways, of course, but that works well enough for now.
Marcus
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Laissez vibrer direction
Hi, Marcus: Until the bug is fixed, perhaps you can use #'rotation as a workaround option...? Hope this helps! Kieren. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Laissez vibrer direction
I see that this issue was unresolved on the lilypond-user list, Panteck
and Graham Percival posting (06 Sep 2006). And I ran into it myself today.
So here's a bug report.
Let me know if I've misunderstood how it's supposed work.
Marcus
\version "2.9.26"
% Bug report for LaissezVibrerTie:
% its direction seems to be broken.
% By default, it's fine for chords, but always down for notes.
% (It should be either up or down depending on the note's
% position on the staff, as with regular ties).
% And \override doesn't work on the #'direction setting, e.g.:
% \override LaissezVibrerTie #'direction = #UP
{
\override TextScript #'padding = #1
s4*0^"DEFAULT:"
d'4~d' d'\laissezVibrer_"down?" r
g''4~g'' g''\laissezVibrer_"up?" r
4~ \laissezVibrer_"up/down?" r
\break
\override LaissezVibrerTie #'direction = #UP
s4*0^"UP:"
d'4~d' d'\laissezVibrer_"up?" r
g''4~g'' g''\laissezVibrer_"up?" r
4~ \laissezVibrer_"up/up?" r
\break
\override LaissezVibrerTie #'direction = #DOWN
s4*0^"DOWN:"
d'4~d' d'\laissezVibrer_"down?" r
g''4~g'' g''\laissezVibrer_"down?" r
4~ \laissezVibrer_"down/down?" r
\break
}
\layout{ ragged-right=##t indent=#0 }
--- Forwarded message ---
From: "Graham Percival" <[EMAIL PROTECTED]>
To: Panteck <[EMAIL PROTECTED]>
Cc: lilypond-user@gnu.org
Subject: Re: Laissez vibrer question
Date: Wed, 06 Sep 2006 19:05:34 -0400
Panteck wrote:
I'm trying to force the direction of a laissez vibrer tie like so:
I can't figure out how to do it, either. The following notes look the
same to me:
\version "2.9.17"
\layout{ragged-right=##t}
{
\override LaissezVibrerTie #'direction = #UP
c'4\laissezVibrer
\override LaissezVibrerTie #'direction = #DOWN
c'4\laissezVibrer
}
However, laissezVibrer ties can clearly tie up, since we see it in the
example in the manual (as part of a chord). Have I missed anything?
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bus error on skip within doubly-nested tuplets
Trevor Bača escreveu:
Hi,
A skip within a doubly-nested tuplet causes a bus error. For example ...
%%% BEGIN BUG %%%
\version "2.9.26"
\new Staff {
\times 2/3 {
\times 2/3 {
c'8
s4 % THIS IS THE OFFENDING EXPRESSION
}
c'4
c'4
c'4
}
}
http://code.google.com/p/lilypond/issues/detail?id=119
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Bus error on skip within doubly-nested tuplets
Hi,
A skip within a doubly-nested tuplet causes a bus error. For example ...
%%% BEGIN BUG %%%
\version "2.9.26"
\new Staff {
\times 2/3 {
\times 2/3 {
c'8
s4 % THIS IS THE OFFENDING EXPRESSION
}
c'4
c'4
c'4
}
}
%%% END BUG %%%
... generates the following:
GNU LilyPond 2.9.26
Processing `0016.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects... Bus error
The skip is required for the error; changing the note to a skip like
this interprets fine:
%%% BEGIN OK %%%
\version "2.9.26"
\new Staff {
\times 2/3 {
\times 2/3 {
c'8
c'4 % THIS IS OK
}
c'4
c'4
c'4
}
}
%%% END OK %%%
The error seems somewhat important, given that interpretation stops completely.
--
Trevor Bača
[EMAIL PROTECTED]
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
shorter braces in 2.9.26?
Is it just me, or have the braces on PianoStaff and GrandStaff suddently
become shorter in 2.9.26?
I know LilypondTool (for jEdit) can sometimes display PDF files a little
bit differently (braces shifted, dashed lines with longer dashes), but the
following file gives me shortened (i.e. not as tall) braces in Xpdf 3 and
Adobe Reader 7 (for Linux) as well:
\version "2.9.26"
<<
\new GrandStaff
<<
\new Staff {c'}
\new Staff {\clef bass c}
>>
\new PianoStaff
<<
\new Staff {c'}
\new Staff {\clef bass c}
>>
Marcus
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bar of 16ths not properly positionned wrt triplets
Raphael Manfredi wrote: Whilst typesetting a partition with a duple meter in the upper part and a triple one in the lower (in the form of triplets), I find that the upper 16ths are not properly positionned horizontally: they should come after the 3rd beat of the triplet (3/4 > 2/3), but they are sometimes either vertically aligned or even coming before the last triplet chord! Hi Raphael, The output in 2.9 looks quite good, and it will be released soon, so it doesn't make sense to spend much time investigating this problem in 2.8. Thanks for the report, though! Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: FiguredBass Extender Lines wrong position - 2.9.26
Trent Johnston wrote:
Whoops forgot the reply all
Yes I know I provided the answers a while ago.
But at the moment the figures still show the same no matter what the
position they entered. Both the 3's in <3> <7 3> are on the bottom so
they
shouldn't be swapped in the first place. Even if they are, swapping the
numbers (<3> <3 7>) in the code still produces the same output as
demonstrated in the code I sent.
I don't know if "s" does the same thing but the manual says that "r"
is what is needed to fix that.
When using continuation lines, common figures are always put in the same
vertical position. When this is unwanted, you can insert a rest with
|r|. The rest will clear any previous alignment. For example, you can write
<4 6>8 r8
instead of
<4 6>4
Paul Scott
Trent
- Original Message - From: "Mats Bengtsson"
<[EMAIL PROTECTED]>
To: "Trent Johnston" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, October 23, 2006 4:26 PM
Subject: Re: FiguredBass Extender Lines wrong position - 2.9.26
This problem/feature has been discussed several times on the mailing
list,
check the archives.
/Mats
Trent Johnston wrote:
Hello everyone,
When using the figured bass above the staff with extender lines and
implicitBassFigures the the line always gets swapped around. In the
example below both lines should be positioned on the bottom.
Switching the order of numbers i.e. <3 7> instead of <7 3> makes no
change.
Thanks
Trent
\include "english.ly"
basso = \new Voice {
\time 3/2
\relative c {
\clef bass
%bar 1
ef2 ef ef
%bar 2
d2_\markup "numbers switch <3 7> instead of <7 3>" d d
%bar 3
c1.\fermata
%bar 4
b2 b b
%bar 5
c1.\fermata
%bar 6
R1*3/2
%bar 7
c'2 c c
}}
bassfig = \figuremode {
\set Staff.useBassFigureExtenders = ##t
<3>2 <7 3> s
\set Staff.useBassFigureExtenders = ##f
\set Staff.useBassFigureExtenders = ##t
<3>2 <3 7> s
\set Staff.useBassFigureExtenders = ##f
s1.
\set Staff.useBassFigureExtenders = ##t
\set Staff.implicitBassFigures = #'(3)
<6>4 <3> <5 3>2 s
\set Staff.useBassFigureExtenders = ##f
\set Staff.implicitBassFigures = #'()
}
\score {
<<
\new Staff = "cont" << \basso \context Staff = cont \bassfig >>
\layout {
indent = 1\cm
}
\midi { }
}
\paper { }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
