[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lilypond duet writing
From: |
Urs Liska |
Subject: |
Re: lilypond duet writing |
Date: |
Mon, 24 Apr 2017 10:18:23 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Am 24.04.2017 um 03:35 schrieb Margaret Voorhaar:
> Hi Hans,
> Thank-you very much for responding to my first efforts at learning Lilypond.
>
> I am going to take advantage of your kindness and submit my next conundrum to
> you.
>
> I have written a flute melody which is is complete at 32 bars in length. Is
> it too late to integrate a second flute part beneath this?
No, not at all.
It is one of the beauties of text-based work that you will very rarely
run into such a situation. While in a graphical program adding something
"after the fact" may indeed break things, in a text based program the
whole text is considered newly upon each compilation.
>
> I have tried following the various directives from the youtube tutorials on
> to the Lilypond manuals and cannot manage to add an extra line after the
> fact. Is this too hard for a beginner such as myself?
>
> Thank-you for taking the time to respond.
> :) margaret. Port Stanley, ON, Canada
>
> Here is a bit of the code:
>
> \version "2.18.2-1"
> % this to be added to Oogway's assent.
>
> \header {
>
> title = "Alex's Dance"
> composer = "Margaret"
>
> }
>
> \relative c''
>
> {
>
> \tempo "Lively"
> \clef "treble"
> \key d\minor
> \time 3/8
> \tempo "Lively"
>
> d8( f8 a8) | %m1
> g4( f8 | %m2
> g4 f8 | %m3
> g4 a8) | %m4
>
>
What you are doing is writing a "music expression" at the top level of
your input file. This is fine for simple use cases (like a plain melody)
but should be extended for more complex scores.
Your code will implicitly be expanded by LilyPoind to (I'm leaving out
many things):
\score {
\new Staff \relative c'' {
% your music
}
}
The first thing you can do is give the music expression a name (or:
store it as a variable:
fluteOne = \relative c'' {
% flute one music goes here
}
\score {
\new Staff \fluteOne
}
This should produce the same score as previously.
In order to add a second staff you create a second variable fluteTwo and
extend the score block to:
\score {
<<
\new Staff \fluteOne
\new Staff \fluteTwo
>>
}
The << >> tells LilyPond to treat the elements within the construct as
*parallel*, so the two new Staff elements will be placed below each other.
You should try this out and then (or before) read through
http://lilypond.org/doc/v2.18/Documentation/learning/how-lilypond-input-files-work
HTH
Urs
>
>
>
>
>
>> On Apr 10, 2017, at 4:22 PM, Hans Åberg <address@hidden> wrote:
>>
>>
>>> On 10 Apr 2017, at 00:47, Margaret Voorhaar <address@hidden> wrote:
>>> Even though it appears that I have saved my Lilypond file as a desktop pdf
>>> on my mac, my score becomes integrated with the email addresses etc when I
>>> go to send or print. Can I sent this score as an attachment, just as I do
>>> my Word Docs and photos?
>> In Mail, just write the letter, and then drop into the PDF or whatever where
>> you want it.
>>
>>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user
--
address@hidden
https://openlilylib.org
http://lilypondblog.org
- emailing a pdf, Margaret Voorhaar, 2017/04/09
- Re: emailing a pdf, David Wright, 2017/04/09
- Re: emailing a pdf, Hans Åberg, 2017/04/10
- Fwd: lilypond duet writing, Margaret Voorhaar, 2017/04/24
- Re: Fwd: lilypond duet writing, Martin Tarenskeen, 2017/04/24
- Re: Fwd: lilypond duet writing, Martin Tarenskeen, 2017/04/24
- RE: lilypond duet writing, Mark Stephen Mrotek, 2017/04/24
- Re: lilypond duet writing, Simon Albrecht, 2017/04/24