Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[MU3] Restrict the first exported MIDI track to timing events. #7523

Closed
wants to merge 1 commit into from
Closed

[MU3] Restrict the first exported MIDI track to timing events. #7523

wants to merge 1 commit into from

Commits on Feb 15, 2021

  1. Fix #207346: Restrict first track to timing events 

    Currently, exported MIDI files will have data events in the first MIDI
track. While this is not forbidden by the standard, the industry
convention is to only put timing related events in the first track, in
which case it is called a tempo track. MuseScore should follow that
convention because a lot of the available software assumes this
convention. This has been discussed and agreed upon in:

https://musescore.org/en/node/207346
    @OmarEmaraDev
    OmarEmaraDev committed Feb 15, 2021
    Configuration menu
    Copy the full SHA
    5149e9d View commit details
    Browse the repository at this point in the history