I can see this bug in Windows 10 with version 7.3.1. Once again, this raises the same returning question : how could this escape a simple quality control ? Also, this is a clear indication about the user interface management. If a setting belonging to a given panel can be disabled when another panel is disabled, there's obviously something wrong in the way the state of the various UI elements is managed. There are other old bugs (still not fixed) that are giving exactly the same signal. The UI elements state must be managed globally in order to avoid inconsistencies. This is a classical issue in software design and the methodology to avoid this is known since a long time. Back to school... Or quit subcontracting to offshore developers. ... View more

Ah, thanks. I didn't read the first post after the merge. ... View more

Chris, > In all cases that I've noticed, it seems that LR actually DOES save it properly - it just won't understand that it did. I would say : it just won't understand when it did 🙂 . ... View more

Hi Sean, This is a very old bug that has never been fixed although it has been thoroughly documented and analyzed. The problem is a wrong timestamp stored in the catalog. Please read the following threads : https://feedback.photoshop.com/photoshop_family/topics/wrong-timestamp-stored-in-lightroom-catalog-c...  (the first post is badly formatted due a forum issue. Just ignore it. It has been rewritten in a subsequent post) https://feedback.photoshop.com/photoshop_family/topics/problem-saving-metadata-if-certain-adjustment... The only known way to (temporarily) get rid of  this issue is to select all affected images, hit Ctrl-S to save the metadata and then use the Metadata | Read from file command to update the catalog with the corect timestamp. But the problem will re-appear later anyway. ... View more

Now I see another problem with this new behavior. The previous .lrtemplate format had provision for the state of each setting panel in the development module :             EnableColorAdjustments = true,             EnableDetail = true,             EnableGrayscaleMix = true,             EnableLensCorrections = true,             EnableSplitToning = true, There's apparently no corresponding tag in the new XMP format, as mentioned above. So, this information has been lost during the conversion from the old format to the new. Even if the previous behavior is restored in a future release, the only way to recover the information about the state of each setting panel will be to convert again the old presets... if they still exist (since they are no longer used, I had deleted them from my system - fortunately, I could restore them from an old backup). I have noticed that the translation is triggered automatically as soon as presets not prefixed with ~ appear in C:\Users\<user>\AppData\Roaming\Adobe\Lightroom\Develop Presets. So, if Rikk succeeds in his attempt to convince the development team to go back to the previous behavior, a backup of the presets in the old format will be needed. If they have not been deleted, it will be necessary to remove the prefixing ~ in the preset names to trigger a new conversion. Once again, the transition to version 7.3 seems to have been rather thoughtlessly managed. Too many obvious bugs that could have been spotted before release, unwelcome behavior changes,... As I already stated elsewhere, there's a problem with the QA dpt. at Adobe. If there's still one. I doubt. We can't spend time "re-learning" LR and chasing bugs each time a new minor version is released. Doing regression testing is not our job. Adding features is nice as long as this doesn't break the user's workflow. LR has to adapt to the users and not the contrary. ... View more

I just noticed something that I consider as a bug : when hovering the presets, I observed that some of them had absolutely no effect on the full Live Preview. Very strange. Until I realized that the settings modified by the preset and located in a disabled development panel (switch button at the top left corner of the panel set to Off), are not taken into account. This is questionable. The live preview should show the full effect of the preset by temporarily re-enabling the setting panels that are switched off. Otherwise, this doesn't make much sense. ... View more

OK. I will open a new thread. ... View more

Rikk Flohr, official rep, apparently reported this issue to the development team. https://feedback.photoshop.com/photoshop_family/topics/lr-7-3-1-often-not-updating-rendering-in-full... ... View more

>> Please make some checkbox in settings to turn it off. Not in settings, Stanislav. The ON/OFF button must be directly accessible during the browsing operations. For example, as you described, one may want to do a quick browsing through a lot of preset folders (groups ?) with full live preview disabled and then activate it when selecting a preset in a specific group. I think the best place for this button is in the toolbar under the viewing area, along with the other tools. NB : There's another related problem with preset previewing that I commented elsewhere. I just noticed something that I consider as a bug : when hovering the presets, I observed that some of them had absolutely no effect. Very strange. Until I understood that if the settings modified by the preset are located in a development panel that is disabled (switch button set to Off), the live preview doesn't take these settings into account. This is questionable. The live preview should show the full effect of the preset by temporarily re-enabling the setting panels that are switched off. Otherwise, this doesn't make much sense. In other words, new feature not tested by someone using LR for real work. ... View more

These are two different operating systems. Although I'm not a MacOS specialist, I don't think that Ctrl-C and Ctrl-V are the default system keys for Copy and Paste (it's rather Command-C and Command-V, I guess). So Ctrl-C and Ctrl-V are "free" and can be assigned in LR to the Copy Settings and Paste Settings tasks. A MacOS expert could confirm this. ... View more

Michael, On Windows, Ctrl-C and Ctrl-V are reserved system keystrokes for the Copy and Paste operations respectively. All applications use them for this purpose. The Copy and Paste operations in Lightroom are something different. I guess this is why these keystrokes can't be remapped.to the Copy and Paste "settings" in LR. In Lightroom, Ctrl-C and Ctrl-V are used to copy and paste text in text fields. So, they can't be used to copy and paste a block of data containing LR settings. Using the same keys for both types of operations would lead to huge problems. ... View more

Hi, In LR version 7.3.1, I'm still unable to manage (at least rename) my preset folders. Also, after installation, I noticed a lot of duplicated (or triplicated) presets, some being moved and renamed by prefixing them with the name of the folder they were stored in. The mess continues. I cannot create a new folder (group ?) without creating a new preset. So far for the preset management capabilities. The Presets panel is missing a Create Group... (or Create Folder...) command. Adobe, to which exotic offshore company are you subcontracting the coding of LR ? ... View more

>first... the chances of an Adobe person responding is much higher than the lottery... stop participating in this discussion only to try to stop me from posting... that is disrespectful and not helpful... i have seen many things answered by Adobe staff< Not if you adopt this attitude with people who are actually trying to help and to explain how things work. You didn't read my message with enough attention. I'm not trying to stop you from posting here (on the contrary) but I'll do stop helping anyway. The official feedback forum is Photoshop Family, not this forum. You may deny this if you want, I don't care, but this will not change the facts. Good luck. ... View more

@aaron > also Adobe people DO respond so this is a fine place to post this Hi, Actually, the best place to report a problem is : Adobe Photoshop Family . This is the only way to have a little chance to have a problem taken into account by an Adobe rep. However, this doesn't prevent you from posting here in case another user has a valid answer. After all, this is a forum setup by Adobe in order to discuss problems about Adobe products. Just, your "please fix this" statement was superfluous. Nobody here will fix anything. If you are very lucky, an Adobe rep might read this message, try to reproduce the problem, go to the development team and tell them about the issue but very frankly, you have much more chances to get the jackpot by playing the national lottery. ... View more

7.3.2 ??? ... View more

Hi, I vote for an ON/OFF button that should be quickly accessible all the time. It's not only a problem with those users who want this feature on and those who don't like it. At some moments, e.g. when browsing through a large set  of presets, I don't want the live preview to be enabled. This makes the screen flashing. Once I have eventually landed in the right preset folder (or group ?), having this feature enabled will be useful. A good location would be in the Presets panel title bar. However, this assumes that it is always visible. Which in turn assumes that scrolling occurs in the Presets panel only and not in the whole left tab. Otherwise, the panel title bar quickly disappears. Another good choice would be the toolbar under the viewing area, beside the viewing and attribute options. ... View more

Still no correct answer to this issue. ... View more

mauricep27921461  wrote you could try analyzing the log files to see why it fails: Troubleshoot Adobe Creative Cloud install issues with log files Maurice, Cherishy, I can't remember how many times during the two last years I have uploaded the log files, explained where the problem occurred (always the very same error at the same place), etc. Still waiting for feedback or for a fix. As explained above, this is a recurring problem. Not something that one can fix by simply restarting the system. There is a bug in this process, not in my system. Error 183 is something that is happening all the time since years for many users and for multiple Adobe products. Just google for it. There's something wrong in their installers and they obviously refuse to admit it. I'm a former software engineer. The first thing I would do in order to trace this issue would be to rework the error/exception handling procedures in the code to make the failure cause more easy to track. These messages are too generic and it's the same for the log files. There's nothing to do with them. Regards. ... View more

> Clicking on Retry never helps, of course, and the explanations for code 183 are just a joke : Got it ! There was a mix-up with the algorithm behind the "Groundhog Day" movie. ... View more

Hi, Here is how you can edit the custom crop ratio drop down list in Windows in order to modify or remove ratios or get more than 5 custom ratios. Make a backup of your catalog first. 1. You need an SQLite management tool. I suggest SQLite Expert Personal 5. It's free and very good. You can find it here : http://www.sqliteexpert.com/download.html . 2. After installation, make sure that LR is not running, go to the File menu of SQLite Expert and Open Database... 3. In the Open dialog, select All files in the drop down list at the bottom right of the window. Now navigate to the folder where your catalog is stored and select the corresponding .lrcat file. Click Open. 4. Your catalog will open as an SQLite database, showing tables, columns and values. In the left panel, select the table named Adobe_variablesTable. 5. In the right panel select the Data tab. 6. In the name column, select the Adobe_customCropAspects entry (line 254). 7. In the value column, right-click on the text beginning with "customCropAspects =" and chose Text Editor. 8. The contents looks like this (this is an example with 5 custom ratios) : customCropAspects = {     {         h = 1,         w = 2,     },     {         h = 7,         w = 9,     },     {         h = 8,         w = 11,     },     {         h = 9,         w = 13,     },     {         h = 11,         w = 19,     }, } Each block like this     {         h = 11,         w = 19,     }, corresponds to one custom ratio (don't forget the comma). Let's assume that you want to replace the 9x13 ratio with 13x21. Easy : customCropAspects = {     {         h = 1,         w = 2,     },     {         h = 7,         w = 9,     },     {         h = 8,         w = 11,     },     {         h = 13,         w = 21,     },     {         h = 11,         w = 19,     }, } Click on OK after you are done with your changes. 9. Exit SQLite Expert and click on Apply pending changes. 10. Launch LR and check the new ratio value. 11. Note that you can have more than 5 custom ratios with this procedure. You just have to add a new block. For example : customCropAspects = {     {         h = 1,         w = 2,     },     {         h = 7,         w = 9,     },     {         h = 8,         w = 11,     },     {         h = 9,         w = 13,     },     {         h = 11,         w = 19,     },     {         h = 13,         w = 21,     }, } defines 6 custom ratios. That works perfectly : this generates 6 custom ratios in the drop down list. Which is another evidence that this feature has not been written very seriously. Hope this helps. ... View more

I should add that the problem appears mainly with 16-bit images. Anywya, ZIP should be used in any case. Only a few programs were unable to open ZIP Compressed TIFF files but it's now fixed in most of them. ... View more

Hi, Not necessarily layered TIFFs. Last year, I have made a study over a large number of non compressed TIFF files (photos) re-saved and compressed in LZW mode. About 50% of them were about 5/10% bigger than the originals. Someone else made a more accurate study and got similar results. I couldn’t believe it, that’s why I wanted to test myself. ... View more

Re-activating this discussion... When I save a TIFF file, the options dialog box defaults to LZW compression mode, which is the worst choice for photos (most of the time, the LZW compressed file is bigger than the non-compressed version). How can I specify ZIP or None as the default option ? The last choice is not retained. ... View more

Hi, Affected users should add their vote here : Text size, leading, tracking etc. PROBLEMS | Photoshop Family Customer Community ... View more

Hi, If my recommendations are unclear for you, I think I won't be able to go deeply enough in the details in a forum message. I suggest that you show my posts to a friend who has more experience with computers. He or she should fix the problem easily. Good luck. ... View more

Well, since you are using the English language I guess that you need to apply the workaround that I have posted in the thread named ‘Filtering issues with “Show photos in sub folders” option’ that you visited recently : You could try to create an empty TranslatedStrings.txt file in C:\Program Files\Adobe\Adobe Lightroom\Resources\en using Notepad. Relaunch LR and try KT again. Then proceed as described in my post by copying TranslatedStrings.txt to TranslatedStrings_Lr_en_US.txt in the same folder. Relaunch LR and your changes should be taken into account. This worked fine for another user who had the same problem as you. Note that the path is now different for Lightroom CC Classic. It’s now rather late here in France so I will not be able to answer again until tomorrow. ... View more

BartonGarrett256  wrote Thanks for the suggestions, however I can't make changes to a program that will not open, and when I go to the folder you suggest it is empty. Hi, 1. Do you mean that Keyboard Tamer is not present when using the File | Plugin Manager command ? 2. If it is, did you make sure that the "Path to Lightroom" field is correct ? 3. What version of Lightroom are you running ? 4. On which OS ? ... View more