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...

Tags: Photoshop Lightroom

Similar Questions

Maybe you are looking for