Am I doing something wrong or does TrueNAS/Nextcloud not support HEIC images?
I'm not super knowledgable on this topic so unsure how to fix (if possible to fix)
Thanks
If you want to be able to watch/preview the HEIC images, you can edit the available mime type for Nextcloud's Viewer. (I do this to our company's NC so customers can use viewer for PDFs and employees can get previews/thumbnails of TIFFs, AIs and PSDs. For HEIC, just go to your NC's 'apps/viewer/js/viewer-main.js' and add 'image/heic' and 'image/heic-sequence' to the mimetype list (about halfway down, I hgihly recommend using VSCode+a formatter to make finding it easier)
Ngl a lot of that went over my head but, I'll look into it, thank you
There is a Nextcloud app that can convert HEIC images in your library https://apps.nextcloud.com/apps/imageconverter
What device/ Operating System are you trying to watch the images on?
That picture is on Android but it doesn't load correctly on any device
Convert them to another format?
Like find "path" -name "*.ext" | xargs mogrify -format jpg or so.
I'd rather just have HEIC natively supported if possible
I don't even know what a heic image is.
Edit: It's a apple picture format from their cameras.
No.
It's a container for image data developed by Moving Picture Experts Group ("MPEG", try to guess what else they have created).
While there are some compatibility issues between vendors HEIC still offers a greater set of features as compared to fx JFIF (you probably know it as JPEG/JPG.
Apple was one of the early adopters (2017) and (as usual?) the industry has followed. Microsoft wants money for the codec in Windows and that's probably one of the reasons why it's not commonly used...yet.
You are missing the elephant in the room here that this format isn't royalty free and requires a license and is patented.
Same story with H.265 and AV1 in the video. AV1 is royalty free video codec while H.265 is patented so every device that transcodes or encodes to it should pay royalty fee to the patent holder, but due to the fact that H.265 predates AV1, a lot of devices still don't fully support AV1.
Also Apple are always supporting not open standards in their device making the whole interoperability a big mess. For example HLS vs Dash or Fair Play vs Widevine and the refusal of Apple to adopt AES-128 CTR to alleviate the problem with interoperability between devices. All of this because they want to extract the maximum profit from their users and lock their users.
The lightning cable was a prime example, where Apple put a small DRM chip that needs to authorize that the cable is authentic otherwise your phone won't charge. And all of this so that they can charge third party vendors royalty fees on their cables and their long standing refusal to adopt USB-C on the iPhone.
I replied to a statement about Heif being an Apple image format. It is not.
Furthermore, HEIF is something that most major mobile device vendors support. Some, like Samsung, even sets it as default on some of their devices. So the whole "Apple always supporting not open standards" is just tiresome at this point.
99.999% of all Android users are defacto locked in by Google. Yes, Android might be open but Play services are not. Google works hard to lock in Android users.
At least Apple are open and honest about locking in iOS users.
iOS and Android spend an inordinate amount of time and money on ways to increase the switching costs between the two systems. Aka they add friction to leaving their ecosystem.
My Samsung uses it for lower-storage size images lol
You can set the camera to store the pictures as JPEG. I am happy with JPEG for my holiday photos. Just check that you have the best quality setting since JPEG uses lossy compression.
While HEIF is not the doomsday thing some describes it as, it currently is somewhat problematic.
There are for example problems, originating in differences in implementation between different hardware vendors, with 10-bit and HDR.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!