DynamicallyLoadedBindings.LibrariesPath vs Initialize() vs ffmpeg.RootPath?

[CodingOctocat]

What are the differences between them? Which one should I use?

// Why System.NullReferenceException:“Object reference not set to an instance of an object.”?
Debug.WriteLine($"FFmpeg version info: {ffmpeg.av_version_info()}");

public static void RegisterFFmpegBinaries()
{
    if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows))
    {
        string? current = Environment.CurrentDirectory;
        string ffmpegPath = Path.Combine(current, "runtimes", "win-x64", "native");

        if (!Directory.Exists(ffmpegPath))
        {
            throw new DirectoryNotFoundException($"FFmpeg binaries not found at {ffmpegPath}");
        }

        ffmpeg.RootPath = ffmpegPath;
        //DynamicallyLoadedBindings.Initialize();
        Debug.WriteLine($"FFmpeg version info: {ffmpeg.av_version_info()}");
    }
    else
    {
        throw new NotSupportedException(); // fell free add support for platform of your choose
    }
}

[Ruslan-B]

Hi there I’ll take a look just back from surgery table Indubhave solution for this please wait a bit. Family and health first.

[LittleTerry]

Hi there I’ll take a look just back from surgery table Indubhave solution for this please wait a bit. Family and health first.

Family and health first. Hope everything goes well❤️ take care bro❤️

[CodingOctocat]

@Ruslan-B Hi, Thanks! Hope you’re doing okay after the surgery.

I finally tested the correct solution. First, the ffmpeg binary version must be correct. I initially used nuget/FFmpeg.GPL, which was convenient, but the version seemed to be incorrect. Second, the namespace must be selected correctly, and LibrariesPath and Initialize() must be set at the same time.

using FFmpeg.AutoGen.Bindings.DynamicallyLoaded;

DynamicallyLoadedBindings.LibrariesPath = ffmpegPath;
DynamicallyLoadedBindings.Initialize();

[CodingOctocat]

This is very strange. In the RegisterFFmpegBinaries() method, I only need to set ffmpeg.RootPath, and then I can print ffmpeg.av_version_info() normally. However, after externally calling RegisterFFmpegBinaries(), printing ffmpeg.av_version_info() causes a NullReferenceException!

[CodingOctocat]

Okay, it's still a namespace issue!

❌:

✅:

[Ruslan-B]

I guess we can do breaking changes in this case or force user to fail as there reasons why it is one of them speed second it is static so assuming this there’s is legitimate way to break stable api and stop this from happening.

Besides I did realized it is complet project for me I have to pass library to community - I’ll do this in a right way.

[CodingOctocat]

Hi, could you explain the difference between DynamicallyLoadedBindings.LibrariesPath, Initialize(), and ffmpeg.RootPath? The example requires DynamicallyLoadedBindings, but I found that setting ffmpeg.RootPath works as well.

FFmpeg.AutoGen/FFmpeg.AutoGen.Example/FFmpegBinariesHelper.cs

Line 24 in f54e0b9

DynamicallyLoadedBindings.LibrariesPath = ffmpegBinaryPath;

FFmpeg.AutoGen/FFmpeg.AutoGen.Example/Program.cs

Line 24 in f54e0b9

DynamicallyLoadedBindings.Initialize();

---

❌: DynamicallyLoadedBindings NOT WORK

✅:

---

Summary:

FFmpeg.AutoGen.ffmpeg.RootPath must be used in conjunction with FFmpeg.AutoGen.ffmpeg.av_version_info, while DynamicallyLoadedBindings must be used with FFmpeg.AutoGen.Abstractions.ffmpeg.av_version_info.

Now I have only one question left: do they have the same functions?

I strongly recommend improving this issue, which has been bothering me all day, or at least making a note of it in the documentation.

// ✅
FFmpeg.AutoGen.ffmpeg.RootPath = ffmpegPath;
Debug.WriteLine($"FFmpeg version info: {FFmpeg.AutoGen.ffmpeg.av_version_info()}");

// ✅
FFmpeg.AutoGen.Bindings.DynamicallyLoaded.DynamicallyLoadedBindings.LibrariesPath = ffmpegPath;
FFmpeg.AutoGen.Bindings.DynamicallyLoaded.DynamicallyLoadedBindings.Initialize();
Debug.WriteLine($"FFmpeg version info: {FFmpeg.AutoGen.Abstractions.ffmpeg.av_version_info()}");

[Ruslan-B]

So look deeper it is okay to refactor this part as users will be impacted anyway

[Ruslan-B]

Оорв wrong poket. They are from different packages, the one from dyn loaded is an cross platform abstraction, dynamically liked lib the way to go as you can write a bindings redirection via dotnet