Lr 2015.3 update

[digitaldog]

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.

[Tim Lookingbill]

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.

[digitaldog]

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.

[Tim Lookingbill]

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

[digitaldog]

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.

[jeremyrh]

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?

[Tim Lookingbill]

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.

[Tim Lookingbill]

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.

[digitaldog]

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.

[john beardsworth]

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.

[Tim Lookingbill]

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.

[adias]

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. 😀

[fdisilvestro]

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.

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.

[fdisilvestro]

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.



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



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



The I changed the readouts to LAB in both applications and got the exact same values:

LR (LAB)



ACR (LAB)



Then I changed the profile in ACR to a modified ProPhoto RGB with gamma=1 and got the same results as LR in RGB

[jeremyrh]

Dehaze in local adjustments, and new camera / lens profiles.

Thanks (for reading what my question was, and actually answering it )   :-)

[digitaldog]

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    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.

[digitaldog]

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!

[seamus finn]

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?

[digitaldog]

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.

[Hans Kruse]

After restarting my iMac, I got the November update via CC App. Updated without a glitch.

Same for me.