On Sun, Sep 24, 2017 at 02:42:20PM -0500, Brian Matherly wrote:
> On 9/23/2017 5:22 PM, Michael Niedermayer wrote:
> >On Thu, Sep 14, 2017 at 08:39:19PM -0500, Brian Matherly wrote:
> >>Correctly set frame.interlaced and frame.top_field_first when pic_struct
> >>indicates paired fields.
> >Do you h
On 9/23/2017 5:22 PM, Michael Niedermayer wrote:
On Thu, Sep 14, 2017 at 08:39:19PM -0500, Brian Matherly wrote:
Correctly set frame.interlaced and frame.top_field_first when pic_struct
indicates paired fields.
Do you have a (small) sample that gets fixed by this ?
Can you make a fate test for
On Thu, Sep 14, 2017 at 08:39:19PM -0500, Brian Matherly wrote:
> Correctly set frame.interlaced and frame.top_field_first when pic_struct
> indicates paired fields.
Do you have a (small) sample that gets fixed by this ?
Can you make a fate test for this case ?
[...]
--
Michael GnuPG finger
On 9/14/2017 8:39 PM, Brian Matherly wrote:
Correctly set frame.interlaced and frame.top_field_first when pic_struct
indicates paired fields.
---
libavcodec/hevc_sei.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
index c
Correctly set frame.interlaced and frame.top_field_first when pic_struct
indicates paired fields.
---
libavcodec/hevc_sei.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
index cd55d50..d0f9966 100644
--- a/libavcodec/hevc_sei.