Aperture Importer stalls during import - can I resume?

I tried to import my photos from Aperture to Lightroom using Adobe’s tool with no success. Every time I try, the import stalls after about 25-27% complete. To make sure I don't end up with duplicates in my new Lightroom catalog I deleted all the images that were imported (both in the LR catalogs as well as at the physical location on my NAS where I had copied them to as part of the migration process).
Is there a way to resume such a stalled import without producing duplicates in both LR and in the folder structure on my NAS or do I have to start all over from scratch (only to end up with another stall …)?

I haven’t seen this problem with my own eyes, but it’s not surprising. After all, Adobe’s developers are having to figure out what’s going on inside Aperture libraries, and Apple aren’t helping them!
My guess is that it’ll be something annoyingly simple – like odd text characters in metadata or an unusual file – which you may be able to fix in Aperture before doing the import again.
To see where the problem happened, in your Documents folder should be a LibraryImporter.log file. Double-click this file and it should open in the Console application, and the most recent entries might reveal information about where the problem occurred.

Similar Messages

Aperture shut down during import

I started the import of photos from iPhoto to Aperture. Aperture shut down in the process. How do I upload only the photos that did not transfer? I tried import again, but it appears to want to upload the entire library again..

Have you done any work in the Aperture Library? If not, just delete it and redo the import into a new Library.
This may be a good idea anyway, until you determine what caused Aperture to shut down during the last import. Aperture allows you to easily merge Libraries.
Make a back-up of your iPhoto data first -- after confirming that nothing was harmed when Aperture shut down while importing.
Also, if you haven't upgraded your OS to the current version (you have 10.7.1 listed), you should.

Premiere Pro CC and After Effects CC - Dynamic Link of an .aep not working - Stalls during import

I have been trying to import an .aep file into Premiere Pro CC from After Effects CC. As suggested, I import the file. The dynamic import window appears. It states connected to file along with the import files ... dialogue box. It stalls there.
I have been working off my network and have all the files collected on my machine.
My workaround to get me to deadline was to render my clips from AE and import them. Importing the .aep would make more sense from efficiency and workflow.
Thank you

Thank You, Jim -
Unfortunately that specifically did not work.
Based on another comment sent to me, here is what did.
In PProCC
File > Adobe Dynamic Link > New After Effects Composition
In AECC
From that composition created from PPro, I imported the project (aep) initially created in AECC from another team member. Saved the file.
Back in PProCC
File > Adobe Dynamic Link > Import After Effects Composition
Magic.

Aperture 3 stalls while importing photo folders

It appears that one of the latest updates for Aperture 3 now creates a situation where it just stops importing, even though it says it is still importing. The progress wheels stop moving and the hard drive stops blinking and it just sits there. This problem did not exist before one of the more recent updates. Yes, it does now import faster, but it is now unreliable. I now only import about 6 folders at a time because about every six or eight batches of folders I have to activate Quit Aperture, where it does not quit, and then I have to use option command escape to force quit. Then I reload and have to inspect to see if some of the folders need to be reinstalled. A pain in the butt. I would rather have a slower, more reliable folder import.

I suspect your Aperture Library needs repairing. If you force quit Aperture, the Aperture Library may be left in an inconsistent state, because Aperture cannot complete the current transactions.
Before you try to import again, run the Aperture Library First Aid tools, to repair (or rebuild if necessary) your Aperture library.
Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library
If Aperture frequently hangs, try to avaoid force quit - it is risky with database applications. Sometimes you can quit an application from the Terminal, if it is unresponsive, see my user tip here:
If Aperture is unresponsive, how to avoid force quitting?
Besides an inconsistent Aperture Library that needs repairing, you may have imported an image or video that cannnot be processed, because it is defective or has an incompatible format. Than Aperture will try over and over again to process that one image or video and hang. Then you need to isolate the one imort that is causing this.
Regards
Léonie

Aperture Creating Doubles During Import

Hello,
Can someone help me determine why Aperture is creating doubles while importing photos? Within Aperture, the events only show single pictures but there are 2 copies of the same photo displayed within finder. Example:
DC101010.jpg
DC101010 (1).jpg
Some findings:
Happens on new files never imported and on files I've imported before (creating new events the 2nd time and unchecking "do not import duplicates")
Removing the file with a "(1)" in the name does not affect Aperture
The 2 files are identical in dates and size, with preview showing the same picture
Creating a new test library and importing did not fix the problem
Any ideas? Thanks.
Aperture 3.5.1
OS X 10.9.4
iMac

Happens on new files never imported and on files I've imported before (creating new events the 2nd time and unchecking "do not import duplicates")
Why are you "unchecking" the "Do not import duplicates", if you do not want to import duplicates?
DC101010.jpg
DC101010 (1).jpg
Which of the two files are you seeing highlighted, when you use "File > Reveal in Finder", when you select one of the image versions with duplicates? It should be the "DC101010 (1).jpg"
The only way, i can reproduce your issue when importing referenced images, is when I use the Import setting
"Store Files" with the folder selected, where the photos to be imported are currently in and the "Copy files" option selected.
This will write a duplicate to the folder you are importing from, in the example above in the Pictures folder.

Itunes Crashed During Download-Can't Resume Download

First, I am running Vista with a SATA drive. I download episodes of "The Office" to that drive them copy to a network location and play the files from there. This has worked the last couple of episodes. I am running version 7.0.2.16.
When I downloaded episode 19, itunes crashed during the download. Now when I check on the store icon in itunes, I get the message that "all purchases have been downloaded for this account". How can I get the episode I have paid for as part of a season pass?
Thanks in advance for any help you can offer. Making Vista and itunes play together so far has been more trouble than it is worth.
Jim
dell Other OS vista
dell Other OS vista

Jim,
If you can't resolve it, you might just need to ask the iTunes store to let you re-download it. Log into your account on iTunes, go to Account Information, click on Purchase History, go to the download in question, and click "Report a Problem."
The iTunes Store is real understanding about letting folks try to re-download an item if they have already purchased it.

Error during import (-40)

I have a G5 Dual 2G with 2G of ram running Imovie 3.0.3. I am trying to import a 42.9M mp4 file and a 189.9M .mov file and am getting this error message after about 6 minutes of trying to import: "Error during import (-40)".
Can anyone tell me what the problem might be? I have serched the forum and came up with the "Use Streamclip 1.8" thats why I could make the 189.9M .mov file into the 42.9M mp4 file.
I was sucsesful in importing 38.5M .mov files into itunes but I seem to have a limit. Does this make sense to anyone?
Thanks for the help.

Aquilafisher,
You can open the 189.9 mov file in MpegStream clip and export to DV format for iMovie (DV is iMovie's native format).
When you choose export to DV format you'll be presented with the "DV Exporter Window" with several options. One option is to "Split DV into Segements" Choose it (This option automatically splits the clip into 2gb or less segments).
You can export the segments directly into your iMovie project's media folder. Next time you open the iMovie project you'll be offered the option to have those segments moved to the clips pane (you can also import the segments but that takes longer).
I was sucsesful in importing 38.5M .mov files into itunes but I seem to have a limit.
Is this the same file 49mb mp4 file that you could only partially import or is this a different file that you were successful importing?????
Is there any particular reason you exported to mp4 first, exactly what are you trying to accomplish?

Aperture 3.6 - wrong image selected during import

Aperture 3.6
OS X Yosemite 10.10.1
MacBook Air
I run a program at a guest ranch where we import photos from our guests into Aperture. We see multiple devices and have this issue randomly on many of them.
Lets choose an iPhone for the example. Connect the iPhone, go to import, select the device, choose 'Uncheck All'.
Now when scrolling through the images, the guest will select a photo, and at times the image next to it will be checked as well without being selected by the guest. Sometimes it it the first or second image that is automatically selected during import.
Any ideas?
Best,
Lee

Problems with the UI can sometimes be resolved by removing the Preference file.
See Get help with Aperture 3 - Apple Support , scroll down until you see
Reset the user preferences
and follow the directions. Note in step 5 Restart your computer if you're using OS X Mavericks that will apply if you are running Yosemite also.
regards

Problem on PC: During import, I can locate the sources folder however the photo do not display. Was working fine.

Problem on PC: During import, I can locate the sources folder however the photo do not display. Was working fine. All file types, Lightroom is no longer recognising the images to import, The panel that usually displays them remains empty. Try using backup versions, removing software that could conflict , still no joy, has anyone had this problem?

Did you follow this procedure?
Our iTunes guru Terence Devlin advises the following:
1. Quit iTunes
2. Drag the iTunes folder from your internal hd - located in ~/Music folder - to your external hd. DO NOT delete the original one from your internal hd... yet!
3. When the transfer is complete, press and hold the Option(alt) key and fire up iTunes.
4. A "Choose iTunes Library" window will come up. Click on the "Choose Library" button.
5. Navigate to where the iTunes folder is located in the external hd.
6. Within the iTunes folder, select the iTunes Library file and click Choose...
That's it. iTunes will now display all your playlists, songs, movies, podcasts etc. At this point, should you wish, you can delete the iTunes folder from the internal hd to free up space.
More info:
http://support.apple.com/kb/HT1751
Or if you prefer a more complicated explanation:
http://www.ilounge.com/index.php/articles/comments/moving-your-itunes-library-to -a-new-hard-drive

Why is aperture 3.4 crashing during import after upgrade?

After running a typical upgrade from Software update on my mac I have had the problem of importing files into Aperture.
Exactly what happened and equipment used. Used SD 45mbs 16gb SD card to import RAW images after a shoot. This has been working and tested the day before update. Was prompted to update to Aperture 3.4 along with another update for OSX. After reboot I launched Aperture and was prompted to update library. Next SD card was inserted, pictures showed up as previews, all were selected and checked to import all. Application crashes see below.
What I have tired.
removed application
removed preference files
reinstalled application
was prompted for upgrade of library
once done inserted SD to import files
Same issue files show up but they do not import and same report comes up
have attempted multiple SD cards with no resolve.
Able to use disk on another computer with no issue.
Someone please help

What Aperture version are you running exactly? Aperture 3.4 or 3.4.1? The 3.4.1 update has some important bug fixes. If you did not install the last update, I'd recommend to update.
Some posters had problems with the image capture preferences, after upgrading to 3.4, and that caused troubles during import. Try if removing the image capture preference files helps:
To remove the image capture preferences:
If Aperture is running, quit Aperture, and log off and on again.
Open your user library from the Finder's Go menu: Hit Command Shift G (⌘⇧G) and then type in: ~/Library/Preferences/ then hit return.
In the window that opens remove "com.apple.ImageCapture.plist"
and look into the subfolder "ByHost": if there are files named com.apple.ImageCapture something.plist remove them too.
then try again.
Regards
Léonie

Can not find size_t during import a dll and calling a function crash labview

Hello, experts
I need to use FingerLakeInstrument DLL ( see the attached) inside Labview to talk to a CCD camera. it is built from microsoft visual studio C++
I unzip FLI dll in my D:\proj\...\linfli-32 and import dll from there. created a c:\FLIDBG.txt as FLI dll needs to write debug message to it if FLISetDebugLevel() or others are called.
During importing the dll, first thing I got is <sys/types.h> ( ie size_t ) cannot be found. I have installed free version of microsoft visual studio C++
but can not find "typedef unsigned int size_t"
at the end, I just added
typedef unsigned int size_t;
in the libfli.h. Having done that, I am able to import all functions into Labview and have a user library called libfli.
However, as soon as I start calling a simple function in a test.vi, such as FLIGetLibVersion(char* ver, size_t len), which involves nothing other than the library, the labview will crash.
I created a simple C test.exe which calls many functions without any problem
any suggstion?
regards
xiaofeng
Solved!
Go to Solution.
Attachments:
libfli-32.zip ‏93 KB

Hi, Smercurio_fc
thanks for your reply. Yes, you are pointing to the right place. I have solved the crash problem.
when importing DLL into Labview using Tools\import\Shared Library (.dll), Labview automatically set the calling convention as C not as stdcall (WINAPI). it is this that later the labview crashes when a function is called. as soon as I manually re-selecte calling convention as stdcall, my test.vi works OK (see attached).
I tried Call Library Function too to call libfli.dll, as long as I select stdcall as call convetion. the test.vi works.
How do I know which Call convention I need to choose if there is no infomation from DLL provider?
as for the size_t,
I add #include <crtdefs.h> in libfli.h and
add additional include path as
C:\Program Files\Microsoft Visual Studio 10.0\VC\include. this solved the "not found" issue.
for this case I know that the DLL is built from VC++, is this right way?
again, thanks for your time.
xiaofeng
Attachments:
test.vi ‏13 KB

I exported jpg, tif, psd, and dng files from Lightroom but Aperture does not see them except for dng during import

How do I import jpg, tif, psd files exported from Lightroom 3 into Aperture 3.2? I had no problems before...seems like since I installed Lion, they do not show up in the import folder.

How are you trying to import them (again) ? If you're importing through the Import Window and have RAW only set then that's all you'll get.
Also what's an Import Folder? Not sure how Lightroom fits into this. If you share your workflow with us we might be able to help.
regards

Power of File Naming during import

Can you append the HH (Hour) MM (Minute) SS (Second) that the photo was shot to the name while importing?
I have read that Aperture will not allow files to be renamed after in the Library to follow along with being non destructive. However I do not see renaming files or appending Meta Data in IPTC as being destructive and should not be ignored if the Photographer desires that to be part of his/her workflow.
I am sure that some third party programmers will write Automator scripts to accomplish many of the things that Aperture will be lacking in.
I am curious as to the power and functionality of Naming digital files as they are imported. I know that they can be tagged with YYMMDD. I have Read the Getting Started but want to know if HHMMSS can be appended also. I have searched the Internet for a naming convention that is very flexible and unique. When files are imported you do not know and can not say what is in each file, so better renaming and IPTC editing should be support post import. I do not consider preImport or during the best place to do this in Post Production. I think this can best be accomplished after using Aperture's Great Meta tagging tools.
I have accepted for for the majority of my workflow that Files should only be named once, and only tagged with a different name on an export. (Like appendning some Keywords).
I used to use a Random, Sequentually generated SN, but think now that the Date is nearly Unique (execpt Multiple Shots a second, or from other cameras at the same time.) I think that this SN to be tagged on the photo is more helpful.
Does any body recommend a powerful naming convention for digital image files?
Here is the naming Scheme that I am thinking of.
YYMMDD-HHMMSSx.CR2
X - is 0 through 9 to account for multiple shots a second.
I was planning on using the sequential numbering. This will allow me to easily speak out differenced between multiple files in a stack by speaking the last number which will usually be unique.
I have also thought about YYMMDD-ABC-HHMMSSx.cr2 (ABC would identify the roll) which is similar to what I have used, but I am do not like ABC now because it might mislead me or not mean anything at all.
What is everybody using, and what is working for you???
(and again)
Can you append the HH (Hour) MM (Minute) SS (Second) that the photo was shot to the name while importing?
PowerMac G5 Mac OS X (10.4.3)

Yes, after playing with it at home, I confirm the same things. All of the - (dashes) and .(dots) and 'PM' is wasteful, and aperture will not even show that full name.
Naming is a Huge deal. The photos will not be in Aperture forever, and when they come back out during an export or whatever, they should be how you want them. Not having control makes using aperture as a Library for your photos and projects weak.
If Aperture starts at the import from digital media, then naming happens only after that point. If I have to rename files before importing them into aperture then, I have to skip Aperture's first Steps.
When I name photos I have in the past tagged some keywords to the file name. Stacks and smart albums would do great to help, but after I put all of the work into naming and organizing, the filenames can not be set to what I want them to be.
This means that I would still have to use a 3rd party app to organize sort and name all photos then import to aperture.
Now the Stacks functionality, and keyword tagging can be skipped in Aperture. What is left are versions, working with RAW and smart albums. And Spotlight would do just as good of a job searching for photos this way.
I do not want to knock Aperture, but I have to accept that it is a learning curve. I need to learn what it can do for me to save time. And I need to learn what it will not do so that I can stay away from it. I was really looking forword to it being my post production SW.
I would like for something like this.
YYMMDD-HHMMSSx-Grouping Keyword(IPTC)-1 of 7(in stack)
This would use the Keyword and IPTC That you work hard to set in aperture, and also the stacking. Then when they are exported to clients, or for backup, web, or use when aperture has reached EOL, then it can be very useful.
I like that iPhoto has 3rd party extensions to use Keywords to Save in photo or extract from photo to add to iPhoto Library. I am a little more afraid of Aperture because it is a closed system. If a 3rd party app sets keywords to a photo or renames it, what info would be lost in Aperture.
Thanks for all of the thougts.

Import Stalls from CF Reader

Does anybody know why Aperture stalls at the beginning of an import session of raw images from an 8-GB SanDisk card, using a SanDisk card reader (it has the same behavior from the camera)? Aperture shows the spinning progress indicator and "Scanning."
Can I drag-and-drop the images from the CF card to a project?

Jerry DaBell wrote:
Does anybody know why Aperture stalls at the beginning of an import session of raw images from an 8-GB SanDisk card, using a SanDisk card reader (it has the same behavior from the camera)? Aperture shows the spinning progress indicator and "Scanning."
Do not import directly from camera or card into Aperture or any other application. Instead Finder-Copy the images from the card to an appropriate original-images folder on the hard drive. After backup and ejection of the card import from the newly created original-images folder on the hard drive.
Also, set Previews to be built manually when you are otherwise not working in Aperture. Automatic Preview-building can kill an Aperture workflow.
Also Max the RAM and make sure that hard drives stay less than 70% full, and do not use (slow) USB for hard drives, except for backup. Ideally by a FW card reader for loading from CF and use fast CF cards.
Can I drag-and-drop the images from the CF card to a project?
No.
HTH
-Allen Wicks

Adding timezone metadata that Aperture will recognize on import

I have 3,200 scanned photos, and a spreadsheet with the time, date and timezone of each one on it (my APS photos, 1997~2004), and I have been making exiftool scripts to write the time and date into each file.
However, I have been unable to make the timezone work on import, I have to use Aperture's import panel to set it, which is okay, but there are 3 different timezones, different DST's etc. etc. over the archive.
I want to be able to write the timezone into the metadata before I import, and have Aperture pick up on it and use it.
I've tried the -TimeZoneOffset, I've tried setting the GPSDate and Time to UTC, and the AllDates to the local time - all to no avail - Aperture seems to ignore this information, and defaults to my computers timezone during import - I can override it for the the whole import, but I would have to separate out the photos into timezones, and import one timezone at a time.
Anyone had any joy with timezone meta data prior to import? (I understand you can set it after import).
For cameras that include home and destination support (home city / destination city) that information is also ignored - I was hoping to make my script emulate that.
I guess a better question is, has anyone been able to have Aperture detect the timezone on import and what metadata did that file have in it?
Thanks.

Had a quick read of the Wikipedia "EXIF" entry and references, it talks about tools for editing exif information.
http://en.wikipedia.org/wiki/Exchangeableimage_fileformat
+"There are many software tools available which allow both viewing and editing of Exif data. The Opanda IExif Viewer is a free stand-alone application for viewing Exif data and also a plug-in for Internet Explorer and Firefox on Windows platforms. It allows examination of detailed Exif data online by right clicking on an image.[11] FxIF and Exif Viewer are multi-platform extensions for Firefox that display Exif data in the image properties dialog. This feature is native in the web browser Opera, under image properties.+
+Retrieval of detailed Exif data not usually displayed by other programs can be accomplished using ExifTool which runs in Perl, and is available for all platforms"+
Tony

Aperture Importer stalls during import - can I resume?

Similar Messages

Maybe you are looking for