P: Support for HEIC file format (Windows)

ADOBE, SHAME SHAME SHAME

New update today... still no support - this is really bad news... My workflow includes files taken with the iPhone too, and heic format is the way to go as it's so much smaller....

284 / 39. Happy Friday everyone!

Hey Ken, yeah that's funny actually I ran into the same fix through trial and error a couple months ago. No idea why it works but you are right, if you go to change the capture time under the Metadata tab and hit "change all" without actually entering in any changes, this somehow locks in the digitized time stamp and validates it. It does work but it's time consuming and I can't help but feel like I am babysitting LR every time I make an import from my iPhone. 

And to complicate this even more, I am now seeing that LR doesn't support the HEVC video codec for MOV files from iOS 11 either. At least with the still images I can have those converted to JPEG's (Syncios does this automatically on Windows 10) and import them with their correct time stamps and get them archived. Videos are a bit more problematic as I cannot find a program that will retain their correct capture time after converting them to the standard h.264 MPEG-4 container that LR can read. The capture date is either stamped to the day the converted file was created (Handbrake), or reels it back to January 1st, 1904!! (WinX HD Converter). I'm pretty sure they didn't have iPhones back then!

So maybe someone has some ideas on what to do about that...

As for the Exif Tool thing, I don't have any experience using commands like this, Dmitry would you be able to give steps on how to do this using  the command function on Windows 10?

I was just on the phone with Adobe customer support for over an hour. They didn't even know what I was talking about with any of this HEIC/HEVC business. I had to run through the gauntlet of their protocols step by step and in the end they just gave me a case number and said they would call me back. All I wanted was to hear them say "Sorry about the inconvenience, we know that a lot of our customers use an iPhone and want to archive their visual media using Apple's new formats. We are working on providing support for this and appreciate your patience." I would be like, OK. COOL. THANK YOU. And no big deal I'll just stash the files in a folder for now and wait until I can import them later. But they won't say a word about it. Unbelievable. I am seriously considering switching to Luminar and am eagerly awaiting their Digital Asset Management module with high hopes.

I use exiftool as workaround for the issue with creation date in the Lightroom that Adobe doesn't fix for many years. They hate their customers and hate them a lot. They don't fix any popular issues at all.

macOS commands to fix the the problem with creation date:
exiftool -GPSDateStamp= -GPSTimeStamp= ./*.*
rm ./*_original

Merging with relevant bug report.

Please reference the new conversation here: Lightroom Classic: Support for HEIC file format (merging)

Hi Dave,

Not sure if this will help your time/date problem, but I had a similar issue with DNGs shot on the iphone using the Lightroom app ... they would appear with the wrong time/date stamp.

In that case, it can be fixed by selecting them all, going to "change capture time", *NOT* changing anything, and just hitting ok. It fixes it for me.

My hypothesis: there must be two "date/time created" metadata fields for some reason, but we can only see one. Lightroom seems to sort by the "hidden" one, which obviously can sometimes be not the actual time shot, but some other kind of time stamp (e.g. maybe it's file created date, which is the date LR on the desktop first saw it come into the catalog. Who knows. Annoying though.). Changing the time/date in LR (but not really changing it...) must write out the actual date again to both fields, I am guessing.

Ken

I'm in the middle of a major catalog re-build and am just now finding out about all this. I've been working for weeks trying to fix my archive because of an EXIF dating error caused during imports from my iPhone going directly into Lightroom. It caused all the videos to be dated seven hours behind their actual capture date, and many of the photos to have an entirely wrong capture date altogether, putting them into the wrong dated folder on my local drive. Total chaos. I tried talking to Adobe, reading everything I could find online, until finally realizing that I am just going to have to go back to every photo and video one at a time and re-enter everything manually. All because Adobe wouldn't invest their time and resources into fixing this issue with iPhone imports.

What I'm saying is that for some people its nothing new to see that Apple and Adobe are not playing along as well as they should be, and I see here that I am not alone with feeling like I am at a crossroads with Adobe entirely. 

What I would like to know are people's thoughts on continued iPhone imports into LR classic using the compressed JPEG's (lame I know) with the intention of switching out those images with HEIC's in the future. How would you do this? Like really, if you think you have a clever way of doing it I think that would be helpful here. I do what a lot of users do, which is import my images into a dated file structure with dated folders, and rename all my images upon import using a reverse date YYYYMMDD etc etc file naming system. So assuming that you stashed away all your HEIC's together in one place, which all have the native iPhone IMG_#### file names, how in the heck would you make the switch? 

In other words, it would be great if Adobe would not only listen to their loyal base LR archivists and roll out the red carpet for HEIC ASAP, but also come up with a way to bridge the imported iPhone JPEGs to their HEIC counterparts stored off catalog. Is this possible? Is there a better way? Am going crazy lol?

277 / 46. Happy Friday everyone!

Forking to HEVC topic to make sure your votes count there too: https://feedback.photoshop.com/photoshop_family/topics/hevc-support-for-lightroom-cc-mac