Luminous Landscape Forum
Raw & Post Processing, Printing => Adobe Lightroom Q&A => Topic started by: RikkFlohr on July 29, 2015, 12:44:09 pm
-
http://blogs.adobe.com/lightroomjournal/2015/07/lightroom-6-1-1-is-now-available.html
-
Thanks Rikk for the update.
I have the Creative Cloud yet these updates never show up unless I log out and log back into my account.
So much for the CC letting you know about updates.
Stu
-
The Creative Cloud Application doesn't show updates instantly. If it did, the Adobe Servers would be slammed by the auto-updaters of the world. It usually shows up within a few hours of release.
-
The Creative Cloud Application doesn't show updates instantly.
Or sometimes at all ;D
The update mechanism is, well less than ideal to be kind.
-
http://blogs.adobe.com/lightroomjournal/2015/07/lightroom-6-1-1-is-now-available.html
Thanks for the info, looks like the D810 issue was fixed.
I am still curious if LR ever picked up the IQ150? 5.7.1 did not have support for it and it was at least 1 year after the back had been announced. Same as the 250, just a different name on the file, but LR would not open them.
Paul
-
I had to reboot (Windows 7) before the CC app saw the updates. It appears that Adobe runs some apps at boot-up to synch the list of latest apps.
-
I had to reboot (Windows 7) before the CC app saw the updates. It appears that Adobe runs some apps at boot-up to synch the list of latest apps.
It's the same on Mac OS. As I said, it's not necessarily the 'server overload' issue as much as buggy software.
-
It's the same on Mac OS. As I said, it's not necessarily the 'server overload' issue as much as buggy software.
Agreed. The Adobe software to do with CC download and management, and user account management, is still not as good as it should be. Pity Adobe isn't a software company. Oh wait...
-
Along with the expected bunch of new camera and lens profile support, here's the published list of bug fixes:
Bug Fixes:
Unable to merge files to HDR. Please note that this only occurred with DNG files taken with a Leica Monochrom camera.
Enterprise customers were unable to access functionality only available in the Creative Cloud version of Lightroom, such as Dehaze.
People keywords export when they shouldn’t if “Write Keywords as Lightroom Hierarchy” is selected.
Preview generation and export was slower in LrCC/Lr6 than Lr5.
Customers reported that they could not exit full screen after invoking it while spot heal tool is selected.
D810 NEF Files could not select Adobe Standard Profile.
Size adjustment bar moving when clicked but the value listed was not updating accordingly.
Metadata Export setting not working for Track, Square and Grid galleries in the Web Module.
Collection name changes were not properly reflected in other Lightroom clients (such as mobile or web). This only impacted collections enabled for sync.
Incorrect metadata timestamp in a Panorama created in Lr.
Some files in exported batch are Blank with Watermark only.
Lr was not properly exporting all photos. Please note that this typically only occurred when the customer was running Bridge at the same time as the export.
Customers reported seeing a “Waiting for connection” message inside Lightroom when Internet is available.
There is no reference to the dramatic speed slowdown (vs Lr 5.7) or the necessity for many users to uncheck "Use Graphics Processor" in order to make Lr CC run on otherwise powerful up-to-date computers. Also no mention of the buggy issues being experienced by many Wacom users. Does Adobe have a history of quietly slotting in a number of undocumented bug fixes addressing contentious issues? I hope so.
-pw
-
The CC installer is clearly not designed for people who are bandwidth constrained, or pay for Internet by the MB. Adobe does not provide delta updates (downloading only the parts of the application that have changed), and just as bad, if there is any kind of error during the installation you have to re-download the entire application installer, which can be huge (several hundreds of MB). Even a trivial error prompts the CC installer to immediately wipe the installation files it had just downloaded. It's immensely frustrating when this happens.
I tried to install the Lightroom CC update just now and it failed. The install failure is obscure: it couldn't move MXF_SDK_GenericContainer_D10_4.4.33_vs10.dll because it was being used by another process (rather strange considering I ran the installer after a reboot and started no other applications except a web browser).
Do the Adobe engineers / management who are responsible for design and implementation the installer ever consider use cases like this? Do they have any experience of trying to depend on their software when in places where the Internet is not unlimited?
-
The installers and update files are all available here http://prodesigntools.com/ .
It does take a while for the latest files to appear though.
Keith
-
It's the same on Mac OS. As I said, it's not necessarily the 'server overload' issue as much as buggy software.
Yup, definitely buggy software. One of my OS X computers with a CC subscription picked up the latest updates, another required a reboot before it could find them—presumably because one of the Adobe updating processes was blocked (probably by another of the Adobe processes).
And, as I've noticed following other recent Adobe updates, the update mechanism fails to unmount the patches for each product after the update is complete:
/dev/disk2s2 on /Volumes/AdobeCameraRaw-9.1.1-CC-mul-AdobeUpdate (hfs, local, nodev, nosuid, read-only, noowners, nobrowse)
/dev/disk3s2 on /Volumes/Lightroom-6.1.1-Update (hfs, local, nodev, nosuid, read-only, noowners, nobrowse)
This isn't harmful, per se, but it's indicative of sloppy programming.
I wonder if Adobe and its customers would be better served by scrapping the multi-product updater and simply having each application poll for its own updates at launch time or, for apps that have been executing longer than 24 hours, once a day.
-
6.1.1....It seems to run more fluidly and loads 1:1 previews much faster, I installed it today, anyone else noticed this?
Paul
-
6.1.1....It seems to run more fluidly and loads 1:1 previews much faster, I installed it today, anyone else noticed this?
Paul
6.1.1 is definitely faster with IQ180 files in Library module. Moving from image to image is now less than 2 seconds, about 30-40% faster than 6.1(on images that don’t have a lot of metadata changes), and zooming to 100% is faster, and the weird very blurry stage when GPU enabled seems to be dramatically faster, to the point it isn’t noticeable. I don’t have LR 5 loaded any longer, but seems performance is now on par and perhaps even better.
-
After updating still get periodic crashes (perpetual license, Win 7), which never happened with 5.x.
-
This afternoon I've given Lr CC 2015 6.1.1 a tough-test project to chew through on my Win 8.1, i7 3.6 GHz, SSD, 32Gb, nvidia GeForce GTX 770 PC and the dreaded performance issues appear to be unaddressed by Adobe. Checking "Use Graphics Processor" still results in the same clunky performance. Working with a simple Radial Filter CPU usage was a solid 100% with "Use Graphics Processor" checked and around 35% with it unchecked. Export delivers a solid 100% CPU usage with or without "Use Graphics Processor" checked. Overall, if anything 6.1.1 seems worse. I really appreciate the features in Lr CC / 6 but serious work will still need to be done in the flawless performance king, Lr 5.7 (on the same tire-shredding machine).
Sigh...
-pw
-
This afternoon I've given Lr CC 2015 6.1.1 a tough-test project to chew through on my Win 8.1, i7 3.6 GHz, SSD, 32Gb, nvidia GeForce GTX 770 PC and the dreaded performance issues appear to be unaddressed by Adobe. Checking "Use Graphics Processor" still results in the same clunky performance. Working with a simple Radial Filter CPU usage was a solid 100% with "Use Graphics Processor" checked and around 35% with it unchecked. Export delivers a solid 100% CPU usage with or without "Use Graphics Processor" checked. Overall, if anything 6.1.1 seems worse. I really appreciate the features in Lr CC / 6 but serious work will still need to be done in the flawless performance king, Lr 5.7 (on the same tire-shredding machine).
Sigh...
-pw
I would suggest you try a reinstallation of LR, with my Dell XPS15 laptop running an I7, 2.6 Ghz processor, 16GB RAM, a 500GB SSD and GT750M graphics card LR 6.1.1 simply flies. I did some stuff using the radial filter and the processor never went above about 15% (occasional quick leap to 50% for about a second), using the sliders etc for any other changes i.e. sharpening see the processor running around 30-40% while moving the slider, the changes on screen are pretty much instantaneous. In every other respect it is running as smooth as can be expected, exporting etc, zooming to 1:1 is really quick.
I have the "use graphics possessor" on too.
Paul
-
I would suggest you try a reinstallation of LR, with my Dell XPS15 laptop running an I7, 2.6 Ghz processor, 16GB RAM, a 500GB SSD and GT750M graphics card LR 6.1.1 simply flies. I did some stuff using the radial filter and the processor never went above about 15% (occasional quick leap to 50% for about a second), using the sliders etc for any other changes i.e. sharpening see the processor running around 30-40% while moving the slider, the changes on screen are pretty much instantaneous. In every other respect it is running as smooth as can be expected, exporting etc, zooming to 1:1 is really quick.
I have the "use graphics possessor" on too.
Paul
Paul
After updating to the latest Lightroom version I still did not get the performance everyone has been talking about. So I decided to try what you suggested in reinstalling. So I did just that. Uninstalled Lightroom and reinstalled Lightroom CC. All I can say is WOW what a difference. Performance seems to be much better. For the record I am currently using a MacBook Pro (June 2012) 15" Retina with 16GB Ram, 2.6 GHz Intel Core i7, NVIDIA GeForce GT 650M 1024 MB, 512gb SSD. Lightroom Catalog is stored on an external Drobo 5D Thunderbolt Drive with 5, 3TB hard drives. Currently there are over 89,000 images stored on the 5D. Have also now checked the "Use Graphics Processor" that I had unchecked because of poor performance.
Stu
-
Paul
After updating to the latest Lightroom version I still did not get the performance everyone has been talking about. So I decided to try what you suggested in reinstalling. So I did just that. Uninstalled Lightroom and reinstalled Lightroom CC. All I can say is WOW what a difference. Performance seems to be much better. For the record I am currently using a MacBook Pro (June 2012) 15" Retina with 16GB Ram, 2.6 GHz Intel Core i7, NVIDIA GeForce GT 650M 1024 MB, 512gb SSD. Lightroom Catalog is stored on an external Drobo 5D Thunderbolt Drive with 5, 3TB hard drives. Currently there are over 89,000 images stored on the 5D. Have also now checked the "Use Graphics Processor" that I had unchecked because of poor performance.
Stu
Glad you got it sorted, its like they forgot to remove some developers code or something in the early versions then finally took it off in 6.1.1 releasing the full potential. I had to reinstall today to get flickr authentication to work and it even runs better now than before, better then LR5.x so i'm a happy camper.
I actually have my LR photos and Catalog on a WD Elements USB3 portable hard drive and still get excellent performance.
Paul
-
Is the suggestion that the results of an incremental update are different from a full installation?
-
Is the suggestion that the results of an incremental update are different from a full installation?
Not really, I think there were some issues with the i nitial release and 6.1 that were resolved with 6.1.1, I don't know why a reinstallation results in better performance but hopefully going forward the incremental updates will be fine.
Paul
-
Along with the expected bunch of new camera and lens profile support, here's the published list of bug fixes:
Bug Fixes:
Unable to merge files to HDR. Please note that this only occurred with DNG files taken with a Leica Monochrom camera.
Enterprise customers were unable to access functionality only available in the Creative Cloud version of Lightroom, such as Dehaze.
People keywords export when they shouldn’t if “Write Keywords as Lightroom Hierarchy” is selected.
Preview generation and export was slower in LrCC/Lr6 than Lr5.
Customers reported that they could not exit full screen after invoking it while spot heal tool is selected.
D810 NEF Files could not select Adobe Standard Profile.
Size adjustment bar moving when clicked but the value listed was not updating accordingly.
Metadata Export setting not working for Track, Square and Grid galleries in the Web Module.
Collection name changes were not properly reflected in other Lightroom clients (such as mobile or web). This only impacted collections enabled for sync.
Incorrect metadata timestamp in a Panorama created in Lr.
Some files in exported batch are Blank with Watermark only.
Lr was not properly exporting all photos. Please note that this typically only occurred when the customer was running Bridge at the same time as the export.
Customers reported seeing a “Waiting for connection” message inside Lightroom when Internet is available.
There is no reference to the dramatic speed slowdown (vs Lr 5.7) or the necessity for many users to uncheck "Use Graphics Processor" in order to make Lr CC run on otherwise powerful up-to-date computers. Also no mention of the buggy issues being experienced by many Wacom users. Does Adobe have a history of quietly slotting in a number of undocumented bug fixes addressing contentious issues? I hope so.
-pw
I'm intrigued Paul - where did you get this list of bug fixes from? I wanted to see exactly this before downloading the latest version, couldn't find it and Adobe Customer Service stonewalled me. Please see attached track of the "chat" I had with them.
-
Undoubtedly individual experiences vary; in my case I have to say kudos to Adobe. After my initial update to LR CC/6.0, after hearing about all the problems people were having with the early July update, I stayed put and lived without the haze filter or the B and W controls in the adjustment tools.
Once 6.1.1 became available the other day I took the plunge on the presumption that Adobe would have by now addressed most if not all the issues that users previously identified. (It had to be a presumption because they wouldn't provide me the list of bug fixes - see post above.) Meanwhile, over the month of July, every day the Adobe Updater application dutifully nagged me to update, and I dutifully ignored it until Thursday morning.
The CC Updater application updated seamlessly, and the subsequent downloads and installation of both Photoshop CC and LR CC 6.1.1 also occurred seamlessly. I downloaded Photoshop first, using the option to retain the previous install, and that worked fine. The Lightroom update however did not provide the option to retain the previous CC version. (So now I have on my system only my "perpetual license" of LR 5.7 and the latest CC 6.1.1.) However, that turned out to be a non-issue, because the new install is fine. It picked-up my latest LR catalog correctly and the application opened exactly where I had left off from the previous usage. As Wayne noticed, I too see quite a dramatic improvement of application responsiveness; for me it seems to be for all tools using the GPU-enabled option. Everything just responds faster and more smoothly. And my GPU is five years old (ATI Radeon HD 5870 1024 MB).
My computing environment is a Rogers High Speed Internet Broadband connection, MacPro mid-2010, 24 GB 1333 MHz DDR3 ECC RAM, 2 x 2.66 GHz 6-Core Intel Xeon hyperthreaded (24 virtual cores), 2.66 GHz, and 2TB Hitachi internal system drive; OSX Mavericks (10.9.5). It's all out of date, but very performing.
-
where did you get this list of bug fixes from?
http://blogs.adobe.com/lightroomjournal/2015/07/lightroom-6-1-1-is-now-available.html (http://blogs.adobe.com/lightroomjournal/2015/07/lightroom-6-1-1-is-now-available.html)
-
For goodness sakes - then I wonder why this tech support person told me it's internal information and didn't point me there! A case of the right hand not knowing what the left hand is doing.
-
For goodness sakes - then I wonder why this tech support person told me it's internal information and didn't point me there! A case of the right hand not knowing what the left hand is doing.
Tech support had immediate access to the internal information and likely no knowledge of the release docs or anything publicly available. He (?) was also quite likely following his process, procedures and scripts. Its likely that in 5 years you would only get a response from a machine rather than a human.
-
Tech support had immediate access to the internal information and likely no knowledge of the release docs or anything publicly available. He (?) was also quite likely following his process, procedures and scripts. Its likely that in 5 years you would only get a response from a machine rather than a human.
Then bottom line is that their training is inadequate. They should be trained to know what is in the public domain and point the customer to the correct place for the information - like Chris Kern did - and I assume he had to such training from Adobe.
-
Then bottom line is that their training is inadequate. They should be trained to know what is in the public domain and point the customer to the correct place for the information - like Chris Kern did - and I assume he had to such training from Adobe.
That would be nice. I hope you get to sit side saddle sometime with a tech support person to understand what their job is like. If Adobe provides that information in the tools the support person has at hand it would be great but kind of unlikely. Please also keep in mind that tech support people are NOT at the top of the tech food chain. Most are measured and compensated by how long it takes for them to close out a support call or session. Its also quite likely that for an online chat session like yours that they are "chatting" with 4 or more people at the same time. It may also be unlikely that the support person supports only 1 or 2 Adobe products.
There are good reasons that Adobe, Apple, etc. have online forums for their products.
-
I have no doubt their jobs are intense and pressured and I'm not blaming them. I'm blaming their employer. Everything you describe is fixable if they put the resources into it. At the same time the idea of on-line forums is good - they have their place.
-
I have no doubt their jobs are intense and pressured and I'm not blaming them. I'm blaming their employer. Everything you describe is fixable if they put the resources into it. At the same time the idea of on-line forums is good - they have their place.
Yep, you nailed it. All you need is some MBA exec willing to allocate $$$ to improve support. I can see the spreadsheet for the cost-benefit analysis already.
-
Well at last...my Win 8.1, i7 3.6 GHz, SSD, 32Gb, nvidia GeForce GTX 770 PC / Wacom Intuos 6.3.11-4 is managing to run Lr CC 2015 1.1/6.1.1 properly.
It took a reinstall of Lr and ALL the latest updates from NVIDIA. This part was critical. Here's hoping it all holds together.
-
Then bottom line is that their training is inadequate. They should be trained to know what is in the public domain and point the customer to the correct place for the information - like Chris Kern did - and I assume he had to such training from Adobe.
It could be Adobe contract out their technical support to a third party company.