lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: header


From: Mark Stephen Mrotek
Subject: RE: header
Date: Thu, 25 Jul 2013 13:25:25 -0700

Urs, Wim, Eluze, Mr. Bruni:

 

Thank you for increasing my knowledge and enjoyment of Lilypond.

 

Outline I should use:

 

% for first movement

rightone = { }

leftone = { }

% for second movement

righttwo = { }

lefttwo = { }

% for third movement

rightthree = { }

leftthree = { }

\book {

                \header { }

\scoreone { }

\scoretwo { }

\scorethree { }

                }

Mark

From: address@hidden [mailto:address@hidden On Behalf Of Urs Liska
Sent: Thursday, July 25, 2013 12:56 PM
To: address@hidden
Subject: Re: header

 

Am 25.07.2013 21:50, schrieb Mark Stephen Mrotek:

Wim,
 
 
 
Thank you for the correction. It works with a single movement ( 1mvmt.ly ).
When I add the second movement ( 2mvmt.ly ) an error message appears
relating to the variable "right."
 
I have tried moving variables of the second movement to different locations.
No success.
 
 
 
Should I enter the notation directly without using variables?

No, that would be a bad idea.
But you have to define _all_ variables as top-level expressions.
The right and left variables of the second movement are inside \book { } again.
I think you'll have to create all four variables outside the book and name them like rightOne etc.

HTH
Urs

 
 
 
 
Mark
 
 
 
From: Wim van Dommelen [mailto:address@hidden] 
Sent: Thursday, July 25, 2013 10:37 AM
To: Mark Stephen Mrotek
Cc: 'Federico Bruni'; 'lilypond-user Mailinglist'
Subject: Re: header
 
 
 
You placed the \book on top, but it should only encompass the \score
sections and what belonds there, so AFTER the variable definition \left and
\right.
 
 
 
Regards,
 
Wim.
 
 
 
 
 
 
 
 
 
On 25 Jul 2013, at 19:00 , Mark Stephen Mrotek wrote:
 
 
 
 
 
Mr. Bruni,
 
 
 
Thank you for your response and recommendation. It encourages me to request
further assistance from you.
 
 
 
From the example you suggest, I see this file structure:
 
 
 
                \book {
 
                                \score {
 
                                                { R1 }
 
                                                \header {  }
 
                                                }
 
                                \score {
 
                                                { R1 }
 
                                                \ header { }
 
                                                }
 
                                }
 
 
 
Using this format I wrote a simple code ( Book.ly ) with desired headers. An
error message appears,
 
"error: syntax error, unexpected STRING right = \relative c'' {."
 
If I remove the "\book" the file ( NoBook.ly ) compiles accurately.
 
 
 
Where is my error?
 
 
 
Thank you for your kind attention.
 
 
 
Mark
 
 
 
From: Federico Bruni [mailto:address@hidden] 
Sent: Wednesday, July 24, 2013 10:51 PM
To: Mark Stephen Mrotek
Cc: lilypond-user Mailinglist
Subject: Re: header
 
 
 
2013/7/25 Mark Stephen Mrotek <address@hidden>
 
Hello:
 
 
 
A three movement piece has the following in the \header: title, composer,
dedication, and opus.
 
 
 
The "opus" appears at the beginning of the second and third movements. How
can I eliminate them?
 
 
 
Thank you.
 
 
 
 
 
 
 
If each movement is in a separate \score block and the \header is in the
(implicit?) \book block, you can put this header inside the \score block of
second and third movement:
 
 
 
\header {
 
  opus =  ##f
 
}
 
 
 
Not tested, just an idea taken from the second example here:
 
http://lilypond.org/doc/v2.17/Documentation/notation/creating-titles-headers
-and-footers
 
 
 
<Book.ly><NoBook.ly>
 
_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user
 
 
 
 




_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user

 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]