[MEI-L] sounding vs. written pitch, <octave>

[Roland, Perry D. (pdr4h)]

> But how you encode it, it's a fourteenth higher.

Ha!  You got me.  I was taken in hook, line, and sinker, by the boundary between octaves.  

My clumsiness aside, I had hoped to demonstrate in a follow-up post that while the values in the *.ges attributes can reflect the result of applying the octave shift, they shouldn't.  Doing so results in a "double encoding" of the octave designation -- once in the <octave> element and again in @oct.ges.  If the <octave> element is altered or removed, then @oct.ges has to be recalculated.

With the correct markup, i.e.,

<note
   pname="c" oct="4"
   pname.ges="b" accid.ges="f" oct.ges="4"/>

or, since the transposition itself doesn't involve an octave shift and therefore, there's no change in the note-level specification of octave,

<note
   pname="c" oct="4"
   pname.ges="b" accid.ges="f"/>

adding an <octave> element, modifying it to be "15va", or removing it doesn't change the note-level markup.  This facilitates editing in a software editor.

It does mean that MIDI generation has to be aware that this note is affected by an octave shift.  This process might be aided by the addition of @plist on <octave> so that a linkage could be maintained between the <octave> element and the note it affects.  I don't think a pointer in the other direction, from <note> to <octave>, would be as effective.

--
p.



> -----Original Message-----
> From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of
> Thomas Weber
> Sent: Wednesday, March 15, 2017 11:42 AM
> To: Music Encoding Initiative
> Subject: Re: [MEI-L] sounding vs. written pitch, <octave>
> 
> Am 15.03.2017 um 15:49 schrieb Roland, Perry D. (pdr4h):
> >
> > <note
> >       pname="c" oct="4"
> >       pname.ges="b" accid.ges="f" oct.ges="5"/>
> >
> > In other words, where @oct.ges reflects the octave shift?
> >
> 
> 
> 
> Glad you asked, because now I can brag about how well-chosen my example
> was ;-).  The gestural pitch should be a minor seventh higher than the written
> pitch (because of <octave>).  But how you encode it, it's a fourteenth higher.
> This means, for some pitches, you'd end up with a different values in @oct and
> @oct.ges (for Bb Instruments, that's all pnames except for c), in some you
> don't.
> 
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l