Lightroom Classic

I have many video files imported into LrC that I want to modify the filename.  The video files were taken with the iPhone 17 Pro.  My usual method to edit the filename is to edit the filename entry in the metadata panel.  When I use the method I get an error message that the filename cannot be edited.  If I use the alternate method of using the F2 key, I get the same error message.  I have submitted another bug report about not being able to import video files into LrC 15.5.  That bug report has been “Acknowledged”.  In that case reverting to v15.4 allows imports. Unfortunately reverting to v15.4 does not fix this issue. 

There is a lightroom bug which is driving me up the F'ing wall. in a nut shell i shoot a wedding dump the photos into an edit folder run Aftershoot over the top of it which does my cull and pre edit with a set specific way i edit photos. it does all the straightening etc etc I then import all the photos into LR and build standard previews. From that i then go through each image and edit everything the way i want. Thats my process.There is a bug thats driving me up the wall. Its random and i cannot find a specific reason why it does this. Essentially I adjust the photos exposure if i need to ... and randomly some photos will accept the exposure adjustments and then others will just revert back to the original setting prior to adjustments.Its batshit crazy and i cannot work it out and its driving me up the wall. Reinstalled LR and still same problem. Thought maybe it was aftershoot and xmp files. But nup.. happens even when i edit directly from the original files that have never

Se cierra más o menos a los 50 segundos de abrirlo. He probado las soluciones que se indican para este error en esta web de Abobe, pero sigue cerrándose. Lo he desistalado y reinstalado, pero sigue con el mismo problema.

My normal work practice of taking all my photos as CR3, doing all the Develop work, then exporting as JPG and reimporting the JPG back into Lightroom has suddenly stopped working.I have just moved my catalogue to my G: Drive from being split between my D: and G: Drive and been through the problems that caused with the Capitalisation of different folder names. Got this resolved yesterday so I am back focusing on my normal processing.After earlier issues that I raised a question over about a month ago I modified my Export Script to output the JPG into the same folder as the CR3, whereas I had always exported to a different folder and dragged the JPG back to where it should have been.Suddenly now with my first export CR3 to to JPG since fixing the capitalisation things have gone awry.The export works and the JPG is created in the folder I expect. I have tried both my old and new export scripts, placing the JPG in an output folder and leaving the JPG where the CR3 is.Now when I go to impor

I updated to LrC 15.5 a few hours ago.  Since then LrC has problems with video files.  The first problem I noticed was that when I tried to synchronize a folder that had two new video files.  After a couple of minutes I got the error message “An unknown error occurred while reading the video file. (2)”.  I had just completed those files with DaVinci Resolve so I went back and produced the same files again to check if DR had made an error.  When I tried again with the new files but got the same errors.  I was able to play both videos without any issue using VLC Media Player, so they seem to be OK.  I then shutdown LrC and did a backup including optimizing the catalog, and then restarted it to see if that made any difference, but same error.  Then I started looking at other videos that were already in LrC and found that when browsing them in the Library module, most of them pop up a message “There was an error working with the video”.  They will not play in LrC but work fine with VLC Med

When decoding Panasonic S1M2 RW2 RAW files in Adobe Camera Raw, the Camera Matching V-Log profile is severely inaccurate.Additionally, after applying the Camera Matching profile in ACR, it is not possible to apply a LUT on top of it. This is a critical limitation for the RAW → V-Log → color grading workflow.（All Bug and issues above do not exist in Lumix Lab which is offical APP of Panasonic, I think you can fix these issues according to their latest offical APP）

SummaryLandscape AI masking in Lightroom Classic 15.5/15.5.1 progressively becomes extremely slow during normal use on my system.Immediately after a Windows reboot, a Landscape mask typically completes in approximately 6–7 seconds. After continued Lightroom use, the same operation on comparable images can take 60–90+ seconds.I captured a controlled example in Lightroom Classic 15.5.1:Degraded state before Windows reboot: 86.68 secondsNormal state immediately after Windows reboot: 6.51 secondsThis represents approximately a 13.3× slowdown.Restarting Lightroom does not consistently restore normal performance. Rebooting Windows restores the fast Landscape masking performance.The problem appears specific to, or particularly severe with, Landscape AI masking. Other AI masks such as Sky and Subject do not exhibit the same degree of degradation in my testing.System ConfigurationOperating System: Windows 11CPU: Intel Core i9-14900KRAM: 64 GBGPU: AMD Radeon RX 9070, 16 GB dedicated VRAMAMD driv

For all the years I have used Lightroom I have used a User Preset to Import my photos. This is pointed at the current month in my Folder Structure and creates folders in that month according to the day of the month the photos are taken. Each month I edit the preset to move the output to the next month. I have recently mover my entire Catalogue from being split between my D: Drive and my external G: Drive so the entire catalogue is on the G: Drive. The Import User Preset has gone “wrong” and I cannot find a fix. Refer the following screens. Import using User Script - everything is as it should be with a couple of days straggling to be moved back to AugustLightroom structure after Import Nothing has added to September. Going through Previous Import - Photo - Go to Folder In Library takes me here. Which is outside my Master CatalogueThen I cannot Drag any of these new folders into their correct location within the Master Catalogue.I cannot find any way of either rectifying the problem wit

When backing up it states that it only backs up the catalog and not the photographs. How do you back up the RAW photographs from LRC to a hard-drive, especially if they’re already in Collections. 

In LrC, German version 15.5.1, Camera Raw 18.5.1, the tool tip for “Punktfarbe”, “Hue Range”, the lower triangle, says “Geringere Abfallkante”. I presume the tool tip in the English version is something like “lower edge”, “lower threshold” or “lower limit” or “lower ramp”. In any case, you would not translate “lower” into “geringer” in such a situation. You would use “Untere” instead, which matches “Obere” for the upper end. Geringer would translate to smaller or less in this context, in the sense of “not as high as something else”, which is arguabely not what you want to say. Note that my mother tonge is German and I am an electrical engineer. Feel free to contact me if you need further input or insight at markus.thieme@gmx.de Kind regards, Markus

Hi there!The previous LR Classic version was snappy and responsive. The latest build is extremely slow, adding a mask takes 5-10 seconds and the image glitches alot. I have an Asus ROG Strix 18 laptop with a Nvidia 5070 ti graphics card and 32 gb ram & a nvme SSD, running Win 11 Pro. When lightroom is opened, everything on my computer slows down, even moving from a browser tab to another adds a 2-3 seconds lag. When LR is closed, everything is snappy and fast. I have the latest Nvidia studio driver, everything is updated, and i have setup Maximum performance in Nvidia App for Lightroom, disabled energy saving for pcie and gpu. I am on Performance mode and Ultima mode in Armory Crate. This laptop should fly, but the latest LR Classic is extremely unperformant.Another thing that happens lately - when i try to exit, it says Lightroom has not finished writing metadata to xmp. I left it over night, still the same message. I optimized my catalog, still the same.What can I do to fix this?

J'ai des problèmes de synchros sur LRC sur des photos avec beaucoup de calques. Il n'envoie pas tout dans le cloud (ce alors que je suis en vert la liste est vide), quand je récupère sur Lightroom mobile il en manque régulièrement je dois jouer avec l'historique des versions pour retrouver la dernière.Tout est en dernière version et je n’ai pas de problème signalé dans Lightroom web.

QED: Updating Adobe CC apps can ruin the whole thing. This time it is to me the very essential Web module, which does allow saving the album at all. Nope: You do not save! So the Web module allows to  compose album normally, but without any reason the saving is disabled and the whole Web module thus useless.Macbook Pro M1 Max, MacOS Golden Gate 27.0 and Lightroom Classic 15.5.1 

Precisava recuperar as fotos de uma cliente, mas acabei apagando a edição no app e Precisava recuperar… 

I am in the terrible situation, where my dumb a** unintentionally deleted Mobile Downloads file, when trying to clear out space on my macbook. Now my LrC cannot find the files… I am looking for a way to restore/fix this mistake. Does any one have any tips or ideas? I am not very familiar with the lightroom eco system, as you might’ve guessed already…Hope any of you know anything of thisThanks in advance, and kind regardsAnders, a very stressed creative...

It seems that my lightroom on my laptop is no longer recognizes my photoshop account and when I click, photo, edit it, photoshop, I only get the photoshop home page,  It doesn’t open the window to edit on photoshop  

I try to denoise my photos with IA and my catalogue crashes out and doesn't do its job giving me with this message 

Ce BUG est aléatoire : autrement dit, cetaines fois, LRC trouve le catalogue sans problème; d’autre fois non.Voila en PJ la capture d’écran avec une copie du message.Il est bien évident que je ne déplace pas le catalogue qui avait été précédement enregistré, ce qui expliquerait que LRC ne le retrouve pas.Ne peut il pas y avoir un pb avec la gestion des fichiers Temp par Windows ?