On Fri, Jul 17, 2015 at 9:22 PM, Luca Barbato <[email protected]> wrote: > On 17/07/15 15:18, Vittorio Giovara wrote: >> On Fri, Jul 17, 2015 at 2:27 AM, Luca Barbato <[email protected]> wrote: >>> On 17/07/15 01:44, Vittorio Giovara wrote: >>>> >>>> On Thu, Jul 16, 2015 at 11:33 PM, Luca Barbato <[email protected]> wrote: >>>>> >>>>> Add DCI 4k and 2160p. >>>>> --- >>>>> >>>>> Yes, I'm testing which encoders are able to do something with 4k now =) >>>>> >>>>> libavutil/parseutils.c | 2 ++ >>>>> 1 file changed, 2 insertions(+) >>>>> >>>>> diff --git a/libavutil/parseutils.c b/libavutil/parseutils.c >>>>> index be238f0..4cf4471 100644 >>>>> --- a/libavutil/parseutils.c >>>>> +++ b/libavutil/parseutils.c >>>>> @@ -80,6 +80,8 @@ static const VideoSizeAbbr video_size_abbrs[] = { >>>>> { "hd480", 852, 480 }, >>>>> { "hd720", 1280, 720 }, >>>>> { "hd1080", 1920,1080 }, >>>>> + { "hd2160", 3840,2160 }, >>>> >>>> >>>> imho uhd here >>> >>> >>> Not sure how many people know that. I'd add it as aslias. >> >> you mean they would not know the ITU name? sounds not likely >> also given there are two resolutions ending in 2160, the hd2160 is >> imho more confusing >> > > Ok, so uhd, 4kdci and 4k and 2kdci.
4k alone is as confusing as h2160, imho just drop it -- Vittorio _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
