>>
>> I want to add a mapped-frame/dummy mode to the CUDA frame allocator, where
>> it does everything a normal hwframes ctx does, except allocating memory,
>> because the backing memory comes mapped from the cuvid frame.
>>
>> Which is a simple flag to set, but there is no way to tell it righ
On 07/05/18 21:52, Timo Rothenpieler wrote:
>> Nack. Implementation-specific details go in the implementation-specific
>> structure (AVHWFramesContext.hwctx).
>>
>> What are you actually thining of using this for? If you want to add flags
>> which are in common between multiple different implem
Nack. Implementation-specific details go in the implementation-specific
structure (AVHWFramesContext.hwctx).
What are you actually thining of using this for? If you want to add flags
which are in common between multiple different implementations then maybe it
would be suitable to put it here
On 07/05/18 19:39, Timo Rothenpieler wrote:
> ---
> doc/APIchanges| 3 +++
> libavutil/hwcontext.h | 7 +++
> libavutil/version.h | 2 +-
> 3 files changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/doc/APIchanges b/doc/APIchanges
> index ede5b186ae..307c7a51ee 100644
> --- a
On 2018-05-07 11:39, Timo Rothenpieler wrote:
---
doc/APIchanges| 3 +++
libavutil/hwcontext.h | 7 +++
libavutil/version.h | 2 +-
3 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/doc/APIchanges b/doc/APIchanges
index ede5b186ae..307c7a51ee 100644
--- a/doc/APIchange
---
doc/APIchanges| 3 +++
libavutil/hwcontext.h | 7 +++
libavutil/version.h | 2 +-
3 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/doc/APIchanges b/doc/APIchanges
index ede5b186ae..307c7a51ee 100644
--- a/doc/APIchanges
+++ b/doc/APIchanges
@@ -15,6 +15,9 @@ libavut
