Or the third monitor. It would be nice to be able to simultaneously see two full-screen copies, one at 1:1 and one at Fit.Only thing that *might* be better if above panel could be moved to 2nd monitor. Maybe.
--
George
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Or the third monitor. It would be nice to be able to simultaneously see two full-screen copies, one at 1:1 and one at Fit.Only thing that *might* be better if above panel could be moved to 2nd monitor. Maybe.
Between the new ISO Dependant ISO presets and Auto I can process a file in 5 seconds if I need to. Auto is not always perfect every time but it is a good starting point. Often it is enough to move to the next file.Lightroom has gotten good enough that I rarely have to make the trip to Photoshop, so I can live with the occasional problems of additional files and destructive editing.Fair observation, but once you hit the Ctrl-E . . .I hate to step into the middle of a good argument, but would like to point out that everything you said couldn't be done in Lightroom is only a Ctrl-E away in Photoshop, which will do any of them in about 12 different ways each. Included with Lightroom, or vice versa.But also: in Lightroom "classic," you can't . . .
It has been quite a few years since I looked at Capture One. Are you telling me it now does everything that LR/PS does, and does it all non-destructively and faster? Hard to believe, but if so it would warrant another look.
I concur.Between the new ISO Dependant ISO presets and Auto I can process a file in 5 seconds if I need to. Auto is not always perfect every time but it is a good starting point. Often it is enough to move to the next file.
I guess that is why they are wasting time and money putting in these great upgrades into LrC. This will take you a while.I don't know what you're looking at, but "new" Lightroom (you know, the one for the cloud), introduced in 2017, has a substantially different UI than "classic."Reilly Diefenbach wrote:That "classic" interface is so great that Adobe redesigned it entirely in 2017,
No, they didn't. It's been pretty much the same all the way back to 2009's version 3 at least. Before that, I was using CNX2, a truly dreadful interface if ever there was one.
That's what I mean when I say Adobe redesigned the "classic" UI in 2017, and called the new product "Lightroom." (And then, as I said, it took a few of the new design elements--the new curves panel, the new profile browser--and retrofitted them to "classic.")
OK boomer!What is "stanning?" The latest millennial buzzword? Is Mother English going down for an eight count again?Same thing with performance--the classic software you're stanning
In the first place, Lightroom "classic" is living on borrowed time because Adobe has another Lightroom, which they just call Lightroom, which is the only one they really ever talk about.Why? What can I not do as presently configured?was performing so well for everyone that Adobe re-wrote a new alternative product from ground up and called that new product "Lightroom."
In the end, however spectacular or unspectacular the classic may or may not be . . . doesn't really matter. It's living on borrowed time.
They added local Hue adjustments to reduce the need to go into PS. PS does these things with real layers, not fake ones. Also I couldn't care about any of these options. I'm not a professional or a portrait photographer. What I want is my telephoto lens corrections which C1 does not offer.But also: in Lightroom "classic," you can't . . .
- perform saturation or luminosity adjustments per hue on a masked layer (which you've been able to do in Capture One since 2012). At least you got local "brushed" hue skews this year. That's something.
- You still can't adjust a hue, saturation, or luminosity region you determine; or specify the breadth of a hue, saturation, or luminosity region to adjust; or specify the blend of hue, saturation, or luminosity adjustment regions with neighboring colors not adjusted (all of which you've been able to do in Capture One since 2007).
- You can't adjust the degree of change or "unification" over a specified hue, saturation, or luminosity region (which you've been able to do in Capture One since 2012).
- You can't split-tone anything other than highlight or shadow hues and saturations. (In Capture One, since 2014, you can also mix a mid-range tone and a "master" tone over the entire frame, including splits you've already specified. And you can adjust hue, saturation, and luminance on every split.)
- Because you can't do any of this globally, you can't do any of it locally or on a mask, either.
There's more. So much more. I mean, there are some really, really basic things Lightroom can't do, like
Imagine how much more versatile presets would be if you could simply adjust "how much" or "how little" of a given look you wanted, in one slider? That's the world people using "garbage" like Capture One have been living in since 2014.
- apply any preset--including any adjustment the editor is capable of making--on a new layer, and determine that preset's overall blend opacity with the original.
I suppose Lightroom's recent enhanced "profiling" tech was a stab at this capability, but it's problematic. You can't adjust the profiles or even make new ones, yourself, with Lightroom! That requires something like 3D Lut Creator. (Which might be why nobody but Adobe's original handful of launch partners ever made any!) And once applied, "enhanced" profiles put weird, arbitrary floors and ceilings on sliders. You can push the highlights or shadows sliders all you like, but depending on the profile, nothing happens.
I don't mean to talk-up Capture One, only. I could do the same sort of comparison DxO. Where to begin how you'd do anything like a U-point adjustment's blend in Lightroom? And that's just table-stakes in DxO.
Even Adobe is over the idea of Lightroom ruling local, system-camera raw workflowing. They don't care. That's why they swept it toward the "classic" dustbin three years ago. Give Josh Haftel--Lightroom's product manager--an interview and he will talk about how much he loves shooting smartphones into the Lightroom cloud. That's where they are, now. That's where the energy and the money is. The future of Lightroom is cloud convenience and Smartphone AI fizzbang, not advanced color adjustment or RAW proofing flexibility.
Which you and everyone already knows. I'm just suggesting some alternatives to consider before Adobe forces your hand.
That is some classic deadpan humor!When Capture One adds Enhance Details, Panorama, HDR, a usable database, a decent interface, a much lower price, etc. etc,, you might have a leg to stand on.
I mean, you can't honestly be suggesting that janky slow beta "Enhance details" is a "deal-breaker" feature for which you're willing to forego basic color correction tools or opacity on your presets?
Also, I vastly prefer Capture One's idea of a "usable database" to Adobe's--namely, that the software doesn't require you to use its asset management scheme if you don't want to!
And tethering, anywone? Getting that to work in "classic" is always a fun de-bugging exercise.
Huh. You know, as you get older your eyes' lenses tend to skew a little yellow.DXO is nowhere near Lightroom/ACR for handling highlights and shadows. DXO's highlight reduction turns to yellow sludge a long way before Lightroom's and that is simply a fact.
But come on! You "hating" U-point might just mean you were a little clumsy with it. "I hated that" is not exactly an objective or specific data point.Blechh. Hate clunky U point. Lightroom's umpteen brushes are far better.
You hate it. I like it. So . . . ? Does that even-out to "meh"?
Oh, there you go again with that "enhance details" nonsense. Come on!I wouldn't take DXO for free. No catalog, no AI Auto worth spit, no Enhance Details that doesn't introduce additional artifacts,Again, they're so greedy for your dollars that they offer a perpetual-license / one-time-purchase product for $149:
https://www.dxo.com/dxo-photolab/pricing/
You talk like it's straight out of Blade Runner!
In part because you don't have access to all of those features I bullet-pointed above, without it!I'd be up schmidt's creek without Photoshop :^)Oh, but neither of these include photoshop! What will you do without photoshop?
Ya know, maybe this workflow preference means you aren't the best spokesperson for matters like breadth of feature set or depth of edit possibility with RAW conversion software.I have no need or desire to twiddle color endlessly with little rotating wheels. I hate rotating wheels. I pick a profile (Camera Standard usually) and maybe make a tiny adjustment or two, end of story.
"I use two clicks and three features from my software, end of story!" Great, but a world exists beyond that, too, right?
Also, color wheels might hate you! Somewhere right now, on some forgotten backwater of the lost anonymous internet, a perfectly reasonable color wheel is probably bitching about being fat-fingered!
Sounds great, but who says you have good taste?Lightroom's output is flat out gorgeous for each and every Nikon DSLR I've owned. Isn't life great when you get great image quality right out of the chute with no extra work?
I mean, you think "Enhanced Details" is a feature worth crowing about! I'm just saying, it doesn't bode well.
(a) lens transformations are available in Capture OneI need Photoshop for Content Aware Fill, six or eight actions, Transform Warp/Scale/Perspective/Skew. None of which are on offer with Capture One.available on those blended layers, you may not need it?)
(b) What happened to "I need a Camera Standard profile, an AI click, and I'm done and it's BEAUTIFUL! No twiddling for me!"
I think you hung the "mission accomplished" banner little early, here. The story continues: the RAW workflow battle is over and Adobe won. And Adobe wept for there were no worlds left to conquer. So it lost interest and called its conquest "classic," then launched a new fight for the hearts-and-minds of selfie-snapping tweens and #novababes everywhere.I'm set for life with LR/PS. I simply have no desire to collect software and endlessly test it out against other contenders. The software battle is over and Adobe won, and most likely will continue to lead if history (or sales) are any guide.
(No offense, #novababes! Keep that influence game #fresh!)
It coulda been worse. Take a look at Josh Haftel & co and tell me you honestly don't believe "Lightroom Jitterbug Edition" hit the whiteboard at some point. Sometimes youth is wasted on the young.
It sure does.Lightroom mobile works just fine for me to couple of times I've ever used it.Bonus, the mobile / iPad version of affinity isn't even gimped!
But how's PS for mobile treating you? I hear that's just fantastic. No complaints at all. "Real," even!
Ah, I'm just messing with you, dude. Busting your chops, fellow adult, in the service of getting some of the comparative points out under the examining spotlight. I like Lightroom "classic," too. Part of my angst, here, is over Adobe sweeping it to the dustbin without really addressing capabilities they'd lose.
The most important thing in getting what you want out of any of this software is liking it and feeling it. Which you obviously do. Which means it's working, well.
I hope they keep it rolling for you. And me!
Numerous significant omissions for Nikon including the lenses I use the most.I guess that is why they are wasting time and money putting in these great upgrades into LrC. This will take you a while.I don't know what you're looking at, but "new" Lightroom (you know, the one for the cloud), introduced in 2017, has a substantially different UI than "classic."Reilly Diefenbach wrote:That "classic" interface is so great that Adobe redesigned it entirely in 2017,
No, they didn't. It's been pretty much the same all the way back to 2009's version 3 at least. Before that, I was using CNX2, a truly dreadful interface if ever there was one.
That's what I mean when I say Adobe redesigned the "classic" UI in 2017, and called the new product "Lightroom." (And then, as I said, it took a few of the new design elements--the new curves panel, the new profile browser--and retrofitted them to "classic.")
OK boomer!What is "stanning?" The latest millennial buzzword? Is Mother English going down for an eight count again?Same thing with performance--the classic software you're stanning
In the first place, Lightroom "classic" is living on borrowed time because Adobe has another Lightroom, which they just call Lightroom, which is the only one they really ever talk about.Why? What can I not do as presently configured?was performing so well for everyone that Adobe re-wrote a new alternative product from ground up and called that new product "Lightroom."
In the end, however spectacular or unspectacular the classic may or may not be . . . doesn't really matter. It's living on borrowed time.
https://www.lightroomqueen.com/whats-new-lightroom-classic-since-version-6/
They added local Hue adjustments to reduce the need to go into PS. PS does these things with real layers, not fake ones. Also I couldn't care about any of these options. I'm not a professional or a portrait photographer. What I want is my telephoto lens corrections which C1 does not offer.But also: in Lightroom "classic," you can't . . .
- perform saturation or luminosity adjustments per hue on a masked layer (which you've been able to do in Capture One since 2012). At least you got local "brushed" hue skews this year. That's something.
- You still can't adjust a hue, saturation, or luminosity region you determine; or specify the breadth of a hue, saturation, or luminosity region to adjust; or specify the blend of hue, saturation, or luminosity adjustment regions with neighboring colors not adjusted (all of which you've been able to do in Capture One since 2007).
- You can't adjust the degree of change or "unification" over a specified hue, saturation, or luminosity region (which you've been able to do in Capture One since 2012).
- You can't split-tone anything other than highlight or shadow hues and saturations. (In Capture One, since 2014, you can also mix a mid-range tone and a "master" tone over the entire frame, including splits you've already specified. And you can adjust hue, saturation, and luminance on every split.)
- Because you can't do any of this globally, you can't do any of it locally or on a mask, either.
I just want to take a moment and point out how silly it is, then, that you're arguing about this.It has been quite a few years since I looked at Capture One.
"Everything"? I mean, you could credibly edit a Hollywood feature movie with Photoshop, alone. You can edit audio in Photoshop. Photoshop has a scripting language development environment, for god's sake. PS is more than a proofing tool for photographers.Are you telling me it now does everything that LR/PS does, and does it all non-destructively and faster?
Why is that so hard to believe? The LrC code base is more than a dozen years old. Its RAW process and slider math is from 2012. It's just not fresh software. It barely leverages the last decade of hardware technologies--I mean, here we are in 2020 and the most effective way to run LrC quickly is still to just have a fast single-core processor clock.Hard to believe, but if so it would warrant another look.
You misunderstood me. I was not arguing. I was explaining **AND** inquiring, and you answered me pretty well. I did say that perhaps I should look into Capture One again. You certainly make it sound like C1 is a competitive product. Sobeit. I am delighted to hear that Adobe has competition. It will be good for all of us.I just want to take a moment and point out how silly it is, then, that you're arguing about this.It has been quite a few years since I looked at Capture One.
"Quite a few years" = you literally don't know what you are arguing against.
Me too. Always works.I've found that when I start to notice that sort of slowdown in LR Classic after a long editing session that it's time to shut down Lightroom and then start it up again. Always solves the issue for me. I don't know if it's leaks or memory fragmentation or cache problems or what, but it does seem to slow down with time after awhile.
You have created a false equivalence. They are not the same type of parametric editing, in multiple ways.Lightroom and Photoshop can do the exact same things. They both have parametric editing capabilities. The difference is Photoshop can have dozens upon dozens of layers all applying some kind of transformation, and you can have smart objects in that stack, masks, layer effects, and on and on, and it will never miss a beat. Whereas just clicking between files in Lightroom starts sucking down resources like no tomorrow.
I've noticed that even on my 16 core water cooled PC with 64GB of RAM my computer is getting flogged by Lightroom. It runs fine for awhile then it starts in with the BS. It gets to the point where clicking on a file sends my radiator fans into a tizzy. When I've been working for a couple hours eventually the sound of the fans rising and falling is akin to a hurricane roaring by outside my window. Yes, the computer is doing it, but boy is it working hard! I couldn't imagine working with bigger files, and I know higher resolution cameras are coming soon.
On the other hand, Photoshop is actually quite good. It pops open huge files very quickly and doesn't cause your computer to go bonkers the whole time you're editing something.
It seems Adobe has the ability but lacks the will to make Lightroom Classic a good program.
No. That would be the simple game app on your phone that requires 100MB of storage space.I've Is Adobe Lightroom Classic the most inefficient program ever made
4 GB SSD is just damn little. ;-)dual 2gb SSD.
That's normal with the laptops I have used. The cramped space doesn't dissipate heat as well as a desktop, so the fan ramps up quite often. What Video chipset does your laptop use? The video is more important for photo processing than your processor, memory or hard drives.I can 100% vouch for Lightroom and Photoshop causing my laptop fans to blow. I only need to open them, wait a few seconds, they blow.
XPS 17, 11th gen i7, 64gb RAM, dual 2gb SSD. The blowing becomes irritating after a while. No connected peripherals
Processors show very little use in task manager, but HWinfo show the temperatures of CPU frequently hitting high 90s and topping at 100c with Core Thermal Throttling set to Yes
I'm using the laptop on risers to allow air circulation.
Seconds after closing Lightroom/Photoshop, the fans can't be heard. The fan also kicks off with Adobe Rush.
Adobe SupportAssist app says all is well. The fans are not gunked up, as I've checked internally.
I would qualify that statement. There are plenty of functions in photo apps that don't need a great video chipset or GPU ... and some apps don't even support a GPU. In those cases, the main processor, memory, and drive storage are all that matter.That's normal with the laptops I have used. The cramped space doesn't dissipate heat as well as a desktop, so the fan ramps up quite often. What Video chipset does your laptop use? The video is more important for photo processing than your processor, memory or hard drives.I can 100% vouch for Lightroom and Photoshop causing my laptop fans to blow. I only need to open them, wait a few seconds, they blow.
XPS 17, 11th gen i7, 64gb RAM, dual 2gb SSD. The blowing becomes irritating after a while. No connected peripherals
Processors show very little use in task manager, but HWinfo show the temperatures of CPU frequently hitting high 90s and topping at 100c with Core Thermal Throttling set to Yes
I'm using the laptop on risers to allow air circulation.
Seconds after closing Lightroom/Photoshop, the fans can't be heard. The fan also kicks off with Adobe Rush.
Adobe SupportAssist app says all is well. The fans are not gunked up, as I've checked internally.