Frédéric Chiasson wrote:
Hi!
For the compiling time, I am surprised that sometimes it takes almost
a minute to compile only 3 pages of music for alto, double bass and
piano! The fastest is 30 seconds. I am using LilyPond 2.11.11 on a
MacBook Intel Core Duo with 512 Mb.
There have been bug
I'm looking at the ps output of Lilypond ('cause I'm writing a completely
unrelated program that also outputs ps) and see this:
/set-ps-scale-to-lily-scale {
lily-output-units output-scale mul
lily-output-units output-scale mul scale
} bind def
Couldn't you say
/set-ps-scale-to-
Hi!
I tried to compile with the new development version. It takes 44 seconds for
4 pages of music for alto, double bass and piano. But there is two things to
notice :
1- I am using JEdit with LilyPondTool, might add some seconds.
2- I ask for a MIDI file, which is the longest process of the piece
Hi!
For the compiling time, I am surprised that sometimes it takes almost a
minute to compile only 3 pages of music for alto, double bass and piano! The
fastest is 30 seconds. I am using LilyPond 2.11.11 on a MacBook Intel Core
Duo with 512 Mb.
For the interface, the best thing for a text entry
Hi Trevor, hi everyone,
> The following might be of interest to folks using proportional
> notation. If there's any general interest (of if Graham wants it to be
> so) then I'll retype the following as an addition to 11.3.4
> "Controlling spacing of individual systems".
Awesome!! This is exactly
Andrzej Kopec escreveu:
> I also have a usability question. I'm using lilypond-2.10.11 (linux
> executable) on intel centrino 1.4MHz with 256MB of RAM, and I cannot
> render 10 page chamber piece of music due to lack of memory. after
> 15 min I stop "Layout outputting to 'xxx.ps'" and I found outp
Dear Han Wen,
under
http://code.google.com/p/lilypond/issues/detail?id=240
I found Your comment to the bug report with rest on wrong side.
Your comment:
The voice containing the rests should have stems/stemdown set, otherwise
lily will mess up with collisions, whether they contain rests or notes.
Andrzej Kopec wrote:
I also have a usability question. I'm using lilypond-2.10.11 (linux executable)
on intel
centrino 1.4MHz with 256MB of RAM, and I cannot render 10 page chamber piece of
music due
to lack of memory. after 15 min I stop "Layout outputting to 'xxx.ps'" and I
found outputted
4
Hello, Andrzej:
your experiences with large lilypond projects [...]
and your hardware?
I recently typeset my 42-page chamber opera score (in Lilypond 2.9).
If I recall correctly, it took between 1 and 2 minutes to generate
the full score (on an Apple MacBook with 2GHz Intel Core Duo).
Hope
First of all, here's an alternative version of
your code that hopefully is somewhat closer to what you want.
Mats, this also says clashing notecolumns in the first note (and merges
them to one position) (with 2.10.11)
___
lilypond-user mailing li
Hi,
I also have a usability question. I'm using lilypond-2.10.11 (linux executable)
on intel
centrino 1.4MHz with 256MB of RAM, and I cannot render 10 page chamber piece of
music due
to lack of memory. after 15 min I stop "Layout outputting to 'xxx.ps'" and I
found outputted
4 pages of 10. If I
Hi,
The following might be of interest to folks using proportional
notation. If there's any general interest (of if Graham wants it to be
so) then I'll retype the following as an addition to 11.3.4
"Controlling spacing of individual systems".
Proportional notation gives near-complete control of
You have received a large number of answers already, but
I'm not sure how many of your original questions have really
been answered. First of all, here's an alternative version of
your code that hopefully is somewhat closer to what you want.
#(set-global-staff-size 17)
% \version "2.10.7"
Jonathan Henkelman wrote:
Upro gmail.com> writes:
I admit that not finding the function for a simple line brake was not very
smart of me. I have studied the online-manual thouroughly, but it's not easy
to find solutions there, and I haven't found them for the descripbed
problems.
Tr
Bertalan Fodor wrote:
The scan that was provided shows
two of the stem-up notes aligned. I suppose that that could be an engraving
error from the scanned piece.
It's a polyphonic Bach violin peace: they are separate voices, not chords, they
figure melodies (despite there are notes b
Bertalan Fodor wrote:
>
> > The scan that was provided shows
> > two of the stem-up notes aligned. I suppose that that could be an
> > engraving error from the scanned piece.
>
> It's a polyphonic Bach violin peace: they are separate
> voices, not chords, they figure melodies (despite there
>> I admit that not finding the function for a simple line brake was not
very
>> smart of me. I have studied the online-manual thouroughly, but it's not
easy
>> to find solutions there, and I haven't found them for the descripbed
>> problems.
>Try the PDF version as it is really easy to search.
These things happen as soon as you include some command
that can only be done within a Staff or Voice context, before
your own first \new Staff/Voice.
In this case, it's the \autoBeamOff command that causes the
problem. Just move it inside the \new Staff{...}. If you want
the setting to apply to a
On Wed, Jan 17, 2007 at 08:15:24AM +0200, Joe Neeman wrote:
> We've had a few questions about ties between voices (especially ties from
> polyphony to chords). It seems that you can get this behaviour simply by
> moving the Tie_engraver form the Voice context to the Staff context. Note
> that the T
> The scan that was provided shows
> two of the stem-up notes aligned. I suppose that that could be an engraving
> error from the scanned piece.
It's a polyphonic Bach violin peace: they are separate voices, not chords, they
figure melodies (despite there are notes between in the first noise)
Rutger Hofman cs.vu.nl> writes:
>
> But the whole point of this \voiceFive thingy is that none of the four
> notes in the first quarter should line up, and especially not the three
> notes with stem upwards.
>
> Rutger
>
I'm not sure I agree with this conclusion. The scan that was provided
Sietse Brouwer wrote:
A bunch of keywords, to help future people with this issue find this
thread:
dynamic marks in lyrics, stanza, number, stanzanumber, font,
fetaDynamic, override, set, tweak, hack, forte, mezzoforte, piano, f,
mf, p.
Instead of keywords in the email archive, why not submit
Dear all,
I'm sorry for responding so late. I've tried both Bertalan's and
Eduardo's suggestions -- they work -- and here comes the summary of
what I've learned.
If you want to indicate the dynamics (forte, mezzoforte, piano, etc.)
of a verse, then it is possible to set this mark in the "\set st
Carl D. Sorensen wrote:
Bert wrote:
Yes! And it *works* !
Rutger
voiceFive = #(context-spec-music (make-voice-props-set 4) 'Voice)
<< { \voiceOne g''4 ~ \stemDown g32[ f( es d c b a b64 )g] }
\\ { \voiceThree b4} \\ { \voiceFive d,} \\ { \voiceTwo g,}\\>>
Bert
I trie
Bert wrote:
> >>>
> >> Yes! And it *works* !
> >>
> >> Rutger
> >>
> >>
> >
> >
> voiceFive = #(context-spec-music (make-voice-props-set 4) 'Voice)
>
> << { \voiceOne g''4 ~ \stemDown g32[ f( es d c b a b64 )g] }
> \\ { \voiceThree b4} \\ { \voiceFive d,} \\ { \voiceTwo g,}\\>>
Upro escreveu:
> Hello!
>
> I have been using Lilypond some years ago, without needs for too good
> formattzig, but now I decided to try to make an edition for a major
> publisher with lilypond.
Interesting! Which one?
> (etc)
If it's really important, you could consider reserving a cut of
wh
Upro gmail.com> writes:
> I admit that not finding the function for a simple line brake was not very
> smart of me. I have studied the online-manual thouroughly, but it's not easy
> to find solutions there, and I haven't found them for the descripbed
> problems.
Try the PDF version as it is real
Rutger hotmail.com> writes:
> Is there anyone who could give me some help me with the file below?
> For some reason, Lilypond creates an unwanted clef and time signature
> (without a staff) above my setting of two voices on one staff. What did I do
> wrong?
Try moving the \autoBeamOff to inside
Hello list,
Using subdivideBeams with manual beaming, as explained
in 6.5.6 in the manual, works fine. However, using it with
automatic beaming with the LilyPond code below, results in
the attached output, which has two problems:
1) The last beam of the first measure is subdivided; a
workaround
Dear all,
Is there anyone who could give me some help me with the file below?
For some reason, Lilypond creates an unwanted clef and time signature
(without a staff) above my setting of two voices on one staff. What did I do
wrong?
Also, would you have any clue why the fermatas in the lower part
If you look at the definition of voice you will see:
voiceOne = #(context-spec-music (make-voice-props-set 0) 'Voice)
voiceTwo = #(context-spec-music (make-voice-props-set 1) 'Voice)
voiceThree =#(context-spec-music (make-voice-props-set 2) 'Voice)
voiceFour = #(context-spec-music (make-voic
31 matches
Mail list logo
