headers
Annette Giesbrecht | 1 Apr 2006 05:02
Picon
Favicon

Lyrics do not appear on the beige box when playing with Winamp.

I am using Lilypond 2.91.1  and I have noticed that in the examples that show 
the lyrics, the lyric box containing the 'A b c D" or whatever does not 
appear. What does appear is LilyPond 2.91.1, then generated by, and  the date 
the file was created. The date the file was created is put down twice.
Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 1 Apr 2006 14:08
Picon

cuenote clash


I've marked the bug report as `important' because a manual correction
is quite difficult (I don't know whether it is possible at all).

    Werner

======================================================================

% important
% wl <at> gnu.org

\version "2.9.0"

\header { texidoc = "
Cue notes clash with the main voice if starting at the same note.
Reason is that the horizontal offset for such notes doesn't take into
account the main voice's size.

On the other hand, if an offset for the main voice is necessary, it is
too big, for exactly the same reason.
" }

\paper {
  ragged-right = ##t
}

\addquote foo \relative c' {
  f8 g a b c2 |
  c8 b a g f2 |
}
(Continue reading)

Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 2 Apr 2006 07:34
Picon

serious problems with mutual cues

% severe
% wl <at> gnu.org

\version "2.9.0"

\header { texidoc = "
This report exhibits two serious bugs.

. The mutual inclusion of cues have worked in earlier versions.  It is
  now broken again.

. A staff starting with a \cueDuring is typeset in cue size.
" }

\paper {
  ragged-right = ##t
}

foo = \relative c' {
  f8 g a b c2 |
  \cueDuring #"qbar" #UP { R1 } |
}
\addquote "qfoo" { \foo }

bar = \relative c'' {
  \cueDuring "qfoo" #DOWN { R1 } |
  c8 b a g f2 |
}
\addquote "qbar" { \bar }
(Continue reading)

Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 2 Apr 2006 07:45
Picon

\killCues not documented


The function \killCues, quite important for full scores with automatic
part extraction, isn't documented.

    Werner
Permalink | Reply | 0 comments |
headers
Paul Scott | 2 Apr 2006 09:04

2.8.0: fermatas forced above text markup

2.8.1 and 2.8.0 at least on Debian sid:  The following results in the 
fermata above the text even if I pad the text.

\version "2.8.0"

{ c''2 d''4\fermata^\markup{ Text } e''4\fermata }

Paul Scott
Permalink | Reply | 2 comments |
headers
Paul Scott | 2 Apr 2006 09:37

2.8.0: bar number default places number in previous bar

\version "2.8.0"

{  
  \override Score.BarNumber #'break-visibility = #end-of-line-invisible
  \set Score.barNumberVisibility = #(every-nth-bar-number-visible 1)
  \set Score.currentBarNumber = #100
  c''1 b'' c'' d''
  \override Score.BarNumber #'direction = #1
  d''
  \override Score.BarNumber #'direction = #0
  e''\fermata
  \override Score.BarNumber #'direction = #-1
  d''
  a''
}

places bar numbers before the relevant bar.

Paul Scott
Permalink | Reply | 0 comments |
headers
Paul Scott | 2 Apr 2006 09:58

bar number direction doumentation inconsistent


The 2.8.0 documentation:
    http://lilypond.org/doc/v2.8/Documentation/user/lilypond-internals.html#BarNumber
    says

|direction| (direction):
    |1|

    Up or down, left or right?

The new reader wouldn't know that 1 was UP and -1 was DOWN and 0 was in 
the middle.  Also LEFT and RIGHT are the same as DOWN and UP, respectively.

I was hoping LEFT might help with the current default position bug.

Paul Scott
Permalink | Reply | 1 comment |
headers
Mats Bengtsson | 2 Apr 2006 12:26
Picon
Picon
Favicon

Re: 2.8.0: fermatas forced above text markup

I think this is the intended behaviour. If you want a fermata above the 
text, you could use
d''^\markup{\center-align { \musicglyph #"scripts.ufermata" Text }}
Another possibility is to fiddle with the script-priority property, see 
Sect. "Articulation", which also explains why this is the default 
behaviour.

   /Mats

Quoting Paul Scott <waterhorse <at> ultrasw.com>:

> 2.8.1 and 2.8.0 at least on Debian sid:  The following results in the 
> fermata above the text even if I pad the text.
>
> \version "2.8.0"
>
> { c''2 d''4\fermata^\markup{ Text } e''4\fermata }
>
> Paul Scott
>
>
>
> _______________________________________________
> bug-lilypond mailing list
> bug-lilypond <at> gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
Permalink | Reply | 1 comment |
headers
Mats Bengtsson | 2 Apr 2006 12:51
Picon
Picon
Favicon

Re: solid line for textspanner?

I would rather say that it's a bug that you don't get a continuous line 
if you use
     \override TextSpanner #'style = #'line

The documentation of the line-interface and the implementation
agree with what's written below, but several grobs, such as
VoiceFollower and Glissando have style set to 'line, even though
the implementation only cares about the style property if it's set
to 'dotted-line. Also, the example text-spanner.ly in Tips and Tricks
sets the style property so that you get the impression that the setting 
actually matters.

   /Mats

Quoting Graham Percival <gpermus <at> gmail.com>:

> On 31-Mar-06, at 8:03 PM, Christopher Ellis wrote:
>
>> \override TextSpanner #'dash-fraction = #'()
>>
>> this works for me.
>
> Thanks, I've added this to the manual.
>
> Cheers,
> - Graham
>
>
>
> _______________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dave K. | 2 Apr 2006 16:19
Picon

default placement of fermatas correct?

{

<g' b' c'' e''>^\fermata

}

Places the fermata above the stem, instead of the highest note? Is
this the correct behavior?
Permalink | Reply | 0 comments |

Gmane