Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: rdonson on November 17, 2015, 10:13:10 am
-
I just updated Lr through CC and the old Import has returned. The update is said to also include bug fixes.
-
I just updated Lr through CC and the old Import has returned. The update is said to also include bug fixes.
Thanks for that. So it's safe to go back in the water again.
Jeremy
-
See this post (http://blogs.adobe.com/lightroomjournal/2015/11/lightroom-cc-2015-3-6-3-now-available.html).
It may take a few hours to show up in your CC application in different locations.
-
Sooner than I expected. And everything seems to work as it should.
Thanks for listening, Adobe people.
-
I just updated Lr through CC and the old Import has returned. The update is said to also include bug fixes.
You need to read carefully before you accept the update! It states it's the October update which is the update that caused all the issues with Import in the first place. Yes, it's annoying to be told every few days about this update, check to see it's not the correct one then wait. But that's about all we can do.
(http://digitaldog.net/files/update.jpg)
-
::sigh::
It is totally broken for me on OS X. I just get a grey window (no grid or anything), and a console full of these:
11/17/15 9:02:30.240 AM Adobe Lightroom[2602]: Failed to restore first responder (message was isBezelWindow) NOT KEY
11/17/15 9:02:30.341 AM Adobe Lightroom[2602]: Failed to restore first responder (message was isBezelWindow) NOT KEY
11/17/15 9:02:30.442 AM Adobe Lightroom[2602]: Failed to restore first responder (message was isBezelWindow) NOT KEY
11/17/15 9:02:30.546 AM Adobe Lightroom[2602]: Failed to restore first responder (message was isBezelWindow) NOT KEY
11/17/15 9:02:30.646 AM Adobe Lightroom[2602]: Failed to restore first responder (message was isBezelWindow) NOT KEY
I really didn't have problems in the past, but the 6.2 and later releases have really shaken my faith in this damned program.
-
Gotta love how poorly the CC upgrade mechanism is still not working. I rebooted my Mac hoping CC would 'see' today's update, a process that worked in the past. No go, now it shows no updates for LR. Sigh.
-
See attached installation instructions, from:
http://blogs.adobe.com/lightroomjournal/2015/11/lightroom-cc-2015-3-6-3-now-available.html
-
The instructions don't let the CC updater off the hook.
Rebooted again, waited about 5 minutes, now I'm shown the update. So in one location, Adobe tells us we're updating to 6.3 but after updating and wishing to confirm it was done, I'm shown this dialog after selecting "About Lightroom" (confusing) but of course it should be clear to all that 2015.3 release is also version 6.3. Sigh....
(http://digitaldog.net/files/LR_version.jpg)
Also, is this a UI bug? Why would the Fill dropdown be blank? There IS a default item in the dropdown list.
(http://digitaldog.net/files/LR_Fill.jpg)
-
Andrew,
I get values in that Preferences>Interface box on both Windows and Mac. (Win 7 and 10.9.5) Six Choices from Black to White...
-
I'll wait a few more days to see what else hits the fan before I try it.
-
I get values in that Preferences>Interface box on both Windows and Mac. (Win 7 and 10.9.5) Six Choices from Black to White...
I get the values in the dropdown after clicking on it, I don't get anything in the dropdown initially. Why? I don't recall ever seeing a dropdown menu with nothing in it as shown in my screen grab. So bug or feature? If feature, why? If bug, more sloppiness on Adobe's part.
-
In the Adobe announcement comments, there's a statement that the import previews have a greyed appearance and a large checkmark for those that are new, but the previously imported photos are not greyed out. The poster wrote:
"Thanks for restoring some of the functionality (and there are improvements like being able to pick up keywording (I don’t think that was there before. However, I find the shaded previews with the big tick completely unhelpful. Is there a way of turning this off so that NEW photos are as before (bright) and PREVIOUSLY imported are the ones that are shaded. This works SO much better for me."
Is this true?
Tom Frerichs
-
The instructions don't let the CC updater off the hook.
Rebooted again, waited about 5 minutes, now I'm shown the update.
Yes, restarting (Mac ElCapitan) woke up the CC updater. Geez, why can't it at least wake up when Mac wakes from sleep? Or better when you switch from Home to Apps, it could call home and check for updates?
-
After restarting my iMac, I got the November update via CC App. Updated without a glitch.
-
After update, import dialog greatly improved:
An internal error has occurred,
Could not find namespace: AgImportScanningService
This happens on clicking Import, after app restart, Mac restart, ...
-
I get the values in the dropdown after clicking on it, I don't get anything in the dropdown initially. Why? I don't recall ever seeing a dropdown menu with nothing in it as shown in my screen grab. So bug or feature? If feature, why? If bug, more sloppiness on Adobe's part.
I have values pre-populated prior to clicking on both OS's. Without testing on your precise OS, it is hard for me to test but I am leaning towards a preference file issue. Have you reset?
-
Gotta love how poorly the CC upgrade mechanism is still not working. I rebooted my Mac hoping CC would 'see' today's update, a process that worked in the past. No go, now it shows no updates for LR. Sigh.
This is why I purchased standalone Lr6 and not CC. I still got the annoying CC updater and found a way to remove it from my machine.
-
Without testing on your precise OS, it is hard for me to test but I am leaning towards a preference file issue. Have you reset?
FWIW, 10.11.1. No didn't reset preferences, I see no reason to do so. Maybe someone else will see this, not a big deal but apparently another bug.
Speaking of bugs, the color number bug introduced in LR6 is still not fixed! WTF? Photoshop, LR5 and ACR all report the values correctly. LR6 is a mile off.
(http://digitaldog.net/files/LR6numberbug.jpg)
Does TH have anyone on LR6 beta checking color stuff any more? Or he doesn't listen to them either.... :'(
-
I long thought Adobe should recruit new beta testers. I suspect they had a click of testers with narrow experience, although highly vocal and dismissive of other people's experience.
I am an engineer and offered to beta test but was told the beta group was full!?! Having experience in the industry I did not understand a numbers limited beta test group. You admit many and filter from there...
-
I long thought Adobe should recruit new beta testers. I suspect they had a click of testers with narrow experience, although highly vocal and dismissive of other people's experience.
As one who was involved (pre 1.0 to 5.0), that's not my experience. I can say, it helps to avoid telling the PM stuff you don't think works well if you hope to be invited back.
-
Just want to clarify that in no way does this thread erode my trust in Adobe.
And I now see how the subscription model makes perfect sense. Beta testers now have to PAY to be testers.
End sarcasm.
-
And I now see how the subscription model makes perfect sense. Beta testers now have to PAY to be testers.
How does the subscription model per se have any bearing? Non subscription software, even those from Adobe in the past didn't behave any differently as far as I can see.
-
Andrew, lighten up.
Whether subscription or perpetual license, users are always going to continue to pay for their software both in time and money, just not in the way they planned.
Your input of your experience of a simple download update makes it sound worse than Thom Hogan's rant linked to in another LuLa thread.
http://forum.luminous-landscape.com/index.php?topic=105446.0
-
Andrew, lighten up.
Typical Tim Lookingbill answer to a reasonable question about his post.
Never mind, it wasn't worth the read, let alone the consideration for clarification.
-
So anyway, after all this, what is the difference between this version, with the "old" import procedure restored, and the last working version i.e. the one before the update with the "new" import procedure?
-
Typical Tim Lookingbill answer to a reasonable question about his post.
Never mind, it wasn't worth the read, let alone the consideration for clarification.
Clearly sarcasm is new to you.
But right now I bet you wish you had Thom Hogans problems compared to what you're going through. WTF!? as you put it which I totally agree.
-
So anyway, after all this, what is the difference between this version, with the "old" import procedure restored, and the last working version i.e. the one before the update with the "new" import procedure?
There's a link to Adobe's site provided in this thread that will tell you this.
-
But right now I bet you wish you had Thom Hogans problems compared to what you're going through. WTF!? as you put it which I totally agree.
The difference is, this bug has been around AND reported since April.
-
So anyway, after all this, what is the difference between this version, with the "old" import procedure restored, and the last working version i.e. the one before the update with the "new" import procedure?
Dehaze in local adjustments, and new camera / lens profiles.
-
Generally speaking I'm expressing my concern over this new and only way to update thousands of user's apps (not just Adobe's) by rearranging that app's directory integration with the system OS through the internet using proprietary download managers & installers.
Just yesterday I got a security update for Firefox browser where all I had to do is restart Firefox for it go into effect. Got the friendly dialog box pop up of the procedure happening without my knowledge because I have its update preference set that way. The only problem is now it takes Firefox nearly 30 seconds to quit until I have to do a force quit. Restart computer and all is well. Nothing to explain why this happens.
No way of knowing the cause of the problem. Nothing is transparent in all these downloading procedures in seeing what it is doing to each of our systems. But this is how it's going to work from here on out. Nothing we can do about it but rely on the pristine process of sending data through the internet and having an update/install software put it in the right place on our computers and mobile devices.
-
As one who was involved (pre 1.0 to 5.0), that's not my experience. I can say, it helps to avoid telling the PM stuff you don't think works well if you hope to be invited back.
I tell it as I see it, honestly. No PC for me in general and even less professionally. And... besides I no longer have an interest in beta testing. Adobe has all its CC subscribers for that. 😀
-
Hi, Just updated LR with no issues, except the almost-non-issue of a blank value in the dropdown.
The short solution: just select a value from the dropdown
Also, is this a UI bug? Why would the Fill dropdown be blank? There IS a default item in the dropdown list.
(http://digitaldog.net/files/LR_Fill.jpg)
What I found:
In the preferences file, the background color of the user interface and secondary monitor are defined by the following variables:
AgCommonUI_backgroundShade
AgMultiMonitor_backgroundShade
In some cases the previous version had 0.5 as the default value for both variables while the latest one just do not include the variable in the preferences file when the default is selected.
So there is no need to reset preferences or edit the preferences (it is just a plain text file anyway), just select the desired value in the droprowns.
-
FWIW, 10.11.1. No didn't reset preferences, I see no reason to do so. Maybe someone else will see this, not a big deal but apparently another bug.
Speaking of bugs, the color number bug introduced in LR6 is still not fixed! WTF? Photoshop, LR5 and ACR all report the values correctly. LR6 is a mile off.
(http://digitaldog.net/files/LR6numberbug.jpg)
Does TH have anyone on LR6 beta checking color stuff any more? Or he doesn't listen to them either.... :'(
Well from the tests I have made, the values shown by LRCC are not wrong, but maybe they are not the values that you expect. It seems that the RGB values shown correspond to the internal color space (Melissa if I'm not mistaken) or a color space with ProPhotoRGB Primaries and Gamma=1.
First, the values in RGB appear only in soft proof and they don't change regardless of the output color space selected. I used the same color patch (red) from the CC 24 and got the following values (no edits):
R=96; G=27; B=16
(http://www.frankdisilvestro.com.au/img/s5/v123/p1635155928-3.jpg)
I opened the same raw image in ACR with no edits, set to Adobe RGB and got the following values:
R=185; G=62; B=68
(http://www.frankdisilvestro.com.au/img/s3/v42/p1660054451-3.jpg)
The I changed the readouts to LAB in both applications and got the exact same values:
LR (LAB)
(http://www.frankdisilvestro.com.au/img/s7/v153/p1848368080-3.jpg)
ACR (LAB)
(http://www.frankdisilvestro.com.au/img/s11/v36/p1878561731-3.jpg)
Then I changed the profile in ACR to a modified ProPhoto RGB with gamma=1 and got the same results as LR in RGB
(http://www.frankdisilvestro.com.au/img/s4/v10/p1780738025-3.jpg)
-
Dehaze in local adjustments, and new camera / lens profiles.
Thanks (for reading what my question was, and actually answering it ) :-)
-
Well from the tests I have made, the values shown by LRCC are not wrong, but maybe they are not the values that you expect. It seems that the RGB values shown correspond to the internal color space (Melissa if I'm not mistaken) or a color space with ProPhotoRGB Primaries and Gamma=1.
That's wrong ;D that's the bug!
IF you examine LR5 or earlier, you'll see the values (which do match Photoshop and ACR) are supposed to be from the profile you selected from the soft proof, NOT MelissaRGB.
It make zero sense to show MelissaRGB from the soft proof. We can do that outside of the soft proof although it's questionable if that's useful since that's not what we get out of LR unless you specifically build a ProPhoto RGB linear ICC profile for export.
It's a bug.
-
In the preferences file, the background color of the user interface and secondary monitor are defined by the following variables:
some cases the previous version had 0.5 as the default value for both variables while the latest one just do not include the variable in the preferences file when the default is selected.
Thanks for confirming yet another bug. Clearly it's not supposed to appear blank!
-
Everything ok with the update but my slide module doesn't work. It didn't work in the last version either but was fine in version 6. A voice in the wilderness: any suggestions?
-
Everything ok with the update but my slide module doesn't work. It didn't work in the last version either but was fine in version 6. A voice in the wilderness: any suggestions?
Specifically what's not working? I am able to run a Preview of a previous built slide show on this end.
-
After restarting my iMac, I got the November update via CC App. Updated without a glitch.
Same for me.
-
So anyway, after all this, what is the difference between this version, with the "old" import procedure restored, and the last working version i.e. the one before the update with the "new" import procedure?
Bug fixes and e.g. the dehaze in local adjustments.
-
That's wrong ;D that's the bug!
IF you examine LR5 or earlier, you'll see the values (which do match Photoshop and ACR) are supposed to be from the profile you selected from the soft proof, NOT MelissaRGB.
It make zero sense to show MelissaRGB from the soft proof. We can do that outside of the soft proof although it's questionable if that's useful since that's not what we get out of LR unless you specifically build a ProPhoto RGB linear ICC profile for export.
It's a bug.
I agree with you that one would like to see the values of the output profile and not those from MelissaRGB. In your previous post I got the idea that the numbers were just off by a random error, that's why I tested it. My guess is that when they allowed in LR6/CC to softproof to CMYK profiles, they (Adobe) had not solved yet how to show the CMYK values and histogram (it would require a slight change in the layout) and opted to use the internal or input profile values. Hopefully this will be solved in future versions.
-
I agree with you that one would like to see the values of the output profile and not those from MelissaRGB.
That's how it used to work. And LR6 should work. It is not like Adobe wasn't made aware of this back in April. Sad.
-
That's how it used to work. And LR6 should work. It is not like Adobe wasn't made aware of this back in April. Sad.
Since April? ... Kind a makes you wonder if they expended the resources tied up in 'simplifying and streamlining' the import dialog .... Then all the extra effort to 'fix' that issue over the past month or so ... Maybe these existing bugs could have been squashed by now.
-
In the Adobe announcement comments, there's a statement that the import previews have a greyed appearance and a large checkmark for those that are new, but the previously imported photos are not greyed out. The poster wrote:
"Thanks for restoring some of the functionality (and there are improvements like being able to pick up keywording (I don’t think that was there before. However, I find the shaded previews with the big tick completely unhelpful. Is there a way of turning this off so that NEW photos are as before (bright) and PREVIOUSLY imported are the ones that are shaded. This works SO much better for me."
Is this true?
Tom Frerichs
Further down you will see several posters state that the update restored the original grid view and check mark system. not sure what was wrong with the person who posted what you quoted.
-
Just a thought but was wondering whether Adobe should strictly separate bug fixing update releases from upgrades that add, change or take away features and GUI design in order to reduce the sort of issues outlined in this thread. Not sure if this is how it's already implemented since I'm not sure how all this upgrade/update stuff works across thousands of user's systems over the internet.
The more features added to these apps, the more complex they seem to become with further complexity integrating with various systems and OS's where making smaller changes in update increments that fix bugs (first) should be adopted with upgrade feature changes provided as a separate option. At least it puts more of the control into the user's hands.
-
Just a thought but was wondering whether Adobe should strictly separate bug fixing update releases from upgrades that add, change or take away features and GUI design in order to reduce the sort of issues outlined in this thread. Not sure if this is how it's already implemented since I'm not sure how all this upgrade/update stuff works across thousands of user's systems over the internet.=
Yes, that's been the behavior from the day they offered perpetual vs. subscription of LR. Perpetual licenses only get bug fixes and new camera support, no new features. Subscribers get both.
-
Andrew, are you finding more or less issues or any differences in levels of quirkyness between subscription vs Perpetual License update/upgrade routines?
I haven't had any problems with the perpetual license route on the level seen in this thread but I haven't moved forward to subscription or even the PL models to get any clear idea.
There's always been someone posting online about bug issues in the past under PL so maybe there hasn't been enough time to make an accurate assessment under the subscription model.
I'm still hanging on to the "if it ain't broke, don't fix it" way of managing my workflow.
-
Andrew, are you finding more or less issues or any differences in levels of quirkyness between subscription vs Perpetual License update/upgrade routines?
I'm on CC since LR6 so not a lot of experience. I'm seeing a couple new features but otherwise what you get from perpetual and I get are the same. The LR6 experience hasn't been anything to write home about between the Import issue now fixed and bugs that I've seen since it's release not yet fixed. One thing I can admit, I'm keeping LR5 around and keeping that catalog updated as I add new images to LR6, just in case.
-
Andrew, are you finding more or less issues or any differences in levels of quirkyness between subscription vs Perpetual License update/upgrade routines?
I haven't had any problems with the perpetual license route on the level seen in this thread but I haven't moved forward to subscription or even the PL models to get any clear idea.
There's always been someone posting online about bug issues in the past under PL so maybe there hasn't been enough time to make an accurate assessment under the subscription model.
Remember that the two versions are the same code, just that their different features become visible depending on how the user licences the program.
-
Further down you will see several posters state that the update restored the original grid view and check mark system. not sure what was wrong with the person who posted what you quoted.
Thanks...I admit that I hadn't gone back to read further postings. I guess it's now safe to upgrade, but I'll also admit that I was waiting for the early adopters to tell me what, if anything, was broken this time. :D
Tom
-
I noticed that the performance preference to use a GPU was checked in the .3 release (I had it unchecked). This resulted in building 1:1 previews for a couple of hundred images not completing after running overnight. Unchecked it, and it works fine again.
-
Perpetual licenses only get bug fixes and new camera support, no new features.
Well that's not correct. The perpetual version was also subject to the 'new feature' of the crippled import dialogue.
It's this sort of nonsense that makes people lose trust in Adobe, not silly programming issues as discussed in another thread.
-
Now you put me into a difficult situation, I don't know whether to cry or laugh ..
Well that's not correct. The perpetual version was also subject to the 'new feature' of the crippled import dialogue.
-
Well that's not correct. The perpetual version was also subject to the 'new feature' of the crippled import dialogue.
It's this sort of nonsense that makes people lose trust in Adobe, not silly programming issues as discussed in another thread.
Adobe did not consider the 'improved' import dialog as a 'new feature' but an update to an existing feature.
-
So what do you think? It's time to upgrade or not?
-
Adobe did not consider the 'improved' import dialog as a 'new feature' but an update to an existing feature.
Yup, a bad one.
-
I just finished updating my windows 7 desktop and windows 8.1 laptop. The update moved very quickly and both systems appear to be running nominally. Interface to 3rd party software also working properly.
-
I just finished updating my windows 7 desktop and windows 8.1 laptop. The update moved very quickly and both systems appear to be running nominally. Interface to 3rd party software also working properly.
Same here.
-
So what do you think? It's time to upgrade or not?
Victoria Bampton says it's safe to upgrade (http://www.lightroomqueen.com/whats-new-in-lightroom-cc-2015-3-and-lightroom-6-3/): that no serious new bugs were introduced in this release. She also provides a link to the standalone Adobe patch installer, which she says is a safer way to get the new rev than using Lightroom's pull-down menu selection.
-
Victoria Bampton says it's safe to upgrade (http://www.lightroomqueen.com/whats-new-in-lightroom-cc-2015-3-and-lightroom-6-3/): that no serious new bugs were introduced in this release. She also provides a link to the standalone Adobe patch installer, which she says is a safer way to get the new rev than using Lightroom's pull-down menu selection.
Thank you Chris. :)
-
I've just updated to 6.3 on W7 and all has gone well.
It appears that the panorama merge feature works more reliably now with a higher success rate.
-
It appears that the panorama merge feature works more reliably now with a higher success rate.
I was curious about the panorama bug fixes. The release notes didn't provide any details. By "higher success rate," do you mean you are seeing fewer stitching errors?
-
By "higher success rate," do you mean you are seeing fewer stitching errors?
Yes, I haven't had enough time to fully test it, but a few sets that failed to be aligned properly now seem to be joined up better.
There are still some smaller errors too though.
-
Big Improvement.
Since upgrading to 2015.3 everything has worked perfectly and very speedily. (W7, i7, 16Gb)
It's easy to be critical when things go wrong - so we should be equally ready to praise when things go right.
Well done, Adobe!
-
praise when things go right.
Praise ?? It's only a bug fix and compatibility release. There's still loads wrong with 6x that hasn't been fixed or works less than perfectly.
-
Praise ?? It's only a bug fix and compatibility release.
Yes, but praise should still be given.. Compare the LR folks to the Capture One folks who say all deficiencies in C1 are why it's better. ::)
I'll add some too. The HDR became night-and-day better in x.2, and speed seemed a bit better in x.2.1 compared to x.1 and earlier.
There's still loads wrong with 6x that hasn't been fixed or works less than perfectly.
Very true. But it's been that way since when I started with LR4, with many still existing to this day. ???
-
Praise ?? It's only a bug fix and compatibility release.
The one thing I think Adobe does deserve credit for is publicly admitting how badly they botched the 2015.2 release. Hopefully, that's a portent of changed behavior in the future.
-
Praise ?? It's only a bug fix and compatibility release. There's still loads wrong with 6x that hasn't been fixed or works less than perfectly.
Show me anything...anything at all that works perfectly. Are you perfect?
-
The one thing I think Adobe does deserve credit for is publicly admitting how badly they botched the 2015.2 release. Hopefully, that's a portent of changed behavior in the future.
Yes, we've had camera manufactures which had major issues with their equipment and never admitted to their mistakes. It takes courage in the corporate culture to admit to a mistake and fix it promptly. I give credit where credit is due...well done Adobe.
-
Yes, we've had camera manufactures which had major issues with their equipment and never admitted to their mistakes.]
Ahhh, another D800/D800E owner?
-
Are you perfect?
No, but I don't expect praise.
-
Ahhh, another D800/D800E owner?
Nope...was part of the 1d3 fiasco.
-
No, but I don't expect praise.
I don't think Adobe is expecting praise as this was a royal f'up...I'm giving them praise in the way they handled it.
-
...I'm giving them praise in the way they handled it.
Once again, I'll go with a 'Yes and no' on that aspect.
Yes, they 'handled it' ... in a reasonable fashion after they were pummeled by a dam burst of dissatisfaction.
No, on their first statements and conversations with users was more or less for everyone to get over it because the new Import dialog was staying and they saw no reason to restore the functionality they arbitrarily removed.
It wasn't until the floodgates opened as they never have before on the feedback forum that Hogarty realized the depth and breadth of the situation and just how serious the problem was. It was then, and only then, they found their good graces and went to work restoring what they had broken. To me, with that first instinct, they revealed a mindset that did little to convince me they really have a handle on what we users desire and consider potentially valuable in a software solution like Lightroom.
While I give them credit for finally seeing the light, they are going to have to accumulate a new proven track record before I dole out any actual 'praise' ... They are going to have to prove to us all they have broken the cycle that created the issue and get back in touch with what we really strive for instead of tracking only a small percentage of data points that do not accurately portray reality.
-
I thought they were going to keep the new look, but put the removed functionality back(folder preview, eject, and no big-ass checkmarks).
I rather liked the new look... Just not the removed functionality so much.
-
Victoria Bampton says it's safe to upgrade (http://www.lightroomqueen.com/whats-new-in-lightroom-cc-2015-3-and-lightroom-6-3/): that no serious new bugs were introduced in this release. She also provides a link to the standalone Adobe patch installer, which she says is a safer way to get the new rev than using Lightroom's pull-down menu selection.
My ears were burning. ::) Yeah, 2015.3/6.3's still looking pretty good. A couple of reports of problems installing, fixed by uninstalling and reinstalling. A few people getting an 'error changing modules' trying to open Slideshow, many fixed by reinstalling, some still in progress. A couple of people having issues importing videos, under investigation. And some memory cards showing in the Files section of the Import dialog instead of the Devices section, so missing the Eject button. We're back to a 'normal' level of bugs.
As one who was involved (pre 1.0 to 5.0), that's not my experience. I can say, it helps to avoid telling the PM stuff you don't think works well if you hope to be invited back.
It's all in the way you say it Andrew... ;) Not that they listened on the Import debacle, but I'm hoping they've learned a lesson.
-
I have updated to 6.3 on Mac OSX 10.11.1. and everything seems to work fine. Even a glitch, that I had with the sliders, has gone...
I am very satisfied.
-
Thanks for updates, people.
-
There seem to be enough reports now that the new update is viable, so perhaps I will try to get my courage up to try it soon. I think I'll need a crisis management team on speed dial just in case...
-
I have a perpetual license for LR6
Never updated to 6.2, so went straight from 6.1 to 6.3
Two problems:
- First my "Adobe Application Manager/Updater" disappeared at my first update attempt, had to download/reinstall that manually. It never completed the update to 6.3 the first time (remained on 6.1) and pressing "update" again in the help drop-down created a little disk activity but no update window popped up.
- All my camera default import settings were gone after the update (I have default settings for all my cameras with custom colour profiles and slightly adjusted develop settings). They were all back to the Adobe standard import settings.
Anybody else had any of these problems, or were these one-offs on my system? (I'm on Windows 8.1)
-
I have a perpetual license for LR6
Never updated to 6.2, so went straight from 6.1 to 6.3
Two problems:
- First my "Adobe Application Manager/Updater" disappeared at my first update attempt, had to download/reinstall that manually. It never completed the update to 6.3 the first time (remained on 6.1) and pressing "update" again in the help drop-down created a little disk activity but no update window popped up.
- All my camera default import settings were gone after the update (I have default settings for all my cameras with custom colour profiles and slightly adjusted develop settings). They were all back to the Adobe standard import settings.
Anybody else had any of these problems, or were these one-offs on my system? (I'm on Windows 8.1)
The same exact situation happened to me and I am running OS X 10.11.1.
-
I have a perpetual license for LR6
Never updated to 6.2, so went straight from 6.1 to 6.3
Two problems:
- First my "Adobe Application Manager/Updater" disappeared at my first update attempt, had to download/reinstall that manually. It never completed the update to 6.3 the first time (remained on 6.1) and pressing "update" again in the help drop-down created a little disk activity but no update window popped up.
- All my camera default import settings were gone after the update (I have default settings for all my cameras with custom colour profiles and slightly adjusted develop settings). They were all back to the Adobe standard import settings.
Anybody else had any of these problems, or were these one-offs on my system? (I'm on Windows 8.1)
I also update from 6.1, using the patch given in previous page. No problem for me, but I'm on Win 7
-
I have a perpetual license for LR6
Never updated to 6.2, so went straight from 6.1 to 6.3
Two problems:
- First my "Adobe Application Manager/Updater" disappeared at my first update attempt, had to download/reinstall that manually. It never completed the update to 6.3 the first time (remained on 6.1) and pressing "update" again in the help drop-down created a little disk activity but no update window popped up.
- All my camera default import settings were gone after the update (I have default settings for all my cameras with custom colour profiles and slightly adjusted develop settings). They were all back to the Adobe standard import settings.
Anybody else had any of these problems, or were these one-offs on my system? (I'm on Windows 8.1)
I updated from 5.2.7 to 6.2 (to get Batis lenses profiles), and last weekend to 6.3. No problem, with W7.
-
Finally getting round to updating 6.3
Now what is the best way? Via the LR updates or using the download linked from the adobe blog about 6.3 ??? The likes of LR Queen and Laura Shoe plus some blog posters appear to advise using the downloaded installer.
-
Finally getting round to updating 6.3
Now what is the best way? Via the LR updates or using the download linked from the adobe blog about 6.3 ??? The likes of LR Queen and Laura Shoe plus some blog posters appear to advise using the downloaded installer.
Anyone who has had problems with one method will probably advise the other. FWIW, I updated from 6.1CC using the CC updater and it worked perfectly first time on both my Macs, under El Capitan.
Jeremy
-
I have stand-alone LR 6.1 and the last pre-CC PS.
I was (fortunately) away when LR 6.2 came out, and the brown stuff had hit the fan in earnest by the time I got home, so I skipped that downgrade.
A few days a go I took my chances on updating from inside LR 6, in the Help menu, "Check for updates." It worked perfectly fine for me (Windows 7 64)., with no unseemly effects so far.
So it may be safe to go in the water again.
-Eric
-
Now what is the best way? Via the LR updates or using the download linked from the adobe blog about 6.3 ??? The likes of LR Queen and Laura Shoe plus some blog posters appear to advise using the downloaded installer.
It's only a matter of speed. The direct links are available immediately.