Major problem with raw files.

I am a photographer and recently did a wedding. The photos shot on my Olympus E-30 when imported into Aperture 3 have a strong colour cast (towards the green, looks like cross processing). The images shot on my E3 are fine.
This is a new problem. I am not posting this in the Aperture forum because the colour cast is the same in preview and in quick view. If I shoot in jpeg the colours are fine, or if I import via olympus software as tiff the colours are correct (i don't want to do this regularly!)
The problem is therefore in the OSX and is a recent.

I am a little ****** off with Apple of late because:
1) Aperture 3 is often painfully slow even though I went out and got a brand new laptop with full 8gb ram and a special fast hard drive. It hardly performs better than the relatively new one i replaced it with!! Thus loosing me a lot of money and time.
2) The latest system update means that whilst in Aperture 3 anything playing in iTunes or streaming over internet sometimes just turns into white noise.
3) This problem has bugger all to do with them updating the support for my E-30 as it has been supported since i bought it a year ago! Basically it's likely some update (camera raw?) messed up something that used to work fine.
4) My G3 iPhone is now at times so bloody slow and buggy due to their latest ios update it's an embarrassment! I guess they would like me to go out and upgrade that at ridiculous expense as well when the contract runs out in Nov, between apple and the thieves who for now here in Spain are the only legal mobile providers I and other users are being screwed (so I may hack the thing and change provider or horror of horrors go Android).
I have used Apple products for over 15 years and happily promoted them and converted quite a few people from PC. Now however I feel less evangelical as they are getting sloppy and dropping the ball because they are more interested in pushing new gadgets into the market.
Sorry to rant but when you are trying to edit a wedding of 1500 images and it's painfully slow and erratic to do in A3 you have a right to be ****** off!.

Similar Messages

  • Problems with RAW files from Nikon D4

    At the moment I'm using LR 4.1 rc and PS CS 6 beta. I tried to send a D4 raw file from LR to PS, but PS didn't open it.
    The next thing I tried was to open D4 raws directly with PS CS 6, no success either.
    The raw files from my D200 aren't any problem.
    So is there knowledge wether PS CS 6 is supporting Nikon D4 RAWs or not? If it should be supported, what could be my problem?
    Thx in advance
    Dominik

    See this link for full details on camera support in Camera Raw versions:
    http://blogs.adobe.com/lightroomjournal/2012/03/raw-support-in-lightroom-and-camera-raw.ht ml
    Snip taken from link above:
    You’ll also note that ACR7, available with Photoshop CS6 beta, is lagging the most in updated camera support.  This is based on when we lock down or “bake” the code for each release.   Even though ACR7 was only released last week it was “baked” before Lightroom 4.0 and Camera Raw 6.7.  Similarly, Lightroom 4.0 was finalized before Camera Raw 6.7.  We’ll get Lightroom and Camera Raw in sync soon but in the interim, here’s the latest incremental support list for each product, relative to Camera Raw 6.6 and Lightroom 3.6:
    Photoshop CS6 beta with ACR7
    Canon PowerShot S100V
    Fuji FinePix X-S1
    NOTE:
    ACR7.1 will have the superset of all currently supported cameras in ACR6.7 and LR4.1 plus a few extras.

  • Problems with RAW file conversion in PS5?

    I recently updated Photoshop and Lightroom to PS5 and LR3.  Never had any problems when I moved between the two programs before.  Now, when I open a RAW photo (jpegs are fine) into PS5 there is a colour/contrast shift which gets saved when I import it back to LR (doesn't make a difference if it is LR2 or LR3).  This happens even when I do nothing but open the file, do nothing and save it back to LR.  I checked and the problem doesn't happen with LR4.  I have ensured that my colour spaces and preferences settings are exactly the same in both PS4 and PS5.  Please, can anyone help me?  I have looked over the commentary on a lot of similar issues but haven't come across the answer.  This is important because I am having problems when I send my photos out to a lab to print.   Thanks in advance!

    Dear Dorin,
    Thank you, thank you, thank you for replying to my question!!!
    I have been having a lot of problems printing (to a lab, not my own printer) since I upgraded to PS5 and LR3 so I am in the process of trying to eliminate all the variables.
    The problem I notice is that my RAW files in LR3 (jpegs are fine) change when I work on them in PS5 and save back to LR3 or when I export them as jpegs to my desktop and re-import back to LR3.  The photos become darker and slightly more contrasty. I have attached some screen shots.  The differences are subtle when
    looked at side by side but really quite noticeable when you switch back
    and forth between the two. Different photos change more than others.
    I have tried various other combinations and the photos stay the same (ie. photo from LR4 to PS5 and back, photo from LR2 to PS4 and back, photo from LR2 to PS5 and back).  So I was thinking it was something to do with the way LR3 converts RAW files to other formats.
    I use Spyder3 Pro for colour calibration and I have made sure that color spaces are the same across programs.  I have also tried  Adobe1998 and ProPhoto with the same results.
    Thank you for your suggestion to figure out the ACR conversion.  I couldn't find the option for plug-ins under "help" so perhaps I am doing something wrong.  I think that my ACR is version 6.1.
    Any suggestions you can offer would be greatly appreciated!!  My business is getting quite backlogged while I try to figure this all out.
    Thanks again for your help.  Cheers, Michele

  • Problems with RAW files transferred via SDHC

    Hi,
    Hoping someone here can help me out with a strange issue i'm having. I recently got a new Canon 450D and i'm having some weird issues with transferring the RAW files to my iMac (I previously had a 350D which used CF cards and never had an issue).
    If I try and view or download the RAW images via a number of different SDHC card readers they come out looking like this.
    (example taken from Adobe bridge but is the same with Lightroom, Aperture, Preview etc. . .)
    However, if I download the images directly from the camera via USB they are all perfectly fine when viewed in any application. I have tried a number of different cards, readers and USB ports and the result is always the same. Even stranger is if I boot the iMac into Windows 7 via Bootcamp and view or download the images via SDHC they are all perfectly fine??
    Given that the images are ok on the mac when downloaded from the camera i'm pretty sure this is something to do with the SDHC, but I just can't figure out what's causing it.
    I have searched pretty much every combination of keywords for this problem but there doesn't seem to be an answer anywhere? The only thing that comes close is corrupted RAW files due to hardware problems/failure but I have ruled this out due to them being ok when transferred from camera.
    Any help would be greatly appreciated as I just don't know why it's happening?
    Thanks

    See this link for full details on camera support in Camera Raw versions:
    http://blogs.adobe.com/lightroomjournal/2012/03/raw-support-in-lightroom-and-camera-raw.ht ml
    Snip taken from link above:
    You’ll also note that ACR7, available with Photoshop CS6 beta, is lagging the most in updated camera support.  This is based on when we lock down or “bake” the code for each release.   Even though ACR7 was only released last week it was “baked” before Lightroom 4.0 and Camera Raw 6.7.  Similarly, Lightroom 4.0 was finalized before Camera Raw 6.7.  We’ll get Lightroom and Camera Raw in sync soon but in the interim, here’s the latest incremental support list for each product, relative to Camera Raw 6.6 and Lightroom 3.6:
    Photoshop CS6 beta with ACR7
    Canon PowerShot S100V
    Fuji FinePix X-S1
    NOTE:
    ACR7.1 will have the superset of all currently supported cameras in ACR6.7 and LR4.1 plus a few extras.

  • CS2, Vista, and problems with raw files

    Hello everyone. I have recently installed CS2 with RAW updates 3.6 on my new computer, which happens to have Vista on it. The RAW files I created with my Nikon D80 are not showing in Bridge either as thumbnails or when I click on them to enlarge them.
    Does Adobe plan to address this problem through future downloads?
    Any suggestions? I may be slow to respond since I will be out of town this weekend.
    Thanks!

    I've seen some strange things happen with Photoshop Elements on Vista. Some of it worked some didn't.
    The security features of Vista are a bit too much at times and I got Elements to work by running the program with Administrator Priviledges.
    It might be worth a try. Right click on the desktop icon and select Run as Administrator ( or something similar - I'm not on a Visa PC right now)
    Colin

  • Problems with Raw files PSE 11

    I have PS Elements 11, recently while part way through editing a batch of photographs taken in RAW I was unable to access the edit screen, I am mystified as I am not aware of making any change to my routine. Help.

    After research I downloaded an updated ACR 7.2
    What exactly did you do? The best way to update ACR is to go to Help>Updates in the editor, which should have brought you to 7.4.

  • Problems working with raw files

    just purchased elements 5 to work with raw files. have downloaded 4.2 and installed it into correct file and have moved existing raw 8 bit file to desktop. when i try to import raw files into elements it still wont let me. stating error or wrong file type or something. i am working with windows xp. and shooting with a nikon D80.

    [email protected] wrote in
    news:[email protected]:
    > Martin ... Not many Elements users here ... the Elements forum is
    > here:
    >
    >
    > That said ... check Elements' 'Help' menu for the ability to list the
    > verion of ACR installed, and any ability to "update" automatically.
    >
    > HTH :)
    >
    I don't think that ACR 4.2 will work with Elements 5.
    John Passaneau

  • Problem with NEF files from Nikon D4

    Hi everyone. I find a problem with nef files from my Nikon D4. When files are open in ViewNX2 (free viewer software from Nikon) they are perfect, as shooted... but in ACR they are very different... I use LR4 or CS5 with ACR 6.7 and the difference seems to be linked at D-Lighting function. My impression is that ACR dont read this option and picture are very very dark that original shootings. Anyone have this problem?

    This question used to be answered in the FAQ before they revised it.  So, here we go again.  ViewNX is capable of reading all of the in-camera settings such as, camera profile, saturation, sharpness and other settings.  It is capable of doing this because it is Nikon Software, and they have the ability to program it to read the settings from their raw images.  Lightroom does not read those settings from Nikon cameras or any other brand of camera.  Part of the reason is that different camera makers store those settings differently.
    When I first started using Lightroom I adjusted one of my images that represented what I normally shoot until it looked the way I wanted it.  Then I saved those adjustments as my default settings for the camera.  From that point onward, whenever I import images those settings are automatically applied, and it takes care of the vast majority of my images.  Of course, I still have to make individual adjustments.  But my default settings greatly reduce the amount of how they work that I have to do.
    Active D-lighting is is one of those features that Lightroom does not recognize.  You would be well advised not to use it, or else create a preset to simulate its effect.  It will provide no benefit to your Lightroom work.
    This is a fundamental difference with Lightroom, and something that must be understood and implemented if you are going to use the program effectively.
    I realize this question was asked in the ACR forum and I referenced Lightroom throughout.  But the principle is the same, and the recommended procedure is the same.

  • Problems with .ARW files and auto toning

    problems with .ARW files and auto toning
    let me try to explain this because this has happened in past and never found a way to resolve but i lived with it
    now that I have a Sony A7R the problem is more serious
    Firstly i take pride it making the picture happen all in camera, i use DRO lvl 5 to get enough light, like when i'm shooting at dusk. DRO its like doing HDR but in a single file, it lightens the darks. in my camera i'm happy with results
    but when I upload them to lightroom, they come out near black.
    allow me to explain
    lets say I import 100 images
    i double check my preferences and everything is UNCHECKED when it comes to importing options, there is no auto toning, nothing.
    as the images import i see a preview in the thumbnail which looks fine.
    i double click on one to enlarge it, hence leave grid view.
    for a brief 1 or 2 seconds, i see the full image in all its glory but than lightroom does something funny, it darkens the image
    one by one as it inspects each image, if it was a DRO image it makes it too dark.
    to make this clear, the image is perfect as it was in the beginning but after a few seconds lightroom for some reason thinks it needs to correct it.
    how to prevent lightroom from doing this, i want the image exactly as it is, why must lightroom apply a correction>?
    i think it has to do something with interpreting the raw file and lightroom applies its own algorithm.
    but here is what i dont get.....before lightroom makes the change i'm able to witness the picture exactly as it was taken and want it unchanged..
    now i have to tweak each file or find a profile for it which is added work.
    any ideas how to prevent lightroom from ruining my images and just leave them as they were when first detected...
    there are 2 phases...one is when it originally imports and they look fine
    second is scanning each image and applying some kind of toning which darkens it too much.
    thanks for the help

    sorry thats the auto reply message from yahoo email.
    i've disabled it now
    thing is, there is no DRO jpg to download from the camera
    its only ARW. so my understanding is when i use DRO setting, the camera makes changes to the ARW than lightroom somehow reads this from the ARW.
    but then sadly reverts it to no DRO settings.
    because i notice if i take normal picture in raw mode its dark but if i apply dro to it, it comes out brighter, yet when i d/l the image from camera to lightroom, which is an ARW - there are no jpgs. lightroom decides to mess it up
    so in reality there is no point in using DRO because when i upload it lightroom removes it.
    is there a way to tell lightroom to preserve the jpg preview as it first sees it.
    its just lame, picture appears perfect...than lightroom does something, than bam, its ruined,.
    what do i need to do to prevent lightroom from ruining the image? if it was good in the first place.

  • Problems loading RAW files from Canon 6D in Elements 10

    Elements 10 - Windows: I have been using the software for a couple of years and never had a problem loading RAW files from my Canon T2i ir 60D, however I just purchased a Canon 6D and when I try to load a RAW from the 6D I get Cannot open 'C:\User...CR2' because it is the wrong type of file.  I thought cameraraw 6.5 patch would be the fix but when trying to install I get "Error loading Updater workflow"

    Will the DNG files perform the same, meaning will I retain all the information that makes RAW important for processing?
    Yes. That's why DNGs were invented. Adobe has put a lot of work into the DNG format for this very reason.
    Raw files are proprietary and manufacturer specific. Raw formats change with every make and model of camera. Software must be updated for the new Raw format of every single camera. Adobe does an admirable job of upgrading Camera Raw for every new camera.
    DNG is also a Raw format but it's open source and works in any software which can read the DNG format. If camera manufacturers used the DNG format instead of their own Raw format, you would not have to upgrade Elements 10. But they don't, and probably never will, so you must upgrade the Camera Raw plugin (and therefore Elements 10 since it's not compatible with the new Camera Raw) to read the new Raw format from the 6D or add another step to your workflow with conversion to DNG first.
    See
    http://photographylife.com/dng-vs-raw
    http://www.adobe.com/products/photoshop/extend.displayTab2.html

  • Issues with RAW files from my 7D

    I have Aperture 1.5.6 on my computer and the software updater says that is the current version. I shoot with a 20D and a 7D. I upload my raw files to Aperture and edit them from there and then process for a jpeg. However, every time I upload a raw file from my 7D I get the following message when I click on it to edit it: Unsupported Image format.
    Any words of advice, other than just buy Aperture 3??

    I have Aperture 2.X and had zero issues with RAW files from a 7D, so I think the problem is you are on 1.X. Converting to DNG first was a good suggestion if you don't want to purchase 3.X. Yet another reason to hate proprietary raw image file formats.......

  • Major problems with Premiere CS4

    Hello there!
    I'm having major problems with CS4. I recently bought a new computer - essentials are as follows:
    Intel Core i7 920 2.66GHz
    2 x Kingston 3x2GB, DDR3 1333MHz (=12 GB RAM)
    Ati Radeon HD 5770 v2
    Asus P6T SE, LGA1366, X58, DDR3, ATX
    2 x 500GB, Barracuda 7200.12 (RAID1), system disk
    2 x 1TB Barracuda 7200.12, media disks
    Windows 7 Pro 64 bit
    Adobe CS4 Production Premium + latest updates
    The problem I have has mostly to do with Premiere although I think the rest of Production Premium softwares should be running better on this computer as well.
    For starters, I was highly disappointed when I couldn't view a single HD clip from the Premiere timeline (it was an .m2ts rip from a previously self-burned Bluray disc) at all. Rendering is very slow and even after that the video doesn't run normally, showing just a few individual frames per second. When I point the timeline at a certain spot, it takes many seconds until even that very frame is shown in the monitor window.
    And this is not all - I decided to try with a basic DV AVI clip, previously captured with my PPro 1.5 on my earlier computer (3.2ghz Pentium from 2005). It's a native file so it doesn't even need rendering and still the same problem occurs. With normal playback only about 6-10 frames are shown per second. It's absolutely ridiculous - even my 2004 laptop runs DV AVIs more smoothly with PPro 1.5.
    While I'm running the Premiere, the level of used RAM comes only up to around 24 percents. The processor, then again, comes close to a hundred when play is pressed on the timeline.
    I haven't had such immense problems with other Production Premium softwares (though as I said, I think they should be running faster as well). Otherwise the computer is running smoothly.
    A friend of mine pointed out that the graphics card I'm using isn't on the Adobe website's list of supported ones with Premiere, but afaik it shouldn't even be a graphics card problem with this high-end machinery.
    So - I sure could use some help and ideas about how to get the Premiere working. My main intention for buying a new computer and Adobe CS4 Production Premium was to start HD editing after all! Thanks beforehand!

    Hi
    Yeah, I hope he solves problem and knows how it got solved and tells us all...it's like being a detective !  " Mr Plum did it in the "svchost" room ! "
    I got a little lost on this....
    You are welcome and I'm glad that it paid off so nicely for you. One more  suggestion, if I may: I'm a big fan of a fixed pagefile size. When making a  fresh install of Windows, one of my first actions is to set a fixed pagefile on  a different disk (min=max) before installing anything else on that different  disk and removing the pagefile on the C drive. This will ensure that the  pagefile in on the fastest part of the drive and will never be  fragmented.
    I think it used to be that I made swapfiles, or swapdisks which now seems to be called pagefile.  That in itself is a little confusing semantic wise, because of the use of mempage stuff.  It used to be that base memory was 640k, with the upper memory (to make up 1024 kb) was mostly for drivers and stuff.  If more memory was needed than 640k (an event the inventor never thought possible...  "who could want more than the enormous amount of 640K ?", he said..)..the extended and expanded memory got invented to swap memory pages from that 640k as needed with the rest of RAM.  That's basically correct right ?  Sooooo, I don't know if that still goes on, but I suspect it does, unless someone totally changes the architecture of the computer and cpu and fsb and everything...  but I don't know what is going on nowadays.  Anyway, there were other ways besides windows OS to create virtual memory on the hard drive, and Photoshop was one of the programs that could do that, I think.
    Why MS would want to call the swapdisk virtual memory "pagefile" is beyond me.
    Anyway, be that as it may, I understand that making the pagefile first on a drive so it's close to the center of the drive (heads don't have to travel far to access).  But I haven't added a lot of drives to a system before, and I suspect I will be pretty soon...and this is the part I don't get...
    You add drives and put OS on them?  So they are bootable ?  I've added a drive or two but just formatted and used as more storage but didn't put OS on them.  So that part is confusing...
    Then you take the pagefile off the C: drive ?  Are you then using the new drive as your boot drive and the C: drive is too full to use accept to run the programs already installed ?
    Thanks again !
    Rod

  • Major problems with CS5

    We just moved to CS5 and are having major problems with crashing and losing text. I haven't seen these kind of issues since beginning the Indesign/Incopy workflow way back in CS2. I've got dozens of users (Indesign and Incopy) slamming me with complaints of crashing. Indesign crashes when exporting to Incopy (usually when exporting a layer), Incopy users are complaining of crashing when peforming copy/paste either from Word or from within Incopy. Also have had incidents where the text in the Incopy story just disappears or the stories corrupt and will not open in the layout or as a standalone file. Trying to open one will crash the application.
    Other departments in our organization who do not use Incopy are not experiencing crashing issues with Indesign CS5, so I have to believe the problem is Incopy.

    Try moving everything to a local harddrive and working on a file there. If you don't get the crashing then you can start checking the network. And please, one thread is enough.
    Bob

  • Sharpening issues with RAW files

    Hi,
    I have downloaded lightroom 5 as a one month trial and have been playing with the program. I am not an experienced user and are wondering if I am doing something wrong, have wrong settings applied or if it is the known sharpening bug that messes with my photos. I know that sharpening and noise reduction includes a bug that does not let you export pictures 1/3 of original size with sharpening/noise intact. However, in my case, this also happens with RAW files. I do not crop or change size/resolution to any of the photos, but the sharpening is still not working. Photos look great in develop mode, but when I click on library mode to export them, all sharpening disappears!
    Is this the same bug previously reportered "only for pictures 1/3 of original size", or do I have some strange settings applied?
    I was loving lightroom 5 up until I noticed this, and now I am reluctant to buy the product...
    I'd be greatful if anyone has any input on this!
    Thanks in advance

    I have Aperture 2.X and had zero issues with RAW files from a 7D, so I think the problem is you are on 1.X. Converting to DNG first was a good suggestion if you don't want to purchase 3.X. Yet another reason to hate proprietary raw image file formats.......

  • I am trying to get the free trial to cc but it said there seems to be a problem with the files (Error code: 205)

    I am trying to get the free trial to cc but it said there seems to be a problem with the files (Error code: 205) please help

    BOILERPLATE TEXT:
    Note that this is boilerplate text.
    If you give complete and detailed information about your setup and the issue at hand,
    such as your platform (Mac or Win),
    exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
    your settings in Photoshop > Preference > Performance
    the type of file you were working on,
    machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
    what troubleshooting steps you have taken so far,
    what error message(s) you receive,
    if having issues opening raw files also the exact camera make and model that generated them,
    if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
    etc.,
    someone may be able to help you (not necessarily this poster, who is not a Windows user).
    a screen shot of your settings or of the image could be very helpful too.
    Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
    http://forums.adobe.com/thread/419981?tstart=0
    Thanks!

Maybe you are looking for