Add custom codec callback in avifEncoder - #2381
Conversation
wantehchang
left a comment
There was a problem hiding this comment.
Yannis: I only took a cursory look at this pull request. The commit message has the subject line "Add custom codec callback in avifEncoder". That is confusing, because these callbacks do not seem to provide access to a custom AV1 codec. Should we change "custom codec" to "custom encode data"?
Thank you. This PR is a proof-of-concept to kickstart a discussion, not a request to merge code.
I did not mention AV1. This could be used for any kind of coded samples (AV2?) but to be compliant with the AVIF specification it would have to be AV1 samples indeed.
To me the piece of software that generates encoded data is a codec, so "custom codec callback" is accurate. Whether that is used to feed already compressed samples or to actually encode pixels on the spot, it is opaque to the libavif API. |
|
Note that |
|
I tagged the new The new API can be fuzzed in another PR once the design is settled. |
|
I had another go at it to answer Maryla's comments but the added API starts to be large. I wonder if this is still worth it. Thoughts? |
|
@y-guyon do you think this PR leads us to be able to demux AVIFs? I'm looking for a way to access raw av1 encoded packets to decode on them on GPU. previously you pointed to this PR as the one that can potentially enable it. do you think it is feasible? |
No, this PR only allows already encoded AV1 OBU sequences to be passed to libavif at encoding. I believe you would need something similar but on the decoding side. |
|
Other libraries should be able to do that. FFmpeg's libavformat, or gpac's libgpac? Note that if the image is a grid, you will have to get each grid cell item data and stitch up the image yourself. Same thing if there is alpha, that will be a different item. Not sure libavformat can get you the different item data, but libgpac should be able to, although I haven't actually tried either. |
No description provided.