Lilypond Crash on the following simple Code
The following Code produces a Crash on my Win XP
BTW: \markuplines should be storable in a Variable.
\version 2.12.3
Varname =
\markuplines{ }
\book{
\bookpart{
\Varname
\score {
c'4
}
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond Crash on the following simple Code
2011/2/13 Beat Stoecklin webmaster2...@elcappuccino.ch:
The following Code produces a Crash on my Win XP
BTW: \markuplines should be storable in a Variable.
It is, but not in 2.12
This crashes 2.13.49 when { } is empty
\markuplines{ }
{ c' }
--
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: Slur+Dot Collision
On Sat 12 Feb 2011, 21:17 Jay Anderson wrote: This is not a regression from 2.12. I know how to manually fix it, but it'd be nice if it avoided the dot automatically. Related bugs: 868, 1091, 1174, 1230, 1352. I didn't see any listed and 1175, but looks to be different. related to dot-slur collisions specifically so I thought it may be useful. Added as 1514: http://code.google.com/p/lilypond/issues/detail?id=1514 Thank you. -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1514 in lilypond: In tight situations slurs may collide with dots
Status: Accepted
Owner:
Labels: Type-Collision Priority-Medium
New issue 1514 by brownian.box: In tight situations slurs may collide with
dots
http://code.google.com/p/lilypond/issues/detail?id=1514
Reported by Jay Anderson,
http://lists.gnu.org/archive/html/bug-lilypond/2011-02/msg00244.html :
In tight situations slurs may collide with dots, badly:
%---8-
\version 2.13.50
\score
{
\new Staff \relative c'''
{
\time 6/8
{
g4. e8( f8. c16) | % Collision between dot and slur
}
}
}
\paper {
% with 2.5 dot is above slur,
% with 4.5 it's right under, very nice:
line-width = 4.5\cm
}
%---8-
It is possibly related to 868, 1091, 1174, 1175, 1230, 1352.
Attachments:
test2.png 1.2 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1091 in lilypond: Dot in \voiceOne collides with stem in \voiceThree in short intervals
Comment #3 on issue 1091 by brownian.box: Dot in \voiceOne collides with stem in \voiceThree in short intervals http://code.google.com/p/lilypond/issues/detail?id=1091 Another one is Issue 1514. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond Crash on the following simple Code
On Mon 14 Feb 2011, 09:35 Francisco Vila wrote:
2011/2/13 Beat Stoecklin webmaster2...@elcappuccino.ch:
The following Code produces a Crash on my Win XP
BTW: \markuplines should be storable in a Variable.
It is, but not in 2.12
This crashes 2.13.49 when { } is empty
\markuplines{ }
{ c' }
It doesn't crash in 2.13.50 for me.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1515 in lilypond: Subdivided beams are disregarded with \cueDuring
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1515 by brownian.box: Subdivided beams are disregarded with
\cueDuring
http://code.google.com/p/lilypond/issues/detail?id=1515
Reported by Ãyvind Moe,
http://lists.gnu.org/archive/html/bug-lilypond/2011-02/msg00162.html :
%---8-
\version 2.13.50
music = \relative c'' {
\set subdivideBeams = ##t
\set baseMoment = #(ly:make-moment 1 8)
c16 c c c
}
\addQuote music \music
\new Staff {
\cueDuring #music #UP s4
}
\new Staff {
\new CueVoice
\quoteDuring #music s4
}
%---8-
Attachments:
test2.png 1.2 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Subdivided beams are disregarded with \cueDuring
On Tue 08 Feb 2011, 07:26 Øyvind Moe wrote: I'm not top posting. % Subdivided beams are disregarded with \cueDuring, % work as expected with \quoteDuring \version 2.13.48 The same in 2.13.50, added as 1515: http://code.google.com/p/lilypond/issues/detail?id=1515 -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: collision between beams and grace notes
On Mon 07 Feb 2011, 21:17 Werner LEMBERG wrote:
[git commit cfe87695]
\version 2.13.49
\header { texidoc =
The beaming algorithm should handle collisions between beams and
grace notes too.
Here is a counterexample.
}
\relative c' {
e'8[ f e \grace { f,16[ a] } e'8]
}
For the record:
This is reported as 795 and is being under discussion and development right
now, as far as i know.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly converts whole rests in 5/4 incorrectly
On Tue 04 Jan 2011, 21:55 Neil Thornock wrote: I'm not top posting. When converting a Finale file that includes measures with 5/4 time signature with whole rests, the rest gets converted with a duration of R1.. rather than R1*5/4 or R4*5. Please (in a case if this is actual still), would you provide a small example (xml file) to prove/check? -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: woodwind-diagram clarinet
On Thu 30 Dec 2010, 22:37 Markus Schnider wrote:
Hallo
Hi!
Please (if this is actual so far), would you provide a minimal example which
shows *bad* result and explain why it's bad?
version 2.13.44 (2.13.45?)
file: define-woodwind-diagrams.scm
The definitions of the keys for clarinet are for the right hand wrong:
(rh . (ees)) should be (rh . (e))
(rh . (gis)) should be (rh . (f))
(rh . (e)) should be (rh . (gis))
bass-clarinet
(rh . (f)) should be (rh . (ees)) or (rh . (dis))
For both types (normal and bass clarinet) there exists also an additional key
for the left hand - low-gis.
For the bass-clarinet there exists also 5 other keys:
low-d for the little finger of the left hand
low-d for the little finger of the right hand
low-d for the thumb of the right hand
low-cis for the thumb of the right hand
low-c for the thumb of the right hand
for more informations (images) there exisits a excellent site:
http://www.wfg.woodwind.org/clarinet/basscl_alt_1.html
thanks
I had to type followings to receive a correct image
clarinet = \relative c' {
s2
e,4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb ))
(rh . (ees)))
}_\markup e
s2.
e4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb f))
(rh . (ees)))
}_\markup e
s2.
e4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb e))
(rh . ()))
}_\markup e
s2.
e4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb e))
(rh . (gis)))
}_\markup e
s2.
f4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb ))
(rh . (gis)))
}_\markup f
s2.
f4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb f))
(rh . ()))
}_\markup f
s2.
fis4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb fis))
(rh . ()))
}_\markup fis ges_\markup ges
s2
fis4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb ))
(rh . (fis)))
}_\markup fis ges_\markup ges
s2
g4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb ))
(rh . ()))
}_\markup g
s2.
gis4^\markup {
\woodwind-diagram
#'clarinet
#'((cc . (one two three four five six))
(lh . (thumb ))
(rh . (e)))
}_\markup gis as_\markup as
}
___
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: abandoned bug reports
On Sat 05 Feb 2011, 18:39 Graham Percival wrote: Guys, I'm looking at: http://lists.gnu.org/archive/html/bug-lilypond/2011-01/threads.html I count 6 emails which have no reply. (I'm not counting automatic ((oops.. i did not count my today's replies, so i could miss something)) How did all seven people miss those emails? As for me, personally --- i figured out that i had had wrong priorities. I was starting to deal with that appeared to be simpler each time. Just to fill my 15 min with something useful. As for me --- sometimes it takes *too much* to follow threads (yes, my English is much worse* than it may appear). (btw -- today i have some spare time completely *unexpectedly*). We have a problem. We can try to fix it with technology, better documentation, different policies, and/or different organization. Any ideas? No ideas. Different people?.. ps. Looking at the CG i started to feel like the bug squad is the only squad with strictly declared responsibilities. I may be wrong, my English is bad*. pps. I will be *happy* when BugMeister tells me that BugSquad can succeed without my help. Here are some things which i hopefully can do better than others, so nothing strange that there are a *lot* of things which i definitely can do much worse than others. However i will try (sometimes,-) to be helpful here until that. * this email took some 7 or 10 minutes :O( =:O] -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond Crash on the following simple Code
2011/2/14 Dmytro O. Redchuk brownian@gmail.com:
This crashes 2.13.49 when { } is empty
\markuplines{ �}
{ c' }
It doesn't crash in 2.13.50 for me.
I have compiled 2.13.51 and it says segmentation fault with this code.
--
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: Lilypond Crash on the following simple Code
2011/2/14 Dmytro O. Redchuk brownian@gmail.com:
On Mon 14 Feb 2011, 12:47 Francisco Vila wrote:
2011/2/14 Dmytro O. Redchuk brownian@gmail.com:
This crashes 2.13.49 when { } is empty
\markuplines{ �}
{ c' }
It doesn't crash in 2.13.50 for me.
I have compiled 2.13.51 and it says segmentation fault with this code.
Which code, please?
Now i can see �} in \markuplines --- there was no anything it last email.
Can you re-post faulty code again, please?
just an empty markuplines before the music,
\markuplines { }
{ c' }
I don't know where the chinese character came from. Did I pasted by mistake?
--
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: Lilypond Crash on the following simple Code
2011/2/14 Francisco Vila paconet@gmail.com:
2011/2/14 Dmytro O. Redchuk brownian@gmail.com:
On Mon 14 Feb 2011, 12:47 Francisco Vila wrote:
2011/2/14 Dmytro O. Redchuk brownian@gmail.com:
This crashes 2.13.49 when { } is empty
\markuplines{ �}
{ c' }
It doesn't crash in 2.13.50 for me.
I have compiled 2.13.51 and it says segmentation fault with this code.
Which code, please?
Now i can see �} in \markuplines --- there was no anything it last email.
Can you re-post faulty code again, please?
just an empty markuplines before the music,
\markuplines { }
{ c' }
I don't know where the chinese character came from. Did I pasted by mistake?
No, I didn't:
http://lists.gnu.org/archive/html/bug-lilypond/2011-02/msg00264.html
--
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 1516 in lilypond: Crash with empty \markuplines
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical
New issue 1516 by brownian.box: Crash with empty \markuplines
http://code.google.com/p/lilypond/issues/detail?id=1516
http://lists.gnu.org/archive/html/bug-lilypond/2011-02/msg00263.html
\markuplines { }
{ c' }
This gives segfault.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Lilypond Crash on the following simple Code
On Mon 14 Feb 2011, 13:04 Francisco Vila wrote:
just an empty markuplines before the music,
\markuplines { }
{ c' }
I don't know where the chinese character came from. Did I pasted by
mistake?
No, I didn't:
http://lists.gnu.org/archive/html/bug-lilypond/2011-02/msg00264.html
Yes, something in a wire, sorry. And i tested with no any symbol as far as i
can remember, but something was wrong here (no segfault, it's strange).
Yes, it segfaults, i can see now.
Added as 1516:
http://code.google.com/p/lilypond/issues/detail?id=1516
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: accidentaled notes too far from the barline
2011/2/14 Janek Warchoł lemniskata.bernoull...@gmail.com:
The amount of whitespace after the barline is fixed, while it should depend
on whether the first note in the measure has an accidental or not. This
results in notes being too far from the barline, especially when there is
only one note in measure:
{ c'4 d' g' f' e'2 a' d'1 }
{ c'4 d' g' f' es'2 a' dis'1 }
Have you tried fiddling with BarLine #'space-alist? Changing the
next-note entry to use minimum-fixed-space appears to deliver the
goods:
\override Staff.BarLine #'space-alist =
#'((time-signature . (extra-space . 0.75))
(custos . (minimum-space . 2.0))
(clef . (minimum-space . 1.0))
(key-signature . (extra-space . 1.0))
(key-cancellation . (extra-space . 1.0))
(first-note . (fixed-space . 1))
(next-note . (minimum-fixed-space . 1.2))
(right-edge . (extra-space . 0.0)))
This doesn't work for the single-note case since that's altered later
using the grob property 'full-measure-extra-space (it overrides the
space-alist default set by StaffSpacing).
Cheers,
Neil
attachment: bach.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1211 in lilypond: [PATCH]Optimizations for pure-height approximations. (issue1817045)
Updates: Status: Fixed Labels: -Patch-review fixed_2_13_51 Comment #14 on issue 1211 by percival.music.ca: [PATCH]Optimizations for pure-height approximations. (issue1817045) http://code.google.com/p/lilypond/issues/detail?id=1211 Pushed. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1488 in lilypond: [PATCH]harmonics and slides (issue3590041)
Comment #4 on issue 1488 by percival.music.ca: [PATCH]harmonics and slides (issue3590041) http://code.google.com/p/lilypond/issues/detail?id=1488 New patch here: http://codereview.appspot.com/4186049/ it still needs work (doesn't compile due to Documentation/snippet/new/ issues) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1278 in lilypond: Enhancement: arrow notation for quarter-tones
Updates: Labels: -Patch-needs_work Patch-review Comment #3 on issue 1278 by percival.music.ca: Enhancement: arrow notation for quarter-tones http://code.google.com/p/lilypond/issues/detail?id=1278 New patch is ready for serious review; regtests look ok, it applies cleanly, etc. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1490 in lilypond: Page labelling fails between barlines and on \bar
Updates: Labels: Patch-review Comment #1 on issue 1490 by n.putt...@gmail.com: Page labelling fails between barlines and on \bar http://code.google.com/p/lilypond/issues/detail?id=1490 http://codereview.appspot.com/4186050/ ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1516 in lilypond: Crash with empty \markuplines
Comment #1 on issue 1516 by n.putt...@gmail.com: Crash with empty
\markuplines
http://code.google.com/p/lilypond/issues/detail?id=1516
\markuplines { } returns '(), which is valid according to markup-list? (and
its C++
equivalent, Text_interface::is_markup_list ()):
foo = \markuplines { }
#(display (markup-list? foo))
- #t
Assuming we want \markuplines { } to behave like \markup { } (i.e., produce
a \null toplevel markup), then this patch works, since it ensures a valid
Paper_score in paper-book.cc:
diff --git a/lily/parser.yy b/lily/parser.yy
index 0bb4c15..e6a7e09 100644
--- a/lily/parser.yy
+++ b/lily/parser.yy
@@ -2405,7 +2405,10 @@ full_markup_list:
| MARKUPLINES
{ PARSER-lexer_-push_markup_state (); }
markup_list {
- $$ = $3;
+ if (scm_is_pair ($3))
+ $$ = $3;
+ else
+ $$ = scm_list_1 (scm_cons (ly_lily_module_constant
(null-markup), SCM_EOL));
PARSER-lexer_-pop_state ();
}
;
It's perhaps not the most elegant solution, so if anybody can come up with
something better which doesn't cause any shift/reduce or reduce/reduce
problems I'd be interested to see it. :)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1517 in lilypond: Add dots to tocItemMarkup
Status: Accepted Owner: Labels: Type-Enhancement Priority-Medium Patch-review New issue 1517 by percival.music.ca: Add dots to tocItemMarkup http://code.google.com/p/lilypond/issues/detail?id=1517 Patch from Bertrand Bordage. http://codereview.appspot.com/4172047 Looks good to me. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1517 in lilypond: Add dots to tocItemMarkup
Updates: Labels: -Patch-review Patch-needs_work Comment #1 on issue 1517 by percival.music.ca: Add dots to tocItemMarkup http://code.google.com/p/lilypond/issues/detail?id=1517 Carl pointed out that this will only work on postscript backends, and thus more work is required. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1229 in lilypond: Notes on ledger lines with stems pointed away from the staff overlap clef and staff ends in tight layouts
Comment #13 on issue 1229 by k-ohara5...@oco.net: Notes on ledger lines with stems pointed away from the staff overlap clef and staff ends in tight layouts http://code.google.com/p/lilypond/issues/detail?id=1229 So what do people think ? Is the side-effect on lyrics good or bad? or not worth caring about ? If there is nothing sticking out of the staff on the lyrics side, then the bar-lines are spaced to make room for the lyrics. If a note or something sticks out, the bar-lines can slide past the lyric syllables, as they did in 2.12.3. My second choice for this issue would be a rule to keep clear the space between the ledger lines and the staff (plus a tiny protrusion of the bar-lines' and time-sigs' space reservation). That would have different side effects, for example, when a neighbor's accidental could fit in that space. Attachments: 1229_lyrics.png 14.1 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
