LMMS / LMMS/lmms

Default instrument volumes are very inconsistent: What should be done?

Open
#7,852 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

The volumes of TripleOscillator, Organic, ZynAddSubFX, Nescaline, etc. are quite different from each other, and it can be a little weird to be using one instrument and then drag in another insturment which has a wildly different volume, and have to fix it.

Ideally, I think all the instruments would have roughly the same default volumes.

Image

I performed a small test by running the same note through all the instruments and recording the volume of each.

Image

Should we fix this? If so, how? We can't really adjust the default volume of a synthesizer without either

  1. Changing the track volume knob value
  2. Changing the internal output volume of the instrument, and adding an upgrade routine to adjust the volumes of instruments in old projects.
    • Either as a per-instrument default volume multiplier (some kind of overridable property/function)
    • Or by literally changing how each instrument generates audio to be louder/quieter
    • Or in some cases, like zynaddsubfx, simply changing the default value of the internal master volume knob

None of these options seem ideal. Either there would be odd default volume knob positions, potential backward compatibility issues, or just be an odd solution.

What should be done?

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 comparing the default output volumes of TripleOscillator, Organic, ZynAddSubFX, Nescaline, and the other instruments named in the issue. Review the listed options for changing track or internal instrument volume, then define an approach that addresses consistency and backward compatibility; no files or tests are named.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
audio-video-rtc
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.