musescore / musescore/MuseScore

MIDI file does not import properly

Open
#28,129 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community MIDI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Import/export issue

Description with steps to reproduce

When you import this midi file, the tempo it shows is incorrect, and all the note values are stretched out by about a factor of 1.34 (the original MIDI is 33 bars long in 4/4, the MS4 MIDI import is 45 bars long, with the first three beats being silent, for 44.25 measures total)
The tempo that shows in Musescore Studio also isn't even the right tempo to sound the right speed with the elongated notes, either. (q = 161 in Musescore vs. q = 100 in the original file)

  1. Import the attached MIDI file
  2. Open the attached MIDI file in some kind of MIDI editor
  3. See the discrepancy in note lengths and tempo
Supporting files, videos and screenshots

Here's the original MIDI view for the first few bars of the first track of the MIDI:

Image

Here's the Musescore Studio import of that same MIDI:

Image

Here's the MIDI file itself (Just rename it to remove the .zip, .mid is not a supported file extension on Github):

Legend of Zelda, The - Ocarina of Time (U) (V1.2) 00000063 00A62D40 Ganon's Castle.mid.zip

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.0-251430318, revision: github-musescore-musescore-69d5c0e

Regression

No.

Operating system

Reported on Windows 11

Additional context

I tried to import this file in Musescore 3, and it does the same behavior, with the rests added at the start and stretched tempo and note lengths

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by importing the attached MIDI file in MuseScore Studio and compare its tempo, note lengths, and leading silence with the original in a MIDI editor. Trace the MIDI import path from that reproduction; done means the file imports with the original timing, tempo, and bar count without the added initial rests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.