On Thu, Apr 6, 2017 at 1:08 PM, Hendrik Leppkes wrote:
> On Thu, Apr 6, 2017 at 11:35 AM, Steve Lhomme wrote:
>> On Thu, Apr 6, 2017 at 11:08 AM, Hendrik Leppkes wrote:
>>> On Thu, Apr 6, 2017 at 11:01 AM, Steve Lhomme wrote:
Hi,
As I am progressing in proper HDR10 support in VLC
On Thu, Apr 6, 2017 at 11:35 AM, Steve Lhomme wrote:
> On Thu, Apr 6, 2017 at 11:08 AM, Hendrik Leppkes wrote:
>> On Thu, Apr 6, 2017 at 11:01 AM, Steve Lhomme wrote:
>>> Hi,
>>>
>>> As I am progressing in proper HDR10 support in VLC, I am facing an
>>> issue. The mastering (and lighting pending
On Thu, Apr 6, 2017 at 12:22 PM, wm4 wrote:
> On Thu, 6 Apr 2017 11:48:54 +0200
> Steve Lhomme wrote:
>
>> On Thu, Apr 6, 2017 at 11:38 AM, wm4 wrote:
>> > On Thu, 6 Apr 2017 11:08:24 +0200
>> > Hendrik Leppkes wrote:
>> >
>> >> On Thu, Apr 6, 2017 at 11:01 AM, Steve Lhomme wrote:
>> >> > Hi,
On 06/04/2017 12:22, wm4 wrote:
> I think these AVCodecContext fields should be removed.
You need to split decoding context from encoding context to do that...
lu
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinf
On Thu, 6 Apr 2017 11:48:54 +0200
Steve Lhomme wrote:
> On Thu, Apr 6, 2017 at 11:38 AM, wm4 wrote:
> > On Thu, 6 Apr 2017 11:08:24 +0200
> > Hendrik Leppkes wrote:
> >
> >> On Thu, Apr 6, 2017 at 11:01 AM, Steve Lhomme wrote:
> >> > Hi,
> >> >
> >> > As I am progressing in proper HDR10 su
On Thu, Apr 6, 2017 at 11:38 AM, wm4 wrote:
> On Thu, 6 Apr 2017 11:08:24 +0200
> Hendrik Leppkes wrote:
>
>> On Thu, Apr 6, 2017 at 11:01 AM, Steve Lhomme wrote:
>> > Hi,
>> >
>> > As I am progressing in proper HDR10 support in VLC, I am facing an
>> > issue. The mastering (and lighting pending
On Thu, Apr 6, 2017 at 11:38 AM, Luca Barbato wrote:
> On 06/04/2017 11:01, Steve Lhomme wrote:
>> I CC'ed libav as they have opinions on possible API changes, even
>> though there is no mastering metadata support in there yet.
>
> You should send over those changes otherwise here isn't much we ca
On 06/04/2017 11:01, Steve Lhomme wrote:
> I CC'ed libav as they have opinions on possible API changes, even
> though there is no mastering metadata support in there yet.
You should send over those changes otherwise here isn't much we can say :)
It should be a side-data like many other from what
On Thu, 6 Apr 2017 11:08:24 +0200
Hendrik Leppkes wrote:
> On Thu, Apr 6, 2017 at 11:01 AM, Steve Lhomme wrote:
> > Hi,
> >
> > As I am progressing in proper HDR10 support in VLC, I am facing an
> > issue. The mastering (and lighting pending patch) metadata are set on
> > the AVFrame but not ava
On Thu, Apr 6, 2017 at 11:08 AM, Hendrik Leppkes wrote:
> On Thu, Apr 6, 2017 at 11:01 AM, Steve Lhomme wrote:
>> Hi,
>>
>> As I am progressing in proper HDR10 support in VLC, I am facing an
>> issue. The mastering (and lighting pending patch) metadata are set on
>> the AVFrame but not available
Hi,
As I am progressing in proper HDR10 support in VLC, I am facing an
issue. The mastering (and lighting pending patch) metadata are set on
the AVFrame but not available to the ff_get_format() receiver.
That means when we configure our vout and decoder we don't know if
it's going to have HDR met
On Thu, Apr 6, 2017 at 11:01 AM, Steve Lhomme wrote:
> Hi,
>
> As I am progressing in proper HDR10 support in VLC, I am facing an
> issue. The mastering (and lighting pending patch) metadata are set on
> the AVFrame but not available to the ff_get_format() receiver.
>
> That means when we configur
12 matches
Mail list logo