Even for those who are sure that he knows the ffmpeg library from C++ side, this information also will be interesting. It will be interesting for those who want to start learning how to work with the ffmpeg library or for those who plan to use it in production.
Each code is workable and has a description with the output results. It contains a lot of code samples for different aims of usage of FFmpeg library. It covers basic architecture aspects along with information: how that was done and what issues are solved during implementation. You may ask a good question: “how is that possible and why wasn't that done before?”, and the answers you can find in current documentation. It is not just calls of certain APIs of a couple predefined objects - all API exposed as methods.
NET wrapper is representation of all exported structures from ffmpeg libraries, along with APIs which can operate with those objects from managed code either from C# or VB.NET or even Delphi.NET. So, usage of such code is also problematic and I am just talking about C# and not take other languages such as VB.NET.Ĭurrent implementation of. NET “unsafe” code implementation of wrapper, so the C# code must be also marked as “unsafe” and the functions of such wrapper have lots of pointers like “void *” and other similar types.
NET what actually can be done with full access to ffmpeg libraries in C++. More productive results have some basic classes which can perform just one of few tasks of ffmpeg and whose classes are exposed as COM objects or regular C# classes, but their functionality is very limited and does not fully perform in. I saw different implementations, mostly just performing calling ffmpeg.exe with prepared arguments and parsing outputs from it.
0 kommentar(er)
