feat: capture mipmap generation options in writer metadata params - #1238
walcht wants to merge 2 commits into
Conversation
Sorry, something went wrong.
* This commit captures mipmap generation options in KTXWriterScParams metadata entry only if mipmap generation is enabled. This might help ktx2 file consumers to, for instance, regenerate the mipmaps using the same params. Signed-off-by: Walid Chtioui <walid.chtioui.main@gmail.com>
|
CTS PR: KhronosGroup/KTX-Software-CTS#82 The MingW CI is failing because I pushed CTS after pushing this PR; again, I keep forgetting to push CTS first ... |
Sorry, something went wrong.
Signed-off-by: Walid Chtioui <walid.chtioui.main@gmail.com>
Yes (to some degree). I enabled this for ASTC as well. For Basis Universal codecs it requires more work which is why I just ignored it.
Yes. This is just a heuristic for a rare use case that is advised against (unless input KTX2 file is not lossy compressed which is probably very rare). |
Sorry, something went wrong.
Fixes Feature request: record mipmap generation options for ktx create/encode #1196
This commit captures mipmap generation options in KTXWriterScParams metadata entry only if mipmap generation is enabled. This might help ktx2 file consumers to, for instance, regenerate the mipmaps using the same params.