Re: Chord Symbol fonts

[Thomas Scharkowski]

Two examples:

\override ChordNames.ChordName.font-family = #'roman

or

\override ChordNames.ChordName.font-name = "Comic Sans MS"


 Original-Nachricht 


how does one change the fonts for the chord symbols?

(I am finding lots of info on the general font setting, but not this, in
particular)



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Mozart Requiem, help needed

[Urs Liska]

Am 08.11.2014 01:25, schrieb Karl Hammar:


Urs Liska:

Am 07.11.2014 21:29, schrieb k...@aspodata.se:

Urs:

Am 07.11.2014 13:59, schrieb k...@aspodata.se:

...

Also I wounder how to make the source available so you can make your
own edition with your own preferences, and I've tried to separate
content from presentataion. That work is incomplete. I looked at
http://lilypondblog.org/ and Urs has some ideas wich I havn't been
able to digest it yet. Anyone intereseted in theese kind of problems,
and how to apply it to this music ?

If you tell me what kind of ideas you are referring to I may give some
hints. No chance joining the project, though, sorry.

__The 1st problem is: Paper sizes and margins

I use A4 or a little smaller format I call choirbook (size taken from
a Bärenreiter choirbook) suitable to be printed on A3, folded,
stapled and cut to size. And could possible envision making pocket
scores to be included with recordings. In other parts of the world
there is different paper preferences.

Changing papersizes/margins directly influences ones decision about
\break's and staff size.

This could be accomplished if one could use lilypond like

   lilypond my_paper_block.ily --ly_code "#(set-global-staff-size 14)" \
   my_page_breaks.ily my_prefs.ily the_music.ily satb_score.ly \
   -o the_music.pdf

i.e. a solution would be to make lilypond work on on the fly
concatenation of files and code. But lilypond arguments does not work
that way. One could make a "preprocessor" to handle that, but I'm
woundering if that that there is a better way to do it.

I'm not fully looking through it, but I see several approaches:

a)
you can pass an include file through the command line.
That's probably how I would approach this: Write all possible style
information in a number of style files and use the include file you
provide through the command line to choose appropriate ones for the
intended target.

  Don't seem to work:
$ cat II.ly
\version "2.19.0"
%{
\header {
   title = "Kyrie"
   %subtitle = ""
   composer = "W.A. Mozart"
}
%}
\include "score_glb.ily"
\include "II.ily"
\include "score_ps.ily"
\include "score_midi.ily"
$

  commenting score_glb away in II.ly and running works:

$ lilypond  -o zz --ps -dinclude-settings=score_glb.ily II.ly

  commenting away II.ily too, don't:

$ lilypond  -o zz --ps -dinclude-settings=score_glb.ily 
-dinclude-settings=II.ily II.ly
GNU LilyPond 2.19.13
Processing `II.ly'
Parsing...
II.ily:80:3: error: unknown escaped string: `\midi_sop'
...
score_ps.ily:14:5: warning: cannot find Voice `Vbas'

 
 \lyricsto Vbas \Lbas

Preprocessing graphical objects...
Interpreting music...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `zz.ps'...
fatal error: failed files: "II.ly"
$

The problem seem that you can include-settings for one file only _or_
that you cannot use settings from the first one in the second -
\midi_sop is defined in score_glb.ily and used in II.ily.


No, your set-up is not what I meant.
See the attached files, compile document.ly and -dinclude either one.ily 
or two.ily.

I think it's self-explanatory, otherwise please ask again.




b)
If you can make your alternative versions controllable by tags you can
benefit from the new command line options with which you can pass a list
of tags to keep or to remove through the command line.
I'm not sure if that enhancement is already in the latest release or if
it will only be in the next one, though.

I'll check that, would be useful.


c)
You can test for commandline options in the code ( with
#(ly:get-option)) and choose your layout according to the presence or
absence of certain options. You can use arbitrary options (e.g.
-dchoirbook-layout) and test for them. LilyPond will issue a warning
about the unknown option but it will work nevertheless.

 From reading the usage.pdf I got the impression it was only for the
specified (on p.4-8) variables, but it seems to work, thought I get a
warning:

$ cat a.ly
\version "2.19.0"

#(define aa (ly:get-option 'sz))
#(define bb (ly:get-option 'backend))
#(display "\naa = <")
#(display aa)
#(display ">\nbb = <")
#(display bb)
#(display ">")
$ lilypond -dsz=tt -dbackend=ps a.ly
GNU LilyPond 2.19.13
warning: no such internal option: sz
Processing `a.ly'
Parsing...
aa = 
bb = 
Success: compilation successfully completed
$

///

And to set the staff-size it works (with a warning):

$ cat a.ly
\version "2.19.0"

#(set-global-staff-size (ly:get-option 'sz))

\relative f { c'4 c c c }
$ lilypond -dsz=12 a.ly
GNU LilyPond 2.19.13
warning: no such internal option: sz
...

Great, thanks, though the warning seems a little misplaced,
perhaps one could append something to
scheme-options-definitions defined in scm/lily.scm, but it is probably
too late when my .ly is looked at.


Yes, that's a nice feature. I used that initially when implementing the 
layout control modes in Frescobaldi but realized that it should be 
changed when 

broken build of 2.16.2 (git 11cdcc31caf00b9b4931bcda846e14fdfddcfd41)

[Knut Petersen]

I tried to rebuild lilypond 2.16.2 (git 
11cdcc31caf00b9b4931bcda846e14fdfddcfd41), but make doc fails:


/home/knut/git/lily/build/scripts/build/out/run-and-check "cd ./out-www; texi2pdf -I ./out-www -I 
/home/knut/git/lily/build/Documentation/out -I /home/knut/git/lily/Documentation -I 
/home/knut/git/lily/Documentation  essay.texi < /dev/null" "essay.texi2pdf.log"

Please check the logfile essay.texi2pdf.log for errors

make[2]: *** [out-www/essay.pdf] Error 1
make[2]: Leaving directory `/home/knut/git/lily/build/Documentation'
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/knut/git/lily/build'
make: *** [doc-stage-1] Fehler 2

./build/Documentation/essay.texi2pdf.log:
===


This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/TeX Live for SUSE 
Linux)
 restricted \write18 enabled.
entering extended mode
(./essay.texi (/home/knut/git/lily/tex/texinfo.tex
Loading texinfo [version 2012-07-03.16@LP]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texmf/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.) (./essay.aux)
(/home/knut/git/lily/tex/txi-en.tex) (./macros.texi (./version.texi)
(./common-macros.texi{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}{/home/
knut/git/lily/build/tex/./out-www/lilypond.map})) [1] (./essay.toc) [-1]
(./essay.toc) (./essay.toc) (./essay/engraving.texi Chapter 1  [1] <./pictures/baer-suite1-fullpage-hires.png> [2] <./pictures/henle-suite1-
fullpage-hires.png> [3] <./pictures/hader-slaan.png (PNG copy)> <./pictures/bae
r-flat-gray.png> <./pictures/henle-flat-gray.png> [4]  (./69/lily-48fd0d15-systems.texi ) (./25/lily-28e6051e-systems.texi ) [5] <./pictures/baer-ledger.png (PNG
copy)> <./pictures/lily-ledger.pnglibpng error: IDAT: invalid distance too far 
back

!pdfTeX error: pdfetex (file ./pictures/lily-ledger.png): libpng: internal erro
r
 ==> Fatal error occurred, no output PDF file produced!
/usr/bin/texi2dvi: pdfetex exited with bad status, quitting.






___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: broken build of 2.16.2 (git 11cdcc31caf00b9b4931bcda846e14fdfddcfd41)

[Knut Petersen]

On 08.11.2014 13:58, Knut Petersen wrote:

I tried to rebuild lilypond 2.16.2 (git 
11cdcc31caf00b9b4931bcda846e14fdfddcfd41), but make doc fails:


/home/knut/git/lily/build/scripts/build/out/run-and-check "cd ./out-www; texi2pdf -I ./out-www -I 
/home/knut/git/lily/build/Documentation/out -I /home/knut/git/lily/Documentation -I 
/home/knut/git/lily/Documentation  essay.texi < /dev/null" "essay.texi2pdf.log"

Please check the logfile essay.texi2pdf.log for errors

make[2]: *** [out-www/essay.pdf] Error 1
make[2]: Leaving directory `/home/knut/git/lily/build/Documentation'
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory `/home/knut/git/lily/build'
make: *** [doc-stage-1] Fehler 2


git cherry-pick dad1370d8d71de4691ae537a19f8b448ca562b52 is needed to build 
2.16.2 docs on libpng 1.6.* systems

cu,
-kp


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

shorten hairpin

[Helge Kruse]

Hello,

I have a staff for a cello where the player should reduce the tone during
the note quite fast. Therfore the normal haiping like this is too long:


\version "2.18.0"

cello = \relative c' {
  \time 6/8
  \key a\major
  \clef tenor
  fis2.~\downbow\p\> %%% this is the hairpin line
  |
  fis4.\! r8 r4
}

harp = \relative c' {
  \time 6/8
  \key a\major
  r16 e e e e e
  r16 e e e e e
}

\score {
  <<
\new Staff \cello
\new Staff \harp
  >>
}


I have somehow written something that looks nearly like what I want to
achive

cello = \relative c' {
  <<
{ s8\p\> s\! } \\
{ fis'2.^~^\downbow | fis4.  }
  >>
  r8 r4
}

But this is ugly to code and not perfect to read.
- The tie sarts at a different point.
- The dots are a line too low.
- The piano is a bit too left.

How can I code this more elegant and avoid the changes?


The original score is
http://conquest.imslp.info/files/imglnks/usimg/a/ad/IMSLP113653-PMLP232035-HASSELMANS_confidence.pdf,
measure 18.

Best regards
Helge
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: shorten hairpin

[Kieren MacMillan]

Hi Helge,

> How can I code this more elegant and avoid the changes?

Maybe something like this?

cello = \relative c' {
  \time 6/8
  <<
{ fis'2.\downbow ~ | fis4. r }
{ s8\p\> s\! }
  >>
}

\layout {
  \context {
\Score
\override Hairpin.minimum-length = #4
  }
}

\score { \new Staff \cello }

Hope this helps!
Kieren.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: shorten hairpin

[Urs Liska]

Am 08.11.2014 20:33, schrieb Helge Kruse:

Hello,

I have a staff for a cello where the player should reduce the tone 
during the note quite fast. Therfore the normal haiping like this is 
too long:



\version "2.18.0"

cello = \relative c' {
  \time 6/8
  \key a\major
  \clef tenor
  fis2.~\downbow\p\> %%% this is the hairpin line
  |
  fis4.\! r8 r4
}

harp = \relative c' {
  \time 6/8
  \key a\major
  r16 e e e e e
  r16 e e e e e
}

\score {
  <<
\new Staff \cello
\new Staff \harp
  >>
}


I have somehow written something that looks nearly like what I want to 
achive


cello = \relative c' {
  <<
{ s8\p\> s\! } \\
{ fis'2.^~^\downbow | fis4.  }
  >>
  r8 r4
}

But this is ugly to code and not perfect to read.
- The tie sarts at a different point.
- The dots are a line too low.
- The piano is a bit too left.

How can I code this more elegant and avoid the changes?


You may have a look at the \at function in
https://github.com/openlilylib/openlilylib/tree/master/input-shorthands/articulations-not-aligned-with-notes

HTH
Urs




The original score is 
http://conquest.imslp.info/files/imglnks/usimg/a/ad/IMSLP113653-PMLP232035-HASSELMANS_confidence.pdf, 
measure 18.


Best regards
Helge



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: shorten hairpin

[Pierre Perol-Schneider]

Hi Helge,

2014-11-08 20:33 GMT+01:00 Helge Kruse :


> I have a staff for a cello where the player should reduce the tone during
> the note quite fast. Therfore the normal haiping like this is too long:
>
>
> \version "2.18.0"
>
> cello = \relative c' {
>   \time 6/8
>   \key a\major
>   \clef tenor
>   fis2.~\downbow\p\> %%% this is the hairpin line
>   |
>   fis4.\! r8 r4
> }
>
>
Try :

cello = \relative c' {
  \time 6/8
  \key a\major
  \clef tenor
  fis2.~\downbow\p
  -\tweak bound-padding #12
  -\tweak X-offset #-11
  \> %%% this is the hairpin line
  |
  fis4.
  \! r8 r4
}

HTH,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Vertical brackets with text around chords

[Ryan McClure]

Hello Abraham,

Thank you for the snippet!!! Believe me, this is EXACTLY what I needed! I'm
attempting to figure out how it works--the brackets, that is. How can I
adjust them for other chords? What do each of the values equate to? I'm a
bit rusty on my LilyPondings... Any help would be appreciated. 

If I could send you a cookie over the internet, it would be sitting on your
kitchen table, still steaming from the oven. Once again, thank you!!!

--Ryan McClure



-
Ryan McClure

Music Education Major, Shepherd University
Luna Music Engraving
www.lunamusicengraving.com
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Vertical-brackets-with-text-around-chords-tp168519p168565.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Piano crossings and ottava indications don't get along?

[Ryan McClure]

Hello all,

These past few days I've been doing a take and take...I'm mailing around
about a lot of problems that I have with some music and I'm not really
responding to any other email...not the best way to behave when returning to
a mailing list, I know, so I hope that you all forgive me.

I am trying to engrave the sample that I've attached. Here is a snippet of
what I've got going in Lilypond...

As you can see, the crossings and ottava aren't getting along nicely. My
client really wants his music to be engraved exactly as he wrote it. What
can I do to make this work? Any help would be greatly appreciated.

I promise after this project to 1) return to the mailing list and 2)
actually return the favor and help answer problems that I can answer. You
all are the best.

-Ryan McClure



-
Ryan McClure

Music Education Major, Shepherd University
Luna Music Engraving
www.lunamusicengraving.com
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Piano-crossings-and-ottava-indications-don-t-get-along-tp168566.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Piano crossings and ottava indications don't get along?

[Ryan McClure]

This has been my kind of day...I forgot to attach the files.


 


Piano.ly   

Once again, thank you all for any help you may be able to give me.



-
Ryan McClure

Music Education Major, Shepherd University
Luna Music Engraving
www.lunamusicengraving.com
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Piano-crossings-and-ottava-indications-don-t-get-along-tp168566p168567.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user