Lightroom 5.7 Map module so slow it is almost useless

I've used iPhoto and Aperture a lot but because Apple are withdrawing these programs soon apparently, I decided to upgrade to Lightroom. Everything else works fine, but the map section is just so slow. The map layers take far too long to download. My internet connection is 8 Mbit broadband. I'm upgrading to fibre optic later this week, so I'll see if that makes any difference - but I see no reason why it should.
OS X Yosemite 10.10.1
iMac 21.5 inch late 2012, 2.9 GHz Intel Core i5, 8GB 1600 MHz DDR3, NVIDIA GeForce GT 650M 512MB

you can´t change folders from inside the MAP module
Yeah, you can't change folders in a number of the modules. However, the Any Source plugin lets you do that.
GEOSETTER has many more features and is my preferred tool for tagging
Mine too.

Similar Messages

Lightroom 4.4 Map Module blinks "Offline" when moved or zoomed.

Lightroom 4.4 Map Module blinks "Offline" when moved or zoomed.
As stated, every time I move the map with the mouse or zoom the map using any method the map blinks into "offline" condition to redraw. This is not only annoying but drastically slows down work flow.
How can this be stopped?
Macbook Pro 2010 i7 8GB RAM
Thanks,

To see what I see, turn off your internet by shutting off your wireless card or disconnecting your ethernet if hard wired. The map will turn into a grey full-earth map and have the note "map is offline."
Woody 77 may be correct but the problem follows me from location to location and happens when others are getting no problems at all.
I was wondering if there was some form of optimizing I could do to improve performanc. Perhaps I am having a problem with my airport card.

Downloaded ios5 to my iPad, had trouble with all my apps but that got fixed. now the whole thing is so slow it is almost useless. have rebooted, didn't help

i downloaded ios5 to my ipad. Initially had problem with apps which was fixed by downloading an upgrade and they all staarted working. But everything is so slow it is almost useless. i have tried rebooting, it didn't help.

Other users have reported this very same issue after updating their iPads. You are using the original iPad according to your profile and those devices seem to be the more adversely affected devices. You can try the basic things and see if any of this helps.
Restart the iPad by holding down on the sleep button until the red slider appears and then slide to shut off. To power up hold the sleep button until the Apple logo appears and let go of the button.
Reset the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons.
Go to the home screen first by tapping the home button. Quit/close open apps by double tapping the home button and the task bar will appear with all of you recent/open apps displayed at the bottom. Tap and hold down on any app icon until it begins to wiggle. Tap the minus (-) sign in the upper left corner to close the apps. Restart the iPad. Restart the iPad by holding down on the sleep button until the red slider appears and then slide to shut off. To power up hold the sleep button until the Apple logo appears and let go of the button.
If none of those things help, you can always try restoring your iPad. I have restored mine with some success, but I still have issues that I hope will be resolved soon.
An update to the iOS has been announced and it is in Beta now. Hopefully it will be released to all users soon.

Lightroom 5.2 map module not displaying maps

I am having all sorts of problems with Lightroom 5.2 and wish I'd just stayed with Lightroom 4. I've already posted about not being able to import directly from an SD card in my laptops reader, and have at least found a work around to that (copy files to hard drive them import - I see others have found the same thing and it works just fine).
Now I have realised that the map screen in the map module is blank. I had this problem initially with Lightroom 5, and then it seemed to resolve itself. It is refusing to resolve itself in Lightroom 5.2 however. I've searched on the web for similar problems, and have found some responses to blank map screens in Lightroom 4, but they are so technical I haven't got a clue where to start trying to follow them.
So, I am a simple soul who needs a simple answer. I am using LR 5.2 on an HP laptop running Windows 7. In the map module, where I already have GPS data (from a Canon EOS 6D) it is displayed in the metadata, and the little pop up box shows the number of photos at selected locations etc. But the central map screen is black. If I search, the screen stays black although it appears as though it has gone to the location. The Navigator screen is blank too. And yes, I am connected to the internet and LR5.2 seems to be able to find the internet (I checked by going into the web module).
Can anyone help me please. I like to put GPS locations on my photos prior to upload to Flickr, and whereas they are there from photos from my 6D, they don't exist for photos taken on my Canon Powershot.

A work-around that I am using is to run Lightroom as an administrator on my Windows 7 system (right-click on the icon and choose run as administrator). Everything then works ok. I also needed to run as an administrator to be able to update some plug-ins I was using. I fixed the plug-in update issues by changing the permissions on plug-ins folder. I suspect that it is a similar issue with the maps.
I have not figured out what folder or files need to have the permissions altered to stop Lightroom from working in the unelevated state but if someone reading this knows please share. I saw some posts related to the same issue but on Macs but the Windows configuration is different.
Dan

Why is Lightroom 5.3 Library module too slow to be productive

6 seconds to select three images in the grid?? I've done all the things recommended by the FAQ's for optimizing Lightroom's performance. My PC setup as reported by Lightroom is below. My catalogue contains fewer than 30,000 images. I don't use stacks. I don't automatically write to XMP. I'm running LIghtroom alone on a freshly started Windows 8 session. All my other software runs fine. Version 4 seemed to run fine. Am I doing something wrong? Are others having this problem?
Lightroom version: 5.3 [938183]
Operating system: Windows 8 Business Edition
Version: 6.2 [9200]
Application architecture: x64
System architecture: x64
Logical processor count: 4
Processor speed: 3.4 GHz
Built-in memory: 8078.3 MB
Real memory available to Lightroom: 8078.3 MB
Real memory used by Lightroom: 919.9 MB (11.3%)
Virtual memory used by Lightroom: 881.8 MB
Memory cache size: 1074.5 MB
Maximum thread count used by Camera Raw: 4
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1680x1050, 2) 1280x1024
Installed Plugins:
1) Behance
2) Canon Tether Plugin
3) Facebook
4) Find Duplicates 2
5) Flickr
6) jf PicasaWeb
7) Leica Tether Plugin
8) Nikon Tether Plugin
GPUDevice: D3D
MaxTexture2DSize: 8192
OGLEnabled: true
Renderer: Intel(R) HD Graphics 4600

Try closing the Metadata panel in the right column, or setting it to "Default". A number of us noticed lags in making selections that went away when setting it to Default. See the bottom of this thread for more details:
http://feedback.photoshop.com/photoshop_family/topics/lightroom_5_5_2_the_library_module_i s_painfully_slow

Why doesn't the Map module work with Lightroom 5.6 on OSX Yosemite?

Since upgrading to OSX Yosemite the Map module won't display the roads or satellite images with Lightroom 5.6. Sometimes it will download a small portion of the imagery but then it just displays the message "No imagery available". If I try and zoom in all I get is a blank view.
It's nothing to do with my internet connection as Google Maps in Safari comes up instantly.

Adobe acknowledged this problem some months ago in the official Adobe feedback forum, but it still hasn't been addressed:
Lightroom: Issue with Map module in OS X 10.10 (Yosemite)
Please add your vote and opinion to that topic.

Lightroom Map Module

I opened the Map Module in LR 5.3 and LR stopped working. I have tried shutting the program down and restarting and also completely shutting the PC down and restarting and nothing will work. LR starts and I can not close the module before the same notification comes up telling me that LR has stopped working. I need help

Apparent Solution Found: Apparently the Beta release of the Mac OS update is fixing this. Review the recent posts at this link. Lightroom: Issue with Map module in OS X 10.10 (Yosemite)

Lightroom CC: In the Map module, why is the Map Tracklog"Auto-Tag Photos" choice inactive?

In the Lightroom CC Map module, the "Auto-Tag Photos" choice in the Main Menu > Map > Tracklog submenu is inactive (grayed out) when I try to tag GPS metadata from a tracklog to a selected photo. However, for the same tracklog and selected photo, the Auto-Tag 1 Selected Photo choice in the tracklog menu in the Toolbar is active and I can successfully tag the photo with GPS metadata from the tracklog using it. (Lightroom CC (2015) running on Mac OS X, Ver. 10.10.3). Can someone tell me why this might be?

Auto-tag greyed out - solution
1. Click on Start(Windows)+R in your Windows 8computer to open the Run Dialog box.
2. Type %appdata% in the Run Dialog box and hit enter.
3. Open the Adobe folder.
4. Open the Lightroom folder.
5. Open the Preferences folder.
6. And rename the file Lightroom 5 preferences.agprefs to Lightroom 5 preferences.agprefs.old
7. reopen the Lightroom and check if your issue has resolved.

Lightroom 4.2: Wrong time in map module

In Lightroom 4.2 I use the map module in the following way:
1. Load a gpx-Track
2. Select one or all tracks
3. Select the photos to be tagged
4. Select the correct time zone shift (normally the time interval of the track contains the time interval of the photos)
5. Tag the selected photos
Now all photos are tagged correctly. But there is one small bug:
moving the mouse along the track displayed in the map does not show the local time including the time zone shift but the UTC without time shift. This is somewhat confusing. I think this bug should be removable easyly.
Best regards

Same issue
Win8 x64, quad amd, hd5850, 2x 1T hdds + 60gig scratch + 160gig os,

Lightroom 4.4 .gpx files in Map Module

I have a Garmin Montana 600 GPS. When I attempt to import a .GPX tracklog from my GPS into the map module of Lightroom an error window pop's up on the screen and the file is not imported. Any suggestions?

Same issue
Win8 x64, quad amd, hd5850, 2x 1T hdds + 60gig scratch + 160gig os,

Why is the "Lightroom Help"(F1) and the "Map Module" Offline?

I ask because everything requiring Internet connection thru Lightroom appears fine, such as the Web Module! There is nothing wrong with my Home Network nor any usage of the Internet, except when it comes to the Map Module and contacting "Lightroom Help"(F1) from the HELP Menu within Lightroom! I have been using Lightroom for a couple of years without encountering this issue and am baffled as to how to address solving it. Any input would be appreciated!

This is a well-known issue with Lightroom. Lots of adjustment brush usage on a particular photo will cause high CPU usage.
If you need to do a lot of brushing, you may be better off doing these tasks in Photoshop.
By the way, I have no idea what SSBOD means, I have never seen that acronym before.

Lightroom LR4 - Map Module - Sticky mouse

Lightroom LR4 - Map Module - Sticky mouse Hi folks. When using the mouse to pan the map, the map sticks to the mouse for a while even when you release the button. This means you can pan teh map to a new location, release the mouse and the map continues to pan where you subsequently move the mouse to. Note: this does not happen with Google maps in the browser, so a problem with LR. Its' highly annoying to pan the map and then hold the mouse still for 2 or 3 seconds to avoid the map moving

Anyone?

Lightroom 4 Map Module Is Blank

I upgraded from LR3 to LR4 yesterday and was excited to dive into the Map module. Unfortunately, the map seems to be blank. I have selected an image with GPS information. The Map module correctly looks up the location of the photo (Magdalena, New Mexico). This seems like a rendering bug.
Update 1
Just to check, I installed LR4 onto another OS X 10.6.8 machine that had not previously had Lightroom and imported the same picture. The Map module worked correctly. So, I tried re-installing LR4 on the original machine. Unfortunately, it still does not work. I tried creating a new catalog and backing up and then deleting all preferences. The map is still blank...
I am open to suggestions so long as they don't involve re-installing the OS, as I just did a fresh install yesterday on this machine and therefore highly doubt that will accomplish anything other than wasting my time.
I am open to all sorts of alternatives, including but not limited to:
Running dtrace to look at library calls
attaching XCode to debug (though I would assume all the objects have been stripped), or
Starting up a WebDialogs/WebEx/VNC/TeamViewer/etc server for a dev to pry around on it or debug with XCode. Of course a debuggable build would greatly help with this.
Update 2
More defect info.
I created a new user on the system that is failing, started LR4, created a new catalog, imported the test photo, changed to Map module--still blank. Something on this particular system is causing the rendering failure.
So I figured what the heck, just to make sure, why don't I copy over the LR4 app from the system that is working. Still a blank map...
My next thought was that perhaps it was an issue with the non-accelerated graphics. So I disabled the graphics switching. Still a blank map...
Any help would be greatly appreciated. Thanks in advance.
--Lance

Thanks juckehu. You nailed the problem. I really appreciate you coming up with this solution.
As a programmer who develops software for all UNIX flavors, Mac OS X, and Windows, I find this not working on a case-sensitive filesytem behaviour to be rather ridiculous. I would be ashamed if my tools didn't work correctly because of something like this. Someone folks should be very embarassed, as from some searches I ran it seems like this issue has been around for a long time and with other Adobe products. So, apparently I now get to revert my Mac back to a Windows-esque case-insenstive filesystem. What a way to spend a Friday.

Can not drag and drop photos in Lightroom 4 map module

In Lightroom4 map module, I can not drag and drop photos onto the map from the filmstrip? I select the photos, and then try and grabbing them to drop them on the map and when I click on one of the pictures to grab, it deselects the others I've selected and only hightlights the one photo, ironically, I can not even drop the one photo onto the map.

Thank you Victoria. I thought I was grabbing it on the thumbnail, but I must not have been, I must have been as you said on the border. Sorry.
Thank you again for the help.

Crash when switching to maps module

More often than not, I find that Lightroom 5.6 crashes when I switch to the Maps module after importing files on my Mac running OS X 10.9.5. I have trouble reproducing it on-demand, but it's a pretty regular occurrence and quite frustrating. The latest crash dump looks like this:
Process:         Adobe Photoshop Lightroom 5 [20295]
Path:            /Applications/Adobe Photoshop Lightroom 5.app/Contents/MacOS/Adobe Photoshop Lightroom 5
Identifier:      com.adobe.Lightroom5
Version:         Adobe Photoshop Lightroom 5.6 [974614] (5.6)
Code Type:       X86-64 (Native)
Parent Process: launchd [174]
Responsible:     Adobe Photoshop Lightroom 5 [20295]
User ID:         501
Date/Time:       2014-10-05 09:42:32.759 -0700
OS Version:      Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: C951A3C7-6482-4EB0-4BAC-41FFE3F63645
Sleep/Wake UUID: A34BE294-7113-4FC7-8391-5C2425BA2A0C
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000020a394080
VM Regions Near 0x20a394080:
    MALLOC_LARGE           00000002066b7000-00000002068b5000 [ 2040K] rw-/rwx SM=PRV
-->
    MALLOC_LARGE           000000020c6ff000-000000020c74f000 [ 320K] rw-/rwx SM=PRV
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                           0x000000020a394080 0 + 8761458816
1   Webkit.dylib                   0x000000018e5c706f WebKitGetAPI + 983347
2   Webkit.dylib                   0x000000018e57eb9f WebKitGetAPI + 687203
3   Webkit.dylib                   0x000000018e95f464 WebKitGetAPI + 4752680
4   Webkit.dylib                   0x000000018e96467b WebKitGetAPI + 4773695
5   Webkit.dylib                   0x000000018e9647d4 WebKitGetAPI + 4774040
6   Webkit.dylib                   0x000000018e6c1740 WebKitGetAPI + 2009092
7   Webkit.dylib                   0x000000018e9b2642 WebKitGetAPI + 5093126
8   Webkit.dylib                   0x000000018e9b27b3 WebKitGetAPI + 5093495
9   com.apple.CoreFoundation       0x00007fff968d53e4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
10 com.apple.CoreFoundation       0x00007fff968d4f1f __CFRunLoopDoTimer + 1151
11 com.apple.CoreFoundation       0x00007fff969465aa __CFRunLoopDoTimers + 298
12 com.apple.CoreFoundation       0x00007fff968906a5 __CFRunLoopRun + 1525
13 com.apple.CoreFoundation       0x00007fff9688fe75 CFRunLoopRunSpecific + 309
14 com.apple.HIToolbox           0x00007fff8ff53a0d RunCurrentEventLoopInMode + 226
15 com.apple.HIToolbox           0x00007fff8ff537b7 ReceiveNextEventCommon + 479
16 com.apple.HIToolbox           0x00007fff8ff535bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
17 com.apple.AppKit               0x00007fff905c224e _DPSNextEvent + 1434
18 com.apple.AppKit               0x00007fff905c189b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
19 com.apple.AppKit               0x00007fff905b599c -[NSApplication run] + 553
20 com.apple.AppKit               0x00007fff905a0783 NSApplicationMain + 940
21 com.adobe.Lightroom5           0x00000001010fe527 main + 1107
22 com.adobe.Lightroom5           0x00000001010fe0cc start + 52
I'm only including info about the first thread because it's the one that crashed, but I have the whole thing if there's like to be something useful there.
It always seems to be related to displaying the map, and the WebKit reference above seems to back that up. Sometimes it'll display some tiles and then crash, and sometimes, like this time, it crashes before it displays any of the map. This has happened with earlier versions of OS 10.9 as well, but I can't find those diagnostic reports to see if they point to the same thing. I've tried throwing away my Lightroom preference file and purging the cache, but neither has helped. It's happened equally with photos that are already geotagged and ones that have no location information. I don't think I've ever seen it happen if I quit Lightroom after importing and before switching to the Maps module, so maybe that's a clue.
Has anyone else had this sort of issue with the maps module?
Rob

I frequently see this problem. Have not yet found a solution. It is not a fatal error -- no data is lost, nothing seems to be corrupted. Since I'm not a programming expert, I can't really guess. I do get the impression that Lightroom, for all it's fantastic features (and I do think they're fantastic), it is very slow (though I am working on pre-Intel Mac).

Lightroom 5.7 Map module so slow it is almost useless

Similar Messages

Maybe you are looking for