lilypond-user
[Top][All Lists]
Advanced

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

Re: How to work with large orchestral1 projects


From: Noeck
Subject: Re: How to work with large orchestral1 projects
Date: Sun, 21 Feb 2016 10:29:30 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1

Hi Carl-Henrik,

the snippets can be quite helpful:
http://www.lilypond.org/doc/v2.19/Documentation/snippets
and online search if you can guess the name.

> 1) The title. Is there a sensibale way to adjust font/fontsize and
> placement of the title? (this is most likely an easy thing, but it would
> be nice to hear how you guys deal with it)

If it is just about the font size, this is probably the easiest way:
\header {
  title = \markup \abs-fontsize #30 "ABC"
}
If you want to create your own style of the header, here you go:
http://www.lilypond.org/doc/v2.19/Documentation/notation/creating-titles-headers-and-footers
http://www.lilypond.org/doc/v2.19/Documentation/snippets/titles

> 2) This is the wierdest thing. Double up of time, clef and tempo, what
> is on earth have i done wrong? 

\grace s8 as Urs pointed out. That's indeed ugly.

> 3) I want the beams to and from rests, with stemlets, like
> so: http://i.imgur.com/62wXphp.png 

This can help you:
http://www.lilypond.org/doc/v2.19/Documentation/snippets/rhythms#rhythms-stemlets

{
  \override Stem.stemlet-length = 0.75
  r8[ gis']
}

However, this requires manual beaming with [ ], IIUC.

> 4) I want the beams to stretch 4 8ths and break if necessary. My puny
> attempt thus far looks bonkers. 

You explicitly put the beaming there:
https://github.com/chbuschmann/Nordlandsk/blob/master/stemmer/fiolin%201.ly#L7
 a16.[\f gis32] a16. b32

This means the a is beamed with gis32 and then the beam has to stop. So
exactly what you get. For a longer beam, you can do either
{
  \time 2/4
  a16.[\f gis32 a16. b32 c8-. < b gis' e' >]\fz |  % manual with [ ]
  % or
  \set Staff.beatStructure = #'(2)                 % beams last 2 beats
  a16.\f gis32 a16. b32 c8-. < b gis' e' >\fz
}
% see http://www.lilypond.org/doc/v2.19/Documentation/notation/beams

> 5) I tried making a scordatura using a snippet from LRS. Perhaps my eyes
> are playing tricks with me, the font size seems off, to large?

You have a \large here which makes the instrument name larger than the
others:
https://github.com/chbuschmann/Nordlandsk/blob/master/main.ly#L37
Just remove it.

> %%General questions
> 6) I also wonder about parts creation. How do i set it up? 

see 9)

> 7) When i did the Sibelius engraving, i came to the conclution that A3
> was the proper page format. Once i've entered my music, will lilypond
> scale the score to fill the entire page, like it does with A4, OR; do i
> need to make adjustments to font and/or staff sizes?

It will fill the paper format you specify while keeping the font and
staff sizes as you set them (or default 20).
\paper {
  #(set-paper-size "a3")
}
If that's what you intend, you can also scale the global staff size by
sqrt(2) to 28.28, of course.

> 8) I've searched far and wide but have not found a way to make
> large/huge time signatures. This is what i really want (from
> Adler): http://i.imgur.com/Jn971jP.png 

There are people on this list who know how to do that. I have seen it
before, but I couldn't find it so quickly.

> 9) Where to i place system wide events, like 
> repetitions, 

As far as I know, repeats must go into each part (voice). However, for
rehearsal marks and
> time and
> tempo?
it is recommended to put them in to a global variable with spacers:
global  = { \time 2/4 s1*8 \mark "A" }

Then you can come back to the parts creation:
You start a new file for each part, let's say the violin I, with a
\score block and you put your global variable and your music variable
(\fiolinEn) of that instrument into it.

\include "stemmer/fiolin 1.ly"
\score {
  \new Staff << \global \fiolinEn >>
}


You ask your questions very clearly. That makes it easy to answer. I
hope this was helpful. Please don't hesitate to ask back in case of
questions.

Cheers,
Joram



reply via email to

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