Hi Jean-Baptiste Sorry for the complexity and confusion to so many people involved on this new patch.
We have been working on this for 4 months because some of our big customers on internet business have been asking Matrox to make our M264 card to support FFmpeg on h.264 transcoding, esp on 4k and HD files. M264 is very powerful on 4k and HD decoding and encoding. M264 uses a h.264 encoding chip made by Matrox, and there are a lot of modules involved to make it work. Those modules are not public in Matrox, which is a company of 40 years. Yes, mvM264Ffmpeg.dll is a wrapper to those modules, it involves all the interfaces talking to the chip. I did not find a better way to make this work. Thanks a lot to all people involved. Yufei. On 03/15/2019 11:23 AM, Jean-Baptiste Kempf wrote: > On Fri, 15 Mar 2019, at 15:02, Tomas Härdin wrote: >>> + #ifdef _WIN32 >>> + lib_handle = dlopen("mvM264Ffmpeg.dll", RTLD_LAZY); >>> + #else >>> + lib_handle = dlopen("libmvM264Ffmpeg.so", RTLD_LAZY); >>> + #endif >> Still dlopen() I see. You should link to these libraries properly, as >> others have said, and add appropriate license stuff to configure. > What are those libraries? Are they drivers/system libraries? > > They seem to be a wrapper done just for the FFMpeg integration. If so, what > is the license of those? > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel