Re: tempo markings
On Sat, 2002-10-26 at 02:45, Paul Scott wrote:
Graham Percival wrote:
Actually your last two solutions sound like they have possibilities.
Possibly something from this could be added to the docs when you have
time. When I get clearer on this I'll post my solution. Of course this
also needs to work anywhere else in the score.
- define a tempopart part which looks like this:
tempopart = \notes { s1^#(note (something = 120) see-refman) }
In your parts, include both the actual part and tempopart.
\context Staff \violinpart \tempopart
In the full score, only include the \tempopart in the first staff.
this is what i generally use. however, i also put rehearsal marks if
needed, and tempo changes for the whole piece in this one. it works fine
for me, especially if i jiggle the vertical offsets of RehearsalMarks
and TextScripts.
greetings,
simon.
--
Don't be irreplaceable, if you can't be replaced, you can't be promoted.
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Lily wasn't here
How do I make ly2dvi NOT to print the Lily was here X.X.X mark?
\header{
tagline =
}
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Lily was here
How do I make ly2dvi NOT to print the Lily was here X.X.X mark? Thanks for your help, Antonio ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: tempo markings
That has possibilities and might solve another problem. I'm going to
post a question or two about vertical spacing when I get a chance. My
tempo marking is too close to the notes right now.
The padding property is your friend, for example:
\property Voice.TextScript \override #'padding = #3
- define a tempopart part which looks like this:
tempopart = \notes { s1^#(note (something = 120) see-refman) }
In your parts, include both the actual part and tempopart.
\context Staff \violinpart \tempopart
In the full score, only include the \tempopart in the first staff.
That sounds more straight forward. I'll work on that.
This is what I've always used.
We should probably add an example of this solution in
the section An Orchestral Score in the tutorial.
/Mats
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: HaraKiriStaffContext question
\context Staff = soprano
\global
\clef treble
\property Staff.instrument = Soprano
\property Staff.midiInstrument = flute
\sopranoNotes
\notes { R2.*7
\context Lyrics = sopranoLyrics
\sopranoLyrics
}
I tried that, and it did fix the haraKiriStaffContext, but it putt all
the lyrics under the system instead of under the notes.
so i instead did this:
tenorLyrics =
\context Lyrics
\lyrics {
%1
\notes { R2.*7 } %\repeat unfold 7 { _2. }
%8
}
and this works fine, although i do get a few
warning: Junking request: `Span_req'
warnings during compilation, but all the lyrics are placed in the right
place under the right notes.
thanks for the help!
Jule
On Friday, Oct 25, 2002, at 18:45 US/Eastern, Graham Percival wrote:
On Tue, 22 Oct 2002 23:44:08 -0400
Jule Slootbeek [EMAIL PROTECTED] wrote:
yeah i forgot the includes, sorry, here they are, i'm using 1.6.0 on
Mac OS X
In the future, please include *all* files necessary to compile the
example -- I had already deleted your previous email, so I had to find
dngg.ly in the web archives. In addition, don't use subdirectories
(the
\include notes/tenor.ly) when sending stuff. When I investigate
stuff, I save the ly files in my ~/tmp and then compile it. I don't
want to mess around making subdirectories.
The problem is that you have lyrics in the beginning. Comment out the
\repeat { _2.*7 } lines in your voices. In the score, do this:
(example)
\context Staff = soprano
\global
\clef treble
\property Staff.instrument = Soprano
\property Staff.midiInstrument = flute
\sopranoNotes
\notes { R2.*7
\context Lyrics = sopranoLyrics
\sopranoLyrics
}
HaraKiri now behaves properly.
One of these days I'll add a note to HaraKiri refman that empty lyrics
don't count as empty bars.
Cheers,
- Graham
Jule Slootbeek
[EMAIL PROTECTED]
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Persistent font problems
Mats, Removing the feta* files in my local directory made the dvips and ly2dvi generated files look the same. Unfortunately it didn't fix the squashed font problem. Sorry about the 16 versus 20 font size oversight. I'm usnig denemo to enter the music which defaults to 16 so I have to change it by hand to 20. The first one I generated probably did have 20, but subsequent version I forgot to change. Any other suggestions on where to look for the squashed font problem? There must be somethin peculiar about my system if noone else has this problem. Thanks. Russell. On Fri, 2002-10-25 at 07:59, Mats Bengtsson wrote: dvipslist: kdebug:search(feta-nummer8.vf) = kdebug:search(feta-nummer8.720pk) = ./feta-nummer8.720pk kdebug:search(feta16.vf) = kdebug:search(feta16.720pk) = ./feta16.720pk kdebug:search(feta-braces4.vf) = kdebug:search(feta-braces4.720pk) = ./feta-braces4.720pk Simply remove the feta* files in your working directory and everything should be fine. Apparently, you used paper16 in your file, that's why our instructions to look for feta20 didn't give any output. Strange that dvips and xdvi use different paths. xdvilist: kdebug:search(feta-braces4.vf) = kdebug:search(feta-braces4.300pk) = /var/lib/texmf/pk/cx/feta-braces4.300pk kdebug:search(feta-nummer8.vf) = kdebug:search(feta-nummer8.300pk) = /var/lib/texmf/pk/cx/feta-nummer8.300pk kdebug:search(feta16.vf) = kdebug:search(feta16.300pk) = /var/lib/texmf/pk/cx/feta16.300pk /Mats ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user -- Russell Smiley [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Persistent font problems
[EMAIL PROTECTED] writes: I hope you saw the other postings on this problem which I think answer your question. Any ideas? Still the only thing I can think of is some kind of resolution mismatch. (are you sure you removed everything, i.e. what does locate feta say?) Second, if you use ly2dvi --pdf, then the type1 fonts (.pfa) are used. They should be immune to squashing. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
