Bridge CS3 and Camera Raw

Hello, I have Bridge CS3 that came with Adobe Web Standard that I bought when I have doing web design. I also have Photoshop CS that I use for my camera digital editing. At a camera club today they were using Bridge and Photoshop CS5 to show what it can do. The man completing the demo said that Camera Raw was inbuilt into Bridge and that I should have it. I've been using Adobe DNG convertor for my RAW editing as I didn't know nothing about Camera Raw but seeing it in action and how much better it is over the DNG I want to use that instead.
I've searched high and low for Camera Raw on my PC but I cannot find it. I've tried downloading it from here but it says No and to quit.
My RAW files have the .DNG extension if that makes a difference.
So, am I missing Camera Raw and if so, how can I get it :?:
Thanks

You can download the latest update of ACR for your software version here....
http://www.adobe.com/support/downloads/product.jsp?product=39&platform=Windows
After you click on the version you want it will take you to a page with installation instructions.

Similar Messages

IView Media Pro erases adjustments and ratings in Bridge CS3 and Camera RAW 4.2

OUCH! I seem to have lost about a day's worth of work. I rated and adjusted my Canon cr2 RAW files using Bridge CS3 and ACR 4.2. Then I used iView Media Pro 3.1.3 to add keywords. When I opened the files back up in Bridge CS3, my ratings and adjustements were gone. Actually, when I open the sidecar files in a text editor, I can see the adjustments, but ACR and Bridge can't read them. Anyone else seeing this? If so, how do you fix it or work around it???
Edward McCain
Tucson, AZ

Have you tried purge cache for folder?
iView Media Pro is now Expression Media 1, maybe this 'upgrade' works for you.
You know that you can add keywords and sets in Bridge as well?

Mac computer: New Nikon d300s, CS3, and Camera Raw

I just purchased a Nikon d300s. I had a Nikon d50, Mac, iPhoto, CS3, and Camera Raw 4.6.0.30. With Nikon d50, no problem opening an image from iPhoto into Camera Raw/CS3. With the new D300s, the image opens into CS3 but does not open into Camera Raw. Do I have to buy CS4?

No, you do not have to. You can alternatively use the DNG Converter, which will process your D300S NEF files into DNG files, which can then be opened in CR 4.6 in CS3. The latest version of the DNG Converter, which supports the D300S, is currently in Release Candidate phase and is available here:
http://labs.adobe.com/wiki/index.php/Camera_Raw_5.5
Eric

Bridge CS6 and Camera Raw

I am unable to open jpegs into camera raw through Bridge CS6. Camera Raw preferences are unavailable. I am using OS 10.9.2.

Did you recently update to camera raw 8.4?
If so, you need to replace the existing camera raw 8.4 plugin with the one from this link:
http://helpx.adobe.com/bridge/kb/acr-84-bridge-cs6-metadata.html

Canon EOS 5D Mark II with Adobe Bridge (CS4) and Camera Raw 5.4

I use a Canon EOS 5D Mark II and store in RAW-format.
The camera is updated with latest software etc.
I have the Adobe Design CS4 package on my computer and updated to the camera raw 5.4 version (bridge/photoshop/etc).
All this is updated to last versions / updates etc.
I upload my pictures from the camera to my computer.
When I inspect the files with the Canon software such as "Digital Photo Professional 3.6.1.0" or "Canon Utilities ZoomBrowser EX 6.3.1" (this are the latest versions and updates) the files are copied correct to my computer.
The files can be opened with the canon software without any problem and can be modified and converted and all normal operations can be performed.
The files can also be converted to ".jpg" and no problem occurs.
The problem starts after the folder with the pictures (in RAW-format) has been opened / viewed in Adobe Bridge or after Adobe bridge is started.
After starting and viewing with bridge the folder only some of the file become corrupted and cannot be used anymore.So the majority of the files remain OK but some files become corrupt.
A part of the picture is visible partly, the remaining part are lines, dots, squares etc and the divisions of correct picture and corrupted seems to be at random. There is no structure in the way the corrupted file are shown in bridge. Please look at the enclosed picture in this message.
The files can be opened in Camera Raw and Photoshop but they show the corrupted file and can be stored etc.
But the picture is destroyed.
Does anybody have a sollution or similar problems?
Best regards

There are forums for Bridge, Camera RAW and Photoshop.
Any of them would be better than posting here.
Bob

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

Raw Workflow PS CS3 and Camera Raw 4.5

Hello
I just started working with raw files, that's why I'm not sure about the best workflow with Camera Raw 4.5 and Photoshop CS3. My aim is to post process in raw 4.5. and in CS3 with as less quality loss as possible.
So when I finished the processing in raw 4.5 do I have to save it before I can continue working with the file in CS3 and in which format am I going to save it? If I save the raw file as psd, will I have quality loss? After post processing in CS3 what is the best format (for quality) to save it (there is no DNG possibility).
Thank you very much for your help!
Sarosa

You will probably get a lot of different answers your question because everyone has their own preferred workflow. Generally speaking, however, I think it is best to do as much of your postprocessing in Camera Raw as possible because it is nondestructive. You do not have to save your image to a different format before you start working on it in Photoshop. By clicking the Open button in Camera Raw, any changes that you have made are stored as metadata, and then the image along with all those changes is opened in Photoshop. Once you have the image in Photoshop you are now going to be editing the pixels of the image directly. And once those types of modifications have begun you cannot save the image as a raw image or a DNG file. It will be necessary to store it in a different format. I think good choices are either as PSD or TIF because either of these formats will save your work without doing any damage to the image data. From either one of those formats you can create JPEG or any other type of image that you need when required. JPEG images are saved with a type of compression that can, over time and through multiple saves causes your image to deteriorate.
In summary, you always have your raw images to go back to if necessary to start over. Use PSD or TIF to save your working files in Photoshop. And only create JPEG images from those PSD or TIF when they are required for the Web or for e-mail, etc..

CS3 and camera raw for Nikon D5000

I have dowloded the 4.6 plug in (installed automaticallywith updater). I still can not open my raw images
in cs3. Is the Nikon D5000 only supported by cs4?

Camera RAW support is only added to whatever version of Photoshop is current at the time the camera is released which would have been CS4 for your newish camera.
CS5 is just around the corner (next 2-3 months) as is Lightroom 3, which will both have the ACR 6 color engine so if you can wait, that would be the version to upgrade to.
In the mean time, you can use the DNG Converter 5.6 to convert your RAWs to DNG (saving the original RAW somewhere in case something happens) and use whatever version of ACR you want. The DNG Converter will give you a choice of what version of ACR to be backwards compatible with.

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

DNGs produced from Hasselblad .fff files display a different image in Bridge and Camera Raw

Lately, not sure when this started exactly, Bridge CC (and Camera RAW 8.7) are displaying incorrect DNG images! Instead of showing the image I expect to see, I'll see an old image from days ago. This seems to carry on from Bridge through to Camera RAW. But then if I continue on to Photoshop with the image, it'll finally show the correct image.
I'm assuming this has something to do with DNG, because if I load another raw file type (like .fff or .NEF), it seems ok. Also it seems to be ok with DNGs produced from other cameras like Nikon D90.
My set up:
- Mac OS X 10.9.5 (Mavericks)
- Bridge CC
- Camera Raw 8.7
- Photoshop CC 2014
- Hasselblad H4D-50

HI, I managed to fix the trouble by reinsatalling once again and running updates BEFORE opening bridge. It seemed that if I ran the update AFTER opening bridge I would get either an up to date status when checking for updates or I would get an install failure notice on all 4 updates that were trying to install. The updates were for camera raw, bridge and PS. I can't explain why but that helped a little. I also changed permissions on my whole user accnt to include read/write for all users. I can't say if this helped or not. I also had to go into my camera B/U files on a sepate HD and replace some of the CR folders I was using o nthe desktop. Still the CR files would not show a thumb nor a preview till I then went to each individual file inside that folder and purged the cashe for that file so it could repopulate the cashe yet again. This has been the strangest few days in PSCS6 history! Well my personal history. I will report back here if more quirks emerge. I would prefer quarks though....aloha, U

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

I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them.

I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them. I get a message saying that Camera Raw does not support my camera type but it always has in the past. The bridge no longer shows the picture view of my NEF files. These are Nikon NEF files from the Nikon 5100 DSLR camera. How do I fix this?

I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them. I get a message saying that Camera Raw does not support my camera type but it always has in the past.
When you re-installed Photoshop, you also re-installed the version of Camera Raw which shipped with Photoshop - in other words you reverted to an older version of Camera Raw which does not support the D5100.
Camera Raw plug-in | Supported cameras
The D5100 was first supported in Camera Raw version 6.4.
In Photoshop, click Help > Updates to update Camera Raw.

Bridge and Camera RAW preferences not working

I'm setting up a new Macbook Pro, late 2013 15", 10.9.2
CS6 Production Premium, Also have Indesign CS6, LR5, Acrobat Pro 11. Camera RAW is version 8.4. Everything is up to date.
Bridge and Camera RAW preferences are not working correctly. Bridge prefs related to Bridge display, e.g. color theme, text beneath thumbnails, favorite locations, etc.. all work fine. Bridge prefs open and close fine with no errors. "Double Click Edits Camera RAW Settings in Bridge" does not take. Photoshop launches to open Camera RAW regardless of whether this is checked or not. Camera RAW preferences will not open. Selecting "Camera RAW Preferences" from Bridge does nothing. Camera RAW seems to work fine hosted by Photoshop.
I tried a new user with the same results.
What's up with this? Anyone else seeing this? Solution?
--David

fixed it with this work around
Camera Raw 8.4 | No metadata or Camera Raw edit

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

HELP!!??? Trouble with PS CS-6 displaying/ producing grainy and pixelated images after being imported using PS Bridge and Camera-Raw 8.5

Help!??? I am having trouble with PS CS-6 displaying/ producing/ saving grainy pictures when import NEF files!!!
Hi all,
When I import all NEF or RAW files into CS6 from Bridge and Camera Raw from the Nikon D200 and D5000, they become grainy/ pixelated. However, RAW files from the D800 did not have problem. I set the Color Space in my Nikons to AdobeRGB, in PS Camera Raw 8.5 to AdobeRGB, in PS CS-6 ColorSpace to AdobeRGB, and Save As Jpeg with Max quality (12). When comparing between CS-6 produced file and the original, I can see a big drop in quality and the picture become grainy and pixelated. What can I do to make this right? Any help/ suggestion is appreciated.
Thank you!
HN

Can you show us a screen-shot of the raw in Camera Raw that shows this noise, or if you only see it in the saved JPG, then show us a side-by-side of the raw in Camera Raw and the JPG? Show the same area of the photo and zoom to 100%.
It is normal for raw photos to have grain but you can mostly remove it with the Luminance Noise-Reduction sliders in the Detail tab of Camera Raw.
The amount of grain depends on the ISO sensitivity setting on the camera.

Bridge CS3 and Camera Raw

Similar Messages

Maybe you are looking for