Olympus E-500 raw file problem with long exposures

Hi,
This topic has come up before, but wasn't resolved. Maybe its somewhere else, but I can't find it.
http://discussions.apple.com/thread.jspa?messageID=4994383&#4994383
Raw files from my Olympus E-500 with exposures over 3.2s come up with overexposed looking previews in Aperture. I think there is some automatic noise reduction (dark frame) info in these files, since they are 16.68Mb instead of the normal 13.47Mb. Apparently Aperture doesn't know what to do with these larger files.
Is there a known way around this within Aperture? The files open fine within Olympus Master 2 and Raw Photo Processor.
I've pasted a screen shot here with some links to raw files:
http://www.mso.anu.edu.au/~grant/wp/2007/10/raw-problems-with-aperture/
cheers
Grant

Yea, I've had that issue also and figured out the DNG workaround. Filed a bugreport with Apple on Nov 2nd, 2006. It sat with what looked like no attention right up until I got an e-mail on Oct 26th, 2007 (notice the date) saying that the issue was fixed in 10.5. I had already preordered Leopard so was hoping this was right. It wasn't. It's still borked. Logged notes back into the issue saying it wasn't.
Perhaps if more E-500 users report this it'll get more attention.
http://bugreport.apple.com

Similar Messages

  • Aperture 1.1 and Olympus E-500 RAW files

    Hi there.
    My problem:
    RAW data from my Olympus E-500 isn´t supported by Aperture 1.1
    After importing RAW files there´s no image data and the preview displays "unsupported image format"
    I wonder why, since that camera is listed in the compatibility list under http://www.apple.com/macosx/upgrade/cameras.html
    Even if it is not listed in the compatibility list of apertures supported RAW filetypes, in my understanding aperture should deal with those files if the OS supports the camera. But this understanding seems to be wrong..
    I know that RAW files can be quite different in structure, so files generated by the E-1 seem not to be the same as RAW files generated by the E-500.. even if they have the same files extension. But I wonder that even the E300 is supported but not the E500.
    Does anybody knows if there is a workaround for this or if there is a chance to use Aperture with these files in the near future?
    Thanks for any information.
    G5 Dual 2.5 GHz, 4GB RAM   Mac OS X (10.4.6)  

    I know that RAW files can be quite different in
    structure, so files generated by the E-1 seem not to
    be the same as RAW files generated by the E-500..
    even if they have the same files extension. But I
    wonder that even the E300 is supported but not the
    E500.
    You are indeed correct that the .ORF raw files generated by the E-1 and the E-300 are different from those generated by the E-500. Olympus must take the responsibility for this. I will assume that they had some good reason for changing the file structure between camera models, but I don't know what it is and have difficulty imagining what it could be. When the E-500 was released, there was considerable discussion about this on several forums (notably the Olympus SLR forum at dpreview.com) as there were several other software programs (sorry, can't remember which specific ones) that also had been working well with .ORF files from the E-1 and E-300, but did not support E-500 .ORF files.
    Why Apple has not added support for the E-500 raw files is another good question, and I hope you've posted your request as feedback for the Aperture team. I am using Aperture and an E-1, and have been enjoying the combination ever since Aperture 1.0 was released. The raw conversions for the E-1 have definitely improved since 1.1 was released, so Apple knows something about .ORF files. I hope that you will also get to experience that (soon) when support for the E-500 files is added. I'm not aware of any workaround at this time, but will post here again should I come across one.
    Let's hope that Apple has not simply assumed that all .ORF files are equal, and has not noticed that you have a problem.

  • RAW Files problems with 5DMarkIII

    I recently started shooting RAW in my new 5DMarkIII but everytime I try to transfer those files to Aperture 3 it crashes and no file can be transfered to my computer. I have the app up to date and the firmware of the camera is the last one. I have no problems with the JPG files, but the RAW files crashes Aperture and I cant get them on my computer!

    Thanks! and I apologize if my english is not good enough.
    No problem your english is probably better than mine!
    Update: In the last two hours Aperture could transfer a couple of files but I had to do it one by one. Then, I attempted to transfer a whole group of files, it crashed again.
    This looks like just one of your images on the card is defective. Try to import without rendering previews: Turn off the Preference: "Previews > new Projects automatically generate previews" before importing.
    Then create the previews one by one after import. Probably Aperture will crash when you try to render a preview for the defective  image, but then you will know which image to remove.
    Regards
    Léonie

  • Raw file problem with Snow Leopard

    I had the chance yesterday to test Aperture on Snow Leopard (don't ask me how!).
    It is working but my raw files are not rotated automatically!! &*%?&$&?!
    That is really really annoying!
    An old bug that is coming back again!
    Note that the bug is also visible in the Finder or iPhoto. It is not related to Aperture but the Mac OS Raw support.
    My raw files are .arw from Sony Alpha-700.
    But I saw the same bug with raw files from a Nikon D80...
    B.t.w., Aperture is not running in 64bits.

    Leopard allows 64 bit applications, and there are some 64 bit apps available (Lightroom 2, for one example). Tiger actually allowed 64 bit applications as well, but only for non-graphical applications (as the graphical frameworks and other associated application bits were not 64-bit ready).
    Your statement is misleading. People that expect that existing applications will somehow become 64 bit just by running on Snow Leopard are misinformed. They must be explicitly built and compiled as 64 bit applications. Mac OS X allows them to be built as 32 or 64 bit, in the same way that it allows applications to be built for PowerPC, Intel, or Universal.

  • RAW file problem with Nikon D7100

    Ijust purchased a Nikon D7100, and I'm unable to upload and edit RAW files(NEF) in Lightroom 3.6. Nikon provided no help. Can anyone offer a solution?

    Have you downloaded the Codec from Nikon. I use both Windows Vista and Windows 7. I downloaded the Codec of the Nikon D7100 yesterday and installed it and I don't have the latest Capture NX, I have the original I brought shortly after buying my D200. I can now use the D7100 files directly into my Capture NX software. ViewNX gives you the basics of Raw editing but Capture NX gives you the advantage of using the U point system. I found this out purely by accident. If you can download the Codec free of charge and pick up a cheap old Capture NX  you can get all your EXIF data as well as lense data without any issues.. The Camera companies pay Adobe a license fee for using the Adobe Gamma in their cameras so why should they pay more for file format. Adobe is very protective over its intellectual property so why not with Canon or Nikon. They comply with the consumer trade agreements on EXIF and image authentication. Nikon have cameras in Space which is more than Adobe ever dreamt of. So file format has little or nothing to do with compatibility.

  • Olympus E-30 Raw files compatibility

    When will be able Olympus E-30 Raw files compatibility with aperture ?

    Digital Camera RAW Compatibility Update 2.6 doesn't works properly with Olympus E-30 Raw files.
    A 4032 x 3024 file i rendered to a 160 x 120 file.?????
    No problem with Lightroom.
    I try and retry with aperture and my 60 thousands images,excellent with light, color and detail treatment, but with too much problems with image management.............
    Any solution ?
    I have to wait a new camera raw update ?

  • Problems with Lightroom 5.2 and Olympus EM-1 RAW files?

    There have been reports on DPREVIEW of color problems using Lightroom 5.2 with RAW files from the Olympus OM-D EM-1 camera.  This causes  difficulty creating camera profiles, and creates a red shift in Images.  JPG images are unaffected.
    Anyone else seeing this?
    When may we look forward to LR 5.3, hopefully with a fix?
    Thanks............... Jack Winberg

    The read me file from Adobe indicate that LR 5.2 has "preliminary" support for the Olympus EM-1 raw files.
    I would make sure you keep your original raw files so they can be converted when the support is finalized. i.e. I would not convert to dng on import if that is your normal workflow.

  • Error -43  when try playback on win7 64bits over the network QT that recide MacPro  osx 10.5 however i can play with VLC player, This happend when the QT is inside a Folder with name longer 8 chars other files has no problem with long names just the QT

    error -43  when try playback on win7 64bits over the network QT that recide MacPro  osx 10.5 however i can play with VLC player, This happend when the QT is inside a Folder with name longer 8 chars other files has no problem with long names just the QT  nfs sharing

    Never mind, I already found the solution myself.
    What I did wrong was:
    - not copying the master image to the nbi folder
    - selecting the netinstall-restore.dmg image as source to copy to my HD.
    The thing is, when you create a netinstall image for 10.5, the image itself is already included in the netinstall image so you don't have to do anything else.
    With the 10.4 image however, you also have to copy the master image to the NetBootSP0 directory.
    In the *.nbi folder contains an netinstall-restore.dmg file. But that is only to boot you to netrestore, it's not the image itself.
    Other alternative is to copy the images to another folder that you share with AFP and adjust the configuration of netrestore like described in this manual:
    http://www.shellharbourd.det.nsw.edu.au/pdf/misc/osxrestoringnet.pdf
    This manual was also how I figured out that I forgot to copy the image to the NetBootSP0 folder.

  • Anyone know if the long standing duplicate files problem with File History has been fixed yet?

    There are loads of public threads about the duplicate files problem
    with Windows 8/8.1 File History backup system.
    From all the threads I've looked at, there seems to be no solution,
    and no acknowledgement from MS that they can even repro the problem
    (which surprises me considerably as there are so many people who
    notice the problem).
    Is anyone aware of whether MS (may) have fixed this for Win10?
    Are MS aware of the problem and if they're able to fix it?
    Dave - with many GB of duplicated files in File History :)

    Hmm, is that the attitude MS would recommend? :)
    Why would I care what Microsoft would recommend?
    Clearly you don't, and you appear to have missed my smiley. Calm down
    Noel, many of us are as annoyed by aspects of modern Windows as you
    are. :)
    I'm all about making Windows actually WORK/./
    Aren't we all? Windows is software I use too many hours every day, I
    along with many millions of others need it to work really well. You
    are not alone.
    When they implement something that doesn't work, and even if it did work doesn't do what's needed - and/beyond that/ they remove features people DO need (such as the GUI for Windows Backup), I see no wrong in advising people of the way things
    really are.
    File History essentially does work - it's saved me a couple of times
    in the past couple of weeks. It just has a highly annoying habit of
    creating 100% duplicates of some files for no apparent reason. If MS
    have fixed that I won't have any known complaints about it.
    If you don't like it, you don't have to use it. I generally like it, I
    just want to see that its fixed.
    Dave

  • Aperture 3.1.3 and Olympus E-PL2 RAW files

    Hi all;
    I'm using Aperture 3.1.3 on a mid-2010 MacBook Pro 2.66 GHz, 8 gig RAM. OS is OS X 10.7
    My new Olympus E-PL2 RAW files  (.ORF) do not seem to be compatible, despite Apple indicating that they are supported. The corresponding DNG files produce the same error message.  Whenever I try to export or use a plug-in, I get the following message:
    Editing Error
    This image cannot be renedered for editing
    because Aperture does not support the image format.
    Does anyone have any recommendations for fixing this issue?
    Thanks!!
    Tim

    Hi Tim,
    I'm running a similar configuration (hardware and camera) and I'm able to edit RAW in Aperture/Lion. Do you have all other s/w maintainance applied?
    Only problem I've seen since Lion is problems with images not on the MBP, in particular my NAS library is no inaccessible.

  • Sony RX100 raw files converted with DNG converter not recognizable

    Since  installing Maverick 10.9.4 on the Mac, Sony RX100 raw files converted with DNG converter are no more recognizable.
    Somebody else the same problem?

    I know my DNG files themselves and the info they contain are fine. But they're not properly supported in Mavericks 10.9.4 and I don't plan on switching to Windows. A file that I converted to a DNG using Adobe software is now listed as an unrecognized file in OSX. No thumbnails, no iPhoto, no Aperture. Essentially, no support. And this is a problem. A quick search will show you people with various Sony cameras (A7, RX100 mkI and mkIII, at least) having the same problem.
    No matter where the blame falls, the simple fact is that if you shoot with various Sony cameras, use Adobe software to convert the file to DNG and happen to be an OSX user, you're files are no longer compatible with OSX or Apple's photo software. They will only open in Adobe software. You literally get a warning message from OSX saying, this is an unsupported file type when you try and open it.
    Like I said previously, I've had a managed iPhoto library for about 5 years now, numerous hours of tagging and organzing, and every DNG file converted from a Sony ARW RAW is currently unsupported. Original ARW files work just fine. It's nuts. Maybe it's Adobe's fault. Maybe it's Apple's fault. It really doesn't matter. If DNG is not a reliable standard format under certain edge cases (Sony ARW, DNG converter, OSX Mavericks), it's not a reliable standard format at all. I just hope that Apple or Adobe figures this out, so that I can get those photos back.
    In the mean time, certain users such as myself just can't rely on DNG. End of story.

  • I cannot open raw file shot with canon 20d. I get an error message.

    I recently used a 50d camera and shot in raw +jpeg. Downloaded into computer. Was able to view jpeg but was unable to view raw version.At first I attributed this to needing software update for 50d. I brought up a raw file taken with a 20d and the same error message appeared. I could open a 20d file before. This morning I tried again.I did open a 20d file.I tried a 50d file and the error message appeared. Went back to 20d file and the error message appeared saying it cannot open file.I am less than a novice. I purchased elements 6 a year ago and am just starting to try to use it. Are there updates that I need to do .

    sdefr0ghsf wrote:
    Further to my above reply, I have just discovered this on the web:
    Why Adobe doesn't touch proprietary raw files
    Touching the bits of raw image formats that aren't publicly documented well (or at all) seems like a bad idea, bound to end in tears. Microsoft is advising customers not to edit metadata using Vista, saying,
    Microsoft has received reports of compatibility issues with Nikon NEF files after installing version 1.0 of Nikon's raw codec posted in January. Tagging the raw files through Windows Vista or the Microsoft Photo Info tool after the codec is installed appears to cause these files to become unreadable in other applications, such as Adobe Photoshop. [Via]
    I'm sure the problem will get sorted out soon enough, but it does illustrate why Camera Raw and Lightroom insist on using sidecar data files for raw formats other than DNG. It's less convenient, but we've seen far too many conflicts arise from touching metadata in these other formats. DNG was designed with flexible internal storage of metadata in mind, and now Lightroom and Bridge offer conversion to DNG as part of their photo-import processes. (For what it's worth, on my MacBook Pro, converting an 8MP CR2 file to DNG takes roughly 1-1.5 seconds--not a bad price for portability & reduced file size.)
    Posted by            John Nack at 01:47 AM on February 12, 2007
    You will note this this was posed on Feb 12th 2007 and that it appears to still be an issue. Oh dear.
    Sure would be nice to see the link to where you got this.
    This refers to problems using Microsoft software and Vista, not Adobe software and Vista. I believe it is saying that Adobe properly handles both .nef and .dng files. I have no idea how this quote relates to this thread at all.

  • Heavily Jagged Curves/Diagonals on Olympus EP-L1 RAW Files and possibly the whole PEN Family

    Hello everybody
    I have a serious situation here. My Olympus EP-L1 raw files have serious jagged diagonals. It's only visible on sharp curved surfaces. I ran some test on straight sharp diagonals from 45º to 0º but found no artifacts. Here is a comparison between in-camera jpeg and .ORF converted to DNG in Lightroom 3.3, ACR 6.3. BTW, this is visible on .ORF files as well as DNG. I took these photos with RAW+JPEG at full resolution, highest quality.
    Full thread and samples here
    Thanks

  • Help render the raw files edited with camera raw how?

    Hi
    i have a problem
    i use  bridge cs5 (updated) to browse my raw files
    often i open my raw files with camera raw inside bridge cs5 and make some corrections like exposure , saturation , contrast and so on
    but after bridge doesn't re-render the files
    i mean the thumbs ,previews , the slideshow still are in default setting
    when i click and open with camera raw inside bridge or with photoshop cs5 ,the raw files look with corretions
    but again bridge show me not with the corrections
    i run under w7 32bit
    what could be the problem?
    thanks

    mantralightroom wrote:
    i see previews and thumbs with the edits but with a big delay
    thanks
    If you are using HQ On Demand you will get fast thumbnails, but there will be a delay in generating the preview as Bridge builds it.
    The Always HQ takes more space, but faster as the data is already in cache.
    Hope this helps.

  • Lightroom changes colour in my RAW files captured with NIKON D300

    Dear All! Lightroom changes colour in my RAW files captured with NIKON D300. Some of the images are completely ruined. I am sure Adobe must be aware of this problem. What could be done? Is there a solution? Many thanks for your help. Regards, Stanislav

    You want "something different" but this "something different" is quite hard to define.
    I want a result which reflects the result on the camera. Have the feeling the display
    of the D800 is not the greatest, at least (not only the color issue which is often discussed)
    but also the exposure. Often I think I would need to compensate it, but then afterwards
    on the computer the non corrected version looks most of the time better.
    I think its interesting to see how allergic people react when the word jpeg comes up.
    This is also just a rendered result, just by the camera. There are many options in my cam.
    I like the vivid setting with some modifications. And that gives me a result I like.
    And if I like the result, why shall I spend way more time to replicate it?
    I do not talk about that I would want the jpeg, I only say that what I get color wise out of the
    box is how I would like to look at it. I still want the capability to fix for example exposure  in image,
    but I want the base the version I got from the jpeg view (or how the Nikon raw software could do).
    On Lightroom I did not manage to have a profile that looked as appealing to me.
    It also consumes way more time in my workflow to fix all pictures manually and results might differ.
    To work on an image you need a starting point, I do not say the jpeg look is always perfect and
    what I want all the time, but most of the time it is.
    You say yourself you use profiles. So why should there not be a profile which automatically adjusts to the camera settings.
    Its so frustrating to see a look which you like (the preview image when the pic is first accessed) and
    then Lightroom switches to its own rendering which is flat and which I do not like.
    For me its clearly something Adobe and/or Nikon should fix, like the mentioned "auto correct to preview look",
    Nikon profiles/settings/raw-details in Lightroom or for example a Nikon import module.

Maybe you are looking for