On 12/09/17 02:43, James Almer wrote:
> On 8/20/2017 7:41 PM, Mark Thompson wrote:
>> This avoids confusion with equivalent H.265 SEI values when both are
>> being used at the same time.
>>
>> (cherry picked from commit 6ea220cbeec8863e2006a03b73bed52db2b13ee7)
>> ---
>> libavcodec/h264_parser.c
On 8/20/2017 7:41 PM, Mark Thompson wrote:
> This avoids confusion with equivalent H.265 SEI values when both are
> being used at the same time.
>
> (cherry picked from commit 6ea220cbeec8863e2006a03b73bed52db2b13ee7)
> ---
> libavcodec/h264_parser.c | 26 -
> libavc
This avoids confusion with equivalent H.265 SEI values when both are
being used at the same time.
(cherry picked from commit 6ea220cbeec8863e2006a03b73bed52db2b13ee7)
---
libavcodec/h264_parser.c | 26 -
libavcodec/h264_sei.c | 20 ++--
libav