P: Please support HEVC (H.265) video support for Windows

Still waiting. No development at all?

For those of you who have needed to use your HECV iPhone videos asap, is there any alternative to importing with a different program, then converting to .mpg4 (or something like that), and then importing to Lightroom?

I'm wondering how any adobe employee with iPhones manage there videos?  Surely they must be frustrated as us!  

I'm not sure what could be the possible delay here....  Help us love your product!

Please adobe it's almost 2019

7.5 adds HEIC support according to release notes

Oh and just to add- if you create copies of an image file with metadata, the developer decides what metadata (if any) to copy to the new file.

If anyone is interested, I can explain some of the technical underpinning with keywords.

Most image file formats have reserved space for metadata, which is data about the file (keywords, ratings, develop settings, copyright, and so on.) Some formats, like RAW files, typically have a linked sidecar file which goes with the image and contains that metadata.

A number of different "namespaces" are defined to store metadata, each with specific fields and formatting required. These namespaces can overlap so that metadata is often duplicated inside a file.

Keywords can be stored in the "DC" namespace with a "Subject" tag but also in the (apparently undocumented) "LR" namespace with a "hierarchicalSubject" tag.

Ideally, keywords would be saved to both namespaces in, say, a JPEG file. Most graphics software reads the DC namespace.

I've written some scripts for Bridge to assign keywords and I write keywords to both namespaces. I don't know how mobile apps or Lightroom CC operate but presumably, using both namespaces would mean that keywords were truly portable.

Note that metadata can be written to files AND/OR to a catalog like Lightroom uses. If files are not updated and changes are only written to a catalog, its up to the developers to export that data as needed.

If you run File Info on an image using Photoshop or Bridge and look at the Raw Data, you'll be able to see the structure of the metadata and what is present or not.

Finally, there are both third-party programs such as EXIFTool and add-ons for Adobe products that let you work in depth with metadata including keywords.

> Are you able to point me to a place on the Adobe site where the main differences, particularly differences in functionality, between Lr Classic and Lr CC are explained? 

clarijoh, not the Adobe site, but this might help (and Adobe have been linking to it)

https://www.lightroomqueen.com/lightroom-cc-vs-classic-features/

> 3. I am not ready to give up control of having a (local) copy and backups of my images. Assuming I have enough space available in the Adobe cloud, how do I make sure I have at least a copy of the originals somewhere else?

In LRCC, you'd check the "store a copy of all originals locally" checkbox in Preferences, and you could use backup software to create additional disconnected backups of that originals folder too.

> 4. Part of my workflow includes my iPhone. Is there a document somewhere that details the workflow of getting my iPhone images into LR CC, while also using LR Classic, and consequently getting a copy into LR Classic? Or is the idea from Adobe that you are either exclusive LR CC or exclusive LR Classic?

I haven't come across any detailed Adobe documentation, but in case it helps, the Cloud Sync chapter of my LR Classic Missing FAQ book goes into the nitty gritty of getting the cloud to play nicely with Classic and the pitfalls to look out for. The mobile apps themselves are detailed in my LRCC Edit Like a Pro book, but you'll like get the gist of those.

Barry,

Thank you for your responses. I am also struggling with my workflow using LR CC. There are many struggles that I am facing, and haven't yet found the kind of information I need to be able to switch to LR CC.

1. I am struggling with the limited space that is available in LR CC. Due to the limited space I cannot move to LR CC completely. But I haven't yet found a methodology that works when mixing LR CC and LR Classic.
2. I have more than enough cloud space available already. Even if I was able to purchase more cloud space with Adobe, I am not ready to pay yet again for space that I already have available. Could it be possible to use my dropbox space or iCloud space instead of the Adobe cloud space?
3. I am not ready to give up control of having a (local) copy and backups of my images. Assuming I have enough space available in the Adobe cloud, how do I make sure I have at least a copy of the originals somewhere else?
4. Part of my workflow includes my iPhone. Is there a document somewhere that details the workflow of getting my iPhone images into LR CC, while also using LR Classic, and consequently getting a copy into LR Classic? Or is the idea from Adobe that you are either exclusive LR CC or exclusive LR Classic?

I look forward to your response and ideas.

Kind Regards,
Jean-Marc

Barry,

I do appreciate your prompt response. I will look forward patiently for the HEVC support.

Thanks also for your explanation regarding the differences in syncing of Keywords between Lr CC and Lr Classic. 

It would be helpful if something could be added as a pop up warning in LR CC when [first] using Keywords warning that they will not sync with Lr Classic. It would have saved me [and judging from comments on the web, many others] significant hours spent in adding keywords. 

Are you able to point me to a place on the Adobe site where the main differences, particularly differences in functionality, between Lr Classic and Lr CC are explained?

Hopefully this would help me as I admit I am struggling to find a satisfactory and robust workflow from Lr CC to Lr Classic, particularly one that uses an iPad on the road as the primary device for collecting and doing the initial input on photos both from my cameras and iPhone. 

Having left my MacBook Pro at home this trip, it was a little frustrating to find that what I was seeing on my iPad [both in Videos and Keywords] did not reflect what was uploaded by the cloud to my Mac. 

Despite my current frustrations I do appreciate all the work that has gone into Lightroom over the years, and I hope that this current bump in my perception is soon gone, so I can go back to my once strong affection and support of Lightroom.