[MEI-L] Barline issues

[Reinier de Valk]

Hello all,

Here is an issue that I hope is not too difficult to solve. (I also posted
this on the MEI Slack channel - apologies if you already saw it there.)

I have a transcription, in CMN, of a piece in tablature, with the tablature
shown on top of the CMN system. The problem now is that the piece is in
3/2, but the tablature is 'barred' as if it were in 2/2 - so with a barline
every (equivalent of a) two half notes - and I can't get this to show
correctly.

I would like to keep the tablature barring, but also the actual metric
barring - i.e., a tab barline in the tab staff after every two half notes,
and a metric barline in the CMN staff after every three.

My initial thought was to use <barLine> in the tablature staff, and this
almost works - the problem now is that the metric barlines coming from
<measure> extend up to the tab staff, dividing some tab bars in two. See
the attached example 1 (circled in red are the problem areas). As the
example shows, the final barlines also don't line up, but I could just
remove all <barLine>s that coincide with a metric barline coming from
<measure> to solve that.

So regarding this first solution, I would like to know if it is possible to
have the metric barline NOT extend up to the tablature staff. I guess this
should be regulated in the <tabGrp>, but I could not figure out how.

As an alternative solution, I set all barlines coming from <measure> to
invisible, and 'hardcoded' <barLine>s wherever I need them. This also
almost works - but now I get two separate barlines in the upper and lower
CMN staves (see example 2 attached) - while I want a single barline that
connects both staves. Again, I tried several things, but couldn't get it to
work.

Regarding this second solution the following question: how could I replace
the separate staff-wide barlines with one barline that spans both CMN
staves?

And then finally: which of these approaches would be preferable? I like the
first one best (minimal adaptation) - if I can get it to work. Or is there
yet another, better solution to my problem?

I've also attached the encodings for both examples.

Any help would be greatly appreciated!

With best wishes,
Reinier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20220723/560597de/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: barring_example_2.xml
Type: text/xml
Size: 14045 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20220723/560597de/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: barring_example_1.xml
Type: text/xml
Size: 13757 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20220723/560597de/attachment-0001.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: barring_example_2.png
Type: image/png
Size: 23611 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20220723/560597de/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: barring_example_1.png
Type: image/png
Size: 26878 bytes
Desc: not available
URL: <http://lists.uni-paderborn.de/pipermail/mei-l/attachments/20220723/560597de/attachment-0001.png>