The tie object | MNX specification

# The tie object

Type: Dictionary

The tie object represents a single tie between two notes. A tie is only encoded on the first note — i.e., the note that starts the tie.

In the common case of simple ties, use "target" to specify the tie's end note.

For laissez vibrer ties — which do not have a particular destination note — omit "target" and use "lv" instead.

## Attributes

Name | Type | Required? | Description
--- | --- | --- | ---
lv | boolean | No | Specifies that this tie is a laissez vibrer tie — which does not have a particular destination note. If this attribute is omitted, the value is assumed to be false.
side | slur side | No | Specifies whether the tie curves upward or downward. If not provided, the consuming software should determine the value automatically according to its own logic.
target | ID | No | The ID of a note that ends this tie. The start note and end note must be in the same part (i.e., it's not allowed for a tie to start in one part and end in a different part). The end note must have the same sounded pitch as the start note — but the two notes are allowed to use different note spellings, as long as those spellings are enharmonically equivalent. If "target" is omitted, "lv" is required with a value of true.
targetType | tie target type | No | Specifies the relationship of the tie's start note to its target (end) note. Generally, most ties are "nextNote", meaning the tie connects notes that are in consecutive events. The other supported values — "arpeggio", "crossVoice" and "crossJump" — describe less frequent situations of music notation. Many simpler notation applications make the assumption that ties are always in consecutive events. This attribute exists as a hint for these applications, so that they can include or exclude ties accordingly. For example, a simple notation-display application may decide to ignore all ties that don't have targetType "nextNote". If this attribute isn't provided, behavior is undefined. In this case, consuming applications may decide how (or whether) to parse the tie, according to their own algorithms. For example, a simple algorithm might be: only honor this tie if the "target" note lives in the subsequent event. It is an error to use this attribute if "lv" is true.

Plus globally available attributes: _c, _x, id

## Parent objects

This object is used by the following parent objects:

- note: "ties"

## Examples

This object is used in the following examples:

Organ layout, Tie targets, Ties