Using the code provided by @Zenja in another post for decoding HEIC images, I have put together a very basic image translator, making it possible to read .heic files in Haiku.
The code is available at GitHub - dospuntos/HEICTranslator: HEIC Image translator for Haiku. It’s the first time I take a shot at an image translator for Haiku, so I’m not sure if it’s done the right way, but it seems to work.
Any suggestions for improvements are much appreciated, of course.
Thanks Johan for taking the effort to make an image translator. I can confirm that it works when I manually assign an images FileType
There is a fix you will need to do to fix images with stride problems. See code below for fix. I will have to upload an HEIC image to another site for you to test with since this forum doesn’t allow uploading HEIC images (I cannot upload right now from Iceweasel/epiphany/web+ since they’re all crashing on me today, so reboot needed to upload),.
With the translator wihtout the stride fix, it will crash, but if you put the stride code as below, it will work.
// Convert BGRA to RGBA
const uint8 *src = data;
for (int y=0; y < height; y++)
{
for (int x=0; x<width; x++)
{
uint8 r=*src++;
uint8 g=*src++;
uint8 b=*src++;
uint8 a=*src++;
*dest++ = b;
*dest++ = g;
*dest++ = r;
*dest++ = a;
}
src += stride - (width * 4);
}
Here is a link to a file which exhibits the stride problem. Link expires in 6 days.
Thanks for your detailed answer and the fix, and for providing the image. I updated my code and it seems to work great. Your image caused Tracker to crash before updating the code, now the image loads without problems.
I guess magic signature should be defined and added to Haiku MIME sniffing rules.
If someone knows how:
The answer might be in here:
Programming with Haiku - Lesson 15
Maybe you could have a look here: GitHub - HaikuArchives/EXRTranslator: Haiku EXR translator
It’s not my code, initially it was part of Haiku’s source but it was moved out and transfered to HaikuArchives.
On the SquashFS recipe, I’ve added a new mimetype so those files can be properly recognized:
You can see how the recipes does it here: haikuports/sys-fs/squashfs_tools/squashfs_tools-4.6.1.recipe at master · haikuports/haikuports · GitHub
The mime type is defined as this: haikuports/sys-fs/squashfs_tools/additional-files/x-squashfs-image.rdef at master · haikuports/haikuports · GitHub
Nice. I just found that one earlier today, and I’ll try to use it as a base to improve my translator.
Thanks, looks great. I was able to register mime/heic on my system using DarkWyrm’s tutorial, but this looks quite different. I’ve got some new concepts to learn…
Question: How can I un-register a mime type, so I can test the installation multiple times?
R/W location of mime_db seems to be: /boot/home/config/settings/mime_db. IIRC, while testing things I just had to remove mime_db/application/x-squashfs-image from there, and reboot (not sure if restarting registrar is possible or enough).
(I remember I had to remove more than once application/x-vnd.ram-beezer for example, while adding .hpkg and squashfs support for it 
)
And yes, for native stuff I guess using proper API makes sense. In my case, as squasfs-tools was more of straight port, using this method was the easiest for me.
(just brought this topic after reading some comments on the “how to set default apps” thread, that reminded me I had to do quite some trial and error until I got it working right for squashfs-tools).
Not really, because it means your application (or add-on) code has to be run once for the type to be registered. Sometimes it’s simpler to just provide the MimeDB type file already ready to use.
I’m not sure if translators get a chance to register a MIME type at some point when they are initialized?
