Skip to main content
Participant
April 5, 2022
Question

Aperture Import not working on Monterey (M1)

  • April 5, 2022
  • 3 replies
  • 594 views

I am trying to import old Aperture libraries into Lightroom Classic.

I made several attempts at this during the CC trial, and had to cancel, as could not get my library migrated across.

 

I can even get to the first step, and I cannot get the "Import" button to enable.

 

Before I even start I notice that the "Disk Space Available" section does not contain any information, which is should according to any documentation.

 

After I select the library, it seems to successfully select it, but does not attemp to read it, or update information about number of images. The "Import" button remains greyed out.

 

I do notice errors in the log. (~/Documents/LrClassicLogs/LibraryImporter.log)

 

When I just open the dialogue, it explain why I don't see the disk space available, as there is an error:

2022-03-24 20:33:31.4950000Z, INFO	Failed to obtain information on available disk space! (error: nil)

 

Subsequentally, when I select my Aperture library, I see additional errors:

2022-03-24 20:33:44.1970000Z, INFO	Failed to get info on image versions with error nil
2022-03-24 20:33:44.2370000Z, INFO	Failed to obtain info on number of master images in trash with error nil
2022-03-24 20:33:44.2740000Z, INFO	Failed to obtain size of masters from Aperture library with error nil

 

This is running the latest 11.2 LRC, on Monterey 12.3.1 (now on latest update - original attempts on older version).

This is running on a MBP with M1 Pro. This is a new machine, so no strange setup. 

 

Had anyone attempted to even just launch the plugin on Monterey? Does even the Disk Spave Available work when launching for anyone?

 

This topic has been closed for replies.

3 replies

Participant
April 7, 2022

I had previously tried launching as an Intel app, and that didn't work either unfortunately.

 

-----

 

But anyone should be able to see at least part of the issue if they just open the importer.

 

 

You will see straight away that Disk Space Available is blank, which I believe is normally set straight away.

You will also see errors in the importer log.

 

 

No need to have an aperture library to reproduce this part of the issue.

 

johnrellis
Legend
April 6, 2022

The Aperture/Iphoto Importer Plug-in has long had many bugs -- it was poorly implemented. If Johan's suggestion helps, you could still run into these other bugs (hangs, days and weeks to convert libraries larger than a few thousand photos, etc.). If you don't make much progress, try Avalanche, a paid program that many people have reported worked well for them. 

Participant
August 27, 2022

OMG johnrellis... CYME Avalanche...

 

This is the COOLEST piece of software I have seen EVER.

I have been struggling with a complex Aperture-to-Lightroom migration for about EIGHT years, blunting and falling on my sword after each swipe at it, giving up for months at a time, licking my wounds, and mustering the strength to try again.

You are a master of understatement: the Plug-in is indeed useless, and Avalanche is over-the-top brilliant.

This software slayed the 8-year dragon in about 8 minutes for US$59.

Couldn't be happier. Thanks to you and CYME.io for coming to the rescue !!! 

JohanElzenga
Community Expert
Community Expert
April 6, 2022

I'm not sure, but this may be due to Lightroom Classic running M1 natively and the importer running in Rosetta 2 emulation. Try this: Open the Creative Cloud app, click on the three points next to the 'Open' button and launch Lightroom Classic in Intel mode.

 

-- Johan W. Elzenga