On 24.12.2021 05:32, lance.lmw...@gmail.com wrote:
From: Limin Wang <lance.lmw...@gmail.com>Note: nvenc sdk will truncated user data unregistered SEI if the size > 503. for example, hardcode its size to 504, trace_headers will report below error: Invalid SEI message: payload_size too large (504 504 bytes).
I'm amazed it even does that now.Last time I tested this, encoding straight up failed if the SEI data was too large, since the allocated packet output buffer has a fixed size, and no API to influence that size exists.
Disabling unregistered SEIs by default is probably a good call, given 99% of the time it'll lead to unexpected failures and is not actually intended or used by the user.
It IS technically an API break though, so not 100% sure on this.Ideally it'd be possible to just increase the buffer size, so the SEI data fits.
Where exactly did you see this 503 byte truncation happening?
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
