Yann:
...
> Sorry to revive this thread, if anybody has thoughts about these
> topics, I'd be interested to read, and also about your workflow and
> used tools for some of you who regularly write arrangements and use
> Lilypond to do so.
Hello Yann,
Instead of using templates, I create skeleton files with mknew.pl [1].
///
My workflow (currently) is, using [2] as an example
. in my git/musik directory, mkdir composer_name, cd composer_name
. set up subdir. with skeleton files, something like:
../bin/mknew.pl ps36 ps36 1 '[ Sup Con Ten Bas ]'
where
ps36 = dir name to possible create
ps36 = stem of filenames to create
1 = number of pieces, for a song this is just 1, for an opera it
will be more
'[ Sup Con Ten Bas ]' = general structure of ly files and how to
name the music variables
. cd ps36
. edit ps36.instrument to my liking
. run make and do an initial check (gv ps36_01.ps) that everything compiled
. edit ps36_01.ily to fill the actual music, run make again etc.
///
Another example is [3], set up with the cmdline
../bin/mknew.pl 'bwv004' 'bwv004' '8' '{ Via Vib } { Vaa Vab } [ Sop Alt Ten
Bas ] BC'
In that cantata there was 8 pieces.
For *.ly files, I just remove staffs for tacet instruments.
The main work is filling in the *.ily files.
The result is i [4].
Regards,
/Karl Hammar
[1] https://aspodata.se/git/musik/bin/mknew.pl
[2] https://aspodata.se/git/musik/Cl%c3%a9ment_Marot
[3] https://aspodata.se/git/musik/JSBach/bwv004/
[4] https://aspodata.se/choir/osthammar/vokalensemble/
