Sergiu Ciumac

Got the same problem.

Yeah, so I thought. That's why I asked if there have been any changes in the generation of the source code since v4.3.2.1? I'm not completely aware of the tools...

Will do it later this week.

@Ruslan-B it is actually quite easy. Create a new console app and run the following code: ```csharp using System; using FFmpeg.AutoGen; unsafe { var pixelFormat = ffmpeg.av_pix_fmt_desc_get(AVPixelFormat.AV_PIX_FMT_RGB24); int_array4 max_step, _;...

Is there any way you will force ref parameters for the 4.x branch? I could test that.

Understand and appreciate your efforts. I'm bundling it with Microsoft Debian Bullseye, which still marks ffmpeg 5.x package as unstable, and frankly saying I don't expect it to become stable...

The latest I can use is v4.3.0.3

Sorry @Ruslan-B I've misunderstood your question. The version that is marked as stable and used with Microsoft Debian Bullseye is 4.3.4. ``` ffmpeg version 4.3.4-0+deb11u1 Copyright (c) 2000-2021 the FFmpeg...

Once a new package is created for 4.3.x, I will give it a run.

The fix is working. I could run it with `ffmpeg v4.4.1` and `FFmpeg.AutoGen.Bindings.DynamicallyLoaded -Version 4.3.2`. Thanks for the efforts.