I guess I'm getting old. This CompuClever is one of the sleaziest
programs I've come across. Not only is the main window
mainly a salespitch but it installed a service and tried to send
out spyware. When I killed the process (with the program closed)
it was restarted! In other words, this thing tries to run automatically
as a service, all the time, calling home without asking.
Just tried several things. So far, "UltraFileOpener" from
Compuclever is the only thing that works. The program
is as dumb as the name. It tells me I need to buy it to
get all functionality, but doesn't explain. HEIC files are
opened but in a window infested with ads and prompts.
Why has it become so hard to just find out what a
program does, where it will run, and what the terms are?
Does anyone know a better, simple converter/viewer for
HEIC? I don't want online converters. Just a simple program,
or a library I can use to make my own converter.
"VanguardLH" <V@nguard.LH> wrote
|
| https://backlightblog.com/iphone-heic-to-jpg
|
| HEIC is an Apple file format generated under iOS, but only starting with
| iOS 11 released September 2019, so it's relatively new. Obviously this
| was long after Windows XP got released (2009), and long after Windows XP
| was discontinued (2014)
|
I know all this, thanks. What I'm hoping to find is a program
of DLL that does the job on XP. I have a possibility, of a libheif
compile that's XP-compatible. It also uses CDECL calls and I'd
need to adapt from C++. That might all be doable, but I don't
want to put the work into it unless I'm pretty sure that I can
get it to work and that it will work on XP.
The format is not a problem. It's just math. The problem is
that most of the people writing this stuff don't care about
backward compatibility. They don't have to use API functions
that are not on XP, or a Visual Studio version that doesn't
support pre-7, but they just don't care. In many cases
they really don't care about Windows. They just like to tinker
with low-level code.
The other problem with that is that there are seldom docs.
There might be a few sample snippets and an .h file. That's
typically pretty much it.
Got a sample .heic file that I could try? I could test using VLC, but
that would be under Windows 10 Home x64. If VLC couldn't support the
file on Win10, it won't under WinXP. However, if it does work on Win10,
it might work back on WinXP.
VanguardLH wrote:
Got a sample .heic file that I could try? I could test using VLC, but
that would be under Windows 10 Home x64. If VLC couldn't support the
file on Win10, it won't under WinXP. However, if it does work on Win10,
it might work back on WinXP.
The one in my collection is from here. On one of the tools I tried,
only the one image came out of it, and no message indicated there
were two frames. Some samples have as many as 10-20 frames (as if
snipped from a video). It really is a stupid/crazyass format.
https://github.com/strukturag/libheif/tree/master/examples
example.avif add AVIF example image <=== cannot open so far
Size: 113,604 bytes (110 KiB)
SHA1: 59D7ED8581E9AAFBC11E3DEF77AFAB54C246CEB3
example.heic Add example image from c492381
Size: 718114 bytes (701 KiB) <=== there are *two* images
SHA1: C1E69214F692DBF06A40A8D1AFD2CF7D12831DDB in here
It's the mystery meat of teh Internets.
[Picture]
https://i.postimg.cc/k5vsfTP9/example-heic.gif
When you get it open, examine the image quality...
"Paul" <nospam@needed.invalid> wrote
| were two frames. Some samples have as many as 10-20 frames (as if
| snipped from a video). It really is a stupid/crazyass format.
|
If I've got the story straight, the format specs require
that versions be stored to accommodate the possibility
that photo orientation was wrong or some such... So that
people don't have to rotate the image. It seems to be basically
a format for sending photos between iPhones. Adaptable,
highly compressed, quality not important.
libheif
"Paul" <nospam@needed.invalid> wrote
| What I'm seeing, is a "directionality" to the distortions
| in the image. That's why I wanted people to look at the
| image quality, because the artifacts I'm seeing are weird.
| And not something you would expect from macroblocks (which
| might be the same vertically as horizontally, in terms
| of "having issues"). Since you're the guy with the
| endless supply of samples of this format, you can tell
| us whether average samples are like that or not.
|
:) I have 2 photos of a cellar wall. Not much to go on for
checking quality. I had also got some HEIFs awhile back
but then I forgot that I'd looked into it at that time and don't
still have them. To be honest, I really don't care very much
about quality because I'm assuming this is a crap format for
sending smaller pictures between iPhones, and a passive
aggressive way for Apple to once again say, "Well, maybe you
should have bought an iPhone."
JPG is already poor quality, in most cases. And this format
apparently manages to drop a lot more data. So I just want to
be able to see it amd maybe convert it to something usable.
I see what you mean, though. I'm looking at the image that
looks like a Dutch or French canal. There's gross distortion from some
kind of sharpening operation. There's flat color. And the lines of
the buildings are so crooked that it looks like one of Frank Gehry's "masterpieces". I wouldn't have noticed if you hadn't pointed
it out, but I see rows of windows and horizontal trim boards
that are crooked or curved. The whole image is severely degraded.
On the 4th full building from the right, with the pale green shutters,
it looks like the ground is erupting, pushing the building up in the
middle. The one to its left is the opposite, collapsing in the middle.
As I understand it there's at least one quality option when saving
to HEIC, but I assume this sample is meant to be at
least average quality. I wonder whether there's some kind of
abstraction involved, where the algorithm "guesses" how to drop
most of the data. And maybe the tree shadows fooled it into
rendering crooked houses?
"Paul" <nospam@needed.invalid> wrote
| The good news is, Cygwin has it.
I'm not sure I follow this. What wa MINGW? So you ended up
getting a Linux command line utility heif-convert to work under
cygwin? I guess that's sort of good. (Is it? :) They're no longer
supporting XP with cygwin. I'm still holding out for an XP compile
of libheif and enough docs to code to it. I'm surprised that
so few sites have old versions anymore. It used to be more
standard to be able to download older versions of things.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (3 / 13) |
Uptime: | 00:52:23 |
Calls: | 7,467 |
Calls today: | 3 |
Files: | 12,691 |
Messages: | 5,627,865 |