Re: multiple markups when combining voices on single staff
Simple! Just make sure that the music and the dynamics belong
to the same Voice context. In your example, this is easiest
done by replacing \new Staff with \new Voice.
(If you start a Staff context with a << ...>>, a new Voice
context will be created for each line within that \simultaneous.)
Mats
Graham Percival wrote:
On Mon, 06 Oct 2003 13:05:04 +0200
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
For dynamic markings, it may be more convenient to define them
separately from the music, so you can choose when to include them:
dynamicsA = \notes{ s1 \f \skip 1*10 s1 \pp ...}
How do you handle collisions when you attempt this?
music=\notes{ g4 g }
dynamics=\notes{s4\mp s4\ff}
\score{ \new Staff <<
\music
\dynamics
>>
}
Cheers,
- Graham
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
ugly lyrics with 2.0.1 on Windows
I'm getting the lyrics in what looks like (monospaced) Courier, but spaced like the usual variable-width (Computer Modern?) text fonts. Needless to say, this doesn't look good. This is with 2.0.1 on Cygwin. Any ideas? -- Arvid ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: ugly lyrics with 2.0.1 on Windows
Did you do anything special in your file, such as including paper16.ly or setting any Lyrics related properties? Mats Arvid Grøtting wrote: I'm getting the lyrics in what looks like (monospaced) Courier, but spaced like the usual variable-width (Computer Modern?) text fonts. Needless to say, this doesn't look good. This is with 2.0.1 on Cygwin. Any ideas? -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: ugly lyrics with 2.0.1 on Windows
Mats Bengtsson <[EMAIL PROTECTED]> writes: > Did you do anything special in your file, such as including > paper16.ly or setting any Lyrics related properties? I have paper16.ly included, yes. Shouldn't that work? Without paper16, I do indeed get a better font, but in return I can only fit one system on a page, which is a bit suboptimal for this piece. paper19 fails as always, paper13 is too small and has the wrong font, paper11 idem, while paper23 and paper26 work (but are a bit on the large side). -- Arvid ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: ugly lyrics with 2.0.1 on Windows
Mats Bengtsson <[EMAIL PROTECTED]> writes: > One possible workaround is to install the tetex-base package Yes, that works. Thanks for the swift reply! -- Arvid ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
How to set properties? Was: rehearsal marks conflict with bar numbers
For years, I have thought of writing a short introduction to the
art of setting properties in LilyPond. Here comes a first attempt.
Feel free to use it as a draft for a section in the manual if you
find it useful.
What You Need to Know About Property Settings
=
=
The default behaviour of LilyPond can be modified by setting
different properties. There are different types of properties
and the syntax is slightly different depending on the type
of property. Also, there are several different ways to set
a property.
Different ways of setting a property
Here, we describe briefly the syntax for the different methods to
set a property. We show the syntax for setting an object property,
but the same idea applies to context properties, as will be described
below.
* Setting a property that only applies to the next note (or the next
whatever):
\once \property contextname.objectname \set #'propname = #value
For example, if you want the next note head to be diamond shaped, do
\once \property Voice.NoteHead \set #'style = #'diamond
* Setting a property that applies from now on:
\property contextname.objectname \set #'propname = #value
The 'contextname' describes the scope of the setting. If you say
\property Score..., then the settings applies to all contexts of
the score, if you say \property Staff..., then it applies to the
current Staff context and all contexts within it (but not to other
Staff contexts), and so on.
For example, to make all coming slurs in the current stave dashed, do
\property Staff.Slur \set #'dashed = #1
When you use the \set command, the current value will be
overwritten. If, instead, you say
\property contextname.objectname \override #'propname = #value
LilyPond will remember the old value and you can go back
to the previous value by doing
\property contextname.objectname \revert #'propname
* Setting a property that applies to a complete score:
If you want to set a property that applies to a complete score,
then it's often most convenient to set a property in the
\paper{...} definition. For property settings of objects
that are created before the first note, this may also be
the only way (well, see \applycontext below) to set the
property.
\score{
...
\paper{
...
\translator{
\ScoreContext
objectname \set #'propname = #value
...
}
}
}
What happens here, is that you actually change the definition of
how your contexts should behave. The \ScoreContext is an
identifier that contains the default definition of how what a
Score context should do. If you only say \translator{\ScoreContext},
you will tell LilyPond to use exactly this definition as soon as
it creates a Score context. When adding lines in the \translator{...},
you modify this behaviour. (Note that the \ScoreContext identifier
itself will not be changed, though, so if you want to make more
modifications, you have to do them within the same \translator{...}
block.)
All properties of a context are inherited to all contexts created
within it, so setting properties for the \Score context means that
it will be applied also to all other contexts (unless they are
explicitly set differently within the definition of some other
context). So, normally you can do all the settings as described
above, but if you specifically have to do a property setting at
the Voice context level, you could do
\translator{
\VoiceContext
...
}
In the syntax example above, we have placed the \paper{...}
definition within a \score{...}, but if it is placed outside
the \score{...}, it will apply to all subsequent \score{...}
blocks within the file.
* Advanced techniques for property settings:
Normally, a property has to be set before the actual object
it applies to is created. If you know the Scheme programming
language, you can modify an already existing object using
the \applyoutput function. See the documentation of \applyoutput
and the "generic-output-property.ly" example in the Regression
Test document.
Different types of properties
=
There are basically three types of properties:
- Music properties
- Context properties
- Object properties
The music objects and music properties are used in the input part
of LilyPond to store the information of the input files. As a
normal user, you will almost never have to fiddle with these directly.
The context properties describe how the different contexts should
work when translating your input to graphical objects in the output
layout.
The object properties describe exactly how each graphical object
should be typeset.
Above, we described how to set object properties. The syntax for
setting context properties is very similar:
\property contextname.propname = #value
For example, to set the instrument name of the current stave, do
\property Staff.instrument = #"Clarinet"
and to tell LilyPond to print a key signature every time
time the clef
Re: Help with fonts
Good!
However, I checked the contents of the lilypond-2.0.1-1.i386.rpm
file available at lilypond.org today and it seems to be newer than
your failing files ("%%CreationDate: Tue Sep 30 11:34:53 2003" in the
header of the feta13.pfa file, whereas yours was from Sep 29). Maybe it
was corrected after you downloaded your copy.
Mats
Robert de Vries wrote:
On Wednesday 08 October 2003 17:23, Mats Bengtsson wrote:
There's something strange with the feta13.pfa that's embedded in the
your Postscript file. Unfortunately, I'm not fluent enough in Postscript
to realize what the problem is. You mentioned in your first email that
you had installed the "2.0.1 redhat version as made available from the
download page". I can't see any RedHat 2.0.1, so exactly what .rpm file
did you download? Have you tried any other of the .rpm files?
I downloaded the one compiled for fedora (Severn/test2).
As it seems that you find the package suspect, I have rebuilt the lilypond
2.0.1 from the tarball, and lo and behold, no more funny stuff! It works.
It seems that the fedora package has been incorrectly built.
I hereby offer my rpm packages for RedHat 9 on my web site.
http://www.xs4all.nl/~rhdv/music/index.html
Robert
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Help with fonts
[EMAIL PROTECTED] writes:
> Good!
>
> However, I checked the contents of the lilypond-2.0.1-1.i386.rpm
> file available at lilypond.org today and it seems to be newer than
> your failing files ("%%CreationDate: Tue Sep 30 11:34:53 2003" in the
> header of the feta13.pfa file, whereas yours was from Sep 29). Maybe it
> was corrected after you downloaded your copy.
>
There was a shortlived fluke rpm with empty fonts, due to upgrade
problems at my side. (I replaced the file.)
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: I need support :)
> In MS Windows, default the abc.ly file evoke the Cygwin bash; > unfortunately > it dosen't work that way, at least it's lilypond abc.ly . Why? The default action on double click is to run lilypond and launch Acrobat. > I would rather it open in an editor - I prefer UltraEdit. Should we change the default association to Notepad or Wordpad or something? Bert ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: I need support :)
Currently, both actions (edit and process) are defined for .ly files, so if you right-click on the file you get an option to open it in an editor. The only question is which one should be the default "open" command. I definitely vote for the current solution since you typically will process the file several times during one editing session, so the processing will be the more common task. Mats Bertalan Fodor wrote: In MS Windows, default the abc.ly file evoke the Cygwin bash; unfortunately it dosen't work that way, at least it's lilypond abc.ly . Why? The default action on double click is to run lilypond and launch Acrobat. I would rather it open in an editor - I prefer UltraEdit. Should we change the default association to Notepad or Wordpad or something? Bert ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: I need support :)
Bertalan Fodor writes: >> I would rather it open in an editor - I prefer UltraEdit. > > Should we change the default association to Notepad or Wordpad or something? Now we bind to notepad, but we could bind to whatever editing of (.ly made earlier) or .txt or .bat files is already bound to. People with fancy editors probably set those first. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: (Artificial) harmonics
On Tuesday 07 October 2003 05:31 pm, Maarten Boasson wrote:
> I am newcomer to Lilypond, and I like what I see - which to date is
> only very little.
> Almost immediately I ran into a problem: artificial harmonics (cello
> music; the problem is the same for all string instruments, of
> course).
The problem is, but not the solutions.
Wouldn't it be far easier to dedicate a different voice to harmonics?
> ---
> \score {
> \notes
> \new Staff { << { \property Voice.NoteHead \set #'style =
> #'harmonic g'} \\ {c'4} >> }
> }
>
> Note very obvious, nor short to type, but this is the idea
> ---
> This indeed works. But, I don't think the solution is worthy of
> Lilypond: the noteheads are really just a little too small and the
> entry is much more cumbersome than necessary, I would think.
> For an example, see the attached extract from S. Saens' 3rd violin
> concerto: it is clear that the diamond-shaped heads actually cross
> the staff lines when the note is between the lines!
>
> My desire would be to have a syntax like the following (but not
> necessarily this; anything else that fits better with the Lilypond
> style is fine, of course):
>
> c\ahfor artificial harmonics, in which case Lilypond would
> automatically create the two noteheads that represent this in printed
> music: the lower, regular note at the pitch specified, and an open,
> diamond shaped one a fourth above it (see attached); for the very
> rare case that a different interval is used,
Not rare at all. Thanks for the code. daveA
--
Br`er Fox told Br`er Rabbit that the Tar Baby had dissed him, and Fox
made a
dummy out of tar and put him in Rabbit's path. When the Tar Baby
failed to
return a civil greeting, Rabbit punched him with a right, a left, both
feet and
butted him with his forehead. Along came Br`er Fox who saw that he was
thoroughly "stuck up". Br`er Fox is much smarter than Br`er Rabbit,
and in
spite of all Rabbit's pleas for help, no one is going to unstick him
and throw
him in the briar patch, so now Br`er Fox is liesurely eating Rabbit's
liver.
D. Raleigh Arnold dra@ http://www.openguitar.com [EMAIL PROTECTED]
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: relative question
On Wednesday 08 October 2003 05:06 pm, Aaron wrote: > sorry about the previous post with the weird subject,(a mixup with my > email client) I am reposting with my original subject. > Aaron > > Hi all, > > I rememeber reading about a change to \relative. I opened the news > section of the docs and this is what I saw. > > I just can't make heads or tails out of it, could someone explain > this for me?? If I understand it correctly, it is relative in the order read rather than the order to be output. This makes it easier to type and human-read, and also far easier to make a utility external to lilypond which would convert relative to absolute, so I like it. daveA -- Br`er Fox told Br`er Rabbit that the Tar Baby had dissed him, and Fox made a dummy out of tar and put him in Rabbit's path. When the Tar Baby failed to return a civil greeting, Rabbit punched him with a right, a left, both feet and butted him with his forehead. Along came Br`er Fox who saw that he was thoroughly "stuck up". Br`er Fox is much smarter than Br`er Rabbit, and in spite of all Rabbit's pleas for help, no one is going to unstick him and throw him in the briar patch, so now Br`er Fox is liesurely eating Rabbit's liver. D. Raleigh Arnold dra@ http://www.openguitar.com [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: I need support :)
However, if the editor that you bring it up in is emacs, then you might always go to emacs and then do the processing from inside emacs. Thus never doing the processing from explorer or the desktop. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mats Bengtsson Sent: Thursday, October 09, 2003 10:26 AM To: [EMAIL PROTECTED] Subject: Re: I need support :) Currently, both actions (edit and process) are defined for .ly files, so if you right-click on the file you get an option to open it in an editor. The only question is which one should be the default "open" command. I definitely vote for the current solution since you typically will process the file several times during one editing session, so the processing will be the more common task. Mats Bertalan Fodor wrote: >>In MS Windows, default the abc.ly file evoke the Cygwin bash; >>unfortunately >>it dosen't work that way, at least it's lilypond abc.ly . > > > Why? The default action on double click is to run lilypond and launch > Acrobat. > > >>I would rather it open in an editor - I prefer UltraEdit. > > > Should we change the default association to Notepad or Wordpad or > something? > > Bert > > > > ___ > Lilypond-user mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: relative question
dOes this mean that relative mode in infact notated the same but means something different, or the notation of it is different??? The new way is infact what I thought relative mode was when I read it originally. Aaron ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Newbie: Emacs: Lily mode
What is the steps to do, to can use Emacs for the Lilypond code (I use XEmacs21). Thanks for advance. Bernard ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie: Emacs: Lily mode
Bernard Meylan wrote: What is the steps to do, to can use Emacs for the Lilypond code (I use XEmacs21). What platform? With Debian GNU/Linux just install the LilyPond package and open a .ly file. Paul Scott ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: ugly lyrics with 2.0.1 on Windows
The problem turns out to be that the tetex-tiny package does not
include all font files needed by LilyPond. Especially, it doesn't
include: cmr{5,6,7,8}.pfb, cmti{5,6}.pfb, cmtt{5,6,7,8,17}.pfb,
cmcsc8.pfb and cmss{5,6,7,8,9,10,12,14,17}.pfb.
The Lilypond package actually includes a few cm*.pfa font files,
but in the list above, I have only mentioned those Type1 font
files that are missing both in tetex-tiny and lilypond at the
moment, but are mentioned in scm/font.scm.
One possible workaround is to install the tetex-base package
(tetex-tiny is a minimal subset of tetex-base). However, that
package is fairly large so it would be better if tetex-tiny
was extended to include all the necessary font files.
I'm sending a copy of this request to the cygwin mailing list.
/Mats
Arvid Grøtting wrote:
Mats Bengtsson <[EMAIL PROTECTED]> writes:
Did you do anything special in your file, such as including
paper16.ly or setting any Lyrics related properties?
I have paper16.ly included, yes. Shouldn't that work?
Without paper16, I do indeed get a better font, but in return I can
only fit one system on a page, which is a bit suboptimal for this
piece.
paper19 fails as always, paper13 is too small and has the wrong font,
paper11 idem, while paper23 and paper26 work (but are a bit on the
large side).
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
