Lightroom new update -- another fine tuning, shame!

[jackgreen]

Lightroom, Sony A7rII, in combination with 4K monitor is not quite usable any more...

If you edited photos in Lightroom, using A7rII 40+ MP RAW files and 4K monitor (= large preview files), then you know that it is getting pretty slow.

I work usually in ca 1000-1500 photo sets. the slowest operations are:

• Importing with pre-defined develop presets, generating smart, regular and full previews
• Using the local correction brush in the develop module

I have last i7 and fast last ATI GPU, M.2 fastest SSD -- and it is still slow. This means only one thing. Adobe Lightroom code is not ready to cope A7RII files and 4K previews. They have to do something. Lightroom is not able to use multi core parallel architecture, neither GPU massive compute power (ok, some exceptions). My personal belief is that they should program it from the scratch.

Tried also ON1, but I really like the catalogue system in LR. And ON1 is too slow in cropping...

What do you think?

--
My hobby www.jackdevant.com

 

[vett93]

Are you saying the new update makes LR slower than before?

 

[NicoG]

I fully agree LR is an ashamely slow resource hog ... arg, and the worse is that it does not seem it will change one day!

C1 is much much faster ... but like you, Adobe got me with their library module! Also, in C1 I did not found a way to manually apply profiles for lens correction which I use a lot for adapted lenses (but that does not seems to bother other people as I did not found much post about it).

 

[addieleman]

C1 is much much faster ... but like you, Adobe got me with their library module! Also, in C1 I did not found a way to manually apply profiles for lens correction which I use a lot for adapted lenses (but that does not seems to bother other people as I did not found much post about it).

I have installed Capture One repeatedly and as many times didn't really start using it because of exactly that, not being able to make lens profiles by myself. The same holds for camera profiles, I've never found anything comparable for C1 to what Lightroom and Photoshop Camera Raw offer in terms of making camera profiles with a Colorchecker Chart. Too bad, I especially like the C1's ability to make local color adjustments

 

[sebbe]

C1 is much much faster ... but like you, Adobe got me with their library module! Also, in C1 I did not found a way to manually apply profiles for lens correction which I use a lot for adapted lenses (but that does not seems to bother other people as I did not found much post about it).

I have installed Capture One repeatedly and as many times didn't really start using it because of exactly that, not being able to make lens profiles by myself. The same holds for camera profiles, I've never found anything comparable for C1 to what Lightroom and Photoshop Camera Raw offer in terms of making camera profiles with a Colorchecker Chart. Too bad, I especially like the C1's ability to make local color adjustments

--
Best regards, Ad.

There is a tool called camprof, which is doing the same in C1 as the x-rite plugin in LR.

https://peterlaszlo.wordpress.com/

I don't know how good it is. But the x-rite plugin is also far away from accurate. But it looks like it is close to pleasing colors because so many use it.

As a better workaround you can profile your camera once with dcamprof or basICColor Input. Then you only need to white balance your shot. As C1 is Lut-based there is no need for seperate profiles of each color temperature or lightsource as long as it is not a very special light setting (e.g. ultraviolet lamp). For LR you can create dual-illuminant profiles which can be used the same way.

Here are four shots with different settings but the same profile. Note that all of them suffers from color haze, shadows, light reflection, flares, ... All things that would have a big influence if you would create a profile out of the shot. But when I have a look on a profile or style I like to have a look on colors under such conditions. To me the colors are still comparable and look(!) good. All shots are white balanced to A2 only.


color temperature: 6700K, flash light


color temperature: 6300, bulb (6500K) with some bulb light (2700K)


color temperature: 5200K, sunlight through a window with shadows of ambient light


color temperature: 4000K, fluorescent tubes (3000K) with some daylight and heavy color haze from the table

dcamprof (free, complicated at the beginning, very customizable):

http://www.ludd.ltu.se/~torger/dcamprof.html

basICColor Input (expensive, very easy to use and very accurate):

http://www.basiccolor.de/basiccolor-input-5-en/

If you use lenses with very different contrast, color, etc. you may create one profile for each lens-camera combination.

--
flickr

 

[Uncover]

Well, at least there is support for the new Sony 85 f1.8 lens, so I am thankful for that.

 

[jackgreen]

True, some people are happy when it's not getting slower. I would say, that it hasn't.

Company like Adobe has to understand the trends and re-engineer their software...

 

[addieleman]

There is a tool called camprof, which is doing the same in C1 as the x-rite plugin in LR.

https://peterlaszlo.wordpress.com/

I don't know how good it is. But the x-rite plugin is also far away from accurate. But it looks like it is close to pleasing colors because so many use it.

As a better workaround you can profile your camera once with dcamprof or basICColor Input. Then you only need to white balance your shot. As C1 is Lut-based there is no need for seperate profiles of each color temperature or lightsource as long as it is not a very special light setting (e.g. ultraviolet lamp). For LR you can create dual-illuminant profiles which can be used the same way.

... (deleted)

dcamprof (free, complicated at the beginning, very customizable):

http://www.ludd.ltu.se/~torger/dcamprof.html

basICColor Input (expensive, very easy to use and very accurate):

http://www.basiccolor.de/basiccolor-input-5-en/

If you use lenses with very different contrast, color, etc. you may create one profile for each lens-camera combination.

--
flickr

Thanks a lot, I'll look into all this! Don't see an installer for macOS though.

--
Best regards, Ad.

 

[mreynolds767]

For me both LR and PS are erratic.

Initial import of the raws and converting to DNG on the A7rii files takes forever, type of things where you put in the card and walk away.

Other than that I can not judge the speed of different updates/versions as every day it seems to behave differently, some days fast, some slow like molasses and others in between.

Unsure if something about my catalog causing this but the speed is all over the place for both Lightroom and Photoshop

I think users want SPEED prioritized over new features and definitely over anything to do with their new stock image roll out. Hope Adobe is listening or more people will start checking out the alternatives, I am sticking with LR & PS personally.

 

[JimKasson]

For me both LR and PS are erratic.

Initial import of the raws and converting to DNG on the A7rii files takes forever, type of things where you put in the card and walk away.

Other than that I can not judge the speed of different updates/versions as every day it seems to behave differently, some days fast, some slow like molasses and others in between.

Unsure if something about my catalog causing this but the speed is all over the place for both Lightroom and Photoshop

I think users want SPEED prioritized over new features and definitely over anything to do with their new stock image roll out. Hope Adobe is listening or more people will start checking out the alternatives, I am sticking with LR & PS personally.

If I have a lot of images, I do my initial sort with Fast Raw Viewer, and then I have far fewer images to deal with in Lr.

Jim

 

[sjazz]

As I wasn't getting good colours with LR, I switched to C1 but I missed the Library module so I tried again LR and found that the camera profiles were improved plus the use of Colorchecker helped a lot.

I don't see big problems in speed with my Mac but what drives me crazy is that every time I switch from Library to Develop, the screen goes black and I need to go back and forward until it works normally.

 

[jayvee7]

Lightroom makes very little use of the multicore and multithreaded capabilities of modern cpus for most of its core functions. The only time it really uses the full potential of the cpu is on exporting. GPU acceleration is only used in a few tasks in the Develop tab and it's possible some tasks may even be slower when gpu acceleration is used.

So basically LR has not kept up with technology and have dragged their feet when pressed to do so.

 

[alextardif]

• Importing with pre-defined develop presets, generating smart, regular and full previews
• Using the local correction brush in the develop module

Tried also ON1, but I really like the catalogue system in LR. And ON1 is too slow in cropping...

Applying predefined presets upon import is the biggest culprit in your workflow, it seems. I've no issues with importing and then doing my culling in LR library module after basic import if I choose full previews upon import. Sure, it takes... I dunno, 20-40 minutes sometimes to do this for 1,500 images but this part is manageable.

What is problematic is working with 1,500 images AFTER you've applied your edits/presets in the develop module, especially after synching this many images from your first "edit". I agree that the lag is quite infuriating and makes things like local correction brush nearly useless. This is even if you recreate full previews after your synching.

I work on a fully loaded MB Pro, eagerly awaiting the release of the new iMac or Mac Pro lineup, but it wouldn't make a difference even with the highest speced machines, as the issue is with LR architecture. Gotta keep these complaints up for Adobe to act.

--
Alex

 

[Jerry Fusselman]

For me both LR and PS are erratic.

Initial import of the raws and converting to DNG on the A7rii files takes forever, type of things where you put in the card and walk away.

Other than that I can not judge the speed of different updates/versions as every day it seems to behave differently, some days fast, some slow like molasses and others in between.

Unsure if something about my catalog causing this but the speed is all over the place for both Lightroom and Photoshop

I think users want SPEED prioritized over new features and definitely over anything to do with their new stock image roll out. Hope Adobe is listening or more people will start checking out the alternatives, I am sticking with LR & PS personally.

If I have a lot of images, I do my initial sort with Fast Raw Viewer, and then I have far fewer images to deal with in Lr.

Jim

 

[DFPanno]

For me both LR and PS are erratic.

Initial import of the raws and converting to DNG on the A7rii files takes forever, type of things where you put in the card and walk away.

Other than that I can not judge the speed of different updates/versions as every day it seems to behave differently, some days fast, some slow like molasses and others in between.

Unsure if something about my catalog causing this but the speed is all over the place for both Lightroom and Photoshop

I think users want SPEED prioritized over new features and definitely over anything to do with their new stock image roll out. Hope Adobe is listening or more people will start checking out the alternatives, I am sticking with LR & PS personally.

If I have a lot of images, I do my initial sort with Fast Raw Viewer, and then I have far fewer images to deal with in Lr.

Jim

 

[Abrak]

Lightroom, Sony A7rII, in combination with 4K monitor is not quite usable any more...

If you edited photos in Lightroom, using A7rII 40+ MP RAW files and 4K monitor (= large preview files), then you know that it is getting pretty slow.

I work usually in ca 1000-1500 photo sets. the slowest operations are:

• Importing with pre-defined develop presets, generating smart, regular and full previews
• Using the local correction brush in the develop module

I have last i7 and fast last ATI GPU, M.2 fastest SSD -- and it is still slow. This means only one thing. Adobe Lightroom code is not ready to cope A7RII files and 4K previews. They have to do something. Lightroom is not able to use multi core parallel architecture, neither GPU massive compute power (ok, some exceptions). My personal belief is that they should program it from the scratch.

Tried also ON1, but I really like the catalogue system in LR. And ON1 is too slow in cropping...

What do you think?

--
My hobby www.jackdevant.com

I think it is a big assumption to think that Adobe 'has' to do something about your problem.

Realistically I would have thought that 99% of their customers for LR are using lower pixel count cameras and 99% are doing smaller batches of photos than 1000-1500.

That makes you a pretty tiny demographic.

I would even wonder if gpu optimization makes that much sense when the vast majority of users have on board graphics.

I agree with others that a front end program would help - I use PM.

--
http://www.salintara.com
http://www.flickr.com/photos/robcoll/

 

[NicoG]

Thanks for all these suggestions. I may have to re-examine my workflow!!!

Concerning the slowness of lightroom, I think you are very patient @Abrak!

I have a 24MP camera and it is sometime slow as hell ... even for a newly create collection on a SSD with a good CPU and above 16GB of ram.

Library mode is not all that worse once previews are generated and you are not zooming/un-zooming. But browsing modified photo while in develp. mode is for exemple a bad idea.

It may affect a good amount of users, not a minority.

 

[jackgreen]

.... absolutely agreed! Photo processing is highly parallelized algorithm and should use multi-core and even GPU vast power in much better way than they du currently...