On 15/05/15 16:09, Vittorio Giovara wrote: So there are formats that leverage texture compression schemes and somebody wants to leverage the hardware to do the texture decompression.
If texture decompression is not the final step you can't just export the textures outside. The main problem I'm seeing with all those approaches is that you have the same problem we have with hwaccel: heterogeneous memory (and computing). Ideally you'd want to pass to the decoder a custom allocator and an unpack callback for the simple case. For the harder case you'd like to have a full hwaccel solution (and let the user implement its own opencl or such decoder so can do something like texture blend for motion compensation). I do not know enough of the formats to see other problems but I'd rather have the normal and plain C implementations out and then think about how they could be accelerated. lu _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
