Problem loading large DNG images with Camera RAW!

Hello,
When loading large DNGs with Camera RAW 4.4 (for example, DNG dimensions are 9984x6656) CS3 says "cannot open the image because this is not a right kind of a document". EXACTLY THE SAME file is loaded without a problem using Camera RAW 3.7 and 4.0 (did not test other versions). Have you specially prevented loading of large files? Wouldn't it be better to provide this as an option? It's a real disappointment - new version of plugin CANNOT do the thing that older versions CAN. (Simply using older version is not an option, as I need to load RAWs from new cameras, like Canon 450D).
Dear Adobe, please correct this problem :)

It might be wise to give some insight like how the DNG was created, by what version of what software, if ACR is hosted in Photoshop or Bridge... What platform you are using, how much RAM, memory allocation, etc.

Similar Messages

Photoshop stuck when opening image with camera raw after updating it

Hi!I need help guys.I updated camera raw to 6.1 (i have cs5);now in camera raw preferences i specified to automatically open every jpeg and tiff files with settings (i don't know what is the english language equivalent of that option) and if i try to open a jpeg now after the update photoshop gets stuck and i have to close it via CTRL+ALT+C
Some help??

Ok, so this is actually a Wacom driver problem( I'm using Intuos 4). If I turn off windows ink in Wacom driver settings then my sliders in camera raw become responsive again, but I lose pressure sensitivity in PS. Just updated Wacom drivers, but no joy. Anybody have a work around/fix?

Problem opening photos with camera raw 7.1 with Photoshop CS6

I am using Windows 7 32 bit system with 4GB ram and graphics accelerator.
I have Photoshop CS5.1 installed in the same system at it works perfectly.
What happens is when I use the B+W function, I get an error message saying that I have not enough ram.
After that, when I open the next photo with Camera Raw, the raw image will not open.
I have already maximised the Ram that Photoshop can use to 1.7GB and there is more than enough space in my scratch disk.
Anyone can tell me what the problem is?

Hi Noel,
Thanks for your reply.
Just to clarify.
I applied B+W layer adjustment on my photos. It is part of an automated set of actions which I apply to all my photos. I adjust the B&W layer to 50% overlay. When I click on the B&W adjustment layer, there is an error message that tells me I have not enough ram. Once that happens, when I open the next photo in raw, I don't see the new photo but only the frame of the camera raw though which I see my photoshop desktop.
It doesn't occur with the first few photos. But by the 3rd or 4th it happens.
I will adjust it to 50% and see what happens.
Leslie

Trouble converting RAW files with Camera RAW/DNG - CS4 Mac

Hello!
I am using CS4, with Camera RAW 5.7 and Adobe DNG 5.7. These are the versions listed as compatible with CS4. I am using a new Canon Powershot S100. Can I use newer versions of the RAW/DNG with CS4, or am I just out of luck? Please help!
caroline

Same story we hear again and again.
New camera, old software, and the often un-stated expectation that the software company should go out of its way to provide new camera support for free. First thought by those in the know is "you bought a new camera, why do you feel you don't need to buy new software to go with it?"
Those same folks who bought a new camera might never consider asking a camera manufacturer to make their new camera compatible with their old software. It's a funny disparity.
Adobe walks a tightrope of expectations. As it turns out, when you download the latest free DNG converter version they actually DO provide new camera support for free - it's just that converting to an intermediate file format is not quite as integrated or convenient as using the latest version of Photoshop with native support for that camera to just open the files directly. Nor do you get the SIGNIFICANT improvements in image quality that the newer converters provide.
Use the DNG converter, but if you care about your image quality you'll consider upgrading Photoshop. They really have made strides in raw conversion.
-Noel

I have downloaded Adobe camera raw 8.4 so that I can open raw files with pictures taken with the Sony a6000 camera. However it is not opening the images in camera raw. What can I do?

I have downloaded Adobe camera raw 8.4 so that I can open raw files with pictures taken with the Sony a6000 camera. However it is not opening the images in camera raw. What can I do?

Close and restart Photoshop if you have not already done so.
In Photoshop, go to the Help - About Plug-in... menu then choose Camera Raw. What version does it say there?
-Noel

PSE 10 from Apple Store problem with camera raw 6.7 upgrade

PSE 9 was not opening Nikon d4 raw files so I've purchased PSE 10 at the Apple Store and installed on my Mac. PSE 10 is still not opening d4 raw files (camera raw 6.5). I tried to update to 6.7 taken from Adobe but did not succeed to install it. Could you please advice what to do?

Thanks for your help. It works !!!
Bartek A
Wiadomość napisana przez Barbara B. w dniu 17 maj 2012, o godz. 00:34:
Re: PSE 10 from Apple Store problem with camera raw 6.7 upgrade
created by Barbara B. in Photoshop Elements - View the full discussion
You will have to do the update manually for the app store version. Instructions are here:
http://forums.adobe.com/message/4106477
(that's for 6.6 but the steps/file paths are the same for 6.7)
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4414265#4414265
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4414265#4414265. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Elements by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Problems with Camera Raw 6.7 after upgrading to OS 10.8

I've been using Photoshop CS 5 with Camera Raw 6.7 on my MacBook Pro with no issues until I recently upgraded to OS 10.8. Now my Canon CR2 files (shot with a Canon G15) won't open. Does anyone know of a solution or work-around for this problem?

thanks for the prompt response...i appreciate it. according to the link you listed, that's correct. the strange thing is that prior to the upgrad to mac os 10.8.4, photoshop CS5 was working just fine and i was able to open my canon raw files with my current camera raw plug-in version 6.7 which adobe has indicated is the last camera raw update they'll be offering for cs 5
so it's clearly an issue related to the "upgrade" of the os. seems like every solution creates 6 new problems...further evidence for the notion that if it ain't broke don't fix it! thanks again.

Problem with Camera Raw update in Elements 11

I need to update the raw plug-in in elements 11, but when I go to the update section, I just keep getting an error message (which says server busy or might be prevented by firewall). I suspect that my firewall is stopping the updates, but I don't know how to over-ride this. Can anyone explain it please? (I have managed to 'allow' certain things on the firewall, but for this update, I don't know what I'm looking for to 'allow'!

I know nothing about Photoshop Elements. But, according to this list, Photoshop Elements can only work with Camera Raw through version 8.0.
Camera Raw-compatible Adobe applications

Starting an action by opening an image in Camera RAW

I am currently using Adobe CS3 Design Premium with Windows XP Pro as the operating system. The computer is a self build and has 2GB of RAM, 450GB of onboard HD storage and 6x500GB of external HD storage.
As a photographer I frequently end up with anything between a 100 and 300 RAW images after a days work and convert them to DNG, Tif and JPEG files.
With CS2 I ran an action which opened the image in Camera RAW which then enabled me to make adjustments before opening the image in Photoshop and completing the other elements of the action. Since upgrading to CS3 I have been unable to create a similar action and having read the "knowledge based" information and looked through the topics in the forum have failed to find anything that is of help. As each image and the conditions under which it has been taken differ it is quite important to make corrections in Camera RAW before completing the action in Photoshop and fixed settings applied by Camera RAW would be inappropriate.
It is always possible that I am making a fundamental error in writing the action but given my previous experience it seems unlikely. Incidentally I usually bring up the images in Bridge and then select the best images to process and start the action from Bridge.
I should be very grateful for any help in resolving this problem

>It is always possible that I am making a fundamental error in writing the action but given my previous experience it seems unlikely. Incidentally I usually bring up the images in Bridge and then select the best images to process and start the action from Bridge.
there's your problem...when you start the action recording from Photoshop you'll need to actually open a raw image FROM Photoshop not from Bridge. Don't know if this changed from CS2>CS3, but that's the only sure way of recording an open function...from within Photoshop. Then in the Batch you'll still need to override open so the open will open the image with the parameters already set in the image.

Bridge crashes with camera raw 4.4.1 installed, OK with 4.0

When I use Bridge with camera raw plugin 4.4.1 installed to navigate to a folder with at least one raw image shot with Sony Alpha 100, it consistently crashes. I can open the same image using Photoshop and Camera raw without a problem, so the image is not corrupted. Bridge works as expected with raw files from Sony Alpha 700.
If I revert to camera raw plugin 4.0 it works like a charm for Sony Alpha 100 pics, but my new Sony Alpha 700 is not supported.
I have tried using a clean user account, with no caches at all so that can not be the problem. I'm on a MacBook Pro with OS 10.5.3 and CS3.
Here is an excerpt from the crash log, showing that it is indeed the camera raw plugin causing the trouble:
Process: Bridge CS3 [802]
Path: /Applications/Adobe Bridge CS3/Bridge CS3.app/Contents/MacOS/Bridge CS3
Identifier: com.adobe.bridge2
Version: 2.1.1.9 (2.1.1.9)
Code Type: X86 (Native)
Parent Process: launchd [604]
Date/Time: 2008-06-26 08:35:41.310 +0200
OS Version: Mac OS X 10.5.3 (9D34)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000008
Crashed Thread: 10
Thread 10 Crashed:
b 0 com.adobe.CameraRaw 0x19849da3 0x196a6000 + 1719715
1 com.adobe.CameraRaw 0x1984a976 0x196a6000 + 1722742
2 com.adobe.CameraRaw 0x1984b775 0x196a6000 + 1726325
3 com.adobe.CameraRaw 0x1984cefc 0x196a6000 + 1732348
4 com.adobe.CameraRaw 0x19982638 EntryFM + 965714
5 com.adobe.CameraRaw 0x1978dd45 0x196a6000 + 949573
6 com.adobe.CameraRaw 0x196ed798 0x196a6000 + 292760
7 com.adobe.CameraRaw 0x1978e63b 0x196a6000 + 951867
8 com.adobe.CameraRaw 0x196eec2b 0x196a6000 + 298027
9 com.adobe.CameraRaw 0x19733a15 0x196a6000 + 580117
10 com.adobe.CameraRaw 0x19926a19 EntryFM + 589875
11 com.adobe.CameraRaw 0x19927271 EntryFM + 592011
12 com.adobe.CameraRaw 0x19921b15 EntryFM + 569647
13 com.adobe.CameraRaw 0x1979c1fb 0x196a6000 + 1008123
14 com.adobe.CameraRaw 0x198df7bd EntryFM + 298455
15 com.adobe.CameraRaw 0x198e1c37 EntryFM + 307793
16 com.adobe.bridge2 0x00420a35 ThumbMetaLib::CameraRawFormat::ReadDraftThumbnail(ZFileSpec const&, ThumbMetaLib::ThumbnailMetaInfo&) + 243
17 com.adobe.bridge2 0x003fc2d9 ThumbMetaLib::FBFormatReader::ReadDraft(ThumbMetaLib::FBFileFormat*, ZFileSpec const&, ThumbMetaLib::ThumbnailMetaInfo&) + 89
18 com.adobe.bridge2 0x003f3d61 ThumbMetaLib::MakeDraftFromFile(ThumbMetaLib::FBFileFormat*, ZFileSpec const&, ThumbMetaLib::ThumbnailMetaInfo&) + 207
19 com.adobe.bridge2 0x0051962e vio_timeout + 78060
20 com.adobe.bridge2 0x005e3470 vio_timeout + 905006
21 com.adobe.bridge2 0x005e8ebf vio_timeout + 928125
22 com.adobe.bridge2 0x00523699 vio_timeout + 119127
23 com.adobe.bridge2 0x003c5704 Mondo::CThread::EntryProc() + 18
24 ...ple.CoreServices.CarbonCore 0x9424955b PrivateMPEntryPoint + 56
25 libSystem.B.dylib 0x970036f5 _pthread_start + 321
26 libSystem.B.dylib 0x970035b2 thread_start + 34
Any ideas to resolve this is greatly appreciated!
Torbjørn

I'm still looking for some help.
Now that I've learned a little bit more, let me try to restate my problem. In using both a Nikon D200 and a new Nikon D300. For software I'm using PS CS3 Extended Edition, as a part of Adobe's CS3 Design Premium suite. My Dell Inspiron 530 is running Vista Home Premium.
As I've said before, my problem is that I cannot open NEF files shot with either the D200 or D300 (and they are uncompressed NEF files). I downloaded the new Camera Raw plug-in, ver. 4.3.1, and unzipped it to \program files\common files\adobe\plug-in\CS3\file format. The Camera Raw.8bi file is dated 11/30/07 and is about 10,446,000 in size. Then I run a search of my hard drive to make sure there are no other Camera Raw files anywhere. Then, in PS Bridge, I purge the cache of the file folder where the NEF files are located. Then I try to open a NEF file and get the following error message in a PS CS3 Extended box:
"Could not complete your request because it is not the right kind of document."
Then, immediately afterwards I ran another search of my hard drive, and the Camera Raw.8bi file is GONE, DISAPPEARED, VANISHED.
Is the problem with the CS3 Entended Edition?
Can anyone help me out here, particularly you Nikon shooters?
Thanks for any advice.
Bob

Possible GPU Issues With Camera Raw 6.6

Over the past day on my Windows 7 x64 workstation I've done some updates. Specifically:
The Adobe updater brought in Camera Raw 6.6, replacing 6.5.
I updated the to the ATI Catalyst 11.12 display driver version from previous version 11.11.
I allowed Windows Update to apply the dozen or so changes that were pending.
I was just doing some OpenGL testing with Photoshop CS5 12.0.4 x64 and I noticed that under some conditions I saw Photoshop drop out of OpenGL acceleration. Specifically, when I opened a Canon 5D Mark II image through Camera Raw I saw subsequent operations stop using OpenGL acceleration even though the checkmark remained in the [ ] Enable OpenGL Drawing box in Edit - Preferences - Performance.
What I did to determine whether OpenGL acceleration was enabled was this: Select the Zoom Tool, then click and hold the left mouse button on the image. When OpenGL is enabled, I see a smooth increase in zoom. When it goes disabled, I see only a jump in zoom level after letting up the mouse button. Also, the [ ] Scrubby Zoom box gets grayed out. As I mentioned, even in this condition, a check of Edit - Preferences - Performance still shows OpenGL enabled.
Just as a control, I saved the converted file as a PSD, and every time I opened THAT file (with a fresh copy of PS CS5 running) and did the same operations I could not reproduce the failure. The difference being I did not run Camera Raw.
Since I wasn't specifically looking for issues with Camera Raw, I am not sure that the problem occurred every time I did run Camera Raw. I do know that when I open images from my own camera (40D; I do not own a 5D Mark II) that the problem doesn't seem to occur. Notably I always open my image from Camera Raw to the largest possible pixel size - 6144 x 4096, as I did with the 5D Mark II image, so it's not an obvious size difference that's leading to the issue. Given other comments of late, I'm wondering if it could be a specific issue with conversions of files from 5D Mark II.
Nor am I sure whether any of the above updates caused it - it might done this before; I don't regularly convert 5D Mark II images. I DO think I would have noticed Photoshop reverting to GDI operation before, since I just noticed it pretty easily, but I'm not completely sure of that either. I do use OpenGL-specific features (such as right-click brush sizing) pretty often.
I'm trying now to find a set of steps with which to reliably reproduce the problem now, and will advise.
-Noel

Figures. Now I can't reproduce the problem at all, even after an hour of testing. It probably had nothing to do with Camera Raw.
I wonder if there are latent GPU status indicators and config values stored by Photoshop based on its specific environment that might not be right for the first run (or first few runs) after a display driver update. Hm....
-Noel

Can't open NEF with Camera Raw from Bridge

I recently updated to CS6 and got a new Nikon D600. Downloaded the lastest DNG converter but when I pull up files in Bridge I can't open them with Camera Raw anymore. My process was to open in Bridge. Select the NEF files I wanted then click mouse+control, which gave me a menu to open in Camera Raw. Now my only option is Photoshop CS6. I downloaded the trial for Photoshop CC and Bridge CC but still can't select to open with Camera Raw.
What is going on? I have never had issues like I have been. HELP Please.

From your description it sounds as if Camera Raw isn't installed, or is installed incorrectly. In Photoshop go to Help/about plug-ins/Camera Raw and verify that you have it installed correctly. Since you are on a Mac, I cannot advise as to where it should be installed.
The other thing I have been thinking about in your situation is, how were these images downloaded from your camera?if you used an older version of Nikon Transfer it can alter the files so that they cannot be opened in Camera Raw.
Do you have other software like ViewNX2 or CaptureNX2, and will those programs open your files?

Bridge NEF view - selected image altered - Camera Raw issue?

I use a Nikon D700 and CS3 Bridge on a MAC OSX 10.4.11, and when browsing NEF images in Bridge there is an action performed on the image whenever I click on it. I use the settings where a filmstrip is along the bottom and upon selection a larger image appears above. Initially the image appears as I recall exposing it and looks balanced with good saturation, but after selection the image brightens and loses saturation after a few moments. When I open the image in Camera Raw I find that the Brightness is set at +50 and the contrast is set at +25, and the Blacks slider is set at 5. When I reset those parameters to zero I do not recover the look of the image as it was before selection in the bridge window. In order to do that I have to raise the saturation, decrease the brightness and do a fair amount of work to get back to the way the image appeared in Bridge prior to selection. Can anyone tell me what is happening to the image in bridge and how to keep the image from changing after I select it, or at least how to find the settings that have been evidently applied to the image? If I right click on the thumbnail first, I find that the image will open in camera raw without any changes being made in Bridge, so I was able to make jpegs that show the difference between the two images. The first image is as it appears before selcting the thumbnail, and the second is the image in camera raw. If I were to have selected the image normally with a left click in Bridge, the photo as you see it in camera raw would have appeared in bridge and not been recoverable to its earlier state. Can someone help me undertand what is happening here? How can I find out what Bridge or Camera Raw is doing to the images and retain the appearance as it first appears in Bridge? Thank you for your help.

This is a common question.
What you see first in Bridge is actually a JPG which the camera has embedded in the NEF, and uses all the camera's color settings (contrast, saturation, etc.). Once you select the NEF, ACR (Adobe Camera Raw) attempts to render its own preview of the NEF. Because ACR does not understand the camera's color settings, it gives you its default rendering, which usually is somewhat different than the camera's.
In newer versions of ACR (5.x), Adobe has profiles which mimic the camera's presets ('Standard', 'Vivid', etc.) and can be applied automatically in Bridge. Unfortunately, you will need CS4 for this version of ACR (and these profiles have some issues of their own, e.g. http://forums.adobe.com/thread/479960?tstart=0). You can also create your own ACR presets to more or less emulate a particular look (I believe you will need CS4 for this as well).

Cannot open DNG files in Camera Raw hosted by Bridge?

I used Adobe DNG converter on a batch of NEF files (D300). The conversion was successful and the .dng files show up in Bridge with the right preview. However, when I double-click on any of these files, it launches Photoshop and opens the file in CR hosted by Photoshop. This in spite of having my preferences set to "Double Click Edits Camera Raw Settings in Bridge" in the Bridge preferences. Furthermore, a right-click (or control-click) on the file's thumbnail shows the Open With... item only has "Open with Adobe Photoshop CS3 (default)", and not the option to "Open with Camera Raw" that other RAW files have. Interestingly, if I do some editing in ACR, and click on "Done", then, right-click on the thumbnail, the missing options in the Open menu in Bridge re-appear!
I don't think this was happening before. Is this the expected behavior, or am I missing something?
My setup:
Bridge 2.1.1.9
Camera Raw 4.3.1
My computer:
Model Name: iMac
Model Identifier: iMac6,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 2 GB
Bus Speed: 667 MHz
Boot ROM Version: IM61.0093.B07
SMC Version: 1.10f3
Regards,
Rafael

Problem solved. I had to delete the preferences file (resetting preferences by pressing the required keys when launching Bridge did not solve the problem).
I am glad I learned that trick by visiting this forum!

Pentax K-x calibration with Camera Raw 3.1, and calibration updates

The Pentax K-x will save its raw files in either DNG (Adobe) format, or PEF (Pentax) format. Until Camera Raw 3.1 was released, I had my K-x writing DNG files, since there was no support in Apperture for PEF files. With Camera Raw 3.1, the K-x is now explicitly included, so that I could switch to PEF format.
My initial sense after doing that was that the PEF files were coming in darker than the DNG files had. But when I switched back to DNG, those were darker than I thought they should be, too. Since I had DNG files that had been processed with Camera Raw 3.0, I went back and made new versions, processing those with Camera Raw 3.1. Those, too, were much darker than the same files processed with the earlier raw developer. For examples, this picture is from a K-x DNG master processed with Camera Raw 3.0, while this picture is from the same master, reprocessed with Camera Raw 3.1. I've embedded the histograms shown in the inspector in each. Each of those has no adjustments applied. The JPEG image produced in camera (I shoot Raw+JPEG) is much closer to the brighter 3.0 image than the darker 3.1 image.
I've seen one other report of similar behaviour with K-x images in here, but that took the approach that the solution was to revert to Camera Raw 3.0, for now, at least. I hate to move backward, particularly if it locks me out of any future updates. So, does Apple have a history of recalibrating cameras that they've already released Raw support for? Might this change in a future Camera Raw update, or is this likely to be what they alway render for the K-x?
I can get the new style images looking okay (in fact, they seem to have better noise characteristics) with a good deal of adjustment, but not if I confine my adjustments to the Raw Processing brick. There, Boost and Hue Boost are both maxxed out by default, already. If I add adjustments in the exposure brick, and maybe a few others, I can probably get a general set of adjustments that will work as a default for this camera, but how common is it to have to do that?

Aperture 3 mostly seems to work fine for me, at the moment. There were some issues with importing my iPhoto Library that I've mostly worked out, and some quirks that were fixed by the 3.0.1 update. I'm not saying it's all better, but it's not the doom that one might imagine reading some of the threads here, either.
I only had the trial version of Aperture 2, though. I only got the K-x in late December, and before that, I had no need for raw processing. The software Pentax supplies is UGLY, though, and iPhoto wasn't cutting it, so I tried the Aperture 2 trial and the Lightroom 3 beta. I concluded that I much preferred Aperture to Lightroom, but I wasn't going to buy Aperture 2 when all the speculation was that Aperture 3 was right around the corner, or not coming at all. Since my Aperture 2 trial had run out, it wasn't a hard choice to buy Aperture 3 as soon as it came out. I do find I use the editing brushes more than I imagined I would, and I'm very happy that it now directly supports my camera - I've switched to shooting PEF raw instead of DNG raw.

Problem loading large DNG images with Camera RAW!

Similar Messages

Maybe you are looking for