Quoting Luca Barbato (2017-01-16 21:39:12)
> On 13/01/2017 16:38, Luca Barbato wrote:
> > On 13/01/2017 15:16, Anton Khirnov wrote:
> >> What about all the other nvenc calls? Is this documented anywhere?
> >
> > It is not documented and before I assumed that the functions would
> > do that interna
On 13/01/2017 16:38, Luca Barbato wrote:
> On 13/01/2017 15:16, Anton Khirnov wrote:
>> What about all the other nvenc calls? Is this documented anywhere?
>
> It is not documented and before I assumed that the functions would
> do that internally, the patch unbreaks my use-case and if that's the
>
On 13/01/2017 3:28 pm, Luca Barbato wrote:
> Make sure that NVENC does not misbehave if other cuda usages happen in the
> application.
> libavcodec/nvenc.c | 7 +++
> libavcodec/nvenc.h | 2 ++
> 2 files changed, 9 insertions(+)
Looks ok.
Thanks
Ruta
--
On 13/01/2017 15:16, Anton Khirnov wrote:
> What about all the other nvenc calls? Is this documented anywhere?
It is not documented and before I assumed that the functions would do
that internally, the patch unbreaks my use-case and if that's the case I
can just put the push/pop around the whole f
Quoting Luca Barbato (2017-01-13 10:57:11)
> Make sure that NVENC does not misbehave if other cuda usages happen
> in the application.
> ---
>
> libavcodec/nvenc.c | 7 +++
> libavcodec/nvenc.h | 2 ++
> 2 files changed, 9 insertions(+)
>
> diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.
Make sure that NVENC does not misbehave if other cuda usages happen
in the application.
---
libavcodec/nvenc.c | 7 +++
libavcodec/nvenc.h | 2 ++
2 files changed, 9 insertions(+)
diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
index 4054e43..fe7b7f4 100644
--- a/libavcodec/nvenc.c
+++
