Aperture Thumbnails

Hi All.
After upgrading to 2.0 I'm not seeing thumbnails in about 80% of my pictures. I just see an empty box with an outline of where the thumbnail should be. This occurs with both my Mac Pro and my MacBook Pro using an external hard drive as the Aperture library. If I double click on the missing thumbnail the full resolution photo appears. When I go back to the "thumbnail view" nothing is there again. I thought it might be taking a long time to generate the thumbnails but this does not seem to be the case. Thanks in advance for help with this problem. Regards, David

for what its worth, i still have seen no resolution, and i am now currently in a project that i imported then relocated masters to an external drive 2 months ago...i have worked in the project dozens of times, however right now over half of the images do not have thumbnails but rather outlined empty boxes in the thumbnail viewer. i have to rebuild all of the thumbnails in this project...again. (this is not the first time, more like the 20th.
i have reported this problem to via the aperture feedback option on 5 different occasions. i urge anyone experiencing similar problems to report them as well.
while i love the interface and the flexibility this program offers, apple gets a huge thumbs down from me for ignoring this issue. early adopter realities notwithstanding, bugs should be fixed when reported, or at least addressed.

Similar Messages

How do I stop Time Machine from backing up Aperture thumbnails?

Hi,
My 2TB backup drive recently became full, and I became curious as to what was filling it up. I wrote a perl script to analyze the Time Machine backups, and I noticed that over 50% of my backup was filled with AP.Thumbnails and AP.Minis from the Aperture project directory. In particular, the AP.Thumbnails files in the backup consumed 737 GB of disk space!
The problem with the thumbnails files is that they are a single file that contains all of the thumbnails for all of the 40,000 photos I have in Aperture and it is now 20gb in size. Every time I add a new file to Aperture, the thumbnail file changes, and I get a new 20gb of data added to my backup. I add photos often which means that most of my backups have 20gb of Aperture files (which are easy to rebuild and don't need to be backed up).
I decided to try and stop Time Machine from backing up these files, and there seems to be no way of doing so (without telling Time Machine to skip backing up my entire Aperture project which I don't want to do). In Finder, you can do a "show package contents", but the Time Machine GUI doesn't allow this.
I tried to tell Time Machine to exclude the files via the GUI, but Time Machine sees the Aperture Library as a single package and won't let me exclude individual files from within the package.
I googled around, and found the attribute that Time Machine puts on files to exclude them from the backup. I used xattr to set the attributes:
xattr -w com.apple.metadata:comapple_backupexcludeItem com.apple.backupd <filename>
I also used this command on the iPhoto thumbnail files.
I used spotlight to find all of the files with this attribute using this command:
sudo mdfind "comapple_backupexcludeItem = 'com.apple.backupd'"
This command returned the iPhoto files, but did not return the Aperture files.
However, if I run "xattr" on the Aperture files, the attribute does exist!
During my next time machine backup, the iPhoto files were skipped as I wanted them to be, but the Aperture thumbnails were backed up again
I thought that maybe time machine was looking at the aperture package as an atomic unit, but iPhoto is stored as a package as well, and the attributes worked there on files inside the package.
Does anyone have any idea why time machine is still backing up these files? Is there any way I can get around this?
It seems to me to be an incredible oversight on Apple's part since both tools are Apple. The thumbnails files are very expensive to backup, and they are not necessary for backup since the are easy to rebuild from the original photos which are also backed up.
Thanks,
Ron

Shadow99999 wrote:
Hi,
My 2TB backup drive recently became full, and I became curious as to what was filling it up. I wrote a perl script to analyze the Time Machine backups,
No need to write your own script for that. there are a couple of already made nice GUI tools for this - TimeTracker http://www.charlessoft.com/ and BackupLoupe http://soma-zone.com/BackupLoupe/
and I noticed that over 50% of my backup was filled with AP.Thumbnails and AP.Minis from the Aperture project directory. In particular, the AP.Thumbnails files in the backup consumed 737 GB of disk space!
The problem with the thumbnails files is that they are a single file that contains all of the thumbnails for all of the 40,000 photos I have in Aperture and it is now 20gb in size. Every time I add a new file to Aperture, the thumbnail file changes, and I get a new 20gb of data added to my backup. I add photos often which means that most of my backups have 20gb of Aperture files (which are easy to rebuild and don't need to be backed up).
I decided to try and stop Time Machine from backing up these files, and there seems to be no way of doing so (without telling Time Machine to skip backing up my entire Aperture project which I don't want to do). In Finder, you can do a "show package contents", but the Time Machine GUI doesn't allow this.
I tried to tell Time Machine to exclude the files via the GUI, but Time Machine sees the Aperture Library as a single package and won't let me exclude individual files from within the package.
I don't have aperture but I think most people exclude the whole thing from TM backups and back it up separately. but if you want to exclude a subfolder in a package that's easy too. just select the package in finder, control-click on it and select "show package contents". in the resulting finder window drill to the folder you want to exclude and drag it to the TM exclusion list in TM system preferences->options.
I googled around, and found the attribute that Time Machine puts on files to exclude them from the backup. I used xattr to set the attributes:
xattr -w com.apple.metadata:comapple_backupexcludeItem com.apple.backupd <filename>
I was not aware of this method for excluding stuff from TM backups. could you provide a link to where you found this?
I also used this command on the iPhoto thumbnail files.
I used spotlight to find all of the files with this attribute using this command:
sudo mdfind "comapple_backupexcludeItem = 'com.apple.backupd'"
This command returned the iPhoto files, but did not return the Aperture files.
that's because Spotlight never looks inside packages unless you start a search inside a package directly. iphoto seems to be the only exception. I don't know how it's done.

IMovie 11 - Image quality issues / aperture thumbnails

I'm importing images from my Aperture library into iMovie but for some reason the images are of a lesser quality than the original file.
I've tried importing it directly using the Aperture preview panel on the right side of the iMovie screen, I have also tried to drag it from Aperture but both methods produce really bad quality images once imported. I right clicked on the clip after importing so that it would show me the file in Finder and it seems that they are referencing Aperture thumbnails which explains the quality. Why is iMovie doing this? Its useless if its going to use my thumbnails, I want my full images in HD!
I did try to drag a drop from Finder to iMovie which seems to solve the problem although I still believe there is some quality loss its not as bad as it is using thumbnails. This is definitely not an easy process!!
Am I doing something wrong here? It just seems silly that iMovie can't import an image with the original quality if it then is going to make an HD video.

On Import you could try unchecking Optimize video and choose Full Size. Your disk space however will get eaten up incredibly quickly choosing these settings as each hour of video = 40GBytes of disk space. So be forewarned about how big those files will expand as they come off the MiniDV tapes.
Another thing you will immediately see a difference in is how you move files from iMovie to iDVD. Share to iDVD while named in an intuitive way, is NOT the best way to get good quality DVDs out of iMovie. Instead you want to Share to Media Browser. Choose the Large Size setting. Then quit iMovie. Open iDVD, click the Media button, the Movies button. Find your project listed under the iMovie star icon and drag it into the iDVD project. Burn the Disc and see if you get a higher quality disk by Sharing to Media Browser instead of Share to iDVD.
If you choose a Blu-Ray burner, also get a copy of Roxio Toast. The encoding to Blu-ray that Toast provides will be top notch and prevent you from making mistakes as the recordable Blu-ray disks are more expensive than DVDs. So every mistake will be expensive.

Aperture thumbnail generation forever

Hello
I like to have all my pictures in one place to share them with apple tv, so I decided to give aperture a try.
I imported all images (about 36000 from 12 years) into one aperture library.
Before importing I switched off face detection and preview generation.
After finishing I had a 236 GB library, but aperture starts to generate some thumbnails.
Problem is, it freezes on generating them.
I used the activity window to hunt down what is happeing and found out that it stops when it comes to a specific picture.
So I managed to
1) start aperture
2) open activity window
3) stop the thumbnail generation when it starts
4) delete the picture where the aperture have problems
This way I managed to get from about 5700 thumbanisl to do to a number of 3500 thumbnails to do, but aperture keeps freezing at a single pic (the bad one)
But now, aperture starts thumbnail generation so quickly that I cannot open activity window and stop the progress before it reaches the bad one.
@Apple: could we have an option like "safe start" that won't schedule any processes for thumbnails before the user wants it?
So, any ideas out there? I tried everything I found like repairing, rebuilding, no help.
Is there any kind of log to look into? I am a newbie in mac os and aperture.
Regards
Klaus

This "bad" one is a video, some of the former bad ones were videos too, so does aperture have a problem in general with video files? Maybe its a good idea to just import all pictures and do the videos in a separate step afterwrds? Otherwise with 36000 pics (and about 300 videos between them) this is tedious...
Klaus,
Aperture may have a problem with videos, if you have a problematic video codec installed, if the video is corrupted, or incompatible with Aperture. What kind of videos did you import?
If you can, delete the whole project, so that you do not need to select the video and reimport only the image files.
Check, if you have the 3ivxVideoCodec installed - if yes, remove it,
see: Aperture 3: May be unresponsive or have slower performance with third-party video codec
This codec could have been installed for example by FlipForMac.
If you do not want to delete all of your last import, you could try to delete the bad video directly from the Aperture library package:
Quit Aperture. Ctrl-click the Aperture library and select "Show Package Content" from the pop-up menu. Open the "masters" folder and navigate to the Year-Month-day of your last import. If you can find the video there, remove it, but don't change anything else. Afterwards the video should show as missing. Delete the version from the library. The dates in the Library package are based on "Import session", not capture dates.
Before manipulating the Library, make sure you have a current backup.
Regards
Léonie
A list of supported videos is here, but it is not exhaustive:
Aperture 3: About Video and Audio formats in Aperture

Aperture thumbnail craziness

Hi all,
I've been having problems with the thumbnails in Aperture. I've been cleaning up the library and moving a lot of files around. So I decided to get all left over thumbnails cleared and regenerate for the whole library. I deleted all AP.* files from the library, opened Aperture and told it to regenerate all thumbnails.
It seemed to have worked fine until I noticed some images with the wrong thumbnails. They had thumbnails from completed different images, some even from different projects. So i told Aperture to regenerate the thumbnails for the images. It did so and they were corrected.
But when I closed and re-opened Aperture the thumbnails had reverted to the original (wrong) images.
I've tried regenerating and reopening several times, I've wiped all thumbnails and regenerated again and it still keeps doing it. It's like Aperture is reading the wrong thumbnails file or something.
Any ideas?
ciao
Derek

Be careful, my aperture library went all wacky, and no matter how many times I did a consistency check or rebuilt the library/rebuilt the thumbnails, it still was messed up. Once I turned off time machine backups, it straightened itself out. Now I have to manually back it up...

Aperture Thumbnails Not Loading

Hi-
Have used Aperture for a long time. Today, when I was importing new photos via a card reader, the "preview" wheel just kept loading and now all the thumbnails for my entire Aperture library are "loading" and not appearing. I am unable to do anything in Aperture since the color wheel is spinning.
I was tempted to power off, since I cannot force quit, however, I am paranoid that my entire library is in jeopardy.
Thanks for any advice.. help!
Jane

Hi Jane,
A friend of mine has the same problem. We are trying to solve it.
In the meantime you can start Aperture and check the damage. If the new photos you want to adjust are grey when you want to work on them you have the same problem.
You can try to delete the corrupted project if thats the only one and than reimport the pics. Othorwise you have to restore your Aperture library from your timemachine or another backup.
Please let me know if it helps.
Regards,
Martin

Aperture Thumbnails on larger files

Hello,
I'm using Aperture 2.1.4 on a iMac 27" i7 w/ 12GB RAM (mid 2011).
Since I started to scan my medium format work at 3200dpi (mostly 6x7 - ca.8900x7100px, but also 6x6) Aperture drives me crazy. It never generates all the thumbnails when importing a scanned film of 10 to 12 frames (or more when I used 220 film). I have broken or black thumbnails, and the only way to repair this is to click on each photo individually and generate the thumbnail via the "Image" menu.
My question is: is this solved in aperture 3? I need to upgrade to AP3 anyway since I'd like to upgrade to Mountain Lion.
Kay

anyone?

Best method of formatting? - having trouble with iphoto/aperture thumbnails

I've recently installed SL on my wife's MB - all good except now her iphoto thumbnails won't show. I've tried rebuilding the iPhoto library (and all other options - but nothing). When i installed SL i did a full reformatting of the HD and I wonder if i perhaps didn't choose the best method - anyone got any ideas??
Message was edited by: Birmingham Mike (because he looked like a bad speller!)

This here might be what you need to do.http://www.justanswer.com/mac-computers/4ahty-rebuild-iphoto-caches.html

Aperture not building thumbnails

Having a problem right now with generating thumbnails in Aperture 3.5.1. Originally had another issue with iMovie seeing very few movies in my Aperture library. I was able to import all files from all cameras into iMovie, and can see them if I import a sampling of them into another library. Apple support suggested I rebuild my library, which revealed a few more, but still less than 5% of the total.
Apple then suggested I create a new library and import my existing library. I was watching the progress bar near the end when Aperture crashed at completion. I repaired the library and it began building thumbnails. The process has been slow, with Aperture running at 100% CPU (one core--single thread?) and very low I/O on the disk.
The status freezes on one image when Aperture processes roughly 1000 thumbnails. It says "Generating Thumbnails for [image]" "35,323 Remaining". At first I thought Aperture may still be processing in the background, seeing how Aperture's CPU utilization remained in the 100% range and disk usage continued. But when I quit Aperture and restart, it shows barely more progress than what was indicated in the status before quitting Aperture. The particular images listed are fine, and the thumbnails are generated when Aperture is launched.
At this point, Aperture will not quit cleanly, or with a Force Quit. Occasionally I've been able to use this suggestion:
https://discussions.apple.com/docs/DOC-3881
In other cases, Aperture seems to quit, but the entry remains in the Activity Monitor, with all accumulated stats, but 0% CPU. I'm unable to launch Aperture at this time and must restart. If I try to kill the process, the OS says it can't find it. Could this be a Mavericks eccentricity?
When restarting the OS and Aperture, thumbnail generation continues from where it left off, and processes another 1000 images or so. I did try repairing the database, and thumbnail generation continued, but eventually failed.
Occasionally, the com.apple.MediaLibraryService stops resonding in the Event Viewer. This had not always correlated with the frozen progress bar. In fact, thumbnails have continued to process when I've seen that hang in Event Viewer. But it always has meant I need to take Aperture down forcefully. Oddly, I do not have sharing previews enabled (set to never for now).
There are a few early articles, but they don't seem to offer any suggestions I have not tried, except to persist and restart Aperture each time this happens. Could take 2-3 weeks at this rate if I need to restart every time the progress bar stops. I have also tried clearing user and system cache a few times.
Apple second level support has been slow to respond, and I'm over 9 days into this process. Has anyone experienced anything similar, or can offer any suggestions?

Is it only your current Aperture library, that is causing this trouble?
Or do you see the same problem, when working with a new test library?
Although otherwise operationally sound, some video in my original library was not viewable in the Media Browser (including iMovie), even after a repair and rebuild.
I created a new, empty library and imported my original library. I described that process. Aside from the crash near the end, it appears to have all my assets. The project and image counts are the same.
The issues described about building thumbnails is in this new library. Upon importing my original library, the new library began generating all new thumbnails.
If the thumbnail generation is only hanging for your current Aperture library, you may have imported corrupted media - image files, videos that cannot be processed, sound files.
I know exactly what you're talking about, and this was my first assumption as well. As an Aperture 3 early adopter, I saw this issue countless times from failed imports. But I have examined over 8 files that it has apparently hung on. The thumbnails are fine! I look at the assets, directly, and they are in perfect condition. I expected to find corrupted TIFF files or bad thumbnails. Neither were true. If I request to generate it again, it works just fine.
Have you tried to remove the images from your Apeture library, that are shown in the message? Inspect them in the Finder and check the media type - jpeg, raw, video and check, if other Applications can open it.
Yes.
I do not have previews generated for nearly 2/3 of the images in my library, although I haven't seen reports about how this could be a problem.
UPDATE
Since my first post, I found a suggestion to regenerate all new thumbnails. Days of time lost, but I restarted. Still had a crash after about 1000 thumbnails. com.apple.qtserver or something was hung. Seemed only to launch occasionally after I restarted. Thought this might be responsible for generating thumbnails for video. So I did a search for all video files and let Aperture build these as I browsed through, page by page.
Since that time, Aperture has been building thumbnails for 10 hours, the longest run yet. Thumbnails are still generating VERY slowly, but I haven't seen a crash since.
Could it be the back and forth between images and video as it's generating thumbnails?

Does anyone have any experience of using an Aperture library on a Drobo or Promise Pegasus? If so any problems or tips?

My intention is to place my Aperture library a Thunderbolt Raid device and access via my Macbook Pro SSD Retina. The thinking is that I would have the capability of having a large library and wouldn't run out of space for some time - I understand that the library would also need to be backed up.
If anyone could share their experience positive or negative I'd be very grateful.

I have Aperture installed on a three month old Drobo 5D ( containing five WD 3 TB RED NAS hard drives) attached via Thunderbolt to my Macbook Pro with Retina Display, and Aperture is beautifully responsive with this setup. I do have a 60 GB mSATA card installed in the Drobo 5D, but I find it makes a real difference only when you are trying to acess a lot of small files, e.g. Aperture thumbnails. The Drobo 5D and Aperture make a good combination.
With a folder containning a mix of large and small size files, I find that it often looks like it is going to take a long time to copy the files with the Drobo 5D, and then after a short period of time the Drobo 5D really takes off and copies files at a very high rate of speed. In other words, don't form too hasty an opinion of how fast a group of files is going to be copied. Also, measured speeds with the Drobo 5D are not as impressive as you might expect, but the real-world performance is quite remarkable and fully in line with my expectations.
Tom

Why won't image change in aperture once I've export to edit in photoshop?

On going learning issue!
I finally managed to edit in photoshop via aperture. I have to change the photo from 16 bit to 8 bit so I can edit it. I like to take the photo into Photoshop (elements 4) to fix some spots and such.
It's supped to change in aperture when you are done editing in photoshop..right?
What I see is a new version of the photo, but the changes have not been made.
What am I doing wrong? I can see this becoming a problem when I try to export to print, burn a CD or even to web.
How I fix it?
Thanks!
IMAC G5 Mac OS X (10.4.6)

<...>
3) Execute a File > Save command in Elements. (NOT a
Save As...).
4) Close the file in Elements.
The edited version will show up in Aperture
automatically with all of your changes applied.
<...>
One note on that excellent summary - you do not have to close the file after saving, you can continue to work on the image and save multiple times. Each time you save Aperture will recognize the changes and update the Aperture thumbnail.
As to the original problem, it sounds like possibly you were saving the image somewhere else? Converting to 8-bit should be fine, as is resizing the image - Aperture should adjust for any changes made to the image.
Another possibility is that Elements does not have something called "compatibility mode" turned on for PSD saves - if you've turned that off to conserve space turn it on again, because that compatibility mode saves a flattened image which is what Aperture uses to recognize image changes.

Restoring Aperture Database from Vault a Nightmare

When my Aperture HD went south with the database of 90,000 images I imediately bought another 1.5 TB drive and started the restore from the Vault expecting to be able to use Aperture as before. It took 24 hours to restore the database. Now I can go back to work I thought. NO. Every Aperture thumbnail in every album has to rebuild when you want to use it. So the smooth experience of using my original database is now a nightmare of stop and go and wait for a rebuild. So the Vault is really is only a partial solution to an Aperture backup. This is totally not an acceptable solution for someone running a business.
Has anyone found any better solutions or has anyone experienced a rebuild of a large database?
Thanks,
Stan
G5 dual processor Mac OS X (10.4.6)

When my Aperture HD went south with the database of
90,000 images I imediately bought another 1.5 TB
drive and started the restore from the Vault
expecting to be able to use Aperture as before. It
took 24 hours to restore the database. Now I can go
back to work I thought. NO. Every Aperture thumbnail
in every album has to rebuild when you want to use
it. So the smooth experience of using my original
database is now a nightmare of stop and go and wait
for a rebuild.
One way to make that go smoother is to go in turn to each project in Aperture and click on it - that will force Aperture to try and see all files and in turn start rebuilding all of the thumbnails for that project. I think you just need to click, wait a second or two for Aperture to catch on, and then you can click on another project - then you can resume using images in albums after and it'll not be doing a thumbnail rebuild per image.
A few longer term solutions if you'd like never to have that problem again:
1) Mirrored drives. If you have mirrored drives and one drive dies, you still have one left. You'd still need to do vaults on yet another drive as mirroring is not really the same as a backup (it replicates mistakes as well as work), but it would make it much less likley you'd need to use the vault.
2) Backup library. If you really want to also backup the thumbnails then either manually backing up the whole library or just stuff within the library would work. If you export projects I believe it also strips the thumbnails but if you just go into the Aperture library and copy them out it keeps everything.

Corrupt Thumbnails

We have been using Aperture for a long time and had no problems. We used to have hard drives plugged into our computers directly and would import our images so they were within the library.
Now, we have set up a network so we have a computer with a firewire 400 drive coming off it, which we connect to over our network, to import our files, but instead of going within the library, the raw files now go in labeled folders outside of the library for ease of archiving. So the files within the library are reference files.
The import was working fine and going nice and quick, and then started noticing some of the files looked corrupt. However, when checking the raw file that had been imported it was absolutely fine. The image corruption would only be on Apertures thumbnail previews. You can actually see the raw file in finder is fine, and when going into the Aperture package contents, the thumbnails are corrupt. I have tried deleting the thumbnails and rebuilding the library but to no avail. It still creates a corrupt preview. Whats going on?!

OS of the computer running Aperture: 10.4.11
Aperture version is: 2.1.4
Camera: Canon 5D Mark II and Raw files are CR2
We have had no problems with the 5D on this computer before, its just decided to happen now that we are running it over the network. Do you think it is because the computer with the hard drive on is not compatible with these files? Even though it is just a storage device. Also, its only 1 in around 10 files that become corrupt?!

Exporting projects that reference images in other projects

Hello, all. I'm wondering if anyone out there has had luck exporting projects that reference images in another project. I've just given this a try, and I get empty images (dotted gray outlines that can't be multi-selected and can't be "managed" as referenced files, even though it knows where the original file should be).
Here's how I have things set up:
1. main project with referenced images
2. secondary project with an album that references images in the main project (secondary project shows 0 images, but album in secondary project shows N images)
I export the secondary project, and import it into another Aperture instance. All images show up as dotted outlines.
Furthermore, if I go into list view, the Activity Monitor does something bizarre. It shows the # thumbnails remaining as a moving target. See the video below for an example.
Any help would be greatly appreciated. Thank you!
Screen captures:
Missing images as dotted outlines:
http://echeng.com/temp/aperture-missing-images.png
Small video of thumbnail creating bug:
http://echeng.com/temp/aperture-thumbnail-bug.mov

I do this sort of thing constantly and things a whole lot more complicated. It works fine on all three of my laptops and my macpro. I actually just tried to simulate the exact conditions you describe and I will tell you what happened.
1)Create new empty project in library A called "export"
2)Create new empty album in that project.
3)Dragged multiple images from different projects (all referenced) into that new album.
4)Used file->export project with the consolidate images checked. Imported that project into a new/different library.
All of the images showed up and they all showed up as managed masters as expected. So I then relocated the masters from that project and did the same thing in reverse, back to the old library. I ended up with another project called "export (1)" with all of the images referenced and having nothing to do with the original project or the original referenced masters - as expected.
I did the testing not to figure it out but to validate that nothing had changed or broken since the last update.
You are either not doing what you think you are doing or your library/library is forked - you may want to try a rebuild or just create a brand new set of libraries and try to validate that it will work with a brand new set of libraries to try to isolate the issue to 1 - your existing libraries or 2 - your installation.
RB

Iphone low resolution

I am syncing photos from aperture 3 to my iphone, but many pictures are coming over to the iphone at horribly low resolution. I opened one such album and found of the 12 photos, only two looked good. The rest were a horrible example of compression artifacting, all the detail was lost and it was very muddy. The pictures looked out of focus. But the pictures looked fine in aperture, even when I had them being displayed at the same physical size on my mbp screen.
After doing some digging in the .applibrary I was able to find where the aperture thumbs and the synced photos were stored and discovered the pattern.
It appears that aperture thumbnails (for the bottom of split view, for example) are always created at 240x360. However, the pictures creates for itunes vary in size, and the size depends on the size of the original. One image original was 426x640 and its iphone image was 213x320 (14k) and looked ok on the iphone. Another however was a 200x300 original and aperture created a 240x360 thumb for itself (upscaled it a tad bit) but created a 100x150 (5k) (yes REALLY) for the iphone, which of course looked horrible. It would have been much better off just passing over the original to itunes instead of butchering it. Aperture has no business creating an image for the iphone that's LOWER than the resolution of the iphone screen. (and that's not even accounting for your ability to zoom what, about 2x, into a picture on the iphone?)
good looking:
First is 213 × 320 pixels (14k)
Second is 240 × 360 pixels (32k)
aperture claims the original is 426 × 640 (0.3 MP)
bad looking:
The first path picture is a WHOPPING 100 × 150 pixels (5k) and looks exactly like the crap on my iphone.
The second is 240 × 360 pixels, 33k.
Aperture claims the original is 200 × 300 (0.1 MP)
So.... what do I do about this? The only workaround I see at the moment is to go through all the pictures I want on my iphone and UPscale them and reload them into aperture, so it creates more sensible images for my iphone. (quite a hassle for something that claims "it just works") Now, is this a bug, or am I missing a setting somewhere?
I also was unable to figure out how to locate the originals inside my applibrary. Control click gives you that option in itunes for example. That would at least be helpful to know how to do if I am forced to upscale all these pictures by hand to work around the bug.

Are you using finder to look at your photos? Stay out of the finder! iPhoto organizes itself so that it can function. If you do anything to that structure, you risk losing your precious photos. The data folder has always been there.

Aperture Thumbnails

Similar Messages

Maybe you are looking for