Re: edition-engraver: multiple editions

[Mason Hock]

On 07/01, Jan-Peter Voigt wrote:
> Hi Mason,
> 
> thank you for the hint what has to be explained more concisely in the
> docs that are still waiting for there incarnation.
> 
> In you examples activation of the editions is done with
> `\addEdition first`. To only apply edition `second` you can omit
> `\addEdition first` or comment that out.
> The command `\editionMod first ...` does not need `\addEdition first` to
> compile.

I see. I incorrectly assumed that \addEdition declares a set of edition-mods, 
but it makes much more sense that it applies them. Thanks for clarifying.

> Now the idea of the edition-engraver is to separate layout-mods and
> editorial stuff from the content. So in a real project one or more files
> containing the bare music definitions, e.g. `wind.fluteI = \relative {
> c''8 b a ... }`, are included in a file starting the typesetting for a
> specific edition.
> All editionMods (for all editions) may be placed in another
> include-file. Now in the file to typeset the specific edition either
> `\addEdition first` for each needed collection of mods is added or in
> one command `\setEditions first.second`.
> So any edition receives is typeset from its own source file. Those files
> are quite short containing the paper, layout and edition settings and
> the actual score-creating command.
> 
> IIRC I once created one file to create multiple PDFs with different
> editions activated and different paper sizes, but that is really tricky.

With the piece I'm currently working, on I'm attempting something similar using 
a bash script that iterates through every paper/tablet size, constructs \paper, 
prepends \version, appends \score, and tells lilypond to compile. Now I can 
also have it include a file containing the appropriate \addEdition statements.

Thanks for creating this very valuable tool. Lilypond is already far more 
powerful than any other scorewriter, but edition-engraver takes it to a whole 
other level.

Mason

> And in production I always use different files for separate editions.
> 
> HTH
> Jan-Peter


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

Re: edition-engraver: multiple editions

[Jan-Peter Voigt]

Hi Mason,

thank you for the hint what has to be explained more concisely in the
docs that are still waiting for there incarnation.

In you examples activation of the editions is done with
`\addEdition first`. To only apply edition `second` you can omit
`\addEdition first` or comment that out.
The command `\editionMod first ...` does not need `\addEdition first` to
compile.
Now the idea of the edition-engraver is to separate layout-mods and
editorial stuff from the content. So in a real project one or more files
containing the bare music definitions, e.g. `wind.fluteI = \relative {
c''8 b a ... }`, are included in a file starting the typesetting for a
specific edition.
All editionMods (for all editions) may be placed in another
include-file. Now in the file to typeset the specific edition either
`\addEdition first` for each needed collection of mods is added or in
one command `\setEditions first.second`.
So any edition receives is typeset from its own source file. Those files
are quite short containing the paper, layout and edition settings and
the actual score-creating command.

IIRC I once created one file to create multiple PDFs with different
editions activated and different paper sizes, but that is really tricky.
And in production I always use different files for separate editions.

HTH
Jan-Peter

Am 30.06.2018 um 18:30 schrieb Mason Hock:
> I'm slowly getting a handle on edition-engraver, largely thanks to this[1] 
> guide, which very clearly explains basic usage for a single edition. However, 
> neither the guide nor the usage examples in the repo demonstrate the use of 
> multiple editions, and I'm confused as to how that would be done in a useful 
> way. For example, these two snippets
> 
> --
> \version "2.19.82"
> 
> \include "oll-core/package.ily"
> \loadPackage edition-engraver
> 
> \addEdition first
> \editionMod first 1 0/4 the-staff.Voice ^\markup { 1 }
> \editionMod first 1 2/4 the-staff.Voice ^\markup { 2 }
> 
> \consistToContexts #edition-engraver Staff.Voice
> 
> \score {
>   \new Staff \with { \editionID the-staff } {
> \relative c' {
>   c d e f
> }
>   }
> }
> --
> 
> --
> \version "2.19.82"
> 
> \include "oll-core/package.ily"
> \loadPackage edition-engraver
> 
> \addEdition first
> \editionMod first 1 0/4 the-staff.Voice ^\markup { 1 }
> 
> \addEdition second
> \editionMod second 1 2/4 the-staff.Voice ^\markup { 2 }
> 
> \consistToContexts #edition-engraver Staff.Voice
> 
> \score {
>   \new Staff \with { \editionID the-staff } {
> \relative c' {
>   c d e f
> }
>   }
> }
> --
> 
> produce identical output, so, in the way I've been using edition-engraver so 
> far, defining multiple editions does not appear to have a different effect 
> from placing all edition-mods in one edition. It is true that I could put the 
> edition-mods for each edition in a separate .ily file and only include the 
> one I want to use when I compile, but even then there is no reason that the 
> edition in each file could be called "first" instead of giving the editions 
> different names.
> 
> My expectation would be that there is a way of specifying which editions(s) 
> should have their edition-mods observed and which should be ignored, but I 
> can't find any information about this. Can anyone provide an example of 
> correct usage of edition-engraver to maintain multiple editions?
> 
> Thanks,
> 
> Mason
> 
> 
> [1] https://lists.gnu.org/archive/html/lilypond-user/2018-01/msg00603.html
> 
> 
> 
> ___
> 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

edition-engraver: multiple editions

[Mason Hock]

I'm slowly getting a handle on edition-engraver, largely thanks to this[1] 
guide, which very clearly explains basic usage for a single edition. However, 
neither the guide nor the usage examples in the repo demonstrate the use of 
multiple editions, and I'm confused as to how that would be done in a useful 
way. For example, these two snippets

--
\version "2.19.82"

\include "oll-core/package.ily"
\loadPackage edition-engraver

\addEdition first
\editionMod first 1 0/4 the-staff.Voice ^\markup { 1 }
\editionMod first 1 2/4 the-staff.Voice ^\markup { 2 }

\consistToContexts #edition-engraver Staff.Voice

\score {
  \new Staff \with { \editionID the-staff } {
\relative c' {
  c d e f
}
  }
}
--

--
\version "2.19.82"

\include "oll-core/package.ily"
\loadPackage edition-engraver

\addEdition first
\editionMod first 1 0/4 the-staff.Voice ^\markup { 1 }

\addEdition second
\editionMod second 1 2/4 the-staff.Voice ^\markup { 2 }

\consistToContexts #edition-engraver Staff.Voice

\score {
  \new Staff \with { \editionID the-staff } {
\relative c' {
  c d e f
}
  }
}
--

produce identical output, so, in the way I've been using edition-engraver so 
far, defining multiple editions does not appear to have a different effect from 
placing all edition-mods in one edition. It is true that I could put the 
edition-mods for each edition in a separate .ily file and only include the one 
I want to use when I compile, but even then there is no reason that the edition 
in each file could be called "first" instead of giving the editions different 
names.

My expectation would be that there is a way of specifying which editions(s) 
should have their edition-mods observed and which should be ignored, but I 
can't find any information about this. Can anyone provide an example of correct 
usage of edition-engraver to maintain multiple editions?

Thanks,

Mason


[1] https://lists.gnu.org/archive/html/lilypond-user/2018-01/msg00603.html


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

Re: Edition Engraver -- multiple editions

[Craig Dabelstein]

Jan-Peter,

Thank you so much. Now I get it!

I'm working on critical editions of band music from the French Revolution
-- at the moment an Ouverture by Charles-Simon Catel. The edition engraver
has just become invaluable to me.

All the best,

Craig


On 1 March 2018 at 18:14, Jan-Peter Voigt  wrote:

> Hi Craig,
>
> you remind me to rethink wording/naming of the different identifiers!
>
> In your example you point on two different ID-types. With \addEdition you
> add one target-ID to the current compilation. You can add multiple targets
> like fullscore, global-mods, original-page-breaks at once.
>
> With \editionID inside a layout-context block you assign a
> context-identifier. There is one context-identifier - one might call it
> context-address - per context-instance.
> So the score will have a contextID like perhaps:
>
> \layout {
>   \context {
> \Score
> \editionID ##f bwv.247.marco.11.choral
>   }
> }
>
> and the different context are created with e.g.
> \new Staff \with { \editionID flute } << ... >>
> so this Staff receives the ID `bwv.247.marco.11.choral.flute`.
> This should be stable across all compilations for all targets.
> Now you can enter modifications like
> \editionMod score 2 3/4 bwv.247.marco.11.choral.Staff  score>
> \editionMod part 2 3/4 bwv.247.marco.11.choral.Staff 
> \editionMod global 2 3/4 bwv.247.marco.11.choral.Staff 
>
> (you can shorten this significantly with a variable!)
>
> Inside the respective files for the core and the part you can add targets
> as you like:
> \addEdition score
> \addEdition global
>
> The EE will apply all modifications for all active targets. In the part
> files you might use the shorter variant
> \setEditions part.violin.global
>
> To activate the "part", "violin" and "global" targets. If lilypond reads
> the mods for the score while compiling the violin part, it doesn't matter,
> as long as the score-target is not active.
>
> The edition-engraver is using pointers/IDs/addresses in three dimensions:
> 1. the target of the current compilation-run
> 2. the context-address
> 3. the timestep
>
> Right now target IDs can not be changed within a file/a compilation for
> different scores. So you will have one file for the fullscore and one for
> each part. These files will include the music from other files and then
> apply the mods needed for the current target.
>
> HTH
> Jan-Peter
>
> Btw.:
> One of the projects I have been working on over the last two years is
> typesetting a new reconstruction of the "Markus-Passion" from Johann
> Sebastian Bach (Ortus-Verlag/Berlin - fullscore ISMN 979-0-502340-65-0,
> piano reduction ISMN 979-0-502340-66-7, choir part ISMN 979-0-502340-67-4,
> instrumental parts ISMN 979-0-502340-68-1)
> by Andreas Fischer (St.Katharinen, Hamburg, Germany).
> I am going to write a description of this project when my schedule allows.
>
>
>
>
> Am 01.03.2018 um 02:34 schrieb Craig Dabelstein:
>
>> Hi all,
>>
>> I thought I had my head around the edition engraver but I'm going wrong
>> somewhere. If I want to have different mods for a score, the parts, and a
>> selection of mods applicable to both the score and the parts, do I need to
>> create three different editions such as this:
>>
>> \addEdition score
>> \addEdition parts
>> \addEdition scoreandparts
>>
>> If so, how do I switch between them?
>>
>> I was trying to use different editionIDs for everything but it's not
>> working. Can a score have multiple IDs such as:
>>
>> \layout{
>> \context {
>>  \Score
>>  \editionID ##f score
>>  \editionID ##f both
>>  }
>> }
>>
>> Thanks in advance,
>>
>> Craig
>>
>> --
>> *Craig Dabelstein*
>> Maxime's Music
>> craig.dabelst...@gmail.com 
>> /http://maximesmusic.com/
>>
>>
>> ___
>> 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
>



-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Edition Engraver -- multiple editions

[Jan-Peter Voigt]

Hi Craig,

you remind me to rethink wording/naming of the different identifiers!

In your example you point on two different ID-types. With \addEdition 
you add one target-ID to the current compilation. You can add multiple 
targets like fullscore, global-mods, original-page-breaks at once.


With \editionID inside a layout-context block you assign a 
context-identifier. There is one context-identifier - one might call it 
context-address - per context-instance.

So the score will have a contextID like perhaps:

\layout {
  \context {
\Score
\editionID ##f bwv.247.marco.11.choral
  }
}

and the different context are created with e.g.
\new Staff \with { \editionID flute } << ... >>
so this Staff receives the ID `bwv.247.marco.11.choral.flute`.
This should be stable across all compilations for all targets.
Now you can enter modifications like
\editionMod score 2 3/4 bwv.247.marco.11.choral.Staff score>

\editionMod part 2 3/4 bwv.247.marco.11.choral.Staff 
\editionMod global 2 3/4 bwv.247.marco.11.choral.Staff 

(you can shorten this significantly with a variable!)

Inside the respective files for the core and the part you can add 
targets as you like:

\addEdition score
\addEdition global

The EE will apply all modifications for all active targets. In the part 
files you might use the shorter variant

\setEditions part.violin.global

To activate the "part", "violin" and "global" targets. If lilypond reads 
the mods for the score while compiling the violin part, it doesn't 
matter, as long as the score-target is not active.


The edition-engraver is using pointers/IDs/addresses in three dimensions:
1. the target of the current compilation-run
2. the context-address
3. the timestep

Right now target IDs can not be changed within a file/a compilation for 
different scores. So you will have one file for the fullscore and one 
for each part. These files will include the music from other files and 
then apply the mods needed for the current target.


HTH
Jan-Peter

Btw.:
One of the projects I have been working on over the last two years is 
typesetting a new reconstruction of the "Markus-Passion" from Johann 
Sebastian Bach (Ortus-Verlag/Berlin - fullscore ISMN 979-0-502340-65-0, 
piano reduction ISMN 979-0-502340-66-7, choir part ISMN 
979-0-502340-67-4, instrumental parts ISMN 979-0-502340-68-1)

by Andreas Fischer (St.Katharinen, Hamburg, Germany).
I am going to write a description of this project when my schedule allows.




Am 01.03.2018 um 02:34 schrieb Craig Dabelstein:

Hi all,

I thought I had my head around the edition engraver but I'm going wrong 
somewhere. If I want to have different mods for a score, the parts, and 
a selection of mods applicable to both the score and the parts, do I 
need to create three different editions such as this:


\addEdition score
\addEdition parts
\addEdition scoreandparts

If so, how do I switch between them?

I was trying to use different editionIDs for everything but it's not 
working. Can a score have multiple IDs such as:


\layout{
\context {
     \Score
     \editionID ##f score
     \editionID ##f both
     }
}

Thanks in advance,

Craig

--
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com 
/http://maximesmusic.com/


___
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

Edition Engraver -- multiple editions

[Craig Dabelstein]

Hi all,

I thought I had my head around the edition engraver but I'm going wrong
somewhere. If I want to have different mods for a score, the parts, and a
selection of mods applicable to both the score and the parts, do I need to
create three different editions such as this:

\addEdition score
\addEdition parts
\addEdition scoreandparts

If so, how do I switch between them?

I was trying to use different editionIDs for everything but it's not
working. Can a score have multiple IDs such as:

\layout{
\context {
\Score
\editionID ##f score
\editionID ##f both
}
}

Thanks in advance,

Craig

-- 
*Craig Dabelstein*
Maxime's Music
craig.dabelst...@gmail.com
*http://maximesmusic.com *
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Edition-engraver: Multiple editions in same file

[Ben Strecker]

Thank you Jan-Peter and Kieren,

That helps clear up a lot of my confusion.

Ben

> On Jan 24, 2016, at 2:24 PM, Jan-Peter Voigt  wrote:
> 
> Hi Ben,
> 
> I was about to write about the three dimension to watch. But I have to think 
> about it, if I can change this.
> For now there will one set of editiontags per compilation. So every call to 
> \addEdition and \removeEdition will affect the list of active 
> modification-layers for the whole run. The compilation of a file is done in 
> multiple steps. The called commands act on in the first step, the actual 
> typesetting is done in another step.
> In my use-cases, I always have one edition-set per file, e.g. full-score or 
> part for single instruments. But your use-case looks reasonable. I attached 
> your example slightly modified, where the first score is modified, but not 
> the second. To achieve this, I used \applyContext, so that the \removeEdition 
> command is performed, when beginning typesetting th second score. The command 
> could be wrapped inside a little helper command.
> This technique has the pro, that it matches your use-case, but a big con, in 
> that it remixes content and design again.
> So I would not recommend this over the solution, you already found.
> Perhaps another solution is found another day ;-)
> 
> HTH for now
> Cheers
> Jan-Peter
> 
> Am 22.01.2016 um 22:00 schrieb Ben Strecker:
>> I’m working on a project that would have the same melody appearing in 
>> different ranges in the same document.  Each range has its own set of 
>> modifications through the edition-engraver, but using \removeEdition 
>> anywhere in the file appears to remove that edition for all of the scores.  
>> What is the best practice for managing multiple editions in the same file?  
>> 
>> I have attached a very simple example where I have two scores:  one that 
>> should have a color modification applied, and another that should not have 
>> any editionMods applied.
>> 
>> Thanks,
>> Ben
>> 
>> 
>> 
>> ___
>> 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: Edition-engraver: Multiple editions in same file

[Jan-Peter Voigt]

Hi Ben,

I was about to write about the three dimension to watch. But I have to 
think about it, if I can change this.
For now there will one set of editiontags per compilation. So every call 
to \addEdition and \removeEdition will affect the list of active 
modification-layers for the whole run. The compilation of a file is done 
in multiple steps. The called commands act on in the first step, the 
actual typesetting is done in another step.
In my use-cases, I always have one edition-set per file, e.g. full-score 
or part for single instruments. But your use-case looks reasonable. I 
attached your example slightly modified, where the first score is 
modified, but not the second. To achieve this, I used \applyContext, so 
that the \removeEdition command is performed, when beginning typesetting 
th second score. The command could be wrapped inside a little helper 
command.
This technique has the pro, that it matches your use-case, but a big 
con, in that it remixes content and design again.

So I would not recommend this over the solution, you already found.
Perhaps another solution is found another day ;-)

HTH for now
Cheers
Jan-Peter

Am 22.01.2016 um 22:00 schrieb Ben Strecker:

I’m working on a project that would have the same melody appearing in different 
ranges in the same document.  Each range has its own set of modifications 
through the edition-engraver, but using \removeEdition anywhere in the file 
appears to remove that edition for all of the scores.  What is the best 
practice for managing multiple editions in the same file?

I have attached a very simple example where I have two scores:  one that should 
have a color modification applied, and another that should not have any 
editionMods applied.

Thanks,
Ben



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


\include "editorial-tools/edition-engraver/definitions.ily"

\version "2.19.32"

melody = \relative c' {
  c d e f
}

\layout {
  \context {
\Score
\consists \editionEngraver my.Test
  }
  \context {
\Staff
\consists \editionEngraver ##f
  }
  \context {
\Voice
\consists \editionEngraver ##f 
  }
}

%Red Note
\editionMod red 1 1/4 my.Test.Staff.A \once \override NoteHead #'color = #red

\addEdition red
%this one should have the modification
\score {
  \new Staff { \melody }
}

% how do you get this one to NOT have te modification?
\score {
  \new Staff {
\applyContext #(lambda (context) #{ \removeEdition red #})
\melody
  }
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Edition-engraver: Multiple editions in same file

[Urs Liska]

Am 22.01.2016 um 22:00 schrieb Ben Strecker:
> I’m working on a project that would have the same melody appearing in 
> different ranges in the same document.  Each range has its own set of 
> modifications through the edition-engraver, but using \removeEdition anywhere 
> in the file appears to remove that edition for all of the scores.  What is 
> the best practice for managing multiple editions in the same file?  
>
> I have attached a very simple example where I have two scores:  one that 
> should have a color modification applied, and another that should not have 
> any editionMods applied.

If your actual file is also organized using different \score blocks you
can achieve what you want by moving the layout block *inside* the score
block:

\score {
  \new Staff { \melody }
  \layout {
\context {
  \Score
  \consists \editionEngraver my.Test
}
\context {
  \Staff
  \consists \editionEngraver ##f
}
\context {
  \Voice
  \consists \editionEngraver ##f
}
  }
}

If that's not what you need please give more details on the actual use
case. It may be that we can help you further

HTH
Urs

>
> Thanks,
> Ben
>
>
>
> ___
> 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: Edition-engraver: Multiple editions in same file

[Kieren MacMillan]

Hi Benjamin,

> So far this seems to be working, but I don't know if this is considered the 
> 'correct' way to do it.
> So have I kept myself on the beaten path or wandered into inadvisable 
> territory?

This is what I do, all the time.
I’ve never had any problems with it, so I’m assuming it’s the “correct” way.

n.b. You can even have multiple editions *in the same score*, by adding them 
[individually] to the appropriate contexts inside the \score block.

Cheers,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: Edition-engraver: Multiple editions in same file

[Benjamin Strecker]

Thanks, Urs.

That occurred to me after a good night’s sleep.  I think I have *a*
solution now, but I don’t know if it’s the recommended way to do things.

My project contains four scores where the melody is the same but in
different registers.  There are some modifications that I want applied
universally to each score, but the individual scores have their own
requirements from different BreathingSign collisions, slur shapes, etc.

I now have my file organized with a global \layout block:

\layout {
  \context {
\Score
\consists \editionEngraver beams
  }
  \context {
\Staff
\consists \editionEngraver ##f
  }
  \context {
\Voice
\consists \editionEngraver ##f
  }
}

And each of the scores has it's own layout block consisted with an
editionEngraver unique to that score.  Here are the first two, for example:

\score {
  \new Staff {
<< \melody \dynamics \global >>
  }
  \layout {
\context {
  \Staff
  \consists \editionEngraver firstTreble
}
  }
}


\score {
  \new Staff {
<< \transpose e b \melody \dynamics \global >>
  }
  \layout {
\context {
  \Staff
  \consists \editionEngraver highest
}
  }
}

So far this seems to be working, but I don't know if this is considered the
'correct' way to do it.

So have I kept myself on the beaten path or wandered into inadvisable
territory?

Ben

On Jan 23, 2016, at 9:17 AM, Urs Liska  wrote:



Am 22.01.2016 um 22:00 schrieb Ben Strecker:

I’m working on a project that would have the same melody appearing in
different ranges in the same document.  Each range has its own set of
modifications through the edition-engraver, but using \removeEdition
anywhere in the file appears to remove that edition for all of the
scores.  What is the best practice for managing multiple editions in
the same file?

I have attached a very simple example where I have two scores:  one
that should have a color modification applied, and another that should
not have any editionMods applied.


If your actual file is also organized using different \score blocks you can
achieve what you want by moving the layout block *inside* the score block:

\score {
  \new Staff { \melody }
  \layout {
\context {
  \Score
  \consists \editionEngraver my.Test
}
\context {
  \Staff
  \consists \editionEngraver ##f
}
\context {
  \Voice
  \consists \editionEngraver ##f
}
  }
}

If that's not what you need please give more details on the actual use
case. It may be that we can help you further

HTH
Urs

Thanks,
Ben




___
lilypond-user mailing
listlilypond-user@gnu.orghttps://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

Edition-engraver: Multiple editions in same file

[Ben Strecker]

I’m working on a project that would have the same melody appearing in different 
ranges in the same document.  Each range has its own set of modifications 
through the edition-engraver, but using \removeEdition anywhere in the file 
appears to remove that edition for all of the scores.  What is the best 
practice for managing multiple editions in the same file?  

I have attached a very simple example where I have two scores:  one that should 
have a color modification applied, and another that should not have any 
editionMods applied.

Thanks,
Ben



edition.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user