LMMS / LMMS/lmms

Handling GM Midi Drum set in Beat+Bassline Editor

Open
#3,374 18 comments 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

If one wants to use a GM drum of a soundfont, currently there are two ways for it (as far as I know):

  1. On a single track, using Piano Roll, or
  2. By adding several soundfont players in Beat+Bassline Editor.

See both versions here:

2017-02-19-232426_2304x1024_scrot

The problem with the first one that it loses the flexibility to manage in Song Editor (see top of the picture, with the lot of small patterns). The second one would be just great if there was a way to choose the sound to play in an easy way.

However, currently there is this lightgreen button over the piano keys (in window "kick", near C5 on screenshot), but this works kind of counter-intuitive, at least in this case. Often I am unable to figure it out, where to pull the green button to get the simple desired sound.

Would it be possible to have a way to choose the piano key directly? For example, by using right mouse button. Thank you very much!

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 reproducing the GM drum workflow in the Beat+Bassline Editor and inspect how the green piano-key control currently selects sounds. No source file or test is named in the issue, so trace the editor's piano-key interaction first. Done means users can choose a desired piano key directly and use it for GM drum sounds without relying on the difficult drag interaction.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
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.