Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

MIDI import only detects overlaps from same start time (rather than same end time also)

未关闭
#1,856 4 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
backend

调研方向

Start by running the reproduction snippet on the attached repro-src.mid and comparing repro-exported.mid against it. The title points at MIDI import detecting overlaps by shared start time but not shared end time, so check how tied notes are grouped when a bass note joins the chord. Done means the exported file holds the C3/E5 chord through beat one of measure 2 without re-attacking it, and the single-track case matches the multi-track workaround.

由索引模型根据 Issue 内容生成。

描述

music21 version

9.9.1

Operating System(s) checked
macOS 26.2

Problem summary

In some cases, importing then re-exporting a MIDI file with a note tied across a measure causes the note to repeat.

Steps to reproduce

from music21 import *
f = converter.parse('repro-src.mid')
f.write('midi', "repro-exported.mid")

Where:

  • repro-src.mid is a MIDI type 1 file with a single track, rendering this:
Image

Expected vs. actual behavior

  • Expected: The exported MIDI file represents the same musical intention as the source--that is, the C3/E5 chord is held through the first beat of the 2nd measure.
  • Actual: The exported MIDI file doesn't tie the C3/E5 chord, but rather plays it again at the beginning of the measure, as if it was written:
Image

More information

I've tried multiple variations of this and found a few different behaviors that all seem to be related, but I'm not sure what the actual expected behavior should be given the structure of the source MIDI. Is my program required to "clean up" or parse the MIDI file into separate tracks somehow before having music21 export it?

  • If you show() the file, the score looks even different from the exported MIDI: it plays the A4 notes in series with the C3/E5 chord, not simultaneously
Image
  • If I edit the MIDI file to have the E5 and the A4 notes on one track, and the C3 on a second track (e.g., export the C3 onto a bass clef), everything works as expected. The exported file has 3 tracks, with the E5 and A4 notes on track 2, and the C3 on track 3.
Image
  • If I remove the C3 note so that only the E5 is tied, the export works as expected. It seems like something about adding the bottom note is causing the midi export to be wonky. (Note however that in this case, show() still renders the A4 notes in series with the E5, rather than simultaneously with it.)
Image
  • The MIDI files in question are mechanically generated, so there shouldn't be any question of duration variance causing problems.

I've attached the source and exported MIDI files for context.

主要语言
Python
星标
2.6k
派生
459
平均合并
1 天 1 小时
30 天内合并 PR
42

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cuthbertLab/music21 的其他 Issue

查看 cuthbertLab/music21 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。