issue_owner_repo
listlengths 2
2
| issue_body
stringlengths 0
261k
⌀ | issue_title
stringlengths 1
925
| issue_comments_url
stringlengths 56
81
| issue_comments_count
int64 0
2.5k
| issue_created_at
stringlengths 20
20
| issue_updated_at
stringlengths 20
20
| issue_html_url
stringlengths 37
62
| issue_github_id
int64 387k
2.46B
| issue_number
int64 1
127k
|
|---|---|---|---|---|---|---|---|---|---|
[
"strukturag",
"libheif"
]
| ```
...
Installing SDK version 1.37.40 ...
error: the fastcomp backend is no longer supported. Please use an older version of emsdk (for example 3.1.29) if you want to install the old fastcomp-based SDK
```
https://github.com/joutvhu/libheif-web/actions/runs/4094245453/jobs/7060289445 | Error: the fastcomp backend is no longer supported when run scripts/install-ci-linux.sh | https://api.github.com/repos/strukturag/libheif/issues/779/comments | 1 | 2023-02-06T13:35:40Z | 2023-02-06T13:42:45Z | https://github.com/strukturag/libheif/issues/779 | 1,572,584,067 | 779 |
[
"strukturag",
"libheif"
]
|
'libheif' is distributed under the terms of the LGPL license but I am wondering about the GPL license (version 3) which is present in the COPYING folder. Example programs used to be under GPL license but after this https://github.com/strukturag/libheif/issues/87 issue, they all were changed into MIT license. I am guessing that GPL-licensed text in copying.txt is redundant and no code in 'libheif' comes under this now. I am looking forward to the confirmation about this. | Why GPL license is present in copying folder of libheif? | https://api.github.com/repos/strukturag/libheif/issues/778/comments | 5 | 2023-02-06T12:42:32Z | 2023-02-16T14:38:16Z | https://github.com/strukturag/libheif/issues/778 | 1,572,503,266 | 778 |
[
"strukturag",
"libheif"
]
| Hi,everone
After we used the Heif_enc in libheif to transfer the Heif picture, we put it on the Android phone to find out that there are excessive exposure problems.
It is found that it seems that in Android that can only support Limited HEIF pictures, and heif_enc can only be set to full rang = 1. Full_range_flag = 0 parameters are invalid in SPS | Heif_enc encoding is too explosive in Android phones | https://api.github.com/repos/strukturag/libheif/issues/777/comments | 5 | 2023-02-02T10:37:04Z | 2023-03-06T13:58:34Z | https://github.com/strukturag/libheif/issues/777 | 1,567,782,796 | 777 |
[
"strukturag",
"libheif"
]
| Building 1.14.2 on OS X 10.13, using Apple's xcode compiler toolchain and other libraries via fink:
```
g++ -DHAVE_CONFIG_H -I. -I.. -I/sw/include -I.. -I.. -I/sw/include/libpng16 -g -O2 -std=gnu++11 -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-error=unused-parameter -Wno-error=deprecated-declarations -Wno-error=potentially-evaluated-expression -Wno-error=tautological-compare -Wno-error=tautological-constant-out-of-range-compare -MT heif_enc-heif_enc.o -MD -MP -MF .deps/heif_enc-heif_enc.Tpo -c -o heif_enc-heif_enc.o `test -f 'heif_enc.cc' || echo './'`heif_enc.cc
heif_enc.cc:397:11: error: cannot initialize a variable of type 'boolean' with an rvalue of type 'bool'
boolean embeddedXMPFlag = ReadXMPFromJPEG(&cinfo, xmpData);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
heif_enc.cc:402:11: error: cannot initialize a variable of type 'boolean' with an rvalue of type 'bool'
boolean embeddedEXIFFlag = ReadEXIFFromJPEG(&cinfo, exifData);
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 errors generated.
```
| Build-failure: examples/heif_enc.cc type mismatch | https://api.github.com/repos/strukturag/libheif/issues/776/comments | 2 | 2023-02-01T13:56:45Z | 2023-02-02T15:39:43Z | https://github.com/strukturag/libheif/issues/776 | 1,566,160,946 | 776 |
[
"strukturag",
"libheif"
]
| Getting this error when trying to build libheif
encoder_png.cc:124:63: error: ‘png_set_eXIf_1’ was not declared in this scope
png_set_eXIf_1(png_ptr, info_ptr, (png_uint_32)size, ptr);
| Issue while builiding libheif | https://api.github.com/repos/strukturag/libheif/issues/774/comments | 3 | 2023-01-31T14:21:30Z | 2023-02-09T11:29:30Z | https://github.com/strukturag/libheif/issues/774 | 1,564,409,114 | 774 |
[
"strukturag",
"libheif"
]
| The `ispe` box should show the image dimensions _prior to_ applying the transformative properties, according to the standard.
I'm not sure this is handled in this way when writing images with `clap` or `irot` properties.
(See also #762). | Check correct use of ispe property | https://api.github.com/repos/strukturag/libheif/issues/773/comments | 1 | 2023-01-29T12:03:31Z | 2023-04-28T11:24:00Z | https://github.com/strukturag/libheif/issues/773 | 1,561,256,459 | 773 |
[
"strukturag",
"libheif"
]
| Operating system : MacOS
Docker container
I'm not able to compile and get this error :
```
#0 64.86 mv -f plugins/.deps/libheif_la-heif_decoder_libde265.Tpo plugins/.deps/libheif_la-heif_decoder_libde265.Plo
#0 64.86 /bin/bash ../libtool --tag=CXX --mode=link g++ -fvisibility=hidden -I@CMAKE_INSTALL_PREFIX@/include -DLIBHEIF_EXPORTS -I.. -DHAVE_VISIBILITY -g -O2 -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-error=unused-parameter -Wno-error=deprecated-declarations -Wno-error=tautological-compare -version-info 15:2:14 -L/usr/local/lib/ -o libheif.la -rpath /usr/local/lib libheif_la-bitstream.lo libheif_la-box.lo libheif_la-error.lo libheif_la-heif_file.lo libheif_la-heif_image.lo libheif_la-heif.lo libheif_la-heif_context.lo libheif_la-heif_hevc.lo libheif_la-heif_init.lo libheif_la-heif_avif.lo libheif_la-heif_plugin_registry.lo libheif_la-heif_plugin.lo libheif_la-heif_colorconversion.lo libheif_la-metadata_compression.lo libheif_la-nclx.lo plugins/libheif_la-heif_decoder_libde265.lo -L@CMAKE_INSTALL_PREFIX@/lib -lde265 -lpthread
#0 64.92 ../libtool: line 7577: cd: @CMAKE_INSTALL_PREFIX@/lib: No such file or directory
#0 64.93 libtool: error: cannot determine absolute directory name of '@CMAKE_INSTALL_PREFIX@/lib'
#0 64.93 make[2]: *** [Makefile:1048: libheif.la] Error 1
#0 64.93 make[2] : on quitte le répertoire « /usr/src/libheif/libheif »
#0 64.93 make[1]: *** [Makefile:541: all-recursive] Error 1
#0 64.93 make[1] : on quitte le répertoire « /usr/src/libheif »
#0 64.93 make: *** [Makefile:450: all] Error 2
```
This is my docker-compose file :
```
RUN cd /usr/src/ && \
git clone --depth 1 --branch v1.14.2 https://github.com/strukturag/libheif.git && \
cd libheif/ && \
./autogen.sh && \
./configure --prefix=/usr/local && \
make -j$(nproc) && \
make install && \
ldconfig /usr/local/lib
```
I don't understand why it does not work on Docker with MacOS , but it works well on a docker host with Linux
Thanks!
| @CMAKE_INSTALL_PREFIX@/lib: No such file or directory | https://api.github.com/repos/strukturag/libheif/issues/771/comments | 6 | 2023-01-28T15:21:33Z | 2023-01-31T16:06:51Z | https://github.com/strukturag/libheif/issues/771 | 1,560,895,554 | 771 |
[
"strukturag",
"libheif"
]
| Hi,
I am trying to create a static build of `heif-convert`. Apologies if this is a rookie mistake, I am not well versed in the c++ toolchain.
I first tried to use the CMake approach as autogen is deprecated. I followed instructions from #189, but the result was a dynamically linked binary.
```
$ mkdir build
$ cd build
$ cmake -DBUILD_SHARED_LIBS=OFF ..
$ make
$ file examples/heif-convert
heif-convert: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=b45e6dcd01374f8a7e03b46221f6559ad36e9e8b, for GNU/Linux 3.2.0, not stripped
```
I also tried autogen, but the result was the same:
```sh
$ ./autogen.sh
$ ./configure --enable-static
$ make
$ file examples/.libs/heif-convert
heif-convert: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=1eb37876e66816492eda3ce886b8fe2c5150533e, for GNU/Linux 3.2.0, with debug_info, not stripped
```
Could anyone point me to the right direction please? | Static build of heif-convert | https://api.github.com/repos/strukturag/libheif/issues/767/comments | 2 | 2023-01-16T17:54:56Z | 2023-06-19T10:54:48Z | https://github.com/strukturag/libheif/issues/767 | 1,535,303,310 | 767 |
[
"strukturag",
"libheif"
]
| Since a few weeks, I'm not able to open heif/heic files at Fedora 37. I think it was caused by an update pushed around Christmas. I saw some reports about this issue but as far as I can see nobody report this bug here.
I see this information when I try to open the heic file via Gnome image viewer.
| Fedora 37 - error when trying to open heic file | https://api.github.com/repos/strukturag/libheif/issues/765/comments | 11 | 2023-01-15T16:13:18Z | 2023-02-18T11:42:27Z | https://github.com/strukturag/libheif/issues/765 | 1,533,888,710 | 765 |
[
"strukturag",
"libheif"
]
| Problem
While loading .heif images works, the texture2D loaded loses a bunch of saturation.
Replicate
To replicate this issue just load an image taken on an iPhone (IOS 11+) camera a load it to unity.
Is there any progress being done to fix this issue? | Loading HEIF images lose saturation | https://api.github.com/repos/strukturag/libheif/issues/761/comments | 0 | 2023-01-11T18:54:24Z | 2023-01-11T18:54:38Z | https://github.com/strukturag/libheif/issues/761 | 1,529,522,430 | 761 |
[
"strukturag",
"libheif"
]
| The `libheif.pc` has fields like `builtin_h265_decoder=yes` even if the libde265 plugin was built as plugin, i.e. is not builtin.
Are these `builtin_*` fields really used given that there are more possible decoders / encoders than what is currently checked? | libheif.pc shows builtin encoders/decoders even if built as plugins | https://api.github.com/repos/strukturag/libheif/issues/758/comments | 11 | 2023-01-10T15:24:05Z | 2023-12-18T20:57:17Z | https://github.com/strukturag/libheif/issues/758 | 1,527,584,245 | 758 |
[
"strukturag",
"libheif"
]
| Currently `ignore_transformations` is an all-in vs all-out switch, there is no way for apps to actually detect and perform transformations by themselves on the original image after decoding.
One would want e.g. to skip the crop, but still handle orientation, do their own memory/parallelization management etc.
| Expose image transformation parameters | https://api.github.com/repos/strukturag/libheif/issues/757/comments | 1 | 2023-01-10T12:59:51Z | 2023-01-10T13:04:43Z | https://github.com/strukturag/libheif/issues/757 | 1,527,347,811 | 757 |
[
"strukturag",
"libheif"
]
| I used ImageMagick, which used your libheif library 1.14.0 and have a problem with big picture files (width >3000 pixels and height >2000 pixels). If I save a jpeg file to heic file format and it has an odd size for width or height, I will get black vertical lines within my saved heic picture at the bottom and on the right side. If I save smaller pictures.
If one side of the picture has an even size, I will not get any black lines.
Here is an example file:
[Amsterdam_Damrak3.zip](https://github.com/strukturag/libheif/files/10376595/Amsterdam_Damrak3.zip)
Here is another sample picture, which can better show the problem.
The original picture is totally white and get black lines.
[Black lines2.zip](https://github.com/strukturag/libheif/files/10382287/Black.lines2.zip)
Here you can see the result (saved as jpeg):
| libheif 1.14.0 - Saved pictures have black vertical lines at the bottom and on the right side (picture size bigger than 3000x2000 pixels) | https://api.github.com/repos/strukturag/libheif/issues/756/comments | 1 | 2023-01-09T20:27:25Z | 2023-01-26T16:31:01Z | https://github.com/strukturag/libheif/issues/756 | 1,526,275,390 | 756 |
[
"strukturag",
"libheif"
]
| Hey,
This is a headsup that the LibFindMacros approach as currently used is unable to detect static libraries on MinGW.
For instance, I built by mistake libaom statically with MSYS2 CLANG64, and when trying to link to it, I got this error:
```
proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" --build e:/krita-win/patches/libheif/build --config RelWithDebInfo --target all --
[build] [1/6 16% :: 0.337] Linking CXX shared library libheif\libheif.dll
[build] FAILED: libheif/libheif.dll libheif/libheif.dll.a
[build] cmd.exe /C "cd . && D:\msys64\clang64\bin\clang++.exe -O2 -g -DNDEBUG -shared -o libheif\libheif.dll -Wl,--out-implib,libheif\libheif.dll.a -Wl,--major-image-version,1,--minor-image-version,14 libheif/CMakeFiles/heif.dir/bitstream.cc.obj libheif/CMakeFiles/heif.dir/box.cc.obj libheif/CMakeFiles/heif.dir/error.cc.obj libheif/CMakeFiles/heif.dir/heif.cc.obj libheif/CMakeFiles/heif.dir/heif_context.cc.obj libheif/CMakeFiles/heif.dir/heif_file.cc.obj libheif/CMakeFiles/heif.dir/heif_image.cc.obj libheif/CMakeFiles/heif.dir/heif_hevc.cc.obj libheif/CMakeFiles/heif.dir/heif_avif.cc.obj libheif/CMakeFiles/heif.dir/heif_colorconversion.cc.obj libheif/CMakeFiles/heif.dir/heif_plugin_registry.cc.obj libheif/CMakeFiles/heif.dir/heif_plugin.cc.obj libheif/CMakeFiles/heif.dir/nclx.cc.obj libheif/CMakeFiles/heif.dir/heif_init.cc.obj libheif/CMakeFiles/heif.dir/metadata_compression.cc.obj libheif/CMakeFiles/heif.dir/plugins/heif_encoder_x265.cc.obj libheif/CMakeFiles/heif.dir/plugins/heif_decoder_libde265.cc.obj libheif/CMakeFiles/heif.dir/plugins/heif_decoder_aom.cc.obj libheif/CMakeFiles/heif.dir/plugins/heif_encoder_aom.cc.obj E:/krita-win/clang64/i_deps/lib/libx265.dll.a E:/krita-win/clang64/i_deps/lib/liblibde265.dll.a E:/krita-win/clang64/i_deps/lib/libaom.a E:/krita-win/clang64/i_deps/lib/libaom.a -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cd ."
[build] ld.lld: error: undefined symbol: pthread_mutex_destroy
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/av1_dx_iface.c:130
[build] >>> libaom.a(av1_dx_iface.c.obj):(decoder_destroy)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/av1_cx_iface.c:2616
[build] >>> libaom.a(av1_cx_iface.c.obj):(av1_destroy_context_and_bufferpool)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/av1_cx_iface.c:2616
[build] >>> libaom.a(av1_cx_iface.c.obj):(encoder_destroy)
[build] >>> referenced 29 more times
[build]
[build] ld.lld: error: undefined symbol: pthread_mutex_lock
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/common/av1_common_int.h:1070
[build] >>> libaom.a(av1_dx_iface.c.obj):(release_pending_output_frames)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:91
[build] >>> libaom.a(aom_thread.c.obj):(reset)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:139
[build] >>> libaom.a(aom_thread.c.obj):(reset)
[build] >>> referenced 59 more times
[build]
[build] ld.lld: error: undefined symbol: pthread_mutex_unlock
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/common/av1_common_int.h:1078
[build] >>> libaom.a(av1_dx_iface.c.obj):(release_pending_output_frames)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:103
[build] >>> libaom.a(aom_thread.c.obj):(reset)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:142
[build] >>> libaom.a(aom_thread.c.obj):(reset)
[build] >>> referenced 74 more times
[build]
[build] ld.lld: error: undefined symbol: pthread_mutex_init
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/av1_dx_iface.c:431
[build] >>> libaom.a(av1_dx_iface.c.obj):(init_decoder)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/av1_cx_iface.c:2468
[build] >>> libaom.a(av1_cx_iface.c.obj):(av1_create_context_and_bufferpool)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/av1_cx_iface.c:2468
[build] >>> libaom.a(av1_cx_iface.c.obj):(encoder_init)
[build] >>> referenced 19 more times
[build]
[build] ld.lld: error: undefined symbol: pthread_cond_init
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:135
[build] >>> libaom.a(aom_thread.c.obj):(reset)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/common/alloccommon.c:176
[build] >>> libaom.a(alloccommon.c.obj):(av1_alloc_cdef_buffers)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/common/thread_common.c:77
[build] >>> libaom.a(thread_common.c.obj):(av1_loop_filter_alloc)
[build] >>> referenced 5 more times
[build]
[build] ld.lld: error: undefined symbol: pthread_cond_wait
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:95
[build] >>> libaom.a(aom_thread.c.obj):(reset)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:95
[build] >>> libaom.a(aom_thread.c.obj):(sync)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:95
[build] >>> libaom.a(aom_thread.c.obj):(launch)
[build] >>> referenced 10 more times
[build]
[build] ld.lld: error: undefined symbol: pthread_create
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:140
[build] >>> libaom.a(aom_thread.c.obj):(reset)
[build]
[build] ld.lld: error: undefined symbol: pthread_cond_destroy
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:145
[build] >>> libaom.a(aom_thread.c.obj):(reset)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:181
[build] >>> libaom.a(aom_thread.c.obj):(end)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/common/alloccommon.c:100
[build] >>> libaom.a(alloccommon.c.obj):(av1_free_cdef_buffers)
[build] >>> referenced 11 more times
[build]
[build] ld.lld: error: undefined symbol: pthread_cond_signal
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:100
[build] >>> libaom.a(aom_thread.c.obj):(launch)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:100
[build] >>> libaom.a(aom_thread.c.obj):(end)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:78
[build] >>> libaom.a(aom_thread.c.obj):(thread_loop)
[build] >>> referenced 7 more times
[build]
[build] ld.lld: error: undefined symbol: pthread_join
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/aom_util/aom_thread.c:179
[build] >>> libaom.a(aom_thread.c.obj):(end)
[build]
[build] ld.lld: error: undefined symbol: pthread_cond_broadcast
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/common/thread_common.c:252
[proc] The command: "C:\Program Files\CMake\bin\cmake.EXE" --build e:/krita-win/patches/libheif/build --config RelWithDebInfo --target all -- exited with code: 1 and signal: null
[build] >>> libaom.a(thread_common.c.obj):(thread_loop_filter_rows)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/common/thread_common.c:577
[build] >>> libaom.a(thread_common.c.obj):(lr_sync_write)
[build] >>> referenced by E:/krita-win/clang64/b_deps/ext_heif/ext_libaom-prefix/src/ext_libaom/av1/decoder/decodeframe.c:0
[build] >>> libaom.a(decodeframe.c.obj):(row_mt_worker_hook)
[build] >>> referenced 1 more times
[build] clang++: error: linker command failed with exit code 1 (use -v to see invocation)
[build] ninja: build stopped: subcommand failed.
``` | The Find Modules do not support static libraries on Windows | https://api.github.com/repos/strukturag/libheif/issues/755/comments | 0 | 2023-01-07T00:39:17Z | 2023-01-07T00:39:17Z | https://github.com/strukturag/libheif/issues/755 | 1,523,355,690 | 755 |
[
"strukturag",
"libheif"
]
| I might be mistaken but there might be a spelling error with "set_color_primaties", should it be "set_color_primaries"?
I bring this up after filing a bug report with the krita folks because it failed the compile with;
`[ 78%] Built target kritaheifimport
[ 78%] Automatic MOC for target kritaheifexport
[ 78%] Built target kritaheifexport_autogen
Consolidate compiler generated dependencies of target kritaheifexport
[ 78%] Building CXX object plugins/impex/heif/CMakeFiles/kritaheifexport.dir/HeifExport.cpp.o
/usr/src/krita-5.1.5/plugins/impex/heif/HeifExport.cpp: In member function 'virtual KisImportExportErrorCode HeifExport::convert(KisDocument*, QIODevice*, KisPropertiesConfigurationSP)'
/usr/src/krita-5.1.5/plugins/impex/heif/HeifExport.cpp:477:32: error: 'class heif::ColorProfile_nclx' has no member named 'set_color_primaties'; did you mean 'set_color_primaries'?
477 | nclxDescription.set_color_primaties(heif_color_primaries_ITU_R_BT_2020_2_and_2100_0);
| ^~~~~~~~~~~~~~~~~~~
| set_color_primaries
/usr/src/krita-5.1.5/plugins/impex/heif/HeifExport.cpp:487:32: error: 'class heif::ColorProfile_nclx' has no member named 'set_color_primaties'; did you mean 'set_color_primaries'?
487 | nclxDescription.set_color_primaties(heif_color_primaries(primaries));
| ^~~~~~~~~~~~~~~~~~~
| set_color_primaries
make[2]: *** [plugins/impex/heif/CMakeFiles/kritaheifexport.dir/build.make:113: plugins/impex/heif/CMakeFiles/kritaheifexport.dir/HeifExport.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:37975: plugins/impex/heif/CMakeFiles/kritaheifexport.dir/all] Error 2
make: *** [Makefile:146: all] Error 2
`
And the krita folks seems to think spelling is the issue. | Spelling error with set_color_primaties? | https://api.github.com/repos/strukturag/libheif/issues/753/comments | 2 | 2023-01-05T18:15:33Z | 2023-01-06T15:41:51Z | https://github.com/strukturag/libheif/issues/753 | 1,521,174,021 | 753 |
[
"strukturag",
"libheif"
]
| Hi, since heif-enc 1.14.0, the output produced by heif-enc for PNG input are broken files.
Example png and output:
[png.zip](https://github.com/strukturag/libheif/files/10330857/png.zip)
`heif-enc -q 60 -v test.png`
I've tried different PNG files produced by different apps (which had worked with previous versions of libheif) as well as different ways to view the HEIC files produced but none of them works.
Any ideas? Thank you | heif-enc 1.14.0 cannot use PNG as input | https://api.github.com/repos/strukturag/libheif/issues/751/comments | 9 | 2023-01-02T09:49:32Z | 2023-01-02T23:46:33Z | https://github.com/strukturag/libheif/issues/751 | 1,516,207,911 | 751 |
[
"strukturag",
"libheif"
]
| The following new warning is emitted:
```
[ 34s] cd /home/abuild/rpmbuild/BUILD/libheif-1.12.0/build/libheif && /usr/bin/c++ -DHAVE_AOM_DECODER=1 -DHAVE_AOM_ENCODER=1 -DHAVE_DAV1D=1 -DHAVE_RAV1E=1 -DHAVE_UNISTD_H -DHAVE_VISIBILITY -DLIBHEIF_EXPORTS -Dheif_EXPORTS -I/home/abuild/rpmbuild/BUILD/libheif-1.12.0/build -I/home/abuild/rpmbuild/BUILD/libheif-1.12.0 -I/home/abuild/rpmbuild/BUILD/libheif-1.12.0/include/libheif -I/home/abuild/rpmbuild/BUILD/libheif-1.12.0/include -isystem /usr/include/rav1e -fomit-frame-pointer -O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -O2 -g -DNDEBUG -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-error=unused-parameter -Wno-error=deprecated-declarations -std=c++11 -MD -MT libheif/CMakeFiles/heif.dir/heif_colorconversion.cc.o -MF CMakeFiles/heif.dir/heif_colorconversion.cc.o.d -o CMakeFiles/heif.dir/heif_colorconversion.cc.o -c /home/abuild/rpmbuild/BUILD/libheif-1.12.0/libheif/heif_colorconversion.cc
[ 34s] /home/abuild/rpmbuild/BUILD/libheif-1.12.0/libheif/heif_colorconversion.cc: In member function 'virtual std::shared_ptr<heif::HeifPixelImage> Op_YCbCr420_to_RGB24::convert_colorspace(const std::shared_ptr<const heif::HeifPixelImage>&, heif::ColorState, heif::ColorConversionOptions)':
[ 34s] /home/abuild/rpmbuild/BUILD/libheif-1.12.0/libheif/heif_colorconversion.cc:835:42: error: conversion from 'long double' to 'double' may change value [-Werror=float-conversion]
[ 34s] 835 | int r_cr = static_cast<int>(lround(256 * coeffs.r_cr));
[ 34s] | ~~~~^~~~~~~~~~~~~
[ 34s] /home/abuild/rpmbuild/BUILD/libheif-1.12.0/libheif/heif_colorconversion.cc:836:42: error: conversion from 'long double' to 'double' may change value [-Werror=float-conversion]
[ 34s] 836 | int g_cr = static_cast<int>(lround(256 * coeffs.g_cr));
[ 34s] | ~~~~^~~~~~~~~~~~~
[ 34s] /home/abuild/rpmbuild/BUILD/libheif-1.12.0/libheif/heif_colorconversion.cc:837:42: error: conversion from 'long double' to 'double' may change value [-Werror=float-conversion]
[ 34s] 837 | int g_cb = static_cast<int>(lround(256 * coeffs.g_cb));
[ 34s] | ~~~~^~~~~~~~~~~~~
...
``` | A new warning with latest GCC 13 and -m32 | https://api.github.com/repos/strukturag/libheif/issues/748/comments | 8 | 2022-12-27T11:53:15Z | 2023-01-17T13:16:20Z | https://github.com/strukturag/libheif/issues/748 | 1,511,730,355 | 748 |
[
"strukturag",
"libheif"
]
| Hi,
I am using a heic:speed parameter in ImageMagick, and it is passed directly to libheif library. But I am unable to get if 0 means placebo or ultrafast. Where I can see some description for it? | speed setting | https://api.github.com/repos/strukturag/libheif/issues/747/comments | 1 | 2022-12-27T08:22:36Z | 2023-01-13T07:40:15Z | https://github.com/strukturag/libheif/issues/747 | 1,511,559,669 | 747 |
[
"strukturag",
"libheif"
]
| Hi @farindk
I can't understand the role of the quality term in the compression. Where can I see what quality number ( 0 to 100) represents?
I read that this library uses x265 to encode an image into HEIF/HEVC, but using different quality what are the parts of the encoder that will change ( the compression matrix, the CTU/CU sizes or other) ?
I will really appreciate your answer | Question About quality term | https://api.github.com/repos/strukturag/libheif/issues/746/comments | 0 | 2022-12-22T13:47:35Z | 2022-12-22T13:47:35Z | https://github.com/strukturag/libheif/issues/746 | 1,507,919,836 | 746 |
[
"strukturag",
"libheif"
]
| hi, colleagues:
As the attached picture shows, I met error when run simple command line as "./heif-enc -A -e rav1e -q 45 ./lake-3000.jpg -o dst2.avif".
The error info are "symbol lookup error: ..../libheif-rav1e.so: undefined symbol: _ZNK4heif14HeifPixelImage18get_bits_per_pixelE12heif_channel".
I also checked it with objdump and does see the symbol in libheif.so instead of in the plugin.
Anything I should notice or improve during the library build or example run? Thanks a lot.
<img width="656" alt="symbol lookup error" src="https://user-images.githubusercontent.com/80802212/208628216-bf831d52-18ec-43f3-a644-2ab7c96a2548.png">
| symbol lookup error in codec plugin | https://api.github.com/repos/strukturag/libheif/issues/745/comments | 15 | 2022-12-20T09:13:45Z | 2023-01-21T13:30:53Z | https://github.com/strukturag/libheif/issues/745 | 1,504,227,872 | 745 |
[
"strukturag",
"libheif"
]
| Hi,
I am running the GNOME Image Viewer app on Arch, and I am unable to view HEIC images in it starting from https://github.com/flathub/org.gnome.eog/commit/16c633d413d71c6e23368a0aed61ede4ed10a340, which switched to version 1.14.0 of libheif. Downgrading fixes this, but is obviously not a solution.
Error log:
```
** (eog:2): WARNING **: 11:49:01.937: Cannot read plugin directory.
(eog:2): GdkPixbuf-CRITICAL **: 11:49:01.938: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed
(eog:2): GdkPixbuf-CRITICAL **: 11:49:01.938: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed
(eog:2): GdkPixbuf-CRITICAL **: 11:49:01.938: gdk_pixbuf_animation_iter_get_pixb
```
Ref: https://github.com/flathub/org.gnome.eog/issues/73 | Unable to load HEIC file since 1.14.0 | https://api.github.com/repos/strukturag/libheif/issues/742/comments | 3 | 2022-12-19T05:49:54Z | 2022-12-20T13:54:32Z | https://github.com/strukturag/libheif/issues/742 | 1,502,349,010 | 742 |
[
"strukturag",
"libheif"
]
| I used the command ` heif-convert -q 100 ` to convert a HEIC image to jpg format.
However, the final image is mostly grey:
Unfortunately, I have deleted the HEIC image for space issues.. is there a way to recover the original image?
Thank you! | Image damaged grey bar | https://api.github.com/repos/strukturag/libheif/issues/741/comments | 1 | 2022-12-12T11:33:03Z | 2023-02-16T12:20:31Z | https://github.com/strukturag/libheif/issues/741 | 1,491,648,948 | 741 |
[
"strukturag",
"libheif"
]
| The function ``HeifContext::decode_and_paste_tile_image`` has a potential race condition when run in parallel from here:
https://github.com/strukturag/libheif/blob/e886cb55a2296f527a9364549d66de5b559e0c0d/libheif/heif_context.cc#L1615-L1617
The problem code is this:
https://github.com/strukturag/libheif/blob/e886cb55a2296f527a9364549d66de5b559e0c0d/libheif/heif_context.cc#L1668-L1675
Which could end up with multiple threads each trying to add an alpha channel to the same image at the same time.
Also the calls to ``HeifPixelImage::has_alpha`` return true for interleaved RGBA type images, which I believe is not the desired requirement.
These can be fixed with something like:
```C++
if (tile_img->has_channel(heif_channel_Alpha) && !img->has_channel(heif_channel_Alpha)) {
#if ENABLE_PARALLEL_TILE_DECODING
static std::mutex m;
std::lock_guard<std::mutex> lock(m);
if (!img->has_channel(heif_channel_Alpha)) // check again, after locking
#endif
{
int alpha_bpp = tile_img->get_bits_per_pixel(heif_channel_Alpha);
assert(alpha_bpp <= 16);
uint16_t alpha_default_value = static_cast<uint16_t>((1u << alpha_bpp) - 1u);
img->fill_new_plane(heif_channel_Alpha, alpha_default_value, w, h, alpha_bpp);
}
}
```
[Also I changed the ``1UL``s to ``1u``, as it doesn’t need to be 64-bit.]
[BTW ``HeifPixelImage::fill_new_plane`` should probably assert (or correctly handle) when called with an interleaved channel.]
| Race condition in HeifContext::decode_and_paste_tile_image | https://api.github.com/repos/strukturag/libheif/issues/740/comments | 1 | 2022-12-12T03:06:31Z | 2022-12-20T14:24:44Z | https://github.com/strukturag/libheif/issues/740 | 1,490,815,472 | 740 |
[
"strukturag",
"libheif"
]
| In the function ``HeifContext::decode_and_paste_tile_image`` there is:
https://github.com/strukturag/libheif/blob/e5ab2ede435e7cc13b7db9dfd66f9d12f7fa48ed/libheif/heif_context.cc#L1669
I think the ``255`` should be ``0xFFFF`` or ``~0u`` or ``(1u << tile_img->get_bits_per_pixel(heif_channel_Alpha)) - 1`` for compatibility with 10 & 12-bit alpha channels (in addition to 8-bit). | Wrong alpha default in HeifContext::decode_and_paste_tile_image | https://api.github.com/repos/strukturag/libheif/issues/739/comments | 1 | 2022-12-09T09:59:57Z | 2022-12-09T10:06:19Z | https://github.com/strukturag/libheif/issues/739 | 1,486,458,908 | 739 |
[
"strukturag",
"libheif"
]
| The referenced line makes an unnecessary copy of ``HeifPixelImage::m_warnings`` (potentially multiple times).
https://github.com/strukturag/libheif/blob/e5ab2ede435e7cc13b7db9dfd66f9d12f7fa48ed/libheif/heif_colorconversion.cc#L3277
The above line & the line that follows it can be simplified/optimised to:
```
for (const auto& warning : in->get_warnings()) {
```
BTW Is it possible to create a permalink for multiple lines of code? | Unnecessary copying of std::vector<Error> | https://api.github.com/repos/strukturag/libheif/issues/738/comments | 3 | 2022-12-09T07:28:13Z | 2022-12-09T14:52:54Z | https://github.com/strukturag/libheif/issues/738 | 1,486,218,279 | 738 |
[
"strukturag",
"libheif"
]
| Cheers, sorry for bothering.
Briefly why this is important (_to me_):
Cmake build was bugged for `1.14.0` (has disabled multithreading by default), and current version from repo is OK.
**MSYS2** uses cmake build, and I use binaries from **MSYS** ... | Can we get release for `1.14.1`? | https://api.github.com/repos/strukturag/libheif/issues/736/comments | 0 | 2022-12-06T11:32:18Z | 2022-12-17T09:59:43Z | https://github.com/strukturag/libheif/issues/736 | 1,478,881,458 | 736 |
[
"strukturag",
"libheif"
]
| I was reading the code when I spotted what looks like a typo.
<https://github.com/AOMediaCodec/libavif/blob/429b005c95d7dd45298d12a99e0781de1bbeb37f/src/avif.c#L858>
says the spec says “the tile_width shall be greater than or equal to 64, and should be a multiple of 64”
& “the tile_height shall be greater than or equal to 64, and should be a multiple of 64”.
This makes sense. So image is NOT MIAF compatible if (width % 64 OR height % 64).
However:
https://github.com/strukturag/libheif/blob/012d77c8340ef8b6e190aea5ac4ff9262d992f0c/libheif/heif_context.cc#L2161
Should probably be ``||`` NOT ``&&``. | MIAF compatibility flag incorrectly set | https://api.github.com/repos/strukturag/libheif/issues/735/comments | 1 | 2022-12-05T10:16:26Z | 2022-12-06T12:05:36Z | https://github.com/strukturag/libheif/issues/735 | 1,476,199,298 | 735 |
[
"strukturag",
"libheif"
]
| dlopen --> LoadLibrary
dlclose --> FreeLibrary
dlsym --> GetProcAddress
see
https://learn.microsoft.com/en-us/windows/win32/api/libloaderapi/nf-libloaderapi-loadlibrarya
and
https://learn.microsoft.com/en-us/windows/win32/api/libloaderapi/nf-libloaderapi-getprocaddress
it should be easy to write a class to embed this for linux and Windows
| plugin on Windows | https://api.github.com/repos/strukturag/libheif/issues/731/comments | 8 | 2022-11-26T09:50:02Z | 2023-02-16T14:42:13Z | https://github.com/strukturag/libheif/issues/731 | 1,465,104,314 | 731 |
[
"strukturag",
"libheif"
]
| First I use command:
_mkdir build
cd build
cmake .. -D LIBDE265_INCLUDE_DIR=../../libde265/build -D LIBDE265_LIBRARY=../../libde265
make_
To compile it and error log is :
```
/mnt/d/Code/libheif/libheif/plugins/heif_decoder_libde265.cc:35:10: fatal error: libde265/de265.h: No such file or directory
35 | #include <libde265/de265.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [libheif/CMakeFiles/heif.dir/build.make:277: libheif/CMakeFiles/heif.dir/plugins/heif_decoder_libde265.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:310: libheif/CMakeFiles/heif.dir/all] Error 2
```
so I change cmake command like:
_cmake .. -D LIBDE265_INCLUDE_DIR=../../libde265 -D LIBDE265_LIBRARY=../../libde265/build_
And error log is :
```
_In file included from /mnt/d/Code/libheif/libheif/plugins/heif_decoder_libde265.cc:35:
/mnt/d/Code/libde265/libde265/de265.h:29:10: fatal error: libde265/de265-version.h: No such file or directory
29 | #include <libde265/de265-version.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [libheif/CMakeFiles/heif.dir/build.make:277: libheif/CMakeFiles/heif.dir/plugins/heif_decoder_libde265.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:310: libheif/CMakeFiles/heif.dir/all] Error 2
make: *** [Makefile:171: all] Error 2_
```
And it seems **de265.h** and **de265-version.h** are in different directory. So I don't know how to config LIBDE265_INCLUDE_DIR and LIBDE265_LIBRARY correctly. Did anyone know it? I would appreciate it if someone could tell me. Thanks. | How to compile it with libde265 build in | https://api.github.com/repos/strukturag/libheif/issues/730/comments | 6 | 2022-11-25T14:42:19Z | 2022-11-27T20:18:05Z | https://github.com/strukturag/libheif/issues/730 | 1,464,640,287 | 730 |
[
"strukturag",
"libheif"
]
| We tried to get encoding with SVT-AV1 working and noticed that the quality parameter (range: 1-100) isn't exposed yet:
```
$ heif-enc -A -e aom -q 1 -o aom_1.avif test.jpg
$ heif-enc -A -e aom -q 100 -o aom_100.avif test.jpg
$ heif-enc -A -e svt -q 1 -o svt_1.avif test.jpg
$ heif-enc -A -e svt -q 100 -o svt_100.avif test.jpg
$ du -h svt_* aom_*
104K svt_1.avif
104K svt_100.avif
16K aom_1.avif
3.1M aom_100.avif
```
As you can see, an AVIF encoded with SVT-AV1 with quality 1 is of the exact same file size as one with quality 100.
Is there anything we could help with to get a 1-100 quality mapping with SVT-AV1?
https://github.com/strukturag/libheif/blob/f43a3a1fba99e603aeabb38dc631493c69432a18/libheif/plugins/heif_encoder_svt.cc#L44 | SVT-AV1: Quality parameter (1-100) mapping | https://api.github.com/repos/strukturag/libheif/issues/729/comments | 3 | 2022-11-23T17:57:38Z | 2022-11-25T16:03:38Z | https://github.com/strukturag/libheif/issues/729 | 1,462,179,411 | 729 |
[
"strukturag",
"libheif"
]
| Now that the cmake build system is the new default and supports more features, we should get rid of the deprecated autoconf / automake build files.
@farindk what do you think? | Remove autoconf / automake files | https://api.github.com/repos/strukturag/libheif/issues/726/comments | 8 | 2022-11-23T10:46:38Z | 2023-05-31T09:53:41Z | https://github.com/strukturag/libheif/issues/726 | 1,461,506,146 | 726 |
[
"strukturag",
"libheif"
]
| 
[test.jpg](https://user-images.githubusercontent.com/34104349/203371976-246bcb34-4062-41fc-bab2-a7ad1c836276.jpg)
```
$ heif-enc -A -e svt test.jpg
Svt[info]: -------------------------------------------
Svt[info]: SVT [version]: SVT-AV1 Encoder Lib v1.3.0-36-g4794f938
Svt[info]: SVT [build] : Apple LLVM 14.0.0 (clang-1400.0.29.202) 64 bit
Svt[info]: LIB Build date: Nov 22 2022 11:17:58
Svt[info]: -------------------------------------------
Svt[error]: Instance 1: Source Width must be at least 64
Svt[error]: Instance 1: Source Height must be at least 64
Svt[error]: Instance 1: Forced Max Width must be at least 64
Svt[error]: Instance 1: Forced Max Height must be at least 64
Svt[warn]: If you are using tiles with the intent of increasing the decoder speed, please also consider using --fast-decode 1, especially if the intended decoder is running with limited multi-threading capabilities.
$ heif-info test.avif
MIME type: image/avif
main brand: avif
compatible brands: avif, mif1, miaf
Could not read HEIF/AVIF file: Invalid input: Item has no data: Item with ID 1 has no compressed data
```
**With `aom` it works just fine:**
```
$ heif-enc -A -e aom test.jpg
$ heif-info test.avif
MIME type: image/avif
main brand: avif
compatible brands: avif, mif1, miaf
image: 60x40 (id=1), primary
color profile: prof
alpha channel: no
depth channel: no
metadata:
Exif: 184 bytes
```
Not sure if it's something that can be improved in libheif or something related to SVT-AV1.
**Version:** latest master (da9eea36d3815ec064cafe47bf9a0ac59809fd8b) | SVT-AV1: encoding small images fails | https://api.github.com/repos/strukturag/libheif/issues/724/comments | 1 | 2022-11-22T16:48:15Z | 2022-11-22T17:03:26Z | https://github.com/strukturag/libheif/issues/724 | 1,460,222,792 | 724 |
[
"strukturag",
"libheif"
]
| This metadata is important for correctly rendering many AVIF HDR images that use a PQ transfer curve.
The Content Light Level Information box is described in MIAF section 7.4.4.2 and AVIF section 2.2.3.
Related to https://github.com/AOMediaCodec/libavif/pull/1194
| Add read/write support for the Content Light Level Information box | https://api.github.com/repos/strukturag/libheif/issues/721/comments | 3 | 2022-11-18T20:30:00Z | 2023-02-16T12:21:04Z | https://github.com/strukturag/libheif/issues/721 | 1,455,757,179 | 721 |
[
"strukturag",
"libheif"
]
| /opt/libheif/libheif/plugins/heif_encoder_aom.cc: In function ‘heif_error aom_encode_image(void*, const heif_image*, heif_image_input_class)’:
/opt/libheif/libheif/plugins/heif_encoder_aom.cc:846:27: error: ‘AOM_USAGE_GOOD_QUALITY’ was not declared in this scope
846 | unsigned int aomUsage = AOM_USAGE_GOOD_QUALITY;
| ^~~~~~~~~~~~~~~~~~~~~~
/opt/libheif/libheif/plugins/heif_encoder_aom.cc:849:16: error: ‘AOM_USAGE_REALTIME’ was not declared in this scope
849 | aomUsage = AOM_USAGE_REALTIME;
| ^~~~~~~~~~~~~~~~~~
make[2]: *** [libheif/CMakeFiles/heif.dir/build.make:284: libheif/CMakeFiles/heif.dir/plugins/heif_encoder_aom.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:320: libheif/CMakeFiles/heif.dir/all] Error 2
make: *** [Makefile:152: all] Error
it happened when i make code, does anyone know what this is about？ | Error in Cmake | https://api.github.com/repos/strukturag/libheif/issues/720/comments | 2 | 2022-11-18T08:49:01Z | 2023-04-14T18:11:58Z | https://github.com/strukturag/libheif/issues/720 | 1,454,719,197 | 720 |
[
"strukturag",
"libheif"
]
| [As Autotools is intended to be removed, the CMake generated .pc file needs to be improved for relocatibility](https://github.com/msys2/MINGW-packages/blob/043607c29b4f26550c7cd04ee3be61f340748f13/mingw-w64-libheif/PKGBUILD#L64) - namely, it should use [`${prefix}` etc. variables when possible](https://people.freedesktop.org/~dbn/pkg-config-guide.html), but still support absolute paths when required.
See e.g. [libjxl](https://github.com/libjxl/libjxl/blob/3f6ec60ce6890132c1e2ea9719de5981042a1d96/lib/jxl.cmake#L642-L663) and [libtiff](https://gitlab.com/libtiff/libtiff/-/blob/31d9e9f73dc8b6fa599c931d9ff058d8ea32795c/cmake/PkgConfig.cmake#L48-63)
Also, there is no need to substitute
```
Libs: -L@libdir@ -lheif
Cflags: -I@includedir@
```
as, being defined correctly at the start, they can be left as
```
Libs: -L${libdir} -lheif
Cflags: -I${includedir}
```
| Improve pkg-config file generation | https://api.github.com/repos/strukturag/libheif/issues/717/comments | 0 | 2022-11-16T12:37:06Z | 2022-11-21T11:29:31Z | https://github.com/strukturag/libheif/issues/717 | 1,451,526,879 | 717 |
[
"strukturag",
"libheif"
]
| successfully compiled libde but compiling libheif got an error:
ological-compare -o .libs/heif-info heif_info-heif_info.o ../libheif/.libs/libheif.so -lpthread
/usr/bin/ld: ../libheif/.libs/libheif.so: undefined reference to `de265_get_image_full_range_flag'
/usr/bin/ld: ../libheif/.libs/libheif.so: undefined reference to `de265_get_image_transfer_characteristics'
/usr/bin/ld: ../libheif/.libs/libheif.so: undefined reference to `de265_get_image_colour_primaries'
/usr/bin/ld: ../libheif/.libs/libheif.so: undefined reference to `de265_get_image_matrix_coefficients'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:668: heif-info] Error 1
make[2]: *** Waiting for unfinished jobs....
| Error in make | https://api.github.com/repos/strukturag/libheif/issues/716/comments | 6 | 2022-11-16T10:45:07Z | 2022-11-17T07:16:03Z | https://github.com/strukturag/libheif/issues/716 | 1,451,345,202 | 716 |
[
"strukturag",
"libheif"
]
| without this patch compiling fails with `configure --disable-multithreading` on no threadsupporting platform
[heif_init_disable_multithreading.patch.zip](https://github.com/strukturag/libheif/files/10020678/heif_init_disable_multithreading.patch.zip)
| libheif-1.14.0 does not compile with --disable-multithreading | https://api.github.com/repos/strukturag/libheif/issues/715/comments | 3 | 2022-11-16T10:26:10Z | 2022-11-16T15:22:13Z | https://github.com/strukturag/libheif/issues/715 | 1,451,312,638 | 715 |
[
"strukturag",
"libheif"
]
| Up until 1.14.0, the build worked pretty much out of the box, but now it fails, see the log here: https://github.com/msys2/MINGW-packages/actions/runs/3473745090/jobs/5806121808#step:11:386
Major: missing symbols when linking the new `libheif-svtenc.dll`
```
Linking CXX shared module libheif\plugins\libheif-svtenc.dll
FAILED: libheif/plugins/libheif-svtenc.dll
cmd.exe /C "cd . && C:\msys64\ucrt64\bin\g++.exe -march=nocona -msahf -mtune=generic -O2 -pipe -DX26
5_API_IMPORTS -O3 -DNDEBUG -pipe -shared -o libheif\plugins\libheif-svtenc.dll -Wl,--major-im
age-version,1,--minor-image-version,14 libheif/plugins/CMakeFiles/heif-svtenc.dir/heif_encoder_svt.c
c.obj libheif/plugins/CMakeFiles/heif-svtenc.dir/__/heif_plugin.cc.obj C:/msys64/ucrt64/lib/libSvtA
v1Enc.dll.a -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -
ladvapi32 && cd ."
C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
libheif/plugins/CMakeFiles/heif-svtenc.dir/heif_encoder_svt.cc.obj:heif_encoder_svt.cc:(.text+0xb5a
): undefined reference to `heif_image_get_width'
```
... and many more
Minor: unused variable (`-Werror=unused-variable` is default on MSYS2)
```
Building CXX object libheif/plugins/CMakeFiles/heif-svtenc.dir/heif_encoder_svt.cc.obj
FAILED: libheif/plugins/CMakeFiles/heif-svtenc.dir/heif_encoder_svt.cc.obj
C:\msys64\ucrt64\bin\g++.exe -DHAVE_UNISTD_H -DHAVE_VISIBILITY -DLIBHEIF_EXPORTS -DPLUGIN_SvtEnc=1 -
Dheif_svtenc_EXPORTS -IC:/msys64/home/kmilos/MINGW-packages/mingw-w64-libheif/src/libheif-1.14.0 -
IC:/msys64/home/kmilos/MINGW-packages/mingw-w64-libheif/src/build-UCRT64 -march=nocona -msahf -mtu
ne=generic -O2 -pipe -DX265_API_IMPORTS -O3 -DNDEBUG -fvisibility=hidden -fno-keep-inline-dlle
xport -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-er
ror=unused-parameter -Wno-error=deprecated-declarations -std=c++11 -MD -MT libheif/plugins/CMakeFile
s/heif-svtenc.dir/heif_encoder_svt.cc.obj -MF libheif\plugins\CMakeFiles\heif-svtenc.dir\heif_encode
r_svt.cc.obj.d -o libheif/plugins/CMakeFiles/heif-svtenc.dir/heif_encoder_svt.cc.obj -c C:/msys64/ho
me/kmilos/MINGW-packages/mingw-w64-libheif/src/libheif-1.14.0/libheif/plugins/heif_encoder_svt.cc
C:/msys64/home/kmilos/MINGW-packages/mingw-w64-libheif/src/libheif-1.14.0/libheif/plugins/heif_enc
oder_svt.cc: In function 'int int_log2(int)':
C:/msys64/home/kmilos/MINGW-packages/mingw-w64-libheif/src/libheif-1.14.0/libheif/plugins/heif_enc
oder_svt.cc:99:7: error: unused variable 'input_value' [-Werror=unused-variable]
99 | int input_value = pow2_value;
| ^~~~~~~~~~~
cc1plus.exe: all warnings being treated as errors
``` | libheif 1.14.0 fails to build for MinGW | https://api.github.com/repos/strukturag/libheif/issues/713/comments | 13 | 2022-11-16T10:07:18Z | 2022-11-16T11:41:25Z | https://github.com/strukturag/libheif/issues/713 | 1,451,282,710 | 713 |
[
"strukturag",
"libheif"
]
| Hi,
Building v1.14.0 on Windows (MSVC - vs17 cmake build) I have an issue with cmake option `-DWITH_DEFLATE_HEADER_COMPRESSION=ON`
> `LINK : fatal error LNK1181: cannot open input file 'zlib.lib'`
Having a quick look on `libheif/CMakeLists.txt` i think `find_library(z-lib z)` might not be standard for all platforms and here is my patch for a working build, according to standart cmake option with ZLIB
> ```
> -DWITH_DEFLATE_HEADER_COMPRESSION=ON ^
> -DZLIB_LIBRARY=%PATH_INSTALL%\lib\zlib.lib ^
> -DZLIB_INCLUDE_DIR=%PATH_INSTALL%\include ^
> ```
```
diff --git a/libheif/CMakeLists.txt b/libheif/CMakeLists.txt
index d47c908..d79bdf0 100644
--- a/libheif/CMakeLists.txt
+++ b/libheif/CMakeLists.txt
@@ -70,9 +70,11 @@ if (ENABLE_PLUGIN_LOADING AND UNIX)
endif()
if (WITH_DEFLATE_HEADER_COMPRESSION)
- find_library(z-lib z)
- target_link_libraries(heif PRIVATE ${z-lib})
- target_compile_definitions(heif PRIVATE WITH_DEFLATE_HEADER_COMPRESSION=1)
+find_package( ZLIB REQUIRED )
+ if ( ZLIB_FOUND )
+ target_link_libraries(heif PRIVATE ${ZLIB_LIBRARY})
+ target_compile_definitions(heif PRIVATE WITH_DEFLATE_HEADER_COMPRESSION=1)
+ endif ()
endif ()
write_basic_package_version_file(${PROJECT_NAME}-config-version.cmake COMPATIBILITY ExactVersion)
``` | Cmake issue with ZLIB | https://api.github.com/repos/strukturag/libheif/issues/712/comments | 4 | 2022-11-16T09:03:15Z | 2022-11-16T15:55:33Z | https://github.com/strukturag/libheif/issues/712 | 1,451,177,049 | 712 |
[
"strukturag",
"libheif"
]
| null | How do I use it in Java or have a demo of the Java language,thanks. | https://api.github.com/repos/strukturag/libheif/issues/711/comments | 1 | 2022-11-14T09:30:00Z | 2023-12-29T05:19:42Z | https://github.com/strukturag/libheif/issues/711 | 1,447,702,184 | 711 |
[
"strukturag",
"libheif"
]
| If image size is above 1MB I am getting `Memory allocation failed` error. Smaller images works fine.
I am on `Ubuntu 20.04.2 LTS`
libheif version is `1.6.1` installed with `sudo apt -y install libheif-dev` command.
Is it possible to install latest libheif in Ubuntu?
Can I increase max memory by editing `heif_suberror_Security_limit_exceeded` variable inside `/usr/include/libheif/heif.h` file?
Thanks. | Memory allocation failed | https://api.github.com/repos/strukturag/libheif/issues/710/comments | 20 | 2022-11-13T22:56:42Z | 2022-11-22T20:19:45Z | https://github.com/strukturag/libheif/issues/710 | 1,447,128,948 | 710 |
[
"strukturag",
"libheif"
]
| This is an image encoded with `avifenc --grid 1x2` (at https://github.com/AOMediaCodec/libavif/commit/cd03eef10a7cc6081ee98e3911e21d977a2bf17b using `ext/aom`):
(extension is .jpg but it is an actual AVIF file)
The pattern is the following:
```
[primary item grid]
^ ^ ^
|dimg |dimg |
| | |auxl
[color] [color] |
|
[alpha aux grid]
^ ^
|dimg |dimg
| |
[alpha] [alpha]
```
Here is the same image manually edited to match the following pattern:
```
[primary item grid]
^ ^
|dimg |dimg
| |
[color] [color]
^ ^
|auxl |auxl
| |
[alpha] [alpha]
```
I did not find anything in ISOBMFF, HEIF and MIAF specifications regarding the invalidity of this pattern. [Compliance Warden](https://gpac.github.io/ComplianceWarden-wasm/avif.html) does not report more errors than for the image generated only with `avifenc` (even fewer errors actually because there is one less grid to complain about `construction_method=-1 on a derived image item`).
`heif-convert` (at d3ec0df07ef1c6f01f0ce81885f76128f3f1fc52 using installed aom) leads to the wrongly opaque following PNG:
No error is reported by `heic-convert`.
There is the same issue with libavif: https://github.com/AOMediaCodec/libavif/issues/1203 | AVIF color grid without alpha grid looses alpha when decoded | https://api.github.com/repos/strukturag/libheif/issues/708/comments | 2 | 2022-11-10T13:49:53Z | 2022-11-10T15:25:39Z | https://github.com/strukturag/libheif/issues/708 | 1,443,944,305 | 708 |
[
"strukturag",
"libheif"
]
| When making libheif, the following error is encountered.
> "encoder_png.cc: member function ‘virtual bool PngEncoder::Encode(const heif_image_handle*, const heif_image*, const string&)’ :\nencoder_png.cc:124:7: error: ‘png_set_eXIf_1’ was not declared in this scope\n png_set_eXIf_1(png_ptr, info_ptr, (png_uint_32)size, ptr);\n ^~~~~~~~~~~~~~\nencoder_png.cc:124:7: remarks: suggested alternative: ‘png_set_sCAL_s’\n png_set_eXIf_1(png_ptr, info_ptr, (png_uint_32)size, ptr) | Error of making libheif | https://api.github.com/repos/strukturag/libheif/issues/707/comments | 2 | 2022-11-07T12:51:57Z | 2022-11-08T12:29:41Z | https://github.com/strukturag/libheif/issues/707 | 1,438,315,498 | 707 |
[
"strukturag",
"libheif"
]
| Hello, thank you again for this nice library.
Eight bit AVIFs images are fine, but I'm seeing a curious black offset when decoding 10 and 12 bit AVIF. For example with these test images:
https://github.com/link-u/avif-sample-images
I run:
```
$ heif-convert fox.profile2.12bpc.yuv422.avif heif-convert-12.png
```
`fox.png` in that directory is the correct result:
https://raw.githubusercontent.com/link-u/avif-sample-images/master/fox.png
Here's the 12 bit AVIF to see how your browser decodes it:
https://raw.githubusercontent.com/link-u/avif-sample-images/master/fox.profile2.12bpc.yuv422.avif
And here's the result from `heif-convert` in master:
If you put them in separate tabs and flip you can hopefully see the issue.
Looking at the histograms shows the problem:
The 12 bit version has been shifted right by about 17, using 8-bit units. Ten bit AVIF images have the same problem, but the shift is smaller, perhaps 14.
I can work around this, sort-of, with:
https://github.com/libvips/libvips/commit/7bff57bcd969464dc61370f55ad9d4c52538fd8a
But that's obviously not a great solution since the white will now be off by that amount.
Ubuntu 22.04 with git master libheif, libaom 3.3.0, libdav1d 0.9.2, though earlier versions seem to have the issue as well.
Downstream issue: https://github.com/libvips/libvips/issues/3123 | strange black offset for 10 and 12 bit AVIF decode | https://api.github.com/repos/strukturag/libheif/issues/706/comments | 8 | 2022-11-03T12:54:48Z | 2022-11-15T13:28:47Z | https://github.com/strukturag/libheif/issues/706 | 1,434,615,270 | 706 |
[
"strukturag",
"libheif"
]
| Hello. I always use this library to convert jpg to heic since latter takes less space, but I have a problem that color in output heic file is kind of different comparing with input jpg, despite the fact that they both use same settings.
For instance this one, (jpg/heic/difference (I mirrored 2nd one for easier comparison)) the HEIC (2) has orange spot whereas JPG (1) has red one.
Looking at the map for the difference, it is clear that many colors have changed, and not so much their brightness (then the map for the difference would be black and white) as the color values themselves
I surfed many issues' pages but didn't find anything helping. Is there any way to preserve color, not its
quality but its value. The problem should be in heic, since when you convert png to jpg there ain't any visible color changes. And even I use -L parameter it doesn't help. Thank you. | Unwanted color change | https://api.github.com/repos/strukturag/libheif/issues/705/comments | 2 | 2022-10-31T18:09:15Z | 2023-05-31T09:55:06Z | https://github.com/strukturag/libheif/issues/705 | 1,430,269,112 | 705 |
[
"strukturag",
"libheif"
]
| It would be very useful to be able to specify the compression level for png output in heif-convert. Specifically, setting the level to zero results in significantly better performance.
Are you interested in a patch?
Thanks! | Allow to specify png compression level in heif-convert | https://api.github.com/repos/strukturag/libheif/issues/704/comments | 1 | 2022-10-29T20:12:21Z | 2023-05-14T10:46:36Z | https://github.com/strukturag/libheif/issues/704 | 1,428,436,788 | 704 |
[
"strukturag",
"libheif"
]
| Actually the question is in the title, I did not find instructions, but the possibility is stated. | How encode multiple images? | https://api.github.com/repos/strukturag/libheif/issues/703/comments | 6 | 2022-10-28T16:56:33Z | 2022-11-21T03:23:52Z | https://github.com/strukturag/libheif/issues/703 | 1,427,528,885 | 703 |
[
"strukturag",
"libheif"
]
| In the context of #692, I am trying to encapsulate grid-image tiles in a HEIF file. Encoding seems to be OK, but when the number of tiles is large (~6700), I get a
> Invalid input: No 'meta' box
when decoding :slightly_frowning_face:.
Is there a limit to the number of top level image in a HEIF file or am I doing something conceptually wrong?
Thank you for your help.
| Is there a limit to top level image count? | https://api.github.com/repos/strukturag/libheif/issues/702/comments | 6 | 2022-10-26T15:37:44Z | 2022-10-27T20:23:21Z | https://github.com/strukturag/libheif/issues/702 | 1,424,270,620 | 702 |
[
"strukturag",
"libheif"
]
| Sorry for raising a question here; however, this may lead to an opportunity to improve `readme.md`.
## Problem
When compiling from source: `libaom` and then `libheif`, `libheif` shows it found `libaom` during `configure` step:
```sh
checking pkg-config is at least version 0.9.0... yes
checking for aom... yes
checking aom/aom_decoder.h usability... yes
checking aom/aom_decoder.h presence... yes
checking for aom/aom_decoder.h... yes
checking aom/aom_encoder.h usability... yes
checking aom/aom_encoder.h presence... yes
checking for aom/aom_encoder.h... yes
```
However, when printing variables, `libheif` doesn't indicate `libaom` is configured:
```sh
$ pkg-config libheif --print-variables
builtin_avif_encoder
exec_prefix
builtin_h265_encoder
prefix
libdir
includedir
builtin_avif_decoder
builtin_h265_decoder
```
## Question
Is, not showing `libaom` in variables, the expected behavior?
- if it is, then what's the proper way to check what codec would be used for encoding/decoding from the CLI? | Question. How to check what codec was used | https://api.github.com/repos/strukturag/libheif/issues/700/comments | 2 | 2022-10-26T07:54:01Z | 2022-10-26T09:27:15Z | https://github.com/strukturag/libheif/issues/700 | 1,423,591,676 | 700 |
[
"strukturag",
"libheif"
]
| Hello, I use `heif-convert 1.13.0`
I use the parameter `--with-aux` which sometimes seems to produce extra files like `lumpi-urn:com:apple:photo:2020:aux:hdrgainmap.jpg`. When are this files produces and what do they mean? | Auxiliary image written to lumpi-urn:com:apple:photo:2020:aux:hdrgainmap.jpg - what's that | https://api.github.com/repos/strukturag/libheif/issues/699/comments | 1 | 2022-10-25T18:05:22Z | 2023-01-18T19:52:39Z | https://github.com/strukturag/libheif/issues/699 | 1,422,871,255 | 699 |
[
"strukturag",
"libheif"
]
| The library of https://github.com/dlemstra/Magick.NET uses libheif to convert AVIF files.
When I tried the sample AVIF files from this repository: https://github.com/link-u/avif-sample-images most of the files succeeded. But some files don't. Some examples:
`https://github.com/link-u/avif-sample-images/blob/master/plum-blossom-small.profile0.10bpc.yuv420.alpha-full.avif
https://github.com/link-u/avif-sample-images/blob/master/plum-blossom-small.profile0.10bpc.yuv420.alpha-full.monochrome.avif
https://github.com/link-u/avif-sample-images/blob/master/plum-blossom-small.profile0.10bpc.yuv420.alpha-limited.avif`
The error which is shown is:
`inboxwarning: fast thumbnail generation failed. Exception message: Invalid input: No properties assigned to item: Item (ID=2) has no properties assigned to it in ipma box (2.116) C:/Users/%user%/AppData/Local/Temp/magick-II8GgJjkwG8lWZecOjJs3ppfPdf7MO7T @ error/heic.c/IsHEIFSuccess/135`
| Sample AVIF files fail to convert with Magick.NET | https://api.github.com/repos/strukturag/libheif/issues/697/comments | 1 | 2022-10-22T20:01:40Z | 2022-11-14T19:48:24Z | https://github.com/strukturag/libheif/issues/697 | 1,419,483,672 | 697 |
[
"strukturag",
"libheif"
]
| I have a large tiled image (DZI like) and I would like to convert it to HEIF format.
I see that decoding tiled images is supported
https://github.com/strukturag/libheif/blob/18291ddebc23c924440a8a3c9a7267fe3beb5901/libheif/heif_context.cc#L1324
but I can't find any reference on tiled images encoding. Can anyone please point me to some documentation or example or any useful material.
Sorry if it is not the right place to ask. :pray: | Tiled image encodeing | https://api.github.com/repos/strukturag/libheif/issues/692/comments | 5 | 2022-10-20T09:13:16Z | 2024-03-21T07:56:03Z | https://github.com/strukturag/libheif/issues/692 | 1,416,261,759 | 692 |
[
"strukturag",
"libheif"
]
| With the following configure options the build fails: `./configure CXXFLAGS="-DNDEBUG -Wall"`. I am getting the following error message:
```
g++ -DHAVE_CONFIG_H -I. -I.. -DNDEBUG -Wall -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-error=unused-parameter -Wno-error=deprecated-declarations -Wno-error=tautological-compare -MT file_fuzzer.o -MD -MP -MF $depbase.Tpo -c -o file_fuzzer.o file_fuzzer.cc &&\
mv -f $depbase.Tpo $depbase.Po
file_fuzzer.cc: In function ‘void TestDecodeImage(heif_context*, const heif_image_handle*, size_t)’:
file_fuzzer.cc:38:7: error: unused variable ‘width’ [-Werror=unused-variable]
38 | int width = heif_image_handle_get_width(handle);
| ^~~~~
file_fuzzer.cc:39:7: error: unused variable ‘height’ [-Werror=unused-variable]
39 | int height = heif_image_handle_get_height(handle);
| ^~~~~~
file_fuzzer.cc:47:7: error: unused variable ‘metadata_ids_count’ [-Werror=unused-variable]
47 | int metadata_ids_count = heif_image_handle_get_list_of_metadata_block_IDs(handle, nullptr, metadata_ids,
| ^~~~~~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
```
Also a bit strange that these files get build when I did not use `--enable-fuzzing`. I solved this locale with some `ifndef NDEBUG` checks but that is probably not the best way. | Build fails with: ./configure CXXFLAGS="-DNDEBUG -Wall" | https://api.github.com/repos/strukturag/libheif/issues/686/comments | 3 | 2022-10-15T20:03:36Z | 2023-04-29T22:26:34Z | https://github.com/strukturag/libheif/issues/686 | 1,410,276,823 | 686 |
[
"strukturag",
"libheif"
]
| I'm using RasPiOS based on Debian,
```
Log started: 2022-09-12 12:59:33
(Reading database ... 229428 files and directories currently installed.)
Preparing to unpack .../libgdk-pixbuf-2.0-dev_2.42.2+dfsg-1+deb11u1_armhf.deb ...
Unpacking libgdk-pixbuf-2.0-dev:armhf (2.42.2+dfsg-1+deb11u1) over (2.42.2+dfsg-1) ...
Preparing to unpack .../libgdk-pixbuf-2.0-0_2.42.2+dfsg-1+deb11u1_armhf.deb ...
Unpacking libgdk-pixbuf-2.0-0:armhf (2.42.2+dfsg-1+deb11u1) over (2.42.2+dfsg-1) ...
Preparing to unpack .../libgdk-pixbuf2.0-common_2.42.2+dfsg-1+deb11u1_all.deb ...
Unpacking libgdk-pixbuf2.0-common (2.42.2+dfsg-1+deb11u1) over (2.42.2+dfsg-1) ...
Preparing to unpack .../libgdk-pixbuf2.0-bin_2.42.2+dfsg-1+deb11u1_armhf.deb ...
Unpacking libgdk-pixbuf2.0-bin (2.42.2+dfsg-1+deb11u1) over (2.42.2+dfsg-1) ...
Preparing to unpack .../gir1.2-gdkpixbuf-2.0_2.42.2+dfsg-1+deb11u1_armhf.deb ...
Unpacking gir1.2-gdkpixbuf-2.0:armhf (2.42.2+dfsg-1+deb11u1) over (2.42.2+dfsg-1) ...
Setting up libgdk-pixbuf2.0-common (2.42.2+dfsg-1+deb11u1) ...
Setting up libgdk-pixbuf-2.0-0:armhf (2.42.2+dfsg-1+deb11u1) ...
Setting up gir1.2-gdkpixbuf-2.0:armhf (2.42.2+dfsg-1+deb11u1) ...
Setting up libgdk-pixbuf2.0-bin (2.42.2+dfsg-1+deb11u1) ...
Setting up libgdk-pixbuf-2.0-dev:armhf (2.42.2+dfsg-1+deb11u1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u4) ...
Log ended: 2022-09-12 12:59:40
```
After this update via `sudo apt update`, my RPi reboots when I try to change or import HEIC image format. This issue occurs with both `GIMP`(sometimes) and `ImageMagick convert` command-line(always).
The command-line can be solved by replacing it with `heif-convert` using `heif-examples`.
I have two heif libraries that automatically installed, `heif-gdk-pixbuf` 1.11.0-1 and `libheif1` 1.11.0-1. | My RPi reboots when I try to change or import HEIC | https://api.github.com/repos/strukturag/libheif/issues/681/comments | 0 | 2022-10-06T14:07:33Z | 2022-10-06T15:20:31Z | https://github.com/strukturag/libheif/issues/681 | 1,399,708,931 | 681 |
[
"strukturag",
"libheif"
]
| The `Orientation` field in the EXIF is ignored for HEIF images, but it is used for JPEG images. This has to be considered when converting HEIC to JPEG. Currently, `heif_convert` does this by ignoring the HEIF transformations during decoding the image and keeping the EXIF Orientation.
However, this does not work when the EXIF Orientation is not in sync with the `irot` box. For example, image 43.heic in #677 has an EXIF Orientation set to "90 CW", while there is no `irot` box. This leads to a wrong orientation in the resulting JPEG.
We have to remove the EXIF Orientation field during the conversion. However, this will likely require a new dependency on some EXIF processing library like `libexif`.
| heif_convert should remove Orientation fields from EXIF | https://api.github.com/repos/strukturag/libheif/issues/680/comments | 4 | 2022-10-05T09:21:43Z | 2022-10-17T18:08:12Z | https://github.com/strukturag/libheif/issues/680 | 1,397,497,695 | 680 |
[
"strukturag",
"libheif"
]
| converting mat into uint8_t array, it should be something like `[[r,g,b,r,g,b,...,r,g,b] * height_times ] * width_times ]`, how can I encode this uint8_t array into heif? | Encoding an RGB image in opencv mat format | https://api.github.com/repos/strukturag/libheif/issues/678/comments | 0 | 2022-09-29T09:08:43Z | 2022-09-29T09:46:23Z | https://github.com/strukturag/libheif/issues/678 | 1,390,526,298 | 678 |
[
"strukturag",
"libheif"
]
| I am use ImageMagick which is using libheif to handle heic files. However, when I convert photos to heic, their exif orientations are always recognized as 1 (no rotate) while Exif orientation is not 1. Here's the example:
[43.txt](https://github.com/strukturag/libheif/files/9662539/43.txt)
See blow 43.heic is not placed correctly. (43ae...ff27.heic is the original photo, I used "convert -define heic:preserve-orientation=true 43ae6f68-7f55-4228-bff3-61c2b383ff27.heic 43.heic")
<img width="427" alt="image" src="https://user-images.githubusercontent.com/43056596/192733260-a22557eb-156c-4b50-8d15-f83c4c92bb76.png">
And Preview App says orientation is 1:
Looks like the m_miaf_compatible is set to true by default and only set to false in some cases. Thus most of heic files will have the "miaf" appended. Is this a bug or Apple's fault?
| extra compatible brand "miaf" make MacOS cannot recognize Exif orientation | https://api.github.com/repos/strukturag/libheif/issues/677/comments | 13 | 2022-09-28T08:02:15Z | 2022-10-17T18:08:44Z | https://github.com/strukturag/libheif/issues/677 | 1,388,910,393 | 677 |
[
"strukturag",
"libheif"
]
| centos 7.x
`cd /tmp && \
tar zvxf libheif-${LIBHEIF_VERSION}.tar.gz && \
cd /tmp/libheif-${LIBHEIF_VERSION} && \
./configure --prefix=/vips && \
make && \
make install`
When i installed it returns
`[2022-09-28 10:33:12] /bin/sh ../libtool --tag=CXX --mode=link g++ -I.. -I../. -I/usr/include/libpng15 -g -O2 -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-error=unused-parameter -Wno-error=deprecated-declarations -Wno-error=tautological-compare -o heif-convert heif_convert-encoder.o heif_convert-heif_convert.o heif_convert-encoder_y4m.o heif_convert-encoder_png.o ../libheif/libheif.la -lpng15 -lpthread
[2022-09-28 10:33:12] libtool: link: g++ -I.. -I../. -I/usr/include/libpng15 -g -O2 -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-error=unused-parameter -Wno-error=deprecated-declarations -Wno-error=tautological-compare -o .libs/heif-convert heif_convert-encoder.o heif_convert-heif_convert.o heif_convert-encoder_y4m.o heif_convert-encoder_png.o ../libheif/.libs/libheif.so -lpng15 -lpthread -Wl,-rpath -Wl,/vips/lib
[2022-09-28 10:33:12] /home/opt/compiler/gcc-8.2/bin/../lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lpng15` | cannot find -lpng15 | https://api.github.com/repos/strukturag/libheif/issues/676/comments | 3 | 2022-09-28T02:48:52Z | 2022-09-28T05:34:08Z | https://github.com/strukturag/libheif/issues/676 | 1,388,638,579 | 676 |
[
"strukturag",
"libheif"
]
| I'm coming across some HEIC files the are not converting when I issue the following command:
heif-convert IMG.HEIC IMG.jpg
I get the following output:
Input file is not an HEIF/AVIF file
| Input file is not an HEIF/AVIF file | https://api.github.com/repos/strukturag/libheif/issues/675/comments | 9 | 2022-09-23T15:49:54Z | 2022-09-24T11:09:18Z | https://github.com/strukturag/libheif/issues/675 | 1,383,997,825 | 675 |
[
"strukturag",
"libheif"
]
| Should the pixbufloader-heif.c use heif_init/heif_deinit calls too?
I am somehow worried about thread safety when heif_init/heif_deinit would be called from different threads.
I am thinking, would it be possible to use a mutex in heif_init/heif_deinit avoid potential concurrency problems? | heif_init/heif_deinit | https://api.github.com/repos/strukturag/libheif/issues/674/comments | 7 | 2022-09-16T18:58:11Z | 2022-09-17T09:51:25Z | https://github.com/strukturag/libheif/issues/674 | 1,376,356,865 | 674 |
[
"strukturag",
"libheif"
]
| I'm trying to run build-emscripten.sh on Ubuntu 20.04 in WSL2, but it fails with this message:
```
wasm-ld: error: unknown file type: .libs/libheif_la-nclx.o
em++: error: '/root/emsdk/upstream/bin/wasm-ld -o .libs/libheif.so.1.13.0 .libs/libheif_la-bitstream.o .libs/libheif_la-box.o .libs/libheif_la-error.o .libs/libheif_la-heif_file.o .libs/libheif_la-heif_image.o .libs/libheif_la-heif.o .libs/libheif_la-heif_context.o .libs/libheif_la-heif_hevc.o .libs/libheif_la-heif_init.o .libs/libheif_la-heif_avif.o .libs/libheif_la-heif_plugin_registry.o .libs/libheif_la-heif_plugin.o .libs/libheif_la-heif_colorconversion.o .libs/libheif_la-nclx.o .libs/libheif_la-heif_decoder_libde265.o -L/root/libheif/libde265-1.0.8/libde265/.libs -L/root/emsdk/upstream/emscripten/cache/sysroot/lib/wasm32-emscripten -lal -lhtml5 -lstubs -lc /root/emsdk/upstream/emscripten/cache/sysroot/lib/wasm32-emscripten/libdlmalloc.a -lcompiler_rt /root/emsdk/upstream/emscripten/cache/sysroot/lib/wasm32-emscripten/libc++-noexcept.a /root/emsdk/upstream/emscripten/cache/sysroot/lib/wasm32-emscripten/libc++abi-noexcept.a -lsockets -L/root/emsdk/upstream/emscripten/cache/sysroot/lib/wasm32-emscripten --relocatable -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr' failed (returned 1)
make[2]: *** [Makefile:988: libheif.la] Error 1
make[2]: Leaving directory '/root/libheif/libheif'
make[1]: *** [Makefile:537: all-recursive] Error 1
make[1]: Leaving directory '/root/libheif'
make: *** [Makefile:446: all] Error 2
emmake: error: 'make -j4' failed (returned 2)
```
You can see the full log here: https://gist.github.com/sk-zk/e40352996382e265b7f0bb88b05f3de8 | wasm-ld: error: unknown file type: .libs/libheif_la-nclx.o | https://api.github.com/repos/strukturag/libheif/issues/672/comments | 0 | 2022-09-13T10:19:19Z | 2022-09-13T10:19:19Z | https://github.com/strukturag/libheif/issues/672 | 1,371,210,164 | 672 |
[
"strukturag",
"libheif"
]
| Rather than encoding an image as an hcv1 image, I want to encode the image using JPEG 2000 and store it in a heif. Does libheif support this functionality?
The instructions for doing this are stored in the following document: https://www.iso.org/standard/80620.html
(Unfortunately, the document isn't free) | JPEG 2000 | https://api.github.com/repos/strukturag/libheif/issues/671/comments | 13 | 2022-09-12T15:20:55Z | 2023-12-01T22:50:34Z | https://github.com/strukturag/libheif/issues/671 | 1,370,089,299 | 671 |
[
"strukturag",
"libheif"
]
| `heif_init()` and `heif_deinit()` were introduced to properly clean up allocated memory when the program ends.
It was implemented such that it should still be backward compatible (i.e. plugins are still initialized at program start by default).
The dummy-class for initialization has been moved to https://github.com/strukturag/libheif/blob/626b6203f1d033f9e8bcacd610baf7cbe775ce82/libheif/heif_init.cc#L80-L87
Still, people report that plugins are not automatically registered at start anymore (https://github.com/strukturag/libheif/issues/554#issuecomment-1232771115).
| Plugins not registered by default after introduction of heif_init() | https://api.github.com/repos/strukturag/libheif/issues/668/comments | 4 | 2022-08-31T11:10:26Z | 2022-08-31T12:46:38Z | https://github.com/strukturag/libheif/issues/668 | 1,357,179,319 | 668 |
[
"strukturag",
"libheif"
]
| Hi All,
I am using below API to decode heif image and get date in image.
struct heif_image* image;
err = heif_decode_image(handle, &image, heif_colorspace_RGB, heif_chroma_interleaved_RGB, decode_options);
Could you please let me know how to get bmp or write bmp from image data which i got from API.
Thanks in advance | How can I write BMP image from heif_image | https://api.github.com/repos/strukturag/libheif/issues/666/comments | 3 | 2022-08-23T11:32:54Z | 2023-01-18T19:42:57Z | https://github.com/strukturag/libheif/issues/666 | 1,347,800,927 | 666 |
[
"strukturag",
"libheif"
]
| I am using [photoview](https://github.com/photoview/photoview) which is importing HEIC/HEIF images with libheif v1.12.0 and I get the following error processing a HEIF image on machine with 4x32 bit ARM CPUs and 8GB of RAM (~4GB are usually free). What is special about this image is that it is a panorama image created on the iPhone 11 Pro with a file size of 15.8 MB (15,769,902 bytes) and an image size of 16382 × 3794 pixels.
```
runtime: out of memory: cannot allocate 251658240-byte block (863109120 in use)
fatal error: out of memory
goroutine 237700 [running]:
runtime.throw({0x9f3fae, 0xd})
/usr/lib/go-1.18/src/runtime/panic.go:992 +0x5c fp=0xc11d850 sp=0xc11d83c pc=0x9334c
runtime.(*mcache).allocLarge(0x74b40538, 0xed18970, 0x1)
/usr/lib/go-1.18/src/runtime/mcache.go:215 +0x1e4 fp=0xc11d878 sp=0xc11d850 pc=0x711c8
runtime.mallocgc(0xed18970, 0x954398, 0x1)
/usr/lib/go-1.18/src/runtime/malloc.go:1096 +0x690 fp=0xc11d8b8 sp=0xc11d878 pc=0x6720c
runtime.makeslice(0x954398, 0xed18970, 0xed18970)
/usr/lib/go-1.18/src/runtime/slice.go:103 +0xac fp=0xc11d8cc sp=0xc11d8b8 pc=0xac6f8
github.com/strukturag/libheif/go/heif.(*Image).GetImage(0xc0f66a0)
/go/pkg/mod/github.com/strukturag/[email protected]/go/heif/heif.go:828 +0x5fc fp=0xc11d9e8 sp=0xc11d8cc pc=0x74febc
github.com/strukturag/libheif/go/heif.decodeImage({0xaf587c, 0x4b5b4a0})
/go/pkg/mod/github.com/strukturag/[email protected]/go/heif/heif.go:1381 +0x98 fp=0xc11da08 sp=0xc11d9e8 pc=0x751e78
image.Decode({0xaf62b8, 0x8749fd0})
```
| Out of memory crash decoding 16MB HEIF image | https://api.github.com/repos/strukturag/libheif/issues/665/comments | 2 | 2022-08-22T08:32:19Z | 2023-03-19T13:53:09Z | https://github.com/strukturag/libheif/issues/665 | 1,346,026,712 | 665 |
[
"strukturag",
"libheif"
]
| Version: 1.12
[img example](http://fnordware.com/superpng/pnggrad16rgb.png)
`heif-enc pnggrad16rgb.png -p chroma=444`
<img width="703" alt="image" src="https://user-images.githubusercontent.com/13381981/185197980-409ce5c0-e11b-4fd4-bf1d-088d48580c95.png">
<img width="644" alt="image" src="https://user-images.githubusercontent.com/13381981/185198295-43596c72-9ef7-4552-a306-d262f1a353a0.png">
<img width="603" alt="image" src="https://user-images.githubusercontent.com/13381981/185214822-494b5bde-a567-4d65-8b8d-501577a0e8bc.png">
With dimensions 128x128, 64x64, 32x32 and 15x15 images is ok.
The same applies for 8 bit images.
Also tried the same on `master` version today from this repository and the same problem occurred.
P.S: Encoded files was opened by macOS viewer, when they opened by libheif itself they looks fine.
| chroma=444 makes wrong images with some dimensions | https://api.github.com/repos/strukturag/libheif/issues/661/comments | 6 | 2022-08-17T18:22:27Z | 2022-09-02T17:33:20Z | https://github.com/strukturag/libheif/issues/661 | 1,342,122,720 | 661 |
[
"strukturag",
"libheif"
]
| Do you know why it is not possible to install libheif through vcpkg on MACOS-Arm64 ?.
Seems the vcpkg having problem installing the x265 library for Latest MacOS having M1 chip-set.
Is it going to be resolved ?
Are there any package manager by which libheif binaries could be installed on machines having the following architectures ?
Windows-x86-64
Windows-arm
Windows-arm64
Linux-x86-64
Linux-arm
Linux-arm64
MacOS-x86-64
MacOS-arm
MacOS-arm64 | Query: libheif installation through vcpkg on MACOS-Arm64 | https://api.github.com/repos/strukturag/libheif/issues/659/comments | 2 | 2022-08-10T07:28:17Z | 2022-08-20T07:17:10Z | https://github.com/strukturag/libheif/issues/659 | 1,334,198,617 | 659 |
[
"strukturag",
"libheif"
]
| Apple M1 Pro. Follow the installation instructions, and try to run examples `./heif-enc` to convert png to heif and get error `Cannot load PNG because libpng support was not compiled.` pkg-config can locate libpng. | Cannot load PNG because libpng support was not compiled. | https://api.github.com/repos/strukturag/libheif/issues/657/comments | 4 | 2022-08-02T06:40:29Z | 2022-08-31T04:45:50Z | https://github.com/strukturag/libheif/issues/657 | 1,325,361,072 | 657 |
[
"strukturag",
"libheif"
]
| Hi,
I'm having issues of `heif-convert` not recognizing some pictures from an iPhone. The majority of the images work ok, for some some I get:
```
$ heif-convert file.HEIC file.jpg
Input file is not an HEIF file.
```
The same file is successfully opened in GIMP.
```
$ uname -a
Linux ryzen7 5.15.0-41-generic #44~20.04.1-Ubuntu SMP Fri Jun 24 13:27:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
```
```
$ apt version libheif-examples
1.6.1-1build1
```
| Input file is not a HEIF file | https://api.github.com/repos/strukturag/libheif/issues/655/comments | 4 | 2022-07-26T10:20:27Z | 2022-11-23T17:46:09Z | https://github.com/strukturag/libheif/issues/655 | 1,318,021,701 | 655 |
[
"strukturag",
"libheif"
]
| Hey,
I just found the following ASAN hit on libheif. The destructor of ColorProfile_nclx doesn't use the correct function to destroy its members:
https://github.com/strukturag/libheif/blob/64d9ab99ce7ea8876700c034b19bbc8dd773ae0b/libheif/heif_cxx.h#L787-L795
```
==51910==ERROR: AddressSanitizer: alloc-dealloc-mismatch (malloc vs operator delete) on 0x6060000f3e00
#0 0x55c03cdabd19 in operator delete(void*) (/home/amalia/krita/build/plugins/impex/heif/tests/KisHeifTest+0x11ad19)
#1 0x7f7fca79d226 in heif::ColorProfile_nclx::~ColorProfile_nclx() /usr/include/libheif/heif_cxx.h:798:5
#2 0x7f7fca79d226 in HeifExport::convert(KisDocument*, QIODevice*, KisPinnedSharedPtr<KisPropertiesConfiguration>) /home/amalia/krita/src/plugins/impex/heif/HeifExport.cpp:451:9
#3 0x7f7fdf7666bb in KisImportExportManager::doExportImpl(QString const&, QSharedPointer<KisImportExportFilter>, KisPinnedSharedPtr<KisPropertiesConfiguration>) /home/amalia/krita/src/libs/ui/KisImportExportManager.cpp:733:47
#4 0x7f7fdf763e26 in KisImportExportManager::doExport(QString const&, QSharedPointer<KisImportExportFilter>, KisPinnedSharedPtr<KisPropertiesConfiguration>, bool) /home/amalia/krita/src/libs/ui/KisImportExportManager.cpp:677:13
#5 0x7f7fdf74e48d in KisImportExportManager::convert(KisImportExportManager::Direction, QString const&, QString const&, QString const&, bool, KisPinnedSharedPtr<KisPropertiesConfiguration>, bool, bool) /home/amalia/krita/src/libs/ui/KisImportExportManager.cpp:441:22
#6 0x7f7fdf75286e in KisImportExportManager::exportDocument(QString const&, QString const&, QByteArray const&, bool, KisPinnedSharedPtr<KisPropertiesConfiguration>, bool) /home/amalia/krita/src/libs/ui/KisImportExportManager.cpp:137:31
#7 0x7f7fdf703c7b in KisDocument::exportDocumentSync(QString const&, QByteArray const&, KisPinnedSharedPtr<KisPropertiesConfiguration>) /home/amalia/krita/src/libs/ui/KisDocument.cpp:1199:13
#8 0x55c03cdd0158 in KisHeifTest::testSaveHDR() /home/amalia/krita/src/plugins/impex/heif/tests/KisHeifTest.cpp:243:14
#9 0x55c03cdae23c in KisHeifTest::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) /home/amalia/krita/build/plugins/impex/heif/tests/KisHeifTest_autogen/EWIEGA46WW/moc_KisHeifTest.cpp:111:21
#10 0x7f7fd904623d in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const (/usr/lib/libQt5Core.so.5+0x29c23d)
#11 0x7f7fde225a6b in QTest::qRun() (/usr/lib/libQt5Test.so.5+0x1ba6b)
#12 0x7f7fde226c40 in QTest::qExec(QObject*, int, char**) (/usr/lib/libQt5Test.so.5+0x1cc40)
#13 0x55c03cde7b21 in main /home/amalia/krita/src/plugins/impex/heif/tests/KisHeifTest.cpp:531:1
#14 0x7f7fd888728f (/usr/lib/libc.so.6+0x2928f)
#15 0x7f7fd8887349 in __libc_start_main (/usr/lib/libc.so.6+0x29349)
#16 0x55c03ccc6d44 in _start /build/glibc/src/glibc/csu/../sysdeps/x86_64/start.S:115
0x6060000f3e00 is located 0 bytes inside of 52-byte region [0x6060000f3e00,0x6060000f3e34)
allocated by thread T0 here:
#0 0x55c03cd719c9 in malloc (/home/amalia/krita/build/plugins/impex/heif/tests/KisHeifTest+0xe09c9)
#1 0x7f7fcd9b99a2 in heif_nclx_color_profile_alloc (/usr/lib/libheif.so.1+0x409a2)
#2 0x7f7fdf7666bb in KisImportExportManager::doExportImpl(QString const&, QSharedPointer<KisImportExportFilter>, KisPinnedSharedPtr<KisPropertiesConfiguration>) /home/amalia/krita/src/libs/ui/KisImportExportManager.cpp:733:47
#3 0x7f7fdf763e26 in KisImportExportManager::doExport(QString const&, QSharedPointer<KisImportExportFilter>, KisPinnedSharedPtr<KisPropertiesConfiguration>, bool) /home/amalia/krita/src/libs/ui/KisImportExportManager.cpp:677:13
#4 0x7f7fdf74e48d in KisImportExportManager::convert(KisImportExportManager::Direction, QString const&, QString const&, QString const&, bool, KisPinnedSharedPtr<KisPropertiesConfiguration>, bool, bool) /home/amalia/krita/src/libs/ui/KisImportExportManager.cpp:441:22
#5 0x7f7fdf75286e in KisImportExportManager::exportDocument(QString const&, QString const&, QByteArray const&, bool, KisPinnedSharedPtr<KisPropertiesConfiguration>, bool) /home/amalia/krita/src/libs/ui/KisImportExportManager.cpp:137:31
#6 0x7f7fdf703c7b in KisDocument::exportDocumentSync(QString const&, QByteArray const&, KisPinnedSharedPtr<KisPropertiesConfiguration>) /home/amalia/krita/src/libs/ui/KisDocument.cpp:1199:13
#7 0x55c03cdd0158 in KisHeifTest::testSaveHDR() /home/amalia/krita/src/plugins/impex/heif/tests/KisHeifTest.cpp:243:14
#8 0x55c03cdae23c in KisHeifTest::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) /home/amalia/krita/build/plugins/impex/heif/tests/KisHeifTest_autogen/EWIEGA46WW/moc_KisHeifTest.cpp:111:21
#9 0x7f7fd904623d in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const (/usr/lib/libQt5Core.so.5+0x29c23d)
#10 0x7f7fde225a6b in QTest::qRun() (/usr/lib/libQt5Test.so.5+0x1ba6b)
#11 0x7f7fde226c40 in QTest::qExec(QObject*, int, char**) (/usr/lib/libQt5Test.so.5+0x1cc40)
#12 0x7f7fd888728f (/usr/lib/libc.so.6+0x2928f)
``` | AddressSanitizer alloc-dealloc-mismatch on ColorProfile_nclx::~ColorProfile_nclx | https://api.github.com/repos/strukturag/libheif/issues/652/comments | 1 | 2022-07-09T21:20:39Z | 2022-08-22T06:07:23Z | https://github.com/strukturag/libheif/issues/652 | 1,299,769,307 | 652 |
[
"strukturag",
"libheif"
]
| I started from the example in the readme. Unfortunately, error handling is not part of the example, this would be useful.
But I consider it essential to include the clean up part, e.g. like this:
```
// done, clean up
heif_image_handle_release(handle);
heif_context_free(ctx);
```
At least this would have saved me a lot of debugging.
Thanks for your effort! | suggesting to improve reading example in readme | https://api.github.com/repos/strukturag/libheif/issues/651/comments | 2 | 2022-07-08T21:12:12Z | 2023-05-05T11:50:08Z | https://github.com/strukturag/libheif/issues/651 | 1,299,447,376 | 651 |
[
"strukturag",
"libheif"
]
| ./configure CXXFLAGS='-fopenmp -g -O2 -Wl,-z,relro,-z,now -fPIC -fPIE -pie -fstack-protector-strong -D_FORTIFY_SOURCE=2 -O2' --enable-shared --disable-static
The -pie option has been added, and the compilation will fail.
The error msg is：
/usr/lib64/libc_nonshared.a(elf-init.oS): In function `__libc_csu_init':
(.text+0x14): undefined reference to `__init_array_start'
/usr/bin/ld: /usr/lib64/libc_nonshared.a(elf-init.oS): relocation R_X86_64_PC32 against undefined hidden symbol `__init_array_start' can not be used when making a shared object
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status
make[2]: *** [libheif.la] Error 1
Has anyone encountered？
| Failed to make with pie | https://api.github.com/repos/strukturag/libheif/issues/650/comments | 1 | 2022-07-05T02:45:56Z | 2023-06-09T07:12:33Z | https://github.com/strukturag/libheif/issues/650 | 1,293,717,783 | 650 |
[
"strukturag",
"libheif"
]
| I want to write a heif that is gridded. In other words, the image is divided into an arbitrary number of tiles.
Does libheif support this feature? If not, where would be an ideal place to implement it? | Writing Gridded Imagery | https://api.github.com/repos/strukturag/libheif/issues/648/comments | 0 | 2022-06-29T14:35:53Z | 2024-06-25T18:19:12Z | https://github.com/strukturag/libheif/issues/648 | 1,288,828,923 | 648 |
[
"strukturag",
"libheif"
]
| Using libheif API I can successfully write an RGB image data to .heic file.
Trying to write ICC color profile data to an image using
```
heif_image_set_raw_color_profile(image, "rICC", input.data(), input.size())
```
and then write that image to the file I am not having any failures.
The problem is that after creating the .heic file (which must also contain the color profile data), I am not able to read the color profile data from that file. I have used the function `heif_image_handle_get_raw_color_profile` and int returns 0.
I have some test samples containing color profile data and I am sure that the getter function `heif_image_handle_get_raw_color_profile` working properly because I can successfully extract that data from the images.
It seems that `heif_image_set_raw_color_profile` function doesn't work at all. | heif_image_set_raw_color_profile doesn't set the color profile data | https://api.github.com/repos/strukturag/libheif/issues/646/comments | 4 | 2022-06-26T16:40:59Z | 2022-07-03T13:05:07Z | https://github.com/strukturag/libheif/issues/646 | 1,284,972,594 | 646 |
[
"strukturag",
"libheif"
]
| My iPhone photo opens for about 2s. Other much heavier files open immediately. Will the speed be optimised in the future or is it no longer better? | Slow opening of the photo | https://api.github.com/repos/strukturag/libheif/issues/645/comments | 5 | 2022-06-18T16:04:24Z | 2023-04-04T13:30:19Z | https://github.com/strukturag/libheif/issues/645 | 1,275,824,432 | 645 |
[
"strukturag",
"libheif"
]
| Hello,
Would it be possible to make a new release?
The main reason why I am asking is the issue with dav1d 1.0.0 causing libheif 1.12.0 unable to open AVIF.
People on different platforms start to encounter the problem. | New release? | https://api.github.com/repos/strukturag/libheif/issues/644/comments | 1 | 2022-06-18T05:17:37Z | 2022-09-02T10:38:53Z | https://github.com/strukturag/libheif/issues/644 | 1,275,668,600 | 644 |
[
"strukturag",
"libheif"
]
| - OS : macOS Big Sur 11.6.6
- emsdk : 3.1.12
- make: 4.3
- gcc:
Apple clang version 13.0.0 (clang-1300.0.29.30)
Target: x86_64-apple-darwin20.6.0
Thread model: posix
error:
em++: warning: object file output extension (.dylib) used for non-object output. If you meant to build an object file please use `-c, `-r`, or `-shared` [-Wemcc]
wasm-ld: error: unknown argument: -flat_namespace
em++: error: '/Users/bytedance/Workspace/emsdk/upstream/bin/wasm-ld -o .libs/libde265.0.wasm -flat_namespace -undefined suppress .libs/libde265.0.dylib-master.o -L/Users/bytedance/Workspace/emsdk/upstream/emscripten/cache/sysroot/lib/wasm32-emscripten -lGL -lal -lhtml5 -lstubs -lnoexit -lc -ldlmalloc -lcompiler_rt -lc++-noexcept -lc++abi-noexcept -lsockets -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr --import-undefined --export-if-defined=main --export-if-defined=__start_em_asm --export-if-defined=__stop_em_asm --export=stackSave --export=stackRestore --export=stackAlloc --export=__wasm_call_ctors --export=__errno_location --export=malloc --export=__cxa_is_pointer_type --export-table -z stack-size=5242880 --initial-memory=16777216 --no-entry --max-memory=16777216 --global-base=1024' failed (returned 1)
make[3]: *** [libde265.la] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
emmake: error: 'make' failed (returned 2)
| execute ./build-emscripten failed | https://api.github.com/repos/strukturag/libheif/issues/643/comments | 2 | 2022-06-03T07:51:21Z | 2023-01-04T09:39:44Z | https://github.com/strukturag/libheif/issues/643 | 1,259,575,207 | 643 |
[
"strukturag",
"libheif"
]
| I'm curious if it is possible to create HEIF files similar to those from Apple iPhone. They contain multiple layers, HDR Gain map is one among them. It is used to display usual images on iPhone XDR display with a wider tonal range (higher brightness for instance).
I already use ExifTool to add a tag `-CustomRendered=HDR (no original saved)` to JPEGs. They have an HDR tag in Apple Photos app and look brighter on iPhone XDR display. I believe, the result should be better if I will use HDR Gain Map for this. | Assembling multi-file HEIF | https://api.github.com/repos/strukturag/libheif/issues/641/comments | 1 | 2022-05-31T17:15:39Z | 2022-06-02T19:15:39Z | https://github.com/strukturag/libheif/issues/641 | 1,254,162,370 | 641 |
[
"strukturag",
"libheif"
]
| libheif now allows writing to monochrome/grayscale images, but the provided API doesn't seem to provide a way to detect if the input image is monochrome. This is reflected in the sample code, for example:
```
$ file test.jpg
test.jpg: JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, baseline, precision 8, 150x150, components 1
$ ~/local/libheif-1.12.0/bin/heif-enc -o test.heif test.jpg
$ ~/local/libheif-1.12.0/bin/heif-convert test.heif test-out.jpg
File contains 1 images
Written to test-out.jpg
$ file test-out.jpg
test-out.jpg: JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, baseline, precision 8, 150x150, components 3
```
Note how the number of components has changed from 1 to 3.
Unfortunately I don't have all of the relevant HEIF specs, so I'm not sure which boxes would need to be used to determine this.
I suspect the `pixi` box given it changes from (8,8,8) to (8) going from an RGB to a monochrome image, but I suspect `hvcC` also includes relevant information. | how to detect and read monochrome images | https://api.github.com/repos/strukturag/libheif/issues/640/comments | 7 | 2022-05-26T00:30:53Z | 2024-04-02T06:49:49Z | https://github.com/strukturag/libheif/issues/640 | 1,248,944,063 | 640 |
[
"strukturag",
"libheif"
]
| Currently, the libheif (C API) has the following functionality to extract the metadata
* heif_image_handle_get_number_of_metadata_blocks
* heif_image_handle_get_list_of_metadata_block_IDs
* heif_image_handle_get_metadata_type
* heif_image_handle_get_metadata_content_type
* heif_image_handle_get_metadata_size
* heif_image_handle_get_metadata
The question is how to decode the byte array returned by `heif_image_handle_get_metadata` ?.
Are you going to add that functionality or do the users have to deal with the parsing of metadata ?.
For example, the `MacOS` (CoreImage) framework provides the full functionality to decode the metadata.
| How to decode raw metadata returned by heif_image_handle_get_metadata | https://api.github.com/repos/strukturag/libheif/issues/639/comments | 7 | 2022-05-23T19:36:22Z | 2022-09-02T09:41:31Z | https://github.com/strukturag/libheif/issues/639 | 1,245,613,520 | 639 |
[
"strukturag",
"libheif"
]
| Not a real issue,
but just curious to understand why in haif_context.cc (function decode_image_planar) the image is always converted to RGB
if (!alphaImage && target_colorspace == heif_colorspace_YCbCr) {
target_colorspace = heif_colorspace_RGB;
}
instead provide YUV + NCLX information.
Thanks
| Curiosity about why decode_image_planar always emits RGB image | https://api.github.com/repos/strukturag/libheif/issues/636/comments | 7 | 2022-05-03T13:36:16Z | 2023-05-31T10:16:46Z | https://github.com/strukturag/libheif/issues/636 | 1,224,117,984 | 636 |
[
"strukturag",
"libheif"
]
| Applications that would like to have a tight control over usage of threads may crash if implicit multithreading is used by libheif. While 3rd party installations may configure libheif with multithreading, and explicit call to heif_global_set_multithreading(0) or something similar would be very much appreciated for these | crashes: add api for turning off multithreading | https://api.github.com/repos/strukturag/libheif/issues/635/comments | 6 | 2022-04-28T08:38:37Z | 2022-04-28T09:57:23Z | https://github.com/strukturag/libheif/issues/635 | 1,218,394,043 | 635 |
[
"strukturag",
"libheif"
]
| It would be nice to have a flag to preserve the original timestamps of files, right now they're set to whenever the command in executed. | Introduce command line flag to preserve original Access/Modify timestamps | https://api.github.com/repos/strukturag/libheif/issues/633/comments | 0 | 2022-04-22T15:41:59Z | 2022-04-22T15:41:59Z | https://github.com/strukturag/libheif/issues/633 | 1,212,515,008 | 633 |
[
"strukturag",
"libheif"
]
| On gentoo here, everything using libheif breaks when you update dav1d to 1.0.0
libheif is also compiled with libaom-3.3.0 | Broken with dav1d 1.0.0 | https://api.github.com/repos/strukturag/libheif/issues/630/comments | 6 | 2022-04-10T06:44:10Z | 2022-04-11T00:14:29Z | https://github.com/strukturag/libheif/issues/630 | 1,198,906,419 | 630 |
[
"strukturag",
"libheif"
]
| I recently upgraded from Debian Buster to Bullseye.
I have uninstalled and installed the libheif-examples (from the Bullseye repos) but I cannot get it to execute. I get this error
`heif-enc: error while loading shared libraries: libx265.so.165: cannot open shared object file: No such file or directory`
I have these Libx265 files:
./lib/x86_64-linux-gnu/libx265.so.192
./lib/x86_64-linux-gnu/libx265.a
./lib/x86_64-linux-gnu/libx265.so
I'm not sure what I should do to resolve the issue? The "165" version does not see to be available for Bullseye?
| Error with Debian Bullseye | https://api.github.com/repos/strukturag/libheif/issues/629/comments | 2 | 2022-04-04T01:40:33Z | 2023-04-27T21:56:59Z | https://github.com/strukturag/libheif/issues/629 | 1,191,139,634 | 629 |
[
"strukturag",
"libheif"
]
| Hi,
is there a plan to add a HW encoder - f.e NVENC ? | HW encoder | https://api.github.com/repos/strukturag/libheif/issues/628/comments | 0 | 2022-04-01T19:15:22Z | 2022-04-01T19:15:22Z | https://github.com/strukturag/libheif/issues/628 | 1,190,181,143 | 628 |
[
"strukturag",
"libheif"
]
| There are currently a lot of open issues (reproducible crashes) in the [OSS-Fuzz bugtracker]( https://bugs.chromium.org/p/oss-fuzz/issues/list?q=label:Proj-libheif) regarding libheif.
What would be the best way to get them addressed? | OSS-Fuzz status | https://api.github.com/repos/strukturag/libheif/issues/624/comments | 4 | 2022-03-25T15:13:43Z | 2022-04-27T16:08:47Z | https://github.com/strukturag/libheif/issues/624 | 1,180,917,491 | 624 |
[
"strukturag",
"libheif"
]
| Hello,
Is there a way to know if the file just opened via heif_context_read_from_file is a HEIC or AVIF? Or maybe after the call to heif_context_get_primary_image_handle? Or anytime thereafter?
Thanks in advance. | How to retrieve image format after heif_context_read_from_file or heif_context_get_primary_image_handle? | https://api.github.com/repos/strukturag/libheif/issues/622/comments | 0 | 2022-03-20T22:29:52Z | 2022-03-20T22:29:52Z | https://github.com/strukturag/libheif/issues/622 | 1,174,709,608 | 622 |
[
"strukturag",
"libheif"
]
| I'm looking for a way to check if a heif still image (not sequence) has been encoded as lossless. I have used `heif-info` tool without any success.
For the following file that I know has been lossless encoded using AV1 compression this is what I get:
```
$ heif-info example.avif
MIME type: image/avif
main brand: avif
compatible brands: avif, mif1, miaf
image: 500x334 (id=1), primary
color profile: rICC
alpha channel: no
depth channel: no
```
I have tried with `-d` option but I don't identify anything that can help me to check that the image has been lossless encoded.
If `heif-info` don't show that information do we have any other way to check for this?
I'm using libheif 1.12.0. | How to check if a heif file has been lossless encoded | https://api.github.com/repos/strukturag/libheif/issues/621/comments | 4 | 2022-03-20T11:27:07Z | 2022-05-03T14:42:25Z | https://github.com/strukturag/libheif/issues/621 | 1,174,515,232 | 621 |
[
"strukturag",
"libheif"
]
| When trying to use heif-convert I get "Protocol error" as follows:
```
# heif-convert 2021/12/IMG_4661.HEIC JPG/2021/12/IMG_4661.HEIC.jpg
File contains 1 images
Written to JPG/2021/12/IMG_4661.HEIC.jpg
Can't open JPG/2021/12/IMG_4661-urn:com:apple:photo:2020:aux:hdrgainmap.HEIC.jpg: Protocol error
could not write auxiliary image
```
The heif-convert does produce the .jpg image, but throws the above error.
Probably related to hdrgainmap being processed as an image....
```
# heif-info 2021/12/IMG_4661.HEIC
MIME type: image/heic
main brand: heic
compatible brands: mif1, MiHE, MiPr, miaf, MiHB, heic
image: 3024x4032 (id=49), primary
thumbnail: 240x320
color profile: prof
alpha channel: no
depth channel: no
``` | Protocol error when using heif-convert | https://api.github.com/repos/strukturag/libheif/issues/620/comments | 12 | 2022-03-19T14:21:27Z | 2022-04-05T08:53:32Z | https://github.com/strukturag/libheif/issues/620 | 1,174,276,400 | 620 |
[
"strukturag",
"libheif"
]
| There are several lines like this, in box.cc:
**uint32_t** num
...
assert(num <= std::numeric_limits<**int32_t**>::max());
where a uint32_t is compared to std::numeric_limits<int32_t>::max() in an assert.
The compiler flags are set to report this as an error, and abort.
The fix is to replace **int32_t** with **uint32_t** in the assert line.
They occur on line 64 and 65 and 2334 thru 2341.
I have tested this and it works, I can compile, install and convert AVIF files.
| box.cc incompatible integer type errors when trying to compile | https://api.github.com/repos/strukturag/libheif/issues/617/comments | 1 | 2022-02-27T04:47:05Z | 2022-08-30T20:36:17Z | https://github.com/strukturag/libheif/issues/617 | 1,152,812,530 | 617 |
[
"strukturag",
"libheif"
]
| Hi there! In the first place, thank you for building this awesome library!
We're having trouble running the latest `heif-convert` after cloning the repo and compiling it. All the dependencies have been installed (or so we think), including libde265. The OS is an Ubuntu 20.04.
After successfully running through all the steps, when running `heif-convert` we get the following error: `heif-convert: symbol lookup error: heif-convert: undefined symbol: heif_image_handle_get_auxiliary_type`
Any ideas of which missing library/dependency might be causing this issue?
Many thanks in advance! | Runtime error after compiling heif-convert | https://api.github.com/repos/strukturag/libheif/issues/616/comments | 2 | 2022-02-25T15:48:54Z | 2023-06-14T18:31:26Z | https://github.com/strukturag/libheif/issues/616 | 1,150,600,779 | 616 |
[
"strukturag",
"libheif"
]
| Hi all,
I built libheif and linked the dav1d codec to it as a static library (and also libde265). I am on Windows with Visual Studio 2019. HEIF images open without a hitch, but I can't seem to open any AVIF images including example.avif included with libheif. The function dav1d_get_picture always returns DAV1D_ERR(EAGAIN).
I did a step-by-step debugging. dav1d_decode_image() first calls dav1d_send_data(), which returns 0 (success) but inside this function, gen_picture() is called, which parses 4 OBUs, the last one being DAV1D_OBU_TILE_GRP. And then the function dav1d_parse_obus() calls dav1d_submit_frame() and returns. And then, back in gen_picture(), output_picture_ready() does not return true, so it appears the decoder can't find anything to actually decode.
I built the codec strictly according to the instructions, and it built and then linked beautifully.
Can anyone please offer some advice? | Can't seem to open any AVIF image with libheif & dav1d codec -- get DAV1D_ERR(EAGAIN) | https://api.github.com/repos/strukturag/libheif/issues/615/comments | 0 | 2022-02-23T19:24:06Z | 2022-03-20T22:31:16Z | https://github.com/strukturag/libheif/issues/615 | 1,148,486,949 | 615 |
[
"strukturag",
"libheif"
]
| Hello,
I created this [avif image](http://pol2095.free.fr/img/test.avif) on macOS using [SDWebImageAVIFCoder](https://github.com/SDWebImage/SDWebImageAVIFCoder) on macOS
and I try to read the avif image using [libheif-sharp](https://github.com/0xC0000054/libheif-sharp) but I have this message error on Windows :
```
Invalid input: No 'meta' box
```
but it work on Linux using libheif
Thanks | Invalid input: No 'meta' box between macOS and Windows | https://api.github.com/repos/strukturag/libheif/issues/614/comments | 0 | 2022-02-22T19:50:29Z | 2022-02-23T09:35:56Z | https://github.com/strukturag/libheif/issues/614 | 1,147,306,416 | 614 |
[
"strukturag",
"libheif"
]
| I ran into this issue while working with libvips in a Docker container running on an ARM64 (aarch64) host (the actual machine is a M1 MacBook Pro) ([discussion here](https://github.com/libvips/libvips/discussions/2673)). When encoding an image to AVIF using libheif, on ARM64 it crashes with the error `Killed`.
I am able to replicate the same issue when using `heif-enc` from this repository too, version 1.12.0 built from source. The OS is Debian 11 Bullseye, and it seems not connected to the version of the aom library used (happens with both aom from the Debian repos, version 1.0.0, and when re-building version 3.2.0 from source).
Repro steps:
1. Build libheif from source
2. Use the `heif-enc` utility from the `examples` folder to convert a JPEG image to AVIF
```sh
$ ./heif-enc testimage.jpg --avif -o testimage.avif
Killed
``` | Encoding to AVIF crashes on ARM64 | https://api.github.com/repos/strukturag/libheif/issues/608/comments | 0 | 2022-02-20T19:39:02Z | 2022-02-20T19:40:56Z | https://github.com/strukturag/libheif/issues/608 | 1,145,114,442 | 608 |
[
"strukturag",
"libheif"
]
| Test free of the latest patches and additions avif converters.
https://github.com/strukturag/libheif/commit/88085bacb3138c44400fb8f395436732c96a3b2b
https://github.com/AOMediaCodec/libavif/commit/96b47b19464c25a01a6ce1edb2a9c45b345b0338
https://github.com/jbeich/aom/commit/a92f3c847f445800e631a43bc2ab5894fedbc841
https://chromium.googlesource.com/codecs/libwebp2/+/9dea4a218fa327014591542042b5717035d3e3a3
https://gitlab.com/chromiumsrc/libyuv/-/commit/b4ddbaf549a1bf5572bf703fd2862d1eb7380c6a
https://github.com/libjxl/libjxl/commit/9f41cb45bb17197aae6a5c29e926bc2ee71f1ccb
```
av1enc.exe -avif -depth 10 -q 100 -420 -size 1563x1558 -effort 1 -tune butteraugli -thread 4 image_21448_24bit(s)_YCbCr.jxt -d av1enc_30bit_butteraugli.avif
```
Photo is creating for 10bit but is underdeveloped.
```
heifenc.exe image_21448_24bit(s)_YCbCr.jxt -v --avif --no-alpha -b 10 -q 100 -p chroma=420 -p speed=1 -p threads=4 -p tune=butteraugli --matrix_coefficients=6 --full_range_flag=0 -o heifenc_24bit_butteraugli.avif
```
Photo isn't creating for 10bit. It's 8bit.
```
av1enc.exe -avif -depth 10 -q 100 -444 -size 1563x1558 -effort 1 -tune butteraugli -thread 4 image_21447_48bit.png -d av1enc_30bit_butteraugli.avif
```
Photo is creating for 10bit but is underdeveloped.
```
heifenc.exe image_21447_48bit.png -v --avif --no-alpha -b 10 -L -q 100 -p chroma=444 -p speed=1 -p threads=4 -p tune=butteraugli --matrix_coefficients=6 --full_range_flag=1 -o heifenc_24bit_butteraugli.avif
```
Photo isn't creating for 10bit. Codec has unknown error.
https://www.sendspace.com/file/w5btkw | Differences when using tune butteraugli | https://api.github.com/repos/strukturag/libheif/issues/607/comments | 1 | 2022-02-20T10:49:41Z | 2023-12-17T06:44:59Z | https://github.com/strukturag/libheif/issues/607 | 1,144,984,211 | 607 |
[
"strukturag",
"libheif"
]
| This PR merge had to be reverted because of errors in the CI:
https://github.com/strukturag/libheif/pull/565
Please check and create a new PR.
| Fix PR-565 (timed wallpapers) | https://api.github.com/repos/strukturag/libheif/issues/606/comments | 0 | 2022-02-19T19:33:21Z | 2022-02-19T19:33:21Z | https://github.com/strukturag/libheif/issues/606 | 1,144,827,695 | 606 |
[
"strukturag",
"libheif"
]
| Should we add an API to support timed wallpapers? This is an implementation in the Go interface: https://github.com/strukturag/libheif/pull/565
Maybe this should be a wrapper API around libheif that caches the currently interpolated images and can create a blended image given a GPS location and timestamp. | Timed wallpaper API ? | https://api.github.com/repos/strukturag/libheif/issues/605/comments | 0 | 2022-02-19T19:08:02Z | 2022-02-19T19:08:02Z | https://github.com/strukturag/libheif/issues/605 | 1,144,822,521 | 605 |
[
"strukturag",
"libheif"
]
| Hi,
full color JPG images I can convert properly, but the b&w are always black - when opened in irfanview or in some other tool. When opened on ImageMagick, then it is shown fine.
Images converted by ImageMagick(on Linux) are fine.
Tested on Windows with the latest build 1.12
I am missing some special switch there, or it is a bug ? | heif-enc issue wih black and white jpegs | https://api.github.com/repos/strukturag/libheif/issues/604/comments | 13 | 2022-02-19T15:35:17Z | 2022-02-21T18:03:26Z | https://github.com/strukturag/libheif/issues/604 | 1,144,755,541 | 604 |
[
"strukturag",
"libheif"
]
| Hi,
I am trying to launch multiple instances of Heif-enc to process multiple folders of JPG's (500,000+)
On launching a second instance (batchfile) I ways get the error " The process cannot access the file because it is being used by another process"
Regardless if I create separate folders with Heif-enc and all supporting files, and request each instance to process completely independent JPG's, it will consistently return the error of "The process cannot access the file because it is being used by another process"
I want to launch 4+ instances (batchfiles) of Heif-Enc to fully saturate my dual CPU Xeon E5530 based Dell workstation (aka 2 sockets, 8 cores, 16 logical processors) on Win10.
This is to workaround the issue I have described in Issue #602 (Heif-enc 1.12.0 not using all physical processors (sockets), cores, logical processors)
Is there a way to have multiple instances of Heif-Enc processing independent files at the same time?
Many thanks
| Heif-Enc 1.12.0 errors in multiple instance batch files (The process cannot access the file because it is being used by another process) | https://api.github.com/repos/strukturag/libheif/issues/603/comments | 2 | 2022-02-18T13:07:20Z | 2022-02-19T11:07:09Z | https://github.com/strukturag/libheif/issues/603 | 1,143,033,916 | 603 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.