A Gold medal please for the person who worked out (at last) how to get LR to use Windows memory - 17GB in use and counting at present.
I'm rendering 1:1 nefs with all 12 cores on full throttle, and after 30 mins NO SLOW DOWN! Amazing!!!
I can predict the new threads - 'LR has blown up my CPU', 'MY CPU is overheating', 'The noise from my cooling fan is intolerable', etc, etc. Perhaps you had better write a note on 'HOW to slow LR down and save your cpu'!!!
It'll be champagne tonight at Valentine's Day Dinner - Adobe we love you ;)
A much less grumpy old man,
The R/A and Y/Y options display properly, the image also shows correctly while cropping.
The first switching into develop mode and (new in 7.2) switching between images in one folder works correctly.
So only the normal development screen with GPU enabled and a change of folders has this issue.
There has to be a possibility to nail it down to the differences in this very case...
lightroom still i have to use viewfinder on camera
From all your smart programmers this is what you could come up with? Just make us go buy more RAM with the RAM prices so high? This is a foolish patch and I am very sure that you could find a better solution to speed up Lightroom than forcing the program into a memoryleak and take over all the system memory INCLUDING WINDOWS MEMORY
Improving these speeds is an important goal for LR - but there are many other aspects as well - it's not just a question of eliminating a spinning beachball in Develop or reducing import and export times. It is the end-to-end timesaving that come from a number of improvements that, at the end of the day, will get the whole job done.
I would like to suggest these enhancements in workflow and the user interface.
1. Consider the screen organization and UI. LR has always had a quirky organization with so many hidden disclosure triangles. etc. And the scrolling, the interminable scrolling to move folders or images or navigate to different places. Instead, use a classic windows approach and allow the collections and folders and develop panels to be broken off into separate manageable windows - with multiple views or instances so we can spread them across our screens (maybe more than 2 !)- then be able to drag and drop from one to another. Or park and organize your favourite Develop subpanels for easy access. The new Favourites feature assists with this - but wouldn’t it be simpler and more traditional to just be able to open the folder tree in a couple of windows in Library and drag between them or drags photos into them ?
2. From the Library, allow a right-click "Add to Collection" from a dropdown list of favourites or recents. Yes, you can use Quick Collection but when distributing the results of a shoot to different collections that is no solution and having to endlessly scroll the collections panel to get to the target is so tedious. So, similarly to the new Favourites feature for Folders, allow specific Collections to be marked as Favourites, too, then you can right-click, Add to Collection | Favourite and cherry pick from the list. Huge time saver.
3. LR is being used increasingly for complex tasks with brushes, spotting, gradients. Implement a new list-oriented view of the tools/brushes/gradients used in an image more like Layers in PS where you can see all the masks, gradients or spots you have entered in a list so you can rename then and (re)select them quickly. If you have done extensive work on an image and come back and revisit it, it's hard to find the adjustment if there are several. If you SYNC all these to a similar photo, some specific adjustments (like placement of brushes and gradients) may need re-tweaking positionally so it would be helpful to locate "Lighten Tree" and move it or fine tune it on the new image. Allow the individual ones to be turned off/on and this would be a great spot to put that overall level slider so you can 'dim' the combined effect without having to collapse the panel then locate the slider and adjust it.
4. We are using LR in photo competitions, to centralize data and try to get judging responses on-line remotely. You are almost there but your mobile/web apps do not allow us to publish selected IPTC fields and enter them on the web - other than Comments. And you can't export the collected comments - they are locked into the CC eco structure and there is no automatic way to move comment data into IPTC fields. Imagine getting photo comments on 300 photos and then having to manually scan that, and copy-type the responses into the IPTC fields you can elsewhere access in the software. Mind numbing.
5. LR is a database - allow us to simply define new fields and then define some simple relationships between them - for example, allow me to define 3 score fields and a total field which is the sum of the 3 ... simple stuff like that.
and while we are on this, make each and every field within the LR SDK available in watermarks, file titles, in export etc. You make some available but not all ... you don't have to expose all of them in the same dropdown - they could be in sub-menus ... but we spend a lot of time putting stuff into LR fields and then trying to get that communicated to other software and we have to bastardize the use of the fields because we can get to some IPTC data but not all of it. Make each one available if it's the SDK and allow us to simply create out own.
Stating this another way, you provide for smart collections using ‘Searchable IPTC’....that’s too general and global and picks up instances of a search target from IPTC fields I may not want. For example, if I want to search City for “Toronto” - but City, itself is not available as a smart collection field ... instead, when I search ‘Searchable IPTC’ I find not only images with Toronto in the city field - but also Toronto in the image title, caption and other places I don’t want. Hours can get wasted trying to filter this out.
And just what does ‘Searchable IPTC’ comprise - what fields doe it search / not search. Too ambiguous for a real database.
LR is a real database - so let’s not dumb it down to a ‘simple’ level that becomes dysfunctional.
These are the kinds of things that will make LR faster for us - yes, pure performance is part of it - but the other tasks are important too.
With the version before the new release I would build 1:1 previews and my iMac’s fan would go at full blast!
With the new update, this doesn’t happen anymore. So I was VERY happy.
The problem is, that it doesn’t seem to be doing anything. Only using a little more than 1 core.
The progressbar was in the same location for 3 hours so I stopped the process.
Lightroom also became very slow in juist building up the folder structure.
I see the folder names go from grey to white 1 folder at a time, unbearably slow.
I truly don’t understand the amount of bugs that show up on each new release.
Hopefully I am not the only one and this will be fixed swiftly.
In the end, Lightroom is now slower than before this release.
I am on a 2017 iMac with 4x4.2 processors and 64GB ram.OSX 10.12.6
Now if we can only get it to work properly. Most everything else seems to be functioning pretty normal for me since the update but if I try to use the folder search everything goes to hell. First it is super slow and unresponsive... it takes about 30 seconds to return any results. Then after I have tried to use it all other areas of Lightroom start bugging out. Cannot rotate photos, cannot label or tag, I get a spinning wheel. I can browse around and etc. like normal but the system logs Lightroom as "not responding" eventually I have to force quit Lightroom and relaunch the program. Then everything is normal until I try to folder search again. Then repeat the whole process above. Guess I will have to stay out of the awesome new "feature" until Adobe gets it resolved.
One other note while we are at it. The progress bars for export behavior has changed and I do not like it. The progress bar used to be very accurate. If I exported 8 photos for example it would progress as expected in chunks and photos would begin appearing as the bar reached completion the last photo would pop up in the browser and the progress bar would go away. NOW the progress bar finishes way too soon and only 1-2 of the new photos have populated the browser then the bar disappears and for like 30 more seconds the files slowly appear one at a time. This is not the expected behavior and should be looked into.
Please fix both of these issues and release an update ASAP!
FATAL: Error occurred in install of package (Name: AdobeLightroom-mul Version: 220.127.116.116743). Error code: '156'
WARN: Unable to delete file at "C:\Users\Bryan\Documents\..\Desktop\Adobe Lightroom Classic CC.lnk". Error 5 Access is denied.
WARN: Unable to create symlink at "C:\Users\Bryan\Documents\..\Desktop\Adobe Lightroom Classic CC.lnk"
So this update has stopped me using LR. Where do I get help?
As a Lightroom Classic user, who embraced the mobile workflow just as Adobe marketing pushed me to the last couple of years, I need a consistent and performant mobile workflow. I would really appreciate, if the product development of Lightroom would rethink their decision to cut off the further development of the sync between Lightroom Classic and Lightroom CC. Features like the "edit/unedit filter" or "making a collection set from folder hierarchy" are not very usable or useful with the current state of syncing.
- LR directory including videos are really laggy.
- Just going through unedited photo in any album - I see the CPU usage increase to up to 80-100% on all threads. CPU temperature increase to up to 90C+. This cause Cpu frequency throttling to up to 700Mhz on my i7 7700HQ.
I am not able to replicate this issue on an old Mac book pro running LR 7.0. On this version/OS, everything is running flawlessly with Idle CPU > 55%, no throttling.
I have posted details here: https://feedback.photoshop.com/photoshop_family/topics/lightroom-really-slow-on-dell-xps-15-9650 (see my post + my last comment).