Here's me staying on macOS 10.14 to avoid all the bugs in 10.15![]()
Article says it affects everything from 10.14.6. Sorry.
Here's me staying on macOS 10.14 to avoid all the bugs in 10.15![]()
Well, I posed it as a question, not a theory. Here's another question: Have you tested whether this is actually limited to Image Capture? Has anyone compared the files and file sizes, of a photo taken on an iPhone, then synced (for many people automatically) to iCloud Photos, and in turn synced via iCloud Photos to a Mac? Has anyone compared the 3 instances of a photo synced in the various ways Apple does? Apple does charge a premium for storage in iCloud and on devices - so I simply asked the question. I'm happy if I'm wrong - but the question is legit.This is an unfounded conspiracy theory. This bug affects images imported to a Mac manually via the Image Capture app, not images saved in iCloud Photo Library. It's not a widespread workflow for people- most folks just let their device sync photos through the Photos app.
Is it a bug in the human psyche that many people cannot accept randomness ('**** happens') and always have to find malicious intent behind anything undesirable? Or is it a feature that lets them feel superior for 'having figured things out'?Is it possible this is more than just a "bug"? Apple makes a LOT of money from services including iCloud storage fees, and by inflating photo file sizes, more people would be nagged to upgrade their iCloud storage from the initial free 5GB, to a paid tier, to accomodate a larger iCloud Photo Library. There is potential financial motive here - anyone with the know how should look carefully at all files stored in iCloud to see if there is any similar artificial inflation of file size. It reminds me of the Wells Fargo scandal where staff were creating extra accounts in customer names to inflate their numbers...
Which came first? Photos.app or HEIF?
Therefore, if I insult you in the form of a question, that's fine then?Well, I posed it as a question, not a theory.
I don't understand, why a workaround is preventing iOS from shooting in HEIF. It's not the problem in HEIF, but in conversion. So if you work only with HEIF files, it should be fine, right?
Had problems with HEIF or HEIC since day one. People sharing photos with me in this format on Dropbox or Box were not viewable on other iOS devices or older macOS desktops. Instructed people to turn off this format.
Question. How does this affect video recordings in this format?
iCloud 50Gb $1 Microsoft OneDrive 100Gb $2 Google Cloud 100Gb $2
iCloud 200Gb $3 Google Cloud 200Gb $3 Microsoft OneDrive 1Tb $7
iCloud 2Tb $10 Google Cloud 2Tb $10 Dropbox 2Tb $10 Microsoft OneDrive Unlimited $10 (as part of Office 365 subscriptions)
Apple's iCloud is pretty competitive compared to some of the other large providers for consumers. In addition iCloud offers functionality to Apple users which the other do not.
The problem is, nothing is compatible with HEIF (or HEVC). I get handed a lot of iPhone stuff at work and need to xcode them to JPG or DNX.
Have you tried it on a Mac, as a comparison?I don't know if it's related to the bug reported here, but there is this bug on iOS/iPadOS:
I select three photos on the Files app:
- Photo 1.HEIC: 1.1 MB
- Photo 2.HEIC: 0.8 MB
- Photo 3.HEIC: 0.8 MB
Total: 2.7 MB
Then, still on the Files app, I create a PDF from the selected photos by:
- clicking "More" then "Create PDF"
or
- clicking "Share", then "Print", then zoom in with two fingers, then click the Share button, then "Save to Files"
I get a 38.1 MB file!
And with pages in the wrong order: 2, 1, 3!
Nice!😩
No. The solution is to keep using them, as they're the future and offer better functionality, while jpg (while still used) is legacy. See others posts above as to why.And the solution is don't shoot in HEIF or HEVCThis is a non-issue, folks.
I selected the three photo files on (macOS Catalina 10.15.4) Finder, then right clicked on the trackpad, then "Quick Actions ---> Create PDF".Have you tried it on a Mac, as a comparison?
If the same thing (or near-same thing) happens on there, then it may be an inefficiency of printing straight to PDF format (unless you make the images smaller first, they're likely still very large resolution, perhaps?).
Have you seen Apple's prices for SSD upgrades recently? It's not just about iCloud. I smell some class action lawsuits coming.This is an unfounded conspiracy theory. This bug affects images imported to a Mac manually via the Image Capture app, not images saved in iCloud Photo Library. It's not a widespread workflow for people- most folks just let their device sync photos through the Photos app.
This is an unfounded conspiracy theory. This bug affects images imported to a Mac manually via the Image Capture app, not images saved in iCloud Photo Library. It's not a widespread workflow for people- most folks just let their device sync photos through the Photos app.
But if this "bug" artificially makes JPG files far larger, suddenly when taken into consideration, HEIC/HEIF doesn't save close to as much disk space as claimed. And therefore the benefits to using a new and largely incompatible image format are lessened.This is an unfounded conspiracy theory. This bug affects images imported to a Mac manually via the Image Capture app, not images saved in iCloud Photo Library. It's not a widespread workflow for people- most folks just let their device sync photos through the Photos app.
How many class action suits have you been the target of after having made a mistake.Have you seen Apple's prices for SSD upgrades recently? It's not just about iCloud. I smell some class action lawsuits coming.
Conversely, given human nature and it's best friend: greed, I'm a VERY big fan of "trust, but verify".Bingo. It's seems some people can't be at peace and try hard to find something to get a case of the shakes about.
That's one way of looking at it.Is it a bug in the human psyche that many people cannot accept randomness ('**** happens') and always have to find malicious intent behind anything undesirable? Or is it a feature that lets them feel superior for 'having figured things out'?
Three problems with this:Today, we're hearing that the bug in macOS 10.14.6 and later is a lot more extensive than was initially believed.
NeoFinder developer Norbert Doerner, who originally discovered the bug, informed MacRumors.
NeoFinder is itself being updated on Monday to include a tool that can find and eliminate the unwanted data in JPG files. NeoFinder for Mac costs $39.99 and a free trial is available to download on the developers' website.
Apple does charge a premium for storage in iCloud and on devices - [...]
I am all for double-checking. But pure speculation based on that human bug/feature doesn't really add anything. It rather represents FUD and is the same method actual misinformation campaigns employ (like Russia did after rebels supported by them shot down a passenger aircraft over Ukraine, flooding the airwaves with all kinds of wild theories to create the impression that it is impossible to know the truth, in that case the Russian population as well as the Russian-speaking population in neighbouring countries were the main target).That's one way of looking at it.
Personally, I'm glad there's "those" people out there double-checking to make sure we're ACTUALLY good to go, and not just HOPING we are.
I mean, Apple DID get caught slowing down older devices, so this doesn't seem so far-fetched.
A company has one goal: make money. Whether or not it's done ethically or responsibly is secondary, which is why the SEC, the FBI, and other government agencies stay busy putting white-collar criminals in their place.
No, this is not the same thing. At all. Converting any 12 megapixel image to a PDF will result in exactly the same thing on any platform (iOS, Windows, Mac) unless you create the PDF with proper image compression settings and other settings that you’ll need to customize with either Preview or Adobe Acrobat DC/Pro or something similar.I selected the three photo files on (macOS Catalina 10.15.4) Finder, then right clicked on the trackpad, then "Quick Actions ---> Create PDF".
The pdf created has 38 MB.
But even worse than the huge size of the pdf: there are blank spaces in between the photos on the pdf (maybe to fit to the A4 format?), this makes the pdf unusable.
When I want to create a pdf from selected photos, I just import the photos to the Scanbot app on iOS/iPadOS.
I can't rely on Apple's Files or Finder on this!
EDIT: at least the photos on the pdf created on Finder are in the right order: 1, 2, 3!