Re: [libav-devel] [PATCH 4/4] movenc: allow alternative hvc1 h.265 codec tag

2017-06-19 Thread Jan Ekstrom
Hi, On Mon, Jun 19, 2017 at 1:23 PM, Martin Storsjö wrote: > However what I'm left wondering is as a next step, after making this > possible at all, is what should be the default? If the default isn't > compatible with apple tools, I'm pretty sure it'll be a very frequently >

Re: [libav-devel] [PATCH 1/3] movenc: Add an option for enabling negative CTS offsets

2017-02-22 Thread Jan Ekstrom
On Sun, Feb 19, 2017 at 11:22 PM, Martin Storsjö wrote: > This reduces the need for an edit list; streams that start with > e.g. dts=-1, pts=0 can be encoded as dts=0, pts=0 (which is valid > in mov/mp4) by shifting the dts values of all packets forward. > This avoids the need

Re: [libav-devel] [PATCH 2/2] pgssub: Support BT709 subtitles

2016-04-25 Thread Jan Ekstrom
On Apr 25, 2016 6:15 AM, "Vittorio Giovara" wrote: > > > +/* Default to BT.709 colorimetry. In case of <= 576 height use BT.601 */ > > colorimetry? don't you mean color space? > Possibly :) > > +if (avctx->height <= 0 || avctx->height > 576) { > > HD

Re: [libav-devel] [PATCH 2/2] pgssub: Support BT709 subtitles

2016-04-24 Thread Jan Ekstrom
On Sun, Apr 24, 2016 at 9:40 PM, Luca Barbato wrote: > From: Jan Ekström > > Use the frame dimension to guess what is what: > SD is BT.601, HD is BT.709 For those only following the mailing list, the original commit message had some extra information on the

Re: [libav-devel] [PATCH] utvideoenc: Enable support for multiple slices and use them

2014-02-13 Thread Jan Ekstrom
On Thu, Feb 13, 2014 at 9:11 PM, Derek Buitenhuis derek.buitenh...@gmail.com wrote: On 2/13/2014 6:59 PM, Jan Ekström wrote: The official Ut Video encoder only threads with slices, thus until now any files encoded by the libavcodec encoder have only been decode'able with a single thread. The

Re: [libav-devel] [PATCH] utvideoenc: Enable support for multiple slices and use them

2014-02-13 Thread Jan Ekstrom
On Thu, Feb 13, 2014 at 9:40 PM, Derek Buitenhuis derek.buitenh...@gmail.com wrote: On 2/13/2014 7:30 PM, Jan Ekstrom wrote: Because [0,256] is the valid range, not [0,255]? av_clip then? :) OK. That's usable. The real issue, though, is that those values would be invalid, and I do not want

Re: [libav-devel] [PATCH v2] lavc: Add colorimetry values for BT.2020, other non-included ones

2013-11-04 Thread Jan Ekstrom
On Mon, Nov 4, 2013 at 1:28 PM, Jan Ekström jee...@gmail.com wrote: --- doc/APIchanges |4 libavcodec/avcodec.h | 42 +++--- libavcodec/version.h |2 +- 3 files changed, 32 insertions(+), 16 deletions(-) The only difference to v1 is