[MEI-L] octaves and back

[Raffaele Viglianti]

Hi Johannes,

I think that by specifying the end point of <octave>, you would essentially
indicate the "reset" point, which would make "loco" vestigial, so encoding
it with just <dir> seems fine to me.

Having said that, I would consider a version of <octave> that is more like
a milestone like you suggest, but in that case we'd probably need a
schematron rule that makes sure that no end points are specified.

For example this would be odd:

<octave staff="1" tstamp="1" dis="8" dis.place="above" tstamp2="3m+1">8
va</octave>
and three measures later
<octave staff="1" tstamp="1" dis="0" >loco</octave>

The tstamp2 in the first octave must not be there to tessellate properly.
This It would also be harder to process, I guess.

Finally, if using "loco" as a marker for ending octave displacements is
common (I admit I haven't come across it, but that means nothing), then we
could consider a value for @lendsym to be "loco" - though I understand
there is no line, so maybe not. But something like that.

Raff

On Wed, Oct 19, 2016 at 9:36 AM, Johannes Kepper <kepper at edirom.de> wrote:

> of course we can specify an @endid or a @tstamp2 (even though this is
> sometimes a little complicated with our data), but I was looking for a way
> to encode the "loco" instruction written on the page. You're certainly not
> suggesting to include that text in the "opening" octave element. I'm just
> wondering of we really have to use the generic <dir> to encode this, or if
> it would be worthwhile to extend the definition of <octave> to allow a
> statement like "don't displace from here on". It's a little bit like an
> accidental, which is allowed to hold a natural, not only sharps and flats…
> (I'm aware that this is a foul comparison)
>
> jo
>
>
> > Am 19.10.2016 um 15:01 schrieb Laurent Pugin <lxpugin at gmail.com>:
> >
> > Not sure I got it right but I assume you need to provide an end point
> with either @endid or @tstamp2. Does this makes sense?
> >
> > Laurent
> >
> >
> > On Oct 19, 2016 2:17 PM, "Johannes Kepper" <kepper at edirom.de> wrote:
> > Hi all,
> >
> > just a quick question: When we run into an octave instruction (8va), we
> encode that using the octave element like so:
> >
> > <octave staff="1" tstamp"1" dis="8" dis.place="above">8 va</octave>
> >
> > However, how do we go back? The @dis attribute uses the data.OCTAVE.DIS
> data type, which only allows "8", "15" and "22". However, how do I encode a
> "loco" instruction? Wouldn't it be correct to do it with something like
> >
> > <octave staff="1" tstamp"1" dis="0">loco</octave>
> >
> > instead of a generic <dir> ?
> >
> > Thanks,
> > jo
> >
> > _______________________________________________
> > mei-l mailing list
> > mei-l at lists.uni-paderborn.de
> > https://lists.uni-paderborn.de/mailman/listinfo/mei-l
> >
> > _______________________________________________
> > mei-l mailing list
> > mei-l at lists.uni-paderborn.de
> > https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
>
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20161019/7d0a3008/attachment.html>