

process a raw into fixed bitmap variants, using a normal photo editor and standard folder structure. Perhaps it's better to step back a few years and use a more traditional system of image management and manipulation - i.e. I for one have no intention of switching to subscription based services, but where to go from here.
ADOBE LIGHTROOM 6 DOWNLOAD MAC UPDATE
Sadly, having had a bit of a disaster with the latest Photos update in High Sierra, I switched back to Lightroom 6 standalone, of course only just before this announcement made this official. I'm afraid this doesn't surprise me, I did predict this in some of my comments a long long time ago. Lightroom 6.13 with support for the Nikon D850 will be released on October 26, 2017. Lightroom 6 will remain for sale for an undetermined amount of time, but will no longer be updated with camera support or bug fixes after the end of 2017. There will not be a Lightroom 7 perpetual offering. Lightroom 6 is the last standalone version of Lightroom that can be purchased outside of a Creative Cloud membership. But it's not like they're gonna lose the images. If you want more secure storage you shouldn't be using them, Apple, Google, Flickr, 500px, or any of those. I imagine you'd have X time to download your images, but like any other online storage system it's a service you're paying for.Īnd trust 'em? no. Note that unlike Lr Classic, Lr CC stops working when you stop paying. You can go month-to-month, and I think even cancel a yearly sub and get some money back.

You are only "locked into" a subscription for a certain time. As long as I have the functionality I need. And if they migrated all the functionality out to a faster application, fine.
ADOBE LIGHTROOM 6 DOWNLOAD MAC SOFTWARE
All software evolves, and I expect that's gonna be true of Classic as well. There are an awful lot of people using it esp with Ps, and so it would be long time before they could move all the features over to Lr CC. I just saw Julianne Kost's comments on it,, and they say they're committed to it. Nice to read that they've done something to address performance issues, but the subtext is that the codebase is so screwed that they are unable to ultimately fix them.

