#4659: Support the MFX Dispatcher from Intel Media SDK -------------------------------------+----------------------------------- Reporter: TheTroll | Owner: Type: enhancement | Status: new Priority: wish | Component: avcodec Version: git-master | Resolution: Keywords: qsv | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -------------------------------------+-----------------------------------
Comment (by GwenoleBeauchesne): I think you need to supply two ways of allocating the VA display: one from within FFmpeg (libavcodec), and another one handed over by the user (e.g. through some vaapi_context). Next, if FFmpeg was to create the VA display handle, using an environment variable to derive the device name is a no-go. You have the option to use libudev to enumerate and pick an Intel device + VGA class device. You can also avoid libudev if you were to parse /sys/bus/pci/devices entries yourself and check for class = 0x030000, vendor_id = 0x8086 for Intel. Last but not least, DRM render nodes are now also the preferred way, unless you really want to ultimately render frames through KMS for instance. A render node id is built as 0x80|i where i has a /dev/dri/card<i> counterpart. With udev, it's generally enough to match "renderD[0-9]*" devices. -- Ticket URL: <https://trac.ffmpeg.org/ticket/4659#comment:4> FFmpeg <https://ffmpeg.org> FFmpeg issue tracker _______________________________________________ FFmpeg-trac mailing list FFmpeg-trac@avcodec.org http://avcodec.org/mailman/listinfo/ffmpeg-trac