On Mon, Oct 13, 2014 at 3:37 PM, Martin Storsjö <[email protected]> wrote: > On Mon, 13 Oct 2014, Vittorio Giovara wrote: > >> Introduced in 0d8a3656ba4c0ae8e4e0c91ff6b07d72a317f9f6. >> >> Reported-by: Ruoyu <[email protected]> >> --- >> libavformat/mov.c | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> diff --git a/libavformat/mov.c b/libavformat/mov.c >> index d4281dc..f767864 100644 >> --- a/libavformat/mov.c >> +++ b/libavformat/mov.c >> @@ -923,7 +923,8 @@ static int mov_read_colr(MOVContext *c, AVIOContext >> *pb, MOVAtom atom) >> * 23001-8) so some adjusting is required */ >> if (color_primaries >= AVCOL_PRI_FILM) >> color_primaries = AVCOL_PRI_UNSPECIFIED; >> - if (color_trc >= AVCOL_TRC_LINEAR || color_trc <= >> AVCOL_TRC_LOG_SQRT || >> + if ((color_trc >= AVCOL_TRC_LINEAR && >> + color_trc <= AVCOL_TRC_LOG_SQRT) || >> color_trc >= AVCOL_TRC_BT2020_10) >> color_trc = AVCOL_TRC_UNSPECIFIED; >> if (color_matrix >= AVCOL_SPC_BT2020_NCL) >> -- >> 1.9.3 (Apple Git-50) > > > The change itself is most probably ok, but the commit message is highly > confusing. What about:
Sounds ok to me, I might as well drop the hash since it's just one change away. Thanks. -- Vittorio _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
