Nyanmisaka
It works. Thanks for your instant response. ``` ffmpeg version N-107767-g7158f1e64d-20220812 Copyright (c) 2000-2022 the FFmpeg developers built with gcc 12.1.0 (crosstool-NG 1.25.0.55_3defb7b) configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32...
There's no need to specify a drm render node again if a vaapi driver is requested, ffmpeg hwcontext will filter the correct render node as per the driver name. `Generic...
> `GetVaapiDeviceArgs(null, "iHD", "i915", VaapiAlias)` I see. Does adding `,kernel_driver=i915` after the `,driver=iHD` fix this for you?
This is the cause. [VAAPI hwcontext](https://github.com/FFmpeg/FFmpeg/blob/1bad30dbe34f2d100b43e8f773d3fe0b5eb23523/libavutil/hwcontext_vaapi.c#L1679-L1683) should use `continue` instead of `break` in case of the first render node isn't renderD128. ``` if (priv->drm_fd < 0) { av_log(ctx, AV_LOG_VERBOSE, "Cannot...
This issue should be fixed in jellyfin-ffmpeg5 [5.1.1-2](https://github.com/jellyfin/jellyfin-ffmpeg/releases/tag/v5.1.1-2). You can upgrade and try it now.
I'm wondering why NVIDIA doesn't provide the normal CUVID(CUDA VIDEO) path for Jetson/Tegra X1, which is a quite mature video API and can utilize the existing ffmpeg impl as well...
Any chance AMF team can setup a staging area for ffmpeg and keep a custom fork with full AMF hwcontext and features? Here are two nice repos from Intel devs...
> * copy/use HWcontext for processing using OpenCL functions (ffmpeg: hwmap=derive_device=opencl) This is feasible for d3d11vaopencl on Windows with two of my patches: https://github.com/jellyfin/jellyfin-ffmpeg/blob/jellyfin/debian/patches/0010-add-d3d11-opencl-interop-for-amd.patch https://github.com/jellyfin/jellyfin-ffmpeg/blob/jellyfin/debian/patches/0011-add-a-hack-for-opencl-reverse-mapping.patch > * afterwards re-mapping the...
OpenMax encoder is only available on arm32 since some runtime are missing on arm64. Pi developers are working on better V4L2 support, we will move to it when it becomes...
> Raspberry Pi OS Bullseye has ffmpeg 4.3.3 available, maybe V4L2 support is now stable enough for use in Jellyfin? The newly developed V4L2 H264/H265 decoders are stable enough in...