Lightroom CC 2015.5 and Lightroom 6.5 have been released today, with panorama improvements and bug fixes, as well as the usual new camera/lens support and bug fixes. (For the update links, skip to the end of the post.)
24 hours on, some Mac users are reporting a permissions error message when launching Lightroom. When following the instructions in the tech note, ensure that you “Apply to enclosed items”.
There’s also a bug with lens metadata not being added to the catalog on import. A fix is forthcoming and you won’t lose any data.
So what’s new?
Dust or sensor spots appear in the same place on every image, and retouching them individually can take a long time on a huge panorama. Until this release, any spot removal already applied to the source photos was ignored when merging. No more! Now you can fix your dust spots on one photo, sync the corrections to the other photos, and they’ll be applied during the merge process.
One thing to note is that these spot corrections are ‘baked in’ to the resulting merged image data, so you can’t go back and edit them in the finished panorama. Other spots that only need to be removed on a single image are best left until the finished merged image is available.
Other smaller updates are listed with the bug fixes at the bottom of the post.
New camera support:
- Canon EOS1D X Mark II
- Canon EOS 80D
- Canon EOS 1300D (Rebel T6, Kiss X80)
- Nikon D5
- Nikon D500
- Olympus PEN-F
- Olympus SH3
- Panasonic DMC-CM10
- Panasonic DMC-GF8
- Panasonic DMC-ZS100 (DMC-ZS110, DMC-TZ100, DMC-TZ101, DMC-TZ110, DMC-TX1)
- Samsung NX3300
- Sony Alpha a6300 (ILCE6300)
- Yuneec CGO4
- Click to view the full list of supported cameras
Tethering for new cameras:
- No new tethering in this release.
- Click to view the full list of cameras supported for tethering.
- Note that tethering Leica cameras on Mac 10.11 El Capitan is still not working – it’s waiting on an update from Leica.
New lens profiles:
Android
- Huawei Nexus 6P
- LG nexus 5X
Canon EF Mount
- SIGMA 50-100mm F1.8 DC HSM A016
Canon EF-M Mount
- Bower 16mm f2 ED AS UMC CS
- Rokinon 16mm f2 ED AS UMC CS
- Rokinon 21mm f/1.4 ED AS UMC CS
- Rokinon 300mm f/6.3 ED UMC CS
- Samyang 16mm f2 ED AS UMC CS
- Samyang 21mm f/1.4 ED AS UMC CS
- Samyang 24mm f1.4 ED AS IF UMC
- Samyang 85mm f1.4 AS IF UMC
- Samyang 300mm f/6.3 ED UMC CS
Fujifilm X Mount
- Bower 16mm f2 ED AS UMC CS
- Rokinon 16mm f2 ED AS UMC CS
- Rokinon 21mm f/1.4 ED AS UMC CS
- Rokinon 85mm f1.4 AS IF UMC
- Rokinon 300mm f/6.3 ED UMC CS
- Samyang 16mm f2 ED AS UMC CS
- Samyang 21mm f/1.4 ED AS UMC CS
- Samyang 24mm f1.4 ED AS IF UMC
- Samyang 85mm f1.4 AS IF UMC
- Samyang 300mm f/6.3 ED UMC CS
Nikon F Mount
- Nikon AFP DX NIKKOR 18-55mm f/3.55.6G VR
- Nikon AFP DX NIKKOR 18-55mm f/3.55.6G
- Nikon AFS NIKKOR 800mm f/5.6E FL ED VR
- Nikon AFS ZoomNIKKOR 28-70mm f/2.8D IFED
Olympus Mount
- Bower 16mm f2 ED AS UMC CS
- Bower 24mm f1.4 ED AS IF UMC
- Rokinon 16mm f2 ED AS UMC CS
- Rokinon 21mm f/1.4 ED AS UMC CS
- Rokinon 24mm f1.4 ED AS IF UMC
- Rokinon 85mm f1.4 AS IF UMC
- Rokinon 300mm f/6.3 ED UMC CS
- Samyang 16mm f2 ED AS UMC CS
- Samyang 21mm f/1.4 ED AS UMC CS
- Samyang 24mm f1.4 ED AS IF UMC
- Samyang 85mm f1.4 AS IF UMC
- Samyang 300mm f/6.3 ED UMC CS
- SIGMA 30mm F1.4 DC DN C016
Panasonic Mount
- Bower 16mm f2 ED AS UMC CS
- Rokinon 16mm f2 ED AS UMC CS
- Rokinon 21mm f/1.4 ED AS UMC CS
- Rokinon 24mm f1.4 ED AS IF UMC
- Rokinon 85mm f1.4 AS IF UMC
- Rokinon 300mm f/6.3 ED UMC CS
- Samyang 16mm f2 ED AS UMC CS
- Samyang 21mm f/1.4 ED AS UMC CS
- Samyang 24mm f1.4 ED AS IF UMC
- Samyang 24mm f1.4 ED AS IF UMC
- Samyang 300mm f/6.3 ED UMC CS
Pentax K Mount
- HD PENTAXDA 55-300mm F45.8 ED WR
Samsung NX Mount
- Bower 16mm f2 ED AS UMC CS
- Bower 24mm f1.4 ED AS IF UMC
- Rokinon 16mm f2 ED AS UMC CS
- Rokinon 24mm f1.4 ED AS IF UMC
- Rokinon 85mm f1.4 AS IF UMC
- Samyang 16mm f2 ED AS UMC CS
- Samyang 24mm f1.4 ED AS IF UMC
- Samyang 85mm f1.4 AS IF UMC
SIGMA Mount
- SIGMA 50-100mm F1.8 DC HSM A016
Sony E Mount
- Bower 16mm f2 ED AS UMC CS
- Rokinon 16mm f2 ED AS UMC CS
- Rokinon 21mm f/1.4 ED AS UMC CS
- Rokinon 300mm f/6.3 ED UMC CS
- Samyang 16mm f2 ED AS UMC CS
- Samyang 21mm f/1.4 ED AS UMC CS
- Samyang 300mm f/6.3 ED UMC CS
- SIGMA 30mm F1.4 DC DN C016
Sony FE Mount
- Rokinon 24mm f1.4 ED AS IF UMC
- Rokinon 85mm f1.4 AS IF UMC
- Samyang 24mm f1.4 ED AS IF UMC
- Samyang 85mm f1.4 AS IF UMC
- Sony FE 24-70mm f/2.8 GM
- Sony FE 85mm f/1.4 GM
Click here for the full list of available Adobe Lens Profiles
Further user-created profiles can be downloaded using the Lens Profile Downloader (scroll down slightly, it’s at the end of the Resources section on that link)
Loads of bug fixes:
There are a number of bug fixes. These are the main ones:
- Mobile sync is now faster thanks to a number of sync-related bug fixes.
- Fixed – Sync wasn’t automatically being logged in on first launch.
Import
- Fixed – Rename failed if raw+jpeg pairs were copied to a second location.
- Fixed – The tethering toolbar wouldn’t move.
- Fixed – Import didn’t work if you weren’t signed in.
- Crashes when tethered to Canon cameras (5dm3, 5ds, 1dsm3)
- Can’t import DNG files from Parrot Bebop drone
Library
- Fixed – Scrolling through photos with the mouse in Loupe view was broken.
- Fixed – The video cache was not correctly limited to the size set in Preferences.
- Fixed – Certain dates couldn’t be entered in Edit Capture Time dialog.
- Fixed – Videos wouldn’t play on some systems.
Develop
Photo Merge
- Improvement – Boundary Warp in Panorama Merge is improved.
- Fixed – Auto checkbox in Panorama Merge is removed as it always selected Spherical.
- Fixed – Merge failed when source photos were virtual copies.
Export
Slideshow
- Fixed – Slideshow was displaying low resolution.
- Fixed – Impromptu slideshow gave error message “video support is disabled”.
- Fixed – Slideshow module wouldn’t work on some systems.
Book
Other
- After export shortcut CTRL+ALT+S not working in Develop
- Crashes when tethered to Canon cameras (5dm3, 5ds, 1dsm3)
- SDK broken edit_field’s validate function, disabling existing plugins
- Months in non-English configurations show in English
- Secondary Window blocks mouse clicks even when closed after switching desktop spaces
If you find another bug, click here to report it.
How do I update?
To update, go to Help menu > Updates or click the Update button in the CC app. The update servers take a while to push the updates around the world, to avoid crashing the servers, but if you’re in a hurry to update, here are the direct links to the patches: Windows – Mac
No, no change of process versions to worry about.
YMMV means your mileage may vary. With a 5-6 year old CPU, I’d bet that’s your bottleneck. You have to remember that Lightroom is running a series of text instructions every time you make a change, which is particularly noticeable with sliders that build masks (e.g. shadows/highlights) and local adjustments (particularly the brush and spot removal).
I have a few questions:
First of all, I noticed that there’s also a CC-version of Lightroom now, correct me if I’m wrong. But what’s different about that? Is that part of the subscription-based Adobe software? Which I’m guessing means that the other version is a standalone product.
Then, I’m still using version 5.4. If I’d move to 6.x, would I lose anything or need to convert anything, or will I simply be able to open a catalog I’ve made in 5? – Because it was a bit of a different story between 3 or 4 and 5. Perhaps they’ve changed that now.
And finally, possibly the most important thing for me; I’ve read that there’s a performance-update, such as letting Lightroom rely on your videocard now. I have a good videocard and all that, but does it make a significant different?
Because the main reason I’m looking into moving to the latest version is because I’m tired of it just lagging once I do something a little heavier such as using the Adjustment Brush and using more than 1 “layer” of that. Cause I’ve come to a point that when I have 2-3 or more layers of it, and then try to change a very basic setting such as white balance, it would take about 10 seconds for the image to update. That’s no way of working.
And I have a decent CPU. I can do anything from pretty significant audio and video editing (like with Vegas, which isn’t exactly light on your system), and videogames (although that relies on the GPU a lot), but once I get more in-depth with Lightroom it just hogs the CPU and eventually it grinds to a halt.
I would probably be better off with a better CPU, maybe (if that would actually make a difference), but that won’t happen for a while.
So, please let me know of these things so I could perhaps improve my experience with Lightroom.
It’s pretty good, but the performance… It’s killing my workflow and productivity.
Do you also see videos throughout my comments?… What’s with that?… I didn’t do that!
I can! Figuring out now….
Phew! Turned out to be a Wordpress Jetpack plugin bug.
CC (subscription) vs perpetual (standalone) is primarily a difference in licensing/payment process, but CC subscribers get early access to new features too. There’s a comparison here:
When you open your LR5 catalog into LRCC or LR6, it will ask permission to upgrade the catalog and you just say yes. Very easy. Just be aware that you won’t be able to open the upgraded catalog into LR5 (e.g. if you’re using an LR6 trial), but it doesn’t change the original version.
The new GPU feature makes the most difference on high resolution screens, so YMMV. You could watch the Resource Monitor (I assume you’re Windows?) and see if you’re maxing out the CPU or RAM too.
I’d recommend making sure you have the latest GPU drivers from the manufacturer’s website (not just Windows Update) and then try the trial of LRCC and check you’re happy with the performance. Just ‘play’ in the upgraded catalog, rather than doing serious work, just in case you decide to carry on using your LR5 catalog.
Ah, I see. Well, I don’t care about getting early access, so that’s OK.
So there’s nothing like new “processing” or something like that between 5 and 6 that might change things? I always just worry about all my tweaks or the results being changed.
And yes, my CPU definitely maxes out when I use the Adjustment Brush for example. I have enough RAM with 8GB for what I’m doing though. And I do have the latest drivers, because I use the GPU for videogames as well.
Don’t worry, I’m on top of all that. But I know my CPU is probably lacking. It holds up, even for 5-6 years old, and it has the advantage that it overclocks well. But the overall processing could be better for Lightroom.
What is YMMV, though?… I only use a resolution slightly under 1080p, being 1050p on a 16:10-monitor. So that probably won’t be affected. But wouldn’t any other processing be offloaded to the GPU? Would be nice if it was able to use CUDA or some such thing, but I’m not sure if it works that way for still image processing. I think Photoshop does that, though…
I guess I’ll test with the trial some time.
Thanks for your reply!
Is there a new “bug” which is affecting the Library Filters? Since the update, the filters (I mostly use star ratings and colour coding) doesn’t seem to stick the each individual library folder, as it used to.
I haven’t heard of one. It’s possible that your preferences became corrupted, and you haven’t rechecked the File menu > Lock Filters and File menu > Remember Each Source’s Filters Separately.
That was it. I had a feeling something had gone wrong with my preferences, as many things had been reset to default settings (identity plate, solo mode, just to name a few). Now that I look at it carefully, it seems everything was reset.
Thank you!
Hi Victoria,
If I follow your instructions to go back https://www.lightroomqueen.com/how-do-i-roll-back-to-lightroom-2015-1-1-or-lightroom-6-1-1/. Do I have to reinstalled all the plug ins that I have now. Thank you
Plugins (and everything else, e.g. presets, prefs) should remain untouched. Only annoyance I encountered was that my LR Mobile sync decided to re-sync everything (no idea why), which took a couple of hours to complete.
I also had to remove and re-import all images imported into the catalogue since I “upgraded” to 2015.5 in order to get lens metadata to appear in the catalogue. This is worrying, as it implies that the metadata is being stripped out (permanently?) when importing Nikon raw files in 2015.5/6.5… Glad I caught this early and rolled back.
Mark many thanks you for your comments. I did not import new images since I upgraded. I will have to look at the images in the catalogue for the images from the Sony camera if the information is there. I guess I have no choice to go back to 6.4 if I want the information from my new D750.
A hot fix is in the works. Once it’s available simply writing the metadata to the problem files and reading it back should ‘fix’ any that are missing lens data.
Thank you Victoria, I will wait for the hotfix instead of reinstalling.
Good to know, mabye I won’ roll back this time.
I realy want to like Lightroom, its features match my workflow pretty good.
But sadly, Lightroom is becoming a bug-infested nightmare.
Hi Victoria, after reading the comments at https://feedback.photoshop.com/photoshop_family/topics/camera-raw-9-5-lens-information-aux-lens-metadata-field-missing-on-import
Is it only related to DNG files or all the files ? Thank you
It appears to affect all Nikon raw files, regardless of whether they’re converted to DNG or left as NEF.
Thank you for the info.
That’s too bad because I just bought myself a Nikon D750 and upgraded to perpetual 6.5.
I just noticed that in the latest version (2015.5 on Win 7), the actual lens used is no longer being displayed *anywhere* in the Library module for newly imported images! Not in the thumbnail view options (if you just select lens model, it doesn’t show anything), not in the metadata panel. Rather unhelpful given how important this information is… It also breaks the smart collections I have set up that rely on lens data, as they no longer pick up any newly imported images.
I’m flabbergasted. How can such basic stuff be missed in beta testing? Do they beta test at all nowadays?
M
I’ve seen a bug report on that one https://feedback.photoshop.com/photoshop_family/topics/camera-raw-9-5-lens-information-aux-lens-metadata-field-missing-on-import
I’m not sure how that one slipped through either!!
It’s obvious to me that we are the beta testers. That’s why I’m never in a hurry to install latest release.
A lot of beta testing does go on before release, but the more complex Lightroom becomes, the more things there are to test, and the more likely bugs are going to get missed unfortunately.
Victoria,
Using that thinking and given Adobe’s historical financial performance, I could just as easily argue that the more money Adobe makes, the more likely the bugs are going to be missed because that’s exactly what is happening. Two of the last four updates have caused problems with people launching the program and that’s inexcusable in my mind.
I would be willing to bet that if you wrote a book with more information, you wouldn’t be caught dead saying that due to the increased information more mistakes were unfortunately going to be missed. Similarly, we shouldn’t be allowing Adobe weak excuses.
Just my thinking.
Got to agree with Mike. There was a time that programers were extremely professional and made extensive testing scenarios to be followed in order to ensure the end product performed as intended. This has apparently gone away with the millennial generation. Nothing but quick, and not be held accountable for their efforts. What makes it worse is the justifying statements in support of this ‘less than professional’ approach. Permissions issues and missing lens data are fundamentals that should NEVER get to the outside for beta testing, let alone into a released product. Very disturbing.
Yeah, that’s fair. I’d love to see them do a “bug fix only” major release, and really spend a year or so just focusing on getting everything as perfect as possible. The trouble is, then users complain there aren’t any new features. There was a thread on the bug forum on that topic just this week. It has to be a tough line to walk, but I’d certainly love to not have to write warnings in blog posts.
I’m not as long term a user as some (started at v4), but seems to me things got worse when Adobe went to the cc model. Thoughts?
Yeah, the fast turnaround and pressure to add new features to each update certainly has certainly let much bigger bugs escape. I think it actually started to get worse around LR4, when LR went from being a fairly streamlined tool in earlier versions to adding a lot of new features in LR4, but it used to be that the .0 release was a bit buggy and subsequent releases improved. With the major changes being added into dot releases now, there’s a lot more potential for issues with dot releases.
The issue is fundamental, lack of a clear leadership with a sound directive for the company to explicitly follow. When you let the bean counters & mouseketeers (marketers) drive the business unchecked, bad things start to occur on an ever increasing scale. If Adobe would establish a comprehensive set of testing scenarios (continually reviewed & updated) that are religiously adhered to including employee sign offs, these really sophomoric misses would be caught BEFORE the ‘beta’ stage. It’s painfully obvious this is NOT occurring. It sure would be a pleasant change to finally deal with a company that ‘gets it’ #NotHoldingMyBreath
I tend to agree that, no matter how much testing you do, some bugs are going to slip through the net – that’s a fact of life with software development and complicated applications such as LR.
However, this is something that *should* have been picked up. It seems that none of the beta testers tried importing a Nikon file and checking it worked properly?? If so, there clearly isn’t enough beta testing going on before release, or alternatively, not enough people doing the testing.
(I feel sorry for all those folk ready to pick up their new Nikon D5s and D500s – which the latest version just added support for – talk about give and take: we support your new camera, but not your lenses! They obviously won’t be in a position to roll back as the earlier version won’t work with the raw files from their new camera.)
Just seems to me unless you really need the update, “if it ain’t broke…” applies. I used to blindly apply every update. Not any more. Others feel the same?
Absolutely… I teach a course in Lightroom and having something not work or launch at all is counterproductive to say the least.
Wished someone else also could ask for native full XMP support in Search and Smart Collection and that all XMP metadata got saved to smp sidecar file … including custom Fields.
2nd update: After un-installing the new LR and re-installing an old version, I decided to be brave this morning and upgrade LR back to 2015.5. Back to the same problem — a fatal permissions error. Here’s the solution that worked for me (on my elderly MacBook Pro, OS X 10.5.5, 8 GB RAM).
This website:
lists 4 solutions. For me, #1 and 2 failed (even using the “Apply to enclosed” option. But #3 did the trick. In fact, I only had to chmod the first folder. That was the magic. And very easy to do.
Good to know, thanks Lawrence.
The update on Windows 8.1 went without problems. No issues (so far) with LR6.5 for me. I think this time it only hit the MAC users …
But I dare say – unless you really need the update for a new Camara or Lens – the improvements in 6.5 don’t really register very high on the thrillometer … Sure there are some bug fixes but not for anything I needed.
As alwasy before installing LR updates I do a full system backup of my C drive SSD – so if necessaty I can very easily revert in no time 😉 Data is on a separate disk.
That’s very sensible Uli.
The “Secondary Window blocks mouse clicks even when closed after switching desktop spaces” was not just an issue with desktop spaces. It was a problem that emerged in Version 4. It would cause issues simply turning the secondary window on then off. Which was, as it happened, solved by turning it on and off again. I often used the secondary window in map mode and was plagued with the issue until I finally discovered a work around and the support thread. In any event it was a minor annoyance and seems to be rectified. All good now.
That’s good to hear Greg!
Alas I jumped the proverbial ordnance on this. After further testing it is still an issue. It may have been fixed for one scenario (still testing) but is definitely still an issue. Today I went into the map module, turned on the secondary window, off again. Then I had the same dead region as before across all modules. Resolved by toggling the secondary window as before.
Rats! Make sure you post back on that thread so it gets followed up.
Hi Victoria, its funny because I did not receive the newsletter for the Lightroom CC 2015.5 and Lightroom 6.5 entry in your blog. Is this normal ?
The newsletter will go out, probably later today. I put the blog post out on social media, but wanted to check there weren’t any massive bugs before I told everyone to upgrade!
Thank you
On launch, I got a message saying that LR could not start due to a permissions error. Dialog box gave OK and Fix as options. Tried Fix, no go. Went to Adobe’s web site and found that 3 folders needed their permissions set to Read & Write. When I found those folders, they were already set correctly. I restarted the computer, used Disk Utility to repair permissions, etc. All the usual stuff. Nothing worked. And I spent a fruitless hour on Adobe’s help chat. Finally un-installed and went back a few versions. If you’re not hearing other bad reports, maybe I’ll try again after work …
When you check the permissions are correct, make sure you “apply to all enclosed items” as it could be a subfolder or file that’s causing the trouble.
I have the same problem, I try fallow adobe’s web site steps without luck, I un-instaledl LR and went back to 6.0. 🙁
Update: I went backwards, for sure. After un-installing the problematic 2015.5, I found an installer for an older version (aspen trees on splash screen, build 1014445, couldn’t find a version number). Works like a charm. I suspect I’ll stay there for a while. Since Adobe seems to be doing this to us regularly, it would be nice if there were a place where all older versions of LR could be found. This is my second go-round of un-install and install in six months.
That’s an odd one Lawrence. I haven’t seen any other reports. What happened when you tried to launch?
There is a place where all older versions can be found –
I was looking forward to a bug-free-er LR, but once I installed 2015.5, it wouldn’t launch. Message about incorrect permissions (Mac OS X 10.5.5, MacBook Pro, 8 GB ram, plenty of space on HD). I did all the things Adobe recommended — sign out and in to CC, change some permissions manually (they were already fine), etc. No dice. For now, going back to 2015.4, but thinking seriously about Capture One.
Thank you so much for the latest info on the updates. I never update until I check here first, I don’t want to revert version updates anymore. I learn so much from your book, thanks again.
You’re welcome. Thankfully we seem to be back to a ‘normal’ level of bugs!
Thanks again for ALL that you do!!! I read The Missing FAQ daily…No lie!