ore it.
Unless it's changed recently and I've missed it, the scale filter will
not be interlaced aware, so you might end up blurring the colours for
the two fields in each frame.
--
Mark Himsley
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https:/
signed to
output two rasters, each containing one or the other of the fields
that were contained in the input raster.
--
Mark Himsley
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visi
On Sun, 8 Dec 2019 at 10:03, Ted Park wrote:
>
> > When I play the file downloaded from that page on an VG 4K Dolby
> > Vision capable TV it plays correctly with the right colours, but the
> > colours are way wrong when decoded/converted with FFmpeg.
> >
> > Should I be expecting Dolby Vision
hted P-Frames: Y:8.7% UV:5.0%
[libx264 @ 0x37f2940] ref P L0: 68.6% 13.3% 11.9% 6.1% 0.1%
[libx264 @ 0x37f2940] ref B L0: 88.4% 9.2% 2.4%
[libx264 @ 0x37f2940] ref B L1: 93.4% 6.6%
[libx264 @ 0x37f2940] kb/s:26957.74
--
Mark Himsley
___
ffmpeg-u
u can give your customer your compiled version of FFmpeg
so long as you make available all of the source code including your patches
from which you compiled your version of FFmpeg.
--
Mark Himsley
___
ffmpeg-user mailing list
ffmpeg-user@f
ILD >=
>> 68"
This has been discussed on ffmpeg-devel with the simplest fix being
adding -lm and -lpthreads to --extra-libs.
http://ffmpeg.org/pipermail/ffmpeg-devel/2017-October/217986.html
--
Mark Himsley
___
ffmpeg-user ma
