Re: lilypond v2.13.54
Hi, 2011/3/17 Phil Holmes m...@philholmes.net It looks like the LilyPond installation is no longer adding the path to the executable to the Windows PATH. I have installed .54 and don't have it on my path. For me that's actually good - my PATH variable overflowed and I lost all the ones I wanted. However, for people who rely on the command line, it'll mean LP won't run. Can someone check whether this has been changed in the Windows install? I recently uninstalled 2.13.53 and installed 2.13.54 on my WinXP machine and it worked both from command line and by double-clicking. Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
ficta bug
I'm not top posting.
Using ficta I have a bug
\version 2.13.54
\score { %With surcharge of ligatures : Bad
\new Staff {
\time 2/2
\set suggestAccidentals = ##t
g'4 fis'8 [ g'8 ] a'8 [ g'8 a'16 g'16 fis'!16 e'16 ] |
d'1
}
\score { %Without surcharge of ligatures : Good
\new Staff {
\time 2/2
\set suggestAccidentals = ##t
g'4 fis'8 g'8 a'8 g'8 a'16 g'16 fis'!16 e'16|
d'1
}
}
\score { %With surcharge of ligatures no problem with time 4/4 : Good
\new Staff {
\time 4/4
\set suggestAccidentals = ##t
g'4 fis'8 [ g'8 ] a'8 [ g'8 ] a'16 [ g'16 fis'!16 e'16 ] |
d'1
}
Cordialement
Marc Lanoiselée
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Possible bug on \addlyrics in Lilypond 2.13.54
2011/3/20 Carl Sorensen c_soren...@byu.edu:
On 3/19/11 4:18 PM, Wim van Dommelen wi...@wanadoo.nl wrote:
I'm not top posting.
I found some weird behaviour in music disappearing when adding a lyric.
This is the smallest I could get the problem reduced to:
\version 2.13.54
\score {
\new Staff {
\relative g' { g1 }
% as soon as the next line is commented in the piece truncates,
% when commented out we see more notes appearing
\addlyrics { milk milk }
\relative g' { c2 g }
\addlyrics { su- gar su- gar }
}
}
Not too sure ifnthis counts as a real bug, nor how serious it might be. When
I
did something wrong please accept my apologies.
On the whole I'm very content with Lilypond, keep up the good work !
Regards,
Wim.
You've got the lyrics in a sequential block with the music, rather than in a
parallel block.
\new Staff {
\relative g' {g1}
\addlyrics { milk }
\relative g' { c2 g }
\addlyrics { su- gar }
}
I hate to say that \addlyrics is not intented to be used this way, either. i.e.
\new Staff {
\relative g' {g1}
\addlyrics { milk }
}
works as expected. The problem is that you can not put another pair
{music}\addlyrics{lyrics} on sequence, given the way in which
addlyrics works. I strongly recommend to use named voice contexts
plus \lyricsto for any other than mostest simplest songs.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1571 in lilypond: ficta and manual beaming - too long stems
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1571 by brownian.box: ficta and manual beaming - too long stems
http://code.google.com/p/lilypond/issues/detail?id=1571
Reported by MARC LANOISELEE in bug-lilypond:
%---8
\version 2.13.54 %% 2.12.3 does it good
\score {
\new Staff {
\set suggestAccidentals = ##t
a'8[ g'8 a'16 g'16 fis'!16 e'16]
}
}
%---8
See test-1.png.
Problem somewhat disappears if the last e'16 is dropped (see test-2.png
-- they're too short, aren't they?).
There is no problem with automatic beaming (test-3.png).
(unsure about priority, sorry)
Attachments:
test-1.png 1.1 KB
test-2.png 1008 bytes
test-3.png 1.3 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: ficta bug
On Mon 21 Mar 2011, 08:08 MARC LANOISELEE wrote:
I'm not top posting.
(your code can not be compiled -- you've missed one closing bracket)
Using ficta I have a bug
\version 2.13.54
\score { %With surcharge of ligatures : Bad
\new Staff {
\time 2/2
\set suggestAccidentals = ##t
g'4 fis'8 [ g'8 ] a'8 [ g'8 a'16 g'16 fis'!16 e'16 ] |
d'1
}
\score { %Without surcharge of ligatures : Good
\new Staff {
\time 2/2
\set suggestAccidentals = ##t
g'4 fis'8 g'8 a'8 g'8 a'16 g'16 fis'!16 e'16|
d'1
}
}
\score { %With surcharge of ligatures no problem with time 4/4 :
Good
\new Staff {
\time 4/4
\set suggestAccidentals = ##t
g'4 fis'8 [ g'8 ] a'8 [ g'8 ] a'16 [ g'16 fis'!16 e'16 ] |
d'1
}
I've submitted this as 1571:
http://code.google.com/p/lilypond/issues/detail?id=1571
In that example (i've shortened it) time does not matter.
Thank you!
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: big format for Notation Manual: unsupported compression type
2011/3/20 Frédéric Bron frederic.b...@m4x.org: 2.13.54 There is an issue with Notation Manual in big format: http://lilypond.org/doc/v2.13/Documentation/notation-big-page.html when clicking on an item of the table of contents (with firefox 3.6.15 on Windows), I get an error message: Erreur d'encodage de contenu. La page que vous essayez de voir ne peut être affichée car elle utilise un type de compression invalide ou non pris en charge. If I try to translate, it could give: Content encoding error. The page you try to see cannot be displayed because it uses an invalid or unsupported compression type It could be a temporary problem of the server and not a bug of the docs. I've tested the link on Ubuntu firefox 3.6.17pre Namoroka, firefox 4.0b13pre Minefield and Google Chrome 10.0.648.134 Whatever. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Release candidate 3 of 2.14 - LilyPond 2.13.54 released
2011/3/20 Frédéric Bron frederic.b...@m4x.org:
I noticed that convert-ly does not converts auto beaming settings.
Didn't convert-ly give you a message that said you needed to change it
manually?
I have run conver-ly for many files so that I did not see the message!
It would have been nice to have a rule that added a comment in the
file it-self, just before the command.
Something like:
%{ convert-ly: you must change this manually %}
#(override-auto-beam-setting '(end 1 8 3 4) 3 8 'Score)
which you can get with:
str = re.sub ('(?=#\\( *(override|revert)-auto-beam-setting)', '%{
convert-ly: you must change this manually %} ', str)
Good idea!
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately
Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 1572 by brownian.box: Enhancement req: Change chord name separator and inversion separator, separately http://code.google.com/p/lilypond/issues/detail?id=1572 Proposed by Arnout Engelen, http://lists.gnu.org/archive/html/bug-lilypond/2011-03/msg00283.html : %8- Hi. This is more of a feature request: I noticed I can change the 'chord name separator', but this also changes the symbol used to separate the chord from its root in case of for example c:/g. A naive way of allowing some more control might be: [patch and example here...] %8- Sorry, i know nothing about patches; so, please update labels and attach patches if necessary. Thanks! ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Change chord name separator and inversion separator, separately
On Mon 14 Mar 2011, 23:19 Arnout Engelen wrote:
I'm not top posting.
Thank you, added as 1572:
http://code.google.com/p/lilypond/issues/detail?id=1572
Hi. This is more of a feature request: I noticed I can change the 'chord name
separator', but this also changes the symbol used to separate the chord from
its
root in case of for example c:/g.
A naive way of allowing some more control might be:
diff --git a/ly/engraver-init.ly b/ly/engraver-init.ly
index 0720893..f9702bb 100644
--- a/ly/engraver-init.ly
+++ b/ly/engraver-init.ly
@@ -646,6 +646,7 @@ automatically when an output definition (a @code{\score}
or
majorSevenSymbol = #whiteTriangleMarkup
chordNameLowercaseMinor = ##f
chordNameSeparator = #(make-simple-markup /)
+ chordInversionSeparator = #(make-simple-markup /)
chordNameExceptions = #ignatzekExceptions
chordNoteNamer = #'()
chordRootNamer = #note-name-markup
diff --git a/scm/chord-ignatzek-names.scm b/scm/chord-ignatzek-names.scm
index 696d02f..38ef219 100644
--- a/scm/chord-ignatzek-names.scm
+++ b/scm/chord-ignatzek-names.scm
@@ -168,6 +168,7 @@ work than classifying the pitches.
(make-line-markup total)))
(let* ((sep (ly:context-property context 'chordNameSeparator))
+ (invSep (ly:context-property context 'chordInversionSeparator))
(root-markup (name-root root lowercase-root?))
(add-markups (map (lambda (x) (glue-word-to-step add x))
addition-pitches))
@@ -183,7 +184,7 @@ work than classifying the pitches.
suffixes
add-markups) sep))
(base-stuff (if (ly:pitch? bass-pitch)
- (list sep (name-note bass-pitch #f))
+ (list invSep (name-note bass-pitch #f))
'(
(set! base-stuff
diff --git a/scm/define-context-properties.scm b/scm/define-context-
properties.scm
index 439f68a..e3accb7 100644
--- a/scm/define-context-properties.scm
+++ b/scm/define-context-properties.scm
@@ -148,6 +148,8 @@ of pitches to chord names.)
(chordNameLowercaseMinor ,boolean? Downcase roots of minor chords?)
(chordNameSeparator ,markup? The markup object used to
separate parts of a chord name.)
+ (chordInversionSeparator ,markup? The markup object used to
+separate a chord name from its root note in case of inversions.)
(chordNoteNamer ,procedure? A function that converts from a pitch
object to a text markup. Used for single pitches.)
(chordPrefixSpacer ,number? The space added between the root
Example lilypond code:
\new ChordNames {
\chordmode {
% default behavior:
c c:7.11 c:/a c:7.11/a \break
% change the seperator for 'c:7/add11' and for 'c:/a'
independently
\set chordNameSeparator = \markup { | }
\set chordInversionSeparator = \markup { : }
c c:7.11 c:/a c:7.11/a \break
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning
Comment #10 on issue 1228 by brownian.box: \override RestCollision #'positioning-done = #merge-rests-on-positioning http://code.google.com/p/lilypond/issues/detail?id=1228 (sorry, i didn't find a better use of this report; so, just for the record) From: Jay Anderson Subj: merge-rests.ily w/ text on full measure rest segfault 2.13.53 (and from git) http://lists.gnu.org/archive/html/bug-lilypond/2011-03/msg00242.html ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
On Mon 14 Mar 2011, 11:16 I wrote: It is http://code.google.com/p/lilypond/issues/detail?id=1073 , isn't it? Can anyone clarify, please? So, if nobody knows, i am clearing importance flag from this thread, sorry. Thanks to all!-) I believe it will be fixed anyway. On Fri 18 Mar 2011, 23:58 Jan Nieuwenhuizen wrote: We are using it, but you're running a different file. def display_encode (s): print 'Yes we are here' return s.encode (sys.stderr.encoding or 'utf-8', 'replace') 23:57:19 janneke@vuurvlieg:~/vc/lilypond $ LANG=C PATH=~/vc/lilypond/out/bin:$PATH midi2ly minué Yes we are here LY output to `minu?-midi.ly'... On Sat 19 Mar 2011, 00:10 Francisco Vila wrote: Yes, there is a midi2ly there. 'which' confirms. -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1571 in lilypond: ficta and manual beaming - too long stems
Comment #1 on issue 1571 by x.sche...@gmail.com: ficta and manual beaming - too long stems http://code.google.com/p/lilypond/issues/detail?id=1571 This is the same issue as #1570 . Marc reported it on the French user list, Mike saw it and began to work directly on this. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: midi2ly crashed with UnicodeDecodeError in convert_midi()
2011/3/21 Dmytro O. Redchuk brownian@gmail.com: On Mon 14 Mar 2011, 11:16 I wrote: It is http://code.google.com/p/lilypond/issues/detail?id=1073 , isn't it? Can anyone clarify, please? So, if nobody knows, i am clearing importance flag from this thread, sorry. Thanks to all!-) I believe it will be fixed anyway. It is fixed, I pushed Jan's patch. http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=e378c1bba8d1db2689fe815c449ace57e234ab17 -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1073 in lilypond: convert-ly and accented characters
Comment #8 on issue 1073 by paconet@gmail.com: convert-ly and accented characters http://code.google.com/p/lilypond/issues/detail?id=1073 It is now fixed. See this thread at the end. http://lists.gnu.org/archive/html/bug-lilypond/2011-03/msg00269.html A problem remained but looks like one in my system only. 'make install' should be forced to install all new files, esp. python scripts. This is another issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1570 in lilypond: Fixes accidental suggestions in the beam collision engraver
Comment #1 on issue 1570 by brownian.box: Fixes accidental suggestions in the beam collision engraver http://code.google.com/p/lilypond/issues/detail?id=1570 Issue 1571 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1571 in lilypond: ficta and manual beaming - too long stems
Updates: Status: Duplicate Mergedinto: 1570 Comment #3 on issue 1571 by brownian.box: ficta and manual beaming - too long stems http://code.google.com/p/lilypond/issues/detail?id=1571 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1571 in lilypond: ficta and manual beaming - too long stems
Updates: Status: Verified Mergedinto: Comment #4 on issue 1571 by brownian.box: ficta and manual beaming - too long stems http://code.google.com/p/lilypond/issues/detail?id=1571 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 34 in lilypond: Grace synchronization
Comment #12 on issue 34 by paconet@gmail.com: Grace synchronization http://code.google.com/p/lilypond/issues/detail?id=34 Re: comment #4 both cases now produce the same output. Examples on #1 and #2 still valid. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
RE: lilypond v2.13.54
Janek, )-Original Message- )From: lilypond-user-bounces+james.lowe=datacore@gnu.org )[mailto:lilypond-user-bounces+james.lowe=datacore@gnu.org] On )Behalf Of Janek Warchol )Sent: 21 March 2011 06:29 )To: Phil Holmes )Cc: lilypond-u...@gnu.org; MING TSANG; Bugs )Subject: Re: lilypond v2.13.54 ) )Hi, ) )2011/3/17 Phil Holmes m...@philholmes.net ) ) It looks like the LilyPond installation is no longer adding the path ) to the executable to the Windows PATH. I have installed .54 and don't ) have it on my path. For me that's actually good - my PATH variable ) overflowed and I lost all the ones I wanted. However, for people who ) rely on the command line, it'll mean LP won't run. ) Can someone check whether this has been changed in the Windows )install? ) )I recently uninstalled 2.13.53 and installed 2.13.54 on my WinXP machine )and it worked both from command line and by double-clicking. ) What does your PATH command show when you run it in a CMD window. Does it show two LilyPond path statements or just one? Also did you use 'control panelsadd/remove programs' or run the uninstaller directly (they should do the same thing but it is interesting to know). James ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Fwd: Re: \repeat percent does not use the beat-slash stencil
Forwarded to the bug list for continuity.
Original Message
Subject:Re: \repeat percent does not use the beat-slash stencil
Date: Mon, 21 Mar 2011 13:18:00 +0100
From: Ed Gordijn ed.gord...@gmail.com
To: Colin Campbell c...@shaw.ca
Hi Collin,
The behaviour has changed since 2.13.39. In that version single
slashes were used in both cases. That is the reason that I found this.
And I have seen the text in the manual but I read it as a limitation
in functionality. That other notation than single slashes is not
supported for single beat repeats.
Greetings, Ed
2011/3/21, Colin Campbellc...@shaw.ca:
On 11-03-19 12:12 PM, Ed Gordijn wrote:
\version 2.13.54
\relative c''{
\time 4/4
\key c \major
% Ok
\repeat percent 4 {c8 c }
% Not Ok
\repeat percent 4 {c8 c16 c}
}
\layout{ ragged-right = ##t }
I believe this is a known issue, arising from using percent repeats on
16th note, Ed. Please have a look at the Notation Reference 1.4.2
Percent Repeats.
Colin Campbell
Bug Squad
--
The test of our progress is not whether we add more to the abundance
of those who have much, it is whether we provide enough for those who
have too little.
-Franklin D. Roosevelt, 32nd US President (1882-1945)
--
Verzonden vanaf mijn mobiele apparaat
--
The test of our progress is not whether we add more to the abundance
of those who have much, it is whether we provide enough for those who
have too little.
-Franklin D. Roosevelt, 32nd US President (1882-1945)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1573 in lilypond: Downstem 64th and 128th flag touchup
Status: Accepted Owner: Labels: Type-Enhancement Priority-High Patch-new New issue 1573 by colinpkc...@gmail.com: Downstem 64th and 128th flag touchup http://code.google.com/p/lilypond/issues/detail?id=1573 64th and 128th flags are made less trianglish (squeezed at the bottom), also the gap between flag and notehead is reduced. The flags look now more consistent with 16th and 32nd flags, as well as with upstem flags. See reitveld http://codereview.appspot.com/4273074/ and discussion in http://lists.gnu.org/archive/html/lilypond-devel/2011-03/msg00128.html ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Lilypond not working on Win7 sp1
After being updated to sp1 for Win7 lilypond no longer generates the pdf. It does generate the ps file, but it then errors out during the pdf conversion. I believe it has to do with ghostscript, but not sure. Please advise. log entry: Converting to `/Users/rrousseau/Desktop/test.pdf'... `(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 - dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite - sOutputFile=/Users/rrousseau/Desktop/test.pdf -c.setpdfwrite - f/Users/rrousseau/Desktop/test.ps)' failed (1) error: failed files: C:\\Users\\rrousseau\\Desktop\\test.ly ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54
I believe the documentation specifies that the Rehearsal, Metronome and Bar Number marks normally live in the Score context; to put them into your order, you need to take them out of Score and put them into Staff, per the note in NR 4.4.3. I know that and I am not saying the contrary but the default order does not correspond to what is in the documentation. This is what you get with 2.13.54 from top to bottom: 1 RehearsalMark 2 MetronomeMark 3 VoltaBracketSpanner 4 TextScript 5 OttavaBracket 6 TextSpanner 7 DynamicLineSpanner 8 BarNumber 9 TrillSpanner 10 MultiMeasureRestText You should get for example BarNumber in 3rd position because as you say, it is in the Score context. However, it is in 8th position. Also VoltaBracketSpanner should in 9th position, not in 3rd. Am I misunderstanding something? Frédéric ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond not working on Win7 sp1
Robbie,
Can you compile a new LP file that just has
{a b c d}
oh and the version number to just stop the warning message in the log.
See if this works? I think it will.
Next can you change it to
{a b c d^\markup {\sans hello} }
See if that fails.
James.
On 21 Mar 2011, at 19:31, Robbie Rousseau rob...@ipanache.com wrote:
After being updated to sp1 for Win7 lilypond no longer generates the pdf.
It does generate the ps file, but it then errors out during the pdf
conversion.
I believe it has to do with ghostscript, but not sure.
Please advise.
log entry:
Converting to `/Users/rrousseau/Desktop/test.pdf'...
`(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -
dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -
sOutputFile=/Users/rrousseau/Desktop/test.pdf -c.setpdfwrite -
f/Users/rrousseau/Desktop/test.ps)' failed (1)
error: failed files: C:\\Users\\rrousseau\\Desktop\\test.ly
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond not working on Win7 sp1
The first line works just fine. But the second line throws the same error. In my existing LP files it's failing when I use the \ChordNames markup. If I just use \chordmode it works, but not when I start using the ChordNames stuff. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54
Frédéric Bron wrote Monday, March 21, 2011 9:23 PM This is what you get with 2.13.54 from top to bottom: 1 RehearsalMark 1500 (Score) 2 MetronomeMark 1000 (Score) 3 VoltaBracketSpanner 600 4 TextScript 450 5 OttavaBracket400 6 TextSpanner 350 7 DynamicLineSpanner 250 8 BarNumber100 (Score) 9 TrillSpanner 50 10 MultiMeasureRestText450 You should get for example BarNumber in 3rd position because as you say, it is in the Score context. However, it is in 8th position. Also VoltaBracketSpanner should in 9th position, not in 3rd. Am I misunderstanding something? For easy reference I've added the values of 'outside-staff-priority taken from scm/define-grobs.scm above. The order you quote seems correct based on these except for MultiMeasureRestText. But in the example you gave earlier you don't use a multimeasure rest text as you attached \mark to the R1 rather than a markup. (Did you think the MM number was the MM text?) When this is done correctly the MM text appears in the correct position. Two comments. It seems as if the interleaving of the Score and Staff objects now seems to honour the value of 'outside-staff-priority even without moving the engravers into the Staff context. Maybe Joe could shed some light on this. The second comment is that the value of 'outside-staff-priority for VoltaBracketSpanner as quoted in the Learning Manual is wrong: it should be 600, not 100. This is the only error I can see. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Fwd: Re: \repeat percent does not use the beat-slash stencil
On 11-03-21 01:52 PM, Ed Gordijn wrote:
Hi Colin,
Attached is a figure of the result as it is and how it was in v2.13.39.
I'll hope that helps.
Greetings, Ed
Originele bericht
Onderwerp: Re: \repeat percent does not use the beat-slash stencil
Datum: Mon, 21 Mar 2011 13:18:00 +0100
Van:Ed Gordijn ed.gord...@gmail.com
Aan:Colin Campbell c...@shaw.ca
Hi Collin,
The behaviour has changed since 2.13.39. In that version single
slashes were used in both cases. That is the reason that I found this.
And I have seen the text in the manual but I read it as a limitation
in functionality. That other notation than single slashes is not
supported for single beat repeats.
Greetings, Ed
2011/3/21, Colin Campbellc...@shaw.ca:
On 11-03-19 12:12 PM, Ed Gordijn wrote:
\version 2.13.54
\relative c''{
\time 4/4
\key c \major
% Ok
\repeat percent 4 {c8 c }
% Not Ok
\repeat percent 4 {c8 c16 c}
}
\layout{ ragged-right = ##t }
I believe this is a known issue, arising from using percent repeats on
16th note, Ed. Please have a look at the Notation Reference 1.4.2
Percent Repeats.
Colin Campbell
Bug Squad
I did some digging in the git history, and found that the behavior
changed in 2.13.51, when the percent repeat and beat slash code was
heavily modified. For interest's sake, here is the new regression test
which most closely fits your case:
The file is in input/regression/repeat-slash-mixed.ly
\version 2.13.51
\header {
texidoc = Beat repeats for patterns containing mixed durations use
a double percent symbol.
}
\relative c' {
\repeat percent 4 {
c8. d f16
}
\repeat percent 2 {
\times 2/3 {
r8 d e
}
c4
}
}
So, LilyPond is behaving as expected, but I'll raise an issue regarding
the need to update the Notation Reference to reflect the new behaviour,
and to add more complete examples.
Thanks for your help in digging this out, Ed!
Colin Campbell
Bug Squad
--
The test of our progress is not whether we add more to the abundance
of those who have much, it is whether we provide enough for those who
have too little.
-Franklin D. Roosevelt, 32nd US President (1882-1945)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash
Status: Accepted Owner: Labels: Type-Documentation Priority-High New issue 1574 by colinpkc...@gmail.com: DOC: Need updated/expanded documentation of percent repeat/beat slash http://code.google.com/p/lilypond/issues/detail?id=1574 Issue http://code.google.com/p/lilypond/issues/detail?id=1426 updated percent repeats and beat slashes, but the documentation in NR 1.4.2 needs updating, in particular to explain and show the treatment of short-duration notes and patterns of mixed length notes. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54
2011/3/21 Trevor Daniels t.dani...@treda.co.uk Frédéric Bron wrote Monday, March 21, 2011 9:23 PM This is what you get with 2.13.54 from top to bottom: 1 RehearsalMark 1500 (Score) 2 MetronomeMark 1000 (Score) 3 VoltaBracketSpanner 600 4 TextScript 450 5 OttavaBracket400 6 TextSpanner 350 7 DynamicLineSpanner 250 8 BarNumber100 (Score) 9 TrillSpanner 50 10 MultiMeasureRestText450 You should get for example BarNumber in 3rd position because as you say, it is in the Score context. However, it is in 8th position. Also VoltaBracketSpanner should in 9th position, not in 3rd. Am I misunderstanding something? For easy reference I've added the values of 'outside-staff-priority taken from scm/define-grobs.scm above. The order you quote seems correct based on these except for MultiMeasureRestText. But in the example you gave earlier you don't use a multimeasure rest text as you attached \mark to the R1 rather than a markup. (Did you think the MM number was the MM text?) When this is done correctly the MM text appears in the correct position. Two comments. It seems as if the interleaving of the Score and Staff objects now seems to honour the value of 'outside-staff-priority even without moving the engravers into the Staff context. Maybe Joe could shed some light on this. This is because of the new ly:side-position-interface::move-to-extremal-staff callback that moves certain score-level objects to the top staff just after line breaking. Cheers, Joe ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1496 in lilypond: Update Pango to 1.28.3
Comment #9 on issue 1496 by pnorcks: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 A little update here: I just tested Pango 1.25.5 with LilyPond, which is the version appropriate for use in GUB (GNOME platform 2.27.91), but I don't think this is a good choice: This version of Pango is buggy with regard to extra-Y-offsets in fonts, as described in issue 1407. So the only option I can see is to update Pango (and the other GNOME platform packages). I'm looking at platform 2.32.1, so I'll try bumping to that first. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
