Aperture 2.1.4 thumbnails problem

aperture 2.1.4 does not halt thumbnails--cannot export nor see images on 970! How to stop? as I maylose 100's of hours...

I did go to: "RE: Trouble with muy Thumbnails since 2.1.4 update" and had noticed Apple Tech had suggested similar. I did go to and found I;'d used wrong key i.e.control not Apple/option. This wurked me to start 'library' and after an hour saw that thumbnails had changedto previews. ALL is well.Enough of shoulder operation after 11 months healing needing 12 mos. R Ski

Similar Messages

Aperture 2.1.3 Export Problems with Cropped Photos

I ran into an odd problem after updating to 2.1.3. I was trying to upload to a Picasa album via "aperture-picasa-plugin", which I had used before without problems. The resulting export had problems with two photos I had cropped from landscape to portrait size. The resulting exports had the entire uncropped/original content "squeezed" into a photo matching the cropped size, so the exported pics were squished making everything look tall and skinny. (I found it especially odd that stuff I had cropped out was back in, but the size was cropped.)
I assumed it was a problem with the plugin, so I exported to a file straight from Aperture and had the same problem. I had other crops that worked OK, but they appear to all be landscape to landscape with no change in aspect ratio.
Is anyone else having this problem?

YES!
I have seen this show up as well. I'm also using Aperture 2.1.3. I too thought it was the fault of the picasa plugin... but when I, like you, started doing my exports directly to files I noticed that they still had the same problem.
The horizontal 16x9 seems to be particularly vulnerable... And, yes, it almost looks as if the (pre-crop) master has been "squished" into the aspect ratio of the (post-crop) version. It is very strange, very annoying, and very intermittent. Although, I found that if I quit aperture, restart then re-export... I have better luck.
Boy, am I relieved to find somebody else who is having this problem. For a while there I thought I was going nuts.
-C.

Aperture 3.2.1 Import problems.

Aperture 3.2.1 Import problems. I can not import. Complete system hang when I try. Have to force reboot. I made a new user and everything seems to work fine under that user. I must have something conflicting in my admin user but I have had no luck finding it. I have tried rebuilding the library (all three options) but to no avail. Aperture will run fine as long as I do not try to import. This is very frustrating, any help would be greatly appreciated.
27" imac 3.06 intel core 2 duo 12 GB Ram

Hello Tim,
If a problem only occurs when working from one account, then very often faulty user preferences or presets are the cause. Try to remove your user preference file, and if that should not suffice, move your presets to the desktop, as described in the Aperture 3: Trouble Shooting Basics:
(Caution: I see, you are running Lion: Because of Lion's non-preemptive Process Management you can never be sure if an application really has quit, even if it looks in the Dock as if the Application has finished. So it is very important to log off, before you launch Aperture again, after you changed something in the libraries like described below.)
Delete the user preferences
You can resolve many issues by restoring Aperture back to its original settings. This will not impact your image files or your library. To reset your Aperture user preference settings to their original state, do the following:
Quit Aperture.
In the Finder choose Go to folder from the Go menu.
Type~/Library/Preferences in the "Go to the folder" field. Press the Go button.
Remove the "com.apple.Aperture.plist" file from the Preferences folder. (and log off and log in again!)
Move the user created presets, keyword lists, and so on...
Quit Aperture.
In the Finder choose Go to folder from the Go menu.
Type~/Library/Application Support/Aperture in the "Go to the folder" field. Press the Go button.
Move the contents of this folder to your Desktop (and log off and log in again!)
Start Aperture and see if the issue is resolved. Note: Permanently removing these files will delete presets, metadata sets, keyword sets, and so on. If moving these files to the Desktop does not resolve the issue, move them back to their original location to restore the presets, adjustment chain presets, and metadata sets. In no case will removing these files affect metadata, keywords, or adjustments already applied to images.
If none of this should help, try to boot into safe mode (hold down shift after the start up chime), to see if you have conflicting plugins or video drivers etc. installed in your admin library.
HTH
Léonie

Has the duplicate erroneous thumbnail problem been resolve in the current Elements software?

I have used both Elements and Lightroom in the past, but have dropped both because of the redundant thumbnails of the same photo when they are moved from one folder to another. Since the complete file only resides on one place other thumbnails are present but only serve to complicate finding the actual file.
I purchased a new Lightroom, but the problem still exists with the current software.
My questions regard the handling of files within Elements. I have 50,000 photos in my inventory and with a work flow that requires moving existing photos from one folder to another, I can not afford to generate erroneous thumbnails with each subsequent move.
Has Adobe addressed the duplicate and erroneous thumbnail problem in the current Elements software? Does the use of Bridge avoid this problem? Is Bridge available within Elements? Is Camera Raw available within Elements? What is the annual cost of Elements if procured thru Creative Cloud without access to the full Photoshop program?
Jerry

Gray Drake wrote:
I have used both Elements and Lightroom in the past, but have dropped both because of the redundant thumbnails of the same photo when they are moved from one folder to another. Since the complete file only resides on one place other thumbnails are present but only serve to complicate finding the actual file.
I purchased a new Lightroom, but the problem still exists with the current software.
My questions regard the handling of files within Elements. I have 50,000 photos in my inventory and with a work flow that requires moving existing photos from one folder to another, I can not afford to generate erroneous thumbnails with each subsequent move.
Has Adobe addressed the duplicate and erroneous thumbnail problem in the current Elements software? Does the use of Bridge avoid this problem? Is Bridge available within Elements? Is Camera Raw available within Elements? What is the annual cost of Elements if procured thru Creative Cloud without access to the full Photoshop program?
Jerry
Jerry,
I don't understand your problem. Moving files from within either Elements or Lightroom doesn't create redundant thumbnails.
There has been problems in older versions of Elements where the 'Folders' view was corrupted and did not show the real content of the folders.
http://www.johnrellis.com/psedbtool/photoshop-elements-faq.htm#_Folder_Location_view
If that's what you have experienced, the problem is solved since PSE11.
Without knowing exactly your workflow, it's difficult to understand your problem. Moving files from folder to folder require taking into account the possibility of files with the same name already existing in the destination folder. Do you get files renamed with a suffix in the destination folder ?
- Bridge is not available with Elements
- The camera raw version in Elements is limited to the 'basic' and 'detail' panels
- Elements is not available in the Cloud subscriptions.

Does upgrading from Premiere Elements 12 to 13 solve the Organizer thumbnail problem?

Thumbnails do not show up after importing clips into Premiere Elements 12 Organizer. I've tried right clicking on a clip and telling it to recreate the thumbnail but it doesn't work. I've tried refreshing and repairing the catalog. I've even started a new catalog and reimported the files. The system says it's creating thumbnails but they still do not show up. Does upgrading from Premiere Elements 12 to 13 solve the Organizer thumbnail problem?

listiak
That is one of those questions best answered by evaluating Elements Organizer13 with your specific files in your specific computer environment.
Each of the Elements Organizer versions often appears to carry along its own baggage.
One of the things that came up about Elements Organizer 13 thumbnails recently was a problem with files with MPEG2
video compression. The Adobe word on this was that this is only an Elements Organizer 13 tryout issue...supposed not to exist
in the purchased version.
ATR

Aperture 2 not loading thumbnails...

...and moving very slow.
Recently I was using Aperture 2 (haven't upgraded since I just bought A2 in January) on my Macbook (3 year-old black one running Leopard) and Aperture was running fine, albeit slow since I was trying to edit around 400+ shots from a recent trip. Because of speed and memory issues, I decided it was time for an upgrade.
I purchased a new iMac with a 3.06 GHz processor and 4GB of RAM hoping that it would speed up the process.
All of my photos were stored on an external hard drive.
I've been trying to import the photos from the hard drive, but when I do I get no thumbnails and when clicked on, most of the photos are showing up blank. There's meta data on the photos, just no picture.
I tried importing the photos directly from my camera, but I'm having the same issue.
I removed and reinstalled A2 and am having the same problem.
Apparently A2 functions better on my MacBook!
Someone help...
Thanks.

Reposting...hoping someone can help out or send me in the right direction.

Aperture and iPhoto 08 integration problems

Hi.
I just bought Leopard and iLife 08. I read in an article (see link below) a great way to integrate pictures from your Aperture library into the iPhoto library:
- Setup Aperture to share previews with iLife
- Setup iPhoto to not copy items into the iPhoto library
- Import photos from Aperture into iPhoto by using the 'Show Aperture library' feature
Photos from Aperture (actually the previews from Aperture) are now in your iPhoto library. The great thing about this is that the Aperture previews are referenced so when you make changes to the photos in Aperture the changes become visible in iPhoto.
However, I have discovered two problems until now with this integration:
1. When I make a change to a photo in Aperture the change is not visible in the iPhoto preview (or what it is). But when I double-click on the preview in iPhoto the full image has the change I made in Aperture.
2. Keywords from Aperture also gets imported into iPhoto. However, some of my photos have more than one keyword in Aperture and when imported into iPhoto some of the photos have all keywords and some only have one of the keywords they have in Aperture.
Is there anybody out there having the same problems and even better a solution?
Thanks!
Link to article:
http://www.oreillynet.com/digitalmedia/blog/2007/08/referencedaperture_previewsi.html

TBDK
Welcome to the Apple Discussions.
The great thing about this is that the Aperture previews are referenced so when you make changes to the photos in Aperture the changes become visible in iPhoto.
Well as you can see, that's not actually true. If you change the pics via Aperture there is no way for iPhoto to know about this change, and therefore no way that it will then update your thumbnail in iPhoto. I guess this integration is intended for after you've finished processing your pics.
Regards
TD

BIG Thumbnail problem

The last few weeks Aperture started driving me insane. After massive permission issues and ending up rebuilding my library - at least now I can access it again.
HOWEVER - I still have issues with the thumbnails - they keep rebuilding every time I open Aperture. Some of them load successfully then disappear again, others don't load at all.
Also selecting all images in a project and selecting "generate thumbnails" doesn't solve the issues.
Any ideas appreciated!!! Thanks!

in my case it's managed, and the import is via the import dialog that opens when the memory card is inserted into the card reader. I've never had this problem before with any previous imports of lumix LX3 photos, nor 40D photos. Don't know what changed. I tried repairing permissions too. Will try a few more things.

Aperture constantly rebuilds same thumbnails and preview images.

What is behind Aperture 2's pathological obsession with constantly rebuilding the same thumbnails and preview images, and is there any way to stop it? I can't link this performance killing problem to any specific action on my part; I see it in many different circumstances. For example:
(1) Putting the system to sleep while Aperture is open then resuming later
(2) Hiding the Aperture app, working on other memory consuming apps for a while (e.g. Photoshop), then returning to Aperture
(3) Switching from one project to another via the "Projects" tab.
(4) Quitting Aperture then restarting it.
I can say with 100% certainty that this is not the result of some previous thumbnailing/preview generation operation that was interrupted. The # of images in the project doesn't seem to have a bearing. Nor does the type of camera or image type I've imported from the camera.
I can be happily working in Aperture, working with a project created months ago, when all of a sudden the "generating thumbnails" message and the dreaded Wait Cursor appear and my speedy, well-apportioned iMac grinds to a total halt while Aperture does the same ** thing it's already completed before.
The only hit I get when searching Apple's support site mentions a known bug for those who upgraded from Aperture 1 to version 2 but definitely does not apply to me here.

Thank you for the reply Tony. I've followed your suggestion but Aperture continues to (apparently) randomly decide to regenerate thumbnails and previews.
The problem has become bad enough that I've had to stop using Aperture completely.
Doesn't anybody from Apple read these forums? I can't possibly be the only Aperture user in the world to experience this problem...

2 OSX logins, 1 shared aperture lib, some missing thumbnails

hey all.
i've googled and searched to no avail.
I have two OSX users/admins that i use on my computer but want to manage my photo's with one Aperture account/libary.
Aperture library file is in "shared->pictures"
permissions for it are both my users "read & write"
many thumbnails don't appear for images, despite trying the right-click and generate-previews option.
any thoughts? Any way to ensure the entire package-contents is R&W for both users?
thx.

I ended up having to export out each album as masters and reimport them. Not sure what went wrong but oh well.
only hitch i ran into was that i didn't realize exporting masters didn't export out any of the ColorCorrects i'd done and also didn't export any images in stacks that i'd collapsed.
hoping now that i've remedied it i dont run into this problem again
thanks for the links you'd sent along.

Aperture 2 install - serial number problem

Disclaimer: I'm pretty good on a pc. Absolutely terrible on Mac, never had so many problems with tech :/
So...I have my serial number from the back of the Aperture 2 "Installing your software" booklet. Checked that I'm entering "I's" not "1's." Got dashed between the sequences. Capslock on etc. Searched forum, quite a few posts on serial number problems. None matched.
Enter serial number. Second window pops up stating I've entered an upgrade serial number (I only have the expired trial version of Aperture installed), and requesting my "serial number."
I'm lost now. Checked my original docs, there's nothing on Aperture trial version. Fired up the trial and I see what looks like a license key (to Apple, not me) on the launch screen. That's not accepted by Aperture 2.
Any thoughts on this appreciated.

M_Austin wrote:
Thanks, think you solved this Wish the label said something like that, the box only says Aperture 2, not upgrade license. So I'm guessing I have to pay $199, and keep this $99 package to upgrade it? I hope not. I'll ask at the store.
There is a tiny label on the bottom edge of the box. Mine says "Aperture 2.0 Retail". The tiny label on my box for Final Cut Express 4 says "Final Cut Express 4.0 UPG". Does yours not say "UPG" on that little label? If not, you should be able to return it for the full version (plus pay the difference, of course). If it does say "UPG" you might be out of luck as most open software can't be returned.

Aperture Dual Monitor Color Profile Problem

I have 'discovered' an interesting problem when using my MBP with a Cintq tablet as a secondary monitor. The displayed colors agree very well in Aperture until I go to full screen and then the laptop monitor develops a greenish tint. I have tried all the different secondary display options, and in all cases where an image is displayed on both monitors the tint develops. It goes away as soon as full screen is exited. The Thunderbolt port is being used to feed the display to the Cintq (with a thunderbolt to DVI (?) adapter. I would guess that the laptop must grap the cintiq profile as soon as it goes to full screen.
In perusing the discussion group I see similar problems were reported in the past. It persists with the latewt MBP and thunderbolt, and latest build of Aperture.

I have no real answer except to say that on an older setup pre-Aperture I never did get the Cintiq 15 color well managed. I used the Cintiq mostly for palettes in Photoshop.
-Allen

Aperture Script - Can't replicate problem

I wrote this script to rename and File Aperture projects by date : http://www.johneday.com/9/rename-and-file-aperture-projects-by-date .
A Mountain Lion user has given me this feedback:
OK, so I get the error that the EXIF tag does not have capture year. I'm on Mountain Lion, and recall that it worked on one project the very first time I ran the script after downloading and installing it... it's almost as if some flag gets set to true or false and it needs to be reset.
Can anyone running Mountain Lion replicate this problem for me? Any insights about what is going wrong for him would be appreciated.
set yourFolder to "Imported by Date" -- Name your folder here
set appendParent to false -- If true, the selected parent's name will be appended to the new project name
set makeSubfolders to false -- If true, new projects will be created in year/month/ folders.
property delimiter : "-"
try
    tell application "Aperture"
        activate
        -- Wait until Aperture is finished processing other tasks
        repeat
            set taskCount to count of tasks
            if taskCount is 1 then
                display alert "Aperture is processing another task" message "Please wait for the task to complete and try again" buttons {"Try again", "Cancel"} default button {"Try again"} cancel button {"Cancel"}
            else if taskCount > 1 then
                display alert "Aperture is processing " & taskCount & " tasks" message "Please wait for the tasks to complete and try again" buttons {"Try again", "Cancel"} default button {"Try again"} cancel button {"Cancel"}
            else
                exit repeat
            end if
        end repeat
        -- Verify that at least one item is selected
        if selection is {} then display alert "The selection {} is empty" message "Please select ONE Project, Folder or Album from the Library tab in the sidebar and try again." buttons {"OK"} cancel button {"OK"}
        -- Get the selected Parent ID
        tell item 1 of (selection as list) to set theParent to parent
        set {parentClass, parentName} to {class, name} of theParent
        if parentClass is album then display dialog "Albums may contain images from multiple projects. Are you sure you want to move these images from their projects?"
        -- Get date of every image in the selected Parent
        tell theParent to set dateList to every image version's (value of EXIF tag "ImageDate")
        tell library 1
            -- Create your folder if it does not exist
            if not (exists folder yourFolder) then make new folder with properties {name:yourFolder}
            -- Assign name of every project in your folder to a list for the Create project command below
            -- (exists project isoImageDate) command is too slow to be included in the loop
            if not makeSubfolders then tell folder yourFolder to set parentList to name of every project
            set dateTest to {}
            repeat with aDate in my dateList
                -- Test each date to avoid processing duplicates
                set shortDate to short date string of aDate
                if dateTest does not contain shortDate then
                    set end of dateTest to shortDate
                    -- Convert the image date to YYYY-MM-DD format
                    set projectYear to year of aDate as string
                    set projectMonth to (month of aDate as integer) as string
                    if length of projectMonth is 1 then set projectMonth to "0" & projectMonth
                    set projectDay to (day of aDate as integer) as string
                    if length of projectDay is 1 then set projectDay to "0" & projectDay
                    set isoImageDate to projectYear & delimiter & projectMonth & delimiter & projectDay as string
                    if appendParent then set isoImageDate to isoImageDate & space & parentName
                    tell folder yourFolder
                        if makeSubfolders then
                            --Create year and month folders if year folder does not exist
                            if not (exists folder projectYear) then make new folder with properties {name:projectYear}
                            tell folder projectYear
                                if not (exists folder projectMonth) then make new folder with properties {name:projectMonth}
                            end tell
                            --Create project if it does not exist
                            if ((name of every project of folder projectMonth of folder projectYear) does not contain isoImageDate) then tell folder projectMonth of folder projectYear to make new project with properties {name:isoImageDate}
                            -- Move the images into the project
                            move (every image version of theParent whose value of EXIF tag "CaptureYear" is year of aDate and value of EXIF tag "CaptureMonthOfYear" is month of aDate as integer and value of EXIF tag "CaptureDayOfMonth" is day of aDate) to project isoImageDate of folder projectMonth of folder projectYear
                        else -- If not makeSubfolders
                            --Create project if it does not exist
                            if parentList does not contain isoImageDate then make new project with properties {name:isoImageDate}
                            -- Move the images into the project
                            move (every image version of theParent whose value of EXIF tag "CaptureYear" is year of aDate and value of EXIF tag "CaptureMonthOfYear" is month of aDate as integer and value of EXIF tag "CaptureDayOfMonth" is day of aDate) to project isoImageDate
                        end if
                    end tell
                end if
            end repeat
            -- Move the initial container to the Trash if no images remain or if it is an album
            if parentClass is album then
                delete theParent
            else if (count of image versions of theParent) is 0 then
                delete theParent
            end if
            beep
        end tell
    end tell
on error errMsg number errNum
    tell me
        activate
        display alert errMsg & return & return & "Error number" & errNum buttons "Cancel"
    end tell
end try
EXIF Tag Name Mapping
The following table provides a mapping between EXIF tag names found in the Aperture 3 interface and EXIF tag names that appear in AppleScript.

Well, the obvious answer to your question is that Aperture in not seeing a 'CaptureYear' EXIF tag on an image. The way you have your try block set up, that amounts to a fatal error in your script. why it's not seeing a capture year is a different question. you might try asking the user with the problem to log the EXIF names for the images s/he's working on:
get name of every EXIF tag of image versions of theParent
you might also try breaking the complex command down into two simpler commands, in case ML has introduced a race condition:
set movables to get (image versions of theParent whose (value of EXIF tag "CaptureYear" is year of aDate) and (value of EXIF tag "CaptureMonthOfYear" is (month of aDate as integer)) and (value of EXIF tag "CaptureDayOfMonth" is day of aDate))
move movables to project isoImageDate of folder projectMonth of folder projectYear
Of course, it could just be goofy user error as well - trying to run the script on an empty album or somesuch.
Sorry I can't test this myself; my copy of aperture is an expired demo I keep around so I have access to the scripting dictionary (aperture questions are common enough to make that worthwhile), so I can't actually use it for anything.

Thumbnail problem

since my last update, I see on my thumbnails several times the same old picture.
When I click on it, the old picture dissapears andI can see the original ones. When I open full screen view, the pictures do not show at all. Anyone experienced this? How can I revert it?
since my last update, I see on my thumbnails several times the same old picture.
-version of iPhoto : Iphoto'11 version 9.1.5
- What version of the Operating System. Mac OS X version 10.6.8
- Details. What were you doing when theproblem arose? Appeared after last software update
- Did it ever work properly? Yes
- Are there error messages? No
- What steps have you tried already tosolve the issue. If I drag en drop the picture to desktop and delete it from Iphoto and then re-enter it in Iphoto by dragging it from the desktop into Iphoto the problem is solved. But I am talking about thousends of photos, so almost impossible to repeat this action for all these pictures
In full screen view of the thumbnails, the old picture dissapears and a blanc picture is seen, as you can see on the screenshot
Thanks for your expert help
JC

I have tried what you said, backed up with time capsule and relaunched iPhoto.
It says after a while "rebuilding library; 20179 versions restored" but than stops, nothing happens.... (even after 7 hours!)
I have tried to find back all my pictures on the time capsule, and in library>pictures>iPhoto i cannot find them!!! I only see the icon of iPhoto and it calculates 49,3 GB on disk but how can i get them back in iPhoto....
please help....
thanks
JC

Aperture 3.0.2 Trash Problem

Have been using 3.0.2 since it was first released and it's been working correctly but all of a sudden now when I empty the Aperture trash it does NOT go to the finder trash, it just disappears. Anybody know what my problem might be?

According to everything I read, and the way it used to work, when you empty Aperture Trash it is supposed to then be available in the finder trash. I have used the reject option but prefer to use trash because less stored within aperture is better for performance. But I liked having the option of still seeing the deleted photos in finder trash as a backup in case of a mistaken delete.

Aperture 2.1.4 thumbnails problem

Similar Messages

Maybe you are looking for