Hi Federico,
thanks for your reply. I also looked at Mutopia and I have to revise
things: My currently planned approach is now B and A would be an
alternative.
Am 05.11.2016 um 10:43 schrieb Federico Bruni:
Il giorno sab 5 nov 2016 alle 0:55, Noeck <address@hidden> ha
scritto:
A) *folders per compilation step and file type*
... The disadvantage is that it would
probably be impossible to produce the output with a simple
lilypond call
but only the scripts would be able to engrave the score.
This is a serious disadvantage.
Well, it probably could still be typed by hand but it would be a long
command with a lot of optional settings.
What are the LilyPond or Frescobaldi limitations/missing features
for
this approach to be possible?
-o can specify the output file or folder. I don't know if it exists
for
midi files separately.
The audio files would still have to be generated by a script.. Or
do you
use the audio export of Frescobaldi?
Yes, that would be an extra script in any case.
B) *folders per score*
This is what I use and I think it's the best approach.
If I want to find a specific file type (PDF or MIDI) I use a file
manager or a documents manager (like Gnome Documents).
My concern was more about clean folders: The ly files contain the
information in a condensed form (in terms of file format simplicity
and
file size). The pdfs and audio files are reproducible. In variant A, I
could delete the pdf and audio folders and start from scratch, I could
see by the folder sizes how large the music information is (ly) and
how
large the derived files.
But scripts that tell me these sizes are easy to write and in git I
can
ignore file types, so the folder separation is not necessary.