> > > > > All h266 conformance test clips will not detect as other formats. But if > > you have a well-designed clip, it may be. This is normal case for a raw > > bytestream detector. > > I'm mainly asking because the H.264 probe function does check some PS IDs > to have a bit more confidence that it is looking at an H.264 stream. > > If the collision cases are rare such that they will never overlap except > with crafted streams then this is probably fine. > H.264 and H.265's seq_parameter_set_id are ue(v). So you can check the max value. But for H.266, the sps_seq_parameter_set_id is u(4). and the range is 0 to 15. It's no way to check it's valid or not. We can check sps_pic_width_max_in_luma_samples and sps_pic_height_max_in_luma_samples, but it's not so meanful.
> - Mark > _______________________________________________ > 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". _______________________________________________ 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".
