-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grid image arranges tiles in wrong order if IDs in the iref
are not sequential
#2311
Comments
Yes, that's what I meant but expressed incorrectly. It should respect the order in the |
iref
are not sequential
Not sure what GIMP 2.10.36 uses under the hood but it opens the out-of-order |
It uses libheif. Same as I used to create the file. |
(Thank you for taking the time to report this issue by the way.) |
Instead of using the order from the constructed items, use the dimg ordering from the iref box. Fixes the libavif bug AOMediaCodec/libavif#2311 PiperOrigin-RevId: 655255206
Instead of using the order from the constructed items, use the dimg ordering from the iref box. Fixes the libavif bug AOMediaCodec/libavif#2311 PiperOrigin-RevId: 655255206
Instead of using the order from the constructed items, use the dimg ordering from the iref box. Fixes the libavif bug AOMediaCodec/libavif#2311 PiperOrigin-RevId: 655255206
To test the fix for this issue, we also need an image grid in which multiple grid tiles reference the same image item. (In the extreme case, all grid tiles reference the same image item.) @farindk Dirk: do yo happen to have such an image available? |
I manually edited The image does not work in Chrome (libavif).
Which is compliant with the ISOBMFF specification ISO/IEC 14496-12:
A workaround would be an intermediate Anyway I believe this is a different issue than #2311. |
Instead of using the order from the constructed items, use the dimg ordering from the iref box. Fixes the libavif bug AOMediaCodec/libavif#2311 PiperOrigin-RevId: 655255206
Yannis: That's good news. I was mislead by the incorrect comment in libavif. Thank you for finding proof that the image grid I requested is not compliant with ISOBMFF. |
Instead of using the order from the constructed items, use the dimg ordering from the iref box. Fixes the libavif bug AOMediaCodec/libavif#2311 PiperOrigin-RevId: 655255206
Instead of using the order from the constructed items, use the dimg ordering from the iref box. Fixes the libavif bug AOMediaCodec/libavif#2311 PiperOrigin-RevId: 655255206
Instead of using the order from the constructed items, use the dimg ordering from the iref box. Fixes the libavif bug AOMediaCodec/libavif#2311 PiperOrigin-RevId: 655255206
Instead of using the order from the constructed items, use the dimg ordering from the iref box. Fixes the libavif bug AOMediaCodec/libavif#2311 PiperOrigin-RevId: 656071329
Changed since 1.1.0 * In avif.h, change "AVIF_API AVIF_NODISCARD" back to "AVIF_NODISCARD AVIF_API" to fix clang-cl and MSVC compilation errors in the shared library build on Windows. * Fix -DAVIF_GTEST=SYSTEM, AOMediaCodec/libavif#2258. * Fix infe_type and codec_config_type wrongly read as byte-aligned fields in the experimental feature AVIF_ENABLE_EXPERIMENTAL_METAV1. * When building aom as a local dependency, runtime CPU detection (`CONFIG_RUNTIME_CPU_DETECT`) is now always `ON`; in 1.1.0 it had been disabled for non-native builds. * Fix CMake config shared library leaks AOMediaCodec/libavif#2264. * Fix clang-cl compilation. * Update gain map metadata to current ISO 21496-1 draft. * cmake: Only search for ASM_NASM language on x86_64 platforms. * Fix "No known features for CXX compiler" CMake error. * Fix aom link flags so that transitive library link flags are included when aom is a static library AOMediaCodec/libavif#2274. * Fix out-of-order 'dimg' grid associations AOMediaCodec/libavif#2311. * Report files with an item used in multiple 'dimg' boxes with AVIF_RESULT_NOT_IMPLEMENTED instead of AVIF_RESULT_INVALID_IMAGE_GRID.
libavif apparently assumes that the tile IDs of a grid image are sequential. If that is not the case, the tiles are composed into the output image in an incorrect arrangement.
Here is an example image that is decoded by libavif like this:
The text was updated successfully, but these errors were encountered: