On 5/8/19 11:30 AM, Federico Bruni wrote:
It seems your fontforge installation is not found.
Does it occur when you run configure?
Which distro are you using?
I have encountered this error when Fontforge was built from git-master
rather than from a release tarball.
__
I think the issue here is that changing the associatedVoice happens one step
later than expected. I could be wrong, but I don't think this is obviously
documented.
I've been bitten by this several times. Usually a workaround is possible,
namely by moving the associatedVoice change back one sylla
On 10/24/07, Daniel Johnson <[EMAIL PROTECTED]> wrote:
>
> I'll parallel-install GUB and see if that changes things.
Indeed, GUB solves the problem. I'm guessing it's not a GUILE issue; I
reverted my local GUILE to 1.8.2 (GUB's version) and still got the "cr
Bizarre. I can reproduce this anytime on my Linux box at home, but I just
tried it on Windows here at work and it ran without a hitch.
The only other thing I can think of is that Lilypond on my home Gentoo box
is built from source (why? because in the past I've occasionally had reason
to apply pa
\version "2.11.34"
%{
Certain border cases in spacing with lyrics result in "cruelty to springs"
programming errors, and subsequent disregard for right margins, in some
cases
overflowing the edge of the page.
In the example below, the lyric syllables "bla" or "verylongtext" will
result
in correct
José Luis Cruz wrote:
Thank you Matt, I didn't knew the syntax change. For the record:
\override TextSpanner #'edge-text = #'("rall " . "")
now woud be:
\override TextSpanner #'bound-details #'left #'text = \markup {
\italic "rall" }
cheers,
The documentation regarding this syntax change needs
Sorry, the previous example should have been:
% BEGIN
\version "2.11.17"
spaceWide = {
\overrideProperty #"Score.NonMusicalPaperColumn"
#'line-break-system-details
#'((alignment-offsets . ( 0 -80 )))
}
\score {
<<
\new Staff { \spaceWide c''1 | \break \spaceWide c''1 | c''1 | \b
When using absolute spacing and moving the Mark_engraver from the Score
context to the Staff context (as described in section 8.1.4 of the Fine
Manual), the mark is applied to the wrong staff. In the following
example, the rehearsal mark should appear on the lower staff, but in the
2.11.17 version
In the following snippet, you'd expect the oboe to be nine times as loud
as the bassoon, but in fact they are the same volume.
%%% BEGIN
\version "2.11.16"
\score {
<<
\new Staff {
\set Staff.midiInstrument = "oboe"
\set Staff.midiMinimumVolume = #0.9
\set Staff.midiMaximum
If afterGrace is used in a voice to which a Lyrics context is attached,
the lyrics become misaligned, and the syllable after the grace notes
overprints the syllable before the grace notes.
\version "2.10.13"
\paper{ ragged-right = ##t }
\score
{
<<
\new Staff { \new Voice = "myVoice" { \afte
In section 10.3.1 of the Fine Manual (for both 2.10 and 2.11), we see the
following:
To remove dynamics from the MIDI output, insert the following lines in the
\midi{} section.
\midi {
...
\context {
\Voice
\remove "Dynamic_performer"
\remove "Span_dynamic_performer"
}
}
Span_d
> Thanks, added as
> http://code.google.com/p/lilypond/issues/detail?id=247
>
> I assume your earlier report about one of the Doc examples was the same
> issue.
>
> Cheers,
> - Graham
No, actually that was a separate issue. It's a minor nitpick, but Lilypond
claims that it can't find a voice to as
Lyrics attached to a Voice are center-aligned if attached to a single
note, and left-aligned if attached to a melisma. Lyrics attached to a
Devnull context, however, are always left-aligned. The following example
illustrates:
\version "2.10.11"
text = \lyricmode { foo bar baz quux }
notes = { c'4
On 2.10.11, running Documentation/user/lily-d5894a905a.ly results in these
warnings:
lily-d5894a905a.ly:1324:19: warning: Lyric syllable does not have note.
Use \lyricsto or associatedVoice.
lyr = \lyricmode {
I like my cat! }
lily-d5894a905a.ly:1324:21: warning: Lyric syllable
I've been having problems with LyricExtenders under Ties on 2.10.11. The
attached example shows one of the LyricExtenders not extending far
enough. This in fact is a fragment of a larger piece, and in the context
of the larger piece none of the LyricExtenders extends further than a
couple milli
When a key change occurs at a line break, in many (most?) editions the
key is cancelled at the end of the first line, and not at the beginning
of the subsequent line. According to the Fine Manual, this is supposed
to be the default behaviour (I'm looking at
lilypond-internals/KeyCancellation.h
In 2.10.10, Dynamic_performer and Span_dynamic_performer have been
replaced by New_dynamic_performer, but convert-ly does not make a change
or issue a warning. I've been using them in my midi block, and now I
will have to remember to manually change them.
Historically, I've had to use them in
When the Instrument_name_engraver is added to a ChoirStaff, GrandStaff
or StaffGroup, and that composite-staff contains child Lyrics contexts,
those Lyric contexts inherit the instrumentName (and
shortInstrumentName) from the parent context; so, for example, if a
ChoirStaff contains two Lyrics
>
> Thanks Joe,
>
> Also anyone using an on-the-fly expression that expects #first-page to be
> true on the first page will also fail if they set first-page-number
> themselves. Because #first-page is determined by comparing the page
> counter
> value to first-page-number. If the user is asking f
Han-Wen Nienhuys wrote:
Mark Dewey schreef:
Hello,
With Lilypond 2.9.7, for Windows (I'm using Windows 2000), I'm having
some
trouble with \rest. These issues did not occur with Lilypond 2.6.5
for Windows.
In certain contexts, b'4\rest (I don't think the duration matters),
in the
treble c
Francisco Vila wrote:
Hi all,
It's rather uncomfortable to have to close a PDF that is being viewed, to let
LilyPond to write on it;
I used to think of Adobe Reader about writing documents read-only, is this true?
Windows XP on a Pentium III machine.
Thanks
Unfortunately this is a problem
Thies Albrecht wrote:
Hi Daniel!
Just a technical issue...
Since this bug did not exist in late versions of Lilypond 2.7.x,
this is a regression.
As far as I understand it, a regression is something that has been fixed
before and now misbehaves again. This doesn't fit for the stem-leng
This is a Gentoo box with Lilypond built from source. Since this bug
did not exist in late versions of Lilypond 2.7.x, this is a
regression. I have not yet gone backwards through the 2.7 branch to
see when the bug was introduced, but I am planning on doing so this week.
Hmm. On further inves
Thies Albrecht wrote:
This results in incorrect beamed stem-lengths as seen the attached
image. If you comment out the Y-extent override, the problem goes
away. If you comment out only the minimum-Y-extent, the output
changes slightly but the problem remains. This has been confirmed in
2.8.
%%% BEGIN LILYPOND CODE %%%
\version "2.8.0"
\paper {
indent = 0\in
raggedright = ##t
}
theNotes = \relative c' {
f8[ g f e] c[ d] aes8[ b] | g'8([ aeh g fis]) c8([ d c b])
}
\score {
\new Voice = theVoice { \theNotes }
\layout {
\context {
\Staff
\ov
Dennis O'Toole wrote:
After upgrading to 2.8.1, I notice that the .pdf files produced are
considerable larger, on the order of about 5 to 10 times the size
formerly produced. This has a detrimental effect on my ability to
store and distribute, so much that I have to back level to 2.6
to use.
Andrzej Kopec wrote:
>And one more question:
>how to make lilypond without documentation? It seems compiling chokes on
>documentation...
>
>thnx in advance,
>/ak/
>
>
Try "make" or "make default" instead of "make all" to build sans
documentation.
For a successful build including documentation
Andrzej Kopec wrote:
Hello,
During compilation I get this error:
font-config-scheme.cc: In function `void display_fontset(FcFontSet*)':
font-config-scheme.cc:32: error: invalid conversion from `FcChar8*' to `const
char*'
How can I fix that?
You have two options:
1. Upgrade GCC to 3.4
Monk Pantleimon wrote:
Previous bug reports involving shape note have to do with alignment. This
report is different. In trying the Sacred Harp system in Lilypad 2.7, I found
that the shapes do not properly correspond to the scale degrees. Properly,
fa (1&4)= triangle
sol (2&5)= round
la (3&6
Mats Bengtsson wrote:
If you use the absolutely latest development ("unstable") version of
LilyPond, you should be prepared for changes that are possibly not
always well documented. However, in this case, convert-ly should
convert your code to something that works in 2.7.17 (actually, as
far as
Yesterday I upgraded from 2.7.14 to 2.7.17, and I immediately noticed
that when trying to set fixed staff-spacing for a staff group, \set
Staff.minimumVerticalExtent = ##f no longer seems to do anything.
Consider the following example:
%%% BEGIN LILYPOND CODE %%%
\version "2.7.17"
text = \ly
clemens heppner wrote:
hi,
i installed lilypond 2.6.4 on gentoo by using the 2.2.x buildscript but i think
thats not the problem.
Try using the ebuild which can be found here:
http://bugs.gentoo.org/show_bug.cgi?id=97574
___
bug-lilypond mailing li
Instrument_name_engraver has a problem calculating the correct Y-extent
to which it applies, when it is applied to a staff-group rather than a
single staff, and the bottom staff has lyrics attached to it. It
calculates the Y-extent as being from the top staff to the bottom of the
lyrics on the
Behavior also confirmed in latest 2.7 CVS
Fairchild wrote:
Daniel -
With 2.4.6 your code gives 15 on the first line and 20 on the second.
Bug in 2.6.3?
- Bruce
-Original Message-
From: Daniel Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 29, 2005
Hans Aberg wrote:
>
> The whole layout, in pseudo-code, is
> \size 1\italic "To Elaine Shaffer"
> \size 4\bold "Suite Modale"
> \size 0\normal "Duration ..."\size 2\bold "For Flute and Piano"
> \size 3\bold
> "FLUTE"
Graham Percival wrote:
>
> On 9-Jul-05, at 9:42 PM, Daniel Johnson wrote:
>
>> The proper English spelling is "eccentricity".
>
>
> Thanks, fixed in CVS.
> - Graham
>
This is not just a documentation issue. The misspelling also exists in
the following f
Graham Percival wrote:
>
> On 11-Jul-05, at 5:19 PM, Daniel Johnson wrote:
>
>> This is another LaTeX leftover documentation bug in section 7.3.2:
>>
>> \lyricmode { He said: ``Let my peo ple go'' }
>>
>> should be using curly double-quotes in
This is another LaTeX leftover documentation bug in section 7.3.2:
\lyricmode { He said: ``Let my peo ple go'' }
should be using curly double-quotes instead of back- and forward-quotes.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists
Not to be nit-picky...
In lilypond-internals/slur_002dinterface.html, we see the following:
|excentricity| (number)
How asymmetrical to make a slur. Positive means move the center to
the right.
The proper English spelling is "eccentricity".
--Daniel
||
Your attachment(s) got stripped off, but I think I know what the issue
is, since I've faced it myself.
When you introduce polyphony via the << { c4( b c2) } \\ { a2( g4 a) }
>> method (just to give a simple example), two new voices (named "1" and
"2") are created. Therefore lyrics attached to the
I built 2.6.0 on my Gentoo box using a home-built ebuild script, which
behind the scenes does the following:
./configure --prefix=/usr
make
prefix=/usr datadir=/usr/share infodir=/usr/share/info
localstatedir=/var/lib mandir=/usr/share/man sysconfdir=/etc
lilypond_datadir=/usr/share/lilypond
local
Daniel Johnson wrote:
>It worked fine once
>I explicitly created Lyrics contexts
>
s/Lyrics/Voice/g
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
I think I encountered this a couple weeks back too. It worked fine once
I explicitly created Lyrics contexts and assigned them to
explicitly-created Staff contexts which were then assigned to the
ChoirStaff. At the time I didn't experiment further because it Just
Worked(TM).
It would be helpful
"It's not a bug, it's a feature"
documented here:
http://www.lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Hiding-staves.html
\override Score.RemoveEmptyVerticalGroup #'remove-first = ##t
Bertalan Fodor wrote:
> %BUG: RemoveEmptyStaffContext doesn't remove staff from the first sytem
I've noticed that when I have a long markup associated with a note, and
a short markup associated with a space occupying the same beat as the
note, the short markup is aligned along the center X-axis of the longer
markup. I first noticed this with the piano centered-dynamics template,
but I've nar
In the file stepmake/stepmake/c-rules.make there is a line that looks
like this:
$(FLEX) -Cfe -p -p -o$@ $<
Change it to this:
$(FLEX) -l -Cfe -p -p -o$@ $<
Then start configure all over again. (The -l flag puts flex into
lex-compatibility mode.)
--Daniel
Tim Hoffmann wrote:
> Hi,
>
> I just
I get an entirely different error, one that was discussed on this list
in February if I am reading things correctly.
cd ./out-www; texi2dvi --batch lilypond.texi
This is e-TeX, Version 3.141592-2.2 (Web2C 7.5.4)
---! /usr/share/texmf-var/web2c/etex.fmt was written by pdfetex
(Fatal format file er
I had the same problem. From what I've read, the flex API has changed
since 2.5.4a. Here's what I did to fix it:
sed -i -e 's:\$\(FLEX\) :\$\(FLEX\) -l :' stepmake/stepmake/c-rules.make
The "-l" flag tells flex to behave like old-school lex. It seems like
the configure script should take care
Hi Han-Wen --
Actually, I'm building my own ESP Ghostscript on Gentoo. I've enabled
the @PNGDEVS@ in Ghostscript's Makefile.in, and for the most part ps2png
is now happy, but when making web for 2.5.16, it chokes on
lily-1812551792.ly (having already successfully done ps2png on a number
of pre
Hi all--
When using the centered dynamics described in Sec. 3.3.4 of the manual,
I've discovered that attaching the dynamic to a beat that has a text
script also attached causes the dynamic to shift to the horizontal
center of the text script. I've attached the output. (Actually, I had
to jum
.5.10.
--d
David Bobroff wrote:
Well, on your advice earlier I upgraded to mftrace 1.1.5 when you told
me I needed potrace or autotrace. So, no, I don't think mftrace 1.1.5
fixes this.
On Mon, 2005-03-07 at 17:10 -0800, Daniel Johnson wrote:
I've heard that mftrace-1.1.5 may fix this.
I've heard that mftrace-1.1.5 may fix this. Is this correct?
David Bobroff wrote:
I've got version 2.5.14 up and running (with the exception of the emacs
mode issue I posted to the user list) and I found something odd. In
this example:
\version "2.5.14"
\score{
\relative c{
\time
Hi --
I am running a fully-up-to-date Gentoo box, with texinfo 4.8. I am
getting the following error when I try to make web:
Compiling ./out-www/NEWS.texi...
LANG= makeinfo --enable-encoding -I ./out-www
--output=out-www/NEWS.html
--css-include=/var/tmp/portage/lilypond-2.5.12/work/lilypond-2
I'm getting the following error when trying to make web for Lilypond
2.5.10 on a fully-up-to-date Gentoo system. It seems that lilypond is
choking on one of the example files. I notice that a number of other
people here are using 2.5.10, so obviously there's a workaround somehow.
--Daniel
===
54 matches
Mail list logo
