MIDI import malfunctions
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
When doing MIDI imports of more than 8 tracks, it only shows the first 15 tracks in the MIDI, plus the percussion track. When there are changes in volume, it shows all of the automations (as if all MIDI tracks are present).
An even stranger part to this bug is that the MIDI tracks after the 15th MIDI track have their patches placed on the first 8 MIDI tracks. In other words, the MIDI tracks after track 15 will be place on the first MIDI tracks (16 will go to 1, 17 will go to 2, 18 will go to 3, ... 22 will go to 7, 23 will go to 8, and so forth). So, if there are 24 MIDI tracks, MIDI tracks 1 through 8 will have the MIDI patches of MIDI tracks 16 through 23 (assuming MIDI track 24 is the percussion track).
I found this out as an LMMS bug because I tried it out on a different type of software (such as MuseScore (as a composition software) or FL) and they were imported normally.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the MIDI import with more than 24 tracks and compare the imported track and patch assignments with MuseScore or FL. Trace the MIDI import workflow and verify that all tracks, percussion, patches, and volume automations remain correctly associated; the issue is done when extra tracks no longer overwrite the first tracks.
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