Re: changing the midi instrument; broken
On Sunday 27 August 2006 07:26, Graham Percival wrote: Ted Walther wrote: The documentation of lyrics has got me befuddled on the notion of contexts, as I haven't seen anywhere it clearly says what I can do in lyricsmode that I can't do in lyricsto, although the documentation does state that there is a difference. Perhaps the complete read-through of the manual will clear it up. If you figure it out, let me know. I don't use vocal music, so I've barely touched that section. I'm happy for corrections, though. In short: \lyricmode is just a marker that says the following input characters should be interpreted as lyrics, rather than notes. \lyricsto is a function, which aligns lyrics to notes. So in \lyricsto you need a voice to align lyrics to, while in \lyricmode you need to specify the duration of each syllable manually. So: You always want to use lyricsto, but if you want to store a line of lyrics in a variable, use lyricmode and then use lyricsto to align that variable to music. -- Erik ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
On Sun, 27 Aug 2006, Mats Bengtsson wrote:
Some further clarifications below.
...
However, as Erik says below, if you want to store the lyrics into a variable,
you have to do
mylyrics = \lyricmode { Here is my ly -- rics }
and then \lyricsto ... \mylyrics
Still remains the question why at all you would want to store the lyrics
into a variable.
Possible answer: Because you want to reuse the same lyrics at multiple
places in the score.
Greetings,
Juergen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
Juergen Reuter wrote:
On Sun, 27 Aug 2006, Mats Bengtsson wrote:
Some further clarifications below.
...
However, as Erik says below, if you want to store the lyrics into a
variable, you have to do
mylyrics = \lyricmode { Here is my ly -- rics }
and then \lyricsto ... \mylyrics
Still remains the question why at all you would want to store the
lyrics into a variable.
Possible answer: Because you want to reuse the same lyrics at multiple
places in the score.
Right! There are often repeated phrases in lyrics.
Also I usually have the notes and words in a separate file from the file
that specifies the part or score.
Paul Scott
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
Ted Walther wrote: The lilypond manual is so good, and appears so complete, that I forgot I was still in Unix land. Burn! That was harsh. I'm going to save this for .sig material. :) On a serious note... In Windows, there is an immense amount of repetition, which saves people from hunting through the documentation. Each help topic assumes the user knows nothing, and tells them what they need to complete the task at hand. I need to bite the bullet and read the whole manual straight through, which I will try to do today. I agree with this analysis (but I'm still committed to doing it the unix way). If you're reading the manual through, please look at the 2.9 manual. I've greatly expanded the general knowledge chapters in the beginning; if we need to clarify this issue, it would probably be in those chapters. The documentation of lyrics has got me befuddled on the notion of contexts, as I haven't seen anywhere it clearly says what I can do in lyricsmode that I can't do in lyricsto, although the documentation does state that there is a difference. Perhaps the complete read-through of the manual will clear it up. If you figure it out, let me know. I don't use vocal music, so I've barely touched that section. I'm happy for corrections, though. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
Quoting Donald Axel [EMAIL PROTECTED]:
Is it
= #oboe
or is it
= oboe
Both work equally well (at least in versions 2.8 and later).
/Mats
On Thu, 24 Aug 2006 14:47:33 +0200
Mats Bengtsson [EMAIL PROTECTED] wrote:
\new Staff {
\time 3/4
\key d \major
\clef treble
\set Staff.midiInstrument = #oboe
That worked. Thank you Mats! If that isn't in the documentation on the
website, it would be helpful to put it in.
documentation
of midiInstrument does say:
\set Staff.midiInstrument = glockenspiel
...notes...
--
http://d-axel.dk/ -- Donald Axel, Consultant -- [EMAIL PROTECTED]
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
Graham Percival wrote:
Ted Walther wrote:
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
Just as any other property setting that applies to a certain Staff, you
have to do the setting within the Staff context, for example:
\new Staff {
\time 3/4
\key d \major
\clef treble
\set Staff.midiInstrument = #oboe
That worked. Thank you Mats! If that isn't in the documentation on the
website, it would be helpful to put it in.
Please see
http://lilypond.org/web/devel/participating/documentation-adding
I think the problem here was the general knowledge of how to set
properties,
which certainly is described in the manual, but probably not in the
parts of the
manual which you read the first time. In my opinion, we cannot keep
repeating
the same information over and over in the manual. Also, the current
documentation
of midiInstrument does say:
\set Staff.midiInstrument = glockenspiel
...notes...
which at least implicitly indicates that the setting should be done just in
connection with the actual notes, not anywhere else in the file.
However, Ted is probably the best one to judge why it was hard to find this
information and propose how the documentation can be made even clearer.
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
changing the midi instrument; broken
I am running Debian unstable, with lilypond 2.6.3 for typesetting, timidity 2.13.2 to play midi files, and freepats 20060219 to provide the midi patchsets. I notice in the manual it says the patch set has to be named exactly, with no variance in case allowed. So I have been pasting in different instrument strings from the manual, trying to get something other than grand piano. I have not had any fortune. Does anyone else have a similar setup to mine, and have they succeeded in making a midi file that does not come out using the grand piano? Is this a lilypond bug or should I harass the timidity and freepats maintainers? I am using the following line: \set Staff.midiInstrument = #oboe I have tried it in the top level, and inside a \score section. It makes no difference; the resulting midi file always uses the default grand piano. You can see the input file I am using here: http://reactor-core.org/~djw/jerusalem.ly Ted -- It's not true unless it makes you laugh, but you don't understand it until it makes you weep. Eukleia: Ted Walther Address: 5690 Pioneer Ave, Burnaby, BC V5H2X6 (Canada) Contact: 604-430-4973 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
Quoting Ted Walther [EMAIL PROTECTED]:
I am running Debian unstable, with lilypond 2.6.3 for typesetting,
timidity 2.13.2 to play midi files, and freepats 20060219 to provide the
midi patchsets.
I recommend you to upgrade to the latest stable version, 2.8. The
installation package available for download at www.lilypond.org should
work without any problems on a Debian system, just as well as other
Linux systems. In addition to a number of new features, the manual has
also been improved significantly (actually, the one for the latest
development version is even better and is relevant also for version
2.8).
I notice in the manual it says the patch set has to be named exactly,
with no variance in case allowed. So I have been pasting in different
instrument strings from the manual, trying to get something other than
grand piano. I have not had any fortune.
Does anyone else have a similar setup to mine, and have they succeeded
in making a midi file that does not come out using the grand piano? Is
this a lilypond bug or should I harass the timidity and freepats
maintainers?
I am using the following line:
\set Staff.midiInstrument = #oboe
I have tried it in the top level, and inside a \score section. It makes
no difference; the resulting midi file always uses the default grand
piano.
Just as any other property setting that applies to a certain Staff, you
have to do the setting within the Staff context, for example:
\new Staff {
\time 3/4
\key d \major
\clef treble
\set Staff.midiInstrument = #oboe
...
}
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
\set Staff.midiInstrument = #oboe
I have tried it in the top level, and inside a \score section. It
makes no difference; the resulting midi file always uses the default
grand piano.
Just as any other property setting that applies to a certain Staff, you
have to do the setting within the Staff context, for example:
\new Staff {
\time 3/4
\key d \major
\clef treble
\set Staff.midiInstrument = #oboe
That worked. Thank you Mats! If that isn't in the documentation on the
website, it would be helpful to put it in.
Is there a Debian-format repository where I can install the latest
stable version of lilypond using apt-get?
Ted
--
It's not true unless it makes you laugh,
but you don't understand it until it makes you weep.
Eukleia: Ted Walther
Address: 5690 Pioneer Ave, Burnaby, BC V5H2X6 (Canada)
Contact: 604-430-4973
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
Ted Walther wrote: Is there a Debian-format repository where I can install the latest stable version of lilypond using apt-get? I don't believe anyone is packaging LilyPond for Debian. As you probably the latest Debian package is 2.6.3. The GUB's work fine even if there may be some redundancy in download and libraries with what's already on you machine. Paul Scott ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: changing the midi instrument; broken
Ted Walther wrote:
On Wed, Aug 23, 2006 at 08:50:31PM +0200, Mats Bengtsson wrote:
Just as any other property setting that applies to a certain Staff, you
have to do the setting within the Staff context, for example:
\new Staff {
\time 3/4
\key d \major
\clef treble
\set Staff.midiInstrument = #oboe
That worked. Thank you Mats! If that isn't in the documentation on the
website, it would be helpful to put it in.
Please see
http://lilypond.org/web/devel/participating/documentation-adding
Cheers,
- Graham (hey, I live about 5 minutes away from you! I didn't think
there were other lilypond users in Burnaby. :)
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
