CS5 and Camera Raw Calibration Profiles

Are there no profiles in Camera raws Camera Calibration other than Adobe Standard in CS5 for Sony Cameras. I have the latest version of Camera Raw 6.7.0 which says it supports both my Sony Cameras.

Hello,
Support does not mean it has Camera Profiles, but that the camera files can be opened and developped with accuracy...
It seems that a user has created some : http://www.piraccini.net/2011/02/profili-colore-sony-a900-per-adobe-lr.html
BTW, this is your second discussion on the topic, I just closed the previous one, that suggested, rightly, to ask the question in the Camera Raw forum.

Similar Messages

I redownloaded my Photoshop CS5 and Camera Raw will not accept my RAW files nor will the Adobe Bridge display the picture view of these files. A message displays saying it doesn't support this camera. I have a Nikon 5100 DSLR Camera. It always displayed

I redownloaded my Photoshop CS5 and Camera Raw will not accept my RAW files nor will the Adobe Bridge display the picture view of these files. A message displays saying it doesn't support this camera. I have a Nikon 5100 DSLR Camera. It always displayed them in the past. How can I get it to display these photos in Bridge and open them in RAW?

Adobe - Adobe Camera Raw and DNG Converter : For Windows : Camera Raw 6.7 Update
Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Camera Raw 6.7 Update
Benjamin

Hex core efficiency in Bridge CS5 and Camera Raw 6.0

Conclusion: Batch processing of files in Bridge CS5/Camera Raw 6.0 is limited by an unknown factor which I currently believe to be software design and/or software implementation. While performance on a dual core would be more or less CPU bound, and on a quad core would use the bulk of the available CPU power most of the time, on a hex core machine the CPU is woefully underutilized; i.e. I could be doing the same work in substantially less time.
Suggestion: At the very minimum, allow the option to have Bridge/Camera Raw process N (where we choose N, given that a dual socket motherboard will be able to have 24 cores in the very near future) files simultaneously, so we can tune our own systems for the disk IO vs CPU bottlenecks we each have. At best, automatically keep the CPU(s) running all cores at or near peak all the time, or until you run out of disk IO bandwidth.
Observations taken with the Windows 7 Resource Monitor and the SirReal G15 keyboard applet
Camera Raw Batch actions:
When I select a number of photographs (I typically select scores to hundreds), either fresh RAW files from a Canon 50D or existing DNG's converted with prior versions of Photoshop, and apply some change to all of them (for instance: changing from the 2003 Process with ACR 4.6 camera profile to the 2010 Process with the Camera Neutral camera profile, I see very tiny sections of disk IO (not exceeding 20MB/s on a high end SSD), no hard faults/s in memory, no real network IO, and CPU follows a very distinct pattern, with about .75 to 2 seconds at each of the following CPU levels, in sequence:
18 (one core plus a bit)
70-88 (5ish cores)
18-23% (one core plus a bit)
45-55% (about 3 cores)
repeat
A very important feature for me, Bridge CS5 Preview Extractions on a new folder show 33-45MB/s of disk activity, and a solid, exact 25% (1.5 cores) of CPU with dips to 19% or so. This very clearly indicates that the Preview Extraction feature isn't able to use most of the cores in my processor.
Build: a new build computer (Gigabyte GA-890GPA-UD3H rev1.0, BIOS F6) with an AMD Thuban 1090T 3.2Ghz hex core (running 5% above clock, FSB change to 210Mhz from the 200Mhz default, Prime95 stable for days), with 8GB of DDR3 RAM, and all Bridge, Camera Raw, and Photoshop cache and files running on an OCZ Vertex Turbo SSD. OS is Windows 7 64-bit. OS level page file is completely disabled.

Is it possible you're overwhelming the main memory bandwidth by the fact that you are working on (multiple) large images? Multi-core machines can only work on as much data as they can get from/to memory, and what you're doing is kind of flushing data right through the cache. I'm less familiar with the AMD architecture, but doesn't the concept of 6 cores on one chip mean that they ALL share one main memory buss? This could be a case where given the task, more cores is not better.
It may also very well be that the entirety of Photoshop, which is at its core a relatively old application (architecture-wise), is not programmed to use multi-threading as well as it might be. Getting multi-threading to work right in an application is no picnic. And don't forget, this software is crafted to build and work in two widely different environments (Mac and PC) and so may not be able to use all the fanciest features of any one of those two realms.
-Noel

Disk IO efficiency in Bridge CS5 and Camera Raw 6.0

After watching Microsoft Process Monitor (ex-sysinternals) while processing a large batch of DNG's that in Camera Raw were being converted to a different Process (2010 to 2003) and a different a different Camera Profile, I have the following questions:
Why read files in sequential chunks far smaller than we could? Why not 128KB or 64KB chunks for the DNG header read instead of 4KB? Why not at least 256KB chunks for the main DNG read?   Why not 32KB chunks for the Camera Profiles, if we're going to read them over and over at all?
Why read all the profiles for every single photo, when we can possibly use at most two (the original one, and the new one), and more often only one? More to the point, if we're working on a large batch of photos on a machine with 6GB of free RAM, I would suggest loading them into RAM and leave them there.
Why multiple Create/Close sets on Defaults\Preferences during large batch processing?
Why so many CreateFile...CloseFile sets for the same main DNG file; we're operating on the same file through this process. Why close it when we're just going to open it right up again?
Summary over one file's processing
00:49:58.72 CloseFile A
00:49:58.72 Mess with Defaults\Preferences.xmp
00:49:58.72 CreateFile B
...               ReadFile B in 4KB chucks out to just past Offset 167,936
00:49:58.72 WriteFile B - write 11,187 bytes at Offset 780
00:49:58.72 CloseFile B
...               Mess with some Adobe\CameraRaw\Database CreateFile, ReadFile, CloseFile stuff for very little time.
00:49:58.72 CreateFile B
00:49:58.72 ReadFile B in 64KB chunks out to just past Offset 19,165,184
     00:49:59.12 The last ReadFile; essentially, reading at ~45.84MiB/s for 0.4 seconds
00:49:59:12 Start reading all the CameraProfiles\Adobe Standard\Canon EOS 50D xxx.dcp in 4KB chunks for 55-110KB or so: the order is Adobe Standard, Camera Faithful, Camera Landscape, Camera Neutral, Camera Portrait, Camera Standard,
    00:49:59.13 The last ReadFile for the profiles
00:49:59.13 CreateFile B
00:49:59.13 ReadFile B in 4KB chunks twice, at Offset 0 and Offset 53,248
00:49:59.13 CloseFile B
...               Mess with some Adobe\CameraRaw\Database CreateFile, ReadFile, CloseFile stuff for very little time.
    00:49:59.13 Last CloseFile on the above
??? CPU use, I assume
00:49:59.78 CloseFile B
    ??? The previous operation on B appears to also b a CloseFile. I assume I'm failing to interpret Process Monitor; I must have missed an operation.
00:49:59.78 CreateFile, CloseFile on Defaults\Preferences.xmp - Read Attributes
00:49:59.78 CreateFile Cache\Index.dat
00:49:59.78 ReadFile Cache\Index.dat in 4KB chunks then write it in 4KB chunks, about 24KB worth
00:49:59.78 CloseFile Cache\Index.dat
??? CPU use, I assume
00:50:01.40 CreateFile B
00:50:01.40 WriteFile B in 256KB chunks
00:50:01.42 CloseFile B
00:50:01.43 Another Read Attributes Create/Close set on Defaults\Preferences.xmp
00:50:01.43 CreateFile C
repeat pattern
Total: 2.71 seconds.
The sum of the two long ??? CPU segments: 2.27 seconds
The time not part of the two long ??? CPU segments: 0.44 seconds, or about 20% of the total for that file.
Of that, changing the main DNG file read from 64KB chunks to 256KB chunks could have reduced that 20%, to about .35 seconds. On a batch of 1000 photos, that's a savings of almost 6 minutes. A hundredth of a second here, a hundredth of a second there, and pretty soon you're talking about real time.
Note that SQLIO, with an outstanding IO queue of only 1 (as this appears to generate), with only 1 thread, dealing with only one 4GB file, for 120 seconds, rates the SSD which stores the DNG's at:
4KB: 48.10MB/s
64KB: 173.85MB/s -- much, much faster
256KB: 222.95MB/s -- still significantly faster than 64KB
While my SSD doesn't take up much more time doing the smaller reads, slower or more heavily used drives will make the lower efficiency more visible to the end user, particularly for batches.

I don't know the specifics, but keep in mind this software is built to work on multiple completely different operating systems. There might be some "minimum common denominator" stuff going on.
-Noel

In compatible upgrades CS5 and Camera Raw 7.4

Hi,
I have been shooting with my Nikon D 200 and processing my RAw files thru Adobe camera Raw 6.0 and finishing them in CS5. Just got my Nikon D7100 which is not compatable with Camera Raw 6.0 but is compatible with 7.4 but 7.4 is not compatible with CS5??
I have light room 4 but like CS 5 much better. How can I get Abodobe Camera raw 7.4 if I convert from Raw in that can I bring my image back to CS 5??
What tcan I do to resolve this dilemma
Thanks!

You can get Camera Raw 7.4 by upgrading to Photoshop CS6. It's that simple. The last version of Camera Raw for Photoshop CS5 is version 6.7. You could download the DNG converter version 7.4 and create digital negative copies of your NEF files. Those DNG files will have all of the original raw data in them and you will be able to open those files with Photoshop CS5. But if you are using Lightroom, it has all of the same adjustments that are in Camera Raw. Lightroom will create a TIF or PSD file that contains all of your Lightroom adjustments, and send that file to Photoshop. It's what a lot of people do when they don't have current versions of both Photoshop and Lightroom. It's what I will be doing when Photoshop CS7 is finally released and I can't get any more Camera Raw updates.

Photoshop cs5 and Camera Raw

Hello,
I've just downloaded the last version of camera raw for mac (I've never used CR before !). When I open PS, no CR... In Bridge, I can see it but nothing happens... camera raw is in gray !!
Thanks for your help...

Hi danae830,
In PS.... go to FILE-menu.... OPEN-file....Click on a RAW-file...... then it must apear in ACR.
IF not....... I...... can't help you.... maybe someone else???
-Fred

When trying to update Adobe Application Manager for PS CS5 and Camera Raw 6.7, I get a window stating "unable to install download, please try again later". There isn't an msg error, I can't list my serial number for this product and Customer Service 'sugg

Can I still get updates if I have not bought into the Cloud?

I don't know why you are getting these errors. Try downloading & installing the updates manually from http://www.adobe.com/downloads/updates.html

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images

Any ideas?

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images from Lightroom and choosing the "Render using Lightroom option when it popped up in the dialogue box. She has been doing this for over a year and a half without any problem. Today when she hit Command E no dialogue box appeared and the image just opened in Photoshop. I'm concerned that all of her Lightroom edits are not being rendered to Photoshop. Anyone have an idea as to how we can get the "Render using Lightroom" dialogue back?

Just upgraded to 10.8.4 and now can't open canon raw files in photoshop cs5 with camera raw plug in 6.7

i've just upgraded to os 10.8.4 and now i can't open canon raw files in photoshop cs5 with camera raw plug in 6.7 which worked perfectly prior to the upgrade....anyone else encountered this issue?

Adobe's software is a mess in terms of the fact that it's sprayed all over the place and may not survive an OS upgrade. Try reinstalling Photoshop CS5.

CS5 not responding after opening Bridge and Camera Raw

I have been using bridge, camera raw and cs5 since it was released. I have not any problems until this morning. I am able to open Bridge and Camera Raw, but when trying to open PS CS5, it does not respond?
Any suggestions?

Try resetting your preferences as described in the FAQ.
http://forums.adobe.com/thread/375776?tstart=0
You either have to physically delete (or rename) the preference files or, if using the Alt, Ctrl, and Shift method, be sure that you get a confirmation dialog.
This resets all settings in Photoshop to factory defaults.
A complete uninstall/re-install will not affect the preferences and a corrupt file there may be causing the problem.

My Photoshop, Bridge, and Camera Raw in CS5 will not update. The update downloads and then says there was an error.

I am not able to update any of my CS5 files. Especially, Photoshop, Bridge, and Camera Raw.

Adobe - Photoshop : For Windows
Adobe - Photoshop : For Macintosh
Photoshop: Basic Troubleshooting steps to fix most issues
Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6

Lightroom 3.2 and Camera Raw 6.2 final releases are available

Lightroom 3.2 and Camera Raw 6.2 are now available as final releases on Adobe.com and through the update mechanisms available in Photoshop CS5 and Lightroom 3. These updates include additional lens profiles support among others. Check out http://blogs.adobe.com/lightroomjournal/. Following the example of Adobe's collaboration with SIGMA, leading lens manufacturers such as Pentax, Tamron and Zeiss worked closely with Adobe to create some of the profiles.
-Simon

Excellent! Now if there were only a way to use my S95 in raw... I guess I'll have to wait another few months

Lightroom 3.2 and Camera Raw 6.2 Release Candidate on Available on Adobe Labs

http://blogs.adobe.com/lightroomjournal/2010/08/lightroom-3-2-and-camera-raw-6-2-available -on-adobe-labs.html
with additional lens profiles available.

function(){return A.apply(null,[this].concat($A(arguments)))}
function(){return A.apply(null,[this].concat($A(arguments)))}function(){return A.apply(null,[this].concat($A(arguments)))}Hudechrome wrote:
You have a wild hair about Bridge, Noel?
Not at all. I like good tools, and from everything I read Bridge is marvelous. I don't have anything against Bridge, I just don't need it.
As a computer engineer, I use my computer for WAY more than just Photoshop. As such, I do everything I can to have the operating system (via Windows Explorer) integrate things for me.
For example, via right-click or double-click or drag and drop onto icons:
I access my configuration management system from Explorer (Tortoise SubVersion).
I do searches (grepWin) from Explorer.
I compare things (Beyond Compare) from Explorer.
I start Photoshop and other image tools on raw and processed image files I manage with Explorer.
I start my development tools (Visual Studio and a host of utilities) from Explorer (e.g., double click .sln files).
I access my web sites with Explorer (via WebDrive).
I get file paths from Explorer (right click, Send to Clipboard as Name).
I access office management apps from Explorer (e.g., double click .doc or .xls files).
This is an abbreviated list. Explorer can be a VERY powerful integrator, and is at the center of my computing world at a higher level. So now you can start to imagine why I prefer Explorer for image work.
-Noel

Are Bridge and Mini Bridge and Camera Raw part of PS?

1.) Are Bridge and Mini Bridge and Camera Raw part of PS? OR do they also come with other programs in the Adobe software suite?
2.) What is the difference between Bridge and Mini Bridge?
Thanks.

1.) The Bridge application is included in the Photoshop installer, as well as some other Adobe products.(more info: http://www.adobe.com/products/creativesuite/bridge/?promoid=GWELP). The Mini Bridge extension is only included in Photoshop CS5, and InDesign CS5. The Photoshop Camera Raw plug-in is shared by Photoshop, and Bridge (and is also found in Photoshop Elements).
2.) Bridge is a separate application, whereas Mini Bridge is a panel that's hosted by the Photoshop or InDesign application. Bridge has a fuller feature set than Mini Bridge and can be used by itself. Mini Bridge needs Bridge to create thumbnails, keep files synchronized, and perform other tasks, but operates in the context of the Ps or ID host application (ie. drag/drop multiple assets into working document w/o losing document view).
Online version of Mini Bridge Help: http://help.adobe.com/en_US/creativesuite/cs/using/WS4bebcd66a74275c33c28e88f1235296fe93-8 000.html
regards,
steve

Can I obtain a Camera Raw lens profile for my Fujifilm X100S?

Can I obtain a Camera Raw lens profile for my Fujifilm X100S?

The Fuji X100S uses built-in lens profile supplied in the raw files, themselves, so Adobe applies the profile automatically and it cannot be turned off.
There is no indication of the profile being applied in Lightroom but the recent versions of the Camera Raw plug-in for Photoshop will indicate that a built-in profile is being used:

CS5 and Camera Raw Calibration Profiles

Similar Messages

Maybe you are looking for