lilypond-user
[Top][All Lists]
Advanced

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

Re: Creating multi-score books


From: Hwaen Ch'uqi
Subject: Re: Creating multi-score books
Date: Thu, 16 Feb 2017 04:23:04 -0500

Greetings Don,

To add to the suggestions, you might consider using pdftk - assuming
of course that both LaTeX and LilyPond files will be converted to pdf.

Hwaen Ch'uqi


On 2/16/17, Abbé Jacques Peron <address@hidden> wrote:
> Hello,
>
> Another alternative is lyluatex, that you may find here :
> https://github.com/jperon/lyluatex.
>
> For this to work, you'll have to use lualatex.
>
> Jacques Peron +
>
>
> Le 16 févr. 2017 14:32, "Urs Liska" <address@hidden> a écrit :
>
>
>
> Am 16. Februar 2017 07:02:10 MEZ schrieb Don Gingrich <
> address@hidden>:
>>I've got a basic problem, and I'm not having much
>>joy with the documentation.
>>
>>Over the past few years I've created several scores
>>for folk songs.
>>
>>Now, I'm going to be doing a workshop discussing
>>their origins.
>>
>>What I'd like to create is:
>>
>><title page in TeX>
>>
>><text page discussing song 1 in TeX>
>>
>><score of song one in ly >
>>
>><text page discussing song 2 in TeX>
>>
>><score of song 2 in ly >
>>
>>and so on
>>
>>I'm probably more familiar with LaTeX than
>>LilyPond, so I'd really prefer to do the cover
>>page and discussion in TeX and the scores
>>in LilyPond.
>
> If I don't misunderstand you I would compile the songs individually and
> include them using \includepdf.
>
> HTH
> Urs
>
>
>>
>>Note that some of the scores were originally
>>entered using MuseScore and the converted
>>using xml2ly -- so the LilyPond code is *ugly*
>>but works as a standalone score. In my copious
>>free time I'd like to shift these converted scores
>>into clean code, but it's in the "if it ain't broke....."
>>category unless the converted stuff is likely to be
>> breaking things.
>>
>>My minimal example winds up being several hundred
>>lines, so I've not included it.
>>
>>I tried this:
>>
>>\header {
>>  title = "Eight miniatures"
>>  composer = "Igor Stravinsky"
>>}
>>\score {
>>  …
>>  \header { piece = "Romanze" }
>>}
>>\markup {
>>   …text of second verse…
>>}
>>\markup {
>>   …text of third verse…
>>}
>>\score {
>>  …
>>  \header { piece = "Menuetto" }
>>}
>>
>>With including the score files and it
>>did not work.
>>
>>I tried this first:
>>
>>\documentclass[a4paper]{article}
>>
>>\begin{document}
>>
>>Documents for \verb+lilypond-book+ may freely mix music and text.
>>For example,
>>
>>Options are put in brackets.
>>
>>Larger examples can be put into a separate file, and introduced with
>>\verb+\lilypondfile+.
>>
>>\lilypondfile[quote,noindent]{MyFileName.ly}
>>
>>(If needed, replace @file{screech-and-boink.ly} by any @file{.ly} file
>>you put in the same directory as this file.)
>>
>>\end{document}
>>
>>And all that I got was the filename printed where the score should
>>have been.
>>
>>I also looked at the thread titled:
>>"Problem with lilypond-book and \markup blocks" from 2007
>>But when I tried to add a header after the \score{ -- e.g.
>>\score {
>> \header{
>> title = "some silly thing"
>>   composer = "Not Mozart"
>>    }
>>    {
>>        <<
>>
>>The title and composer disappeared into the ether -- clearly
>>the method here only works for snippets, not full or multi-page
>>scores.
>>
>>I keep banging at this and getting nowhere.
>>
>>
>>As putting a bunch of individual scores together into a book may
>>be a more or less common task, a good template would be brilliant
>>and potentially useful for others
>>
>>Thanks,
>>
>>-Don
>>
>>--
>>Don Gingrich
>>
>>
>>
>>_______________________________________________
>>lilypond-user mailing list
>>address@hidden
>>https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.
>
> _______________________________________________
> 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]