: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] vdpau: do not use buggy HEVC support by
default
On Tue, 8 Aug 2017 05:15:52 +
Manoj Bonda wrote:
> Hi ,
>
> HEVC issue for read-back API has been fixed and will be part of the upcoming
> drivers.
> Please help us under
On Tue, 8 Aug 2017 05:15:52 +
Manoj Bonda wrote:
> Hi ,
>
> HEVC issue for read-back API has been fixed and will be part of the upcoming
> drivers.
> Please help us understand the issue with the open gl interop.
That's great to hear. (Sorry, saw this only now...)
> As per our understan
On Tue, 8 Aug 2017 05:15:52 +
Manoj Bonda wrote:
> Hi ,
>
> HEVC issue for read-back API has been fixed and will be part of the
> upcoming drivers. Please help us understand the issue with the open
> gl interop. As per our understanding we are mapping the video surface
> to gl using the gl-
Hi ,
HEVC issue for read-back API has been fixed and will be part of the upcoming
drivers.
Please help us understand the issue with the open gl interop.
As per our understanding we are mapping the video surface to gl using the
gl-interop
and the app(mpv) will be doing the merging/de-interlaci
em up along with other
tasks based on the priority
Thanks,
ManojGupta.
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of wm4
Sent: Friday, July 14, 2017 3:54 PM
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] vdpau: do not use
On Fri, 14 Jul 2017 09:55:58 +
Manoj Bonda wrote:
> Hi,
>
> Thanks i'll look into the issue and come up with an ETA ASAP.
> Going on I will be the maintainer of VDPAU. Please direct any VDPAU issues to
> me.
That's great to hear. Is there a bug tracker for this? Other than
fixing the bug
Sent: Friday, July 14, 2017 3:04 PM
To: FFmpeg development discussions and patches
Cc: Yogender Gupta
Subject: Re: [FFmpeg-devel] [PATCH] vdpau: do not use buggy HEVC support by
default
On 2017-07-14 08:19, Yogender Gupta wrote:
> Please help to understand what is broken with a command line,
On 2017-07-14 08:19, Yogender Gupta wrote:
Please help to understand what is broken with a command line, so that
we can address this issue.
This is the issue that the hevc low level decoder outputs frames instead
of fields - which all the other decoders do.
Originally, the vdpau support didn't
On Fri, 14 Jul 2017 08:19:25 +
Yogender Gupta wrote:
> Please help to understand what is broken with a command line, so that we can
> address this issue.
With ffmpeg CLI, you can try something like:
ffmpeg -hwaccel vdpau -i some_8bit_hevc_file.mkv -frames 10 -pix_fmt yuv420p
out.y4m
Yo
: [FFmpeg-devel] [PATCH] vdpau: do not use buggy HEVC support by
default
On Sat, 1 Jul 2017 07:10:47 -0700
Philip Langdale wrote:
> On Sat, 1 Jul 2017 11:40:38 +0200
> wm4 wrote:
>
> > NVIDIA broke its own API when using VDPAU decoding. If you retrieve
> > the decoded YU
On Sat, 1 Jul 2017 07:10:47 -0700
Philip Langdale wrote:
> On Sat, 1 Jul 2017 11:40:38 +0200
> wm4 wrote:
>
> > NVIDIA broke its own API when using VDPAU decoding. If you retrieve
> > the decoded YUV data, or if you map the surfaces with GL interop, the
> > result are interlacing artifacts. Th
On Sat, 1 Jul 2017 11:40:38 +0200
wm4 wrote:
> NVIDIA broke its own API when using VDPAU decoding. If you retrieve
> the decoded YUV data, or if you map the surfaces with GL interop, the
> result are interlacing artifacts. The only way to get non-broken data
> is by using the vdpau video mixer t
NVIDIA broke its own API when using VDPAU decoding. If you retrieve the
decoded YUV data, or if you map the surfaces with GL interop, the result
are interlacing artifacts. The only way to get non-broken data is by
using the vdpau video mixer to convert it to RGB. There is no way to
block the non-wo
13 matches
Mail list logo
