DNG sharp in Bridge/ACR, soft in PS4

Hello,
I'm new to the forum - I hope I am asking this in the right place! I just upgraded to a D7000 and found that ACR can't read the .NEF files, so I used Lightroom to convert the files to DNG. I've since downloaded the DNG converter and will use that in the future, as I only have the trial of LR and don't do any editing there yet.
When I preview the photos in Bridge and open them in ACR they look nice and sharp...but when I open them in CS4 they look terribly blurry! As a test I saved some files from PS as jpegs and then uploaded and viewed them in Flickr and they look nice and sharp there. Any idea what settings in PS could be wonky? Prior to today I had a D70s and used ACR/PS4 with no problem, but I didn't have to convert to DNG (and my file size was a lot smaller, not sure if that's relevant).
Thank you for any help or ideas!!
Cheers,
M

Hi Noel,
Thank you for your thoughful and detailed response. Sorry it took me a while to get back to you, but here's what I've found out.
*I have a Macbook Pro from 2008 with a NVIDIA GeForce 8600M GT 512 MB video card.
*I have no idea what display driver version I have
*We recently upgraded to OS X Lion 10.7.1 (within the last month)
*Last week I upgraded my camera to a D7000 which significantly increased my file size (vs the D70s from 2005)
*I have CS4 which doesn't read the NEF files from my new camera, so I'm converting them to DNG
*Photos would look sharp everywhere (Bridge, Finder, saved as JPEGs and uploaded to Flickr) except for within PS4
To make things even more strange, the problem seems to be intermittent. I opened some photos with and without OpenGL today and took screen shots to attach here, and they look very similar - maybe a slight change in tone and sharpness, but nothing to write home about. I checked the Nvidia site, and when I search for updated drivers for my card they don't list OS X Lion as an option for the operating system - maybe that is part of the problem? I did a Google+ search and apparently a lot of Macbooks from 2007/2008 are having issues with this video card, and Apple is actually repairing them for free if they fail within four years of purchase. I'm now wondering if the new file size + OS X Lion is somehow exposing an inherent weakness in the video card. At the extreme end these cards have failed completely - I'm clearly not there yet, as my photos look fine today! Not sure if this makes any sense. Thank you for your help!

Similar Messages

LR RAW adjustments not visible in Bridge/ACR or iView MP3

I have just added LR 1.3 to my RAW workflow after using Bridge /ACR /CS2 for some time. If I make adjustments in LR - a big improvement over ACR 3.7 - I cannot see the changes when I open in the other applications. I am using DNG. I am sure I am missing something simple but I cannot find the answer anywhere. How do I do this please?

Gary,
I don't know if you are going to check back here in this forum again. But I think you will find it necessary to export copies of your images and then open to those copies in order to see your Lightroom adjustments.

Does ACR 100 sharpening = PS4 100 sharpening amount?

I'd like to do my capture sharpening in ACR in Bridge then do output in PS4, but the Bridge sharpening Amount range is 1-150, while PS has an Amount range of 1-500; and an even more dramatic difference in "pixel" settings (ACR has .5 - 3.0 while PS has 1-64). I've read that the ACR sharpening is basically USM (unsharp mask), so is there any way to correlate these numbers? For instance, if I apply 150 in ACR does that equal 150% in PS or is the scale different so that ACR's 150 = PS 500% for an incremental increase of 3.3?
Brian

BALawson wrote:
Does ACR 100 sharpening = PS4 100 sharpening amount?
No...

I have reinstalled cs4 student edition afther a deactivation by adobe but can not veiw ORF or DNG files in bridge i am runing windows 7

I have reinstalled cs4 student edition afther a deactivation by adobe but can not veiw ORF or DNG files in bridge i am runing windows 7

Keep in mind that if your camera is newer than the last released version of Camera Raw (5.7) for Photoshop CS4, Adobe does provide a free solution for compatibility, as Curt has mentioned, through the use of the free DNG Converter application.
The way that works is this:
1. You get your raw images from your new camera into a folder on your computer.
2. You run the latest DNG Converter application and choose the folder.
3. It converts the entire folder full of images to .DNG files.
4. You open a DNG file as you would an older raw file, with your old version of Photoshop.
While the DNG Converter provides you a way to continue to use your older Photoshop software with a new camera, keep in mind that there are significant improvements in the raw converter in the latest version of Photoshop that may allow you to make better images out of your raw files if you do choose to upgrade Photoshop.
-Noel

Photoshop cs4 ORF or DNG files in bridge

I have installed my Photoshop cs4 in my new computer wich is running windows 7 But I cannot preview ORF or DNG files in bridge I th
ink this may be a activation problem

If I do that it doesn't get any bigger just makes the window bigger, not the image
If that is the case something is wrong with your set up. The slider bottom right Yammer p pointed you to does alter the size of the thumbnails, not the panel itself.
Top right are the workspace names, at the right of it is triangle, click on it and choose reset workspace. Otherwise restart bridge holding down option (mac) or control (win) when restarting bridge and choose reset preferences.
If still out of luck provide more details about your computer (RAM / VRAM) OS version and exact Bridge version.

PowerMac DP 2 Ghz vs 15" Powerbook & Aperture vs Bridge-ACR and 10 D2X nefs

10 D2X nefs, equal settings(including sharpening) on each file.
Test: Time the export/saving 10 full sized JPGs(level 10) on both systems under both Aperture and Bridge/ACR
In Aperture, stamp the same settings to 10 nefs, wait for the changes to appear on each thumbnail, then select the 10 nefs, and select export versions.
In Bridge, paste the camera raw settings to the 10 nefs, wait for the thumbnails to show changes(building cache), select the 10 nefs, open ACR under Bridge(not CS2) by pressing CMD-R, in the ACR dialog, select all images on the left, click "Save 10 images".
PowerMac: G5 dual 2 Ghz, 2 GB RAM, X 800 XT vid card, Aperture library and Bridge cache on separte SATA 7200 RPM internal disk
PowerBook: 15" 1.5 Ghz, 1.5 GB RAM, ATI Mobility Radeon 9700, and 80 GB disk
Aperture results:
PowerMac: 2:07
PowerBook: 5:06
Bridge/ACR results:
PowerMac: 1:18
PowerBook: 2:12
As you can see Aperture requires 2x the time to export/save when compared to Bridge/ACR.
Further, it is amazing that the Powerbook could plow through the images in Bridge in the same time it took the Powermac to export the Aperture images...
Hmmm, then that would imply the best money is on a Powerbook running Bridge/ACR/CS2?
Sooooo, if you can cull/sort the images and apply raw settings in Aperture three to four times as fast as in Bridge then it is a wash...

zozi56 wrote:Can you reproduce the problem without Skype, Bastian?
From what I remember I have also had this issue when Skype wasn't open.
Yesterday my computer started up beeping - I took the harddisk out and it started normally (initramfs tho). Then I put it back in and the laptop have been running fine so far. I suspect it might just have been a bad connection, but I am giving it time..
EDIT: Still experiencing the issue..
Last edited by Bastian (2014-01-19 18:09:08)

Bridge-ACR Help Please

Bridge-ACR Help Please
I'm using Bridge CS3 v2.1.9
I have CS3 v2.1.9 and using Bridge I have been opening JPGs in AdobeCameraRaw with no difficulty using the keyboard shortcut CTRL-R. Now all of a sudden it won't work. In addition 'FILE > Open in camera Raw' is greyed out.
Any ideas?
Thanks for any help,
Henry

Have you done any updates to Bridge, or made any changes since it last worked? There must be some change if the behavior has changed.

DNG Preview in Bridge CS3

I recently converted all my NEF's (from a Nikon D70s) to DNG files using Adobe DNG Converter 4.3.1. I use Lightroom to do most all of my cataloging and post processing however I went into Bridge the other day for the first time in a while and noticed that I none of the DNG have a preview other than the standard .DNG adobe icon. Why? Am I missing something I've gone through preferences of both Bridge and the DNG converter. Bridge sees the .NEF files perfectly.
Cheers
Ben

Ben,
Couple of ideas -
Is Bridge is totally up-to-date?
Have you tried resetting your Bridge preferences? Hold down the Option key (Mac Alt on Windows) and launch Bridge. You should get a dialog box that will give you the option to trash the prefs.
If that didnt fix it, are you sure that the Camera Raw plugin is installed correctly and working? You mentioned that Bridge displays your NEF previews but do they open into CR? If all is well with CR, then the next thing Id try is copying a few of the DNGs to a new folder and then do some quick edits to them. Make sure the Camera Raw preference under DNG File Handling is set to Update embedded JEPG previews. That will force a new preview to be built. If you still cant see them, Im out of ideas other than the more drastic step of reinstalling Bridge...
Hope that helps-
Greg

Batch Process White Balance From Bridge/ACR?

Here's what I want to do:
Open Bridge
Use Tools > Photoshop > Image Processor
Set ACR white balance to be used on all files being processed from Bridge
Save to JPEG
I can do 1, 2, and 4. When the Image Processor window opens it gives me a checkbox option that says, "Open first image to apply settings". I assumed this meant I could open the first image in ACR (via Image Processor), adjust the white balance settings (and any other ACR settings I want), and then have those settings applied to the rest of the images that are processed. However, when I do this, the ACR settings are applied only to the first image, none of the others. Is there a way to apply the ACR settings I create on that first image to the rest of the images?
Thanks,
Aaron

Apologies for replying to this thread, but it seemed like a better idea than creating another topic for more or less the same issue.
I am attempting to do the same thing using Bridge/ACR except I am not seeing the edits on the JPEG file afterwards.
Here are the steps I go through.
1) Open Adobe Bridge CS3
2) Select several RAW files
3) Click Tools > Photoshop > Image Processor
The options I have checked (1) open first image to apply settings. (2) Save in Same Location (3) Save as JPEG, Quality 12 (4) Include ICC profile
4) Click Run
5) Make edits in ACR, click Open Image
6) Photoshop batches those files.
I only chose 6 files to batch as a test, but it only made the edits to the first picture, the remaning 5 were untouched.
I am wondering if maybe I am just missing something simple here and someone could point it out to me

Reinstall older Bridge/ACR

The current Bridge / ACR updates now insist on rebuilding all thumbs and previews. For me this is awkward (750,000 images on archives).
How can I reinstall an older version of Bridge and ACR so that my archives will not be rebuilt ??
Is it necessary to revert both Bridge and ACR ???

Adobe uses Bridge as a DAM of all of the digital programs that "unite" their programme spectrum.
I stay with my opinion about bridge being not suitable for real use of DAM. Bridge is powerful but it is certainly not as good in DAM as a real dedicated DAM application. As in its turn a real DAM is not as good in tasks for preparing and sorting files etc, here is where the powers of Bridge should come to the rescue, just the right application for the right job
They are oblivious to how users perceive Bridge (at least in my experience).
Sadly enough with large companies there are to many departments and also divided over several countries and even continents. The Bridge team is in China and as long as I can remember has lack of resources and attention of Adobe HQ.
The effort and resources HQ puts in advertising could be spend wiser IMHO and the several layers of management seem to live on a whole other planet then the work floor.
A customer is an idiot that keeps paying money (I'm one of that idiots I'll ave to admit…) and he/she really does not know what is needed, that is in better hands with the bean counters department.
As one of those idiots I try to get the most out of Bridge for my workflow and also try to forget thinking about what it really could have been if those bean counters where not involved but the hard workers on the development floor (some of them are really very nice and do listen but also often feel like Don Quixote) could make their own decisions more freely.
I can't miss Bridge in my daily workflow, even in its current state, CC, including the AOM. I have a single monitor so no need for synchronized windows but feel sorry for those who do. Also the export panel is not missed by me but a perfect example of what is needed and could have grown to key features if only get developed to the limit.
The File Browser presented in PSCS the first Creative Suite edition did have a cache management that was far more superior and faster then current Bridge. I did welcome Bridge for it's promises, the name indicates it should be a bridge between the different suite applications.
Yet since CS4 there have been no significant developments of existing features (yes, cache has been more stable and faster but still causes massive cache files and needs a long time to cache) but even in CC there is still lack of support for certain file types in Bridge that are produced or handled by other Adobe Creative Suite applications
But it seems Adobe Policy to create new features that the advertising department can use for yelling around and the bean counters need for increasing sales.
Mini Bridge is also a perfect example of what we would need. It started promising in CS4 yet it has been screwed severely in CS5 and has not been corrected in CS6 nor CC. I have a very limited use for it but boy, imagine what it could have been if they really wanted it to be. Imagine a panel in Bridge that you can prepare (drop files on, like a collection but then better working) and this same panel would be visible as a panel in all other suite applications so you don't need to switch back and forth between apps. Mini Bridge should act like this but it simply doesn't.
I could go on and on...
We idiots are driven to the creative cloud subscription, which in basic is a good thing because having predictable costs and all applications available with latest updates is good for commercial users (I'm one of them). But a good willing non professional user that only need PS now pays about twice as much as would be the case with a perpetual license.
If you want the proof of Adobe CEO Shantanu Narayen being oblivious here is such shocking example:
http://www.youtube.com/watch?v=juM46ny1WhM

Bridge / ACR - too Yellow!

I have gone through the best settings for color management by Deke. You can see by the screenshot that my color settings are calibrated.
I shoot in raw (love bridge for my workflow, but with this new computer, it is wayyyy off).
Color Calibrated System using Huey
Windows 8
CS5 Premium Suite
What am I missing? This has totally undermined my trust of Bridge/ACR as the best part of my workflow.
Please help!

Or I should complain to myself for not updating before complaining. John, Thank you for the quick response.
I see marked improvement!

DNG Flat Field Plug-in usable with Bridge/ACR?

Can the DNG Flat Field plug-in be used at all with Adobe Bridge and ACR, or to apply a flat field must you import images into Lightroom and create DNG files using Lightroom?
Also - must you apply the flat field correction before you apply any other processing or development to the main image? i.e. I assume the main image and flat field calibration image must have identical processing steps applied to them and those should be default or minimal development.

Hi Alan,
No, the DNG Flat Field plug-in can only be used with Lightroom. It is specifically a plug-in for Lightroom.
The Develop adjustments do not affect the flat field correction. Internally, the plug-in will apply the calibration to the image data before any of the Develop adjustments come into play. (This is necessary because the flat field or shading correction needs to be applied very early in the image processing pipeline.) So, it does not matter what you have your Develop controls set to.
In terms of a practical workflow, it makes sense to apply your flat field correction before even going into Develop. This is because the result of a flat field correction will change the baseline or "starting point" for your image (e.g., it will change the color and/or tonal balance). So, it is better to find out what that corrected starting point is before you begin tuning color and tone in Develop.
Eric

CS3 Bridge Preview Soft

Please see Case No: 172571700 for details, however, I would love to see your developers come up with an option in preferences that would allow one to choose to see larger RAW files as sharp as they really are. Right now when I load up images from my Canon 1Ds Mark II or Canon !1D Mark III, the images in the preview pane are soft and mushy even though they are sharp. The problem is that I have to shoot sometimes in order of 1,500 images a day for certain assignments, and I can't tell if my images are in focus or not without opening them up in ACR. That takes too much time. In Bridge CS2 I never had that problem. I understand that you generate the image from the preview image in the RAW file, but even if I convert to DNG with High Res preview, the good images still look soft and mushy.
Take a look at your forum on Bridge and you will see that I am not the only one that wants a preview pane that works. I will take the hit in speed. I am sure is will be faster than opening up every image in ACR.
Thanks,
Daniel Root
Portland, OR

Adding my voice to the chorus... I use a Canon 5D (among other cameras) and the previews in Bridge look little like what I see when I open the files in ACR or as converted TIFFs in PS CS3. Purging the caches (globally, and then often again for the individual folder) is an unnecessary manual step and there should be an option to build the preview directly from the RAW file (vs. the embedded JPEG as it appears to do now).
Same goes for the magnified 'loupe' view in Bridge -- it's not much use as is in terms of checking for sharpness, it looks like it's just magnifying the JPEG preview (and beyond 100% as well, it would appear), so what you see are, mostly, soft pixels resulting from the bicubic smoother upscaling and color blocks from JPEG artifacting.
Thanks,
--Geoff

Time to export/save one D2X NEF to JPG Aperture vs. Bridge/ACR

15" PB, 1.5 Ghz, 1.5 GB RAM, running Firefox, Entourage, while each app is running test.
Single D2X NEF in an Aperture project:
-No sharpening applied, export to JPG 11 seconds
-Any sharpening applied, export to JPG 29 seconds
Single D2X in a folder in Bridge, open in ACR
under Bridge:
-Any sharpening or not, save to JPG 15 Seconds
Note, while Aperture exports, the entire app is tied up. Bridge does the saving in the background, which allows you to continue working in Bridge/CS2

I have not run that test, but I did do Aperture batch versus CS(1) batch...
Basically, when I'm batching from CS RAW -> JPEG, my dual G5 turns 12 images per minute. When I "export" from Aperture (which might as well be a "batch," it's doing the same function), I get a little over 13 images per minute.
Frankly, I almost never sharpen when coming from RAW. I prefer to make a highly selective sharpening pass later after going to JPEG, sharpening only those that need it the most. I'm not a big believer in sharpening, due to fact that I have no control over how image will be resized, and sharpening prior to a significant resizing is pointless in my experience... and despite all the talk about how digital images are soft compared to film (due to the built-in sensor filter) I don't really buy that. I don't remember film being so dang sharp.... with the L series glass I'm using and 8.2 megapixels, this stuff looks as freakin' sharp as 35mm film ever did to me... now I will concede that medium format film has a certain sharpness advantage, but 35mm??? Maybe Kodachrome on a tripod, but probably not an ISO 400 print film hand held at a wedding reception... I digress.
Now I'm going to go run your sharpness test to see what I can see, seeing as how I finally upgraded to CS2 this week.

Question about DNG converter in Bridge CS4

Hello,
I just installed Photoshop CS4, When I updated, it downloaded a hefty update (199 megs), so my setup now is:
Win XP pro
Bridge 3.0.0.464
Camera RAW 5.7
Photoshop CS4 11.0.2
My Camera is a Panasonic Lumix FZ150 ( 2011 vintage)
I have downloaded the Adobe DNG converter 6.6.0.261
Every thing seems to be working fine so far, except:
In Bridge when I "get Photos from Camera" the DNG conversion doesn't work. When I use the standalone converter it works fine.
From reading past material on this forum I am assuming this is due to the fact that Bridge is older than my camera, and doesn't recognize the format.
The questions:
1. Does Bridge have its own built in DNG converter that is not upgradeable separately?
2. If 1 is correct, is there a way to point Bridge to the location of the standalone converter so the work flow can be optimized.
3. Since Bridge is not doing the conversion, but only importing the files, does the "Apply metadata" section of that window actually do anything? Should I bother to fill in any of those boxes?
Thanks for any help.

I posted a similar question quite a while ago, and what I learned was that Bridge has a DNG converter built in, but it's using ACR to read the file before it can convert. So you need ACR support for your camera.
AFAIK there's no way to point Bridge to a standalone DNG converter.
I suggested an updateable DNG converter plugin for Bridge, don't know why nobody listened...I thought it was an excellent idea
As for the metadata, you just have to try. I don't know if it can write metadata when it can't read the file.

DNG sharp in Bridge/ACR, soft in PS4

Similar Messages

Maybe you are looking for