LMMS / LMMS/lmms

MIDI Device detection lost after deleting track linked with MIDI input

Open
#8,028 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

### System Information

Gentoo, Ryzen 3 3200G, kernel 6.6.62, RX580, 16GB RAM, Gigabyte B450M, HGST 4TB HDD, alsa

### LMMS Version(s)

1.3.0-alpha.1.869+c86fe78 and lower

### Most Recent Working Version

Unknown/ Not Applicable

### Bug Summary

During the deletion of an unwanted track in the DAW, I had a connected MIDI keyboard (DONNER 25-key, though have had the same issue on various other models) detectable by LMMS. It could no longer be detected after deleting the track linked with it. Tried all the basic steps (restart app, restart keyboard, change MIDI mode, restart PC, etc) to no avail. This error is only in LMMS, as lsusb still detects the device

### Expected Behaviour

MIDI device should remain detectable and usable within LMMS after track deletion linked with MIDI device.

### Steps To Reproduce

Link a track (via MIDI input) with a physical MIDI keyboard on the ALSA Sequencer MIDI mode on Linux, then delete the track without first unlinking keyboard.

### Logs

_No response_

### Screenshots / Minimum Reproducible Project

_No response_

### Please search the issue tracker for existing bug reports before submitting your own.

- [x] I have searched all existing issues and confirmed that this is not a duplicate.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the failure with a physical MIDI keyboard in ALSA Sequencer MIDI mode, then trace MIDI input handling when a linked track is deleted. Confirm that deleting the track does not make the device unavailable in LMMS, and verify the device remains usable afterward without restarting the application.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
audio-video-rtc, operating-systems
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.