LMMS / LMMS/lmms

Cannot send MIDI input to multiple tracks at once

Open
#7,788 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

I have an external MIDI keyboard, and I want to use it to play all my instruments in LMMS. However, the MIDI input only goes to one track at a time (whichever track was selected last).
The behavior I expect instead would be: when the keyboard transmits MIDI data, all instrument receive data (if they're on the right channel).

https://github.com/user-attachments/assets/ff3c528b-204a-4828-aeeb-0af9223c4312

I believe this is a duplicate of #5866, but that issue never got a reply. I know there's a master MIDI thread #1472, but I don't know the etiquette for contributing to it. Based on #5499 and #7543, the "bug" i'm describing is intended behavior. Anyway, here's my two cents.

My keyboard can transmit MIDI on multiple channels, in a customizeable way. LMMS also lets me configure which instruments receive events from which channels. This should, in principle, let me play different instruments with different keys. However, only one track at a time can receive MIDI, so channels are entirely pointless. If I send notes on a channel different than the current track's channel, then no MIDI is received at all.

I seem to recall in older versions of LMMS, all instruments would receive MIDI input at the same time. I can understand why this was changed, since it can be chaotic and confusing. However, the new workflow is much more inefficient for me. Is there a setting to use the old behavior instead?

System Info
Debian GNU/Linux 11 (bullseye), GNOME 3.38.5, Intel® Core™ i5-8265U CPU @ 1.60GHz × 8
LMMS Version
1.3.0-alpha.1.787+7f2761d (Linux/x86_64, Qt 5.15.2, GCC 10.2.1 20210110).

Contributor guide

No contributing guide indexed for this repository

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

Review the related discussions in #5866, #1472, #5499, and #7543 before choosing an approach, since the issue says the current behavior may be intentional. Trace how LMMS handles MIDI input and channel routing, then define whether a setting or changed routing behavior should let multiple instruments receive matching channels; done means the requested multi-track workflow works without breaking the existing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.