4 ms·
> Take a look at FFMPEG, the most popular and feature complete video library out there: it’s huge, consisting of several DLL files and lots of dependencies. Wh
by chme 3y ago
> Take a look at FFMPEG, the most popular and feature complete video library out there: it’s huge, consisting of several DLL files and lots of dependencies.
What? You can compile it with just the stuff you need and only activate stuff without any dependencies. Static linking is also possible if too many 'DLL' files is a issue.
But vulkan video decoding is still cool.
- _gabe_ 3y ago> What? You can compile it with just the stuff you need and only activate stuff without any dependencies. Sure, but running config alone takes like 10-15 minutes on my PC with an Intel I7-9700K processor at 4.9GHz. This is while using all my cores at 100% CPU usage too, it's ridiculous. And not only that, you'll likely have to run this massive script several times to tweak the config until you're happy with what you're using. Then actually compiling the library statically takes another 15-20 minutes. So I think the remark that it's huge and consisting of several DLL files is spot on. > Static linking is also possible if too many 'DLL' files is a issue. FFmpeg doesn't recommend static linking. > The following is a checklist for LGPL compliance when linking against the FFmpeg libraries. It is not the only way to comply with the license, but we think it is the easiest...Use dynamic linking (on windows, this means linking to dlls) for linking with FFmpeg libraries.[0] [0]: https://www.ffmpeg.org/legal.html https://www.ffmpeg.org/legal.html
- izacus 3y agoIt's kind of a strange comparison... FFMPeg is a library for everything and anything video, audio and image transcoding. The API this post writes about is basically a single decoder... without even (de)muxing ability.