Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: davidgp on March 07, 2017, 01:18:56 pm
-
Hi all,
Adobe just released Lightroom 2015.9. Only new cameras, lens profiles and bug fixes... no new features:
https://blogs.adobe.com/lightroomjournal/2017/03/lightroom-cc-2015-9-now-available.html
Regards,
David
-
Some good bug fixes for me. Not available yet on my machines with Lr CC.
-
If you don’t see the update in your Creative Cloud App, you can use the obscure [Cmd/Ctrl]+[Opt/Alt]+[ R ] to refresh your app. If you are a perpetual license holder, you can access the update via Help>Updates…
Refer to this for any installation issues: http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015
-
If you don’t see the update in your Creative Cloud App, you can use the obscure [Cmd/Ctrl]+[Opt/Alt]+[ R ] to refresh your app. If you are a perpetual license holder, you can access the update via Help>Updates…
Refer to this for any installation issues: http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015
One shouldn't need obscure anything for something as elementary as an up-date path, which should be time-worn routine by now. Just another reminder from Adobe that for those who don't need the labour-pains of early adoption, it's best to wait several months for the bugs to be identified and corrected.
-
There's no obscuring. On CC simply go to the tools icon (gear at top right) and click Check for App Updates. On the perpetual license there's an Update command under one of the menus.
The no-showing updates on CC is probably due to a user choice to not auto-update the CC manager.
I updated to the new version and it works well.
-
There's no obscuring. ............
Sorry - it was Mr. Flohr, an Adobe rep, who introduced that expression, so I was just taking-up where he left off. Glad to hear it is working well for you. Once there is an accumulation of such positive reports it will be safe enough to do the update.
-
... Once there is an accumulation of such positive reports it will be safe enough to do the update.
I am not that paranoid. My experience with Adobe, and in particular Lr/ACR's core development team, is that should a major bug materialize they are quick to take action or provide access to re-install the previous version. This dot version is worth it just for its fixed curves control.
-
Just updated to 2015.9 and the tone curve problem still exist with Sierra. It has been a problem since September of 2016 when Sierra was first released. I wonder what Adobe would say if those of us with this CC Lightroom problem were to ask for a partial refund? Yep, we all know exactly what Adobe would say.
-
Sorry - it was Mr. Flohr, an Adobe rep, who introduced that expression, so I was just taking-up where he left off. Glad to hear it is working well for you. Once there is an accumulation of such positive reports it will be safe enough to do the update.
Obscure is the Autocorrect for "KBSC" (Keyboard Short Cut). I didn't catch that it had been autocorrected before posting it. My apologies for confusing you.
-
Just updated to 2015.9 and the tone curve problem still exist with Sierra. It has been a problem since September of 2016 when Sierra was first released. I wonder what Adobe would say if those of us with this CC Lightroom problem were to ask for a partial refund? Yep, we all know exactly what Adobe would say.
Tell Adobe that as it may be hardware specific. I have reported this before, but it is working fine (for me) now under Sierra.
-
Tell Adobe that as it may be hardware specific. I have reported this before, but it is working fine (for me) now under Sierra.
I and many of those who are dealing with this bug have already provided Adobe with our hardware specs. Months ago.
-
Obscure is the Autocorrect for "KBSC" (Keyboard Short Cut). I didn't catch that it had been autocorrected before posting it. My apologies for confusing you.
Thanks Rick, I'm still confused, but let's move on. If it works, fine.
-
Just another reminder from Adobe that for those who don't need the labour-pains of early adoption, it's best to wait several months for the bugs to be identified and corrected.
Yup ... best to wait and see. I have had to roll back to a known working past version far too many times in the past to blindly update anything from Adobe.
Considering there's really little improvement offered in this update that is worth the risk of early adoption.
-
There's no obscuring. On CC simply go to the tools icon (gear at top right) and click Check for App Updates. On the perpetual license there's an Update command under one of the menus.
The no-showing updates on CC is probably due to a user choice to not auto-update the CC manager.
I updated to the new version and it works well.
Sorry...that wasn't the case for me. I NEVER chose not to auto-update CC manager in fact it still showed that auto-update was enabled.
For the first time I did have to go to the "gear" icon and tell it to check for app updates. Then the update to Lr appeared. My guess is that Adobe changed something with the last update to the CC app.
BTW, the update to ACR showed up without any intervention on my part.
-
If you keep your PC on most of the day and seldom restart (I put it in hibernation instead of shutting down, for example), the CC app may look for updates one or two days after the actual release. This is why some people don't see the updates pending right away.
Also if you are not on Windows 10 it's easy to miss the update notifications.
No issues on my part either, not a single issue since I switched to CC from CS6. Last time I had a crash it was with one of the 2014 versions of Photoshop, no issues since then. I understand that some software and hardware combinations can be prone to issues, but there's no reason to be paranoid about updates. A safe route is to update your second (or third) machine first and keep your main workhorse for later, so if you spot any problems you can keep working without interruptions. Obviously keep backups of everything important, and keep them up to date. More importantly have a plan to quickly restore said backups.
-
I understand that some software and hardware combinations can be prone to issues, but there's no reason to be paranoid about updates.
It isn't paranoia if more than a few users have a lack of faith in new updates from Adobe. The historical facts prove otherwise. Once burned, twice shy. There is a difference between a lack in faith that a software developer employs due diligence or suffering from paranoia.
If you haven't experienced any issues of late, bully for you. Your experience may very well be the result of your workflow not pushing the envelope in a wider range of use. There are many issues and bugs in both Photoshop and Lightroom that I don't experience personally because I may not utilize those functions in my workflow. I certainly don't go online and profess all is well because I don't experience them. Perusing any of the popular user forum discussions is another form proof positive that the issues are not all outlier problems that result from obscure 'software and hardware combinations' ... many were the outright removal of functionality. Some intended because Adobe thought they knew better, some as a consequence of those same folks at Adobe not doing their homework prior to implementation and official release.
Rather than diagnosing your fellow forum participants as suffering from unwarranted delusion of persecution, maybe you could trust their experiences have been quite different than yours and are actually justified by historical fact.
-
Such hostility.
-
Such hostility.
Not hostility. Unfortunately there are folks who see Adobe either as having a halo, or that of a meal ticket. The truth is, it is a for profit, public company which answers to Wall Street and as such will sometimes make decisions not in the best interest of its paying customers. This isn't hostility, but facts.
I prefer Lightroom (ACR) over other post processing programs. It is excellent as a color processing tool. But Adobe also nears malfeasance in its arrogance:
https://feedback.photoshop.com/photoshop_family/topics/tone-curve-still-broken-in-lr-cc2015-8?utm_source=notification&utm_medium=email&utm_campaign=new_comment&utm_content=reply_button&reply[id]=18480961#reply_18480961
-
Such hostility.
To whom are you referencing as behaving in a hostile manner?
Is it customers who have pointed out historical fact of Adobe's less than desirable results for several recent updates ... or the person accusing his fellow forum members as suffering from delusions?
-
Sorry, my intention wasn't to attack people. I understand being wary of updates, this is why I suggested updating other machines first and test the new version to make sure everything you need is working as expected.
The only company I care about is mine. I use Lightroom and Photoshop in my workflow as they are very efficient for my style of shooting, but I prefer Capture One Pro colors and color tools. If anything I miss the old Corel applications, maybe I should just move to the CorelDRAW X8 suite! :P
-
... I understand being wary of updates, this is why I suggested updating other machines first and test the new version to make sure everything you need is working as expected.
Yes, great advice for yet another workaround. Though a workaround is not really a solution for the long term, simply more work.
On the update versions I had issues with, I followed your advice precisely. (Without you ever sharing it for my benefit beforehand) However, it still required extra time and effort on my part to restore the test workstation to a previously known working version from a backup. All as a direct result of Adobe not applying proper oversight and/or using a too narrow private beta testing field to ferret out such issues before the official release. Not to mention, one of my major problems with applying a Ps Droplet upon export took not 1, not 2 ... but 3 attempts to restore.
Trust should never be expected or offered blindly. It must be earned. Adobe hasn't done much to earn that trust over the past year or more. I'm also not inclined to become a pay-to-play public beta tester.
In my instance, there is very little paranoia involved. My views is based purely on factual accounts.
-
Adobe has had some issues with a few of their updates which have caused some serious problems. On a percentage basis they haven't done that badly, considering they have issued dozens of upgrades and updates of Lr over the past ten years and only a few of those have caused serious issues. But those have been serious enough and obvious enough it makes users wonder where their quality control is and why they don't utilize a little larger beta test group.
Regarding this update, I will say I've been using it since it appeared on two different Macs, including raw processing of IQ3 100 files and printing with no issues. I haven't tried any pano merges yet to see if they broke that functionality (which I believe has happened twice before, once in Ps and once in both Ps and Lr). Maybe users who have tried that could chime in so those users wanting to "wait and see" have some feedback to help their decision as to when to apply the update.
Wonder if this will be the last release of Lr 2015 ...
anyway, here's my first image from my IQ3 100 processed in Lr. The use of the automask tool and brush adjustments gave me a better result than I achieved in C1. Not saying that's C1's fault, but I've just found my technique for this works so well in Lr and haven't figured out how to do it in C1 with the same simplicity and degree of success.
(if anyone cares, here's the details on the shot and post processing ... Phase One XF with 75-150 lens at 75mm, 1/80th at f/9, 6 shot focus stack using XF focus stacking tool, process in Lr 2015.9, output to tifs into Helicon Focus for merging, back to Ps as smart object with raw filter applied for final tweaking)
-
Hi Wayne,
Very nice shot, I assume you had no wind? I have tried the focus stacking in the field, but have found that Helicon can't handle the slightest amount of wind and creates very strange issues. But when I have a solution where it works amazing.
LR, pano, not broken, but still not working 100% as it still pushes exposures beyond recovery. I have opened several tickets on this, but have never gotten any word LR Adobe is working on it. But often LR will take a shot that is not overexposed (but close) and when it makes the merge, the highlights will be pure white. Same files exported to Adobe CC will work fine but you don't gain the benefit of the boundary wrap which I really like.
Paul Caldwell
-
I'm still using Lr 2015.6.1 and Photoshop 2015.5.1 because both of them haven proven to perform the functions I need correctly. Except for panos in Lr. The algorithm for Photomerge>Pano fails to find enough pixels in common for lining up the images, whereas Photoshop has no such problem with exactly the same photos exported as TIFF or PSD files, and in fact does a much better job than I obtained trying them with a demo version of PTGUI. So if nothing has changed in this area between the version of Lr I'm using and the newest one, it would indicate that problems in this area remain to be resolved.
-
Hi Mark.
I agree LR often will not work well on a pano with a lot of fog or clouds. I just wish Adobe would add boundary warp to CC. It's so much better than the content aware option in CC.
Paul Caldwell
-
Hi Paul,
I find panos in general are a hit or miss proposition in Lr, and the photos I'm stitching do not have clouds or fog. These days it's mostly street art, which tends to have a lot of high density detail and very distinct graphics. Where I made the photos intended for future stitching I of course ensured sufficient overlap. This is what's so troubling about the functionality. However, the saving grace is the 800 lb. gorilla waiting on the wings - exporting the files to Photoshop and stitching them there usually works very well. The two applications start with very different kinds of data and perhaps somehow or other this explains why one appears to work better than the other, but I have no real technical insight into this.
-
Adobe has had some issues with a few of their updates which have caused some serious problems. On a percentage basis they haven't done that badly, considering they have issued dozens of upgrades and updates of Lr over the past ten years and only a few of those have caused serious issues. But those have been serious enough and obvious enough it makes users wonder where their quality control is and why they don't utilize a little larger beta test group.
Hi Wayne - yes, I too am in the "wondering" mode, while I agree with your evaluation of the overall experience for the past decade. I have the impression, which could be disproved with real data, that the appearance of serious issues has been skewed toward the more recent period of the decade, suggesting perhaps changes in management approach that could be sub-optimal in these respects. As for the beta test group, yes bigger may be better, but I suspect conscious stratification of the sample may be also important, to assuredly capture a reasonably broad range of user computing environments. While I think we need to attune our expectations to the complexity of what they are working with, like many others I would like to see the day when I can return to being an early adopter with more confidence than I now have in a trouble-free experience.
Where I would really like to see a major evolution of Lr going forward, and I have recommended this to persons in Adobe a long time ago, is to see a broadened structure of editing capability in the local adjustment modes of the Develop Module (brush and gradient functions) whereby the controls available in this mode would be the same as the ones in basic mode, providing for much more powerful and refined local adjustment capability.
All this said, Lr remains my application of choice given the capabilities that have been developed over the years, its relative ease of use, image quality (in the hands of people who know how to use it), the strength of the Print module and integration with Photoshop.
-
I'm still using Lr 2015.6.1 and Photoshop 2015.5.1 ...
Unfortunately, this is the case for more than a few users. While you are using a prior stable version that offers you the best workflow for your personal needs ... with the CC subscription you have been paying for all the subsequent updates, up to and including the most recent Lr CC 2015.9 and Photoshop 2017.0.1/ACR 9.9.
While working with an older version is not of great consequence in of itself, I do wonder how many folks would be content to drive a leased 2015 automobile all the while they are being charged for the most current 2017 model that remains in the garage because it is either unsafe or unable to be driven?
-
Butch, the subscription remains worthwhile to me whether I hit the bleeding edge on day one or some time thereafter, because for my needs they haven't introduced anything compelling since the versions I'm using, and each update embeds a certain element of risk - small as it may be - so why bother until there is a more compelling reason? When there is, by having the subscription all I need to do is push the button. I think we all agree that the lower the upgrade risk the better.
-
(if anyone cares, here's the details on the shot and post processing ... Phase One XF with 75-150 lens at 75mm, 1/80th at f/9, 6 shot focus stack using XF focus stacking tool, process in Lr 2015.9, output to tifs into Helicon Focus for merging, back to Ps as smart object with raw filter applied for final tweaking)
Result == Excellent! Very nice.
-
Butch, the subscription remains worthwhile to me whether I hit the bleeding edge on day one or some time thereafter, because for my needs they haven't introduced anything compelling since the versions I'm using, and each update embeds a certain element of risk - small as it may be - so why bother until there is a more compelling reason? When there is, by having the subscription all I need to do is push the button. I think we all agree that the lower the upgrade risk the better.
This is exactly what I do. I let the noise die down around a release, then I upgrade. So far doing this resulted in zero upgrade issues. The most I waited to upgrade to the latest was 2 months...I can live with that.
-
I agree LR often will not work well on a pano with a lot of fog or clouds. I just wish Adobe would add boundary warp to CC. It's so much better than the content aware option in CC.
A little pet peeve of mine.. You're not the only one I've seen do it, though - so I don't want you to think I'm picking on you or anything. :)
CC is really more of a payment model, not a program. Kind of like if someone said: "I exported from CC, then imported into Adobe CC, but I like CC better than Adobe - but not as much as CC". Would you know what the world I was talking about? ??? ;D
I haven't done a lot of pano merges yet, but I'd like to understand what people are saying about each program when referring to them so I can know for any future panos I might do. I can kind of decipher by context here in the previous references to "CC" and "Adobe CC" (as CC wouldn't do context-aware panos like Adobe CC would ;) ), but some I'm still unsure of. (Albeit, the latest LR-CC does have boundary warp IIRC.)
-
Butch, the subscription remains worthwhile to me whether I hit the bleeding edge on day one or some time thereafter ...
It's quite apparent you don't have to be concerned with being on the bleeding edge ... Lr 6.1/CC2015.1 was released in July 2015 ... that's 18 months behind the curve. I don't think anyone would consider that pushing the envelope. :)
-
It's quite apparent you don't have to be concerned with being on the bleeding edge ... Lr 6.1/CC2015.1 was released in July 2015 ... that's 18 months behind the curve. I don't think anyone would consider that pushing the envelope. :)
I'm on 2015.6.1 released July 25, 2016. So only 7 months behind the curve! :-)
-
It's quite apparent you don't have to be concerned with being on the bleeding edge ... Lr 6.1/CC2015.1 was released in July 2015 ... that's 18 months behind the curve. I don't think anyone would consider that pushing the envelope. :)
No not pushing the envelope, I would think that the envelop is lost to history.
-
I'm on 2015.6.1 released July 25, 2016. So only 7 months behind the curve! :-)
sorry ... cot my CC2015.x and v6.x versions mixed up.
-
Hi Paul,
I find panos in general are a hit or miss proposition in Lr, and the photos I'm stitching do not have clouds or fog. These days it's mostly street art, which tends to have a lot of high density detail and very distinct graphics. Where I made the photos intended for future stitching I of course ensured sufficient overlap. This is what's so troubling about the functionality. However, the saving grace is the 800 lb. gorilla waiting on the wings - exporting the files to Photoshop and stitching them there usually works very well. The two applications start with very different kinds of data and perhaps somehow or other this explains why one appears to work better than the other, but I have no real technical insight into this.
I do a fair amount of two-shot panos with LR and can't recall the last time I had a problem with that. Perhaps more shots creates problems sometimes, or the size of the files?
-
The recent ones I've done have been either two or three photos. The files are much larger in Photoshop because they are rendered, yet the stitching has been much more workable.