libVLC: audio compressor filter not working when called via command line to libVLC

Hello everyone, I tried to call the audio compressor filter using libVLCSharp in a C# Windows Forms application using the command line arguments (code attached below).

• Audio compressor WORKS fine when I use libVLC version 2.1.5 oder 2.1.0. Video plays fine. Log from Test: https://pastebin.com/dFdXDx7k
• Audio compressor does not work with any libVLC version later than 2.2.0. Log from test with version 3.0.8: https://pastebin.com/ffKHWN5r Video and other functions are fine, but the filter command is ignored. libVLC installed using NuGet.
• Audio compressor also WORKS of course with the official VLC application when called via the command line with the same arguments. Log from my computer: https://pastebin.com/ymfivyvs.

Since the code works fine using libVLC 2.1.5, but does not work when using any later version, I assume the issue comes from libVLC in the sense that anything distorts calling the command from external applications (can this come from security "features"?). I also tried using the ActiveX control. Here the Log shows the message: "unsafe command compressor filter ignored".

I discussed the topic in the VLC forum: https://forum.videolan.org/viewtopic.php?f=32&t=153183&e=1&view=unread#unread

Windows 10 Pro 1909, 64 bit, CPU: Intel i5-4300M, Grafics: AMD Radeon HD 8790M, Audio: Realtek onboard chip (Dell Notebook)

CODE: Core.Initialize(); InitializeComponent();

string[] _commandLineOptions = { "--audio-filter=compressor", "--compressor-rms-peak=0.00", "--compressor-attack=24.00", "--compressor-release=250.00", "--compressor-threshold=-25.00", "--compressor-ratio=2.00", "--compressor-knee=4.50", "--compressor-makeup-gain=17.00" };

_libVLC = new LibVLC(_commandLineOptions); _mp = new MediaPlayer(_libVLC); videoView1.MediaPlayer = _mp;

_mp.Play(new Media(_libVLC, @"C:\Testfile.mp4", FromType.FromPath));

Care to read the libvlc_new() documentation before reporting bugs, please?

added Status::invalid label

closed

marked this issue as related to #27445