<commit_before># DPF - DISTRHO Plugin Framework

Even though DPF is quite liberally licensed, not all plugin formats follow the same ideals.  
This usually due to plugin APIs/headers being tied to a specific license or having commercial restrictions.  
This file describes the licensing that applies to each individual plugin format as a way to make it clear what is possible and compatible.  
Note that if you are making GPLv2+ licensed plugins this does not apply to you, as so far everything is GPLv2+ compatible.

Regardless of target format, DPF itself needs to be mentioned in attribution.
See the [LICENSE](LICENSE) file for copyright details.

| Target          | License(s)           | License restrictions  | Attribution |
|-----------------|----------------------|-----------------------|-------------|
| JACK/Standalone | MIT (RtAudio)        | Copyright attribution | **RtAudio**: 2001-2019 <NAME> |
| LADSPA          | LGPLv2.1+            | ???                   | 2000-2002 <NAME>, <NAME>, <NAME> |
| DSSI            | LGPLv2.1+            | ???                   | **DSSI**: 2004, 2009 <NAME>, <NAME> and <NAME>;<br/> **ALSA**: 1998-2001 <NAME>, <NAME>, <NAME> |
| LV2             | ISC                  | Copyright attribution | 2006-2020 <NAME>, <NAME>;<br/> 2000-2002 <NAME>, <NAME>, <NAME> |
| VST2            | GPLv2+ or commercial | Must be GPLv2+ compatible or alternatively use Steingberg VST2 SDK (no longer available for new plugins) | GPLv2+ compatible license or custom agreement with Steingberg |
| VST3            | ISC                  | Copyright attribution | (none, only DPF files used) |<commit_msg>Add special licensing note for LADSPA and DSSI<commit_after># DPF - DISTRHO Plugin Framework

Even though DPF is quite liberally licensed, not all plugin formats follow the same ideals.  
This usually due to plugin APIs/headers being tied to a specific license or having commercial restrictions.  
This file describes the licensing that applies to each individual plugin format as a way to make it clear what is possible and compatible.  
Note that if you are making GPLv2+ licensed plugins this does not apply to you, as so far everything is GPLv2+ compatible.

Regardless of target format, DPF itself needs to be mentioned in attribution.
See the [LICENSE](LICENSE) file for copyright details.

| Target          | License(s)           | License restrictions  | Attribution |
|-----------------|----------------------|-----------------------|-------------|
| JACK/Standalone | MIT (RtAudio)        | Copyright attribution | **RtAudio**: 2001-2019 <NAME> |
| LADSPA          | LGPLv2.1+            | ??? (*)               | 2000-2002 <NAME>, <NAME>, <NAME> |
| DSSI            | LGPLv2.1+            | ??? (*)               | **DSSI**: 2004, 2009 <NAME>, <NAME> and <NAME>;<br/> **ALSA**: 1998-2001 <NAME>, <NAME>, <NAME> |
| LV2             | ISC                  | Copyright attribution | 2006-2020 <NAME>, <NAME>;<br/> 2000-2002 <NAME>, <NAME>, <NAME> |
| VST2            | GPLv2+ or commercial | Must be GPLv2+ compatible or alternatively use Steingberg VST2 SDK (no longer available for new plugins) | GPLv2+ compatible license or custom agreement with Steingberg |
| VST3            | ISC                  | Copyright attribution | (none, only DPF files used) |

### LADSPA and DSSI special note

The header files on LADSPA and DSSI are LGPLv2.1+ licensed, which is unusual for pure APIs without libraries.  
LADSPA authors mention this on ladspa.org homepage:

> LADSPA has been released under LGPL (GNU Lesser General Public License).
> This is not intended to be the final license for LADSPA.
> In the long term it is hoped that LADSPA will have a public license that is even less restrictive, so that commercial applications can use it (in a protected way) without having to use a derived LGPL library.
> It may be that LGPL is already free enough for this, but we aren't sure.

So the situation for LADSPA/DSSI plugins is unclear for commercial plugins.  
These formats are very limited and not much used anymore anyway, feel free to skip them if this situation is a potential issue for you.
{'fraction_non_alphanumeric': 0.11744804253262446, 'fraction_numerical': 0.029966167230546157, 'mean_word_length': 2.580449826989619, 'pattern_counts': {'":': 0, '<': 37, '<?xml version=': 0, '>': 41, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 8, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6832517', 'n_tokens_mistral': 1205, 'n_tokens_neox': 1064, 'n_words': 512}