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

Similar Messages

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

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.

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.

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.

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.

Accessing raw file taken with Canon Powershot G16 using Elements 11

I own adobe photoshop elements 11, which I have used successfully for the past 18 months or so with my Canon Powershot G15 camera. I recently upgraded to the Canon Powershot G16 but was disappointed to find that elements 11 does not recognise the raw files taken with the G16. I have tried various intenet forum fixes to no avail. I would rather not go to the expense of purchasing Photoshop Elements 12 to remedy this shortcoming, particularly as Elements 11 more than meets my current photoediting needs. I would be grateful for information on any patches etc that might allow me to access raw files taken with the G16 without have to resort to purchasing Elements 12.

after much consternation I have discovered that the problem is APERTURE. Despite claiming that the program is compatible with the G16 RAW files it really is NOT. I had to download Canon's own photoediting and viewing software....and guess what no problem at all editing, viewing any of the files.
I tried them in Lightroom too and guess what...no problem at all!
So although Aperture has been like an old friend it is time to say bye bye and make the big trek over the Lightroom!
Sad but relieved.

Hi, I've just purchased and installed an upgrade from Lightroom 4 to 5. It doesn't seem to handle raw files authored with a new Nikon D750 camera. I spoke to the sales rep about this and he gave me a link to the 8.6 DNG converter page with instructions

Hi, I've just purchased and installed an upgrade from Lightroom 4 to 5. It doesn't seem to handle raw files authored with a new Nikon D750 camera. I spoke to the sales rep about this and he gave me a link to the 8.6 DNG converter page with instructions to download. 8.6 only works with Mac OS 10.7-10.9, according to the page. I'm running Yosemite, Mac 10.10. Please can you tell me my options? Lightroom 4 worked beautifully with my older cameras' raw files so I would like to continue using the application. What should I do? How soon will Lightroom 5 be able to deal with raw files from a D750. Many thanks, Adam.

Until the next version of Lightroom is released, you need to use the DNG Converter version 8.7RC to convert your RAW photos to DNG and then import the DNGs into Lightroom.

I am unable to import Raw files taken with my new camera Canon SX60HS.

I am running Elements 12, I have just downloaded and installed Adobe Camera Raw v 8.7.1 as it indicates that it supports raw files taken with this camera model. I continue to get the error that nothing imported as it did not contain supported file types. Do I have to do something further to connect this ACR program to Elements in order to have it work or am I missing something else.

The SX-60 HS requires ACR 8.7, and PSE12 is only compatible up to ACR 8.5, so you’ll either need to upgrade Elements or use the DNG Converter 8.7 or newer to convert a folder of raw files to DNG files, and then those DNG files will open in your older ACR.
You can get the DNG Converter from here: http://www.adobe.com/downloads/updates/

Why can't I open RAW files taken with my Nikon D3200 in Elements 10?

Is there a fix in the works that will allow me to open RAW files taken with my Nikon D3200?

Actually the 7.1 camera raw update covers the D3200, but for whatever reason adobe has denied users of pse 10 that update.
Maybe it will still be released, but to me something else seems to be up, because in the past the latest version of elements (at least on windows) was always updated
to the latest version of camera raw at the same time photoshop was.
In the meantime you could download the 7.1 DNG converter to convert your files to dng copies which will then open in pse 10.
windows:
http://www.adobe.com/support/downloads/detail.jsp?ftpID=5389
mac:
http://www.adobe.com/support/downloads/detail.jsp?ftpID=5388
I know this stinks, but other than using the camera makers or aftermarket raw programs (lightroom), that's the best i can suggest for now.

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

Can you export a raw file photo with Lightroom adjustments attached?

Can you export a raw file photo from Lightroom with Lightroom adjustments attached in some way? If not what is the equivalent? There are some individuals I would like to send the full data of the raw file, but with the non-destructive Lightroom adjustments layered on top.
--Gerry

You can select "Original" as the file type, in Export. This saves out a copy of the imported source file into the selected location, labelling the current adjustments onto that image. When this is sent to somebody and imported to LR / opened in ACR, these metadata will be found and used automatically, with the exact same outcome as within your own LR Catalog - provided the LR / ACR versions are sufficiently compatible, and provided camera and lens profiles applied to the image, are present in both contexts.
LR uses whatever method is normal when writing metadata, for each file type involved. So, if one imported file is a proprietary Raw file, LR will write an XMP file alongside. If another is capable of having metadata written into its file header, LR will do that instead.
One important difference between doing this, vs writing LR metadata out to your original imported file, and sending that: the Export Original method will work in the same way, just as successfully, for one or more Virtual Copy versions (duplicating physically as needed), as it will for the primary Master version - relating to a given imported file.

How do I open raw files taken with Canon 70D. Not supported in Elements 12. Is there a download? Thanks.

How do I open raw files taken with a Canon 70D? Elements 12. Version 8.0 Windows 7 64 bit. Thanks in advance for any help.
JWT
Lamar, CO

Thank you so much for you quick answer. Works fine, now. Thanks again, Barbara.
JWT

RAW Files problems with 5DMarkIII

Similar Messages

Maybe you are looking for