Skip to main content
Inspiring
August 4, 2014

P: Issue with Map module in OS X 10.10 (Yosemite)

  • August 4, 2014
  • 302 replies
  • 4770 views

On OS X 10.10 (Yosemite), the map in Lightroom's Map module is very slow to load. It takes several minutes before the first part of the map appears, and some parts don't load at all, saying instead "Sorry, we have no imagery here", even though the part in question is on Google Maps. When zooming in or out, it's the same, it takes very long to update.

This topic has been closed for replies.

302 replies

Heliodon
Participating Frequently
October 27, 2014
I recently upgraded my desktop and laptop to OSX 10.10 and now find the Maps section of Lightroom 5.6 crippled. On both of my machines the maps either fail to load, load partially (missing tiles), or load very slowly (~15 minutes).

I rely on the Maps section and geotagging for my work. Please attend to this issue, which I understand has been known for three months now.

Help!
Participating Frequently
October 27, 2014
Pretty conclusive. I have just had an hour of perfect maps, and managed to geotag loads. The download finished in Windows 8.1/Parallels and bingo, back to "Sorry we have no imagery here".

If the machine isn't actively downloading somewhere, then LR won't fetch. Actiev download anywhere (including other VMs in //) then it works.

Utterly bizarre. What on earth is going on?
Inspiring
October 27, 2014
Mark

How totally bizarre! I will experiment later......
Participating Frequently
October 27, 2014
Now this *is* bizarre.

I've initiated the download (of LR) in Windows 8.1 in parallels. To kill time, I flipped back to the running lightroom in the native Mac....and the maps download =:-O

If I pause the windows download after a few seconds the maps stop. If I restart the windows download, after a few seconds maps starts working again.

Utterly bizarre.
Participating Frequently
October 27, 2014
Dear Mr Adobe,

I don't think you're reading this. And I don't think you're going to fix this quickly, despite the fact that you have known about it for three months.

As a last-ditch attempt to get going again, I'm going to install LR in my parallels Windows 8.1 partition and try it there. If it barfs about licensing issues, I think I'll probably go off my trolley. I assume this is ok with you?

But, to be honest, I'd much rather Lightroom actually worked on the Mac.
Participating Frequently
October 26, 2014
I have just left Trustpilot review of LR and asked that trust pilot forward this onto adobe maybe they will read that
https://www.trustpilot.co.uk/review/w...
Inspiring
October 26, 2014
I totally agree Mark, Adobe's silence on this is both bizarre and unacceptable.

What are they so scared of? They should have broad enough shoulders to at least acknowledge the issue. Very disappointing from a company that actually charges a lot for their software which I am happy to pay when it works!!
Participating Frequently
October 26, 2014
Thank you John glad that it helps the cause good old google had no idea what console was
Participating Frequently
October 26, 2014
This is quite bizarre. We have a major company, an acknowledged bug for 3 months and complete, utter, stony silence from the company.

I have to say I am struggling to see what Adobe's game plan is here. It certainly isn't going to keep them in pole position. Real shame, because Lightroom is a very nice piece of software. But 5/6 of Lightroom for 12 weeks isn't. Especially when a bunch of users appear to have located the problem.

It's the silence which is annoying.
johnrellis
Legend
October 26, 2014
Yes, your console log also shows "HTML Trace" errors from Lightroom, with names that indicate it's related to the maps.