Hi
When I used the \change Staff command in a piano arrangement I'm working
on, I found it necessary to force the stem directions to avoid column
clashes. No problem. However, I've found that if both parts have a rest
at the same moment, I get error messages like this...
warning: can't resol
Mats Bengtsson wrote:
Try to use \voiceOne instead of \stemUp and \voiceTwo
instead of \stemDown. It specifies the direction not only
on stems but also on a number of other things like slurs,
ties, rests, ...
/Mats
Thanks Mats, that seems to work perfectly.
Brett
__
Easyheads appears to be broken in 2.10.12
\version "2.10.12")
\paper { ragged-right=##t}
{ \setEasyHeads c' d' e' f' }
produces a single notehead with no stem. (see attached png)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/
Graham Percival wrote:
Thanks for the report.
This worked ok in 2.11.13 -- could you test it in 2.10.13, and let me
know if the problem still exists.
Cheers,
- Graham
Nope - the output is even worse - check the attached png.
Here's the output from LP:
Parsing...
Interpreting music... [1]
Graham Percival wrote:
Brett Duncan wrote:
Nope - the output is even worse - check the attached png.
Here's the output from LP:
This means that there is an extra character somewhere. I noticed that
your example contained
\version "2.10.6")
with an extra ). Please do
In making some changes to a file I had created with LP 2.8, it
unexpectedly broke under 2.10.14.
I eventually isolated the problem to chordmode. I've since downloaded
2.11.18 for Intel Mac (I'm running OS X 10.4.8 on a MacBook Pro), but
the problem remains.
Here's a small example of what doesn
Graham Percival wrote:
Brett Duncan wrote:
I eventually isolated the problem to chordmode. I've since downloaded
2.11.18 for Intel Mac (I'm running OS X 10.4.8 on a MacBook Pro), but
the problem remains.
Sorry, I can't duplicate on my machine -- which is also 2.11.18,
10.4.8.
Graham Percival wrote:
Brett Duncan wrote:
A little more experimenting reveals a few more things - if I specify
PNG for the output instead of the default PDF, there are no errors
and the PNG image is fine.
That makes sense; it's ghostscript that's broken.
If I specify Postscri
Graham Percival wrote:
I don't know exactly what the deal is, but I've heard that lilypond
.ps files (perhaps only since 2.10?) use some features of postscript
that only very recent ghostscript versions can handle. The
ghostscript that's built into Preview is too old. That's why we
distribut
Mats Bengtsson wrote:
I looked at the .ps file that Brett sent me, and couldn't notice
anything strange
there. The problems seems somehow to be related to the Verdana TrueType
font that's used for the chord names, but I don't understand why your
Ghostscript
(which should be the one included in
Mats Bengtsson wrote:
Brett Duncan wrote:
I am completely baffled by this problem. I've checked all the
instances of the Verdana font I can find on my laptop, and they all
check out okay. Maybe there's another instance of the font somewhere
I can't find. I thought maybe the w
Graham Percival wrote:
Brett Duncan wrote:
Mats Bengtsson wrote:
Have you checked if ps2pdf calls the Ghostscript version included
with the
LilyPond distribution or any other Ghostscript version on your machine
(I don't know any details on how the LilyPond installation looks on
Graham Percival wrote:
Brett Duncan wrote:
I don't have a ~/.fonts, but there is an XML doc: ~/.fonts.conf
I do have a ~/.fontconfig - a folder with some 28 files in it, and
there is also a ~/.fonts.cache-1
Two possible ideas:
- Try removing (or renaming) those files and running lil
The following code compiles without errors, but the flat sign in the
chord name does not appear.
\version "2.11.18"
\header { title = "Whereditgo?" }
\score {
<<
\override Score.ChordName #'font-name = #"Arial"
\new ChordNames { \chordmode { aes1 }
\relative c' { c
Rune Zelder wrote:
Manual says "thirds are added to the root until it reaches the specified
number" which would be the correct thing to do.
But when specifying :13, the 11 is left out, so that the chord name printed is "9/add13" instead of "13"
And that's not all - if you enter ":13.11" to in
Peter Budny wrote:
I'm unsure how to enter the following music:
[1. ] [2. [1. ] [2.
| x x x x | x x x x | x x x x :||: x x x x | x x x x | x x x x :|| x x x x |
A
16 matches
Mail list logo
