I followed the test procedures to a t, but got this error over and over:
Now processing `test.ly'
Parsing...
test.ly:2:20: error: unknown escaped string: `\notes':
\score { \notes
{ c4-( c4-) } }
test.ly:2:19: error: syntax error, unexpected STRING:
\score { \n
On 29-Sep-04, at 5:59 PM, Susan Smily wrote:
The test file worked, but I can't open other files. I tried Haydn's
op76-n6-violoncello.log, and got the attached log.
Please read the beginning of the attached log:
-
lilypond (GNU LilyPond) 2.2.5
Running lilypond-bin...
Now processing `op76-n6-viol
The test file worked, but I can't open other files. I tried Haydn's
op76-n6-violoncello.log, and got the attached log.
Thanks for your help.
S. Smily
op76-n6-violoncello.log
Description: Binary data
___
lilypond-user mailing list
[EMAIL PROTECTED]
ht
On Thursday 30 September 2004 00.00, Jeffrey Philpott wrote:
> I've got the same problem as described in the digest of 25.07.04.
>
> Using the example from Schubert doesn't seem to work for slurs, only for
> beaming.
> So exactly HOW do I start tweaking the melismaBusyProperties so that I
> can use
[EMAIL PROTECTED] writes:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> > [EMAIL PROTECTED] writes:
> >> Hi,
> >>
> >> I'm am planning on using Lilypond as a case study for a software
> >> reliability reserach project. Does anyone know:
> >
> > Interesting. Are you aware that someone else
[EMAIL PROTECTED] writes:
> Arvid Grøtting writes:
>
> >> That sounds like a job for \partcombine, see input/test/hymn.ly
> >
> > Won't that give a single stem when the voices share a note head?
>
> No, there's splitInterval just for that.
Yes, but unfortunately, that property does not work anym
I've got the same problem as described in the digest of 25.07.04.
Using the example from Schubert doesn't seem to work for slurs, only for
beaming.
So exactly HOW do I start tweaking the melismaBusyProperties so that I
can use a dotted slur and at the same time turn off the melisma?
If it's any
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>> Hi,
>>
>> I'm am planning on using Lilypond as a case study for a software
>> reliability reserach project. Does anyone know:
>
> Interesting. Are you aware that someone else did work in this area
> before?
>
> http:/
Yes, but at least in the example you sent, the \stemUp command doesn't
change anything, since you already have a \voiceOne.
/Mats
Jean-marc LEGRAND wrote:
The \stemUp is used because I have a viola da gamba part and some chords to write
at the beginning
of the score, with the upper voice \ste
The \stemUp is used because I have a viola da gamba part and some chords to write at
the beginning
of the score, with the upper voice \stemUp , the lower voice \StemDown, and the
middle part Stem
trnasparent.
What I havedone is to write \stemBoth twice. And it does work.
Why isn't it the s
The real problem is that the construct << {...} \\ {...} >>
only makes sense within ordinary staves, since it creates two new
Voice contexts.
If you want a corresponding version that works in the TabStaff
context, you have to do something like:
partitionTab = \notes {
\relative c' {
\time 3/4
If you have read computer science and know about stacks, then
it's easy to understand. I'll try to describe it without going
into that terminology.
When you do a
\override blabla #'someproperty = #'somevalue
as is done in \stemUp, you tell LilyPond to store the previous
property value in some memor
Hi all,
it seams, that there is a problem with polyphony and TabStaff context.
The notes get drawn twice in \context Staff and none in \context
TabStaff
greetings
Alexander
example:
\version "2.2.5"
partition = \notes {
\relative c' {
\time 3/4
c4 << { f d e } \\ { b c2 } >>
}
}
\s
Hi list !
Some weird behaviour under Lily 2.2 and XP.
I've just moved from Lily2.0 to 2.2, and \stemBoth doesn't seem to work the same way.
Here's my script :
tr = \markup {\musicglyph #"scripts-rcomma"}
basseI =\notes
\context Staff <<
\new Voice {\voiceOne
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> That's just one application of the part combiner.
OK, so the only problem is how to apply the part combiner to this
case, then. I haven't found out how, yet, and I have read the fine
manual in several of its incantations.
Assuming I have \sopMusic
Arvid Grøtting writes:
>> That sounds like a job for \partcombine, see input/test/hymn.ly
>
> Won't that give a single stem when the voices share a note head?
No, there's splitInterval just for that.
> And
> won't rests that exist in one voice only, be dropped?
No.
> Traditionally in SATB (and
It's very hard to guess what you have done. As can be seen at
http://lilypond.org/doc/v2.2/input/template/out-www/collated-files.html,
the template works fine as it is, so there's something related to how
you used it.
Please send a small example file if you want a more qualified answer.
/Mats
J
Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
> Robinson P. Tryon writes:
>
>> I'm typesetting a book of college songs and came across some parts
>> where two voices are on a single staff and share rests.
>
> That sounds like a job for \partcombine, see input/test/hymn.ly
Won't that give a single
Hi,
Recently I tried to use the piano dynamics template on version 2.2.5.
However, two things went wrong:
1) There is a stave (with 5 lines, clef and time signatures) in between the
two normal staves with dynamics sticking to the bottom of it. This stave is
not supposed to appear. The piece sta
Michal Seta writes:
> I've been away from Lily since the version 2.0, I think... Since then
> I changed a puter, running Mdk10 and using thac's rpm of lilypond
> 2.3.13 at the moment. Everything is working spledidly but last night I tried
> midi2ly and it barfed saying that module midi cannot
Robinson P. Tryon writes:
> I'm typesetting a book of college songs and came across some parts
> where two voices are on a single staff and share rests.
That sounds like a job for \partcombine, see input/test/hymn.ly
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music type
Hi Bert,
Thanks a lot; it all works very nicely now. I had downloaded the
program files but not, it appears, your manual. Regardless of that,
however, the solution
was embarrassingly simple. You've produced a nice, easy to install and use
utility.
One problem, though, is that it does not open
22 matches
Mail list logo