You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were previously using libavif v0.9.2 (with libaom v3.1.2), both built locally on a Mac Intel machine with Xcode 12 and Apple Clang 12.0.0 (clang-1200.0.32.29), to decode .avif images and retrieve RGB color values. After upgrading to libavif v1.2.1 (with libaom v3.12.0)—both built locally on a Mac M2 machine with Xcode 16 and Apple Clang 16.0.0 (clang-1600.0.26.6)—we noticed that for some images, the RGB color values differ slightly (by ±1) compared to the results from v0.9.2. Same happens when Mac intel and XCode16 (Apple Clang 16.0.0 (clang-1600.0.26.6)) is used for compiling v1.2.1 (with libaom v3.12.0).
Interestingly, when compiling v1.2.1 (libaom v3.12.0) on the same Mac Intel machine with Xcode 12 and Apple Clang 12.0.0, the RGB values match the previous results exactly.
Is this a known behaviour, and do we have any insights into what might be causing these differences?
The text was updated successfully, but these errors were encountered:
For building libaom using below command to generate Xcode project and then building using Xcode: cmake ./aom -G Xcode -DAOM_TARGET_CPU=generic -DENABLE_EXAMPLES=0 -DENABLE_TESTS=0 -DENABLE_TOOLS=0 -DBUILD_SHARED_LIBS=OFF -DCONFIG_PIC=1 -DENABLE_DOCS=0 -DENABLE_TESTDATA=0 -DCMAKE_OSX_ARCHITECTURES="arm64;x86_64"
For libavif, I was facing issues similar to #2780 while using Xcode generator for generating Xcode project and then building.
Hence had to use below commands:
Just following up to check if you had a chance to review this issue. Please let me know if you need any further details or clarification. I’d appreciate any updates when you have the time. Thank you!
Uh oh!
There was an error while loading. Please reload this page.
We were previously using libavif v0.9.2 (with libaom v3.1.2), both built locally on a Mac Intel machine with Xcode 12 and Apple Clang 12.0.0 (clang-1200.0.32.29), to decode .avif images and retrieve RGB color values. After upgrading to libavif v1.2.1 (with libaom v3.12.0)—both built locally on a Mac M2 machine with Xcode 16 and Apple Clang 16.0.0 (clang-1600.0.26.6)—we noticed that for some images, the RGB color values differ slightly (by ±1) compared to the results from v0.9.2. Same happens when Mac intel and XCode16 (Apple Clang 16.0.0 (clang-1600.0.26.6)) is used for compiling v1.2.1 (with libaom v3.12.0).
Interestingly, when compiling v1.2.1 (libaom v3.12.0) on the same Mac Intel machine with Xcode 12 and Apple Clang 12.0.0, the RGB values match the previous results exactly.
Is this a known behaviour, and do we have any insights into what might be causing these differences?
The text was updated successfully, but these errors were encountered: