Issue 429 in lilypond: new accidental style: teaching

2008-10-01 Thread codesite-noreply
Issue 429: new accidental style: teaching http://code.google.com/p/lilypond/issues/detail?id=429 Comment #4 by john.mandereau: IMHO it deserves an item in NEWS. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You m

Issue 690 in lilypond: Beams and stems disappear when using RemoveEmpltyStaffContext in a PianoStaff

2008-10-01 Thread codesite-noreply
Issue 690: Beams and stems disappear when using RemoveEmpltyStaffContext in a PianoStaff http://code.google.com/p/lilypond/issues/detail?id=690 Comment #1 by v.villenave: May be related to Issue 487. -- You received this message because you are listed in the owner or CC fields of this issue,

Issue 487 in lilypond: stems of beamed notes too long before staff change

2008-10-01 Thread codesite-noreply
Issue 487: stems of beamed notes too long before staff change http://code.google.com/p/lilypond/issues/detail?id=487 Comment #5 by v.villenave: A possibly related problem is in Issue 690. -- You received this message because you are listed in the owner or CC fields of this issue, or because yo

Re: problems with RemoveEmptyStaffContext in PianoStaff

2008-10-01 Thread Neil Puttock
2008/10/1 Valentin Villenave <[EMAIL PROTECTED]>: > 2008/10/1 Mark Polesky <[EMAIL PROTECTED]>: >> What's going on here? Are these known bugs? >> (see attached png for description) > > Wow, crazy! Added as http://code.google.com/p/lilypond/issues/detail?id=690 Only the second issue is dependent on

Re: problems with RemoveEmptyStaffContext in PianoStaff

2008-10-01 Thread Valentin Villenave
2008/10/1 Mark Polesky <[EMAIL PROTECTED]>: > What's going on here? Are these known bugs? > (see attached png for description) Wow, crazy! Added as http://code.google.com/p/lilypond/issues/detail?id=690 (there's also another issue related to PianoStaff and RemoveEmpty on http://code.google.com/p/

Issue 690 in lilypond: Beams and stems disappear when using RemoveEmpltyStaffContext in a PianoStaff

2008-10-01 Thread codesite-noreply
Issue 690: Beams and stems disappear when using RemoveEmpltyStaffContext in a PianoStaff http://code.google.com/p/lilypond/issues/detail?id=690 New issue report by v.villenave: % Beams are irregularly printed at the end of the bars (see picture); % then beams and stems completely disappear abov

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-01 Thread Alexander Kobel
Valentin Villenave wrote: > [...] > The ultimate enhancement would be that when you type \tempo "Andante" > LilyPond would recognize it and attribute a default Andante tempo to > the MIDI rendering... but maybe that's science-fiction. > [...] I guess this would neither be necessary nor good. There

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-01 Thread Valentin Villenave
2008/10/1 Thies Albrecht <[EMAIL PROTECTED]>: > Once a tempo indication dur = count is explicitly set, it will be displayed > even though you just indicate e.g. \tempo "Allegro". A simple workaround > would be to use \once \set Score.tempoHideNote = ##t everytime you just want > the textual tem

Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-01 Thread Thies Albrecht
> I'm not top posting Hi everybody! Using the new tempo mark function I get the following bug: Once a tempo indication dur = count is explicitly set, it will be displayed even though you just indicate e.g. \tempo "Allegro". A simple workaround would be to use \once \set Score.tempoHideNote = ##