On 28.05.2018 09:30, Xiang, Haihao wrote:
On Sat, 2018-05-26 at 17:29 +0100, Mark Thompson wrote:
On 25/05/18 07:57, Tobias Rapp wrote:
On 25.05.2018 07:58, Xiang, Haihao wrote:
On Thu, 2018-05-24 at 11:15 +0100, Mark Thompson wrote:
For example:
ffmpeg -i bt709_input.mkv -vf colorspace=bt2
On Sat, 2018-05-26 at 17:29 +0100, Mark Thompson wrote:
> On 25/05/18 07:57, Tobias Rapp wrote:
> > On 25.05.2018 07:58, Xiang, Haihao wrote:
> > > On Thu, 2018-05-24 at 11:15 +0100, Mark Thompson wrote:
> > > >
> > > > For example:
> > > >
> > > > ffmpeg -i bt709_input.mkv -vf colorspace=bt2020
On 25/05/18 07:57, Tobias Rapp wrote:
> On 25.05.2018 07:58, Xiang, Haihao wrote:
>> On Thu, 2018-05-24 at 11:15 +0100, Mark Thompson wrote:
>>>
>>> For example:
>>>
>>> ffmpeg -i bt709_input.mkv -vf colorspace=bt2020 bt2020_output.mkv
>>>
>>> will have the output file marked as BT.709 after this p
On Fri, 25 May 2018, Tobias Rapp wrote:
On 25.05.2018 07:58, Xiang, Haihao wrote:
On Thu, 2018-05-24 at 11:15 +0100, Mark Thompson wrote:
For example:
ffmpeg -i bt709_input.mkv -vf colorspace=bt2020 bt2020_output.mkv
will have the output file marked as BT.709 after this patch, where
pre
On 25.05.2018 07:58, Xiang, Haihao wrote:
On Thu, 2018-05-24 at 11:15 +0100, Mark Thompson wrote:
For example:
ffmpeg -i bt709_input.mkv -vf colorspace=bt2020 bt2020_output.mkv
will have the output file marked as BT.709 after this patch, where previously
it was "unspecified". (Explicitly set
On Thu, 2018-05-24 at 11:15 +0100, Mark Thompson wrote:
> On 24/05/18 07:29, Xiang, Haihao wrote:
> > On Wed, 2018-05-23 at 03:27 +0200, Michael Niedermayer wrote:
> > > On Mon, May 21, 2018 at 11:07:34PM +0100, Mark Thompson wrote:
> > > > On 16/05/18 08:19, Haihao Xiang wrote:
> > > > > In lavc/h
On 24/05/18 07:29, Xiang, Haihao wrote:
> On Wed, 2018-05-23 at 03:27 +0200, Michael Niedermayer wrote:
>> On Mon, May 21, 2018 at 11:07:34PM +0100, Mark Thompson wrote:
>>> On 16/05/18 08:19, Haihao Xiang wrote:
In lavc/hevec_vaapi, colour properties in AVCodecContext are needed to
write
On 22.05.2018 00:07, Mark Thompson wrote:
On 16/05/18 08:19, Haihao Xiang wrote:
In lavc/hevec_vaapi, colour properties in AVCodecContext are needed to
write the sequence header
Tested by the command below:
ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
-hwaccel_output_format vaapi -
On Wed, 2018-05-23 at 03:27 +0200, Michael Niedermayer wrote:
> On Mon, May 21, 2018 at 11:07:34PM +0100, Mark Thompson wrote:
> > On 16/05/18 08:19, Haihao Xiang wrote:
> > > In lavc/hevec_vaapi, colour properties in AVCodecContext are needed to
> > > write the sequence header
> > >
> > > Tested
On Mon, May 21, 2018 at 11:07:34PM +0100, Mark Thompson wrote:
> On 16/05/18 08:19, Haihao Xiang wrote:
> > In lavc/hevec_vaapi, colour properties in AVCodecContext are needed to
> > write the sequence header
> >
> > Tested by the command below:
> > ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/r
On 16/05/18 08:19, Haihao Xiang wrote:
> In lavc/hevec_vaapi, colour properties in AVCodecContext are needed to
> write the sequence header
>
> Tested by the command below:
> ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
> -hwaccel_output_format vaapi -i input-with-hdr.mkv -c:v hevc_va
In lavc/hevec_vaapi, colour properties in AVCodecContext are needed to
write the sequence header
Tested by the command below:
ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
-hwaccel_output_format vaapi -i input-with-hdr.mkv -c:v hevc_vaapi
-profile:v main10 output.h265
Signed-off-by: H
12 matches
Mail list logo