LMMS / LMMS/lmms

Instrument container plugin

Open
#6,938 2 comments 2 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
  1. Add a container plugin capable of loading multiple other instruments (unlimited number).
  2. By extension, ability to assign and map user-input key(range) passed to Plugin, to instrument-received key(range), so it can map entire ranges, multiple keys, or an individual key. (C4->D5 of instrument1; D4-D5->C2-C3 of instrument2; C3-D3->B3,B4,B5 of instrument3 etc).
    Simply put: load multiple instruments, assign keyIn to keySent.
  3. The individual instruments may have a master volume knob or something similar to the W/D mix in the effect chain.
  4. The plugin may have a master ability to put filters, envelopes, stacking and effects, so it behaves like a typical instrument plugin but with the components just being more plugins.
  5. Additionally, ability to cycle through GUIs of component instruments would be useful. Especially over the same window.
Justification

Several possible use cases due to ability to load multiple instruments and assign keys.
Most common include:

  1. Drum pad / sound box functionality
  • Drumkits can be loaded as AudioFileProcessor instances for samples, but also Kicker, 3xOsc... no restriction on your percussive choices, as opposed to a typical idea of a drum kit that is limited to loading samples.
  • Since it can synthesize sounds too, it can function like an sfx Box of sorts. Highly convenient.
  1. Layering sounds and instruments
  • Multiple instruments playing the same sound. Useful from a sound design perspective.
Mockup

image

Note:

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

No source files, tests, or entry points are named. Start by reviewing linked issues #1460, #793, #443, #6118 and pull request #4075; the work is done only after the broad feature scope and implementation requirements are narrowed and agreed.

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.