Previews.lrdata catalog Lightroom mac <>- pc

Similar Questions

• Should I back up the package of Previews.lrdata?

  I use LR CC on a Mac.

  Is it necessary to save the packages "Lightroom Catalog Previews.lrdata" and "Lightroom Catalog Previews.lrdata Smart? I use a service of online backup, as well as a 'Time Machine' and 'CC Clone' backup. I would like to limit the costs of downloading data, as well as the disk space on my local backups.

  I guess that these files would be just rebuilt, if they disappeared?

  Thank you

  David

  You are correct David. No need to back up. They can be generated at any time.

• Delete "Lightroom 5 catalog Previews.lrdata Smart?

  My Lightroom folder has a 2.28 GB "Lightroom 5 catalog Previews.lrdata" file and a 10.01 GB file called "Lightroom 5 catalog Smart Previews.lrdata."

  "Lightroom 5 catalog Previews.lrdata" file was created on 09/02/13 and amended on 20-11-14.

  "5 Smart Previews.lrdata Lightroom Catalog" file was created on 09/03/13 and has never been amended since this date.

  The last time that I imported the photos 11/14/14. I did no changes what whether from 20/11/14.

  Given that the "5 Lightroom Catalog Previews.lrdata Smart" file has not changed since its inception, I wonder what, if any, it is in service. Delete would free up much of the space, so I want to do if I wouldn't lose something important.

  I use PL 5.7 for Mac, in the case where that matters.

  Thanks in advance for your answers.

  ... Previews.lrdata files (not files), are required by Lightroom and should not be deleted. I mean, they peuvent be removed if they cause problems (or they are associated with a catalog obsolete..) and they can or will be recreated, but management is to minimize the storage:

  remove the 1:1 previews, and/or

  remove smart insights

  (using the Lr menu functions)

  In addition, if you reduce the size and/or quality of the standard previews (using Lr preferences), then it will be not so great...

  That said, some of us just delete these records as a quick dirty way to 'start over' preview-wise...

  SoC

• Lightroom 2 catalog previews.lrdata?

  I run into the problems of space on my C drive (hard to imagine, but I my computer has been configured before LR and iTunes).  I have moved the music from iTunes to another player, but still need to free up space.  LR use / 3GB in the following location:

  C:\Documents and Settings\ < user > \My Documents\My Pictures\Lightroom\Lightroom 2 catalog Previews.lrdata

  There are less records 0 to 9 and A to F (more a file called miniature - cache.db).  These have in turn their own subfolders.  I can't remove it the entire structure of C:\Documents and Settings\DandJ\My Documents\My Pictures\Lightroom\Lightroom 2 catalog Previews.lrdata?  What I have to change the preference to have this things overview go to another drive in the future?  My 'Camera Raw Cache Settings' points to another drive, but this doesn't seem to be the same.

  I have 3 GB + free for other things (such as defragmentation without having to move stuff back)!

  Thank you.

  You can move the "[nomcatalogue] .lrcat" (like LRCAT) file as well as the "[catlogname] Previews.lrdata" (like LRDATA) folder with Windows Explorer to a new location and that's it. Then, you can double-click on the file ".lrcat [nomcatalogue]" and LR should open with her.

  Gossweiler beat

  Switzerland

• Previews.lrdata in the file instead of the file (Win vs Mac)

  I find very useful the way OsX treats of my catalogs Previews.lrdata files, because I have easy and immediate access to their size and decide it is a good time to clean them or not.

  Why Windows (7) shows sub folders? In addition, it is not a way to quickly view several size of folders in Windows. You must manually check one by one by pressing Alt + Enter. It of very frustrating and slows down the process of cleaning.

  Thank you.

  I find very useful the way osx treats my catalog Previews.lrdata files, because I can have easy and immediate access to their size and decide it is a good time to clean them or not. Why Windows (7) display them as folders?

  Previews.lrdata is actually a folder on OS X and Windows, with the same structure on both platforms.

  But the OS X Finder has a concept called "package".  An application (for example LR) can declare a file extension (for example, ".lrdata") is treated specially as a package, and the Finder will by default show it as a file instead of a folder, hide the contents of the folder.  You can see the actual file of a package by double-clicking on it and view the contents of the package.

  Windows Explorer is not such a feature, but as others have already pointed out, you can get the other files for Windows browsers that provide total dimensions for the records.

• Previews.Irdata file catalog Lightroom, empty the cache memory Previews

  Previews.Irdata file catalog Lightroom, I have 2000 files in 8 GB in this folder.  Is it safe to delete?  Is there a better way to clear my cache Previews?

  Hi kurth,.

  No, you should not remove this folder because it contains previews of all the images in your Lightroom Catalog.

  If you remove this folder, Lightroom will start automatically re-create as you work on images in the catalog should be previews.

  If you want to optimize your catalog, you can refer to this article: How to improve and accelerate the performance of Photoshop Lightroom

  Kind regards

  Claes

• I have two catalogs - Lightroom called an and a single called Lighroom 5, both in the same folder (Mac). I used 5, but now use LR CC. Just the catalof error. Now, he wants to make me choose one to use. Which one? And then I delete the other?

  I used LR 5 for a year or so, but recently spent to LR CC has been since then problems. Earlier got the dreaded corrupt CC catalog error and had to leave the app. When I restarted I got a dialog box showing two catalogs in the same folder. One is called simply Lightroom and Lightroom 5. The dialog box wants me to choose an action. I suppose that the LR 5 is older, but do not want to make things worse. And, once I choose the right, how safely get rid of the bad? Thank you.

  Navigate to the folder that contains your catalogs and look at the dates. The one with the most recent date would be the one you use. However, if it is damaged, it will be difficult to recover. It would be better to replace it with your latest backup. You can double-click the file itself catalog, Lightroom will start and try to open this catalog. But if it is corrupt, there are not many things you can do.

• Cannot reduce the size of previews.lrdata

  Hi all

  My Previews.lrdata folder is 45 GB. On a 500 GB SSD (end 2013 15 "MacBook Pro retina), it is a reasonable piece.

  So I went through and used the menu option "ignore surveys 1:1..." in all the pictures that I do not expect to change again. Somewhat to my surprise, the Previews.lrdata folder did not file size of 1 byte. I used the option "optimize catalog", but that doesn't seem to do anything either.

  I prefer not to empty the cache of the preview while suppressing the Previews.lrdata, regarding the last pictures I've not edited and yet I enjoyed having to previews pre-rendered 1:1.

  I don't expect too much here? Should not be a relationship between throw me 1:1 previews and a reduction in the size of the Previews.lrdata folder?

  Thank you

  
  Nick

  ntompson wrote:

  So if I reduce the size of the standard preview for the screen resolution below, then Lightroom uses only brief (down-scales) 1:1...

  That is right.

  ntompson wrote:

  What are the downsides to this?

  No - your standard previews have been set too high before.

  ntompson wrote:

  Why have a standard preview at all?

  For reasons of performance - faster to enter/resize some smaller if he wants to.

  ntompson wrote:

  Would I better off put the standard preview to the smallest possible size?

  Lol if you do this, then Lr re - will make a brief 1:1 for fit view, even if a standard preview was already available (because it would be too small). Certainly, if the 1:1 Preview is already available, it wouldn't need the re - make, but if you are when they expire, it may not be available, and despite this, it takes more time to load/resize a larger and a smaller preview.

  ntompson wrote:

  When I do the standard preview size change in Lightroom, then does invalidate all standard previews in my catalog? Does crank through and to regenerate all the standard previews to the new size?

  No and no (but in my opinion, the user should be prompted to see if he/she would like to rebuild so size or quality changes).

  In many cases, the difference over having a frame is too small or too large a framework, will be almost (or totally) without consequence. To be honest, I'm surprised that adobe exposed this option to the user, since most users have any idea what optimum setting should be. If I were Adobe, I suppose that Lr/hand-UI would be on the bigger screen and automatically size previews accordingly. Often when I mention this, people point out that the same catalog can also be used on a laptop, review how would be more optimal, and there are other considerations double monitor.., but hey - whatever...

  PS - Lightroom creates different preview (up to) 7 sizes: from 1:1 to little thumb. When he creates a large preview (1:1 or standard), he created all the smaller previews also, in halfening size. It is very fast, and no doubt explains the reason why it will not throw a 1:1 if next (standard) would be more than half it's size (it's actually only create 6 previews in this case: 1:1 through thumb, there is no big standard preview size you specified in this case) (, or if you prefer another way of seeing things: the preview of 1:1 is your largest standard preview).

  If you want to better understand what is stored for previews, you can play with the PreviewExporter plugin I wrote (free) - it allows you to specify at what level (1-7) to preview you want to export, and if you enable verbose logging will provide info on what was available, and what level of preview has been exported. Here is an excerpt of "post-process action" (export filter) UI:

  

  See you soon,.

  Rob

• LR previews.lrdata files

  I understand that the LRCAT is the main file for a catalog. In the LR4, the program generates a file preview.lrdata containing thousands of new files and take a lot of hard disk space and a lot of time when the readers of synchronization.

  If I delete all the files and preview files and reopen the catalog, LR begins immediately generating these files again.

  I have something checked (as previews full size) which is originally LR do all these files? I remember this in LR3. I looked around in the prefs and catalog for a checkbox.

  Maybe there something to the size of the preview, I chose? I had the Settingst catalog at 1440/Medium/throw 1:1 after a day.  I just put it to 1024/low/throw 1:1 after a day.

  My main catalog now has 170 000 files and the LRCAT file is approximately 2.63 concerts.

  I use Alwaysync to synchronize the disks on a PC running Windows 7. All records requires more time to analyze.

  Thanks in advance,

  M Jackson

  M,

  Lightroom has always been so. The previews on Windows were (and still are) always embedded in a large folder tree.

  As the overview file can be re-created at will, you don't have to back it up. Is there a way to tell Alwaysync to ignore it when you synchronize your disks?

  HAL

• Previews.lrdata folder size

  I remember this discussion a few weeks ago, but I can't find it by searching.  Anyway, my problem, if it is indeed a problem, is that for my LR catalogs 4.1 RC previews.lrdata folder are a lot larger than the same pictures catalogued in LR 3.4.  It comes on several catalogues.  I deleted the folder previews.lrdata on the Catalog under both versions and regenerated previews, but differences remain. Any ideas as to why this is happening?

  Just to be clear on the process:

  If you had to upgrade LR4 your LR3 catalogues, everything that happens is LR4 "steals" extracts from the catalog in LR3 and renames the file found to match the name of the catalog LR4. So if you were to look at the contents of the folder catalog Lightroom immediately after the upgrade you will find the original catalog in LR3 but no associated file previews and catalog LR4 a previews file related... and because it's a simple hi-jack of the previews folder LR3 is of course the same size as the old folder to LR3.

  If you open the catalog in LR3 LR3, because no record of previews there is now a new parameter is created and (unless you ask then LR3 to rebuild previews of images again) LR3 will create standard previews that you import photos in the grid/film. In this scenario, obviously the newly created previews LR3 will be much smaller than the old previews folder that is now labeled LR4.

  I've seen a lot of posts since LR4 came out to complain about the perceived in comparison with LR3 LR4 folder size, and I think that in many cases there was a lack of knowledge about the process.

• How to synchronize the catalog between mac pro and imac?

  I recently bought a macbook pro to work on the road.

  Since I was a very big picture library (catalogue of 25 GB, + / 40000 photos), I enclose the keywords to make a nice database.

  It is a hell of a job. But with my laptop now I could kill time and I am working on my catalog everywhere. This is the big idea.

  I would like the same catalog to keep being synchronized between my imac and laptop. My Imac is still my main computer. This is attached to my NAS system and the database of photos of 6 TB.

  All the images are in a catalog. On my laptop I don't need access to this database of real images. I just want to make selections, add keywords. Is there some way this can be done easily, without paying attention to the rather, I'm working on my laptop or My Imac, to avoid disrupting the catalogues.

  When I import new images on my laptop, I make a new catalog and import/export this to my main catalog, once my files are on their place on my NAS system.

  THX

  Hi Wannesnim,

  What you describe is more or less how I work all the time. I use Dropbox to synchronize my catalog and use Smart Previews (also synced via Dropbox) to work with my images. I use a MacBook Pro on the go and a Windows machine at home. I created a video tutorial explaining how this is done:

  A cell phone catalog Lightroom - Mike Hoffman

  I hope it's useful for you.

  MIke

• Files dng catalog Lightroom 6 not supported

  After 2 days struggling with my internet connection very slow, I've finally updated OSX El Capitan JUST so I could update to Lightroom 6 so that I could import of Olympus raw files. At startup, Lightroom prompted me to update my Lightroom Catalog, but Lightroom now displays an error message whenever one of my old dng files are open. Something along the lines of "file appears not supported or damaged.

  In addition, it crashes whenever I try to import files from Olympus. so I did not win anything.

  is it possible to have another go at updating the catalog Lightroom 6, or do I just go back to Lightroom 5 and maybe forget my subscription of the CC?

  I think that this is a known problem with some devices, including your.

  Lightroom CC 2015.6 / 6.6: cannot read the X - E2 Fuji DNG files more | Community customer Photoshop family

• My Lightroom does not. It is showing the message - failed to open the Lightroom catalog called Catalog Lightroom because it is too new to be used by this version of Lightroom. You want to select a different catalog?

  My Lightroom does not. It is showing the message - failed to open the Lightroom catalog called Catalog Lightroom because it is too new to be used by this version of Lightroom. You want to select a different catalog?

  It is a catalog that you created on your computer, or coming from another computer?

  If it is one that has been created on your computer, you can search your computer to see if you have two different versions of Lightroom installed. If so, then you want to open the new version of Lightroom by double-clicking its icon, and then you should be able to open the catalog.

• PC with Lightroom 6 just installed. At the opening, it says Lightroom - opening catalog: catalog Lightroom - 2.Ircat, then a Popup comes up saying Failed Assertion and the program closes. I checked to make sure that the pictures folder is under user direc

  I have a PC with Lightroom 6 just installed. At the opening, it says Lightroom - opening catalog: catalog Lightroom - 2.Ircat, then a Popup comes up saying Failed Assertion and the program closes. I checked to make sure that the photos folder is under the directory of the user and the registry redirects to the right/directory of the user file. The catalogues are stored in a subdirectory of Lightroom in the photos subdirectory. You need to resolve without losing all the catalogs.

  Could you please try to uninstall and reinstall Lightroom once on the computer

• Try to upgrade a PES 10 catalog Lightroom CC - problem: conversion file path problem [was: upgrade Photoshop elements catalog]

  Update 20150707:

  So I think I found the reason for the problem:

  About 60% of my files in my catalog of PES 11 are converted (or probably better: "sent") to Lightroom with a double slash "/ /" in the path of the file.

  This looks like: D:/photos/ /Keep, albums, 2002, 200212 < the rest of the way is OK >...

  Lightroom complains that it cannot find the file on the disk, probably because of the double slash.

  With more than 4,000 theses error Lightroom core dumps with a buffer overflow, probably due to the large number of error messages. Cup of the catalogue of PES 11 decline little by little I managed to identify the cause.

  The problem is that my PES 11 catalog is repaired, optimized and PES 11 think that the file is in the correct location and can open and edit it.

  So what do I do to make the two programs to understand each other with their file name conventions? ... or how to get rid of the second crime "/"?

  Thank you

  Thomas

  ---

  Good afternoon

  I'm trying to upgrade a PES 10 catalog Lightroom (Lightroom details below) CC - both on Windows 8.1 (details below as well)

  There are about 30,000 photos in the catalogue of PES 10. Import runs for awhile then LR CC shows a short message that it could not import all of the photos and then it is intercepted by a Windows operating system message that indicates «Lightroom has stopped working...» »

  He has imported about 3,500 photos and converted all the photos of Collections, but also in the tree of the key.

  I tried the following:

  (in PES 11)

  • optimized and repaired the catalog
  • removed all files types that LR does not support
  • removed all media offline

  (in LR cc)

  • Tried running in different compatibility modes
  • Tried running in administrator mode
  • Temporarily disabled any antivirus software

  I run LR CC successfully with a new catalog and it behaved very well through all operations. TI ROM dumps on the conversion of this catalogue. Importing photos from the catalogue above works fine hierarchy; just that it loses the key word and obviously knows no collections.

  Is there any log file indicating the element involved the conversion?

  I have to say that I love LR after a period of three weeks of the trial, but I'm not really ready to let go hold on 90% of my data meta at this stage.

  Best

  Thomas

  System Info for LR and PSE

  ---

  Version of Lightroom: CC 2015.0.1 [1018573]

  License: Trial

  Operating system: Windows 8.1 Business Edition

  Version: 6.3 [9600]

  Application architecture: x 64

  System architecture: x 64

  Number of logical CPUs: 4

  Processor speed: 3.1 GHz

  Built-in memory: 16199,9 MB

  Real memory for Lightroom: 16199,9 MB

  Real memory used by Lightroom: 364.6 MB (2.2%)

  Virtual memory used by Lightroom: 314,3 MB

  Memory cache size: 185.7 MB

  Maximum thread count used by Camera Raw: 4

  Camera Raw SIMD optimization: SSE2, AVX, AVX2

  System DPI setting: 96 DPI

  Composition of the Bureau enabled: Yes

  Exhibition: 1) 1920 x 1200, 2) 1920 x 1200

  Entry types: Multitouch: no, built-in touch: No, built-in pen: no, touch external: No, external pen: no keyboard: No.

  Graphic processor News:

  Check the supported OpenGL: failed

  Vendor: Intel

  Version: 3.3.0 - Build 10.18.10.3345

  Renderer: Intel(r) HD Graphics 4600

  LanguageVersion: 3.30 - Build 10.18.10.3345

  The application folder: C:\Program Files\Adobe\Adobe Lightroom

  Library path: C:\Users\behreth\Pictures\Lightroom\Lightroom Catalog.lrcat

  Settings folder: C:\Users\behreth\AppData\Roaming\Adobe\Lightroom

  Plugins installed:

  (1) Behance

  (2) substantive canon Plugin

  (3) Facebook

  (4) Flickr

  (5) attachment Plugin Leica

  (6) home Plugin Nikon

  Config.LUA flags: None

  Update Kit: Adobe Camera Raw to Lightroom 6.0 9.0 (build 1014445)

  Update Toolkit: book Module 6.0 (build 1014445)

  Update Kit: develop Module 6.0 (build 1014445)

  Toolbox update: Import Module 6.0 (build 1014445)

  Updated Toolkit: library Module 6.0 (build 1014445)

  Update Kit: Card Module 6.0 (build 1014445)

  Update Toolkit: monitor Module 6.0 (build 1014445)

  Update Toolkit: print Module 6.0 (build 1014445)

  Update Toolkit: Slideshow Module 6.0 (build 1014445)

  Toolbox update: Module Web 6.0 (build 1014445)

  Update Kit: com.adobe.ag.AgNetClient 6.0 (build 1014445)

  Update Kit: com.adobe.ag.AgWFBridge 6.0 (build 1014445)

  Update Kit: com.adobe.ag.Headlights 6.0 (build 1014445)

  Update Kit: com.adobe.ag.LibraryToolkit 6.0 (build 1014445)

  Update Kit: com.adobe.ag.MultiMonitorToolkit 6.0 (build 1014445)

  Update Kit: com.adobe.ag.archiving_toolkit 6.0 (build 1014445)

  Update Kit: com.adobe.ag.bridgetalk 6.0 (build 1014445)

  Update Kit: com.adobe.ag.catalogconverters 6.0 (build 1014445)

  Update Kit: com.adobe.ag.cef_toolkit 6.0 (build 1014445)

  Update Kit: com.adobe.ag.coretech_toolkit 6.0 (build 1014445)

  Update Kit: com.adobe.ag.curculio 6.0 (build 1014445)

  Update Kit: com.adobe.ag.discburning 6.0 (build 1014445)

  Update Kit: com.adobe.ag.email 6.0 (build 1014445)

  Update Kit: com.adobe.ag.export 6.0 (build 1014445)

  Update Kit: com.adobe.ag.ftpclient 6.0 (build 1014445)

  Update Kit: com.adobe.ag.help 6.0 (build 1014445)

  Update Kit: com.adobe.ag.iac 6.0 (build 1014445)

  Update Kit: com.adobe.ag.imageanalysis 6.0 (build 1014445)

  Update Kit: com.adobe.ag.layout_module_shared 6.0 (build 1014445)

  Update Kit: com.adobe.ag.pdf_toolkit 6.0 (build 1014445)

  Update Kit: com.adobe.ag.sdk 6.0 (build 1014445)

  Update Kit: com.adobe.ag.sec 6.0 (build 1014445)

  Update Kit: com.adobe.ag.socket 6.0 (build 1014445)

  Update Kit: com.adobe.ag.store_provider 6.0 (build 1014445)

  Update Kit: com.adobe.ag.substrate 6.0 (build 1014445)

  Update Kit: com.adobe.ag.ui 6.0 (build 1014445)

  Update Kit: com.adobe.ag.video_toolkit 6.0 (build 1014445)

  Update Kit: com.adobe.ag.xml 6.0 (build 1014445)

  Update Kit: com.adobe.wichitafoundation 6.0 (build 1014445)

  Map #1: Vendor: 8086

  Feature: 412

  Subsystem: 204a 8086

  Review: 6

  Video memory: 96

  Map #2: Seller: 1414

  Device: 8 c

  Subsystem: 0

  Revision: 0

  Video memory: 0

  AudioDeviceIOBlockSize: 1024

  AudioDeviceName: Speakers (Realtek High Definition Audio)

  AudioDeviceNumberOfChannels: 2

  AudioDeviceSampleRate: 44100

  Build: not initialized

  Direct2DEnabled: false

  GPUDevice: not available

  OGLEnabled: true

  ---

  10.0.0.0 elements Organizer

  Basic version: 10.0 (20110914.m.17521)

  Language version: 10.0 (20110914.m.17521)

  Current catalog:

  Catalog name: fitt_master_backup

  Catalog location: C:\data\pse11_catalog\fitt_master_backup\

  Size of the catalog: 135, 8 MB

  Catalog Cache size: 1, 1 GB

  System:

  Name of the operating system: 2000

  Operating system Version: 6.2

  System architecture: Intel CPU Family: 6, model: 12 Stepping: 3 with MMX, SSE whole, SSE FP

  Built-in memory: 15, 8GB

  Free memory: 4, 9 GB

  I found the reason, but there is no solution...

  Comments:

  The double slash ' \ ' in the path appears to be introduced with the upgrade to PSE10. I can't say how it happened, but there were about 27,000 files connected by an access path "D:\pictures\\album\portrait\image_1.jpg".

  Fortunately, I worked with this database, as in fact all files could be catalogued, modified, opened with the editor. I checked from time to time for "Missing files" and none has been identified. After I discovered the problem during the conversion of catalogue Lr, I checked the display "File Location" and none of the files with the double slash are recognized as part of the catalog. I could import into the catalog of the "location of the folder" producing duplicates:

  'D:\pictures\\album\portrait\image_1.jpg '.

  'D:\pictures\album\portrait\image_1.jpg '.

  live happily next to each other.

  I could "move" the wrong file in the thumbnail view in its original, which corrects the incorrect path. But as my collection is well distributed on a large directory structure and there is no way to sort way "thumbnail" it would be a never-ending task.

  Here are the steps I took to fix the problem. It was not as simple as it sounds by

  now and took a lot of trial and error for weeks.

  1. I made a backup of the catalog PSE10 ("File-> backup catalog..") hard disk
  2. I have 'removed' photos from their original location, so that they could not be found (as I had a distinct data reader, I just removed the drive letter in the Windows Disk Management Console)
  3. I restored the backup PSE10 ("File-> Restore Catalog... "), choose 'new place' and placed in the root of a different drive. If you do not have a spare laptop drive, you can use the "subst q: ; I had hoped to keep the structure of the root, it is easier for the PSE10 to reconnect files later, but I can't confirm that it makes a difference.
  4. After restoring PSE10 complained (thankfully!) could not find any files (27,000) with double '-', so, unlike the situation at the beginning, I could now chose "file-> reconnect-> all missing files. He tried to find the files, but he could not find them in the area returned after searching for 5 minutes for the first file. Then I reconnected a file manually and restarted the process and after 1 h PSE10 had reconnected all files without any problems, and the images appeared as well in the 'file location' display.
  5. As I wanted my files in their original location, I "return" the files in their original location by moving them in the 'File location' view, which took another 3 hours.
  6. As I was not very confident with the whole process ensuring all files have actually been part of this process, I closed 10 PSE and "reinstalled" my original tree together file pictures of the "retired" location (step 2) after you delete the files moved PSE10.
  7. I grew up PSE10 and checked for missing files, everything was still connected.
  8. Finally I re-imported the tree of the original files 'reinstalled' together again to see if something is missed, but all files have been correctly identified as duplicates. The final step was to validate "File Location" view, where are the files appears in the tree structure tight.

  Then, I did what I wanted finally to update the catalogue of PSE10 to LR6 and it worked without any problems take images and metadata across.

  Fact.

  A plea to Adobe...

  I think it would be a great idea to publish catalogues different proprietary formats (PES / LR). This

  cannot be that difficult because you must have appropriate documentation. In this case the problem could be

  solved with double '-' setting programmatically. If you think that your customers entrust their digital

  assets on your cloud, some "opening" your end would be just one...