[ANN] LSP Plugins 1.1.15 is out!

[sadko4u]

This release mostly fixes problems found in the 1.1.14 release.

The overall list of changes:

• Fixed improper TTL file generation for several plugins.
• Restored missing SVG files, implemented proper icon installation.
• Added better desktop entry categorization (contributed by Dennis Braun).
• Added protection from NaNs, Inf's and denormal floating point values passed to plugins' audio all considered to be invalid values are replaced with zeros.
• Added '-fvisibility=hidden' compilation option to avoid conflict between builtin resources of objects that contain implementation of different plugin formats.

[fruen]

Fantastic!

[ents]

Congrats on new realse, fantastic plugins. I'm a total audio newbie and have couple of questions and problems.

1) 1.1.15 version has lost somethings(dB, ms). Compare screenshots using Ardour5 and sc_dyna_processor_mono plugin

1.1.14

1.1.14.png (143.27 KiB) Viewed 1135 times

1.1.15

1.1.15.png (143.3 KiB) Viewed 1135 times

2) When usign sidechannel dynamic processor stereo plugin(sc_dyna_processor_stereo) and when I'm doing pinout configuration in Ardour5, there are sidechainL and sidechainR pins put only sidechainL is working. Is this normal and as expected?
Sidechain conf

sidechain.png (32.39 KiB) Viewed 1135 times

And really stupid question

3) In the manual I see about sc plugins and listen that "Listen - allows to listen the signal processed by sidechain." What does it exactly mean? It is not "clean" audio from sc? Because it does not sound like it....

[ents]

Hey again

Another problem with ffmpeg and lv2. Don't know if it is ffmpeg problem or lv2 (Or my problem....)plugin problem, maybe You are best to know. I can also make a ticket https://github.com/sadko4u/lsp-plugins/issues

Problem is that same conf for ladspa and lv2 make different results

EDIT: I changed lv2 option pe1=true -->> pe1=1 and now much better but still different to LADSPA, atleast now ardour+lv2 and ffmpeg+lv2 give me same result.

EDITED LV2

Code: Select all

ffmpeg -hide_banner -i orig.wav -filter_complex "[0:a]lv2=p=http\\\\://lsp-plug.in/plugins/lv2/dyna_processor_stereo:c=atd=10.00000000|rtd=10.00000000|tl0=0.39810717|gl0=0.39810717|pe0=1||pe1=1|tl1=0.03162277|gl1=0.31622776|hlr=100.00000000,volumedetect[out1]" -map [out1] -b:a:0 256k asi.aac

[Parsed_volumedetect_1 @ 0x5579ddfd95c0] n_samples: 20929998
[Parsed_volumedetect_1 @ 0x5579ddfd95c0] mean_volume: -9.4 dB
[Parsed_volumedetect_1 @ 0x5579ddfd95c0] max_volume: 0.0 dB
[Parsed_volumedetect_1 @ 0x5579ddfd95c0] histogram_0db: 192757

LV2

Code: Select all

fmpeg -hide_banner -i orig.wav -filter_complex "[0:a]lv2=p=http\\\\://lsp-plug.in/plugins/lv2/dyna_processor_stereo:c=atd=10.00000000|rtd=10.00000000|tl0=0.39810717|gl0=0.39810717|pe1=true|tl1=0.03162277|gl1=0.31622776|hlr=100.00000000,volumedetect[out1]" -map [out1] -b:a:0 256k asi.aac

[Parsed_volumedetect_1 @ 0x55bd9dfa9f40] n_samples: 20929998
[Parsed_volumedetect_1 @ 0x55bd9dfa9f40] mean_volume: -20.4 dB
[Parsed_volumedetect_1 @ 0x55bd9dfa9f40] max_volume: -5.1 dB
[Parsed_volumedetect_1 @ 0x55bd9dfa9f40] histogram_5db: 27
[Parsed_volumedetect_1 @ 0x55bd9dfa9f40] histogram_6db: 59
[Parsed_volumedetect_1 @ 0x55bd9dfa9f40] histogram_7db: 114
[Parsed_volumedetect_1 @ 0x55bd9dfa9f40] histogram_8db: 2576
[Parsed_volumedetect_1 @ 0x55bd9dfa9f40] histogram_9db: 27290

LADSPA

Code: Select all

ffmpeg -hide_banner -i orig.wav -filter_complex "[0:a]ladspa=file=lsp-plugins-ladspa:p=http\\\\://lsp-plug.in/plugins/ladspa/dyna_processor_stereo:c=c12=10.00000000|c13=10.00000000|c15=0.39810717|c16=0.39810717|c24=1|c25=0.03162277|c26=0.31622776|c55=100.00000000,volumedetect[out1]" -map [out1] -b:a:0 256k asi.aac

[Parsed_volumedetect_1 @ 0x55f285639b00] n_samples: 20929998
[Parsed_volumedetect_1 @ 0x55f285639b00] mean_volume: -15.7 dB
[Parsed_volumedetect_1 @ 0x55f285639b00] max_volume: -1.8 dB
[Parsed_volumedetect_1 @ 0x55f285639b00] histogram_1db: 2
[Parsed_volumedetect_1 @ 0x55f285639b00] histogram_2db: 30
[Parsed_volumedetect_1 @ 0x55f285639b00] histogram_3db: 287
[Parsed_volumedetect_1 @ 0x55f285639b00] histogram_4db: 1759
[Parsed_volumedetect_1 @ 0x55f285639b00] histogram_5db: 9457
[Parsed_volumedetect_1 @ 0x55f285639b00] histogram_6db: 33851

ORIG.WAV

Code: Select all

ffmpeg -hide_banner -i orig.wav -af "volumedetect" -y -f null /dev/null

[Parsed_volumedetect_0 @ 0x55932346adc0] n_samples: 20929998
[Parsed_volumedetect_0 @ 0x55932346adc0] mean_volume: -20.4 dB
[Parsed_volumedetect_0 @ 0x55932346adc0] max_volume: -5.1 dB
[Parsed_volumedetect_0 @ 0x55932346adc0] histogram_5db: 27
[Parsed_volumedetect_0 @ 0x55932346adc0] histogram_6db: 60
[Parsed_volumedetect_0 @ 0x55932346adc0] histogram_7db: 113
[Parsed_volumedetect_0 @ 0x55932346adc0] histogram_8db: 2576
[Parsed_volumedetect_0 @ 0x55932346adc0] histogram_9db: 27290

So it seems that LV2 command does nothing, result is almost same as orig file


Attached conf where I took lv2 options

[sadko4u]

Hello

1.1.15 version has lost somethings(dB, ms)

Yes, that's definitely bug. Fixed today and available in git repository in devel branch. Will be published at the end of week.

EDIT: I changed lv2 option pe1=true -->> pe1=1 and now much better but still different to LADSPA, atleast now ardour+lv2 and ffmpeg+lv2 give me same result.

There's no much difference between LADSPA and LV2 since plugin implementation doesn't differ, the different only are wrappers that adapt plugin to LADSPA and LV2. I would recommend to use UI first, then export configuration via the UI and take the values from the exported configuration file.

[sadko4u]

Also please consider to set enabled=1 property for LV2 plugin. Without enabled=1 it will just bypass the signal.

[sadko4u]

Is this normal and as expected?

No, it's not normal and needs to be fixed. Thanks for that you've noticed it.

UPD: just committed the change to devel branch which fixes the problem.

[sadko4u]

What does it exactly mean? It is not "clean" audio from sc? Because it does not sound like it....

No, it's not that audio that comes to the input. It's already pre-processed audio (depending on the 'sidechain type' switch) that will be passed as a control signal to the dynamic processor.

[ents]

Hey

Yes, I did this way. Exported conf from lv2 gui in ardour and compared to to default conf and extracted only the differences. Problem was that lv2 gui exported conf had pe1=true but ffmpeg wants only numbers, so I had to change true -->> 1 then everything worked.

As for ladspa and lv2 differenses I think I understand why. LV2 and ladpsa have some default differences. Below are some differences between sc dyn proc plugin in lv2 and ladspa

Code: Select all

scr       <float> (from 0.000000 to 250.000000) (default 10.000000)        Sidechain reactivity
c10: Sidechain reactivity (ms) [<float>, min: 0.000000, max: 250.000000 (default 0.000000), logarithmic scale]

atd       <float> (from 0.000000 to 5000.000000) (default 20.000000)       Attack time default
c12: Attack time default (ms) [<float>, min: 0.000000, max: 5000.000000 (default 0.000000), logarithmic scale]


tl0       <float> (from 0.000250 to 15.848930) (default 0.251190)     Threshold 0
gl0       <float> (from 0.000250 to 15.848930) (default 0.251190)     Gain 0
kn0       <float> (from 0.063100 to 1.000000) (default 0.501180)     Knee 0

c15: Threshold 0 (G) [<float>, min: 0.000250, max: 15.848930 (default 0.062946), logarithmic scale]
c16: Gain 0 (G) [<float>, min: 0.000250, max: 15.848930 (default 0.062946), logarithmic scale]
c17: Knee 0 (G) [<float>, min: 0.063100, max: 1.000000 (default 0.501196), logarithmic scale]

Also compiled new devel branch and those other problems are indeed fixed


Also is feature request multiband dynamic processor a overkill?

Hello

1.1.15 version has lost somethings(dB, ms)

Yes, that's definitely bug. Fixed today and available in git repository in devel branch. Will be published at the end of week.

EDIT: I changed lv2 option pe1=true -->> pe1=1 and now much better but still different to LADSPA, atleast now ardour+lv2 and ffmpeg+lv2 give me same result.

There's no much difference between LADSPA and LV2 since plugin implementation doesn't differ, the different only are wrappers that adapt plugin to LADSPA and LV2. I would recommend to use UI first, then export configuration via the UI and take the values from the exported configuration file.

[sadko4u]

As for ladspa and lv2 differenses I think I understand why. LV2 and ladpsa have some default differences. Below are some differences between sc dyn proc plugin in lv2 and ladspa

Yes, that also can be the cause since LADSPA does not provide reliable way to define default value. Here's a snippet of what LADSPA does allow in our case:

Code: Select all

/* This default hint indicates that the suggested lower bound for the
   port should be used. */
#define LADSPA_HINT_DEFAULT_MINIMUM 0x40

/* This default hint indicates that a low value between the suggested
   lower and upper bounds should be chosen. For ports with
   LADSPA_HINT_LOGARITHMIC, this should be exp(log(lower) * 0.75 +
   log(upper) * 0.25). Otherwise, this should be (lower * 0.75 + upper
   * 0.25). */
#define LADSPA_HINT_DEFAULT_LOW     0x80

/* This default hint indicates that a middle value between the
   suggested lower and upper bounds should be chosen. For ports with
   LADSPA_HINT_LOGARITHMIC, this should be exp(log(lower) * 0.5 +
   log(upper) * 0.5). Otherwise, this should be (lower * 0.5 + upper *
   0.5). */
#define LADSPA_HINT_DEFAULT_MIDDLE  0xC0

/* This default hint indicates that a high value between the suggested
   lower and upper bounds should be chosen. For ports with
   LADSPA_HINT_LOGARITHMIC, this should be exp(log(lower) * 0.25 +
   log(upper) * 0.75). Otherwise, this should be (lower * 0.25 + upper
   * 0.75). */
#define LADSPA_HINT_DEFAULT_HIGH    0x100

/* This default hint indicates that the suggested upper bound for the
   port should be used. */
#define LADSPA_HINT_DEFAULT_MAXIMUM 0x140

/* This default hint indicates that the number 0 should be used. Note
   that this default may be used in conjunction with
   LADSPA_HINT_TOGGLED. */
#define LADSPA_HINT_DEFAULT_0       0x200

/* This default hint indicates that the number 1 should be used. Note
   that this default may be used in conjunction with
   LADSPA_HINT_TOGGLED. */
#define LADSPA_HINT_DEFAULT_1       0x240

/* This default hint indicates that the number 100 should be used. */
#define LADSPA_HINT_DEFAULT_100     0x280

/* This default hint indicates that the Hz frequency of `concert A'
   should be used. This will be 440 unless the host uses an unusual
   tuning convention, in which case it may be within a few Hz. */
#define LADSPA_HINT_DEFAULT_440     0x2C0

So LADSPA allows only the following default values:

• values that are 0%, 25%, 50%, 75%, 100% of the min:max range;
• constant values of 0, 1, 100, 440.

Also compiled new devel branch and those other problems are indeed fixed

Good

Also is feature request multiband dynamic processor a overkill?

No, it's planned but currently I can not say when it will be available.
You can create the corresponding issue on GitHub, of course.