Aperture 2.1 / Photshop bug?

This is a weird one. When I select a RAW image and a version is created, I make my adjustments and send it to be edited in Photoshop (in this case, Elements 4). I do my touch-ups and save the file. The new version appears in the Aperture stack for that photo, but the image is only showing one of the previous layers I created when in Photoshop and not the final flattened version. I flatten the image before I save it, so there is no more selection or any other layer but the background. If I tell Aperture to load the version into Photoshop, it looks fine. But in Aperture's browser and preview windows, it looks like a layer I created from a selection and everything else (that wasn't selected) is black.
Is this a bug or am I doing something wrong?
Matt

Matt-
PS Elements is at version 6 now. First thing is to upgrade. Also, I don't know about PSE but with PSCS3 and OS 10.5.2 Adobe has said that problems exist that would not be resolved until OS 10.5.3 at the earliest. 10.5.3 is out now and at least some issues are fixed.
I recommend that you update to PSE v6 and OS 10.5.3.
Good luck!
-Allen Wicks

Similar Messages

  • Aperture ... Bug .... timezones and smart albums

    Hello everyone,
    i've just jumped into the mac world a week ago, just bought my first macbook ! Yeah !
    I decided to give Aperture a try, and given i've played with it now for 2 days, if this bug I found is really there, NO WAY am I going to pay for such software !
    I've been using Picasa on PC for the past couple years now.
    Its handling my photo library extremely well: over 50gb of photos, 10 years worth of photos.
    So after looking at all the Aperture videos on the apple site, I decided to give it a try to replace my picasa, since there is no picasa for my new mac.
    The bug I found (and I'm a newbie !, 2 days of playing, struggling to import my pictures, and bam ... bug .... hummmm).
    I tried importing only 1 folder in my library.
    I'm french and this summer, went to USA for holiday. Western deserts and all.
    So, I took my folder:
    2008 08 09 - USA Grand West
    And tried importing it.
    It contains around 100 photos of the 1st 3 days of the trip.
    My camera was set to French time, so at import I appreciated the "Change time thingy" and set it to Los Angeles time.
    Did the import in a new project.
    Great.
    All pictures in the project. Exif Date updated to los angeles time. GREAT !
    Now.
    I want to have them show up on a day to day basis.
    So, I created smart albums giving the date I wanted.
    August 9 2008, August 10 2008 and August 11 2008.
    It DOES NOT WORK ! BUGGGGGGGG
    photos taken on the 3rd day, having correct EXIF date metadata, show 11/08/2008 for the date (correct), however they are not shown in the August 11 2008 album !
    They are shown in the August 12 2008 album !
    Reason !
    The smart album is using the wrond date. The French one.
    Since there is 11 hours difference.
    Some late August 11 (Los Angeles time) pictures are pushed to August 12 (early morning French time).
    Am I the only one with this bug ?
    The only fix I found for now that works, is adding 3 rules to the smart albums:
    - exif: day of the month = 11
    - exif: month of the yar = 08
    - exif: year = 2008
    That works.
    However there is NO WAY, i'm setting up 50gb worth of smart albums having to apply 3 specific rules to compensate for a bugged out calendar rule that does not work.
    Any ideas ? fixes ?
    Thanks
    Regards
    Tim

    Hum, i'm not sure I understand what is going on, or what you are describing.
    you say: "... Aperture is correct in it's assertion the image was taken on 12th"
    I dont understand.
    When i've done the import, and look at that pictures metadata, the date/time is corrected. It shows up as 15:42 20080811 (youre writting).
    So if the metadata is correct, I really dont understand how the computers time and timezone has any effect on the smart albums ... could you explain ?
    Unless what you are suggesting, is that the smart album date is applied to the computers time zone, and thus when searching for the files, it automatically does a conversion of the time of the picture to fit the computers timezone => thus my 15:42 20080811 set to Los Angeles time zone, is researched using a French timezone and thus found on 00:42 20080812 ?
    Wow, if so, this would be a stretch !
    And if this is the answer, I do not understand the "feature" to import using a different time zone, and not be able to search according to it ?
    There is effectively no point?
    In respect to the workaround you describe. Its effectively what I did, I sorted using 3 criterias: exif day of the month = 11, month of the year = 08, year = 2008. And for some reason that works !
    Would there be another workaround? Instead of using the TimeZone panel, import them untouched, and doing a batch Time change on the pictures once imported and leaving them at the same Paris timezone, but compensating for 9 hours, effectively, bringing them to 15:42 Paris time, instead of Los Angeles time ?
    If my memory is correct when having played with this, the batch time modification, did not compensate the days: Effectively, clicking 9 times on the down arrow when showing 00:42 12th did not change the 12th into an 11th ...

  • Aperture 2.1 crop bug? Feature?

    I'm going nuts with something that is either a bug or a really annoying feature.
    When trying to crop an image, I may select the 8 x 10 aspect ratio and draw a crop frame on the image. However, if I try to select of the corner anchors for the first time to resize it and move it at all, the aspect ratio of the crop immediately jumps to the image's current aspect ratio and the crop heads-up display now reads "Custom."
    Am I doing something wrong? Is this a bug or is this somehow supposed to be how it works? Can't find anything in the manual on it suggesting it is supposed to do this.
    Thanks.
    Matt

    Was doing a search for something else and stumbled across your Crop issue.
    I am having the same issue. Another issue I get quite often is a change in the Width and Height boxes. If I choose 3x4 and drag an anchor point, the size changes to 128x85 or some other random numbers, (not same aspect ratio and is this inches or pixels?). So I go and change it back. This happens with all sizes (2x3, 4x5, etc.).
    Anyway, sorry I can't help you, I just wanted to let you know that you are not the only one out there with this issue. I was hoping that there was an answer to this. Alas no, just a, "mine works fine", in your face answer.
    Also, my files are not on a network drive or firewire or USB. I back up to an external drive but I put my library on an internal drive. I have also reinstalled Aperture to see if this might fix things. Good Luck,
    Narvon

  • Aperture 2 - Possible UI bug?

    G'day all,
    I've been just being enjoying my first couple of days of Aperture 2. Fantastic, really enjoy using this version (keep it up Joe & team!)
    I think I may have stumbled into a UI bug though. When I cycle through the viewer mode until the filmstrip disapears and the selected image is displayed at it's largest, I can't use the cursor keys or the arrows under the view to move to the next image.
    Do you think it's a bug or is this intentional?
    Cheers,
    Dean
    p.s. I'm looking for the Aperture feedbank link to send as feedback.

    Is it a matter of what "window" has focus? (...which can be hard to tell) Try clicking the cursor once in the viewer then using the arrows? Does that work?
    One way you can get into what you are seeing: If you click in a field in the metadata tab, then try and use the arrow key, its the metadata tab that is getting the keystroke, not the viewer, so the image doesn't change. You can see how it can happen, if you click there, the switch with a click to the adjustments tab, then adjust, then use the arrow key, you get nothing. If this is what you are seeing, then no need to quit the app, just click the window first with the cursor.

  • More....! Aperture 3.0.2 bugs...??

    Hi...
    Since the Aperture 3.0.2.update I have experienced quite a few frustrating faults. Prior to this update... from what everyone else has experienced, I had no glitches at all.
    1. As I posted elsewhere here, I had the Teal Green effect.. where a number of photo's were.. er very green..!
    2. Then came the recent update, which gave me the HUD with no slider's...!!
    3. Now I have no version numbers next to each project indicating how many versions there are...! When I hover over the project the version numbers appear.
    You can look at these two screengrabs to see what I mean.... http://gallery.me.com/gm.g#100736
    My MBP does not have any of these issues. I have done the repair/re-build library and delete the aperture.plist, this worked fine, got rid of the teal green effect, and gave me some sliders to work with...
    Now I have this added plus of 'no numbers'... I can live without it... but hey it should be there..!!
    I will submit feedback to Apple, but has anyone seen this...??
    Thanks...
    Gerry.........

    Thanks Gerry for your help.
    I had already tried repairing my library, but did not remove the aperture.plist. Done now and will see what next.
    I have no problem with space on my HD. I have only my Aperture libraries on a Drobo with 4x1.5 GB. Plenty space free.
    For the import, I always used the Destination as one of my existing Album within one existing Project. It always worked well before, even with version 2.0 with all my photos in the project and in the album at the same time.
    Now, still my photos ONLY go in the project and I have to look for them and drag them in the selected album.
    Weird!
    Anyway, will see if Aperture does not crash again after some adjustments.
    Cheers
    Frederic

  • Mobile me gallery vs Aperture 3 -- incompatible?

    My Mobile Me gallery worked perfectly in Aperture 2. I upgraded to Aperture 3 and about 20% of my gallery images got deleted and the remaining ones appeared in a random order. I am rebuilding the galleries now, but the process is VERY annoying (not to mention the time and effort needed to select from ten thousand images). The order of the images keep changing; when I try to rearrange then, some stay in their desired positions while others jump around. Although my update preference is set to "manual", Aperture keeps updating every 30 seconds or so, slowing down work significantly. My final grudge is that some of the images that appear in the published gallery are not the same as the ones I chose to create the gallery. It appears that Aperture 3 is full of bugs ... Any advice?

    Aperture does not have bugs any more, at least that is what some folk would have you believe.
    If you have just installed Ap3. It needs quite a long time to do all that it has to, to finish fully, and depending mostly on the library size, it could take a couple of days to several to finish. It is best left to get on with it. If this is not the problem then i have no other ideas. Allan

  • How to preserver Face data in Aperture 3.5.1 export to new library ?

    In an Aperture 3.5.1 library I add some face names and export smart albums to a new Aperture 3.5.1 library. However, in the new library, when I create a smart album of Faces that include a name I had added in the old library, the album is empty. The face name is a valid name and photos with that name can be seen in the Faces view. How do I properly export albums to a new library so that the new library will allow me to create smart albums based on Face info?
    Is this an Aperture 3.5.1 bug ?
    Thanks

    In an Aperture 3.5.1 library I add some face names and export smart albums to a new Aperture 3.5.1 library.
    How did you export the albums to a new library? Like this?
    Select the album in Aperture and use the command "File > Export > Album as new library"
    Open the exported library in Aperture and all Faces were there with the correct name.
    However, in the new library, when I create a smart album of Faces that include a name I had added in the old library, the album is empty. The face name is a valid name and photos with that name can be seen in the Faces view.
    Same here. At first, the smart album was empty. I tried all variants of smart rules "Face is", Face includes" etc., and the smart album stayed empty.
    Then I simply edited the name label in the Faces stack and reentered the name, exactly as it has been. Also, I clicked the -button and edited the full name again, and that sufficed, for the smart album to populate again.
    It looks like Aperture would need to reindex the Faces names.
    This looks indeed like a bug.

  • Aperture will not import all CR2 (iPhoto is fine....)

    I'm currently attempting to move from a PC to a Mac. For the most part this has been a positive experience however Aperture is starting to bug me.
    My photo library has been copied across and some old NEF files converted to JPEG. The library is located in a folder in the Pictures directory. The entire library imports fine into iPhoto.
    When attempting to import into Aperture I get seemingly random rejection of CR2 files. Photos prior to the failure import fine. Photos after the failure import fine. Around 20% of images are rejected.
    When the failure occurs no error messages are sent to the console. Examination of photo metadata shows not significant differences between photos that work and photos that do not. Changing the file name to something shorter does not help.
    Restarting Aperture does not work. Restarting the OS does not help. Downgrading to RAW 2.1 does not help.
    The only similar report I have found was from people having issues with CF cards, and the solution was to copy the files locally and then import....
    I'm not going to convert my CR2 files to DNG or JPEG just because Aperture is buggy. Other than that any suggestions would be greatly appreciated (is there an Aperture log file somewhere ?)
    Camera: Canon EOS 30D
    Aperture 2.1.2
    OSX 10.5.6
    Raw Bundle 2.5
    iPhoto 09
    Thanks !

    I seem to be having the same problem. I was to shoot an entire stage production with a canon 50D and when I only had a 4gb card at my disposal, I wanted to take some more pics so I went with Raw2. apparently aperture doesnt like this. it imported the project but all it gives me are thumbnails and in the canvas it says "unsupported image format".
    what do they expect me to do...spin back time and reshoot the entire production? no i dont think so...apple needs to get on this (if they havent already) and make this work.

  • Aperture don't show type of lens

    Mac OS X 10.6.8
    Aperture 3.2.4
    Preview 5.0.3
    Mac OS X 10.8
    Preview in 10.8
    I have RAWs.
    Created with Canon EOS 5D Mark 3 and Zeiss Distagon T* 2.8 / 21 mm.
    In Aperture and in Preview there is no Info about type of lens.
    There is only info: Unknown (33) 21 mm, see screenhot from Aperture 3.2.4
    I have communicate with Zeiss and and Zeiss say that there is a code for Exif in the CPU of distagon that give info of type of lens.
    The creator of RAWs has no problem with type of lens.
    He use not a Mac and not Aperture.
    He use WIN and Lightroom ;-)
    My question.
    Why is it a problem for Apple to implement correct info about type of lenses ?
    Other RAWs with Canon lenses show the right type of lens in Aperture and Preview.
    Has someone heart about new Aperture 4 that this bug is solved ?
    Jochen

    Jochen,
    this problem occured on and off since the raw update in september last year. So I dare no prediction, if and when this will be fixed. My Canon EOS 5D Mark II shows the correct exif info.
    Have a look at this thread: Re: EXIF lens code cannot be recognized
    As a work-around, if the lens info is very important to you, you can try to fix it with exiftool, as described in the thread above - you may also have a look at my user tip here:
                     Modifying EXIF tags of Originals Using exiftool: camera, lens, gps
    Regards
    Léonie

  • ITunes, iPhoto & Aperture - odd sync issue

    Hi all,
    I am a user of both iPhoto & Aperture, with unified photo library, and occasionally sync one or more events to my iPhone (rather than syncing all photos automatically).
    I've noticed recently a rather odd issue, where iTunes does not seem to be "seeing" my iPhoto library. If I set Aperture to the source, then all my events/projects show up correctly. If I choose iPhoto as the source, 0 photos .
    Opening the library directly in either iPhoto or Aperture works just fine - all events and photos present and correct - so the issue appears to be around the link from iPhoto to iTunes - weirdly, given the unified library, Aperture to iTunes seems to be fine.
    Whilst I _could_ just sync to Aperture, a) the error bugs me , and I'd like to sort it out, and b) iPhoto is a better manager of events (chronological order etc) so I would prefer to use iPhoto to sync to iPhone, iPad etc.
    I'm running Mountain Lion and both Photo apps are up to date. Hopefully some kind soul can assist!?

    Hey Aljrob_UK
    Thanks for the question. It sounds like there may be a permissions issue with your iPhoto library, let's see if repairing this will help to resolve the issue. See the additional information section of the following article:
    Important: Please backup your library first (http://support.apple.com/kb/PH2504)
    iPhoto 6 and later: Rebuilding the iPhoto library
    http://support.apple.com/kb/HT2638
    Additional Information
    iPhoto 9.3 and later introduces a new Library First Aid dialog in place of the previous rebuild options.
    If Repair Permissions does not resolve your issue, attempt Repair Database and/after Rebuild Database. You can skip the Rebuild Thumbnails.
    Thanks,
    Matt M.

  • Processed Images Not Displaying Correctly

    I've searched the discussion pool and Internet, but I can't seem to find someone with my exact issue, so hoping someone out there has some ideas.
    I am using Aperture 3.0.2 on an iMac 24" 2.16Ghz Intel Core 2 Duo with 3GB RAM, Mac OS X 10.6.3.
    Recently, images that I have applied adjustments to have started appearing incorrectly. This does not appear to happen to images that I have not made any adjustments to after import. Here's an example:
    In this case, half of the image is blacked out, but other symptoms include pieces of other images interlaced with the image or random colored boxes and lines blocking out portions of the image.
    I have tried deleting previews, rebuilding them, removing adjustments, reapplying them, running Aperture in both 32 and 64 bit mode without success in fixing the problem.
    Thoughts?

    Yep, this is a problem of displaying the image in Aperture's preview window. I think it's primarily a video driver bug caused by a bad mix of Aperture 3.0.2, Mac OS X 10.6.3, and (at least) the Nvidia 7300 graphics card specifically on the 24" 2.16 GHz white iMac. This model seems to be the one most affected. If you look hard enough, there are actually a couple other threads on this forum and other forms regarding this and/or similar graphic problems. The commonalities are the three things I listed above.
    Workarounds (not really solutions): As someone else mentioned, restarting the program may temporarily "cure" it. Forcing the screen to redraw the image, either by zooming in/out or by resizing Aperture's window, also may temporarily fix it. The best thing is to simply downgrade to 10.6.2. I Simply installed Mac OS on one of my external HDs and applied the 10.6.2 Combo update. I then simply reboot when I start a Aperture session, and reboot back to 10.6.3 and the rest of my life when done. No, this is not convenient.
    Everyone should call Support, visit Apple Geniuses, and/or at least send in Aperture feedback regarding this bug. With such a narrow range of affected hardware and software, I don't think we'll be seeing a real solution anytime soon. Hopefully with the next scheduled Aperture or Mac OS update in a few weeks/months/seasons, but I'm not holding my breath.

  • Mobile Me Gallery Conflict

    My mom and my brother are both on PC's, she can't see any of the gallery (although this may be part user error on her part), my brother is pretty fluent with computers and he can see pictures, but can't get the movies to roll in any browser (IE7, FF or Safari). Suggestions?
    Thanks.

    Aperture does not have bugs any more, at least that is what some folk would have you believe.
    If you have just installed Ap3. It needs quite a long time to do all that it has to, to finish fully, and depending mostly on the library size, it could take a couple of days to several to finish. It is best left to get on with it. If this is not the problem then i have no other ideas. Allan

  • German translation with ß renders website unusable

    Hi,
    I just wanted to report an ugly problem with the German translation for the language strings in Aperture 3. When I recently exported my photographs to a website it produced links that were completely unusable.
    The problem: For detail view Aperture exports html pages that were in English named large-xxx.html. The German translation for "large" ist "groß" – but groß contains the letter ß. Thus all details pages produce 404 errors on a web server – a desaster!
    I found the solution on the web: You habe to open Aperture package and have to manually change the German language strings (to "gross" or something alike).
    But this is certainly not a solution which is feasible for everybody.
    So please: Could somebody make it happen to remove this stupid bug from the next release?
    Thanks for helping
    Reinhard

    What a nasty bug!
    So please: Could somebody make it happen to remove this stupid bug from the next release?
    Are you using the latest Aperture version 3.5.1, Reinhard?
    Then, if you have a Developer Account, use "Bug Reporter" to file a Bug Report.
    If you don't have access to Bug Reporter, fill out the Feedback form:
    Apple - Aperture - Feedback
    Describe the bug there, then the Developer Team will also see it.
    I'll try to reproduce the bug, and if I can, I'll also file a bug report.
    Léonie

  • Strange little thing when exporting a cropped sqare image

    I needed a exact square crop of an image from my Aperture library, so I cropped it using common sizes->square, and then exported creating a special export set, keeping within same size in pixels (300). What I got at the end was a 300x299 pix. image. Can someone please verify this before I push a bug report?
    macBook Pro 1.83GHz   Mac OS X (10.4.8)   1 gig ram, aperture 1.5.1

    This bug is been with us since v.1.0. If you do a web gallery/journal, all the images exported will have the exactly same size you chose. It might help until this is fixed.
    If you wanna report the bug, you can do it here:
    http://www.apple.com/feedback/aperture.html

  • How to import only RAW images from folder with RAW & JPEGs?

    My system is set up that I have both RAW & JPEGs in the same folder since I shoot JPEG+RAW. How can I import just the raw images without also sucking in the jpegs? There is no way to distinguish the difference in the Import box and also no way to easily separate the the two in the Import box. I've tried using the List View and separting them by File Size, but Aperture has a stupid bug here and it tells me that the JPEG file sizes are in the teens (like 17-18 megs) and they are still hard to separate from the RAW which are about the same size.
    Why can't Aperture do this basic thing?

    I'm not doing anything. What I wrote in my workflow example above is exactly what I'm doing. I've been trying some experiments to see if it was "A Better Finder Rename" that is causing the issue. So far, no go. I have taken just a couple of JPGs only and pointed Aperture's Import to the folder that contains them. Aperture is reading that there are only 2 jpegs (which is what there is) and their file size is right on the mark.
    Ok. I just narrowed it down to something. The flaw is showing up after the RAW files are converted to DNGs. The JPEGs do not show up in the Import box when there are camera raw files like NEFs or CR2s and the corresponding JPEGs. That is Aperture's normal behaviour. But, and this is a big BUT, when the raw files are converted to DNGs and they are in the same folder as the corresponding JPEGs, that's when Aperture pulls its shenanigans. It has something to do with the JPEGs and DNGs having the same name. Even though the files have different extensions, Aperture is doing something to the file size of the JPEGs that make them seem that they are much larger files than they actually are.
    I figured it out like this:
    I had 2 CR2 files and the corresponding JPEGs in a folder. Pointing Aperture's Import to that folder, Aperture did what it is supposed to do; it saw only 2 raw files (doesn't matter that the G9 CR2 files are not supported yet). So, I renamed all the files using A Better Finder Rename and Aperture still only saw 2 raw files.
    So far so good.
    Then, I converted just the 2 CR2 files to DNG and kept them in the same folder. Aperture saw 2 DNGs and 2 CR2 files. No jpegs were seen. Business as usual. Then I removed the CR2s and renamed the jpegs so they had the same names as the DNGs (except for of course different extensions) and that's when Aperture saw the jpegs as separate files and saw them with bogus file sizes.
    So I tested that by altering the jpeg names so that they were different from their corresponding DNGs and Aperture went back to seeing the jpegs with the correct file sizes.
    Therefore, Aperture is having some difficulty with two separate files, one JPEG and the other DNG, when they both have the same name (different extensions, of course).
    Try it if you have a moment. Take one raw file and convert it to DNG and place it in a folder with its corresponding jpeg. Rename both to the same name and different extensions (.dng + .jpg) and see what happens when you try to get Aperture to import. Chance are Aperture will show bogus file sizes for the jpeg.
    Let me know if that's clear.
    Antonio

Maybe you are looking for