Dirk Farin

> According to [OSS-Fuzz Build Status](https://oss-fuzz-build-logs.storage.googleapis.com/index.html#libheif) , libheif's oss-fuzz builds have been failing since September 23rd. It is now building again.

In the upcoming v1.19.0, I have removed many of the unnecessary internal color conversions. Decoding should be faster in many cases. To get the best decoding speed, use `heif_decode_image()` with...

I really would like to have C++ integer types that have a limited range (e.g. `int'). Then we would not constantly have issues of signed vs unsigned or +1 overflows...

I have downloaded the image: [issue-1183-data.zip](https://github.com/user-attachments/files/15759152/issue-1183-data.zip) The image contains no auxiliary tone-mapping image, just standard EXIF and XMP metadata. The NCLX color profile says that it uses a PQ transfer...

Yes, I agree on the tone mapping and ICC side. This should just be passed through and we can output a warning in `heif-convert` when the auxiliary tone-mapping image is...

For the library itself, this should not include any color management other than basic nclx handling. However, I would consider doing some (optional) color profile conversion in `heif-convert` if we...

> The build failed while building libheif with this error: x265 had changed the signature of the `encoder_encode()` function in version 212. See https://github.com/strukturag/libheif/pull/1314 and https://bitbucket.org/multicoreware/x265_git/issues/952/crash-in-libheif-tests. It seems that they...

I'm also not sure whether there is much benefit in using x265 `master` instead of `stable`. I just know that we constantly had fuzzing alarms because of issues inside x265....

@chenm001 Hi Min Chen, can you advise @bobfriesenhahn which branch of x265 he should use together with libheif for building GraphicsMagick?

Why did you close this PR? It is very good and just was not merged yet because we lack the EVC codec implementation. If you don't mind, I'd like to...