『アドビコミュニティフォーラム』に質問/トピックを投稿する方法
Bug Reports
新着順
Since upgrading to Lightroom Classic 8.3 (on macOS 10.12.6) I have the following problem: syncing with Lightroom mobile works fine after a fresh launch of Lightroom. But when Lightroom is running and the Mac goes to sleep, after waking up the system, Lightroom doesn't want to sync anymore, it says "Waiting for connection" and doesn't reconnect. But the Mac is online and everything else Internet related works as usual. I have changed nothing on my system besides updating Lightroom and Photoshop. I have found no other way to fix this than to quit Lightroom and launch it again but this is annoying.
Lightroom Classic 8.0 has suddenly started crashing shortly after startup, again! This problem really needs to be fixed. I send in crash reports, but get nothing back. Each time this has happened I've been left to fix it myself. On previous occasions I tried various methods to recover and eventually got Lr going again with no real knowledge of what actually fixed the problem. I just tried what appeared to fix it last time, but it didn't work this time. It would be very nice to hear back from Adobe. It would be great to have Adobe tell me they have identified the problem. It would be even better if Adobe told me they have fixed the problem. Meanwhile, I'm paying for a product that doesn't work! Lr Classic 8.0 is broken and needs fixing. As you can see, Lr hasn't even opened a catalogue before crashing.Note: This conversation was created from a reply on: Lightroom Classic 8 crashing on launch.
After upgrading to MacOS Mojave 14.0 and also the latest Lightroom Classic CC 8.0 (Build 1193777, Camera Raw 11.0), Lightroom is very slow on my MacPro 2015 computer. MacintoshHD drive has 600GB of free disk space, restarted the computer and only running lightroom with most of the 32GB of ram free, tried disabling graphics processor within preferences also. When I start Lightroom I notice my folder free is grey and there is scan going on every time that slows down the startup, then after that startup process is done, moving from one photo to another or doing simple menu selections or edits has a lag of a few seconds with the occasional spinning beach ball appearing. As a last resort, I reformatted my MacintoshHD drive, reinstalled Mojave and then install all of my apps from scratch and Lightroom is still slow, it make no difference whatsoever to the poor performance. Prior to the Mojave upgrade, Lightroom was fast so the issue is with some sort of
I noticed recently that the Library filter panel stops showing the number of images in each category after some period of usage. In the attached screenshot you can see that there are no numbers against any of the metadata values. I can't work out how long it takes for them to stop showing but it appears to be anywhere between 5 and 20 minutes or so.Normally, the total number of images is shown to the right of each value (second screenshot). When I first start my cataloguing session, the numbers are clearly visible. At some point in the session I realize they have gone. I know that this did not happen until recently because I rely upon those numbers to conduct my key-wording. I suspect the problem has come in with the last Lightroom update. To restore the numbers I have to exit and then return to Lightroom, as shown in the second screenshot. Can you please resolve this problem as it does compromise the cataloguing/key-wording workflow?No numbers:Numbers re-appear after restarting LR:
Zooming doesn't seem to be working for me in the map module, using the two fingered up/down gesture on my MacBook Pro's trackpad. I've been offline due a corrupted disk for a few weeks and had to restore my Mac from a TimeMachine backup, and now zooming's not working. It used to work, and it still works in Google Maps in my browser. Is this configurable somewhere, or could there be a problem with either Lightroom or some change Google's done on the backend that's affecting the map module? It's really frustrating because all the alternatives are incredibly slow and clunky in comparision, and I've got a lot of muscle memory using gestures.
Nikon d700 will not connect to Lightroom Classic CC 8.2 for tethered shooting.I am using the latest versions of Lightroom, mac os Mojave and camera firmware.The same hardware setup works with capture one pro with no problem and Lightroom connect with no problem to my Nikon D810 and Z6.
When HEIC photos from an iPhone are imported, they immediately have Metadata Status: Changed On Disk. Editing the photos changes the status to Conflict Detected.The incorrect status prevents metadata changes from being written to the .xmp sidecars when the option Automatically Write Changes Into XMP is enabled.To reproduce:1. Download and unzip these sample photos: https://www.dropbox.com/s/h9xwwlk11d3jdcc/heic-metadata-bug-2019-06-13.zip?dl=02. Import the photos into LR using the import option Add.3. Wait a few seconds and notice the metadata status changes to Changed On Disk:Tested on LR 8.3.1 / Mac OS 10.14.5 / Iphone 7 / Ios 12.1.4
The documentation for Preferences > Lightroom Sync in "Lightroom Classic CC Help" is out-of-date and incomplete:https://helpx.adobe.com/lightroom/help/lightroom-mobile-desktop-features.html#preferences- The screenshot is from an older version.- The tab has been renamed from Sync to Lightroom Sync.- The Rebuild Sync Data button is no longer visible but rather a hidden easter egg accessible by holding down Opt / Alt.- Rebuild Sync Data isn't documented. From the user forums, it appears this is a fairly common suggested magic incantation, so documenting it would be worthwhile.
I ended up with a bunch of orphan XMP sidecar files and finally figured out what was happening. This happened because of the following If you use "export as original" for a RAW file and DO NOT choose "add to this catalog" during export and then import this file into the catalog all the adjustments from the XMP file are applied and an entry for Sidecar Files is entered in Library. If you "Delete from Disk" this photo using Lightroom the XMP file is removed too.I you use "export as original" for a RAW file and choose "add to this catalog" during export the photo is added to the catalog all the adjustments from the XMP file are applied but an entry for Sidecar Files is NOT entered in Library. If you "Delete from Disk" this photo using Lightroom the XMP file is NOT removed as there is no link in the Library to the XMP.I think this should be considered a bug as "import" vs "add to this catalog during export" should both register the XMP as a sidecar file.
There is an unneeded blank line when using the right-click popup menu on the filter bar for the edited-unedited filters.
I am using LR Classic 8.3 on Win10. I know how to move a page while in the Multi-page view as long as I am moving it to a location that is in the current 8-page view, but I am having problems moving it further up (or down) in the book to an area that is not in the current 8-page view. When I click and hold on the yellow tab at the bottom of the page and try to move/drag the page up (or down) LR will not scroll to the upper (or lower) location that is not in the current 8-page view. Of course, I know that this must be possible, but I cannot figure out how to do it since it is not behaving like any other program I have used. I watched a Julieanne Kost video and also a Laura Shoe video where they show moving a page, but in both cases they moved the page within the current 8-page view so I still do not know how to move it further away in the book. I hope someone can help. Thank you!
Despite LightRoom's long term weakness with timezone handling, I've always been able to store a full timestamp with tz info in the "Date Created" field. Recently (maybe since the LR 8.3 update), it has started stripping this out. This appears to only affect RAWs with XMP sidecars, and does not affect JPEGs. I think it happens when metadata is read from file.I have a workflow where I save my metadata after import, process it in GeoSetter (I've been using it with LR since before the maps module was added, and frankly it's better for some things), and then re-import it. GeoSetter has always insisted on choosing a timezone before saving, which I suppose is to comply with exif standards/conventions,I copied the my files at each stage of this process, and you can see how LR saved without any tz info, GeoSetter added, and after import back in to LR and save again, LR has stripped it: mymac:_compare myuser$ grep -r -e "DateTimeDigitized" -e "DateTimeOriginal" -e "DateCr
Using build 1206193 on MacOS MojaveIn the Book Module, when I copy the layout from one page to another, the page text checkbox becomes unresponsive. If the source layout already has a page text, I cannot disable it. If not, then I cannot enable it.Thanks for looking into it.Best,Alex
This is just a minor translation issue (using version 7.4):When a new version of Lightroom is available, a window pops up instructing the user to got to "Hilfe -> Updates" for getting the new version installed. However, in the "Hilfe" menu, the corresponding menu item is "Aktualisierungen" rather than "Updates". The terminology should be aligned.Just a minor issue but should be straight forward to correct.
Lightroom 8.3, Build [201905061635-edecdfdb]Windows 10 Pro In Grid, select two CR2 raw files.Export these to a DVD.The DVD is missing the XMP files.The DVD only has the CR2 raw files.This is a bug. If you export to a Hard Drive, the XMP and CR2 raw files arecopied as expected.Thanks
After publishing new photos from Lightroom to Adobe Stock using the provided plug-in, LR asks me if I want to jump to the web site (Adobe Stock) but I got the following message:"Failed to update the collection.An internal error has occurred: bad argument # 1 to 'openUrlInBrowser' (string expected, got nil)".Photos are correctly posted and I can see them in the collection, but I cannot reach the website directly from LR. The obvious workaround is to open the web browser manually and log on AS.Anyone experienced this unpleasant issue ?Thanks in advance.
LR Classic CC auto upgraded from 8.2.1 to 8.3 ... with that the ability to export videos in 'Original' format fails. (The progress bar shows action, but no files are exported.) It still can export videos in H.264 format (but obviously downgrades resolution from 4K (3840x2160) down to 1080p which is useless to requirement). I tried clearing video cache and disabling metal video acceleration ... neither addressed the issue.I downgraded back to 8.2.1 and the functionality returned as designed.I would suggest that the LR Classic CC 8.3 rev has a functional error with exporting video in 'Original' format.This is on MacOs 10.13.6
Before I first purchased CC I asked on a forum the question, "will it still run if my internet is down", and I was informed yes.I have moved to a small volcanic (desert) island where the internet isn't always good. So far I have been luck in that it has been off when I have not needed to be at my computer. This morning was the first time, but I thought it would allow me to catch up with photo processing and art work. Until I got the message that Adobe can't check my subscription!!! So for most of the morning I might as well have gone back to bed!Now we are hoping to move further inland, where connection problems are more than likely to increase. I wasn't bothered until this morning, as I thought I would still be able to use Photoshop and Lightroom. :'( So, have finally got internet back on I opened up Photoshop and Lightroom ok. When it went down again they did stay open so I see that I must just have a connection in order to open them.So I have to a
Not sure if this is the right place for a bug report, if not could anyone direct me to the right place please.Clicking develop module at top right from the Library module opens the photo with film strip and both side bars black empty spaces. Initial few times I had to quit and restart Lightroom but then discovered switching to grid view again and develop keyboard short cut, everything comes back.
Discovered a BUG with selections in Lightroom Publish collections:When you select several photos within the Library Grid the first/most selected photo does not display as the brighter white colour in the grid, it does display correctly within the film strip.(I checked back through several versions of LR: LR7.1, 2015.12 and LR5.71 on Windows 7 and they all have the same bug. Also LR7.1 using Windows 10 on 2nd computer has same problem.)This only affects selections in Publish collections (tested Hard drive publish, Flickr and jfZenfolio collections)Steps to reproduce: In a Publish collection select first photo (different from the initially selected photo) Use SHIFT key and select additional photos Result the '1st' photo does not brighten to show it as the 'most selected'It does work for the following: If you use CTRL key to make the multi-selection If you use the initially selected photo upon opening the collection as the first photo, then shift selection works
When sorting Library grid view by capture time, LR doesn't sort correctly by fractional seconds -- it ignores leading zeros in the EXIF:SubSecTimeOriginal field. To reproduce:1. Take three photos directly from a camera: a.jpg, b.jpg, c.jpg.2. Set the DateTimeOriginal and SubSecTimeOriginal field of the three photos using these commands: $ exiftool -datetimeoriginal="2017:01:02 03:04:05" -subsectimeoriginal=0.1 a.jpg$ exiftool -datetimeoriginal="2017:01:02 03:04:05" -subsectimeoriginal=0.01 b.jpg$ exiftool -datetimeoriginal="2017:01:02 03:04:05" -subsectimeoriginal=0.002 c.jpg 3. Import the photos into LR.4. In the Metadata IPTC panel, observe that Date Created shows what was set in step 2:a.jpg: 2017-01-02T03:04:05.1b.jpg: 2017-01-02T03:04:05.01c.jpg: 2017-01-02T03:04:05.0025. In Library grid view, do View > Sort > Capture Time.6. Observe that the sort order is incorrect: a.jpg, b.jpg, c.jpg. It should be: c.jpg, b.jpg, a.jpg. Most likely the Lua code is doing t
hi folks,just installed LR CC. Rendering in develop module is really slow. Eg. when I move between photos, it takes a good 3 seconds for the photo to fully render. Displays "loading" for about 2 seconds and then a further second or two before the image is fully rendered.This isn't happening in the Loupe view.This is with a new set of photos I just imported, and I had "build 1:1 previews" set during import.Is this an issue or have I got a setting wrong somewhere?It wasn't quite this bad on LR 5.ThanksDave
I have made a number of profiles to be used with Lightroom Classic CC. Two of them (V1 and V2) are made with the same lens and camera, just under different lighting conditions, and with the same X-rite Colorchecker Passport plugin.Only one of them shows up in the Profile Browser; if I move V1 to a different folder and restart Lightroom, V2 shows up in the Profile Browser and vice versa.I'm on the latest versions: Lightroom Classic CC 8.2.1 on MacOS High Sierra 10.14.4.Is there a way to have both profiles available in the Profile Browser? Thanks.
The title says it all. This should be added to the list of bugs I've posted over the last few years.Is anyone going to fix all the API bugs or are you abandoning the API? There's been no update in 3 years!For example, seehttps://feedback.photoshop.com/photoshop_family/topics/list-of-lightroom-sdk-lrdevelopcontroller-bug...https://feedback.photoshop.com/photoshop_family/topics/lightroom-api-bug-most-transform-adjustments-...https://feedback.photoshop.com/photoshop_family/topics/lightroom-sdk-bug-alt-key-ignored-when-moving...Does anyone at Adobe care? There are lots of users of my free software (over 900 youtube videos discussing how to use it), but I'm thinking of pulling the plug if this lack of support and increasing number of bugs continues.
When trying merge 6 images (which have plenty of overlap and merge without issue in Photoshop), Lightroom Classic CC says "Unable to merge the photos. Please cancel and review your selection." There is no indication why these photos cannot be merged by Lightroom.
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
すでにアカウントをお持ちですか?ログイン
アカウントをお持ちではありませんか? アカウントを作成
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.