On Sun, 22 Jan 2017 12:12:26 -0700
Pavel Koshevoy wrote:
> Yeah, but I don't even get a 1st frame failure with YUV420P 8K from
> h264_cuvid -- all I ever get is a 0 from avcodec_send_packet and
> AVERROR(EAGAIN) from avcodec_receive_frame. This is what I've
> observed with GeForce GT 730 and G
On 1/22/17 11:13 AM, Philip Langdale wrote:
On Sat, 21 Jan 2017 10:27:30 -0700
pkoshe...@gmail.com wrote:
From: Pavel Koshevoy
Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
and only a limited set of resolutions per codec are supported.
Unfortunately CUVID silently drops
On Sun, Jan 22, 2017 at 9:37 AM, Pavel Koshevoy wrote:
> On 01/22/2017 07:05 AM, Timo Rothenpieler wrote:
>>>
>>> Despite wm4 objections I am resubmitting this patch, because I can
>>> find no other reasonable method for rejecting ffmpeg cuvid decoder
>>> when it can't handle a given video stream.
On Sat, 21 Jan 2017 10:27:30 -0700
pkoshe...@gmail.com wrote:
> From: Pavel Koshevoy
>
> Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
> and only a limited set of resolutions per codec are supported.
>
> Unfortunately CUVID silently drops packets for video of unsupported
>
On 01/22/2017 05:28 AM, Mark Thompson wrote:
On 21/01/17 17:35, Pavel Koshevoy wrote:
On Sat, Jan 21, 2017 at 10:27 AM, wrote:
From: Pavel Koshevoy
Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
and only a limited set of resolutions per codec are supported.
Unfortunate
On 01/22/2017 04:58 AM, wm4 wrote:
On Sat, 21 Jan 2017 10:35:50 -0700
Pavel Koshevoy wrote:
On Sat, Jan 21, 2017 at 10:27 AM, wrote:
From: Pavel Koshevoy
-ret = cuvid_test_dummy_decoder(avctx, &ctx->cuparseinfo);
+ret = cuvid_test_dummy_decoder(avctx, &ctx->cuparseinfo,
+
On 01/22/2017 07:05 AM, Timo Rothenpieler wrote:
Despite wm4 objections I am resubmitting this patch, because I can
find no other reasonable method for rejecting ffmpeg cuvid decoder
when it can't handle a given video stream. An unreasonable
alternative would be to duplicate the work that cuvid.
> Despite wm4 objections I am resubmitting this patch, because I can
> find no other reasonable method for rejecting ffmpeg cuvid decoder
> when it can't handle a given video stream. An unreasonable
> alternative would be to duplicate the work that cuvid.c does
> internally on my application side,
On 21/01/17 17:35, Pavel Koshevoy wrote:
> On Sat, Jan 21, 2017 at 10:27 AM, wrote:
>> From: Pavel Koshevoy
>>
>> Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
>> and only a limited set of resolutions per codec are supported.
>>
>> Unfortunately CUVID silently drops packets
On Sat, 21 Jan 2017 10:35:50 -0700
Pavel Koshevoy wrote:
> On Sat, Jan 21, 2017 at 10:27 AM, wrote:
> > From: Pavel Koshevoy
> >
> > Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
> > and only a limited set of resolutions per codec are supported.
> >
> > Unfortunately CUVI
On Sat, 21 Jan 2017 10:35:50 -0700
Pavel Koshevoy wrote:
> On Sat, Jan 21, 2017 at 10:27 AM, wrote:
> > From: Pavel Koshevoy
> >
> > Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
> > and only a limited set of resolutions per codec are supported.
> >
> > Unfortunately CUVI
From: Pavel Koshevoy
Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
and only a limited set of resolutions per codec are supported.
Unfortunately CUVID silently drops packets for video of unsupported
resolution. However, it will error-out at cuvidCreateDecoder call
if the in
On Thu, Jan 12, 2017 at 10:32 AM, Timo Rothenpieler
wrote:
> On 1/9/2017 7:22 PM, pkoshe...@gmail.com wrote:
>> From: Pavel Koshevoy
>> enum AVPixelFormat pix_fmts[3] = { AV_PIX_FMT_CUDA,
>> AV_PIX_FMT_NV12,
>>
On Sat, Jan 21, 2017 at 10:35 AM, Pavel Koshevoy wrote:
> Despite wm4 objections I am resubmitting this patch, because I can
> find no other reasonable method for rejecting ffmpeg cuvid decoder
> when it can't handle a given video stream. An unreasonable
> alternative would be to duplicate the
On Sat, Jan 21, 2017 at 10:27 AM, wrote:
> From: Pavel Koshevoy
>
> Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
> and only a limited set of resolutions per codec are supported.
>
> Unfortunately CUVID silently drops packets for video of unsupported
> resolution. However,
From: Pavel Koshevoy
Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
and only a limited set of resolutions per codec are supported.
Unfortunately CUVID silently drops packets for video of unsupported
resolution. However, it will error-out at cuvidCreateDecoder call
if the in
On 01/12/2017 10:32 AM, Timo Rothenpieler wrote:
On 1/9/2017 7:22 PM, pkoshe...@gmail.com wrote:
From: Pavel Koshevoy
Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
and only a limited set of resolutions per codec are supported.
Given that stream resolution and pixel forma
On 1/9/2017 7:22 PM, pkoshe...@gmail.com wrote:
> From: Pavel Koshevoy
>
> Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
> and only a limited set of resolutions per codec are supported.
>
> Given that stream resolution and pixel format are typically known as a
> result of p
From: Pavel Koshevoy
Evidently CUVID doesn't support decoding 422 or 444 chroma formats,
and only a limited set of resolutions per codec are supported.
Given that stream resolution and pixel format are typically known as a
result of probing it is better to use this info during avcodec_open2
call
19 matches
Mail list logo
