Camera Raw 7.3 bad at multicore usage

Has anybody else noticed? But with the 7.3 update my quad core is suddenly down to 60 % CPU useage total, with 7.2 it was a 100 % and therefore faster processing of raw files. (Zenbook with i7 quadcore)
On my main machine I am still struggling with the time acr needs to open an nef file from D800, takes about 8-10 secs (from the raw file preview to actually open in photoshop cs6) thats is a Xeon core 6 (12 virtual cores) with 24 g of ram and SSD`s
But the cores are not used all, and so the total cpu use is also about 50-60 %
The older Cs5 and acr is faster on d800 nef files on both machines due to less corrections done in acr.
Any idea how to go to the ACR 7.2 back?

Thank you for the fast answer!
Checked it again and made a screen shot, CPU load total was 36 % and as you said, seems like some of the virtual ones are not used.
But still 36 % is not good, when you think of, that opening takes 10 secs (from an SSD) and I know timings from similar systems that go down to 4 secs, therefore I am wondering. If you process 1000 of pictures like I do, this makes a difference. Just came back from a 3 month trip to south America for example, a ton of good pictures to process.

Similar Messages

Bridge CS6 bad preview after adjustment in Adobe Camera Raw 7.0

Hi,
when i update camera raw from 6.5 to 6.6 the preview can`t give me right preview only after 1 or more adjustments in adobe camera raw (yes, "Always High Quality"and "Generate Preview-Size Previews").
Image apears and stays like when we open it in camera raw in the first few seconds with the yellow exclamation mark.
Months ago the only solution i found after several reinstals of phoshop, was to turn back to camera raw 6.5.
Now im trying beta bridge cs6 and problem come back for me again.
I use Nikon D3x with 14 bits ~49MB .nef files with Windows 7 64 bits .
Is any one have same problem?And why only in 6.6 (and new camera raw 7.0) and not in 6.5?
Thanks
Arménio Teixeira

When I saved a image to my desktop and wanted to open in Preview so I could do some altra fast tweeks like add sepia and then resaved it came up that I didn't have aothourization to save changes. I then as suggested went to finder - get info - and unlocked the file and entered the desktop password when prompted and closed but it still won't save the changes. I don't want to change it to open as a PS file because it is a JPEG and takes allot of effort when preview cnages under tools color is so efficient. Other suggestions to try?

Update of Camera Raw 7.2 for Photoshop CS6 and Lightroom 4.2 - now Bad color

Did the auto update of Camera Raw 7.2 to Photoshop CS6 and Lightroom 4.2 now the color is green and flat in all images after I save them. I do use a Nikon Camera profile and lens correction. Everything was working fine until the 7.2 update. Now the only way to save correctly is to Save for Web. Where do I match the color/profiles?
Mig

Color Settings are :     RGB     sRGB IEC61966-2.1
                                   CMYK     U.S.Web Cooated (SWOP) v2
Color Management:     All say preserve embedded profile
I had marked the Profile mismatch boxes to see if I got an error message, but I never did, so I cleared them again.
Conversion Options:     Engine     Adobe
                                            Intent     Relative Colorimetric
Advanced Control     Only one checked iis Blend Text Colors using Gamma at 1.45
As far as what settings do I open images with. File > Open and find the file. During the edit process everything looks perfect - only after I save is the file trashed.
Under Preferences: File Handling > File Compatibilty > checked are Prefer Adobe Camera Raw for Supportred files
Everything has been fine for months with PS CS6 & Lightroom 4.2 & Colorchecker software profiles, until the Raw Camera update. And I can still save perfect images as long as I save they with the File > Save for Web.

Adobe Camera Raw - CPU or RAM?

Hey All!
Please read the whole post, but if you want to cut to the chase, my question is: for ACR conversions would I be better off with an (Windows) 8-core system and 6gigs of ram, or a 4-core system and 12 gigs of ram?
I am a professional photographer who, after upgrading to some equipment that spits out serious file sizes, needs to upgrade his computer system. I shoot almost exclusively RAW and I rely primarily on Adobe Camera Raw to convert my files and open them in photoshop. While photoshop performance is a consideration, my biggest concern is to be able to open ACR images ridiculously quick.
Right now, working off 21 megapixel images on my current system, it takes between 10 - 20 seconds to open/convert a single file into photoshop. I'm aiming for a couple of seconds.
My current system (please don't laugh ... I know its bad):
XP 32-Bit
dual-core 2.00GHz
3G DDR2 Ram (with 3G switch enabled)
5400 rpm Hard Drives
Running CS4 and ACR 5.3
Future Set Up Considerations:
Vista 64-Bit
Processor/RAM
a) quad-core-Q9600 3.00 GHz with 8 gigs DDR2 (1150MHz)
b) i7-920 2.66 GHz with 12 gigs of DDR3 (1600 MHz) - adds about $500 to price - worth it?
c) 2 Xeon-quad-core-5530 2.40 GHz with 6gigs DDR3 (1600Mhz) - adds about $1000 to price - worth it?
d) something AMD?!?!
Hard Drives (7200rpm)
2 for images storage (one as an internal backup)
1 For operating system, applications, music, etc
1 For scratch disk
Basically, the question comes down to whether extra cores or extra ram will ultimately make the biggest difference in the ACR performance
During my testing on my (sad) currently system, here are my conclusions (let me know what you think):
Changing the 3G switch to allow the jump from 2 to 3 gigs of ram usage for applications makes no difference in performance
When I am opening up ACR files both cores show 100% usage (will that continue over 4 or 8 cores?)
Photoshop in general seems to be more CPU limited in my case than ram limited (most of the time is says 100% efficiency but things still take bloody long
From some more experienced users, or users who have quad or octa core system or systems with insane amount of ram, I woudl really appreciate your feedback!
Thanks for the long read!
~
Justin

Hey Zeno!
Thanks for the reply.
I would have to disagree thought that it is hard drive limited at this moment. Take a look at my task manager:
It was running about 5% before I started converting pictures, and then as soon as I started converting the pictures, both cores hit 100% (with little gaps between pictures), and then back to 5% after they were done. You can also see the ram alocation being increased with each picture that is opened.
So basically, I am wondering if going to a quad core will have all 4 CPU's hit 100%, thus coming close to doubling the speed. Or if I go i7 then with hyper threading it'll go to 8 effective cores. Or if I go to dual Xeon processors I'd have 8 cores and with hyperthreading effectively 16 cores.
I am wondering if anyone has experience with a quad core or octacore system that might be able to share some insight.
But I would agree that probably for now 6Gs of ram is probably plenty.
I also don't understand when you said:
"same goes with the CPU, the more cores you have the less benefit you get out of adding more of them"
Could you elaborate. Its just that it takes about 15-20 seconds to convert a single file, and space that out even over 50 photos, that is still 15 minutes of wasted time. Just trying to get the best I can without wasting needlessly.
Thanks a ton!
~
Justin

Adobe Bridge in Photoshop - How to install Bridge and camera raw? And what is it all about?

Hi everyone! I am actually in love with this adobe photoshop. I used PSCS2 before, but later on upgraded to CS4. But I feel tired in upgrading to CS5.
One time, I found a tutorial in youtube about camera raw, and would really want to use it. But I was wondering how to install the camera raw. I believe camera raw is a plugin? so I downloaded the plugin here, installed it in my PS. I downloaded a file Camera Raw.8bi and paste it on my C drive - C:\Program Files\Adobe\Photoshop CS4\Plug-ins\File Formats.
I now am very confused, how will I open it? I do not have adobe bridge! After I installed the camera raw, I opened my PS. I clicked the file>then browse in bridge. I had an error, it's "error 2 photoshop11 undefined". Which is what I thought, I might have done something wrong with installing it.
My question is, do you still need adobe bridge installed in order to use camera raw?
If yes, how does it work? How am I suppose to open camera raw?
If no, how am I going to open camera raw without bridge?
And also, where will I download adobe bridge? I cannot find one here for CS4, only adobe bridge for CS5. I am wondering, is it okay to install adobe bridge CS5 and use it with my PS CS4?
I badly need help!

WebDAV (Web-based Distributed Authoring and Versioning) is a set of extensions to HTTP/1.1.
The main difference from FTP as far as I can see is that it allows you to edit documents on a remote web server.
WebDAV was used by the Apple server - MobileMe but is not generally supported by hosting services.
Using WebDAV you can mount a directory locally. This was how iDisk worked on your Mac and you could drag files onto it to upload them to the remote directory.
With WebDAV, a number of users can share a directory which is why its used in local networks but presents security problems when using a remote server.
If you are into file sharing rather than publishing, Dropbox or its new rival SugarSync are more appropriate.

Opening RAW files in Bridge - not recognized as "Camera RAW files"

I would appreciate any help with this as I am frustrated after spending hours trying to figure this out:
I use a Mac OS X laptop
I have a Panasonic (DMC FZ8) camera that I've been taking RAW pictures with. I plug my camera into my computer and try and open the RAW files directly from the camera using Bridge (I have Photoshop CS2)..I have also tried copying the files to a folder on my desktop and opening from there. The problem is that Bridge doesn't recognize my .RAW files as actual "Camera RAW" files and the icons remain as the Preview icon and not actually a preview of the image. If I click on it to open it in Photoshop the "Photoshop RAW Options" come up set on 8 bits and when I open it, it's just a gray screen. I have checked the settings for RAW Camera and the Panasonic RAW files .raw is selected. I have also tried selecting "show only camera raw files" in my window that is open and my .RAW files that are there gray out - so the program isn't recognizing them.
I just downloaded the Plug-in 3.7 Camera Raw and had to create folders for it in Application Support/Adobe/Plug-Ins/CS2/File Formats. the only folder I had was Application Support/Adobe so the rest I created.
I'm now lost as to what I should do next. Nothing I try seems to be working.
PLEASE HELP!

>I plug my camera into my computer and try and open the RAW files directly from the camera
Ouch! Ouch! Ouch!
That is a monumentally bad idea. Transfer the closed files to your local hard drive first.
This excerpt is from a long-gone post by the late, lamented author Bruce Fraser:
Bruce Fraser - 4:17pm Jun 14, 04 PST (#5 of 21)
Opening files directly from the camera is a bad idea for a variety of reasons*, and it most certainly isn't faster than using a FireWire or USB2 card reader.
         Drains the camera battery
         Runs the risk of the software you're using to open the images writing to the card and destroying the format
         Runs a small but significant risk of USB power frying the camera
         Slowest method known to mankind of getting images off a CF or SD card

Adobe Bridge CS4 Not converting camera raw files right?

I run an HP computer with Windows Vista 64 bit and have CS4. We also have a Canon 40D camera and shoot in camera raw format. When I download the images Bridge converts them into usable images. The last two times I've downloaded images, after converting them, Bridge showed a few of them as either not readable at all or with large chunks of the image whitened out. My husband shoots college football games and takes anywhere from 300 to 600 pictures at each game. October 14th was the first time we had problems, 5 or 6 shots out of 250 were showing up as corrupted. This last weekend there were 15 out of 307 images corrupted. Thinking that the card is going bad or we have a problem with the camera, we purchased a card rescue program Sandisk recommends to see if we could recover any of the images. It shows that all 307 images are on the card and in good condition. But, when I ran the recovered file through Bridge there were 31 images that are showing up as corrupted. I'm beginning to think there might be a problem in the conversion process and that it is getting worse each time it runs. Is this possible and if so, what can I do to correct it?
Thanks for any help,
Linda

Thanks Curt for the quick reply.
After a very stressful afternoon it appears that the card recovery program I downloaded just accesses the thumbnails on the card when it previews them, not the actual images. It would have been nice if they told me that before I forked out the money for it, but.... So although it was telling me they were there, they were not. It wasn't until I viewed the files in Bridge that the corrupt images were showing up. It is also showing more corrupt images than actually are. When I view the card in Bridge I'm still seeing the original corrupt images. We are leaning toward a bad battery grip with our camera. He is going to shoot without it the next time he does a game and see if we still have the problem.
Thanks again for your reply.

Bridge CS4 and Multicore usage?

Hi everyone-
I build a new machine a few months ago and am now in the process of reshuffling the hard drives as I underestimated the size of the archive. The current specs of the machine are:
Core i7 920 (stock)
12 GB RAM
Main drive: Seagate 1.5TB 7200rpm 7200.11
Archive drive (new one): 2TB WD Green
Photoshop/Bridge CS4
One area that is particularly slow is Bridge when importing files. Most of the files are from a 1Ds MKIII, so it takes a while to generate previews. The photos get added to the slideshow fairly quickly and the thumbnails are extracted in pretty fast time as well. However, it takes a while for the full res previews to generate. For example, in a directory mix of about 7.5gig worth of 1Ds MKIII files and 1D MKII files, the machine currently takes close to 8 minutes before the previews are generated. I looked at the processor usage once and it never goes over 20%. Thinking my hard drive may be slow since it wasn't a CPU bottleneck, I installed 2 OCZ Vertex drives in a RAID0 configuration, moved the photos and cache onto that drive, but ended up seeing the same performance when the previews were generated. (the files were added to the slideshow and had the thumbnails extracted much faster however.)
My question is does Bridge support multiprocessors like the Core i7? It appears it doesn't based on my results but perhaps there is something wrong with my setup.
Thanks for any help,
Chris

Schlotkins wrote:
One area that is particularly slow is Bridge when importing files.
My question is does Bridge support multiprocessors like the Core i7? It appears it doesn't based on my results but perhaps there is something wrong with my setup.
Thanks for any help,
Chris
Hi Chris,
How are you importing the files?
Bridge and Camera Raw both support multithreaded operations. If you are using the 'Get Photos from Camera...' menu option than you are hitting a non-threaded process. That menu item calls a new process and it is not multithreaded. It's there for mounting peripherals that otherwise don't mount via Explorer and one way for ingesting images from a camera.
If you are speaking of just browsing to files and getting cached data, what setting do you have under Preferences> Advanced? If you have Generate Monitor-Size Previews on, what size is your monitor resolution? And you are not talking about using the Loupe for 100% in the Preview panel, right?
I haven't broken down the overall size to image count; approximately how many images are we talking?
regards,
steve

How to: DNG colors from pentax camera are completely different in camera raw compared to pentax soft

Hi all, i have a problem.
I always used adobe camera raw to manage RAW files. I find it really fast and friendly compared to many other programs (i mean lightroom, pentax digital camera utility, DxO optics pro, Silkypix, etc.). It has no rivals, on my macbook pro it is absolutely faster than others.
BUT i found a lot of differences comparing colors (not just tone, but definition inside an object with similar colors) from a DNG using camera raw vs pentax digital camera utility 4. It is a know problem by pentax people. You can check (without the camera) the problem here (see the colorcheker chart): http://www.dpreview.com/reviews/pentaxkx/page14.asp
I can post examples of what i mean speaking of "definition inside an object with similar colors"...
I always use the "embedded" camera profile in camera raw, finding it more similar to the pentax software. The adobe standard is really different.
Is there a way i can bypass this issue? using pentax digital software is really boring…it's unfriendly, SLOW, with bad light adjustments and interface.
I tried opening the DNG with pentax software and converting it to tiff: the colors are ok, but you lose a lot adjusting light etc.
thank you all

> I don't know anything, and haven't read anything, about the unique characteristics of Pentax DNG files.
firmware in cameras that can create raw files in .DNG format (Pentax, Samsung, Ricoh, Leica) will write so called DNG profile in those raw files (see Sandy's comments) - those profiles are not identical to what Adobe creates to use w/ ACR/LR, but they also can be used by Adobe raw converters (you will get a little different colors)... you can extract those profiles from native DNG raw files for example using Adobe DNG profile editor... in addition, Pentax cameras (modern) can create raw files either in their own PEF format or in DNG format and Pentax suppied software (DCU) can in fact create DNG files from PEF files and unlike Adobe DNG converter DCU will do that w/o discarding any information and it will write Pentax DNG profile in those converted DNG files.

How to open jpg, tiff files in camera raw from elements 10 organizer

How to open JPG, TIFF files in camera raw from Elements 10 organizer.

Thanks for that Damead, I agree with you that Organiser is real pain (there is a total lack of intuitiveness if that is the correct word).
For my own work I use 'Lightroom' for around 90% of the time, only going into PSE10 for the 10% difficult bits the Lightroom can't handle.
I only needed to sort out the JPEG file opening method within PSE10 for some freinds in a small Photo Group that I run in Woodhall Spa, UK. 50% of the 12 members are beginners & a number of them do not have Raw capability on their Camera's, but now they can get their JPEG's into Camera Raw within PSE10 they have the same simple tabular form of adjustment sliders (not as many as in Lightroom of cause) but it gets over the labourious problem of going thru the PSE10's individual tool selection process each and every time since we are trying to get everyone in the Group working with individual Tools rather than the 'Auto' functions. We do this so that they learn what they are doing rather than staying 'dumb&happy' within Auto all the time & they also learn how to get more detailed control for each photo.
Ref. your comments on file handling/usage, I agree with your comments. Its far and away much more preferable to set up a file structure in 'Finder" (or in 'Explorer' if still using Windows) that you understand so you always know how to find the files. Also, I also never ever use the Camera Auto Load programme but physically 'drag & drop' photo files direct from the 'card' into the file system so I always know thier place (ie: they go into the location I want, not that which the Auto Loader wants).
As regards your comment about 'Lightroom', I don't have any problems at all since I just imported the whole of my photo file structure into the Lightroom Library Catalouge and then it automatically shows up on the LHS of the screen, still in that format, so you can search it direct within Lightroom and display all of the photo's in variuos arrangements and sizes; everything is as easy to find as it is in 'Finder' plus of cause you have all the 'Tagging' possibilities to use as well. As you add more new files into the 'Finder' structure, all you need to do in Lightroom is reimport, starting 1 level up from the new files and Lightroom will find the new files that need loading (ignoring the older ones already in the Library at that or lower levels) then 1 click and its done.
Your comments about getting others to follow a set file structure is very pertinant and also applies to evrything else that one ever does apart from just photo work; the times I have had to help others find info/files etc on their PC's because they don' know the location of anything is too many to contemplate.
Regards

Camera Raw 4.0 unusable in Photoshop CS2

If you have Photoshop CS2 and you download the latest RAW 4.0 update, forget about opening any RAW files from cameras produced in the past year and a half or so. As a clever marketing move Adobe has disabled all functionality for RAW cameras once covered under RAW versions 3.0 through 3.7 when using the RAW version 4.0 in Photoshop CS2. Why would they do that, you ask? To sell more software, of course!
The RAW 4.0 update adds only the Panasonic DMC-FZ8, a camera that I recently purchased. But, if I want to view RAW files from this camera I have to upgrade to Photoshop CS3 or buy Lightroom 1.0, and that is exactly what Adobe is hoping. Suddenly my Photoshop CS2 program has become obsolete because in addition I can no longer open RAW files from my Nikon D200. What is so difficult about making the RAW 4.0 plug-in compatible with other more recent Photoshop programs? Absolutely nothing! Adobe cares more about selling new software than they do about customer loyalty. Such a marketing practice is unfortunate and, in my mind, reflects poorly on Adobe's business ethics.

"I think a nice compromise to the ACR things is to design the next full version of upgrade of ACR (in this case 4.0) so that it will work with the last version of Adobe Photoshop (in this case CS2)."
Yeah, ok, here's the problem with that...Mac CS2 required 10.3.9 or above...Win CS2 required Win 2K or XP/SP2...Photoshop CS3 (and Camera Raw 4.0) requires Mac 10.4.8 and Win, XP/SP2 or Vista.
So, you code to the latest APIs of the system (10.4.x, XP/SP2 or Vista) and you are supposed to magically make a plug-in work on older APIs of the previous version of Photoshop? Even though, to progress and advance (and hopefully optimize) you commit to using the new APIs. So, how ya gonna make Camera Raw 4.0 work in Photoshop CS2-disable it for 10.3.9 and Win 2K? Forget about using new API's and suffer through the old ones?
So, you say, well, just keep updating Camera Raw 3.x...ok, for how long? Forever? For 1 quarter? For a year?
So, you got the Camera Raw engineering team (3 guys) taking time away from Camera Raw 4 to re-write code for Camera Raw 3 for cameras that weren't even sold when Camera Raw 3.x shipped...you ok with that? You realize that it will drain resources from new products with new features, but that's ok. . .you want Adobe to support old products even though they no longer sell them.
I suppose in a perfect world, that would be ok. But as a user of the current Photoshop CS3 and Camera Raw 4, I would want the engineers to be concentrating their time and energy working on what they ARE selling right now. Adding new cameras to Camera Raw 4. Adding new functionality to Camera Raw 4.
People have a pretty skewed view of software, IMHO. They drop down bucks for HARDWARE and expect the software to be upgraded forever, for free. There's just as much value in intangible personal property (software) as there is in tangible personal property (hardware). And...it ain't like these shiny new cameras don't come with the camera maker's software...and Adobe STILL provides support for new cameras in old versions via DNG...which, BTW is free...
Big ol' bad Adobe, out there trying to screw their customers...I don't think so. They bend over backwards to do the right things, but of course, to some people, even that's not enough.

Batch Saving jpg from Camera Raw PSE 6 for Mac

I'm running PSE 6 for Mac. I'm shooting in RAW to retain all data from sensor. My work flow is straight forward.
Review photos on CF card and do initial throw away of bad photos.
Download from CF card to Backup drive to preserve original photos.
I upload photos to Bridge, keyword, grade, and copywrite, etc. then open in Camera Raw and process as necessary; exposure, recovery, sharpen, fill-in, crop, fill-in etc.
Select all and do a save (default is .png) to save my changes. Since Camera Raw will not save to jpg format I open in PSE6
My workflow can change here depending on what my end product will be but usually I'll send some photos out to share which is the subject of another post. I can't make the program resize more than one photo for email even though I have all of the photos I want to email selected in the film strip.
Anyway my process for batch saving to jpg is as follows:
Select all of the photos (I will select only those that have been cropped to the same size such as 4x6) in the film strip.
Open File > Process Multiple Files
Fill out the dialogue box (see attachment) and press OK
The next thing that happens completely negates the automated process, I get the Save As Dialogue box for every photo (see attached)
I delete the "copy" text and save
   6. Some of the photos turn out black under preview in finder
   7. When I try to reopen the jpg in PSE6 I get an error message (see attachment)
Any help is appreciated.

love2kruz wrote:
I'm running PSE 6 for Mac. I'm shooting in RAW to retain all data from sensor. My work flow is straight forward.
Review photos on CF card
Stop right there! That's a very bad idea.   You should not be viewing images that are still on the card. Download them to your local hard drive first. Otherwise you run the risk of the software writing to the card and destroying the format.
This excerpt is from a long-gone post by author Bruce Fraser:
Bruce Fraser - 4:17pm Jun 14, 04 PST (#5 of 21)
Opening files directly from the camera is a bad idea for a variety of reasons*, and it most certainly isn't faster than using a FireWire or USB2 card reader.
         • Drains the camera battery
         • Runs the risk of the software you're using to open the images writing to the card and destroying the format
         • Runs a small but significant risk of USB power frying the camera
         • Slowest method known to mankind of getting images off a CF or SD card

Duller colors from Camera Raw to Photoshop: why?

Hello!
I'm opening my Canon 70D RAW files with Camera Raw 8.4.1. After this step, I open the corrected file in Photoshop CC. At this point colors have changed, everything is duller and less contrasted.
See image.
Camera Raw color management: Adobe RGB, 16Bit.
Photoshop color management: RGB: Adobe RGB (prepress Europe 3)
Also, no color proofing is active.
How can I correct this issue?

This is a problem with your display profile. The conversion from source profile to display profile is not the same in these two cases, so a bad display profile can show up this way.
ACR converts from its internal working space, linear ProPhoto. Adobe RGB is just the export color space here, so irrelevant. Photoshop OTOH converts from Adobe RGB.
Recalibrate, and examine your calibrator's settings. V4 profiles and LUT-based profiles have caused problems for some, so try v2 and matrix-based if you have these options. You can also test by substituting a known good profile, which would be sRGB for a standard display, or Adobe RGB for a wide gamut one.

Camera Raw Camera Calibration Tab and 5D Mark III

I don't think that many people do this in camera raw, but it was kind of an important step in my workflow with the Canon 7D before and is just not working the same way with the 5D Mark III now.
In the Camera Calibration Tab (Third from the right side) I always changed Camera Profile from Adobe Standard to Camera Standard or Camera Portrait. This step made the image automatically look better, contrast was better and the highlights look a lot better that way. Of course the "Camera Portrait" option makes the image a lil bit red, like the Picture Style in the camera does. But it was an easy adjustment with the Hue Slider of the Red Channel. Like I already said - really great improvement of the image on the 7D raw files, beautiful highlights, shiny, contrasty and so on... Same stuff worked with 5D Mark II perfectly, too.
Now with the 5D Mark III the "Camera Portrait" option, my favourite one, gets me pretty bad results. The Image is too strong oversaturated, too much red in the skintones and in the shadows, too! Shadow contrast gets worse and I can't control this settings the way I did before with the hue/saturation sliders of the channels. It's too extreme red or it's too yellow, but not something right between this extremes. And the highlights get some green tint, so it's no real optimization of the image overall quality at all, like with the other cameras. I don't know if the support of the 5DMIII is still not up to date... It is not only my camera, I also have asked other photographers with a 5D Mark III and they have the same issues changing the camera profile. Lightroom has exactly the same effect... It would be great, if an Adobe Employee can forward this issues, so that it gets tweaked with the further updates and 5dm3 will work the same way in camera raw like mark 2 or 7D.
Sorry for my bad english

Yes, white balance is another possible reason for mismatch
These rules apply:
- if you use white balance "as shot", then white balance in ACR will be the same as from camera or DPP (in a sense - what is white color in ACR will be white in DPP also). However, color temperature/tint shown in ACR will be probably slightly different than value recorded in exif of jpeg or raw file. It's because in that case, whitebalancing is performed using some metadata in raw file by both ACR or DPP, while temperature displayed in ACR is calculated from that metadat using color matrices in selected profile, according to a formula from one book (as documented in dng sdk), while DPP is probably using some other formula or slightly different color matrices
- the same will happen if you use WB dropper on exactly the same position in the photo by both ACR and DPP
- but, if you use the same temperature preset in ACR and DPP (for instance 5200 K), then white in ACR and DPP will probably be a bit different, because whitebalancing is performed in oposite direction now (ACR calculates RGB multipliers from that temperature and using color matrices in the profile)
I hope this was understandable, although it's a bit complicated

Camera Raw 6.7/LR4.1 photos corrupted

I have Photoshop 5, LR4.1, Windows 7 64-bit, Camera Raw 6.7 and a Canon 5D Mk3.
When I import photos from the camera into LR4.1 some get corrupted with posterised type artifacting. While I quite like this from a creative aspect, it's not what is on the camera! This example is a bad one...my feeling is that it's a Camera Raw bug as it happens when I import using Bridge direct to my hard disk. Adobe may have rushed this version out a bit too quickly?

It's likely to be a hardware issue - Lr doesn't directly touch your files, but it does stress the kit.
Every other example like this (there have been many such posts, and I've had it myself) has been traced to hardware: either failing RAM, or - as in my case - a dying hard drive.
The Bridge dimension's unusal though - let's see what others have to offer about that - but from an Lr perspective this is hardware all the way.
How are you importing the files, incidentally? Card reader? Or USB straight from camera to computer? If it's the latter, please try the former.

Camera Raw 7.3 bad at multicore usage

Similar Messages

Maybe you are looking for