Re: lilypond source and music sheet database

[Joseph Rushton Wakeling]

On 04/06/2013 10:50 PM, Janek Warchoł wrote:
> The things is, use git for tracking source files, not pdfs.  If you
> put \version statements in all your .ly files, you can always recreate
> a pdf with appropriate LilyPond version.
> 
> Actually, it might make sense to track some pdfs as well, but i'd say
> only the versions that are somewhat final, and i'd create two
> repositories: one with sources, in which all pdfs would be ignored,
> and another one with finished ("published") versions of pdfs - ones
> that are supposed to change rarely.

Good call.  The trouble with versioning binary or binary-ish files is not so
much about diffs in the sense of being able to see what has changed (e.g. bzr
with the qbzr plugin does nice side-by-side before and after comparison of
graphics files) but that because it can't be diff'd, each new version almost
always adds an amount of data the size of the entire file to the version 
history.

So, if you keep updating the version of a particular binary file, you wind up
with a repo whose size is out of all proportion to the size of the checked-out
tree :-(

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

Re: different fonts in composer name

[wjm]

Greetings,
You wrote:-
+
I am trying to use 2 different fonts for the composter name.
But lilypond doesn't show it the way I would like it to.

composer = \markup \override #'(font-name . "Plantin MT Std Italic") {
Muziek: }  %\markup \override #'(font-name . "Plantin MT Std") { John Goss
(1800 - 1880) }
+

This seems to work - nb : removing the second \markup

composer = \markup { \override #'(font-name . "Plantin MT Std Italic") {
Muziek: }   \override #'(font-name . "Plantin MT Std") { John Goss
(1800 - 1880) } }

Regards
Bill

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

Re: different fonts in composer name

[Nathan]

On Sat, Apr 6, 2013 at 8:07 AM, Christian  wrote:

> I am trying to use 2 different fonts for the composter name.
> But lilypond doesn't show it the way I would like it to.
>
>
>   composer = \markup \override #'(font-name . "Plantin MT Std Italic") {
> Muziek: }  %\markup \override #'(font-name . "Plantin MT Std") { John Goss
> (1800 - 1880) }
>
>
Does \italic not work?

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

Re: lilypond source and music sheet database

[Yann]

> Hi,
>
> 2013/4/6 Stjepan Horvat :
>> Hey guys .. what would you prefer using as a lilypond database. I have bunch
>> of files in bunch of folders laying around my pc with diferent versions of
>> the same song, 20 same/diffrent config files, unsorted and some of them
>> already are lost or can't find. Call it as a local "publishing" thing. I was
>> using git but they say it is not good for binary (pdf) files..it is for
>> programming..i want something where i can look for something i made 2 years
>> ago. What are your solutions..?!
>
> I am using git and i'm *very* happy about it.  Git can be used for
> everything, binary files too.  Of course, the problem with pdfs is
> that they cannot be easily diffed, but that's not particular to git -
> i don't think other VCS do better in this regard.
>
> The things is, use git for tracking source files, not pdfs.  If you
> put \version statements in all your .ly files, you can always recreate
> a pdf with appropriate LilyPond version.
>
> Actually, it might make sense to track some pdfs as well, but i'd say
> only the versions that are somewhat final, and i'd create two
> repositories: one with sources, in which all pdfs would be ignored,
> and another one with finished ("published") versions of pdfs - ones
> that are supposed to change rarely.
>
> hope this helps you,
> janek
>
> PS depending on your experience with VCSes (and your OS) Mercurial
> might be a better choice sometimes.

Hi,

I don't know if this will be useful, but this is just a small comment
(somewhat off topic) on my (small) experience with this kind of
things.
For a project I currently work on (a set of songs and hymns that we
are still heavily modifying and arranging), I did set up a mercurial
repository, to keep track of all the changes in the ly files.

I decided not to track the pdf and midi files, but I did some
makefiles and shell scripts to ease the compiling of the whole project
(this part is easier on linux-like systems I guess).
With this system set up on a server, I can have the relevant pdf and
midi files compiled and published to a www folder whenever a
contributor pushes some changes on the repository (thanks to some
mercurial hooks, that can run a script on a given event).

I chose mercurial mainly because it works well on win systems, with a
gui, so it can be easier to use in our team, for non-technical users
that are unlikely to use linux. Second reason was the possibility to
set up hooks to manage the automatic compilation thing.
(then I discovered several fancies extensions that were adding useful features).


Anyways, even if this is probably too complicated for most uses,
managing source versions of scores with a version control system is
really helpful even for day to day use (though it implies a bit of
learning at the beginning). I would say makefiles are really useful as
well when working on multi instrumental scores (managing instruments
parts ans so on).


Good night !
If the system described is interesting someone, I can give more details on it.

Yann

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

Re: different fonts in composer name

[David Kastrup]

Christian  writes:

> I am trying to use 2 different fonts for the composter name.
> But lilypond doesn't show it the way I would like it to.
>
>
>   composer = \markup \override #'(font-name . "Plantin MT Std Italic") {
> Muziek: }  %\markup \override #'(font-name . "Plantin MT Std") { John Goss
> (1800 - 1880) }

Hard to guess what you actually want here from this fragment without
description and only half-active.  Presumably something like

composer = \markup {
  \override #'(font-name . "Plantin MT Std Italic") Muziek:
  \override #'(font-name . "Plantin MT Std") { John Goss (1800 - 1880) }
}


-- 
David Kastrup


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

Re: lilypond source and music sheet database

[Janek Warchoł]

Hi,

2013/4/6 Stjepan Horvat :
> Hey guys .. what would you prefer using as a lilypond database. I have bunch
> of files in bunch of folders laying around my pc with diferent versions of
> the same song, 20 same/diffrent config files, unsorted and some of them
> already are lost or can't find. Call it as a local "publishing" thing. I was
> using git but they say it is not good for binary (pdf) files..it is for
> programming..i want something where i can look for something i made 2 years
> ago. What are your solutions..?!

I am using git and i'm *very* happy about it.  Git can be used for
everything, binary files too.  Of course, the problem with pdfs is
that they cannot be easily diffed, but that's not particular to git -
i don't think other VCS do better in this regard.

The things is, use git for tracking source files, not pdfs.  If you
put \version statements in all your .ly files, you can always recreate
a pdf with appropriate LilyPond version.

Actually, it might make sense to track some pdfs as well, but i'd say
only the versions that are somewhat final, and i'd create two
repositories: one with sources, in which all pdfs would be ignored,
and another one with finished ("published") versions of pdfs - ones
that are supposed to change rarely.

hope this helps you,
janek

PS depending on your experience with VCSes (and your OS) Mercurial
might be a better choice sometimes.

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

Re: define \header

[bobr...@centrum.is]

Ok, I'll try to clarify:

First off, Marek is correct, \header can appear within \score{} and is useful 
especially when printing all headers as I'm doing.

My initial music input files essentially look like this:


one-global = \relative {
  
}

one-first = \relative c' {
   
}

one-second = \relative c' {
  
}

one-third = \relative c' {
  
}

one-fourth = \relative c {
  
}

The second chorale is in the same file.  The above blocks are the same except 
that they start with 'two-'

My score definitions are in another file:

chor-one = {
  \context StaffGroup <<
\new Staff <<
  \one-global
  \context Voice = "first"  <<
\voiceOne \one-first
  >>
  \new Voice = "second" <<
\voiceTwo \one-second
  >>
>>
\new Staff <<
  \one-global
  \context Voice = "third"  <<
\voiceOne \one-third
  >>
  \new Voice = "fourth" <<
\voiceTwo \one-fourth
  >>
>>
  >>
}

Again, the next chorale's score block has 'one-' replaced with 'two-' (except 
at the top of the block where it's '-two' instead of '-one')

So far, so good.

Now, the file which is actually going to produce the PDF:

\book {
  \paper {
print-all-headers = ##t
  }
  \bookpart {
\score{
  \chor-one
  \header {
title = "Title 1"
subtitle = "Subtitle 1"
composer = "Composer 1"
}
}
\score{
  \chor-two
  \header {
title = "Title 2"
subtitle= "Subtitle 2"
composer = "Composer 2"
  }
}
\paper {
  page-count = #1
}
  } %% end bookpart
}


The above series of files work just fine but I would like to move the actual 
header information out of this file.  If I put it in the score blocks in the 
second file I get syntax errors.  I had thought that since I could have the 
\header block inside a score block I could simply keep it with the defined 
score block.  Evidently I was wrong.

Is there a way of doing this?

-David


- Original Message -
From: "Urs Liska" 
To: "Urs Liska" 
Cc: lilypond-user@gnu.org
Sent: Saturday, April 6, 2013 6:44:11 PM
Subject: Re: define \header

I still don't have a sufficient picture of your material,
but you may try another approach:

If your initial concern was to clean up the 'master' .ly file you may:
- define each chorale in one file:
  - write your music definitions
  - write a \header block
  - write a \score block
- In the master file you can \include the individual chorale files so you have 
only one line per chorale.

Of course the included chorale doesn't have to be completely defined in one 
single file but can also use includes.

One question that isn't clear from your initial post:
Do you write the \score blocks manually for each chorale?
Or do you have a default block that you include?

Urs



On Sat, 06 Apr 2013 20:08:05 +0200
Urs Liska  wrote:

> Sorry,
> 
> a closer look showed me that your request was quite the opposite of what 
> my suggestion could provide :-(
> 
> Really a \header block is a top-level expression that can't be written 
> inside a \score:
> http://www.lilypond.org/doc/v2.17/Documentation/notation/file-structure
> 
> Sorry again, I don't see an easy solution for your question (although it 
> should be possible with Scheme ...)
> 
> Urs
> 
> Am 06.04.2013 18:30, schrieb bobr...@centrum.is:
> > Two things:
> >
> > One; This looks like I would need to create a separate header file for each 
> > chorale.  This might not be quite what I'd prefer.
> >
> > Two; I couldn't make it work anyway.
> >
> > When you say:
> >
> > "You may put your \header in a separate file and \include it where you
> > want it to appear."
> >
> > Do you mean:
> >
> > \score {
> >  \definedScoreStuff
> >  \header {
> >\include "headerFile.ly"
> >   }
> > }
> >
> > -David
> >
> > - Original Message -
> > From: "Urs Liska" 
> > To: lilypond-user@gnu.org
> > Sent: Saturday, April 6, 2013 3:07:51 PM
> > Subject: Re: define \header
> >
> > You may put your \header in a separate file and \include it where you
> > want it to appear.
> > Does that help you?
> >
> > Urs
> >
> > Am 06.04.2013 17:02, schrieb bobr...@centrum.is:
> >> I think I've probably answered my own question already.
> >>
> >> I want to define a header block and then use the definition later.
> >>
> >> What I'm trying to do and why:
> >>
> >> I'm putting together a book of chorales for trombone quartet.  I have the 
> >> music for each part defined.  Then I create \score blocks containing the 
> >> '\definitions'.  With a whole book of these the \book{} block was getting 
> >> a bit blinding to read.  I figured out how to define my \score blocks and 
> >> then use my '\scoreDefinitions' to greatly reduce the complex look of the 
> >> \book{} file.
> >>
> >> The \header, however, seems to require being in the final \book{} block.  
> >> That is, I can't do:
> >>
> >> headerOne = {
> >>title = "Title"
> >>composer = "Composer"
> >> 

lilypond source and music sheet database

[Stjepan Horvat]

Hej guys..what would you prefer using as a lilypond database. I have bunch
of files in bunch of folder laying around my pc with diferent versions of
the same song, 20 of same/diffrent config files, unsorted and some of them
i already can't find. Call it as a local "publishing" thing.

Hey guys .. what would you prefer using as a lilypond database. I have
bunch of files in bunch of folders laying around my pc with diferent
versions of the same song, 20 same/diffrent config files, unsorted and some
of them already are lost or can't find. Call it as a local "publishing"
thing. I was using git but they say it is not good for binary (pdf)
files..it is for programming..i want something where i can look for
something i made 2 years ago. What are your solutions..?!

-- 
*Nesmotren govori kao da mačem probada, a jezik je mudrih iscjeljenje.
Izreke 12:18 *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Question about shaped note head width

[Carl Peterson]

I am working on a hymn project using shape notes. I noticed that the "mi"
head (the diamond) is wider than the others. The result is that when (using
aiken heads) I have a mi stacked on a do (diamond on triangle), the bottom
point of the diamond does not "sit" on the top of the triangle. This is
unattractive and is contrary to what I've observed in typeset shaped note
music. Is there a way to dynamically resize the notehead and/or is this
something that could be put in as a bug report/change request? The width of
the other shapes in Font Forge is 329 units while the diamond is 394 units
(the diamond needs to be 83.5% of its current width). Or, if anyone's
already tweaked their font files to accommodate, that would be great, too.

Thanks,

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

different fonts in composer name

[Christian]

I am trying to use 2 different fonts for the composter name.
But lilypond doesn't show it the way I would like it to.


  composer = \markup \override #'(font-name . "Plantin MT Std Italic") {
Muziek: }  %\markup \override #'(font-name . "Plantin MT Std") { John Goss
(1800 - 1880) }


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

Re: define \header

[Marek Klein]

Hello Urs,

2013/4/6 Urs Liska 

> Really a \header block is a top-level expression that can't be written
> inside a \score:
> http://www.lilypond.org/doc/**v2.17/Documentation/notation/**
> file-structure


This is not true, as you can read here:
http://www.lilypond.org/doc/v2.17/Documentation/notation/creating-titles-headers-and-footers#titles-explained


-- 
Marek Klein
http://gregoriana.sk
Gregoriana on 
youtube
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: define \header

[Urs Liska]

I still don't have a sufficient picture of your material,
but you may try another approach:

If your initial concern was to clean up the 'master' .ly file you may:
- define each chorale in one file:
  - write your music definitions
  - write a \header block
  - write a \score block
- In the master file you can \include the individual chorale files so you have 
only one line per chorale.

Of course the included chorale doesn't have to be completely defined in one 
single file but can also use includes.

One question that isn't clear from your initial post:
Do you write the \score blocks manually for each chorale?
Or do you have a default block that you include?

Urs



On Sat, 06 Apr 2013 20:08:05 +0200
Urs Liska  wrote:

> Sorry,
> 
> a closer look showed me that your request was quite the opposite of what 
> my suggestion could provide :-(
> 
> Really a \header block is a top-level expression that can't be written 
> inside a \score:
> http://www.lilypond.org/doc/v2.17/Documentation/notation/file-structure
> 
> Sorry again, I don't see an easy solution for your question (although it 
> should be possible with Scheme ...)
> 
> Urs
> 
> Am 06.04.2013 18:30, schrieb bobr...@centrum.is:
> > Two things:
> >
> > One; This looks like I would need to create a separate header file for each 
> > chorale.  This might not be quite what I'd prefer.
> >
> > Two; I couldn't make it work anyway.
> >
> > When you say:
> >
> > "You may put your \header in a separate file and \include it where you
> > want it to appear."
> >
> > Do you mean:
> >
> > \score {
> >  \definedScoreStuff
> >  \header {
> >\include "headerFile.ly"
> >   }
> > }
> >
> > -David
> >
> > - Original Message -
> > From: "Urs Liska" 
> > To: lilypond-user@gnu.org
> > Sent: Saturday, April 6, 2013 3:07:51 PM
> > Subject: Re: define \header
> >
> > You may put your \header in a separate file and \include it where you
> > want it to appear.
> > Does that help you?
> >
> > Urs
> >
> > Am 06.04.2013 17:02, schrieb bobr...@centrum.is:
> >> I think I've probably answered my own question already.
> >>
> >> I want to define a header block and then use the definition later.
> >>
> >> What I'm trying to do and why:
> >>
> >> I'm putting together a book of chorales for trombone quartet.  I have the 
> >> music for each part defined.  Then I create \score blocks containing the 
> >> '\definitions'.  With a whole book of these the \book{} block was getting 
> >> a bit blinding to read.  I figured out how to define my \score blocks and 
> >> then use my '\scoreDefinitions' to greatly reduce the complex look of the 
> >> \book{} file.
> >>
> >> The \header, however, seems to require being in the final \book{} block.  
> >> That is, I can't do:
> >>
> >> headerOne = {
> >>title = "Title"
> >>composer = "Composer"
> >>}
> >>
> >> ...and then use:
> >>
> >> \headerOne
> >>
> >> ...inside a \score block.  I'm using; print-all-headers = ##t, so I can 
> >> print all the title/subtitle info for each chorale.
> >>
> >> Depending on how I try, LilyPond throws errors like "unexpected \header" 
> >> or something about a problem with a music definition.  This has led me to 
> >> conclude that pre-defining things works with musical information, but not 
> >> otherwise.  Headers are not musical information.
> >>
> >> Is there a way to do this, or am I stuck with putting the header blocks in 
> >> the \book{} block?
> >>
> >> -David
> >>
> >> ___
> >> 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
> >
> > ___
> > 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

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

Re: define \header

[Urs Liska]

Sorry,

a closer look showed me that your request was quite the opposite of what 
my suggestion could provide :-(


Really a \header block is a top-level expression that can't be written 
inside a \score:

http://www.lilypond.org/doc/v2.17/Documentation/notation/file-structure

Sorry again, I don't see an easy solution for your question (although it 
should be possible with Scheme ...)


Urs

Am 06.04.2013 18:30, schrieb bobr...@centrum.is:

Two things:

One; This looks like I would need to create a separate header file for each 
chorale.  This might not be quite what I'd prefer.

Two; I couldn't make it work anyway.

When you say:

"You may put your \header in a separate file and \include it where you
want it to appear."

Do you mean:

\score {
 \definedScoreStuff
 \header {
   \include "headerFile.ly"
  }
}

-David

- Original Message -
From: "Urs Liska" 
To: lilypond-user@gnu.org
Sent: Saturday, April 6, 2013 3:07:51 PM
Subject: Re: define \header

You may put your \header in a separate file and \include it where you
want it to appear.
Does that help you?

Urs

Am 06.04.2013 17:02, schrieb bobr...@centrum.is:

I think I've probably answered my own question already.

I want to define a header block and then use the definition later.

What I'm trying to do and why:

I'm putting together a book of chorales for trombone quartet.  I have the music 
for each part defined.  Then I create \score blocks containing the 
'\definitions'.  With a whole book of these the \book{} block was getting a bit 
blinding to read.  I figured out how to define my \score blocks and then use my 
'\scoreDefinitions' to greatly reduce the complex look of the \book{} file.

The \header, however, seems to require being in the final \book{} block.  That 
is, I can't do:

headerOne = {
   title = "Title"
   composer = "Composer"
   }

...and then use:

\headerOne

...inside a \score block.  I'm using; print-all-headers = ##t, so I can print 
all the title/subtitle info for each chorale.

Depending on how I try, LilyPond throws errors like "unexpected \header" or 
something about a problem with a music definition.  This has led me to conclude that 
pre-defining things works with musical information, but not otherwise.  Headers are not 
musical information.

Is there a way to do this, or am I stuck with putting the header blocks in the 
\book{} block?

-David

___
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

___
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: Vocal music sheet - hyphens wrongly engraved

[Phil Holmes]

Try converting direct from Noteworthy to Lilypond:

http://www.holmessoft.co.uk/homepage/Software/NWC2LY/ (advert).

--
Phil Holmes


  - Original Message - 
  From: Jun Wang 
  To: lilypond-user@gnu.org 
  Sent: Saturday, April 06, 2013 2:45 PM
  Subject: Vocal music sheet - hyphens wrongly engraved


  Hi 


  I am new to lilypond, I am helping my church to generate music sheet in pdf 
in order for them to practice in choir.


  The original score is in nwc format, so I used nwc2xml to convert it into 
musicxml,  then I  tried to load the musicxml file into musescore and print the 
pdf. The pdf generated from musescore is  ok, but It has limited control on the 
layout.  So I turn to lilypond.  I used muxiscml2ly (version 2.16.2) to convert 
to lilypond file. It works great, the quality of the final pdf definitely 
better than the pdf generated from musescore.  but I found couple engraving 
issue, I want to see if you can help. I attached musicxml file, lilypond file 
and pdf file for your reference.


  First,  I found hyphens are engraved for 3 times. see the 3 hythons between 
"He’ll" and "forgive" and also lyrics of measure 11 and measure 12.  this seems 
to be my major issue so far.


  Second, This could be muxiscml2ly convertion issue, see "Duet Gently" and 
"Quartet" are printed for 3 times. I checked  the generated lilypond file, 
looks like extra voices are added. I was able to fix this by remove following 
lines from lilypond file.


  \context Voice = "PartPOneVoiceOne" { \voiceOne 
\PartPOneVoiceOne }
  \new Lyrics \lyricsto "PartPOneVoiceOne" 
\PartPOneVoiceOneLyricsOne
  \new Lyrics \lyricsto "PartPOneVoiceOne" 
\PartPOneVoiceOneLyricsTwo
  \new Lyrics \lyricsto "PartPOneVoiceOne" 
\PartPOneVoiceOneLyricsThree


  \context Voice = "PartPOneVoiceTwo" { \voiceThree 
\PartPOneVoiceTwo }
  \context Voice = "PartPTwoVoiceTwo" { \voiceThree 
\PartPTwoVoiceTwo }


  Thanks
  Jun 


--


  ___
  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: define \header

[bobr...@centrum.is]

Two things:

One; This looks like I would need to create a separate header file for each 
chorale.  This might not be quite what I'd prefer.

Two; I couldn't make it work anyway.

When you say:

"You may put your \header in a separate file and \include it where you 
want it to appear."

Do you mean:

\score {
\definedScoreStuff
\header {
  \include "headerFile.ly"
 }
}

-David

- Original Message -
From: "Urs Liska" 
To: lilypond-user@gnu.org
Sent: Saturday, April 6, 2013 3:07:51 PM
Subject: Re: define \header

You may put your \header in a separate file and \include it where you 
want it to appear.
Does that help you?

Urs

Am 06.04.2013 17:02, schrieb bobr...@centrum.is:
> I think I've probably answered my own question already.
>
> I want to define a header block and then use the definition later.
>
> What I'm trying to do and why:
>
> I'm putting together a book of chorales for trombone quartet.  I have the 
> music for each part defined.  Then I create \score blocks containing the 
> '\definitions'.  With a whole book of these the \book{} block was getting a 
> bit blinding to read.  I figured out how to define my \score blocks and then 
> use my '\scoreDefinitions' to greatly reduce the complex look of the \book{} 
> file.
>
> The \header, however, seems to require being in the final \book{} block.  
> That is, I can't do:
>
> headerOne = {
>   title = "Title"
>   composer = "Composer"
>   }
>
> ...and then use:
>
> \headerOne
>
> ...inside a \score block.  I'm using; print-all-headers = ##t, so I can print 
> all the title/subtitle info for each chorale.
>
> Depending on how I try, LilyPond throws errors like "unexpected \header" or 
> something about a problem with a music definition.  This has led me to 
> conclude that pre-defining things works with musical information, but not 
> otherwise.  Headers are not musical information.
>
> Is there a way to do this, or am I stuck with putting the header blocks in 
> the \book{} block?
>
> -David
>
> ___
> 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

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

Re: Scheme music function to expand lyrics

[Yannick CHARLES]

2013/4/6 Felix Janda 
>
> On 04/06/13 at 02:14pm, Yannick CHARLES wrote:
> > Hello !
> >
> > Thank you for your answer and your suggestions.
> > I plan anyways to use inclusion and to split my code between multiple
> > files.
> > My main problem is that the number of verses can vary between songs. But a
> > solution to this could be to build the list in the lyric file, which is
> > specific to each song.
>
> That sounds good. There is no specific need to know the number of verses, is
> there?

Well, using a construct like :
#(define rawlyrics (list #{ \one #} #{ \two #}))
assumes that I know there are exactly 2 verses, this part cannot thus
be generic.

Problem is fixed if I define a specific "rawlirics" list per song.
Or maybe I can find some way to make it generic by, let's say, having
a variable verseNumber = n, and a function extracting the n first
elements of a big liste storing generic names for the verses ("one"
"two" "three"...). This is more or less what I was thinking at the
beginning.

But in the end it is maybe even better to have a list per song, even
if it seems less generic : this allow to group together 3 current
template I have (verse-verse verse-chorus and chorus only), the fourth
is different (chorus-verse-dacapo chorus). And it helps with simple
exception to predefined templates (e.g. verse1 chorus, verse 2 chorus,
verse3 chorus, verse4 end-chorus).

I'll think of the two possibilities.

> > Then I can use the other functions you suggested me in the template file.
> >
> > Thanks a lot I'll look to the code to figure out it's different parts.
> They were just some (too) minimal examples. I hope you find a nice solution.
>
Thanks a lot ! It will already help me a lot, as I'm totally new to
scheme, and it was difficult for me to figure out how to combine
properly lilypond code and scheme. Now I have this (working) basis so
start with.

Yann

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

Re: define \header

[Urs Liska]

You may put your \header in a separate file and \include it where you 
want it to appear.

Does that help you?

Urs

Am 06.04.2013 17:02, schrieb bobr...@centrum.is:

I think I've probably answered my own question already.

I want to define a header block and then use the definition later.

What I'm trying to do and why:

I'm putting together a book of chorales for trombone quartet.  I have the music 
for each part defined.  Then I create \score blocks containing the 
'\definitions'.  With a whole book of these the \book{} block was getting a bit 
blinding to read.  I figured out how to define my \score blocks and then use my 
'\scoreDefinitions' to greatly reduce the complex look of the \book{} file.

The \header, however, seems to require being in the final \book{} block.  That 
is, I can't do:

headerOne = {
  title = "Title"
  composer = "Composer"
  }

...and then use:

\headerOne

...inside a \score block.  I'm using; print-all-headers = ##t, so I can print 
all the title/subtitle info for each chorale.

Depending on how I try, LilyPond throws errors like "unexpected \header" or 
something about a problem with a music definition.  This has led me to conclude that 
pre-defining things works with musical information, but not otherwise.  Headers are not 
musical information.

Is there a way to do this, or am I stuck with putting the header blocks in the 
\book{} block?

-David

___
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

define \header

[bobr...@centrum.is]

I think I've probably answered my own question already.

I want to define a header block and then use the definition later.

What I'm trying to do and why:

I'm putting together a book of chorales for trombone quartet.  I have the music 
for each part defined.  Then I create \score blocks containing the 
'\definitions'.  With a whole book of these the \book{} block was getting a bit 
blinding to read.  I figured out how to define my \score blocks and then use my 
'\scoreDefinitions' to greatly reduce the complex look of the \book{} file.

The \header, however, seems to require being in the final \book{} block.  That 
is, I can't do:

headerOne = {
 title = "Title"
 composer = "Composer"
 }

...and then use:

\headerOne 

...inside a \score block.  I'm using; print-all-headers = ##t, so I can print 
all the title/subtitle info for each chorale.

Depending on how I try, LilyPond throws errors like "unexpected \header" or 
something about a problem with a music definition.  This has led me to conclude 
that pre-defining things works with musical information, but not otherwise.  
Headers are not musical information.

Is there a way to do this, or am I stuck with putting the header blocks in the 
\book{} block?

-David

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

Re: Scheme music function to expand lyrics

[Felix Janda]

On 04/06/13 at 02:14pm, Yannick CHARLES wrote:
> Hello !
> 
> Thank you for your answer and your suggestions.
> I plan anyways to use inclusion and to split my code between multiple
> files.
> My main problem is that the number of verses can vary between songs. But a
> solution to this could be to build the list in the lyric file, which is
> specific to each song.

That sounds good. There is no specific need to know the number of verses, is
there?

> Then I can use the other functions you suggested me in the template file.
> 
> Thanks a lot I'll look to the code to figure out it's different parts.

They were just some (too) minimal examples. I hope you find a nice solution.

Felix

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

Re: Removing the start or the end of some music

[Gilles]

If no one objects, your functions are sufficiently concise that I
would suggest folding them directly into the extractMusic.ly file
which is linked from the snippet URL, if the original author agrees.


No problesm for me to add that, but you can notice that in the snippet
( http://lsr.dsi.unimi.it/LSR/Item?id=542 ), there is a link, pointed to  
the last version of "extractMusic.ly", and there is already some functions  
which already do the same things ( well there are called \extractBegin and  
\extractEnd).

There is even a small doc for these functions (and also for others).
Here is this link :
http://gillesth.free.fr/Lilypond/extractMusic/

--
Gilles

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

Re: Scheme music function to expand lyrics

[Yannick CHARLES]

Hello !

Thank you for your answer and your suggestions.
I plan anyways to use inclusion and to split my code between multiple
files.
My main problem is that the number of verses can vary between songs. But a
solution to this could be to build the list in the lyric file, which is
specific to each song.

Then I can use the other functions you suggested me in the template file.

Thanks a lot I'll look to the code to figure out it's different parts.

Best regards.
Yann

Le 6 avr. 2013 12:33, "Felix Janda"  a écrit :
>
> Hi,
>
> how about putting the lyrics into a list and looping over this list?
> Like:
>
> 
>
> \version "2.16.0"
>
> one = \lyricmode {Some text }
> two = \lyricmode {more text }
> #(define rawlyrics (list #{ \one #} #{ \two #}))
> #(define packedlyrics (map (lambda (arg) #{
>   \new Lyrics \lyricsto "voice" $arg
>   #}) rawlyrics))
> #(define alllyrics (make-simultaneous-music packedlyrics))
>
> \score {
> \new Staff <<
> \new Voice = "voice" {
> \relative c'' {c c }
> }
> \alllyrics
> >>
> \layout {}
> }
>
> 
>
>
> As an alternative to putting the score templates into a music function
> one could also use "\include":
>
> score.ily --
>
> \version "2.16.0"
>
> % Score template
>
> \score {
> \new Staff <<
> \music
> }
> \layout {}
> }
>
> song1.ly ---
>
> \version "2.16.0"
>
> music = \relative c'' c
> \include "score.ily"
>
> 
>
> Felix
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Scheme music function to expand lyrics

[Felix Janda]

Hi,

how about putting the lyrics into a list and looping over this list?
Like:



\version "2.16.0"

one = \lyricmode {Some text }
two = \lyricmode {more text }
#(define rawlyrics (list #{ \one #} #{ \two #}))
#(define packedlyrics (map (lambda (arg) #{
  \new Lyrics \lyricsto "voice" $arg
  #}) rawlyrics))
#(define alllyrics (make-simultaneous-music packedlyrics))

\score {
\new Staff <<
\new Voice = "voice" {
\relative c'' {c c }
}
\alllyrics
>>
\layout {}
}




As an alternative to putting the score templates into a music function
one could also use "\include":

score.ily --

\version "2.16.0"

% Score template

\score {
\new Staff <<
\music
}
\layout {}
}

song1.ly ---

\version "2.16.0"

music = \relative c'' c
\include "score.ily"



Felix

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

Re: two columns of staves

[Eluze]

Gustar wrote
> I need to have four short pieces arranged on the one landscape page in a 
> table-like manner - two rows and two columns. Is it possible?

why not!?

here is a simple example - note I'm using the development version 2.17.15
and this code will _not_ work correctly before 2.17.10


\version "2.17.15"
#(set-default-paper-size "a4" 'landscape)
aScore = \markuplist \column-lines {
  \score {
\repeat unfold 3 \relative c' {c d e f g a b c }
\layout{indent=0 line-width=75}
  }
}
\markuplist 
\override-lines #'(line-width . 150)
{ 
  \column {
\fill-line {
  \column-lines \aScore
  \column-lines \aScore
}
\vspace #2 \draw-hline \vspace #2
\fill-line {
  \column-lines \aScore
  \column-lines \aScore
}
  }
}

you might also be interested in the /\columns/ command as described in
http://lsr.dsi.unimi.it/LSR/Item?id=464 to automatically spread two or more
columns of the same width over the page

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/two-columns-of-staves-tp143983p143989.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: Lilypond libraries

[Urs Liska]

"Fried" is a "private" edition project Janek and I are working on, so these 
references are spurious and don't mean anything.

OpenLilyLib is a project with a family of resources for LilyPond and LaTeX. It 
is currently in a pre-release state, therefore there _are_ references but 
rather unclear ones ;-)
We'll make a real announcement when it's ready.

Best
Urs



Andrew Bernard  schrieb:

>Greetings folks,
>
>I have seen passing reference on the list to some lilypond libraries,
>OrgLilyLib, OLLib and Fried. I seem to be unable to find out anything
>about
>them. Any clues?
>
>Andrew
>
>
>
>
>___
>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

Lilypond libraries

[Andrew Bernard]

Greetings folks,

I have seen passing reference on the list to some lilypond libraries,
OrgLilyLib, OLLib and Fried. I seem to be unable to find out anything about
them. Any clues?

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