ncertoNo3.ly:
>
> \include "myMusic_ForConcertoNo3.ly"
> \include "myStructure_ViolinI.ly"
> \include "myStructure_Orchestra.ly"
>
> \myOrchestralScore
>
> This is a more structured approach than splitting the syntax across
> file
a more structured approach than splitting the syntax across
> files. Perhaps it is already possible to do this -- I haven't tried.
>
> Thoughts?
>
>-Dave
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
--
View this message in context:
http://www.nabble.com/Orchestral-score-file-organization-tf2288589.html#a6413345
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
David Greene wrote:
This is a more structured approach than splitting the syntax across
files. Perhaps it is already possible to do this -- I haven't tried.
Try it! You will be positively surprised.
/Mats
___
lilypond-user mailing list
lilypon
Rick Hansen (aka RickH) wrote:
\include CommonHeader.ly% contains header block and begins a
score block and begins a nested choir staff block
\include AltoSax1.ly % generic template for alto
sax and transposes for Eb
\include AltoSax2.ly
l items to variables and use them
> throughout a piece. This helps a lot, thanks!
>
>
--
View this message in context:
http://www.nabble.com/Orchestral-score-file-organization-tf2288589.html#a6368078
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
__
x27;Y-offset = #0.08
>
> \override MultiMeasureRest #'expand-limit = 1
>
> Then after that, there's the actual music. Each file has that part up
> there in common, with only the file name and the instrument name changed.
> If I need to transpose anything or use a d
or each part that refference the one big
> file? To me, at least, the first option makes the most sense. However,
> what do most people do in this situation?
>
--
View this message in context:
http://www.nabble.com/Orchestral-score-file-organization-tf2288589.html#a6357277
