Re: Tuplet brackets appear when I've asked them not to
On Mon, 03 Mar 2008 09:35:58 +0100 Mats Bengtsson <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Hi, > > According to the doc, to suppress a tuplet number and > > bracket you do \override TupletNumber #'transparent = ##t > > No, this should only hide the number, not the bracket. > To control the visibility of the bracket, use the bracket-visibility. > As is noted in > http://lists.gnu.org/archive/html/lilypond-devel/2007-11/msg00139.html > the syntax of this property is sufficiently strange to deserve some > extra attention in the docs. For this kind of issue, I strongly recommend adding (or modifying) a snippet in LSR and marking it "rhythms" and "docs". Once that's done, it will definitely show up in the list of Rhythms snippets. Also, if it's important enough, it'll be included in the NR section directly. (this isn't specifically aimed at Mats adding snippets: rather, anybody who thinks that something "should be in the docs" should begin by adding it to LSR) Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 546 in lilypond: Incorrect merging when a same note has different accidentals
Issue 546: Incorrect merging when a same note has different accidentals
http://code.google.com/p/lilypond/issues/detail?id=546
Comment #7 by erlenda:
I've attached a patch that will fix this issue. According to Gardner
Read there is three ways to solve altered
unisons;
1) use split stems
2) use brackets
3) use normal stems with double accidentals
IMHO 1) and 2) look pretty messy, and in my eyes 3) is visually most
attractive and it is also fairly easy to
implement.
There is one problem with this patch: With code like << { ais } \\ { a
} >>, the "a" should automatically get a
forced natural. I haven't figured out how to solve this yet. A
workaround is to manually force the natural.
I've tested the patch against the relevant files in input/regressions
and I don't think I've broken anything (yet)
:-)
Comments?
Attachments:
alteredunison.diff 5.4 KB
Issue attribute updates:
Status: Started
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 540 in lilypond: programming error: 'cruelty to springs' and irregular spacing.
Issue 540: programming error: 'cruelty to springs' and irregular spacing. http://code.google.com/p/lilypond/issues/detail?id=540 Comment #15 by joeneeman: Oh, good, then this is a compiler bug and not our problem :) Thanks for your help in debugging and I'm sorry that we don't have a more satisfying fix for you. Issue attribute updates: Status: Invalid -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: uneven bars in alternate repeats
This problem has already been fixed in the development version, 2.11.x.
If you want to stick to 2.10, see
http://lists.gnu.org/archive/html/lilypond-user/2005-01/msg00013.html
/Mats
John Rehwinkel wrote:
If I have an alternative with a note sticking out above the staff,
LilyPond moves the marker for that alternative up to avoid collision
(as it should). However, it doesn't move the marker for other alternatives,
which gives an uneven look.
\version "2.10.33"
\paper{ ragged-right=##t }
\relative c'' {
\repeat volta 2 { e1 }
\alternative { { e } { e' } }
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
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
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Tuplet brackets appear when I've asked them not to
[EMAIL PROTECTED] wrote:
Hi,
According to the doc, to suppress a tuplet number and bracket
you do \override TupletNumber #'transparent = ##t
No, this should only hide the number, not the bracket.
To control the visibility of the bracket, use the bracket-visibility.
As is noted in
http://lists.gnu.org/archive/html/lilypond-devel/2007-11/msg00139.html
the syntax of this property is sufficiently strange to deserve some extra
attention in the docs.
/Mats
This works only in the absence of grace notes.
\version "2.10.10"
\score {
\context Staff \relative c'' {
\override TupletNumber #'transparent = ##t
\times 2/3 { \acciaccatura d8
c8 b c
}
}
}
Without the grace note, things work as expected. When it's there, you
see a bracket (but no number).
It'd be worth a note in the documentation, I think, to say under what
circumstances a tuplet bracket appears, and how to suppress it.
See:http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Tuplets
under `commonly tweaked properties'.
--
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au ERTOS within National ICT Australia
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
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
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 540 in lilypond: programming error: 'cruelty to springs' and irregular spacing.
Issue 540: programming error: 'cruelty to springs' and irregular spacing. http://code.google.com/p/lilypond/issues/detail?id=540 Comment #14 by wbsoft: --disable-optimising fixes the problem. All files that spewed these errors now compile fine! gcc -v Ingebouwde specs worden gebruikt. Target: i686-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/configure --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disable-multilib --enable-libmudflap --disable-libssp --enable-java-awt=gtk --with-arch=i686 --enable-languages=c,c++,java,treelang,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc versie 4.1.2 (Gentoo 4.1.2 p1.0.2) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
