2009/3/6 David Kastrup :
>
> Ping? Anybody out here?
Yeah, I'm right here.
Added as http://code.google.com/p/lilypond/issues/detail?id=762
(when I see that a bug report is more than 2 lines long, I tend to
easily be discouraged ;-)
Regards,
Valentin
__
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Low
New issue 762 by v.villenave: Ambitus engraver should be smarter about
accidentals
http://code.google.com/p/lilypond/issues/detail?id=762
New report from David:
The ambitus engraver will, when determining the ambitus i
Ping? Anybody out here?
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Low
New issue 761 by v.villenave: Enhancement: Voice contexts should be kept
alive
http://code.google.com/p/lilypond/issues/detail?id=761
\version "2.12.2"
%The dontDie is necessary to keep the voices alive.
dontDie = {
Updates:
Status: Accepted
Labels: Type-Enhancement Priority-Low
Comment #2 on issue 760 by v.villenave: Feature request: polyphony shortcut
could be better
http://code.google.com/p/lilypond/issues/detail?id=760
Now, a much better example from James:
\version "2.12.2"
musOne
2009/3/6 James E. Bailey
> I'm of the opinion anything Mats does is better than anything I do. The goal
> is that <<{}\\{}>> doesn't create two new voice contexts, but rather keeps
> the first one active, and just creates a second new voice context. Remember
> that the goal here is that one vo
El 06.03.2009, a las 13:54, Valentin Villenave escribió:
2009/3/6 James E. Bailey :
\version "2.12.2"
musOne = \context Voice = upperOne \relative f' { f4 <<{g a}\\{e d}
>>f }
musTwo = \context Voice = upperTwo \relative f' { f4 <<{\voiceOne g
a}\context Voice = lowerTwo {\voiceTwo e d}>>\o
2009/3/6 James E. Bailey :
> \version "2.12.2"
> musOne = \context Voice = upperOne \relative f' { f4 <<{g a}\\{e d}>>f }
> musTwo = \context Voice = upperTwo \relative f' { f4 <<{\voiceOne g
> a}\context Voice = lowerTwo {\voiceTwo e d}>>\oneVoice f }
> lyr = \lyricmode { This text splits here. }
Comment #1 on issue 760 by v.villenave: Feature request: polyphony shortcut
could be better
http://code.google.com/p/lilypond/issues/detail?id=760
Here's an example from James involving lyrics and voice names. I'm not sure
how this
could be handled automatically though.
\version "2.12.2"
2009/3/6 :
> New issue 760 by jameselihubailey: Feature request: polyphony shortcut could
> be better
> http://code.google.com/p/lilypond/issues/detail?id=760
Hi James (assuming that it's your pseudo),
could you provide us with a minimal example of a situation where << \\
>> screws up while << {
Updates:
Status: Fixed
Labels: fixed_2_13_0
Comment #2 on issue 729 by v.villenave: MIDI #47 instrument's name is
incorrect
http://code.google.com/p/lilypond/issues/detail?id=729
Thanks Andrew, I'll verify it as soon as the next GUB build is out.
--
You received this message
Status: New
Owner:
New issue 760 by jameselihubailey: Feature request: polyphony shortcut
could be better
http://code.google.com/p/lilypond/issues/detail?id=760
The shortcut for multiple voices could be better. It would be nice if the
shorthand, <<{}\\{}>> were equivalent to <<{\voiceOne
I just noticed that convert-ly does not work from the lilypond.app
menu item in osx 10.4. I have python installed. convert-ly works from
the terminal, but here are the problems with the menu item.
• If I update the convert-ly file to be: env python, lilypond does
not find python. That's not
13 matches
Mail list logo
