Updates:
Status: Verified
Comment #6 on issue 1084 by brownian.box: lilypond-book fails on identical
snippets
http://code.google.com/p/lilypond/issues/detail?id=1084
(No comment was entered for this change.)
___
bug-lilypond mailing list
b
Updates:
Status: Verified
Comment #4 on issue 996 by brownian.box: Wrong beaming of eighth notes in
2/8 measures
http://code.google.com/p/lilypond/issues/detail?id=996
(No comment was entered for this change.)
___
bug-lilypond mailing list
On Mon 23 Aug 2010, 10:29 Patrick Schmidt wrote:
> Hi all,
>
> in the following example misplaced tremolos appear in tablature
> without \tabFullNotation. With \tabFullNotation the symbols are
> placed correctly but IMO in both cases the tremolo symbols are too
> massive in tablature (see attached
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1233 by brownian.box: Tremolos in tablatures are too massive
http://code.google.com/p/lilypond/issues/detail?id=1233
Reported by Patrick Schmidt:
http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00424.html
Pleas
On 8/23/10 3:28 PM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>> [...]
>>>
>> It seems that we should use 0.48 times the *actual* staff space, rather than
>> the default staff space.
> Um, after reading your answer twice - it should be the other way round,
> isn't it?
Oops, yes, of cour
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1232 by brownian.box: Misplaced tremolo in tablatures
http://code.google.com/p/lilypond/issues/detail?id=1232
Reported by Patrick Schmidt:
http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00424.html
Carl Sorensen schrieb:
[...]
The #'beam-thickness of the tremolo beams is defined in
scm/define-grobs.scm as .48 * staff space.
In ly/engraver-init.ly we have the staff space spread to 1.5 * staff
space, so it would be optimal to
define the #'beam-thickness in TabStaff being 0.48/1.5=0.32 to ens
Carl Sorensen schrieb:
[...]
It seems that we should use 0.48 times the *actual* staff space, rather than
the default staff space.
Um, after reading your answer twice - it should be the other way round,
isn't it?
The *actual* staff space within a TabStaff is 1.5 * default staff space,
a
Carl Sorensen schrieb:
On 8/23/10 1:26 PM, "Marc Hohl" wrote:
Patrick Schmidt schrieb:
Hi all,
Hi Patrick,
yes, of course. I didn't use tremolos very often while playing around with
the new tablature appearance which yielded to scm/tablature.scm, so
I overlooked this.
Patrick Schmidt schrieb:
Hi all,
in the following example misplaced tremolos appear in tablature
without \tabFullNotation. With \tabFullNotation the symbols are placed
correctly but IMO in both cases the tremolo symbols are too massive in
tablature (see attached pngs).
\version "2.13.30"
m
I think I have reported this before - a beamed note with an accidental
on a ledger line above the stave has the accidental colliding with the
stem of the previous note. For different notes it happens at different
heights above the stave and also seems to depend on the length of the
stem of the
In guitar scores I usually increase the default stem length to minimise the
amount of manual tweaking needed to prevent fingering indications from being
overlaid by beams (I usually put fingering indications above treble notes and
below bass notes).
If I do this, then in single-staff polyphony
Op maandag 23-08-2010 om 17:07 uur [tijdzone +], schreef
lilyp...@googlecode.com:
> Unfortunately, it seems that in GUB, python is not built with that python
> module, so of course the subprocess module refuses to laod.
I have been working on this and the latest gub does build this. It
see
On 8/23/10 1:26 PM, "Marc Hohl" wrote:
> Patrick Schmidt schrieb:
>> Hi all,
> Hi Patrick,
>
> yes, of course. I didn't use tremolos very often while playing around with
> the new tablature appearance which yielded to scm/tablature.scm, so
> I overlooked this.
>> Workaround(s):
>> 1) Use
>>
Am 23.08.2010 um 21:26 schrieb Marc Hohl:
Patrick Schmidt schrieb:
Hi all,
in the following example misplaced tremolos appear in tablature
without \tabFullNotation. With \tabFullNotation the symbols are
placed correctly but IMO in both cases the tremolo symbols are too
massive in tablat
Am Donnerstag, 19. August 2010, 09:43:11 schrieb Phil Holmes:
> "Trevor Daniels" wrote in message
> news:3df57d198d544514adecfbe3c1278...@trevorlaptop...
>
> > Eluze wrote Sunday, August 15, 2010 10:20 AM
> >
> >> Trevor Daniels wrote:
> >>> The mingw binary of 2.13.30 gives the following error
Updates:
Status: Fixed
Owner: reinhold.kainhofer
Comment #3 on issue 1226 by reinhold.kainhofer: lilypond-book in the MinGW
release is currently unusable (2.13.30?)
http://code.google.com/p/lilypond/issues/detail?id=1226
The filter_pipe function used os.popen3, which according
On Mon 23 Aug 2010, 10:04 Patrick Schmidt wrote:
> Hi all,
>
> it doesn't seem to be possible to draw arrow-type arpeggios across
> several voices. In the following example the arpeggio is drawn but
> the arrow is missing.
>
> \version "2.13.30"
> musicVoiceOne = {
> \arpeggioArrowUp
%{ \o
On Mon 23 Aug 2010, 10:29 Patrick Schmidt wrote:
> Hi all,
Hi!
(Un)fortunately, i know nothing about tablatures, so let's wait for some quite
possible feedback.
Tomorrow, if nothing happens (this is quite possible, too) i'll add this to
tracker.
Thank you!
(below is overquote, nothing more)
>
On Mon 23 Aug 2010, 01:42 Paul Scott wrote:
> I didn't see this in the bug list. I'm thinking it started with 2.13.30 but
> I'm not sure.
>
> The following code shows new clefs overlapping the non-church multimeasure
> rest "lines."
> \version "2.13.30"
>
> {
> \compressFullBarRests \overr
Status: Accepted
Owner:
Labels: Type-Collision Priority-Critical Regression
New issue 1231 by brownian.box: New clefs collide with compressed
multimeasure rests
http://code.google.com/p/lilypond/issues/detail?id=1231
Reported by Paul Scott:
http://lists.gnu.org/archive/html/bug-lilypond/
i think it started with 2.13.29 ( 2.13.28 looks fine)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
I didn't see this in the bug list. I'm thinking it started with 2.13.30 but
I'm not sure.
The following code shows new clefs overlapping the non-church multimeasure rest
"lines."
\version "2.13.30"
{
\compressFullBarRests \override Score.MultiMeasureRest #'expand-limit = #1
a'1 R1*2 \cl
Comment #25 on issue 684 by jan.nieuwenhuizen: Enhancement: MetronomeMark
should support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
@neil: can you please specify/clarify?
___
bug-lilypond mailing list
bug-lilypond@g
Hi all,
in the following example misplaced tremolos appear in tablature
without \tabFullNotation. With \tabFullNotation the symbols are
placed correctly but IMO in both cases the tremolo symbols are too
massive in tablature (see attached pngs).
\version "2.13.30"
music = {
4:16
\stem
Hi all,
it doesn't seem to be possible to draw arrow-type arpeggios across
several voices. In the following example the arpeggio is drawn but
the arrow is missing.
\version "2.13.30"
musicVoiceOne = {
\arpeggioArrowUp
4\arpeggio
}
musicVoiceTwo = {
%\arpeggioArrowUp
e4\arpeggio
}
26 matches
Mail list logo
