>>This seems to have forgotten to actually allocate anything?
I made an empty allocation here, since in fact all allocation
takes place in the decoder.
>>This makes it look like you really wanted to implement map_from,
not transfer_data_from.
These functions were conceived specifically for transfe
On 01/05/2024 19:38, Dmitrii Ovchinnikov wrote:
> Adds hwcontext_amf, which allows to use shared AMF
> context for the encoder, decoder and AMF-based filters,
> without copy to the host memory.
> It will also allow you to use some optimizations in
> the interaction of components (for example, SAV)
May 2, 2024, 10:04 by ovchinnikov.dmit...@gmail.com:
> >>Is there a reason to add this code in now?
> DX12 and Vulkan native encoders will expose less features compare to AMF,
> at least in foreseeable feature. The missing features include low latency,
> PreAnalysis including look-ahead etc.
>
Do
>>Is there a reason to add this code in now?
DX12 and Vulkan native encoders will expose less features compare to AMF,
at least in foreseeable feature. The missing features include low latency,
PreAnalysis including look-ahead etc. AMF context on Windows allows fully
enable SAV - ability to utilize
May 1, 2024, 20:38 by ovchinnikov.dmit...@gmail.com:
> Adds hwcontext_amf, which allows to use shared AMF
> context for the encoder, decoder and AMF-based filters,
> without copy to the host memory.
> It will also allow you to use some optimizations in
> the interaction of components (for example,
Adds hwcontext_amf, which allows to use shared AMF
context for the encoder, decoder and AMF-based filters,
without copy to the host memory.
It will also allow you to use some optimizations in
the interaction of components (for example, SAV) and make a more
manageable and optimal setup for using GPU
