새로운 Adobe 커뮤니티에 오신 것을 환영합니다.
Connect with fellow editors in our Lr Classic community.
최근 활동
In the Import dialog, there should be an option to skip importing any JPEG files where a matching RAW file exists. I always leave my camera on shooting JPEG+RAW, since I can easily download pics to my phone and share with others while on the go, but I don't keep those in my computer. Therefore, an easy solution to just skip these files during import would be great. Currently, the closest process is to either: in the Import dialog, import all files, go to settings, configure to "display jpeg and raw as separate files", remove all JPEG, revert your configuration; OR In the Import dialog, select all images, sort by image type, uncheck all JPEG images, import just the others Any of these alternatives are cumbersome and not perfect: if you happen to have a picture in JPEG only, not the matching RAW, you risk deleting it by mistake.
Hi y'all! Please excuse my lack of technical terminology in advance, but I'm having issues with Lightroom Classic and cannot for the life of me pinpoint the problem. Upon importing pictures from SD AND CF cards, I noticed that when clicking from the Library tab to Develop that once I clicked on an image to start editing it, a pixelated color/overlay started appearing over 70% of the image. In some cases it goes away when I click back to Library but in other cases it's stayed. I tested this on another import with other cards and the same thing happened. I also thought it could be a bug surrounding the Import button, but I clicked back on folders with pics from years ago and the same thing happens. This is still happening even after I've ensured my Mac is up to date as well as LRC with the latest version. The images also appear fine in LRC on my *14-year-old* MacBook (... I don't even know how that thing functions, but the program and same photos are fine). Can anyone help,
I am posting this here, but I found the issue first in Bridge and then in Lightroom, so I assume it's also an issue here, as it seems by design. And it just continues a trend which I begin to despise in Adobe.No Adobe product I have tried can write metadata directly into an JPEG XL. They all create a xmp file in the same folder instead. Once that file is deleted, the metadata is gone. But according to the file format specifications, JPEG XL does support it, of course it does. And that Adobe software does not, is not acceptable. JPEG XL is a modern file format, the successor to JPEG. It is widely superior to it, and should be fully supported. The same also applies to mp4 audio files, that Audition can't write, for whatever reason. All Adobe products seem to support Adobe's own DNG file format, which seems to actually uses some JPEG XL technology in its latest iteration. So, I am sharing this as a bug. As this should not be the case. It can't be, that we need more and more exte
After clicking the Enhance button on the Denoise pop up window, I keeep getting this message : "The file could not be written due to permission issues". I have the latest version of Lightroom Classic and it is up to date. Am using it on my Mac Mini2. I never had this problem on my PC running Windows 11.
Not sure if this is a bug or intended behavior, but, it's more than a little annoying. So, idea to change, or bug to fix: Situation: Adjusting Lens Blur settings (blur amount; focus range; brush strokes/adjustments) in Develop when "Visualize Depth" is checked. Use Command-Z to undo a change. Result: Change is indeed undone. However, Visualize Depth mode is turned off/unchecked. Expected result: Develop/Lens Blur stays in Visualize Depth mode until user explicitly unchecks "Visualize Depth." I don't understand why it would/should pop out of Visualize Depth mode when you undo a change. Odds are you're adjusting multiple things while visualizing depth and want to stay in there until you're done! --MBP 13" M1 2020; MacOS Sonoma 14.6.1; LrC 13.5.1-- This behavior does not occur in LrD 7.5; a command-Z undo of an adjustment in Visualize Depth mode leaves you in that mode as I would expect.
depuis les dernieres mises a jour , LRC est tres lent et se bloque au bout d'un certain temps d'utilisation de meme avec photoshop ( processeur incompatible ... erreur 43 ) alors que mon pc est recent et assez puissant, mais pas de carte graphique. intel I5 13500, 64 GO DE RAM, grand stockage . carte mere a jour , processeur aussi pourquoi windows desactive la carte graphique du processeur
I am using Lightroom Classic 12.4 in MacOS 12.6.6. Since one of the more recent updates of the MacOS version of Lightroom Classic I have been have been having an issue where I will be typing text into the Library metadata fields ("title", "caption", etc.) and it will suddenly trigger some sort of lightroom keyboard shortcut and take me to a "Develop" feature I didn't mean to invoke. This is super annoying! Most recently it caused the photo whose Metadata I was editing to be hidden or moved in the Library somehow so it no longer even shows up in Lightroom search. Again, this is super annoying. Is there a way to disable keyboard shortcuts or at least could they not be invoked when the mouse or keyboard focus is on a Library Metadata field?
I'd like to see some improvements/additions to the lens blur manual adjustment tools. The AI does a great job, but it's never quite perfect. It would be really useful to be able to simply set/calibrate depth with an adjustment brush, rather than a relative focus/blur. I think it means adding a third tool that is more explicitly "paint depth"—preferably with an eyedropper to select the depth level from the image. The depth level you are painting should correspond directly to the 1-100 scale that the focus range adjustment uses. At least half of my time spent adjusting photos using lens blur is adjusting imperfect AI mapping of objects outside the main subject so that they match their surroundings. For that, I switch to the "visualize depth" map mode. If you're trying to get the image to a place where you can then adjust the blur amount and focus range, you really need the depth map itself to be accurate. Why is the new tool needed? U
Hello everyone, I'm just curious about how you use the contrast slider.With shift key pressed and double click on the basic sliders Lightroom applies automatically the values. This operation can be useful, for example, to set the white and the black points.I just noticed that using the shift key + contrast Lightroom doesn't go never more then 6-7. It apply automatically always a very low contrast to the files.What do you think about it?
Hallo Ich habe das Problem dass meine Einstellungen von der Kamera nicht von LR übernommen werden.Das heisst ich habe in der Kamera 5500 K Weissabgleich und nach dem Import in LR 6500 K Es steht "Wie Aufnahme" ist es aber leider nicht. Es sind keine Änderungen beim Import hinterlegt.Ich wäre froh um Hilfe.
I've been noticing this very intermittent issue occuring over the last year, so it's not based on an Lightroom version updates, and it hasn't phased me too much until now. So, I do some edits in lightroom and once I'm done the visible changes are seen via the viewing window and panel across the bottom. Occasionally I will reopen lightroom and go back to an previously edited image and it has been converted back to the original state of the raw file. I am aware that Lightroom doesn't actually adjust the raw image as it creates a sidecar .xmp file that partners up with the raw file, allowing virtual copies to be made and multiple edits to be created from the one base import file. I know .xmp files exist but I don't know enough to fault find. I also assume that all the .xmp files are created automatically and stashed with the raw import files. Would this issue be caused by the .xmp not being saved properly in it's auto mode? Is there a way to manually prompt lightroom
For the last 6 years, I have been the owner of a Pentax K-1 II DSLR .When I use the Pixel Shift feature, it records 4 images in a single DNG file.LRc is able to process these files and combine the 4 exposures, as long as there is no motion.If there is motion, it is preferable to use an external processor such as Pentax Digital camera utility or RawTherapee. My problem is that I don't see any way to distinguish which images in my catalog are Pixel Shift, and which are not. I can filter by camera model and file format (I only shoot in DNG anyway), but that does not narrow it down enough. I checked the metadata of one of my PixelShift files using exiftool. It showed the following field : [Pentax] Quality : RAW (pixel shift enabled)Is there any way to create a smart collection that filters based on this metadata ?I checked using "all plug-in metadata" for the word "shift" and it didn't match any photo.
I have a folder of product photos I want to edit. I used to export and change the name, but today I do not want to do that. I want to over ride the original photo, but everytime I try and export I select "exisiting photos- override without warning" but when I press export it says it can't do it because it will replace the exisiting file. How do I replace the exisiting file without running into this issue?
Mac OS Sonoma 14.6.1, Lightroom Classic 13.5.1, Macbook Pro 16", M2Max. The GPU is perfectly capable of running two displays with full acceleration (I do it everyday in Final Cut Pro)However, for Lightroom Classic, enabling secondary display makes the preview very laggy, it drops to 10 or 5 fps from usual realtime update for zoom-in and out, for slider adjustments previews, etc - essentically bringing the user experience back in 1990-ies! Especially pronounced in Develop module (in Loupe seems ok). See attached video for actual demonstration of the issue.
Mac OS (all latest builds as of time of writing), Macbook Pro M2Max, working with external display. If you use the external display as primary and enable Loupe view for secondary display (which in this case will be the laptop's screen) it shows a band of desktop wallpaper on top of display which is extremely distracting. Please see screenshot attached. Needs fixing, especially for modern macbook pro displays with notch.
I am coming from Capture One and want to keep the same working flow which works for me. Sessions. Each shoot is it's own individual thing. How do I make catalogs work as a session. I thought I was doingit right but all my shoots are now in one catalog and confused how to spearate them. I know a lot of people perfer all shoots in one catalog but that isn't for me. Thank you
I am capturing via tether while using multiple displays all day / every day and the widget it constantly disapearing. If it goes way I have to make sure LR is in full screen mode then go to another app and then back to Lightoom to find the widget over on another display then drag it to the correct display to shoot. Yes I know I can F12 to shoot and shift/command T to change Shot Name but I often need the "Tethered Capture Settings" window to change sesssion name and that's a button on the widget. I want the tether window to imbed in my develop module to which I'm shooting or have a completely new customizable Tether Module. Thoughts? How does that sound Adobe, let's make it happen. -Rf
Hi,anyone knows why I have a paper size mismatch between LRC and printer driver?The printer setup is A4, no doubts about it.For LRC is Letter ...A4 for the printer's driver - Letter for LRC - the entire image is previewed and printedA5 for the printer's driver - Letter for LRC - only the first quarter og the image is previewed and printedWhy is this happening and - more important - how can I reset it .. ?Thanks, Andrea
Buonasera,Posseggo un monitor proart 27" da 350 cd/mq.Con quale luminositá e contrasto del monitor devo lavorare mentre uso lightroom,cosí da avere immagini abbastanza fedeli a quelle di stampa?Grazie.
Denoise AI increases chromatic aberrations. "Remove chromatic aberrations" is enabled and "built-in lens profile" is used on both photos. The amplification of aberrations by denoise varies from lens to lens. In the case of Tamron 17-28 F2.8 Di III, they are very visible. For the Tamron 28-75 F2.8 A063 and 70-180 2.8 A056 they are less visible or not visible at all.Lightroom version 13.5.1
Hey I'm encountering an issue where every time I export my images, it exports both the AI-denoised version and the original photo. As a result, I'm getting a lot of duplicates. How can I configure the export settings to only export the AI-denoised photo and avoid these double ups?
I have a subscription for adobe photography.Since yesterday I get the warning that there is a problem with my license. Ive tried to change my password and a new install but the problem still occur. It says my activation stops in 5 days.
Hello all, here's some context, then my question.In the company I work for, there are three photographers that take photos for clients and then store them on a NAS at the office. We then edit those photos in LrC by adding the folder from the NAS into LrC. We do this on three different computers, thus creating 3 different locally stored Lightroom catalogs that are pointed back to the same original files on the NAS. About 20 Other employees at the office also have access to these photos on the NAS and use their own Lightroom account primarily to locate the photos and export them to be used on client web sites. Till running into problems, we photographers assumed that when we edit, changes are saved as XMP for RAW images (we set this to happen automatically) or saved to the image itself in the case of DNGs. Then, we thought anyone else that imports/synchronizes the folder that contains those images would be able to see our edits. But we're h
I'm sorting through many photos. I know I can right-click on a group of pictures to apply a color label to the selected photos. Is there a shorcut key to do the same thing? Thanks!
Nedaří se mi instalace Adobe Photoshop 6 (zakoupený) na Windows 11
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
이미 계정이 있으신가요? 로그인
sso.login.detail.descriptionWithRegistrationLink
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.