IPad photo syncinc problem from Aperture
Hi,
I have a weird photo sync problem (Itunes 10.0.1, Aperture 3.0.3). Sometimes when I add a project to Aperture and an album under that project, I can't sync that to my ipad as Itunes doesn't see any pictures in the album.
My Aperture library is huge so I'm not syncinc all of it, just selected photos. When I open iTunes, plug iPad in and go to iPad photos page, the project and the album appear in the list but if I check either one of those, the number on the right showing the number of photos in the album/project, is zero and nothing gets synced.
Sometimes I've been able to fix this by restarting aperture and itunes. I've tried reprocessing previews (previews are 2560x2560) but it doesn't seem to help anymore.
I've sort of localised the problem to Aperture. When I quit aperture, an information window "updating information for sharing previews" and a progress bar apperars. If this takes only a couple of seconds, then iTunes doesn't seem to detect any changes I've made. Sometimes it takes from 30 seconds to a minute and usually after that everything works.
I tried to google this and others seem to have had similar problems but I didn't find a solution. Is there one?
Hello,
Try the troubleshooting help Aperture 3: Troubleshooting Basics
Repairing the Aperture database and repairing permissions may help.
If you have Aperture 2, go here. Aperture 2: Troubleshooting Basics
Carolyn
Similar Messages
-
Ipad picture download problem from aperture
I have downloaded 54000 pictures on my ipad 1 from aperture. It works until I installed the IOS5 on the Ipad, now downloading stop after 500 pictures are downladed. I still have snom leopard on my imac
Hello,
Try the troubleshooting help Aperture 3: Troubleshooting Basics
Repairing the Aperture database and repairing permissions may help.
If you have Aperture 2, go here. Aperture 2: Troubleshooting Basics
Carolyn -
Having issues publishing certain photos to website from Aperture.
Hi All,
I really hope someone can help me with this. I created a new website yesterday and had no problems publishing everything to my website. This included dragging photos from Aperture to iWeb, creating photo albums and such. Late last night, I tried to add a new album with all new photos that were from Aperture just like before. Once I had customized the new album (which is exactly like the other albums, just different pictures) I hit publish and I get an error message every time. It's saying there's a problem publishing because of the FTP and to contact my service provider. I contacted Yahoo Small Business, and after running a few tests on my account, they said everything was working fine on their end.
I thought maybe the pictures were too big, so I resized them to under 1MB, but I still can't get them to publish and am still getting the same error message! The photos are in .jpg format just in case you're wondering. Any ideas or suggestions on what I should do to try and get this working?
I'm totally new at making a website, so please be thorough when responding. Thanks so much!Are you able to publish the site to a folder on your hard drive? If so then it's not an iWeb problem per se but a communications prolbem with the server.
You might have to try the publishing to a folder and use a 3rd party FTP client like the free Cyberduck to upload the site to the server. I'd get Cyberduck, configure it for your server and see if you can get it to login and view your account folder on the server.
Otherwise you can try the following:
delete the iWeb preference file, com.apple.iWeb.plist, that resides in your Home()/Library/Preferences folder.
go to your Home()/Library/Caches/com.apple.iWeb folder and delete its contents.
launch iWeb and try again.
If that doesn't help continue with:
move the domain file from your Home/Library/Application Support/iWeb folder to the Desktop.
launch iWeb, create a new test site, save the new domain file and close iWeb.
go to the your Home/Library/Application Support/iWeb folder and delete the new domain file.
move your original domain file from the Desktop to the iWeb folder.
launch iWeb and try again.
OT -
Can a photo be exported from aperture in CMYK profile
Can a photo be exported from aperture in CMYK profileas TIFF jpeg PSD etc .?
Yes, in the export dialogue panel pick a TIFF or PSD setting, and then set the colorsync profile selector to a cmyk-profile,
You need to have installed cmyk-profiles, however;
most of my colorsync profiles were installed by photoshop.
You will find the cmyk-profiles in the system library:
/Library/ColorSync/Profiles/
Regards
Léonie -
Unlogged Missing Photos After Import From Aperture
Hi!
I have just made the switch from Aperture to Lightroom, and have use the 1.1 version of the Aperture import plugin.
In my Aperture Library I have, according to the Library -> Photos: 11105 Photos, however after importing to Lightroom, I have only 10967 photos. I have checked the import log, and there were 4 items which failed to import - 3 were .mpo files (panoramas from an xPeria) and 1 was a .gif file. This leaves a deficit of 133 photos that I can't account for.
Is there any way to compare the aperture library to the lightroom library to see what is missing?*WARNING* Once agin, this is a VERY long post! And this contains not only SQL, but heaps of command line fun!
TLDR Summary: Aperture is storing duplicates on disk (and referencing them in the DB) but hiding them in the GUI. Exactly how it does this, I'm not sure yet. And how to clean it up, I'm not sure either. But if you would like to know how I proved it, read on!
An update on handling metadata exported from Aperture. Once you have a file, if you try to view it in the terminal, perhaps like this:
$ less ApertureMetadataExtendedExport.txt
"ApertureMetadataExtendedExport.txt" may be a binary file. See it anyway?
you will get that error. Turns out I was wrong, it's not (only?) due to the size of the file / line length; it's actually the file type Aperture creates:
$ file ApertureMetadataExtendedExport.txt
ApertureMetadataExtendedExport.txt: Little-endian UTF-16 Unicode text, with very long lines
The key bit being "Little-endian UTF-16", that is what is causing the shell to think it's binary. The little endian is not surprising, after all it's an X86_64 platform. The UTF-16 though is not able to be handled by the shell. So it has to be converted. There are command line utils, but Text Wrangler does the job nicely.
After conversion (to Unicode UTF-8):
$ file ApertureMetadataExtendedExport.txt
ApertureMetadataExtendedExport.txt: ASCII text, with very long lines
and
$ less ApertureMetadataExtendedExport.txt
Version Name Title Urgency Categories Suppl. Categories Keywords Instructions Date Created Contact Creator Contact Job Title City State/Province Country Job Identifier Headline Provider Source Copyright Notice Caption Caption Writer Rating IPTC Subject Code Usage Terms Intellectual Genre IPTC Scene Location ISO Country Code Contact Address Contact City Contact State/Providence Contact Postal Code Contact Country Contact Phone Contact Email Contact Website Label Latitude Longitude Altitude AltitudeRef
So, there you have it! That's what you have access to when exporting the metadata. Helpful? Well, at first glance I didn't think so - as the "Version Name" field is just "IMG_2104", no extension, no path etc. So if we have multiple images called "IMG_2104" we can't tell them apart (unless you have a few other fields to look at - and even then just comparing to the File System entries wouldn't be possible). But! In my last post, I mentioned that the Aperture SQLite DB (Library.apdb, the RKMasters table in particular) contained 11130 entries, and if you looked at the Schema, you would have noticed that there was a column called "originalVersionName" which should match! So, in theory, I can now create a small script to compare metadata with database and find my missing 25 files!
First of all, I need to add that, when exporting metadata in Aperture, you need to select all the photos! ... and it will take some time! In my case TextWrangler managed to handle the 11108 line file without any problems. And even better, after converting, I was able to view the file with less. This is a BIG step on my last attempt.
At this point it is worth pointing out that the file is tab-delimited (csv would be easier, of course) but we should be able to work with it anyway.
To extract the version name (first column) we can use awk:
$ cat ApertureMetadataExtendedExport.txt | awk -F'\t' '{print $1}' > ApertureMetadataVersionNames.txt
and we can compare the line counts of both input and output to ensure we got everything:
$ wc -l ApertureMetadataExtendedExport.txt
11106 ApertureMetadataExtendedExport.txt
$ wc -l ApertureMetadataVersionNames.txt
11106 ApertureMetadataVersionNames.txt
So far, so good! You might have noticed that the line count is 11106, not 11105, the input file has the header as I printed earlier. So we need to remove the first line. I just use vi for that.
Lastly, the file needs to be sorted, so we can ensure we are looking in the same order when comparing the metadata version names with the DB version names.
$ cat ApertureMetadataVersionNames.txt | sort > ApertureMetadataVersionNamesSorted.txt
To get the Version Names from the DB, fire up sqlite3:
$ sqlite3 Library.apdb
sqlite> .output ApertureDBMasterVersionNames.txt
sqlite> select originalVersionName from RKMaster;
sqlite> .exit
Checking the line count in the DB Output:
$ wc -l ApertureDBMasterVersionNames.txt
11130 ApertureDBMasterVersionNames.txt
Brilliant! 11130 lines as expected. Then sort as we did before:
$ cat ApertureDBMasterVersionNames.txt | sort > ApertureDBMasterVersionNamesSorted.txt
So, now, in theory, running a diff on both files, should reveal the 25 missing files.... I must admit, I'm rather excited at this point!
$ diff ApertureDBMasterVersionNamesSorted.txt ApertureMetadataVersionNamesSorted.txt
IT WORKED! The output is a list of changes you need to make to the second input file to make it look the same as the first. Essentially, this will (in my case) show the Version Names that are missing in Aperture that are present on the File System.
So, a line like this:
1280,1281d1279
< IMG_0144
< IMG_0144
basically just means, that there are IMG_0144 appears twice more in the DB than in the Metadata. Note: this is specific for the way I ordered the input files to diff; although you will get the same basic output if you reversed the input files to diff, the interpretation is obviously reversed) as shown here: (note in the first output, we have 'd' for deleted, and in the second output it's 'a' for added)
1279a1280,1281
> IMG_0144
> IMG_0144
In anycase, looking through my output and counting, I indeed have 25 images to investigate. The problem here is we just have a version name, fortunately in my output, most are unique with just a couple of duplicates. This leads me to believe that my "missing" files are actually Aperture handling duplicates (though why it's hiding them I'm not sure). I could, in my DB dump look at the path etc as well and that might help, but as it's just 25 cases, I will instead get a FS dump, and grep for the version name. This will give me all the files on the FS that match. I can then look at each and see what's happening.
Dumping a list of master files from the FS: (execute from within the Masters directory of your Aperture library)
$ find . -type f > ApertureFSMasters.txt
This will be a list including path (relative to Master) which is exactly what we want. Then grep for each version name. For example:
$ grep IMG_0144 ApertureFSMasters.txt
./2014/04/11/20140411-222634/IMG_0144.JPG
./2014/04/23/20140423-070845/IMG_0144 (1).jpg
./2014/04/23/20140423-070845/IMG_0144.jpg
./2014/06/28/20140628-215220/IMG_0144.JPG
Here is a solid bit of information! On the FS i have 4 files called IMG_0144, yet if I look in the GUI (or metadata dump) I only have 2.
$ grep IMG_0144 ApertureMetadataVersionNamesSorted.txt
IMG_0144
IMG_0144
So, there is two files already!
The path preceding the image in the FS dump, is the date of import. So I can see that two were imported at the same time, and two separately. The two that show up in the GUI have import sessions of 2014-06-28 @ 09:52:20 PM and 2014-04-11 @ 10:26:34 PM. That means that the first and last are the two files that show in the GUI, the middle two do not.... Why are they not in the GUI (yet are in the DB) and why do they have the exact same import date/time? I have no answer to that yet!
I used open <filename> from the terminal prompt to view each file, and 3 out of my 4 are identical, and the fourth different.
So, lastly, with a little command line fu, we can make a useful script to tell us what we want to know:
#! /bin/bash
grep $1 ApertureFSMasters.txt | sed 's|\.|Masters|' | awk '{print "<full path to Aperture Library folder>"$0}' | \
while read line; do
openssl sha1 "$line"
done
replace the <full path to Aperture Library folder> with the full path to you Aperture Library Folder, perhaps /volumes/some_disk_name/some_username/Pictures/.... etc. Then chmod 755 the script, and execute ./<scriptname> <version name> so something like
$ ./calculateSHA.sh IMG_0144
What we're doing here is taking in the version name we want to find (for example IMG_0144), and we are looking for it in the FS dump list. Remember that file contains image files relative to the Aperture Library Master path, which look something like "./YYYY/MM/DD/YYYYMMDD-HHMMSS/<FILENAME>" - we use sed to replace the "./" part with "Masters". Then we pipe it to awk, and insert the full path to aperture before the file name, the end result is a line which contains the absolute path to an image. There are several other ways to solve this, such as generating the FS dump from the root dir. You could also combine the awk into the sed (or the sed into the awk).. but this works. Each line is then passed, one at a time, to the openssl program to calculate the sha-1 checksum for that image. If a SHA-1 matches, then those files are identical (yes, there is a small chance of a collision in SHA-1, but it's unlikely!).
So, at the end of all this, you can see exactly whats going on. And in my case, Aperture is storing duplicates on disk, and not showing them in the GUI. To be honest, I don't actually know how to clean this up now! So if anyone has any ideas. Please let me know I can't just delete the files on disk, as they are referenced in the DB. I guess it doesn't make too much difference, but my personality requires me to clean this up (at the very least to provide closure on this thread).
The final point to make here is that, since Lightroom also has 11126 images (11130 less 4 non-compatible files). Then it has taken all the duplicates in the import.
Well, that was a fun journey, and I learned a lot about Aperture in the process. And yes, I know this is a Lightroom forum and maybe this info would be better on the Aperture forum, I will probably update it there too. But there is some tie back to the Lightroom importer to let people know whats happening internally. (I guess I should update my earlier post, where I assumed the Lightroom Aperture import plugin was using the FS only, it *could* be using the DB as well (and probably is, so it can get more metadata))
UPDATE: I jumped the gun a bit here, and based my conclusion on limited data. I have finished calculating the SHA-1 for all my missing versions. As well as comparing the counts in the GUI, to the counts in the FS. For the most part, where the GUI count is lower than the FS count, there is a clear duplicate (two files with the same SHA-1). However I have a few cases, where the FS count is higher, and all the images on disk have different SHA-1's! Picking one at random from my list; I have 3 images in the GUI called IMG_0843. On disk I have 4 files all with different SHA-1's. Viewing the actual images, 2 look the same, and the other 2 are different. So that matches 3 "unique" images.
Using Preview to inspect the exif data for the images which look the same:
image 1:
Pixel X Dimension: 1 536
Pixel Y Dimension: 2 048
image 2:
Pixel X Dimension: 3 264
Pixel Y Dimension: 2 448
(image 2 also has an extra Regions dictionary in the exit)
So! These two images are not identical (we knew that from the SHA-1), but they are similar (content is the same - resolution is the same) yet Aperture is treating these as duplicates it seems.. that's not good! does this mean that if I resize an image for the web, and keep both, that Aperture won't show me both? (at least it keeps both on disk though, I guess...)
The resolution of image 1, is suspiciously like the resolutions that were uploaded to (the original version of) iCloud Photos on the iPhone (one of the reasons I never used it). And indeed, the photo I chose at random here, is one that I have in an iCloud stored album (I have created a screensaver synced to iCloud, to use on my various Mac's and AppleTVs). Examining the data for the cloud version of the image, shows the resolution to be 1536x2048. The screensaver contains 22 images - I theorised earlier that these might be the missing images, perhaps I was right after all? Yet another avenue to explore.
Ok. I dumped the screensaver metadata, converted it to UTF-8, grabbed the version names, and sorted them (just like before). Then compared them to the output of the diff command. Yep! the 22 screensaver images match to 22 / 25 missing images. The other 3, appear to be exact duplicates (same SHA-1) of images already in the library. That almost solves it! So then, can I conclude that Lightroom has imported my iCloud Screensaver as normal photos of lower res? In which case, it would likely do it for any shared photo source in Aperture, and perhaps it would be wise to turn that feature off before importing to Lightroom? -
Yesterday 10-4-2011, I downloaded the Aperture App. I haven't gone to my Aperture class yet, but wanted to know why the photo place holder in an email stationary application will not accept a drag and drop from the Aperture library. I did find only one photo that actually did populate, what do you think is the difference with all the rest of my photos?
I did import all my photos and movies to Aperture from the iPhoto Library and then deleted my iPhoto Library.
ThanksYesterday 10-4-2011, I downloaded the Aperture App. I haven't gone to my Aperture class yet, but wanted to know why the photo place holder in an email stationary application will not accept a drag and drop from the Aperture library. I did find only one photo that actually did populate, what do you think is the difference with all the rest of my photos?
I did import all my photos and movies to Aperture from the iPhoto Library and then deleted my iPhoto Library.
Thanks -
Importing photos into iphoto from aperture
I just upgraded to Snow Leopard not realizing Aperture 1.5.6 would not open again. I do not use Aperture enough to pay for an upgrade and want to import my photos into iPhoto for future use. How do I do this (where are the files) and keep the quality of the pictures? If I can get the data into iphoto, can i then delete the aperture file? Thanks
The correct way to do this is to Export from Aperture to folders on the Desktop and then import to iPhoto.
As Aperture 1 won't open for you, you could download a trial of Aperture 2, open your Library, do the exports and then trash the app and the library.
This has the added advantage of it being possible to access versions, metadata that you added in Aperture etc
Otherwise:
Go to your Pictures Folder and find the Aperture Library there.
Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed.
Inside you will see a lot of stuff but you are looking for the .approject packages
So, you will see something like
JohnsBirthday.apprproject
Right click on that and go Show Package Contents
A new window opens with the project exposed.
Look for a folder called XXXX @ YYYY - 1.apimportgroup - where X and Y are the date and time of the import. Insie that you'll find a folder for each shot you imported. Just drag the original out of there to a folder on the desktop.
Repeat. And Repeat. And Repeat for each photo in your Aperture Library.
This will yield you your Original Files as imported to Aperture.
Regards
TD -
How to burn photos to DVD from Aperture
How to burn CD from Aperture to DVD
Found this on the Aperture plugin page: http://www.blueroomsoftware.com/BurnToDisc/ApertureBurnToDisc.html
-
Problem Using iTunes To Sync Photos To iPhone4 From Aperture Library
hello, i have 1400 pics in my aperture library and when i sync it to my iphone4 it's only show me 114 photos.. i don't know why?
may u help me?Do matters improve if you update to iPhoto 9.4.1?
iPhoto 9.4.1
From the release notes for the new version:
What's New in Version 9.4.1
Improves the reliability of syncing to iOS devices via iTunes
Fixes an issue that could cause iPhoto to quit unexpectedly when using the Export command
Addresses an issue that could cause iPhoto to quit unexpectedly when upgrading multiple books, cards, and calendars
Resolves an issue with downloading and viewing photos synced from Facebook albums -
Bulk photo export problems from iPad
I have 5000+ RAW files on my iPad (50gb or thereabouts) uploaded using the camera connector kit during a holiday. I've tried iPhoto, Lightroom, Image capture. Everything freezes up or crashes, whether I try to export them all at once or ten at a time. Help!
You can try Photo Transfer App; try and do it in a few installments.
Please read application features before you purchase. -
How to modify photos being streamed from Aperture
I set up photo streaming from the Aperture library to Apple TV2 awhile ago. I am not sure how to modify the album/photos accessible from Apple TV2?
If you want to remove all photos and not have them sync back to the iPad, with your iPad connected to your computer, while iTunes is running and with the iPad selected under the Devices icon at the top of the iTunes window, click on the Photos Tab and then uncheck the box next to Sync Photos From and click on Apply in the lower right corner of the iTunes window.
-
Photo Transfer Problem From Minox Dcc M3 to Ipod via Camera Connector
Hi,
I have a minox Dcc M3 digital camera,and i recently purchased a 5th generation ipod with the intention of downloading images from my minox camera direct to the ipod, so that i could delete the images from my camera and carry on taking more pictures without having to carry my laptop around with me, The camera only has a 32mb built in flash memory and will not download direct to the ipod via an ipod camera connector,I have tried other cameras that only have built in flash memory and none of them will download direct to the ipod, Has anyone out there come across this problem before,according to apple the ipod supports the following image transfer protocols:- PTP
Type 4 (or Normal)and Mass Storage.Could anyone tell me if there is any firmware update for the ipod or camera that would make the ipod compatible with the cameras flash memory and allow me to download my images to my ipod.I don`t think there is an option to turn on or off any transfer protocols,on connecting the camera to windows xp it connects staight away and viewing/downloading photos is no problem,it works the same as my other camera no problem.I have followed apples procedure of connecting (ie:-turn on ipod/connect camera connector/turn on camera and connect usb cable) the camera then shuts off immediately,i can turn it on again but all i get from the ipod is the message "ready to connect".It seems to me that the ipod does not even know the camera is connected?,looks like maybe this camera is not compatible with ipod,but i cannot help but think that other camera makes with built in memory would suffer from the problem.
-
Since the recent upgrade i have lost my Aperture libaray and cannot open the old one message reads you cannot use this version of the application Aperture original with this version of OS X you have Aperture original 3.2.4.
How do i get my photos back please.Aperture 3.2.4 will not work on Mavericks.
You can do as I did, either do a web search for Aperture updates to your current version of Aperture to update to Aperture 3.4.5 OR just simply upgrade to latest version of Aperure 3.5 ( from the Mac App Store) that is fully 64 bit compliant for OS X Mavericks. As long as you have registered your previous version of Aperture, the new 64 bit version will be a free upgrade.
Be advised that if you just upgrade to the latest version of Aperture, it will update your Photos Library, as well.
When this happens, your old version of Aperture on older versions of OS X will no longer work with the new, updated Photos Library.
If you still want to be able to access your Photos Library with an older version of Aperture and older OS X version, you need to make a copy of your current Photos library.
Make a copy of your current Photos Library and put it into a folder called something like old Photos Library so you still have an older version you can still access if you need to. -
I deleted all my photos in my ipad (manualy). But in the settings and when i pull it up on itunes, it still says i have 3.65gb of photos when i dont. Does anyone know why or know a solution of how i could get that extra space back.
Try deleting the photo cache...
iTunes: Understanding the iPod Photo Cache folder -
Color changes in photos after exporting from aperture and viewed on another computer
Help! I import raw images, I'm Proofing with sRGB IEC61966-2.1 and my colorsync profile in my export settings are also set with sRGB IEC61966-2.1. When i export to my computer the pictures look exactly as they should be, but when i email them and see them on other computers the colors are not at all what i be;ieved to have been exported! Im a newbie to the digital world...
What is your Mac's display color setting?
Maybe you are looking for
-
Adobe Acrobat 6.0 CE Standard edited forms do not display fields
I have a user who has Adobe Acrobat 6.0 CE Standard, she uses it to fill out an editable form created with Adobe and send it to clients. When this form is saved and attached to an e-mail, anyone who recieves it and opens it in Reader 9.0 the fields t
-
Develop a report to migrate territories and its attributes
Hi All, My requirement -> create territories, assign BP and attributes to it through a custom report. Using BAPI BAPI_TERRITORY_CREATE I manage to create territories but assign BP and Attributes i did not find any FM and BAPI. kindly guide me how i c
-
Just started using my Mac Mail program instead of web mail. When I went to attach two pdf files, one attached as a file, the other inserted all the text into the body of the email message. How do I get it to attach both pdf's as files?
-
i want to store the word document into the data base. how can it be done by converting the word document to bytes and then store the same in the data base.
-
BAPI_PO_CHANGE error number 351
Hi, I am facing a problem while trying to update a Partner in the Purchase order header. I am doing it through the BAPI "BAPI_PO_CHANGE" and getting error number 351 "Please enter a valid partner role". Please let me know how to remove this error. Th