LMMS / LMMS/lmms

Custom control surface

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

Nobody has claimed this yet.

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

Description

### Enhancement Summary

Essentially [FL Studio's control surface](https://www.image-line.com/fl-studio-learning/fl-studio-online-manual/html/plugins/Control%20Surface.htm) plugin but in LMMS. This will probably need to wait until LMMS separates GUI from core, so I'm guessing this feature/plugin will be on the low ends of the list

### Implementation Details / Mockup

LMMS already has these control elements on its own (knobs, sliders, buttons), so I don't think any new elements are required to be created.
![Image](https://github.com/user-attachments/assets/223a50ae-5d7f-4896-8a46-3b1f1113a640)
![Image](https://github.com/user-attachments/assets/4c03a9d0-6aeb-46c6-9afe-322972f73a14)
![Image](https://github.com/user-attachments/assets/90da2aba-097d-4ee7-8138-f43b58464ad8)

The lingering issue is how the control surface would link to the various control elements in LMMS. We can already automate a lot of the elements in LMMS, but I'm not sure how that's done internally

### Please search the issue tracker for existing feature requests 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

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 studying LMMS's existing knobs, sliders, buttons, and automation mechanisms, then review the GUI/core separation mentioned in the issue. The work is done when a custom control-surface plugin can expose LMMS controls and link them reliably, but the issue does not name specific files or tests.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.