Lightroom has some new compettion

[krötenblender]

There is no way for one non-destructive "editor" to properly apply the edits made in another such editor unless the two use EXACTLY the same processing engine.

The question, of course, is how similar exactly the two implementations have to be, to be usable or acceptable. I don't think, that many people are able to see toggles in the least significant bit of a 16-color-channel of a RAW-picture. Other image-manipulations might be easier to see, of course. But I think, there is less to be afraid of, than many think (me included... 🙄)

Besides that, most people (IMHO) edit a picture once and then reach a final state of it. So it would be acceptable to migrate to a different DAM/Developer-Tool by importing the original files the the final edited version and have some symbolic connection between them in the new tool, so that one knows, what came from what. Even better, if the history of edits could be saved as a protocol from LR (this is possible AFAIK), so that one can try to match that with the tools in the new SW, if needed. - My LR catalogs contain currently about 60k different images: I think, there are less than 100 which I edited multiple times. I could probably live with the inability to further edit finished images from LR.

 

[PKR]

Adobe Cloud
https://petapixel.com/2017/11/14/adobes-new-lightroom-downloader-exports-cloud-photos/

 

[willie_901]

Adobe Cloud
https://petapixel.com/2017/11/14/adobes-new-lightroom-downloader-exports-cloud-photos/

An obvious necdessity.

At the same time, this has nothing to do with LR Classic CC. With LR Classic CC.he ability to leave the Adobe ecosystem is unrestricted. For final renderings in LR Classic CC, just export a high-quality JPEG or a TIFF.

You already have the original out-of-camera JPEGs and, or raw files. If you want to modify a LR rendering with your new, non-Adobe platform you can re-render them there.

 

[fireblade]

So, for S&G i purchased Luminar. After a couple of introductory videos i like it.
Processed my first B&W and was impressed.
Untitled by vinny morrissey, on Flickr

 

[willie_901]

From Mike Johnston at TOP

"• Annoyed at Adobe? What Michael Reichmann called "the Photoshop tax" seems to some people to be getting more onerous. With the latest shift in Lightroom to a CC (Creative Cloud) monthly subscription model, it's not hard to foresee a future in which you're consigned to storing your own archive not on your own hard drive (or not only on your own hard drive), but on the amorphous "cloud." Where, of course, your pictures will be safe in perpetuity, we say sarcastically."

http://theonlinephotographer.typepad.com/the_online_photographer/blog_index.html

X

Just more FUD propaganda.[1]

I maintain it's extremely hard to see a future where one is forced to keep their photos anywhere but where they prefer to keep them. It is absurd to imply photographers will be "consigned" to do anything they won't want to do.

Our archive options include:

• negatives and transparencies in notebooks or file cabinets
• prints and self-produced books of various forms
• digital source files (raw) and rendered images (JPEG, TIFF, etc) on an assortment of local media
• storage at off-site locations (relatives/friends homes, safety deposit boxes
• cloud storage solutions

I happen to use all of the above to some degrees as I deem appropriate. I can't think of single reason why others can't implement a system that they prefer.

I use LR Classic and PS CC. I store nothing in Adobe's cloud. I store backups of rendered and original images and files in Amazon's Cloud. If Amazon's Cloud fails the least of our worries will be our photography backups. Amazon Web Services (cloud solutions) has more than 1 million active business, government and non-profit customers in 190 countries. Microsoft Azure and Google Cloud have significant global customer bases as well.

Obviously, professional photographers could be required by their employer or by contractual agreements with clients to use cloud services. But they are also free to find another job, not sign a contract or find a profession that is not immersed in digital technologies.



1/ Fear, Uncertainty, Death

 

[willie_901]

Not sure where you are getting your numbers but the Lightroom CC plan includes 1TB of storage not 20TB. The photography plan (Lightroom and Photoshop) just doubled from $9.99 to $19.99. This is today, at any time Adobe can up the pricing for the software or the cloud storage.

...

I'm still being billed $9.99 per month. I have not received a price increase notice.

 

[willie_901]

That is, except for the new "Lightroom CC". It is cloud only. This new interloper "steals" the old Lr naming style. Perhaps Adobe wants to sucker users into switching. This version stores the images in the cloud. It is also only v1.0 and is lacking many of the functions of the "Classic" Lr.

The newest release in the "old" Lr series is now named "Lightroom Classic CC", with the current version being "Lightroom Classic CC 2018". It only needs the "cloud" for the 2 reasons you list.

Yes.

Except I doubt Adobe wants to sucker anyone. A large number of people actually want to execute some sort of image manipulation with smartphone JPEGS and share photos privately with friends and family members.

The recent, and confusing, changes in product branding simply eliminates the restriction of these activities to mobile devices.

It will be a long time before LR is a practical alternative to LR Classic. Customers would have to upgrade to a higher level of ISP bandwidth (if available). Home network (intranet) performance levels are too diverse. Many customers would also have to upgrade their home intranet as well.

Eventually ISP and home network performance and quality will increase. After all, many of us were using DSL with wired-only home networks a couple of decades or so ago. In the future consumer attitudes will change.

 

[Kent]

As to Luminar: I have been a Beta-User and I kinda liked it. The beta-version (WIN) crashed quite often. But I have pre-ordered the 2018 version and hope that runs more stable. (And yes, I do use Adobe CC primarily as well as other apps...)

After some days of playing around with the final version of Luminar 2018 (WIN 10, i7, 8GB), I must say that this version is still in "beta"-mode. It is pretty slow, slower than LR, and it crashed at the third photo I was editing.

None, I repeat NONE of my other application has ever crashed that way on my system.

They have pushed an update already, like 2 days after the initial release! This is either a sign for a prompt reaction or proof for a premature market launch.

 

[squirrel$$$bandit]

Apple Photos recently added “edit in…” and Affinity is now compatible with that. It makes Photos a pretty compelling library system, though some people are still going to find it lacking in customizability and flexibility.

Pixelmator is planning to release its “Pro” version soon, and I’m interested in the possibilities of that as a photo editor as well.

 

[c.poulton]

I've pushed the button on the purchase of Luminar 2018 as my version of Aperture is a little suspect at the moment. It's not as stable as it used to be and crashes when using the healing tool.

I'm not sure whether to wait for the DAM module due for release sometime in 2018 (?) or bite the bullet and migrate my Aperture library over to Photos. Using Photos alongside Luminar as an extension pretty much covers me however Photos DAM isn't quite there yet.