Am 08.05.2018 um 17:49 schrieb wm4:
On Tue, 8 May 2018 17:43:49 +0200
Timo Rothenpieler wrote:
-frame->buf[0] = av_buffer_pool_get(ctx->pool);
+if (frctx->flags & AV_CUDA_HWFRAMES_DUMMY_MODE)
+frame->buf[0] = av_buffer_create(NULL, 0, NULL, NULL, 0);
+else
+frame->b
On Tue, 8 May 2018 17:43:49 +0200
Timo Rothenpieler wrote:
> >> -frame->buf[0] = av_buffer_pool_get(ctx->pool);
> >> +if (frctx->flags & AV_CUDA_HWFRAMES_DUMMY_MODE)
> >> +frame->buf[0] = av_buffer_create(NULL, 0, NULL, NULL, 0);
> >> +else
> >> +frame->buf[0] = av_buf
-frame->buf[0] = av_buffer_pool_get(ctx->pool);
+if (frctx->flags & AV_CUDA_HWFRAMES_DUMMY_MODE)
+frame->buf[0] = av_buffer_create(NULL, 0, NULL, NULL, 0);
+else
+frame->buf[0] = av_buffer_pool_get(ctx->pool);
+
Is this really needed? Because at least videotoolbox als
On Mon, 7 May 2018 23:46:48 +0200
Timo Rothenpieler wrote:
> Frames can be mapped from nvdec/cuvid, not needing any actual memory
> allocation, but all other features of the hw_frames_ctx.
> Hence the dummy-mode, which does not allocate any (notable amounts of)
> memory but otherwise behaves the
>
>> Frames can be mapped from nvdec/cuvid, not needing any actual memory
>> allocation, but all other features of the hw_frames_ctx.
>> Hence the dummy-mode, which does not allocate any (notable amounts of)
>> memory but otherwise behaves the exact same.
Can someone explain the actual use-case?
2018-05-08 5:10 GMT+08:00 Timo Rothenpieler :
> Frames can be mapped from nvdec/cuvid, not needing any actual memory
> allocation, but all other features of the hw_frames_ctx.
> Hence the dummy-mode, which does not allocate any (notable amounts of)
> memory but otherwise behaves the exact same.
>
On 07/05/18 22:28, Timo Rothenpieler wrote:
> Am 07.05.2018 um 23:22 schrieb Mark Thompson:
>> On 07/05/18 22:10, Timo Rothenpieler wrote:
>>> Frames can be mapped from nvdec/cuvid, not needing any actual memory
>>> allocation, but all other features of the hw_frames_ctx.
>>> Hence the dummy-mode,
Frames can be mapped from nvdec/cuvid, not needing any actual memory
allocation, but all other features of the hw_frames_ctx.
Hence the dummy-mode, which does not allocate any (notable amounts of)
memory but otherwise behaves the exact same.
---
doc/APIchanges | 3 +++
libavutil/hwcon
Am 07.05.2018 um 23:22 schrieb Mark Thompson:
On 07/05/18 22:10, Timo Rothenpieler wrote:
Frames can be mapped from nvdec/cuvid, not needing any actual memory
allocation, but all other features of the hw_frames_ctx.
Hence the dummy-mode, which does not allocate any (notable amounts of)
memory bu
On 07/05/18 22:10, Timo Rothenpieler wrote:
> Frames can be mapped from nvdec/cuvid, not needing any actual memory
> allocation, but all other features of the hw_frames_ctx.
> Hence the dummy-mode, which does not allocate any (notable amounts of)
> memory but otherwise behaves the exact same.
> ---
Frames can be mapped from nvdec/cuvid, not needing any actual memory
allocation, but all other features of the hw_frames_ctx.
Hence the dummy-mode, which does not allocate any (notable amounts of)
memory but otherwise behaves the exact same.
---
doc/APIchanges | 3 +++
libavutil/hwcon
11 matches
Mail list logo
