Pentax K-x RAW color shift problem with Aperture 3

I have seen a few posts similar to what my problem is but not exactly.I have two Pentax K-200D's and a new Pentax K-x. I shoot RAW with all of them and the K-200D's work great. The RAW files however from the K-x are doing something strange. Sometimes (more and more though) the files are being imported into Aperture and there is a radical color shift after they finish loading. ALL of the preview thumbnails look fine in the camera and the Aperture import window. However, after importing them and processing is complete, some of the shots have a magenta color shift, but most that have this problem shift radically to a green tint. Everybody looks like they are in "The Matrix."
I do not have any brightness correction on the camera turned on as other posts imply might be the problem. I have also remove the Aperture RAW 3.2 and tried 3.0 and 3.1 with no solution. 3.0 doesn't recognize the files at all and 3.1 does the same thing as 3.2. Here are two examples of UNEDITED RAW files:
Frame that looks fine in RAW
http://gallery.me.com/mattcline#100470/IMGP5982&bgcolor=black
The next frame taken with the same settings on the camera:
http://gallery.me.com/mattcline#100470/IMGP5983&bgcolor=black
I do have one possible pattern. I had the camera set on rapid fire capture. It appears to me that the first frame I take when the shutter button is depressed looks and translates fine. All the subsequent frames take in rapid fire under the same shutter release have the green shift when taking shots in relative shade. Things taken in bright sunlight have the magenta shift.
Any ideas on what is going on or how to fix this?
Thanks.

kb8wfh wrote:
I just downloaded Apple's RAW 3.3 and it still made no difference.
Going back over the files, I found that going back and forth between the two, see no difference in the RAW processing headings. I did see however that in the meta data that the two pictures I have in the example of those listed above have one difference. There is a setting on the Exposure Bias for the one that was fine was -0.3 ev and the one that has the green contrast blast has an Exposure Bias of 0.3 ev. So the one that looks right is slightly negative. Doesn't seem like that should be a big difference, but apparently it is.
I did take some pictures with the RAW+JPG setting and I had the same problem with the RAW files. Some were ok, some were green, others were magenta shifted. However, all the JPG files looked just fine.
Switching from Aperture isn;t really an option for me. I have been using it for a long time and it generally works very well...perfectly with my K-200D's. It's just some bug with the RAW decoder for the K-x.
It's a known bug and I have been in touch with Apple staff over it, including engineers. It's not just the K-x. Other brands (Canon) and models suffer from the RAW processor gone wrong.
Right now there is no fix. At the pace Apple works at, there may not be one for quite some time. Use JPEG, use iPhoto, or move to Lightroom.
Another suggestion is to phone customer service and complain that their "Pro" program is not working as expected. I spent hours with an engineer going over the issue including a screen share session, only to be told to use JPEG.
This was 4 months ago.

Similar Messages

  • Solution to Gamma/Color Shift Problems with Apple Codecs - Adobe BUG

    Hi....
    In AfterEffects when choosing an output module and that module be ProRes or 10 Bit Uncompressed,
    when trying to color manage the file, there is a fine line called
    'This Codec Does Not Support Output Profile'
    You can find it int he Color Management Pane of the output module....
    Funny thing is - That Profile Embedding IS support by:#
    Apple's Compressor and THE CODEC 4444 AND UnCompressed
    Episodes Encoder
    See following Screen Shots:
    First one from Apple's Compressor...
    Look at that little beautiful Color Option... Adobe did you MISS that one, perhaps...
    You must have - because your APPS are NOT including that when encoding or should I say
    butchering movie files....
    Here adobes famous but wrong dialog!!!!
    And in this next screen shot you can easily see that adobe just strips the color profile out of the file...
    AND THAT IS WHY THERE IS A COLOR SHIFT...........
    left image = Apple's Compressor Encoding (Colors match of course) - Right Adobe's BRUTAL encoding (Colors WONT match...)
    Now, in after effects you wont notice the shift. But ALL mac and PC users using quicktime to watch YOUR movies
    are going to be looking at a movie with a different look than you thought it WOULD be... Courtesy of adobe ;-)
    Jokes aside, Adobe.... It seems as if this one is on you to fix... Apple's Compressor has NO problems. And other encoders are also preserving those values.
    Now... Let us assume that I encode in compressor... Looks are matching 100% that of the original source. All it takes to mess that up is ONE
    roundtrip to after effects, premiere pro or Media Encoder. That is if I wanna maintain my initial choice of transcodec - in my case 4444 or 10bit Uncomp.
    I could of course export to animation and then use compressor AGAIN to transcode to my format of choice... But in the long run I think that will become tedious.
    Perhaps you could assign a few engineers on this one and in the future spend MORE time on living up to the name PRO(The most misused word in the software business) instead of wasting time generating new Application icons for your apps....
    Thanks for reading and for a PROMPT and near-future BUG FIX

    Mylenium wrote:
    It's not really "embedding" anything, it merely sets the QT color space flags which have been there forever, but are mostly unused. Specific to ProRes it also toggles different internal optimizations in the encoding. That's also documented somewhere on the QT developer pages. I'm not sure I share your views otherwise. The point really is, that Apple developed ProRes just as much as a closed workflow within their products as Avid did with their CoDecs. Therefore the widespread use of the CoDecs is merely a byproduct of the use of the products, but not per se an intended workflow outside of those and, which is the more important part, also not explicable as a causal circumstance of the quality. If I may be so bold: What you are saying sounds like everyone would be using the Animation CoDec because it is so good, when the simple fact is that there are no decent free cross-platform alternatives and people are willing to accept limitations because of that. Don't get me wrong, ProRes is well designed and pretty robust, but the world doesn't come to an end without it and outside the Mac world it is difficult to deal with. Hell, it's even difficult to deal with between different versions of FCP occasionally...
    Mylenium
    I have been testing codecs for a long long looooooong time. My criterion(s) are:
    1) Image Quality and that through multiple encoding generations and color grading
    THEEEN
    a looooong way down the road
    2) Performance
    BTW - I find that working with files less compressed and thus HUGE is much better. Hard drives are so cheap that one can build himself an 8 Disk RAID0 and that takes care of everything. In PPRO I can cut real time in FulRes with an uncompressed codec with the processors maxing at 3%  while the H264 editing sequence will stutter like a drunken wasp and maxing the CPUs at 63%.... Go figure...
    ProRes 4444's impeccable imageQuality:performance ratio, is unbeaten.
    Especially on H264 material like that of the Canon5D. You might say if the source is 4:2:0 why bother upping it to 4444... Well in theory perhaps
    it is overkill. But rather than reading in theoretical white papers I conduct my own tests. And the end results are (REALITY) and way different from what theory states. TO anyone reading this. DONT believe ANYTHING you read about codec nor what I am saying.... DO YOUR OWN TESTING and judge for yourself. Problem is that you have to do 100's and 100's of transcodings with ONE source to various destinations with lost of grading and transcoding generation. THEN you have to keep track of your tests and THEN compare them. It takes WEEKs. But it is well worth while it. In my case... I start with a Canon5DMKII H264 movies. Transcode it to PRORES4444 then I do LOTS of compositing and re-encoding then lots of color grading etc etc etc. Then I export back to H264 - and the end result is STUNNING has NO artifacts and is adorable to look at. Not so with at least 6 other codecs claiming to be top-notch....
    Sure Mylenium, the world would NOT end with PR4444 not in it... BUT the WORLD has ALREADY decided that it WANTED ProRes4444 in it. It is growing and that every day..........
    Had the codec not been so darn excellent - it would NOT have been used. Period.

  • PLEASE HELP - COLOR SHIFTING PROBLEM on output NTSC monitors

    http://www.smmlv.com/testproject/
    Above is a link to a layered photoshop file that has a USA map and over a dozen network overlays used in a section of our video. I animate each layer on sepeartely in the video and have noticed a major problem recently, the color of the art does not hold true to placement. I created the art originally in Illustrator and then converted the file to Photoshop at 640x480, 72dpi. This has always worked perfectly in the past to display and animated artwork in FCP.
    Right now, in FCP I am using the NTSC DV 3:2 frame size, and the compressor of DV/DVCPRO - NTSC. I have a JVC Profressional DV deck that hooks up through firewire and sends S-Video to my monitors. This setup has always given me a great picture even though it is not completely upcompressed. Using these settings and this art, the color lines on this map in red, light blue, yellow and purple all have a "color shift" to the left about 5 pixels. It makes it appear that the line is where it is in the file, but the color overlaying the line is offset to the left 5 pixels and transperant to about 50%. This occurs only when viewed on some TV's and NTSC monitors and projectors. The strange thing is, some monitors display the color aligned almost perfectly on these maps and other monitors and projectors show this "digital halo" of color shifting really bad. If I take the layered network overlays in these colors and color tint them to black or grey, white, light green, or even light orange, they no longer have the color shifting and the detail is perfect.
    Is there any way to fix this problem? I have tried duplicating the sequence and setting the compressor to 8bit Uncompressed, and while my captured footage is not this compression, in theory the art should render at this higher resolution setting. This did nothing to solve the problem.
    I also have tried using different Broadcast safe and Y/C corrector filters with different results. The Y/C filter allowed me to reposition the color problem and thus removing most of the problem, but also removing most of the color. Nothing else has allowed me to seemingly move the color into the proper possition.
    What is causing this color shift on the displayed NTSC image?
    In FCP 4.5 I can see my rendered video in the program viewer screen and besides the pixel compression appearing on the lines, overall the video looks great paused or even better when playing. Then you view it through my deck onto my Pro Sony NTSC 19" color monitor and it also appears great, with a slight color halo to the left of these colors, but the color in the lines are there. If you are a few feet from the screen and know what you are looking for you might see it, but doubtful. Then you view it using the same signal on a 17" Samsung TV and the color shifting makes the map and other art, like the clients blue logo, look horrible, with each color line appearing twice and offset left from each other as if you had double vision. Normally I would think it is the TV causing this, but then we tested this same movie on 2 differnt projectors. The $700 Epson projector displayed everything beautifully, again with only the slightest color halo to the left, but then the Panasonic $4000 projector made everthing in these colors look double vision again. What is going on???
    One more thing to keep in mind, my color bars also show this problem with these colors as well as shot footage of these facilities. There are tall red poles in the shots and everything displays fine except for the red pole color looks like it's glowing off the pole to the left.
    PLEASE tell me there is a solution to this.

    I have tried Degaussing, using filters, changing cables, and testing other monitors and systems on these monitors, everthing I can think of to solve the issue. Is it FCPo or is it the monitors?... or is it a signal strength thing. Can monitors and projectors shift color when the signal is read from a DVD or Mini DV Deck? Is there a fequency difference (Ie: 75mgz or 80 mgz) that might be causing the shift in some monitors and not so badly in others. But if this was true, how would some DVD's (like Baby Einstein DVDs that use really bright colors) display red and blue perfect using these same player and monitor, while my projects is shifting color? Doesn't that rule out the signal from the DVD player if other DVD's do not have this issue?
    I have uploaded the original art used, an exported .jpg file from the FCP timeline and sample photos of 2 different monitors to show to show this problem as best I can. http://www.smmlv.com/testproject/
    Someone out there must have had this problem before. There's no way a color shift problem like this with Mini DV has gone on this long without someone seeing it.
    One last thing about what I have tried... I do understand that with editing in Mini DV instead of uncompressed or HD video I lose a bit of resolution (4:2:2) and I see this compression occuring in some of the areas in the video where these problems persist. But, I did remake the art and rerender this project in an 8bit uncompressed settings and then displayed that up on the screen and I get the same color shift. I keep going in circles trying to find the culprit that is causing the delema.
    PLEASE HELP! There are large tours going through our facilities daily and the large screen projector is displaying this problem as well. Let's just hope they don't notice and that their TV's at home or office does not display it on our final DVD's made.

  • Some problems with aperture 3

    I have some problems with aperture 3...
    //1
    I updated my library with aperture 3, and export some projects for make another one, everything works fine, I can switch the library very quickly...but when I want change my background in snow leopard, the first library ( current default ) don´t show anything, seems like don´t load well, the "aperture" shows right but without arrow for open the hierarchy, and if I switch the library ( the second one ) the background can load this library without problems, works with all folders, projects...
    I repaired the permissions, database and rebuild database but nothing happens.
    //2
    The second problem I think is the same. In Mail, iWork, iLife...the Media Browser don´t load my main library, only the second one, I have the last update installed, and the second library works fine, why not the first?
    //3
    I imported some projects from the one library to the other, for adjust my pipeline and make much easy my workflow, but if I import, for example, 2 folders with 4 projects, aperture import in my library 4 folders and 8 projects, the imported files are duplicated O_O
    I see the same stuff inside the folders, and when I delete one of them, the aperture delete the 2 "versions", but in the trash I see only one of them xD and if I put back the folder/project, again I see 2 versions xD
    I "fixed" creating new folders/projects and moving the photos manually...( with some crush in the process ) any idea about this problem?
    //4
    This problem is more as a enhancement...what happen if I want to sync different projects from my 2 libraries in my iPhone?? because iTunes only show me the last loaded library
    Regards,
    Jonatan

    many thanks for the answer
    not being very computer literate i will try and answer your question
    1st i tried to download a "fix" from apple support for Aperture3 but after changing the file name to Aperture.app
    as suggested by someone on forum I got the answer
    The version of Aperture installed on this Mac must be updated through the Mac App Store. Check the Mac App Store to see if an update is available.
    by aperture is 3.2.2
    2nd in answer to your question,
    memory 2gb 667  Mhz DDR2 SDRAM
    I have 128.53 gb free out of 319.21 gb
    hope that helps

  • Problem with Aperture 3.6 Can't open Preferences

    I had a problem with Aperture 3.6; opened a new Library from the Vault, now cannot open Aperture Preferences. When I attempt to open preferences I get a very thin vertical line about 1 ½ inches long?? Any fixes for this/  Thanks, Vic

    Try to delete the Aperture preferences as described here at this link:
    Get help with Aperture 3 - Apple Support
    Steps to reset preference settings
    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.
    Restart your computer if you're using OS X Mavericks.
    The locations of your Aperture libraries are stored in the preference file listed above. If you have stored your library outside the default location of  ~/Pictures/Aperture Library, make a note of where the library is before deleting the Aperture preferences file. If you have more than one library, you can bring up a dialog to choose which one to load by pressing Option immediately after you open Aperture.

  • I still am having problems with Aperture not loading,  It just refuses to work, and I get the message saying it has encountered a problem, and I may need to re-install which I have done dozens of times. The fix mentioned on an earlier post wont work as it

    I still am having problems with Aperture not loading,  It just refuses to work, and I get the message saying it has encountered a problem, and I may need to re-install which I have done dozens of times. The fix mentioned on an earlier post doesn't work as it is for Ver 10.6.6 and I am running 10.6.7

    Do you have Final Cut installed on your machine?
    If so, you may want to look at this article: http://support.apple.com/kb/TS3528
    Let us know if that helps.

  • RAW file rendering problems with Pentax-k5

    Since a few weeks I have serious problems with the raw rendering in aperture 3.4. I have done everything to solve this problem, but until now without succes. I have upgrade with mountain lion OS X 10.8.2 and I use the latest version of aperture 3.4.3 RAW 402 build 672.6.
    Does anyone have this problem to? Or do you know how to solve this problem?
    Regards
    Jan K.

    Jan,
    that may be the same problem as discussed in this thread. Do you use in-camera settings to enhance your pictures? these will not be captured in the raw processing that Aperture does, but the pentax software understands the in-camera settings:
    Image Previews In Aperture 3 - Canon 5D MK2
    Regards
    Léonie

  • Raw file rendering problems with Canon EOS 5D in Aperture 3

    Since upgrading to Aperture 3, I have had serious problems with the rendering of Canon EOS 5D (not Mark II/III) RAW files. With Aperture 2, both the preview and full-sized images looked basically the same as the original images as displayed on the camera's display, without any adjustments.
    With Aperture 3, each preview images initially look fine after import, but when Aperture re-renders it from the RAW file (e.g. when displaying the full-size image), the colors are drastically intensified, and the hue is shifted generally towards green/blue. I've checked the RAW Fine Tuning, and it is set to the defaults. If I turn the default RAW Fine Tuning settings all the way down, the image is still not at all like the preview from the camera - it becomes much darker and stays too blue/green, with washed-out colors.
    A friend with a Canon EOS 5D MkII also recently upgraded her Mac from Aperture 2 to 3, and hasn't experienced any problems. We've tried importing RAW files from my (non-MkII) camera to her Mac (with the default RAW Fine Tuning settings), and get the same results as with my own Mac (i.e. strange colors), so the problem seems to be related to the camera model.
    I've also noticed that scanned greyscale tiff images (including images that were originally imported under Aperture 2) are changed when first displayed by Aperture 3 - they become darker and more contrasty, with lots of information lost in the shadow areas.
    I've also tried removing Aperture preferences, Aperture itself, and re-installing from download, with no change in the problem. (Aperture is the current latest version, 3.3.2.)
    Has anyone experienced similar problems?

    I'm having the same problem.
    iMac running Mac OS X Lion 10.7.4 and Aperture 3.3.2.  Workflow is importing through Canon's DPP and then using referenced images in Aperture.  The images look great in LR4, or Canon's DPP but are flat and dingy in Aperture.
    There's a free preset that goes part way to fixing it at http://theapertureblog.com/2011/02/10/my-aperture-workflow-for-working-with-cano n-5d-mark-ii-files/
    but as good as this fix is, it doesn't quite do the trick. [not being a hater, and not saying I can do better]
    I just got back from shoooting 1,500 images with a 5DMii and a T2i using Canon 24-105L IS, 70-200 2.8L, 50 1.8 and a Sigma 120-400 and the T2i images are not just better, they're in a different league.
    I've tried shooting in Faithful, Neutral and also toggling these presets in different ways and still can't get Aperture to match what I see on the camera's screen or in other Apps.  I love the interface and DB of Aperture, but what's the point of using it if it doesn't produce and awesome image in the end?

  • Color shift problem

    I have a problem with a sudden color shift when starting certain apps. I'm also using a 2nd Eizo monitor.
    The problem persists after repairing all color profiles.
    Not only in CS apps, as well in QT player, Pixelmator, QT utility and others I'm getting the color shift.
    Hardware test passed using MBP end 2011 10.8.3.

    What version of Windows are you running?
    Let us know and I or someone can give you instructions for setting the color profile to Windows default (sRGB IEC61966-2.1) to test to see if the problem goes away.
    For example, in Windows 7:
    Click Start, enter color management in the search box.
    Click Color Management when it comes up.
    Click the Devices tab.
    Check [ ] Use My Settings for this device.
    Add sRGB IEC61966-2.1 and set it as the default profile.
    Close out then log off Windows and on again.
    -Noel

  • Problem with Aperture 2 and Digital Camera Raw Compatability update 3.1

    Has anyone using Aperture 2 experienced problems with the Digital Camera Raw Compatability update 3.1. It may be purely coincidence but, since downloading this on March 3, I get the dreaded red screen and unsupported image format on my previously downloaded and edited RAW photos. I use a Pentax k-7 with which, once set up, I have had no problems until now!
    Please - any help would be very gratefully received

    That probably explains why any checks that your computer did to see if the Camera Raw update was okay to apply didn't stop it. You should probably contact Apple and explain that they broke something that was working fine previously.
    A few people have reported backing off Camera Raw 3.1 and going back to Camera Raw 3.0 for now. This note is one of the ones I've found describing how to do that, if you wish to try that. Or, you could head down the path Apple means to lead you on and upgrade to Aperture 3.
    Message was edited by: Ailish Eklof

  • Color shift problem in Safari and Preview

    I have recently had a color shift in Safari and in Preview.  My monitor is color profiled (using eye-one) and images opened in Aperture, Bridge, Photoshop and the Color Management app look just fine.  However, images on the web-browser (Safari) and in Preview show a definite and disagreeable increase in saturation, particularly in the red-orange range. Is there a suggestion on how to deal with this problem?
    Thanks for the help.

    This could be part of the problem >  Known Issues | Adobe products on Mac OS 10.7 Lion
    You can have Safari set to open PDF files in Preview.
    Right or control click the Safari icon in the Applications folder then click Get Info.
    In the Get Info panel click: Open with
    Select Preview
    Click: Change all

  • Batch processing "save for web" color shift problem

    In Illustrator CS3, when batch processing "save for web and devices," there is a dramatic color shift in resulting files.
    Is there a workaround for this problem?
    Thanks!
    Karen.

    Make sure the color mode of your documents is RGB (not CMYK) and that your workspace is sRGB.

  • Printing problems with Aperture

    I just switched from Windows (long story, many years) to an Intel iMac 20, with Aperture pre-installed. I had a Canon PIXMA iP 6000D printer; all prints had a yellow cast. I bought an HP Photosmart 7160; all prints have a yellow cast. I have done a format and re-install of OS X and all software. I have installed my Aperture software on another iMac 20 at the store; with my printer and the store's printer the prints had a yellow cast. I took my computer to the store and printed on their printer; all prints had a yellow cast. I get the same results printing from Photoshop CS2 for Mac or from Preview. I have tried several USB cables. My monitor is calibrated with a SpyderPro 2. Prints directly from a memory chip in the printer are fine. I've tried all the adustments in the print setup; no help. I'm working on the sliders now, but with seven sliders with 100 possible settings on each I think that's seven to the 100th power possible settings. Both printers work fine with my Windows computers.
    I've exhausted all the available Apple support. Anyone have any ideas?
    Arthur
    iMac 20   Mac OS X (10.4.8)  
    iMac 20   Mac OS X (10.4.8)  

    Well, to reiterate, I am using the HP printer as there is only room for one printer on my desktop. I am using HP paper, the "Advanced" type which is bar coded so that the printer recognizes the paper type and sets the appropriate defaults. I have also tried other HP papers, and selected them from the printer dialog. I have tried setting the paper type manually with the "Advanced" paper. I have tried printing with all the defaults left alone.
    When I said that I had tried every print option in the printer dialog sequence, I meant that in the printer dialog I had tried each of the paper types, each of the color options, each option under HP Colorsmart, several types of HP printer paper with the proper option selected. Under ColorSync, there are only two options here. One is "Standard" and the other is "in Printer" which is greyed out.
    Go down the print dialog. I have tried every option. Under "Paper Type, Quality" I have tried every option for paper type, quality, and color. I have done this systematically, using all available combinations.
    I don't know how else to describe the process Apple and I have tried to use to try to repair my problem. Name an option--I have printed using it.
    I tried the "sliders" as a possible way of altering the output from the computer to the printer, as I had exhausted all other possibilities, and if I could find the magic combination I could set it as the default and all my prints would be
    affected by those settings and print correctly. They appear in the printer dialog from Aperture. My photos print correctly if I copy the file to a Compact Flash chip and place it into the printer slot and print directly.
    Pardon me if I seemed snappish. I bought the iMac specifically for photographic work, have had it for a couple of months, have made several hundred prints, have exhausted support from Apple, and am grasping at straws. I have 8 GB of photos from my last trip which remain unprinted. Shortly before the trip I did two wedding shoots which were quite successful, printed from Photoshop CS2 under Windows. All my current photos print acceptably on this printer from my Windows computer. They are not acceptable printed from Adobe CS2 for Mac.
    Can I be more specific in what I have tried? Do you have a suggestion for something for me to try? Apple and I are grasping at straws, and would appreciate any help you can give.
    Arthur

  • 10.5.3 problem with Aperture 2.1

    I recently spent the $200 to buy Aperture and have been enjoying it.
    Until, last night I updated Leopard to 10.5.3
    Last night I read about problems other people were having with RAW photos appearing black upon editing after upgrading, and NOW the same thing is happening to me.
    Not only that, but upon adjustments, my photos are also appearing as a 'scrambled' graphic.
    I can't seem to find the post, but I notice that touchy topics are quite often deleted from this forum very fast.
    Does anybody know if Apple has addressed this and plan to release a fix?
    I am a wedding photographer who has a tight deadline to deliver, hence the reason I just picked up a new imac 24" and Aperture 2.1
    Now I am on hold and can not deliver my product. I hope there is some info out there.
    Thanks in advance!
    Message was edited by: colorsound

    I'm posted an image of Aperture corruption, fresh this morning:
    http://lemon.soju.co.uk/2008/06/05/would-you-trust-your-photos-to-an-application -that-does-this/
    - New iMac 3.06GHz Dual Core, 4GB Memory, NVidia 512MB (received Sunday 1st June 2008)
    - 10.5.2 upgraded to 10.5.3, then Aperture 2.1 trial installed
    - First import of 40GB of photos, left to run overnight
    - When trying to use this morning, Aperture screens were corrupt and it refused to shut down. I had to power off then boot back into Mac OS X. When I restarted Aperture it worked, but it still seemed to have problems taking over the machine - eg, I wasn't able to send mail from Gmail within VMWare Fusion until I closed down Aperture. I never have problems with VMWare Fusion.

  • Is anyone else having problems with Apertures Date fields?

    After experiencing a sysems failure I began restoring my images from backups.  I have had no end of problems with Image dates.  I have come to the determination that Aperture is NOT using either the "Create Date" or "DateTimeOriginal" as the image "Date" or "Date Created" data if other fields have other dates.
    Here is a clip from my image metadata using exiftool:
    File Modification Date/Time     : 2012:09:23 19:53:15-04:00
    File Access Date/Time           : 2013:01:16 11:34:38-05:00
    File Inode Change Date/Time     : 2013:01:16 11:31:32-05:00
    Create Date                          : 2006:02:20 11:51:12.10
    Date/Time Original              : 2006:02:20 16:51:12.10
    Modify Date                          : 2006:02:20 11:51:12.10
    And here is what Aperture utilized on import
    Date:                               9/23/12 7:53:15 PM EDT
    Date Created                         9/23/2012 7:53:15 PM
    So Aperture utlized the File Modification Date/Time as the Create Date despite that the fact that the Create Date field is present and is properly formatted in the original image.
    According to the Aperture mapping table, this shouldn't be happening.
    Now, before someone recommends that I use Aperture's Date Adjust utility - I'm talking about  slightly over 30,000 images.  Editing images one at a time, or in blocks when you don't know what field Aperture is using as the Create Date would require individual inspection of each image followed by manual adjustment of each image.  That approach isn't acceptable.

    Hmm ok, let me restate the issue then, I thought I was clear.  I could have pointed out in my original post however, that only the EXIF and IPTC date fields were displayed from the metadata dump.
    The data set presented in my first post is the EXIF dataset from the file which clearly shows the image was captured by digital camera at
    Create Date                          : 2006:02:20 11:51:12.10
    Date/Time Original              : 2006:02:20 16:51:12.10
    (The delta of 5 hours is the result of Zulu versus local time offset)
    But, when I ingested it into Aperture, the import routine utilized the IPTC field
    File Modification Date/Time     : 2012:09:23 19:53:15-04:00
    which is updated by the OS whenever you move the file around outside of Aperture. (a number of image data fields are updated by the OS - filename for example is another.).  This resulted in the image date fields being stamped in Aperture as:
    Date:                               9/23/12 7:53:15 PM EDT
    Date Created                         9/23/2012 7:53:15 PM
    Which obviously came form the File Modification Date/Time field and not (either) the Create Date or Date/Time Original fields.

Maybe you are looking for