Re: Percent repeat questions

2005-01-16 Thread Erik Sandberg
First, sorry for the long delay (the mail got lost)

On Tuesday 21 December 2004 03.23, Richard Schoeller wrote:
> I've been running into some issues with percent repeats and want to see
> if there are suggestions.
>
> If you have a line that is completely percent repeats, then
> RemoveEmptyStaffContext removes the line.  This gets me alot in ensemble
> scores where the bass and percussion are repetive and the melody parts
> are very busy.  Is there anyway to avoid this?

Thanks, added the bug as percent-repeat-harakiri.ly

A workaround is to add invisible stuff to the percent repeated bars, something 
like:

<<
  \repeat percent 10 {c4 d e f }
  \new Voice {\hideNotes \repeat unfold 10 c1}
>>

> I would like to be able to specify percent repeats but have it
> automagically unfold the measure at each new line.  This would be
> similar to chordChanges = ##t for chord names.  Is there anything like
> that?

Not that I know of. I'm quite sure it's possible, though, through some deep 
Scheme hacking.

> The final thing is a bug.  And I have not been able to find a
> workaround.  If one part has precent repeats and another part has
> measures that begin with a grace note, then the percent repeats will be
> mispositioned in the measures near the one with the grace note.  This
> can even result in a percent repeat mark at the very beginning of the
> line.

I can't find a workaround either. The bug has been added as 
percent-repeat-grace.ly. Thanks!

Erik


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Beams across repeat signs

2005-01-16 Thread Erik Sandberg
On Tuesday 11 January 2005 20.02, Erik Ronström wrote:
> According to the regression tests, LilyPond does not typeset beams
> across manual repeat signs. That is true. However, it does place beams
> across repeat-voltas, if the repeat sign is mid-bar. Is there a way to
> avoid that without using manual beaming?

Of course you can work around the bug by adding a manual repeat sign, like
\repeat volta 2 { ... }\bar ":|" ...
but that's pretty silly.

Anyways, I added the bug to CVS as auto-beam-repeat.ly. Thanks!

Erik


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Bar lines. Was: Lilypond pieces already entered

2005-01-16 Thread Erik Sandberg
On Thursday 13 January 2005 16.35, Mats Bengtsson wrote:
> Michael Kallas wrote:
> > Barcheck is really great, yes, but I've found some times it fails when it
> > shouldn't. Try for example:
> > \time 4/4
> > r4 R4*3 |
> > This fails reproduceably in 2.4.2 (or am I coding nonsense here)?
>
> As has already been pointed out by others, your example doesn't really
> make sense, since R gives you a full bar rest (or more of them). Still,
> the bar check should work, so I send a copy to the bug reporting mailing
> list.

Since multimeasure rests only make sense when they occupy full bars, lily 
automatically adds a barcheck at the start and end of each MM rest (or at 
least, it seems to be that way which looks sensible to me)

Erik


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: hidenotes bug

2005-01-16 Thread Erik Sandberg
On Sunday 16 January 2005 08.25, Graham Percival wrote:
> On 10-Jan-05, at 5:17 AM, johannes schöpfer wrote:
> > i think i found about \hideNotes and \unHideNotes.
>
> Interesting.  If you delete the \paper{} and \layout{}, then
> it compiles fine.  It gives warnings about rests and
> notes on the same stem, but it _does_ compile.
>
> Alternately, if you leave the \paper{} and \layout{} in there
> but remove the \break s, it's still fine.
>
> I guess the combination of raggedright and one bar per line
> is too much for LilyPond to handle...?
>
> (LilyPond chokes with an "abort trap" message; 2.4.2 on OSX)

I can't reproduce - It never crashes here, neither with Pedro's 2.4.2 debian 
package nor with 2.4.3 from CVS.

Could you send the lilypond --verbose output?

Erik


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: hidenotes bug

2005-01-16 Thread Graham Percival
On 10-Jan-05, at 5:17 AM, johannes schöpfer wrote:
i think i found about \hideNotes and \unHideNotes.
Interesting.  If you delete the \paper{} and \layout{}, then
it compiles fine.  It gives warnings about rests and
notes on the same stem, but it _does_ compile.
Alternately, if you leave the \paper{} and \layout{} in there
but remove the \break s, it's still fine.
I guess the combination of raggedright and one bar per line
is too much for LilyPond to handle...?
(LilyPond chokes with an "abort trap" message; 2.4.2 on OSX)
Cheers,
- Graham
\paper {
  raggedright = ##t
}
\layout {}
\relative c
{\clef bass
<< {
  c4( \hideNotes c)
  \unHideNotes c( \hideNotes c)\unHideNotes
} {
  s4 r s r
} >>
\break
<< {
  c8( \hideNotes c)
  \unHideNotes c( \hideNotes c)
  \unHideNotes c( \hideNotes c)
  \unHideNotes c( \hideNotes c)\unHideNotes
} {
  s8 r s r s r s r
} >>
\break
<<{c8 (\hideNotes c)}{s8 r}>>\unHideNotes
 <<{ c8\noBeam (\hideNotes c)}{s8 r}>>\unHideNotes
 <<{ c8\noBeam (\hideNotes c)}{s8 r}>>\unHideNotes
  <<{ c8\noBeam (\hideNotes c)}{s8 r}>>\unHideNotes
}

___
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: centralCPosition

2005-01-16 Thread Graham Percival
On 7-Jan-05, at 3:07 AM, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
centralCPosition should be middleCPosition.
Also, it would be nice if the example at the bottom of the page could
demonstrate this property somehow.
I'll try to fix it in a few days -- I'd like to be able to test this
change before
committing it, and we're still working on the OSX build.
Unless you use really strange commands, it's not much work for me to
figure out where the build breaks and
  @ignore
This case is more awkward than normal, since the LilyPond example
won't compile under 2.4.2  (it doesn't like the clef.X names)
Could somebody running 2.5.x check this example?  I've just
added the final two lines, but I don't know what kind of number
I should give to middleCPosition.  If #4 isn't good, could you figure
out what number it should be?  (#0?  #10?)
{
  \set Staff.clefGlyph = #"clefs.F"
  \set Staff.clefPosition = #2
  c'4
  \set Staff.clefGlyph = #"clefs.G"
  c'4
  \set Staff.clefGlyph = #"clefs.C"
  c'4
  \set Staff.clefOctavation = #7
  c'4
  \set Staff.clefOctavation = #0
  \set Staff.clefPosition = #0
  c'4
  \clef "bass"
  c'4
  \set Staff.middleCPosition = #4
  c'4
}
Cheers,
- Graham

___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Two questions

2005-01-16 Thread Mats Bengtsson

Dean Karns wrote:
I am running lilypond-book with LaTeX (Kile) on Linux with Fedora Core.
I have two questions:
1) In marking up a glyph from the Feta font, such as a prall or mordent,
is it possible to include a command that will cause the glyph to print
in a grey shade?
 

Not easily.
2) In text markups how do I include an "e with acute accent?" in a word
of French origin? I can access the character with \char #233, but when I
put it into a word there are spaces around it.
 

Just input the character directly in the file. However, make sure that 
your text editor
saves the file using Latin1 encoding (also called ISO8859-1 encoding).

  /Mats
 



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: hidenotes bug

2005-01-16 Thread Erik Sandberg
On Monday 10 January 2005 14.17, johannes schöpfer wrote:
> hello,
>
> i think i found about \hideNotes and \unHideNotes.
>
> i'm using lilypond 2.4.2 with slackware 10 linux.
>
>
> greetings johannes
>
>
>
> script-output is selfexplaining:

Sorry, I don't understand the problem. Can you please elaborate?

(you might want to use \new Voice for the rest voices)

Erik

> \paper {
>
>raggedright = ##t
> }
>
> \layout {}
>
> \relative c
> {\clef bass
> << {
>c4( \hideNotes c)
>\unHideNotes c( \hideNotes c)\unHideNotes
> } {
>s4 r s r
> } >>
> \break
> << {
>c8( \hideNotes c)
>\unHideNotes c( \hideNotes c)
>\unHideNotes c( \hideNotes c)
>\unHideNotes c( \hideNotes c)\unHideNotes
> } {
>s8 r s r s r s r
> } >>
>
> \break
>
> <<{c8 (\hideNotes c)}{s8 r}>>\unHideNotes
>   <<{ c8\noBeam (\hideNotes c)}{s8 r}>>\unHideNotes
>   <<{ c8\noBeam (\hideNotes c)}{s8 r}>>\unHideNotes
><<{ c8\noBeam (\hideNotes c)}{s8 r}>>\unHideNotes
>
> }
>


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Documentation error? How a prall is played.

2005-01-16 Thread Erik Sandberg
There may exist different conventions for this. However, J.S. Bach has written 
the following:
http://icking-music-archive.org/scores/bach/ornaments.jpg
which more or less looks like the explanations from the lilypond docs. So IMHO 
it's an OK definition.

Erik

On Monday 10 January 2005 10.31, Trond Aasan wrote:
> l#ornament>
>
> In example
> >
>
> Playing a prall:
>
> e'4 e32[ d e d ~ d8] c2
>
>
> Shouldn't it be something like this?
>
> e'4 e16[ f e8 ] c2
>
>
> This is the mordent, and a prall is supposed to be en inverted mordent (up
> instead of down)?
>
> g4 a b16-[ a b8] a4
>
>
> Same goes for 2.4.2 docs.
>
> --
> Trond Aasan
> 
>
> In my wee world Bill Gates cheats at cards, steals candy from children and
> pees on the toilet seat.
>
>
> ___
> 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: Fooling \partcombine in lilypond 2.4.2

2005-01-16 Thread Erik Sandberg
Thanks! Added to bug cvs as partcombine-missing-voice.

Erik

On Friday 14 January 2005 15.45, Alexandre Beneteau wrote:
> Hello,
>
> I have found a case where \partcombine does not print the second
> voice...
> Having tried a lot of combinaisons, I have founded that it is the
> conjunction of the R1 in the beginning *and* the decrescendo following
> which produce this unexpected result.
>
> Hoping this will be usefull...
> Thanks,
>
>  Alex.
>
> P.S. : Using Pedro's package of lily 2.4.2 in debian unstable.
>
> code snippet :
>
> \include "italiano.ly"
>
> partA = \transpose do re' {\relative do' {
>   R1
>   do1 \> ~
>   do \!
>   do
> }}
> partB = \transpose do re' {\relative do {
>   R1
>   la'1 \> ~
>   la \!
>   la
>  }}
>
> \score {
>   \partcombine \partA \partB
> }
>
>
>
> ___
> 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