You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, both x264 and x265 support writing a string into their SEI headers that contain a simple key=value space separated string that contains information related to encoder specific settings (see x264_param2string() for what x264 does for generating the string, and x264_sei_version_write() for the full string it writes, similar thing with x265_param2string()) and this can really help when trying to determine what might be the difference between two nearly identical bitstreams.
This format is obviously not necessarily standardized, as not all h264 and h265 encoders will put the same information, but some common open source ones do (for example kvazzar does so in encoder_state_write_bitstream_prefix_sei_version())
A cursory glance at the spec does not seem to hint at any place where it might be possible to insert such a string into the av1 bitstream, whether that would be in the obu metadata header or somewhere else for encoder specific settings, however, someone did mention that perhaps it may be possible to insert such information in a padding OBU https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/1912
The text was updated successfully, but these errors were encountered:
Currently, both x264 and x265 support writing a string into their SEI headers that contain a simple key=value space separated string that contains information related to encoder specific settings (see
x264_param2string()
for what x264 does for generating the string, andx264_sei_version_write()
for the full string it writes, similar thing withx265_param2string()
) and this can really help when trying to determine what might be the difference between two nearly identical bitstreams.This format is obviously not necessarily standardized, as not all h264 and h265 encoders will put the same information, but some common open source ones do (for example kvazzar does so in
encoder_state_write_bitstream_prefix_sei_version()
)A cursory glance at the spec does not seem to hint at any place where it might be possible to insert such a string into the av1 bitstream, whether that would be in the obu metadata header or somewhere else for encoder specific settings, however, someone did mention that perhaps it may be possible to insert such information in a padding OBU https://gitlab.com/AOMediaCodec/SVT-AV1/-/issues/1912
The text was updated successfully, but these errors were encountered: