Skip to content

Tempo and Dynamics , Symbols and Text, Inertia vs. Change #453

@dougheyer

Description

@dougheyer

Sorry for the formality of my comments here, but I have previously had trouble explaining these ideas to others.

I have looked at some of the discussions related to
(1) Tempo Marks and tempo-related text (accel., rit., a tempo, etc.) and
(2) Dynamics symbols (Hairpins) and dynamics-related text (cresc., dim., etc.)

Tempo and Dynamics have a few things in common:
(1) at any point in time they both exist in one of two states: static or changing, and
(2) both can be represented by (graphic) symbols and/or text, and
(3) both are subject to their location on the timeline of music, and
(4) both can be treated in a similar way while in a state of change, and
(5) both are regarded in a similar way by human performers.

If there is disagreement about the above, then I think we need to take an empirical look at how it can be otherwise.

Based on this reasoning I would conclude that
(1) tempo-related text should be an optional, visible attribute of Tempo Mark, with an appropriate combination of text and BPM attributes working together to form a more meaningful, useful, and flexible tempo element, and
(2) dynamics-related text should be an optional, visible attribute of Dynamics, with an appropriate combination of text and Hairpin attributes working together to form a more meaningful, useful, and flexible dynamics element.

In both cases X and Y offsets would be required for the text.

P.S. - Is there a good reason why "dynamics" such as "sfz" should not be considered to be Accents rather than Dynamics?

Also sorry, I haven't quite figured out how to use markup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions