Dirk Farin
Dirk Farin
Yes. But that is for all kinds of parse errors, not only the `essential` flags. In `libde265`, I was assigning decoding errors to the respective images instead of having a...
> @liudian I have an nvdec plugin in draft at https://github.com/bradh/libheif/tree/nvdec - feel free to test and provide feedback. Looking forward to it (but I have no nVidia card to...
See #1007. I've added some API for that in the file `heif_items.h`. Still in the `develop-v1.18.0` branch until merged.
```` uint32_t heif_context_get_item_type(const struct heif_context* ctx, heif_item_id item_id);` const char* heif_context_get_mime_item_content_type(const struct heif_context* ctx, heif_item_id item_id); ````
H.265 works up to 16 bits per pixel. However, libde265 has never been tested with that. I also don't know any encoder implementation that would support this. x265, for example,...
It might be that the old automake build did this, but it has to be done manually in cmake. I found this: https://stackoverflow.com/questions/6693100/how-to-generate-windows-dll-versioning-information-with-cmake
I will look at it when I have time. The vcpkg is not built by me, but I'm sure they will update it when I have a new release.
Do the above changes fix this?
What environment and compiler are you using? I want to reproduce it here.
I see. I thought it may be ARMv7, mobile or old RPi.