Re: state-of-the-art multi-instrumental/transposing mechanism

2017-03-21 Thread Kieren MacMillan
Hi Jan-Peter,

> I am going to add key-sigs to the EE, so that they can be added as 
> editionMods.

Thanks!
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: state-of-the-art multi-instrumental/transposing mechanism

2017-03-15 Thread Jan-Peter Voigt

Hi again,

it needs some more thinking, how key signatures can be treated right for 
this case. It is all about the timing - if you set the 
instrumentTransposition with the editionEngraver, the properties are set 
early and the keys look fine here.
I am going to add key-sigs to the EE, so that they can be added as 
editionMods.


Best
Jan-Peter

Am 15.03.2017 um 08:29 schrieb Jan-Peter Voigt:

Hi Kieren,

now I had a look into the autotranspose code. The problem is the order
of context properties set in the Staff. If you change the transposed
code to:

\new Staff \with \autoTranspose << \global \flutepart >>

It should get the key-signatures right. Though this is only a hint where
the autotransposer fails. I'll search a way to make the engraver act
later - perhaps in the acknowledger slot. But still I have to set the
Staff-context-properties, so that accidentals are set right.

Jan-Peter


Am 06.03.2017 um 01:15 schrieb Kieren MacMillan:

Hi Urs,


it's too late for me right now to properly understand the issue


1. Thanks for responding anyway!  =)
2. Looks like you do understand most of the issue.


but I wanted to direct you to Jan-Peter's
https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose,

not knowing if it's even *related* to your question.


It is!

In the modified snippet (below), I use \autotranspose. It works great
EXCEPT the [abstracted] key signature part. If we could just figure
out how to have the key signature properly displayed in the transposed
part, I think we’d be most of the way to a complete solution (though
admittedly I don’t know the internals of this engraver yet, so there
may be other issues it doesn’t or can’t handle.

Thanks!
Kieren.

%%%  SNIPPET BEGINS
\version "2.19.56"
\include
"openlilylib/snippets/editorial-tools/auto-transpose/definitions.ily"

\paper { line-width = 6\in }

flute = {
\set Staff.instrumentName = "Flute"
\set Staff.shortInstrumentName = "Fl."
\transposition c'
}
altoflute = {
\set Staff.instrumentName = "Alto Flute"
\set Staff.shortInstrumentName = "A. Fl."
\transposition g
}
toF = \markup "take flute"
toAF = \markup "take alto flute"

global = {
\key c \major s1 \break
\key d \major s1 \break
\key e \major s1 \break
}

flutepart = {
\flute
a'2 r^\toAF
\altoflute
a'2 r^\toF
\flute
a'2 r
}

\markup \bold "C score:"
\score {
\new Staff << \global \flutepart >>
}

\markup \vspace #4
\markup \bold "Transposed score/part (incorrect):"
\score {
\new Staff \with \autoTranspose << \global \flutepart >>
}
%%%  SNIPPET BEGINS



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




___
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: state-of-the-art multi-instrumental/transposing mechanism

2017-03-15 Thread Jan-Peter Voigt

Hi Kieren,

now I had a look into the autotranspose code. The problem is the order 
of context properties set in the Staff. If you change the transposed 
code to:


\new Staff \with \autoTranspose << \global \flutepart >>

It should get the key-signatures right. Though this is only a hint where 
the autotransposer fails. I'll search a way to make the engraver act 
later - perhaps in the acknowledger slot. But still I have to set the 
Staff-context-properties, so that accidentals are set right.


Jan-Peter


Am 06.03.2017 um 01:15 schrieb Kieren MacMillan:

Hi Urs,


it's too late for me right now to properly understand the issue


1. Thanks for responding anyway!  =)
2. Looks like you do understand most of the issue.


but I wanted to direct you to Jan-Peter's
https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose,
not knowing if it's even *related* to your question.


It is!

In the modified snippet (below), I use \autotranspose. It works great EXCEPT 
the [abstracted] key signature part. If we could just figure out how to have 
the key signature properly displayed in the transposed part, I think we’d be 
most of the way to a complete solution (though admittedly I don’t know the 
internals of this engraver yet, so there may be other issues it doesn’t or 
can’t handle.

Thanks!
Kieren.

%%%  SNIPPET BEGINS
\version "2.19.56"
\include "openlilylib/snippets/editorial-tools/auto-transpose/definitions.ily"

\paper { line-width = 6\in }

flute = {
\set Staff.instrumentName = "Flute"
\set Staff.shortInstrumentName = "Fl."
\transposition c'
}
altoflute = {
\set Staff.instrumentName = "Alto Flute"
\set Staff.shortInstrumentName = "A. Fl."
\transposition g
}
toF = \markup "take flute"
toAF = \markup "take alto flute"

global = {
\key c \major s1 \break
\key d \major s1 \break
\key e \major s1 \break
}

flutepart = {
\flute
a'2 r^\toAF
\altoflute
a'2 r^\toF
\flute
a'2 r
}

\markup \bold "C score:"
\score {
\new Staff << \global \flutepart >>
}

\markup \vspace #4
\markup \bold "Transposed score/part (incorrect):"
\score {
\new Staff \with \autoTranspose << \global \flutepart >>
}
%%%  SNIPPET BEGINS



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




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


Re: state-of-the-art multi-instrumental/transposing mechanism

2017-03-06 Thread Jan-Peter Voigt

Hi Kieren,

I just compiled your example and saw the error. Maybe the transposition 
is (re)set after the auto-transposer acts - we'll see.

I am quite busy right now, but I hope I can have a look at it soon.

Best
Jan-Peter


Am 06.03.2017 um 13:11 schrieb Kieren MacMillan:

Hi David,


\key \default shows something wrong?


No… But I don’t want to have to manually add that in every part. And then if 
the location where the key signature changes, I would have to change it in 
every part. etc.

I see in the comments of the engraver that Jan-Peter has a “to-do” to handle 
this very issue — hopefully that implementation is not too far off.

Thanks,
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




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


Re: state-of-the-art multi-instrumental/transposing mechanism

2017-03-06 Thread Kieren MacMillan
Hi David,

> \key \default shows something wrong?

No… But I don’t want to have to manually add that in every part. And then if 
the location where the key signature changes, I would have to change it in 
every part. etc.

I see in the comments of the engraver that Jan-Peter has a “to-do” to handle 
this very issue — hopefully that implementation is not too far off.

Thanks,
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: state-of-the-art multi-instrumental/transposing mechanism

2017-03-06 Thread David Kastrup
Kieren MacMillan  writes:

> Hi Urs,
>
>> it's too late for me right now to properly understand the issue
>
> 1. Thanks for responding anyway!  =)
> 2. Looks like you do understand most of the issue.
>
>> but I wanted to direct you to Jan-Peter's
>> https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose,
>> not knowing if it's even *related* to your question.
>
> It is!
>
> In the modified snippet (below), I use \autotranspose. It works great
> EXCEPT the [abstracted] key signature part. If we could just figure
> out how to have the key signature properly displayed in the transposed
> part,

\key \default shows something wrong?

-- 
David Kastrup

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


Re: state-of-the-art multi-instrumental/transposing mechanism

2017-03-05 Thread Kieren MacMillan
Hi Urs,

> it's too late for me right now to properly understand the issue

1. Thanks for responding anyway!  =)
2. Looks like you do understand most of the issue.

> but I wanted to direct you to Jan-Peter's
> https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose,
> not knowing if it's even *related* to your question.

It is!

In the modified snippet (below), I use \autotranspose. It works great EXCEPT 
the [abstracted] key signature part. If we could just figure out how to have 
the key signature properly displayed in the transposed part, I think we’d be 
most of the way to a complete solution (though admittedly I don’t know the 
internals of this engraver yet, so there may be other issues it doesn’t or 
can’t handle.

Thanks!
Kieren.

%%%  SNIPPET BEGINS
\version "2.19.56"
\include "openlilylib/snippets/editorial-tools/auto-transpose/definitions.ily"

\paper { line-width = 6\in }

flute = {
\set Staff.instrumentName = "Flute"
\set Staff.shortInstrumentName = "Fl."
\transposition c'
}
altoflute = {
\set Staff.instrumentName = "Alto Flute"
\set Staff.shortInstrumentName = "A. Fl."
\transposition g
}
toF = \markup "take flute"
toAF = \markup "take alto flute"

global = {
\key c \major s1 \break
\key d \major s1 \break
\key e \major s1 \break
}

flutepart = {
\flute
a'2 r^\toAF
\altoflute
a'2 r^\toF
\flute
a'2 r
}

\markup \bold "C score:"
\score {
\new Staff << \global \flutepart >>
}

\markup \vspace #4
\markup \bold "Transposed score/part (incorrect):"
\score {
\new Staff \with \autoTranspose << \global \flutepart >>
}
%%%  SNIPPET BEGINS



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: state-of-the-art multi-instrumental/transposing mechanism

2017-03-05 Thread Urs Liska
Hi Kieren,

admittedly it's too late for me right now to properly understand the
issue but I wanted to direct you to Jan-Peter's
https://github.com/openlilylib/snippets/tree/master/editorial-tools/auto-transpose,
not knowing if it's even *related* to your question.

Best
Urs

Am 06.03.2017 um 00:13 schrieb Kieren MacMillan:
> Hi all,
>
> Inspired by the “tweaking clefs” thread, I’m trying again to see if we can 
> crowd-source a state-of-the-art multi-instrumentalist mechanism.
>
> The snippet below (minimal, for these purposes?) demonstrates the problem I’m 
> trying to solve.
>
> Am I just being too optimistic in hoping that we can find a [relatively] 
> dead-simple solution, one that doesn’t require:
>   1. the music being broken up into variables and knitted back together;
>   2. multiple (and often redundant key signatures/changes and 
> \transpose-itions;
>   etc.
> ??
>
> Has someone already invented this wheel, and I just don’t know about it?
>
> Thanks,
> Kieren.
>
> %%%  SNIPPET BEGINS
> \version "2.19.56"
>
> \paper { line-width = 6\in }
>
> flute = {
> \set Staff.instrumentName = "Flute"
> \set Staff.shortInstrumentName = "Fl."
> \transposition c
> }
> altoflute = {
> \set Staff.instrumentName = "Alto Flute"
> \set Staff.shortInstrumentName = "A. Fl."
> \transposition g
> }
> toF = \markup "take flute"
> toAF = \markup "take alto flute"
>
> global = {
> \key c \major s1 \break
> \key d \major s1 \break
> \key e \major s1 \break
> }
>
> flutepart = {
> \flute
> a'2 r^\toAF
> \altoflute
> a'2 r^\toF
> \flute
> a'2 r
> }
> flutepart_tr = {
> \key c \major
> \flute
> a'2 r^\toAF \break
> \altoflute
> \transpose c f { \key d \major a'2 r^\toF } \break
> \flute
> \key e \major
> a'2 r
> }
>
> \markup \bold "C score:"
> \score {
> \new Staff << \global \flutepart >>
> }
>
> \markup \vspace #4
> \markup \bold "Transposed score/part (incorrect):"
> \score {
> \new Staff << \global \flutepart >>
> }
>
> \markup \vspace #4
> \markup \bold "Transposed score/part SHOULD look like:"
> \score {
> \new Staff \flutepart_tr
> }
> %%%  SNIPPET ENDS
>
> 
>
> 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

-- 
u...@openlilylib.org
https://openlilylib.org
http://lilypondblog.org


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


state-of-the-art multi-instrumental/transposing mechanism

2017-03-05 Thread Kieren MacMillan
Hi all,

Inspired by the “tweaking clefs” thread, I’m trying again to see if we can 
crowd-source a state-of-the-art multi-instrumentalist mechanism.

The snippet below (minimal, for these purposes?) demonstrates the problem I’m 
trying to solve.

Am I just being too optimistic in hoping that we can find a [relatively] 
dead-simple solution, one that doesn’t require:
  1. the music being broken up into variables and knitted back together;
  2. multiple (and often redundant key signatures/changes and \transpose-itions;
  etc.
??

Has someone already invented this wheel, and I just don’t know about it?

Thanks,
Kieren.

%%%  SNIPPET BEGINS
\version "2.19.56"

\paper { line-width = 6\in }

flute = {
\set Staff.instrumentName = "Flute"
\set Staff.shortInstrumentName = "Fl."
\transposition c
}
altoflute = {
\set Staff.instrumentName = "Alto Flute"
\set Staff.shortInstrumentName = "A. Fl."
\transposition g
}
toF = \markup "take flute"
toAF = \markup "take alto flute"

global = {
\key c \major s1 \break
\key d \major s1 \break
\key e \major s1 \break
}

flutepart = {
\flute
a'2 r^\toAF
\altoflute
a'2 r^\toF
\flute
a'2 r
}
flutepart_tr = {
\key c \major
\flute
a'2 r^\toAF \break
\altoflute
\transpose c f { \key d \major a'2 r^\toF } \break
\flute
\key e \major
a'2 r
}

\markup \bold "C score:"
\score {
\new Staff << \global \flutepart >>
}

\markup \vspace #4
\markup \bold "Transposed score/part (incorrect):"
\score {
\new Staff << \global \flutepart >>
}

\markup \vspace #4
\markup \bold "Transposed score/part SHOULD look like:"
\score {
\new Staff \flutepart_tr
}
%%%  SNIPPET ENDS



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