[EMAIL PROTECTED] wrote:
>
> Hi,
>
> this tiny m-tx excerpt shows a situation where 2 adjacent "chords"
> should be slured. (m-tx V0.52)
> There _is_ a nice slur for the bottom notes, but the top slur comes out
> far too short...
>
> Did I miss something "basic" or is there a special trick to code this
> properly?
>
> %-----------------------------------------------------------------
> Title: OneBar-Slur-Problem
> Sharps: 3
> Style: Piano
> Meter: 4/4
> Bars/Line: 2
>
> [+4 d1 za+ a- r (1 cn (2u za+ ] [+4 c- )1 za+ )2u a- cs zg+ a- ] r2 |
> r0
> %-----------------------------------------------------------------
The M-Tx code that translates ( and ) to PMX slurs is older than the
PMX labelled slur feature, and does not take into account that slurs
may be put on chordal notes.
There are two ways to solve your problem:
1. Select the "s" option, i.e.
Options: s
in the preamble. This tells M-Tx to leave slurs as they are,
instead of translating them to "s" and/or "t".
2. Code PMX "s" and "t" slurs direcly. Since you don't have lyrics,
it does not matter that M-Tx can't see the slurs.
In either case you should use the "t" option on the slurs, because
for a tie that looks nicer. So your code becomes
1. ("s" option selected)
[+4 d1 za+ a- r (t cn (2ut za+ ] [+4 c- )t za+ )2ut a- cs zg+ a- ] r2 |
2. (PMX slurs coded directly)
[+4 d1 za+ a- r cn st za+ s2ut ] [+4 c- st za+ s2ut a- cs zg+ a- ] r2 |
Note that only one of the slurs needs a label.
Dirk
