LMMS / LMMS/lmms

velocity, pan and other1, other2, and so one

Open
#7,407 3 comments 0 reactions 0 assignees View on GitHub
core enhancement gui in progress
Dominant language
C++
Stars
10.4k
Forks
1.3k
Avg merge
2d 13h
Merged PRs (30d)
7

Description

### Enhancement Summary

since velocity and pan is not enough, we should add our own effects into the track
The "other" property controls an effect assign to it
For example, if i wanted a note to be reverb, i can change the "other" properties so that 1 note has reverb, while the other doesnt

yes, i've made this suggestion 2 times. No, im not a fan of the previous one

### Implementation Details / Mockup

1. add an effect
2. go to track options -> midi -> assign effect (name it whatever you want. In this case, "Effect")
3. choose the desired effect (we will be going with wet amount, Reverb
4. Now you have Velocity, pan and Effect
![Untitled_ - LMMS 1 3 0-alpha 1 667+g1c865843f 30_07_2024 2_04_32 PM](https://github.com/user-attachments/assets/ab39a7ef-b940-432f-a778-e9a18ebc760c)
![Capture0](https://github.com/user-attachments/assets/545ab382-d3b9-4adb-ac25-21a9913f0cf0)

### 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

Research direction

Start by tracing LMMS's Track Options > MIDI controls and the existing velocity/pan assignment path; no source files or tests are named in the issue. Compare the proposed per-note effect assignment and mockups with current effect handling, then define acceptance criteria for choosing an effect and applying it to one note without affecting others.

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.