Ps 25.12.0 https://tech.ridefox.com/img/help/page1147-Z52T/inline/605-01-321_REV_A%20Instruction%20FLOAT%20X%20Volume%20Spacer%20Installation_FINAL.pdf ... View more

Disablng the integrated GPU is heavy handed.  That can have unintended consequences for laptop users that are detrimental in other ways.  Running the discrete GPU continuously when not needed can create heat issues which will force CPU and GPU throttling below the OS layer by the BIOS.  Where the option exists, as it does with most laptops, at least trying to use power settings to effectively manage GPU utilization is a more surgical and stable approach.  Disabling the embedded GPU should be the last resort. ... View more

Check your Windows "Power Mode" settings.  My Lenovo P53s laptop had this same error when the power mode was on "Best power efficiency".  Changing the power mode to "Balanced" resolved the error.  I believed Windows was disabling the discrete GPU that Lightroom was actively using due to that power setting.  Hence the error. ... View more

If the Library filter is set to "None" and I select Catalog > All Photographs, I see the same slow loading thumbnails when scrolling down the grid. Selecting a folder or collection from the navigator is just as bad. Using a single filter column has the same behavior.  Once a filter value is selected, the grid is immediately populated with the expected image tiles but all have gray thumbnails.  So filtering the metadata doesn't seem to be an issue.  As the query count resolves immediately.  It is only the thumbnails which are slow to load.   ... View more

Yes, this is still a problem in 2024 versioin 13.1.  Lightroom doesn't abide Windows scaling nor is it's own internal "font size" preference consistently applied.  Overriding the high DPI Windows setting when starting the app fixes some of the font readability issues.  But still causes this pop-up / misaligned preview image problem in the develop module.  I also had to go back to the default of not overriding the high DPI.   ... View more

Are you sure?  I believe synchronizing the folder does remove the "missing" (in this case renamed) images from the catalog.  It then adds the "new" (renamed) images and associated XMP metadata back into the catalog.  The loss of virtual copies is annoying.  That's not something I often make use of so it's an acceptable outcome for me.   Lightroom is able to generate my desired naming scheme.  I use a custom import renaming template to do that (Here's a screenshot of the tags.  The raw text cannot be copied out of the window.  Add that to today's list of annoyances.)    The issue in this instance was that one camera used over multiple shoots was set to sRBG color space while another was set to AdobeRGB.  Using AdobeRGB adds an "_" (underscore) to the raw file names on most cameras while sRGB does not.  I've always wondered about the origin of that "standard".  So I had files intermingled with {SerialNumber}{Fileame} and {SerialNumber}_{Fileame}.  I normally use AdobeRGB so don't include another "_" in the renaming template.  I have changed my template to do that now.  The "_" delimiters in the final file names are important for later steps in my billing and archiving workflows.  I've modified those to handle consecutive delimiters so "ABC_123" and "ABC__123" will be handled the same when parsed.  That could introduce other issues if the EXIF camera serial fails to be read at import.  But that's going to have to be a tomorrow problem.     ... View more

While it technically would have been possible to sync a years worth of files just to fix the files from the speciifc days I needed to rename, the processing time and risk could be excessive.  It took LR many minutes just to analyze some of the individually effected folders.  Would have taken hours or days potentially to analyse the full collection.  I also try to avoid unnecessarily including files in batch processes that aren't absolutely needed.  There's always potential for errors and corruption.  My policy is to only touch the files I need to touch. If the effected files covered 80% of the collection, I may have made a different decision.  As it was, they were only a small fraction of the collection. ... View more

I appreciate your reply.  These are date based folders in 'yyyy-MM-dd' format.  The next level parent folder is the 'yyyy' year.  Given the number of files that do not need to be touched in the rest of the year folder, I'll go one by one through the necessary folders with renamed files.   My edits are not lost because I use sidecar XMP files to hold metadata.  The .xmp files were renamed along with their companion images.  After synchronizing and re-importing the file pairs, all the edit history is intact. ... View more

You need to disable writing metadata tp xmp while you clean up your files.  Then re-enable it afterwards.   ... View more

Found a suggestion in another thread which seems to have fixed this issue for me.    Disable writing metadata to xmp temporarily. Filter entire catalog on "metadata status" and look for anything not "up to date". Resolve your conflicts and retry wrting the metadata. Re-enable writing to xmp That allowed me to close Lightroom without it hanging on the xml writing.   I had "changed on disk", "conflict detected" and "unknown".  The "conflict detected" message is baffling to me as I don't know what other app could possibly have touched these files.  All of them were years old and I hadn't touched them in a long time.  I to "overwrite settings" although I frankly have no idea exactly what that did.  I had no edits that I recalled or cared about on those images.  There were no XMP's in the folders so there were apparently no previous edits.   The "changed on disk" error seems to have been partially due to read-only files.  Other surrounding files in the effected folders were not read only and I don't know how a few files got that way.  I also don't understand why the native image file being read only impaired Lightroom from writing data to XMP files.   The "unknown" set were all .mov video files.  Lightroom offered no option to fix these.  They have been in the catalog for years over multiple version updates without issue.  I took no action on them.   ... View more

Same issue and same setup.  Immediately after the last Lightroom update I got the same message about updating XMP and assumed it was due to the update so allowed it to run . . . an run  . . . and run.  After 24 hours it still hadn't finished so I quit.  Next exit of LR did the same thing but eventually XMP updates finished and LR exited.  Now several days and several reboots and app start/shutdown cycles later, I'm getting a similar message with only an option to "Stop".  The most recent Lightroom session included an upload of ~100 images and only edits on one.  This is absurd.   Clearly Adobe instroduced a bug in the last "update".  ... View more

I see this issue in Windows so it is at the application level and not related to the OS. ... View more

What type of image files are you viewing?  Some Fuji and Olympus cameras use very small embedded previews in their raw files.  Lightroom may be generating new minimal sized previews because the embedded ones are smaller than your minimum "standard" size as set in your catalog file handling.  You can go to preferences - general and allow your machine to replace embedded with standard previews while idle.  That may help when you later browse library images for the first time.  Also increasing the raw cache size will give you a larger back stock of the previews you do generate for later use. ... View more

I appreciate the response, but after further experimenting with the options I still don't see any meaningful difference.  As I said, other apps I use, including other Adobe apps such as Lightroom, scale more noticeably with Windows settings.  Photoshop shows no noticeable changes until I scale Windows to 200% or 250%.  Then all my other apps are so out of proportion as to be unusable.  I have tried all the permutations of "UI Scaling", "UI Font Size" and "Scale UI to Font" followed by restarting the app.   The UI scaling in Photoshop simply does not work as I expect.  Perhaps it works as designed, but I can't find any comfortable viewing scale where Photoshop matches all my other desktop functions.  ... View more

OK. I will adjust OS scaling.  But I already have mine scaled up on both monitors which works well with all other apps.  Thank you. ... View more

My Adobe profile name displays as "First Last" but Lightroom is now displaying "First%20Last".  Since the account profile name is constructed from the "First" and "Last" values this is definitely a problem in the Lightroom display rendering. ... View more

I appreciate the link and the info.  Now I'm wondering what the source of that person's information was.  I was hoping to find "official" Adobe documentation on this.  Does this parallel processing continue after the images are imported until all imported images have a new preview?  Does this parallel processing consume all available physical cores?  Logical cores? Does this rely on enabling Intel hyperthreading BIOS options? ... View more

The link above does not work.  Can you tell me where this topic can be found now?  I'd like more information on lightroom > preferences > performance > "generate previews in parallel". Thank you. ... View more

I upgraded to newer cameras which I doubt is a near term solution for your large fleet.  The a7RM4 logs its serial number in the SerialNumber EXIF tag which Lightroom recognizes and displays as "Camera Serial Number".  The older model a7RM3 and a7M3 only log the body serial number in EXIF MakerNotes as InternalSerialNumber.  Lightroom still does not recognize that tag.  I never found any workaround within Lightroom itself.  You can use exiftool to access that tag in the a7M3 files.  So you could, in theory, write your own script to rename using the serial number prior to importing into your catalog.  Definitely a PITA. ... View more