This is the assumption that is made everywhere in the codebase
and in several specifications too. The added benefit is that any
variable referencing range can now be simply considered a boolean.
Signed-off-by: Vittorio Giovara <vittorio.giov...@gmail.com>
---
This is the first patch I had in mind for the transition period after
the bump, when ABI in not exactly stable.
Unrelated to this patch, is there anything else baking for this time?
Cheers,
Vittorio
libavutil/pixfmt.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/libavutil/pixfmt.h b/libavutil/pixfmt.h
index 41498cc..80a0651 100644
--- a/libavutil/pixfmt.h
+++ b/libavutil/pixfmt.h
@@ -389,9 +389,9 @@ enum AVColorSpace {
* MPEG vs JPEG YUV range.
*/
enum AVColorRange {
- AVCOL_RANGE_UNSPECIFIED = 0,
- AVCOL_RANGE_MPEG = 1, ///< the normal 219*2^(n-8) "MPEG" YUV ranges
- AVCOL_RANGE_JPEG = 2, ///< the normal 2^n-1 "JPEG" YUV ranges
+ AVCOL_RANGE_MPEG = 0, ///< the normal 219*2^(n-8) "MPEG" YUV ranges
+ AVCOL_RANGE_UNSPECIFIED = AVCOL_RANGE_MPEG,
+ AVCOL_RANGE_JPEG = 1, ///< the normal 2^n-1 "JPEG" YUV ranges
AVCOL_RANGE_NB, ///< Not part of ABI
};
--
2.10.0
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
