libva lacks a way for user/app to get the actual parameter sets supported by the HW before encoding begins
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start by reviewing the VA_ENC_PACKED_HEADER_SEQUENCE flow and the existing dummy-encode approach described in the issue, then examine how libva exposes encoder options to drivers. Done means reaching agreement on an API method that lets applications obtain the driver's HEVC parameter sets before the first frame, with the behavior documented and validated across relevant drivers.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
As the title suggests, libva currently assumes that the VA_ENC_PACKED_HEADER_SEQUENCE written by the user or application is fully compatible with the actual bitstream encoded by the hardware. However, in practice, this assumption does not hold true for hardware other than Intel QuickSync.
Starting with FFmpeg 8.0, the MP4 muxer strips in-band parameter sets from videos using the HEVC codec_tag hvc1, leaving only the incompatible VA_ENC_PACKED_HEADER_SEQUENCE written by FFmpeg.
https://github.com/FFmpeg/FFmpeg/commit/f0051604c7f131582e6fa97febd77069e1d87032
This causes decoding failures for the encoded video. Affected players include, but are not limited to, Safari, Chrome, Firefox, FFplay, and MPC-BE. The affected videos cannot be used in HLS fMP4 segments (which is why hvc1 is needed).
Matroska/MKV files also require AV_CODEC_FLAG_GLOBAL_HEADER, so similar issues arise there as well.
Mesa/AMD developer have provided a suggestion:
What would be a good solution is to have an option to only get the encoded headers, eg. a new flag that will disable slice output. App would do the exact same calls as when encoding a frame, except set this new flag. But then again, this is just like a dummy encode which apps can do today and it will work with all drivers. Since it's only needed once at the start of the session, the overhead of one encode job is probably not a big deal.
Could libva consider adding a method to obtain HEVC parameter sets from the vaapi driver before encoding the first frame?
Thanks in advance! @XinfengZhang @nowrep
- Lenguaje dominante
- C
- Estrellas
- 793
- Forks
- 318
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de intel/libva
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 65/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
-
registry_packageAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 10/100
-
OjaidiAbierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 1/100
Todos los issues de intel/libva
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
osam-cologne/archlinux-proaudio#909 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
ARM-software/CMSIS-DSP#354 ·
-
good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
documentation good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
ai-quokka-wannabe/link#40 ·
-
[BUG] Sentinel sends CONFIG REWRITE to instances started without a config filePosiblemente ocupada @jdymitarai la tomó hoy. Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 2 días