> More widely, I would actually suggest to revise existing mediasdk plugins > loading path and change it from loading plugins at the first place to: > 1. Try to initialize component directly from the library 2. If #1 fails, try > to > initialize component from the plugin This will allow to avoid a cost of > plugins > loading when you don't actually need to load them and will preserve > compatibility with the old versions of mediasdk.
That could be a good idea but only based on a query interface, instead of MSDK initialization failure. There are many reasons may cause the failure but application can't what is the exact reason. I haven't see MFXVideoDECODE_Query() has exposed this, this could be addressed if you have a plan to improve MSDK query functions. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
