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
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
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,
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)
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
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