LMMS / LMMS/lmms

Plugin blacklist

Open
#5,771 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

A file answering the Question
```
Q(T, P, PV, H, HV):
Are there known issues with
* Plugin P
* of Type T (LADSPA, Lv2, VST2, VST3, ...)
* in Plugin-Version PV
* in Host H in Host-version HV?
```

#### Justification

Some plugins may be defective, causing ear or speaker damage. E.g. #5767 or test reports from #5761 .

#### Open Questions:

1. Should the blacklist be a separate repo (submodule)? In my opinion: Yes. It can be useful for other DAWs.
2. What file format would be suited? Maybe a simple config file, like
```
# lv2 plugins with the URI specified are buggy in versions 2.4.1 - 2.4.3 in LMMS in versions 1.0.0 to 1.2.0
lv2 http://lsp-plug.in/plugins/lv2/crossover_ms 2.4.1-2.4.3 LMMS 1.0.0-1.2.0
# ladspa plugins with ladspa ID 1902 from version 1.0.0 to current are buggy in all hosts in all versions
ladspa 1902 1.0.0- all all
```
3. ...?

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. First resolve whether the blacklist belongs in a separate repository or submodule and choose a file format that can represent plugin type, identifier, version ranges, host, and host-version ranges; done means the scope and implementation location are agreed.

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.