Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: pflower on July 05, 2016, 02:50:22 pm
-
This is becoming a bit of a nightmare. I am in the middle of printing for an exhibition. Most of the images were processed in the last version of LR CC before the CC2015.6 version was released - I am on Mac OSX 11. I can't remember now precisely the version number but it was CC2015.5.x. I upgraded to CC2015.6 and have suffered from the printing bug in this release - the prints on my Epson 3880 look like rubbish (and despite what Adobe says I am on the most recent driver for the printer).
So I have tried to roll back to the last release before CC2015.6. This is not available to me through Creative Cloud so I found this link - https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html. You have to download the Application Installer and then the version you want. The only option before CC2015.6 is CC2015.5.1.
However installing that I simply get a splash screen that says it is CC2015 - i.e. no later release. More urgently for me is that this version, whilst it prints fine, does not have the Dehaze option in it. Many of my images have used Dehaze and in the now installed version don't work properly.
Can anyone help in guiding me to somewhere I can get the last release of LRCC before the 2015.6 release?
Thanks
-
http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015
-
Slightly different link but the same options as the one that I found. That's the one I downloaded and installed - i.e. 2015.5.1 - no Dehaze -. There must be a later version or I am being very stupid (entirely possible). I thought Dehaze was released in an earlier version to 2015.6 which itself only added the guided upright. But for the life of me I can't find it. There was a huge fuss over the import options somewhere in the CC2015.5.x releases which Adobe then retracted. I remember going through those without too many problems. But I am now stuck with images in 2015.6 that printed fine on previous versions of LR but won't now or rolling back to a version that doesn't include an adjustment I made use of.
The only solution for my immediate problem is to use 2015.6 and export as Tiffs and print through Photoshop CS 5 which I still have. But this is a huge mess and a pain. Have Adobe completely re-written history by deleting all versions of LR after 2015.5.1 up to 2015.6 or am I delusional?
http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015
-
Dehaze came in 2015.1 as a global adjustment, and was added as a local adjustment in 2015.2 Where are you looking for it? Are you definitely a CC subscriber, and signed into your account when you're running Lr?
-
Yes I am indeed a CC subscriber and when I download and install the 2015.5.1 app I am asked to register with my ID and password (as opposed to taking a trial run). But there is definitely no Dehaze in the options.
This is the screen shot - and I have done this several times expecting 2015.5.1
Dehaze came in 2015.1 as a global adjustment, and was added as a local adjustment in 2015.2 Where are you looking for it? Are you definitely a CC subscriber, and signed into your account when you're running Lr?
-
Where are you looking for Dehaze?
Helo > System Info shows the version number.
-
I ran into this problem. (ie Dehaze missing). I tried all the usual, including logging out of CC, reboot my Windows PC ....etc.... The Adobe CC app told me I had the latest version of Lrcc. I created a support ticket with Adobe. In prep for a chat session I rebooted my PC, re-logged into CC (use the Help tab to find the Log In option on Windows) and then .... boom .... back in the latest version. Adobe chat could not explain what happened, even though they had remote access to my machine.
The sense I had was that I had launched the non CC version of Lightroom, even though I was using CC for as long as CC has been available.
My assumption ... a glitch with the Adobe sign-on server .....
Another suggestion ... if you are windows ... replace the Lr shortcut from the windows tool bar.
-
This is becoming a bit of a nightmare. I am in the middle of printing for an exhibition. Most of the images were processed in the last version of LR CC before the CC2015.6 version was released - I am on Mac OSX 11. I can't remember now precisely the version number but it was CC2015.5.x. I upgraded to CC2015.6 and have suffered from the printing bug in this release - the prints on my Epson 3880 look like rubbish (and despite what Adobe says I am on the most recent driver for the printer).
So I have tried to roll back to the last release before CC2015.6. This is not available to me through Creative Cloud so I found this link - https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html. You have to download the Application Installer and then the version you want. The only option before CC2015.6 is CC2015.5.1.
However installing that I simply get a splash screen that says it is CC2015 - i.e. no later release. More urgently for me is that this version, whilst it prints fine, does not have the Dehaze option in it. Many of my images have used Dehaze and in the now installed version don't work properly.
Can anyone help in guiding me to somewhere I can get the last release of LRCC before the 2015.6 release?
Thanks
For the same reason as you, I uninstalled 2015.6, reinstalled LR 2015 and then applied the 2015.5.1 update all from this site (http://prodesigntools.com/adobe-cc-2015-updates-links-windows.html#lightroom). Dehaze is there, as expected, under 'Effects'
Cheers
Tim
-
For the Mac:
http://prodesigntools.com/adobe-cc-2015-direct-download-links.html
http://prodesigntools.com/adobe-cc-2015-updates-links-mac.html#lightroom
-
For the same reason as you, I uninstalled 2015.6, reinstalled LR 2015 and then applied the 2015.5.1 update all from this site (http://prodesigntools.com/adobe-cc-2015-updates-links-windows.html#lightroom). Dehaze is there, as expected, under 'Effects'
Cheers
Tim
Fair enough, but in so doing you do without the whole new transform panel, so anyone who had used the new upright tools will lose all those adjustments by rolling back one version. I'm one of those. I did go back to the penultimate version of Photoshop for some urgent diagnostic work, but left the LR install alone. I'll delay non-essential printing till Adobe comes to its senses and fixes all this.
-
Thanks, I tried that - the download file is called setup.dmg which when mounted shows an app called AdobePatchInstaller. Double clicking on that just brings up an error message saying that this update is not for you (i.e. me).
Stumped at the moment.
For the Mac:
http://prodesigntools.com/adobe-cc-2015-direct-download-links.html
http://prodesigntools.com/adobe-cc-2015-updates-links-mac.html#lightroom
-
That is a patch, not a full version. Uninstall the current version of Lightroom like you uninstall any program - either through Applications or through Adobe's CC App. If it asks about Preferences, leave them. Then use the links at Adobe http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015 to download the older version (that Prodesigntools site just recycles Adobe material and links) .
And again, where are you looking for Dehaze? Help > System Info shows the version number.
-
Finally sorted it out with the help of Adobe support. Interestingly they went straight to the Prodesigntools site and pointed me to the same file I had already downloaded. I explained that it didn't work and double clicked it to prove it (for the 4th time). Strangely it worked this time and I now have version 2015.5.1 running which is what I wanted. The Adobe site download file - although saying it was 2015.5.1 only installed the original 2015 release without Dehaze.
I am now back printing and won't be upgrading until I am certain that 2015.6.x really works - pity because I did rather like the guided upright addition.
That is a patch, not a full version. Uninstall the current version of Lightroom like you uninstall any program - either through Applications or through Adobe's CC App. If it asks about Preferences, leave them. Then use the links at Adobe http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015 to download the older version (that Prodesigntools site just recycles Adobe material and links) .
And again, where are you looking for Dehaze? Help > System Info shows the version number.
-
Fair enough, but in so doing you do without the whole new transform panel, so anyone who had used the new upright tools will lose all those adjustments by rolling back one version. I'm one of those. I did go back to the penultimate version of Photoshop for some urgent diagnostic work, but left the LR install alone. I'll delay non-essential printing till Adobe comes to its senses and fixes all this.
Yeah I know Mark. I like those tools.
But I need LR to print and the new version is useless until whoever needs to, sorts out the colour management bug.
;(
Tim
-
I hear you and I agree!! (in spades)
-
Although when I spoke to the Adobe support team they immediately agreed with me that CC2015.6 was flawed in the print module and immediately tried to get me back to a functioning version. So hopefully someone or some persons are actually working on this. Complaints work. So complain away
I hear you and I agree!! (in spades)
-
I hope they know it is Photoshop also.
-
I ended up installing the 2015 version (full install) over the 2015.6 via the prodesigntools. It automatically removed the 'defective' version. Then just download the patch (setup.dmg) file (again from prodesigntools) to bring it up to 2015.5.x. I still get CC trying to convince me to 'upgrade' to 2015.6
-
Just checking: Aside from regressing to a prior LR version, there is no fix for the LR print problem yet, is this correct?
Is it also true that printing to Epson machines from OS X does reliably suffer the ill effects?
Thank you,
John Caldwell
-
I haven't heard of a fix yet nor any communication from Adobe about what the problem is and the ETA of a fix; and yes, poorly colour-managed outcomes printing from both of the latest LR/PS versions is a scientifically repeatable and therefore assured occurrence.
-
I find this extraordinary. Is there no response from Adobe about this issue? Let alone a fix?
I haven't heard of a fix yet nor any communication from Adobe about what the problem is and the ETA of a fix; and yes, poorly colour-managed outcomes printing from both of the latest LR/PS versions is a scientifically repeatable and therefore assured occurrence.
-
I find this extraordinary. Is there no response from Adobe about this issue? Let alone a fix?
Hi,
I'm somewhat amazed as well. I suppose that the subscription model of payment gives them enough confidence that they can take their time without consequences. Although I've not hunted down all their communications about the issue, it seems to be awfully quiet, for several weeks now and counting.
Cheers,
Bart
-
I find this extraordinary. Is there no response from Adobe about this issue? Let alone a fix?
Stay tuned.
-
Stay tuned.
Hi Mark,
If I'm not mistaken, it's you who already hinted at something being announced (released?) tomorrow (on Monday, presumably 12:00 EST, for those in different time-zones).
Why the secrecy? Or did Adobe actually even formally acknowledge that there is an issue, and what the issue was (with temorary work-arounds), beyond a necessary Epson 3800 driver update (that would somehow automagically solve the issue for all printers, even though it seems to be caused by a(n) (future) update of Mac OS Color Management APIs ).
It gives me a hard time advising anyone to use (some of the) Adobe products at the present (even if I use several myself).
Cheers,
Bart
-
I didn't mention anything about Monday - I believe it was Andrew in another thread. It is safe to use the penultimate versions of Photoshop and Lightroom until we hear more.
-
I didn't mention anything about Monday - I believe it was Andrew in another thread. It is safe to use the penultimate versions of Photoshop and Lightroom until we hear more.
Okay, I misinterpreted then (good I asked), some next Monday (or not) it is then ...
Cheers,
Bart
-
For clarity, I'm hoping that late Monday we'll hear something back from all that has been put forward up to now, but I don't know what and I doubt there will be a fix by then.
-
For clarity, I'm hoping that late Monday we'll hear something back from all that has been put forward up to now, but I don't know what and I doubt there will be a fix by then.
Got it.
Cheers,
Bart
-
Can't sleep so wandering around the internet and found your article. Many thanks for the work and effort you put into this.
If, as Adobe say, the fix will not be available until sometime in August then presumably something has gone very wrong. I know nothing about software development but clearly this is not a trivial problem.
Again thanks for your work and persistence.
For clarity, I'm hoping that late Monday we'll hear something back from all that has been put forward up to now, but I don't know what and I doubt there will be a fix by then.
-
Can't sleep so wandering around the internet and found your article. Many thanks for the work and effort you put into this.
If, as Adobe say, the fix will not be available until sometime in August then presumably something has gone very wrong. I know nothing about software development but clearly this is not a trivial problem.
Again thanks for your work and persistence.
You are welcome. Much credit also to Andrew for bringing this issue to our attention and all the testing work he has done on it too.
-
Can't sleep so wandering around the internet and found your article. Many thanks for the work and effort you put into this.
If, as Adobe say, the fix will not be available until sometime in August then presumably something has gone very wrong. I know nothing about software development but clearly this is not a trivial problem.
Again thanks for your work and persistence.
I’m sure Adobe can’t simply “fix” it and then push it out. Some pretty serious testing needs to occur to both make sure it works and doesn’t break something else. Additionally I’m sure they are into the next version, so they need to figure out how to put a hard stop in that version with whatever work has been done, and get the fix added in before they push it out. It’s quite possible the “fix” will include a few other things, maybe just a couple of new camera’s supported, that were in the pipeline.
I’m just glad they finally found the issue and admitted it. Thanks Mark and Andrew.
-
Thank you Mark and Andrew - and LuLa!