i noticed that you have vaapi somehow implemented, so i try it out, but it crashes. i ran into similar problem with the tool Weylus: mesa and my apu won't work with empty_moov. i managed to make it work by using faststart instead of empty_moov: is there anywhere in your code a place, where i could inject ffmpeg parameter like that? i could not find anywhere in the files that you would be explicitly declaring that, so it might be implicit somewhere? i just cannot read or write C or C++ very well, but i would be interested if this parameter could make it behave. but it might be crashing cause of the direct mapping error.
log.
[2022:01:03:16:22:32]: Debug: vaapi vendor: Mesa Gallium driver 22.0.0-devel for AMD RENOIR (LLVM 13.0.0, DRM 3.42, 5.15.11)
[AVHWDeviceContext @ 0x55a6520f8d00] Format 0x36313050 -> unknown. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x30323449 -> yuv420p.
[AVHWDeviceContext @ 0x55a6520f8d00] Format 0x32315659 -> yuv420p. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x56595559 -> unknown.
[AVHWDeviceContext @ 0x55a6520f8d00] Format 0x32595559 -> yuyv422. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x59565955 -> uyvy422.
[AVHWDeviceContext @ 0x55a6520f8d00] Format 0x41524742 -> bgra. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x41424752 -> rgba.
[AVHWDeviceContext @ 0x55a6520f8d00] Format 0x58524742 -> bgr0. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x58424752 -> rgb0.
[AVHWDeviceContext @ 0x55a6520f8d00] VAAPI driver: Mesa Gallium driver 22.0.0-devel for AMD RENOIR (LLVM 13.0.0, DRM 3.42, 5.15.11). [AVHWDeviceContext @ 0x55a6520f8d00] Driver not found in known nonstandard list, using standard behaviour.
[AVHWFramesContext @ 0x55a651fc5640] Created surface 0x1. [AVHWFramesContext @ 0x55a651fc5640] Direct mapping disabled: deriving image does not work: 1 (operation failed).
[h264_vaapi @ 0x55a652099900] Input surface format is nv12. [h264_vaapi @ 0x55a652099900] Using VAAPI profile VAProfileH264High (7).
[h264_vaapi @ 0x55a652099900] Using VAAPI entrypoint VAEntrypointEncSlice (6). [h264_vaapi @ 0x55a652099900] Using VAAPI render target format YUV420 (0x1).
[h264_vaapi @ 0x55a652099900] Driver supports RC modes CQP, CBR, VBR. [h264_vaapi @ 0x55a652099900] RC mode: CBR.
[h264_vaapi @ 0x55a652099900] RC target: 100% of 1000000 bps over 16 ms. [h264_vaapi @ 0x55a652099900] RC buffer: 16666 bits, initial fullness 12499 bits.
[h264_vaapi @ 0x55a652099900] RC framerate: 60/1 (60.00 fps). [h264_vaapi @ 0x55a652099900] Using intra and P-frames (supported references: 1 / 0).
[h264_vaapi @ 0x55a652099900] Driver does not support some wanted packed headers (wanted 0xd, found 0). [h264_vaapi @ 0x55a652099900] Using nv12 as format of reconstructed frames.
[AVHWFramesContext @ 0x55a6520f07c0] Created surface 0x3. [AVHWFramesContext @ 0x55a6520f07c0] Direct mapping disabled: deriving image does not work: 1 (operation failed).
[h264_vaapi @ 0x55a652099900] Using level 4.2. [h264_vaapi @ 0x55a652099900] Input frame: 1920x1080 (1).
[h264_vaapi @ 0x55a652099900] Pick forced IDR-picture to encode next. [h264_vaapi @ 0x55a652099900] Issuing encode for pic 0/0 as type IDR.
[h264_vaapi @ 0x55a652099900] No reference pictures.
[h264_vaapi @ 0x55a652099900] Input surface is 0x1.
[h264_vaapi @ 0x55a652099900] Recon surface is 0x3.
[h264_vaapi @ 0x55a652099900] Allocated output buffer 0x5
[h264_vaapi @ 0x55a652099900] Output buffer is 0x5.
[h264_vaapi @ 0x55a652099900] Param buffer (22) is 0x6.
[h264_vaapi @ 0x55a652099900] Param buffer (27) is 0x7.
[h264_vaapi @ 0x55a652099900] Param buffer (27) is 0x8.
[h264_vaapi @ 0x55a652099900] Param buffer (27) is 0x9.
[h264_vaapi @ 0x55a652099900] Param buffer (23) is 0xa.
[h264_vaapi @ 0x55a652099900] Slice 0: 0-67 (68 rows), 0-8159 (8160 blocks).
[h264_vaapi @ 0x55a652099900] Param buffer (24) is 0xb.
[h264_vaapi @ 0x55a652099900] Sync to pic 0/0 (input surface 0x1).
[h264_vaapi @ 0x55a652099900] Output buffer: 25048 bytes (status 00000000).
[h264_vaapi @ 0x55a652099900] Output read for pic 0/0.
[h264_vaapi @ 0x55a652099900] Output packet: pts 1 dts 1.
i noticed that you have vaapi somehow implemented, so i try it out, but it crashes. i ran into similar problem with the tool Weylus: mesa and my apu won't work with empty_moov. i managed to make it work by using faststart instead of empty_moov: is there anywhere in your code a place, where i could inject ffmpeg parameter like that? i could not find anywhere in the files that you would be explicitly declaring that, so it might be implicit somewhere? i just cannot read or write C or C++ very well, but i would be interested if this parameter could make it behave. but it might be crashing cause of the direct mapping error.
log.
[2022:01:03:16:22:32]: Debug: vaapi vendor: Mesa Gallium driver 22.0.0-devel for AMD RENOIR (LLVM 13.0.0, DRM 3.42, 5.15.11) [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x36313050 -> unknown. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x30323449 -> yuv420p. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x32315659 -> yuv420p. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x56595559 -> unknown. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x32595559 -> yuyv422. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x59565955 -> uyvy422. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x41524742 -> bgra. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x41424752 -> rgba. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x58524742 -> bgr0. [AVHWDeviceContext @ 0x55a6520f8d00] Format 0x58424752 -> rgb0. [AVHWDeviceContext @ 0x55a6520f8d00] VAAPI driver: Mesa Gallium driver 22.0.0-devel for AMD RENOIR (LLVM 13.0.0, DRM 3.42, 5.15.11). [AVHWDeviceContext @ 0x55a6520f8d00] Driver not found in known nonstandard list, using standard behaviour. [AVHWFramesContext @ 0x55a651fc5640] Created surface 0x1. [AVHWFramesContext @ 0x55a651fc5640] Direct mapping disabled: deriving image does not work: 1 (operation failed). [h264_vaapi @ 0x55a652099900] Input surface format is nv12. [h264_vaapi @ 0x55a652099900] Using VAAPI profile VAProfileH264High (7). [h264_vaapi @ 0x55a652099900] Using VAAPI entrypoint VAEntrypointEncSlice (6). [h264_vaapi @ 0x55a652099900] Using VAAPI render target format YUV420 (0x1). [h264_vaapi @ 0x55a652099900] Driver supports RC modes CQP, CBR, VBR. [h264_vaapi @ 0x55a652099900] RC mode: CBR. [h264_vaapi @ 0x55a652099900] RC target: 100% of 1000000 bps over 16 ms. [h264_vaapi @ 0x55a652099900] RC buffer: 16666 bits, initial fullness 12499 bits. [h264_vaapi @ 0x55a652099900] RC framerate: 60/1 (60.00 fps). [h264_vaapi @ 0x55a652099900] Using intra and P-frames (supported references: 1 / 0). [h264_vaapi @ 0x55a652099900] Driver does not support some wanted packed headers (wanted 0xd, found 0). [h264_vaapi @ 0x55a652099900] Using nv12 as format of reconstructed frames. [AVHWFramesContext @ 0x55a6520f07c0] Created surface 0x3. [AVHWFramesContext @ 0x55a6520f07c0] Direct mapping disabled: deriving image does not work: 1 (operation failed). [h264_vaapi @ 0x55a652099900] Using level 4.2. [h264_vaapi @ 0x55a652099900] Input frame: 1920x1080 (1). [h264_vaapi @ 0x55a652099900] Pick forced IDR-picture to encode next. [h264_vaapi @ 0x55a652099900] Issuing encode for pic 0/0 as type IDR. [h264_vaapi @ 0x55a652099900] No reference pictures. [h264_vaapi @ 0x55a652099900] Input surface is 0x1. [h264_vaapi @ 0x55a652099900] Recon surface is 0x3. [h264_vaapi @ 0x55a652099900] Allocated output buffer 0x5 [h264_vaapi @ 0x55a652099900] Output buffer is 0x5. [h264_vaapi @ 0x55a652099900] Param buffer (22) is 0x6. [h264_vaapi @ 0x55a652099900] Param buffer (27) is 0x7. [h264_vaapi @ 0x55a652099900] Param buffer (27) is 0x8. [h264_vaapi @ 0x55a652099900] Param buffer (27) is 0x9. [h264_vaapi @ 0x55a652099900] Param buffer (23) is 0xa. [h264_vaapi @ 0x55a652099900] Slice 0: 0-67 (68 rows), 0-8159 (8160 blocks). [h264_vaapi @ 0x55a652099900] Param buffer (24) is 0xb. [h264_vaapi @ 0x55a652099900] Sync to pic 0/0 (input surface 0x1). [h264_vaapi @ 0x55a652099900] Output buffer: 25048 bytes (status 00000000). [h264_vaapi @ 0x55a652099900] Output read for pic 0/0. [h264_vaapi @ 0x55a652099900] Output packet: pts 1 dts 1.thanks!