Skip to main content
Adobe Photoshop Family
jack_donaghy_7194331

4 Messages

 • 

318 Points

Fri, Apr 24, 2015 2:59 AM

In progress

Lightroom CC: File handling much slower

I'm having an issue with Lightroom CC being very slow at file handling. In Lightroom 5 I could move files from one folder to another on the same drive very quickly (almost instantly, never more than a few seconds), but in Lightroom CC I'm currently moving 400 CR2 files to a different folder and it's taken 10 minutes. This is on a Retina MacBook Pro with an SSD.

Also, the way Lightroom CC converts to DNG seems to be different. Normally when I import files I choose to convert to DNG in the Import dialogue. Normally in Lightroom 5 I ended up with a folder full of DNG files. However, in Lightroom CC I seem to get a folder of CR2 files which are then converted to DNG. I tried moving these files (from within Lightroom) while this process was going on and Lightroom got very confused and around 25% of my files could no longer be found by Lightroom (they were still on the disk, but with "DNG" extensions as opposed to the "CR2" which Lightroom seemed to be expecting, even though it had just converted them!).

Overall, this has slowed my import workflow down hugely. I used to Import as DNG, move my files around and boom, done. Now I need to import as CR2, then move the files into the right folder (which takes at least 100x longer now), and then convert to DNG. Not good!

Problems

 • 

Updated 

4 years ago

0

35

Responses

Official Solution

venkatesh_penjuri

56 Messages

 • 

1.1K Points

4 years ago

Hi Tyron,

Thank you for reporting. We will look into this. 

- Venkatesh

0

Wolf_Eilers

51 Messages

 • 

2.2K Points

5 years ago

Lighroom 6/CC has changed it's import method when converting to DNG. The raw files (CR2 in your case) are copied as fast as possible and then converted to DNG in the background. Don't touch the files in the OS directory while this is happening!

I don't understand your workflow in the last paragraph. When you move files do you mean moving within Lightroom or within the OS?

1

0

jack_donaghy_7194331

4 Messages

 • 

318 Points

That's interesting. I suppose I can see the advantage of splitting up the import and the conversion process for some people.

I'm not talking about moving the files using the OS file manager, I'm exclusively moving files within Lightroom. Essentially, I work at a nightclub, and so a lot of my photoshoots will be spread over two days (as I'll be working from, say, 11pm one day through to 2am the next morning). I normally just import by date and then move the files (inside Lightroom) from the later date into the folder of the first date just to keep everything together. I found that if I did this while Lightroom was converting to DNG, instead of queuing the process and doing the move once the conversion was complete, it started doing both at the same time and that seemed to result in LR losing track of a bunch of files because it was expecting the wrong file extension.

Like

5 years ago

0

jason_crowder

3 Messages

 • 

102 Points

5 years ago

The bottom line is this "new and improved" way of doing things is much slower.

The old 5.x way simply read the CR2 file off the memory card and then wrote the file back to the hard drive in DNG format. This required only one hard drive write per file.

The new method reads the CR2 file from the memory card then writes the CR2 file to the hard drive and then reads the CR2 file from the hard drive and then writes it to the hard drive again in DNG format and then deletes the original CR2 file from the hard drive. This now requires two hard drive file writes and one delete process per file.

How can anybody think this new way is faster than the old way? This slows down the import process tremendously. Importing and converting a card full of raw files now takes 3 times as long.

3

denni_russel

44 Messages

 • 

672 Points

Exactly. If we wanted to do it this way, we would have simply imported the CR2s then converted to DNG once in the catalogue.

Like

5 years ago

0

louann_brizendine

1 Message

 • 

60 Points

Does the Adobe company expect to survive with this poor engineering team it seems they have? This new Lightroom CC handling of the CR2 files, hard drive twice, DNG copy system must never have been beta tested or quality controlled. At my company someone on this engineering team would have been fired. We, your customers, deserve better.

Like

5 years ago

0

peter_todd_7321806

3 Messages

 • 

150 Points

With Time Machine and similar, there will not only be the issue of redundant writes to the main storage mentioned by others, but also a very significant bloating of backup storage if it makes a habit of not getting 'round to doing the conversion before a backup kicks in.

I'm trying to refrain from ranting too much here... hope the team manage to shape up a bit better; the software is barely functional for me in its current state (problems far beyond somewhat sluggish file handling). Most things I try to do (e.g., export one photo) seem to stand a significant risk of bringing up a progress bar that either doesn't move at all, or goes a certain way before stopping dead...

Like

5 years ago

bobaskey

9 Messages

 • 

140 Points

5 years ago

I am seeing the same sluggish behavior when importing raw files to DNG. Three times longer does not seem to be a stretch. I also find that moving from one image to the next (in develop) to be just as slow as before. Rendering 1:1 previews does not seem to help. I initially tested with and without the GPU option, and did not see a difference.

I have a gone through all of the standard performance guidelines and have not improved anything. I do need to try deleting the preferences file and perhaps removing my color calibration software and it's profile.

I have a 4GHZ 8 core AMD cpu, and 16 gig of memory, two SSD hard drives. What more can I do?

0

0

eric_burlet

68 Messages

 • 

1.4K Points

5 years ago

Well, we've been doing some benchmarks here in France and for me for instance, it appears that LR CC is 30% slower to import files in t eh catalog, 18% slower to render the 1:1 previews and 40% faster to export to jpeg.

Not the speed breakthrough we were expecting according to Adobe announcement...

0

0

john_h_seidel

2 Messages

 • 

70 Points

5 years ago

With my 13" Macbook Air, general slowness until I turned OFF gpu acceleration. I'm not sure if the speed-up I've experienced in various processing areas since turning the graphics acceleration off is throughout every part of Lightroom. I'm guessing that the speed improvement Adobe claims is only in machines with a separate, speedy graphics card. (Preferences > performance > Use Graphics Processor. Uncheck the box)

0

0

bobaskey

9 Messages

 • 

140 Points

5 years ago

I have yet to try importing with the GPU acceleration turned off. I turned it off a couple of days ago and have not noticed much difference. I suspect that while my video card qualifies it is probably slower than my CPU. Supposedly the GPU is only used while in the Develop module, but perhaps there is some overhead with it turned on that slows everything down.

This weekend I will try some different things, such as moving the catalog and camera raw cache to a different drive, trying different options for rendering image previews, anything I can think of.

A few people are using a RAM Disk to store the catalog and it works well for them, but is there any advantage over an SSD?

0

0

sarah_dugan_7210579

2 Messages

 • 

70 Points

5 years ago

import speed is so much slower since new Lightroom cc from Lightroom 5. I too choose to copy as DNG and the "copy to new location, import, then Convert to DNG" has my MacBook Pro fan working overtime. I'm not happy-hoping there is an adjustment made when enough users voice their dissatisfaction with the slow down.

0

0

_ystein_mehus

5 Messages

 • 

168 Points

5 years ago

Much slower in CC/6.

0

0

bobaskey

9 Messages

 • 

140 Points

5 years ago

I got the first update which seems to have helped with some issues. I still have GPU acceleration turned off. Changing to the next image seems snappier. I have not done an import yet, but the export that I did last night seemed to take much longer than normal. I really don't have all day to wait on photos to import, and it can be terribly inconvenient to wait overnight for a few hundred images to come in so that I can work on them. My 4 GHZ, 8 core system, with 16gig of ram is spinning up the fans to full speed and the Windows resource monitor shows all the cores maxed out. BTW, with that running only 6 gig of ram is being used.

0

0

mick_gardner_6331169

1 Message

 • 

60 Points

5 years ago

Since the upgrade to Lightroom CC, the convert to DNG has become ridiculously slow. I've resorted to using the Adobe DNG Conversion utility to convert my NEFs to DNGs & then I inport these into Lightroom. A work-around but hardly satisfactory. I hope Adobe listen to the comments in this forum & fix what is a fundamental failure.
Also, Lightroom won't use my GPU - Ok it's 4 years old but the drivers are up to date. I can't be the only person using a 4 year old PC.

1

0

jason_crowder

3 Messages

 • 

102 Points

I was thinking about using the DNG Conversion Utility as a workaround, but I hadn't gotten around to it. I should be able to point the Conversion utility at the raw files on my SD card and have the output of the conversion be my destination folder on the hard drive. Seems like it would be faster.

With regards to the GPU issue. I had the same problem with my AMD Radeon HD6850 you until I read in the forums that the solution was to downgrade my AMD Graphics driver to a prior version, version 14.4. This caused Lightroom to be able to use my GPU. You might want to check out this discussion: https://forums.adobe.com/thread/1822782 for more info.

Like

5 years ago

0

john_h_seidel

2 Messages

 • 

70 Points

5 years ago

https://forums.adobe.com/thread/1828580
This clarifies where any potential speed-up should happen. There are bits of useful information further down the page as well.
Info. here as well. http://www.diyphotography.net/adobes-...

0

0

adam_fairclough

3 Messages

 • 

80 Points

5 years ago

I've noticed the same problem with the most recent batches of images I've been trying to convert to DNG

For me the solution was to pause the face detection indexing, which seems to be indexing every photo i've ever taken.

15 seconds after I paused it , Lightroom was converting one CR2 file every second or so.

0

0

denni_russel

44 Messages

 • 

672 Points

5 years ago

I've been looking through the various LR CC/6 'performance issue' threads on the Adobe forums and there seems to be a heck of a lot of people experiencing the same problems. We're dealing with both Macs and PCs, slow to top of the line CPUs, 4-32 gig RAM allocations, varying and apparently supported GPUs, SSD and traditional HDs, GPU acceleration both turned on and off...

Here's my question: WHERE THE HECK IS ADOBE IN COMMENTING ON THIS? We vent in these forums and are relieved to see these problems are not happening in isolation, and yet we have no evidence that Adobe is even paying attention to us.

I've put the problem directly to them and have not heard anything back.

4

0

lightroomqueen

Champion

 • 

5.8K Messages

 • 

102.2K Points

That would suggest they're busy scrambling to figure out what's going on.

Like

5 years ago

0

adam_fairclough

3 Messages

 • 

80 Points

I solved it by pausing facial recognition indexing

Like

5 years ago

0

denni_russel

44 Messages

 • 

672 Points

I hope so :). You never know with adobe though

Like

5 years ago

0

denni_russel

44 Messages

 • 

672 Points

I've paused facial reignition too. And as for Victoria's comment, unfortunately after all these years dealing with adobe, I think we all know they tend to avoid uncomfortable issues for a year or more.

Like

5 years ago

0

robert_greatrix_7220828

1 Message

 • 

60 Points

5 years ago

I would be interested in hearing if others are experiencing issues with LR hanging up. It seems I have to use force quit way too often. And I agree import has become incredibly slow. It would seem this product should have been Beta tested more thoroughly.

0

0

Helpful Widget