[MEI-L] Place text on staves

[Craig Sapp]

Hello Daniel,

How you encode the Tacet will depend on the purpose of the encoding, i.e.,
what you plan to do with the encoding after you have finished encoding it.
If you want a photocopy of the score, then you can encode in a way that
says there is a blank staff in the music that happens to have some text on
it.  If you want to manipulate the data afterward to generate a modern
style score, render a MIDI file, etc., then this "Tacet" text represents
rests at a deeper structural level than the visible content and so should
be encoded to reflect that.

Perry Says:
> No, I think <space> is the appropriate markup in this case.
> <space> fills up time; i.e., it has duration. <pad> has visual size, but
doesn't have duration.

"Tacet" is a shorthand for the part resting for an entire section of the
music, however, @dur/@dots for a <space> are limited to printable rhythms.
It is not possible to represent "20 breves" with those attributes.  Could
@dur.ges be used to represent the duration of 20 breves?   This is closer
to <mSpace>, although there are no measures (or technically there is one
measure?).

In other words, the "Tacet" text represents a duration in this case, so it
should be given a duration or used in parallel with something that has
duration.  The element possessing the duration is "invisible".  The tacet
line should be encoded in its own <mdiv> or at least <section> as well.

If you want it both ways, then this music should be encoded in <part>
rather than <score>, and the part version can be more literal, while the
score encoding could be more structural by accounting for the rests.

Take this page of music from a trumpet part from an orchestral work for a
modern equivalent:

[image: Inline images 1]

page 10 of
http://scores.ccarh.org/mendelssohn/elijah/parts/current/mendelssohn-elijah-trpt1.pdf
if the image does not get through the mailing system.

Notice that the truplet is "tacet" in movements/sections 23, 24, 25, 27,
28, and 29.  The trumpet will not immediately start playing the music for
no. 30 after they have finished playing no. 26 (otherwise they will be
fired).

-=+Craig





On 9 March 2017 at 11:53, Daniel Alles <DanielAlles at stud.uni-frankfurt.de>
wrote:

> In fact, my "tacet" is also followed by notes on the next page. Until now
> I did not encode line breaks because I encoded each of the six parts of
> each Magnificat as <section>, the lines only separated optically using <!--
> x. line -->. But thinking about reproducing the source - wouldn't it be
> better to encode all the lines at once, without <section>, but with line
> breaks?
>
> I don't get the difference between <space> and <pad>, could please someone
> explain that a little bit?
>
> Thank you and good night,
> Daniel
>
>
>
> Zitat von Anna Plaksin <annplaksin at gmx.net>:
>
> Hi Perry,
>>
>>
>>
>> according to your mail yesterday, wouldn’t <pad> here also be more
>> appropriate, because Daniel wants to reproduce the source?
>>
>> In fact, my example displayed a similar situation. There is a visual
>> padding and a text directive “Tacet” which intends logically time, where
>> that particular voice remains silent while the others are singing. The
>> difference is, that in my example the directive is followed by notes and in
>> Daniel’s it is vice versa.
>>
>> As it seems to me, we have to decide here whether we want to encode the
>> visual information or the logical. But the question is: which decision fits
>> better to the encoding approach of “representing a source”?
>>
>>
>>
>> Best wishes,
>>
>> Anna
>>
>>
>>
>> Von: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] Im Auftrag von
>> Roland, Perry D. (pdr4h)
>> Gesendet: Donnerstag, 9. März 2017 16:23
>> An: Music Encoding Initiative <mei-l at lists.uni-paderborn.de>
>> Betreff: Re: [MEI-L] Place text on staves
>>
>>
>>
>>
>>
>> Since this is mensural notation, @tstamp won't work.  Instead, use
>> <space> as a placeholder in the 2nd staff and associate the text with the
>> space via @startid --
>>
>>
>>
>> <staff n="1">
>>
>>   <layer>
>>
>>     <!-- notes -->
>>
>>   </layer>
>>
>> </staff>
>>
>> <staff n="2">
>>
>>   <layer>
>>
>>     <space xml:id="space01"/>
>>
>>   </layer>
>>
>>   <dir startid="#space01">... Tacet</dir>
>>
>> </staff>
>>
>>
>>
>> --
>>
>> p.
>>
>>
>>
>>
>>
>> From: mei-l [mailto:mei-l-bounces at lists.uni-paderborn.de] On Behalf Of
>> Raffaele Viglianti
>> Sent: Thursday, March 09, 2017 9:25 AM
>> To: Music Encoding Initiative
>> Subject: Re: [MEI-L] Place text on staves
>>
>>
>>
>> Hello,
>>
>>
>>
>> I think <dir place="within"> is the most appropriate element given that
>> the text gives an instruction. You can use @tstamp to position it based on
>> time.
>>
>>
>>
>> Raff
>>
>>
>>
>> On Thu, Mar 9, 2017 at 7:08 AM, Daniel Alles <
>> DanielAlles at stud.uni-frankfurt.de <mailto:DanielAlles at stud.uni-f
>> rankfurt.de> > wrote:
>>
>> Dear all,
>>
>> in my source, there often appears the playing instruction "Tacet" written
>> directly on a staff (see attachment). How can I reproduce that in MEI? I
>> always try to reproduce the source as accurately as possible, but couldn't
>> find a possibility to put this text on the staff. Is that possible at all?
>> <dir> seems not to work, as there are no notes in that staff.
>>
>> Best, Daniel
>>
>> _______________________________________________
>> mei-l mailing list
>> mei-l at lists.uni-paderborn.de <mailto: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/20170309/d42460a5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-03-09 at 11.59.22 AM.png
Type: image/png
Size: 304384 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20170309/d42460a5/attachment.png>