On Tue, 20 Jan 2015 08:51:13 -0800, Kieren MacMillan
wrote:
2. What would be required so that the \bar "||” \key \default stuff could be
avoided
It is awkward to make this happen with an add-on to current LilyPond.
Jan-Peter took the approach of watching for transposition changes in his
au
Hi Keith,
> By saying "reedPlayer stores written pitches", I meant only that the
> \transpose{...} operations, to tell LilyPond which notes should be printed at
> which transposition, were included in the variable reedPlayer.
Thanks for the clarification.
> You could try the attached modificat
On Sun, 18 Jan 2015 19:34:24 -0800, Kieren MacMillan
wrote:
This does have the variable reedPlayer storing written pitches, where we
recommend storing concert pitches
I would much rather code in concert pitches.
What I was suggesting, and what I put into the example, had all the typed inp
On Sun, 18 Jan 2015 21:09:07 -0800, Paul Scott wrote:
So I am saying that I would like any new features for instrument switching to
suit my need to
not always enter the notes in concert pitch. I don't really think that be a
problem.
Absolutely.
There is a set of tests to make sure the ol
Hi all,
> I certainly understand that as being the most common need.
And apparently the one we officially recommend in the documentation. =)
> However I am not a composer. I am in the position of either adapting an
> existing book
> for younger players who may not be able to play all the instr
On Mon, Jan 12, 2015 at 07:29:39AM -0500, Kieren MacMillan wrote:
> Hi Keith,
>
> > I guess you enter the notes in concert pitch, then ?
>
> Yes — I can’t imagine entering it any other way and maintaining my sanity. :)
I certainly understand that as being the most common need. However I am not
Hi Keith,
Thanks for adding the issue to the tracker — it’s a great starting place.
> You have to admit that this does (accidentally) make it sound a bit like you
> are looking for a convenient way to write music with no regard for the
> instrument.
Not at all. I inhabit [at least] three roles
On Tue, 13 Jan 2015 05:54:48 -0800, Kieren MacMillan
wrote:
I understand that in realistic cases you probably have the notes in one
variable and options for arrangements in another parallel sequence
flute_notes = {c'2 c'' }
arrangementB = {s1*4 \prep_alto_flute s1*4 \switch_alto_flute
Hi David,
> I've never quite found the right term for this.
> 'Player' isn't bad, although I would also suggest considering the following:
> 'folder', 'chair', 'stand' or 'desk’.
But (as you go on to point out) a “folder", “stand", or “desk" could certainly
encompass more than one player — and
On Wed, Jan 14, 2015 at 6:55 AM, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> > You want to write music as if it is for a single voice
> A single *player*…
A very interesting concept.
Trick question: where in lilypond is the concept of a 'player' modeled?
I've never quite found t
Hi David,
> You want to write music as if it is for a single voice
A single *player*…
> You are essentially writing polyphonic material (albeit, one voice is playing
> rests at any one time.)
That’s a valid, but non-intuitive, way of looking at it… I like your
outside-the-box thinking! =)
>
Am 12.01.2015 um 13:29 schrieb Kieren MacMillan:
Do you use the \quoteDuring mechanism (as below) or Jan-Peter's
auto-transposing engraver to generate the engraved pitches for each instrument?
Neither. I simply use \transpose.
(I was planning to look at Jan-Peter’s engraver, but haven’t yet ha
> From: Kieren MacMillan
> To: Keith OHara
> Cc: Lilypond-User Mailing List
> Subject: Re: instrumentSwitch and addInstrumentDefinition use
>
>
> Hi Keith,
>
> > I understand that in realistic cases you probably have the notes in one
> variable and options for
Hi Keith,
> I understand that in realistic cases you probably have the notes in one
> variable and options for arrangements in another parallel sequence
> flute_notes = {c'2 c'' }
> arrangementB = {s1*4 \prep_alto_flute s1*4 \switch_alto_flute s1*8 }
> and it is not so convenient to break
Hi Keith,
thanks for that snippet! It should be possible to add KeySignatures to
the edition-engraver ... and to automatically create a KeySig on change
of instrument transposition ...
Cheers,
Jan-Peter
Am 12.01.2015 um 06:28 schrieb Keith OHara:
> ...
>
> \version "2.19.15"
> transpositionUpda
On Mon, 12 Jan 2015 06:36:15 -0800, Kieren MacMillan
wrote:
how I *want* to use it:
flute_part = {
c'2 c'' |
b'4 g'8 a' b'4 c'' |
c'2 a' |
g'2. r4 |
\prep_alto R1*4 | % [input below in concert pitch] \play_alto a2 f' | %[
desired typeset d'2 bes' ...]
e'4 c'8 d' e'4
Hi Keith,
Thanks for the function and snippet. Here is a [compiling, but non-functional]
revision showing how I *want* to use it:
SNIPPET BEGINS
\version "2.19.15"
transpositionUpdateKey =
#(define-music-function (parser location new-transposition) (ly:pitch?)
(_i "Set instrument transp
Hi Keith,
> I guess you enter the notes in concert pitch, then ?
Yes — I can’t imagine entering it any other way and maintaining my sanity. :)
> Do you use the \quoteDuring mechanism (as below) or Jan-Peter's
> auto-transposing engraver to generate the engraved pitches for each
> instrument?
On Sun, Jan 11, 2015 at 03:36:43PM -0500, Kieren MacMillan wrote:
> Hi all,
>
> >> Is anyone using instrumentSwitch that can explain what the various
> >> variables in addInstrumentDefinition mean?
> >
> > Don't use instrumentSwitch. It is a pointless frustrating waste of time.
>
> I agree. An
On Sun, 11 Jan 2015 12:36:43 -0800, Kieren MacMillan
wrote:
So LilyPond does not store a global key signature.
No, but as you well know, many (most?) Lilypounders abstract the key signature
(etc.)
into their own global [variable](s).
Right, but LilyPond doesn't know if that is the concert
Hi all,
>> Is anyone using instrumentSwitch that can explain what the various
>> variables in addInstrumentDefinition mean?
>
> Don't use instrumentSwitch. It is a pointless frustrating waste of time.
I agree. And I’m particularly irritated about that fact, since I was the one
who sponsored (
Paul Scott ultrasw.com> writes:
> Is anyone using instrumentSwitch that can explain what the various
> variables in addInstrumentDefinition mean?
Don't use instrumentSwitch. It is a pointless frustrating waste of time.
(The same could be said for LilyPond, except that there is sometimes a
poin
Hi,
version 2.19.15:
Is anyone using instrumentSwitch that can explain what the various
variables in addInstrumentDefinition mean?
I don't care about the midi transposition. AFAIK I really only
want the key signature to change automatically when I do an
instrument switch.
In the following e
23 matches
Mail list logo
