![]() ![]() ![]() Libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/iHD_drv_video.so Libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so hb_display_init: attempting VA driver 'iHD' Though surrounding comments seem to suggest they might be patches in Plex's FFmpeg fork (though tracking them down for GPL compliance if they use libx264 or libx265 might be something). There's at least some support per this Reddit comment. And this would go through ffmpeg's vaapi implementation no? Maybe I'm mistaken, IIRC someone said ffmpeg does not support zero-copy in any hardware encoder yet. Sure, HandBrake supports those, but without me digging into why QSV isn't being detected on my machine, I'd be stuck without any hardware accel if VAAPI is never made available for them in a stock build. I made it with VAAPI being the conditional part, but if available, always make H.264 and H.265 available since not everyone has hardware/drivers for the other ones handy. I made this comment explicitly with these in mind since they are already covered by QSV, NVenc, and AMF which will always be enabled in an official buildĪh. (Supporting what we already do is a stretch for a project with limited resources) Also, we don't formally support or have any intention of supporting any other hardware platforms. QuickSync is Intel Only, so it doesn't matter that it's x86 only library. We already have a wrapper around using libav encoders, so it's not a giant leap to extend that and use ffmpeg/libav's built-in support that already exists. Since we need libmfx and the nvidia/vce sdks's via ffmpeg anyway for Windows, everything should just use those same paths so we have consistent behaviour on all platforms. Does VA-API support the full feature set of these encoders, including the filters and do we actually have up-to-date driver support (the intel site doesn't indicate support for Kaby/Coffee lake features for example).VT on Mac cripples the hardware encoders feature set, DXVA on windows is horrifically unreliable and in areas, fundamentally broken for example. You need separate implementations for Windows and Mac.Īlso, general purpose API's tend to have problems. It wouldn't be a single code path though. ![]()
0 Comments
Leave a Reply. |