Bridge ACR Conversions Far Superior to LightRoom or Dr. Browns 123 Process?

I use the above apps constantly.
Just did a test of bringing out a Canon RAW file to PSD from Bridge CS3 manually with ACR, doing it from Bridge using Dr. Browns 1-2-3 Process automator and doing it using the conversion automator within LR.
Hands down the manual conversion was far superior to the other 2 automated conversions.
Detail was way better, color fidelity more pleasing and accurate.
So is there a way to make the automators do as good a job as ACR does?
Hate to think I have to sacrifice so much quality for the sake of expediancy.
Any thoughts?

I suspect as much.
It would make sense that the output from both "engines" should be the same.
But what accounts for the difference in image detail?
What are the critical settings in each app to make them match?
Where exactly in each app do you set the color control?
Color management continues to be the bane of my professional existence.
In a related matter, whenever I tell LR to create a website or generate jpegs of my RAW files, I wind up with that sad looking desaturated, greenish-caste look in the resultant jpegs.
They lack the warmth and vibrance of the previews Im seeing in LR.
My output images look non color managed even though I could sware Im specifying that they be sRGB to cover the lowest common denominator of the on screen viewing world.
I believe LR's environment is ProRGB, so what's a guy to do to make the origin match the final?

Similar Messages

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

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 and Camera Raw vs. Lightroom

Is there anything that can be done in Bridge or Camera Raw (CS6) that can not be done in Lightroom4?

This is an extremely broad question, you could probably make a list of three dozen items, and I'm not going to attempt to do so. I point out that there is probably a very long "opposite" list, i.e. things that you can do in Lightroom that you cannot do with Bridge/ACR.
One of the biggest differences is that Bridge is a file browser, while Lightroom is not. Thus, if you point Bridge to a folder, and there are 15 photos there, then Bridge "knows" about all of them, and you can view all of them and work with all of them. If you have previously imported 5 of those files into Lightroom, but not the other 10, then when you point Lightroom to this folder, it only knows about the 5 that have been imported, and you cannot see or work with the other 10. A consequence of this is that if you move a photo in your operating system, Bridge has no issues, but the photo becomes disconnected in Lightroom and cannot be used until a reconnect happens. Naturally there are advantages and disadvantages to both ways of doing things.
If you have specific question about doing something in Bridge vs Lightroom, we can discuss those.

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.

D3 NEF/ACR Conversion

I notice that there are now two ACR Profile options in the Camera Calibration panel for the Nikon D3. Namely 4.3 and 4.4; the latter apprearing to be the default. I have to say to my eye the conversions each make on a sample NEF file appear remarkably similar - although I have no doubt some who know better will tell me otherwise.
Notwithstanding that, I also notice from a thread in the LR Beta2 forum the hint from Eric Chan that moves are afoot to improve the ACR conversion performance nearer to that of Nikon, Canon etc. A hint supported by Thomas Knoll no less in the same thread. As my local farmers say, relative to rumours of the Beast of Exmoor: 'thar mut be summut init'.
Looking at the timeline of these postings and the release of ACR 4.4, my supposition is that such 'improvement' was not incorporated therein, and there is more on the way. Unless, of course, someone knows better.

There were some improvements made to all profiles in Camera Raw/DNG 4.4/Lightroom 1.4.
From the release notes:
Previous camera profiles identified in the Calibrate panel of the Develop module may have displayed poor results at extreme ends of the temperature and tint ranges. A new camera profile identified as Camera Raw 4.4 is now available and will be applied by default to all images without existing Camera Raw or Lightroom settings. The creation of new default profiles will also include the updated Camera Raw 4.4 profile.
So there might be a slight improvement for all your files in 4.4.1/1.4.1 (the current release). I created a preset to enable batch conversion, which is available on the site in the sig.
The 4.4 release isn't the same thing that Thomas and Eric are talking about.
Richard Earney
[commercial link deleted]

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.

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

I am using Bose AE2 headphones. The music quality is far superior when I listed on a PC than on the isphone5. Also, the volume is also considerably less. Is it something that I am doing wrong.

I am using Bose AE2 headphones. The music quality is far superior when I listed on a PC than on the isphone5. Also, the volume is also considerably less. Is it something that I am doing wrong.

There are quite a few possibilities.
The quality difference may simply be the lower volume. Hearing is not linear with volume.
How much power do the headphones require? Possibly your computer can provide greater power output than the iPhone.
Some Bose headphones have a volume compensation switch somewhere. On my QC3 its on the adapter plug at the headphone end. You have to unplug it from the headphones to find it.
Do you have volume limits enabled in the iPhone settings/Music?
Are the equalization settings the same on your computer and your iPhone?
Do you have Sound Check enabled on music that is synced to the iPhone?
Have you checked "Convert higher bit rate songs..." in iTunes on your computer?

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!

I have installed Adobe Lightroom CC. In the process of launching, a popup appears, that says: "AN INTERNAL ERROR HAS OCCURRED. Cannot create the required folder: /Users/(my user name)/Library/Application Support/Adobe/Lightroom/Develop Presets." So e

I have installed Adobe Lightroom CC. In the process of launching, a popup appears, that says: "AN INTERNAL ERROR HAS OCCURRED. Cannot create the required folder: /Users/(my user name)/Library/Application Support/Adobe/Lightroom/Develop Presets." So even though Lightroom CC is installed, it will not launch. What do I need to do to allow it to launch?

The problem was solved today. Here's the full story. I'm a Mac user. At first I installed Lightroom CC on my iMac (desktop). I had this problem so I called Adobe, and was referred to a "special unit" . After about an hour the tech solved it for me ... we did a screen sharing and she took control of my computer for a loooong time. Because of language difficulties, at first I wondered if she knew what she was doing but she eventually solved it. Although she couldn't explain exactly what she was doing, she summarized it by saying "it was a permissions problem." I asked if I would have the same issue later when I installed it on my laptop (Macbook Air). She said probably not.
But I did. The same internal error popup arose on launch and launch did not complete on my laptop. I tried chat but no joy so I eventually called Apple Care. I had noticed that on my laptop (and the iMac for that matter), that there was no Library folder after my user name. The Apple tech explained that the Library folder is actually there but it is hidden because it's very easy for users to do some very nasty things to their computer by going astray while in the Library folder. The folder is actually there, but they hide it. I did remember seeing that the tech helping me with my iMac had typed the work "Library" while she was controlling my computer. Basically she had activated the hidden Library folder so she could open the path that Lightroom was trying to follow to create that "Develop Presets" folder. For some reason, the inability to create that folder in the launch process was preventing launch from being completed. The Apple tech said she didn't actually have to do that and activated the Library folder by use of the Go selection on the menu bar. Anyway, once that complete path was replicated and opened, the next step was to go to the Lightroom Permissions field and add my user name to the user categories already there and enable "read and write" permissions to my user name. Once done, I shut down my laptop, and then rebooted. I launched Lightroom and then boom, voila, heavens to betsy, etc. it launched and suddenly a dismal weekend turned into a great one.
I am not a geek, so I hope this makes some sense. I also hope Lightroom launches again tomorrow and beyond!

Conversion Error: I/O error while communicating with native process

Hi,
I am trying to use Oracle Outside In Technology Image Export for conversion of images. I am trying to run the example ExportTest that comes with the downloaded SDK.
I get the below error while running the ExportTest example.
Conversion Error: I/O error while communicating with native process .
Am I missing any settings?
Please guide to the right forum if this is not the one for posting queries on Oracle Outside In Technology Image Export.
Thank you.

Hi Revanth,
I am using Image Export 8.3.7 and I am trying to run the java class "ExportTest" that is in the location sdk\samplecode\ExJava\Examples\ExportTest\src of the download.
My input folder has one jpg - puzzle.jpg (this is just a simple jpg), I am trying to convert it to TIFF. ExportTest.java uses the classes in Export.jar . Export.jar is located in the sdk\samplecode\ExJava\Examples\ExportTest . You can see source files of the Export.jar at location sdk\samplecode\ExJava\Java API\src of the download. I am running the 'ExportTest' by providing the arguments (input folder, output folder and ix.cfg - this file comes with the download). So now when I run this class I was getting the error I mentioned in this post. Inorder to find more details about the error I modified the 'Export.java' (at sdk\samplecode\ExJava\Java API\src\com\outsideinsdk) just to printStackTrace when the exception occurs and rebuilt the 'Export.jar' and ran the 'ExportTest.java'.
And below is the stack trace that I got :
java.io.IOException: CreateProcess: nullexporter.exe "inputpath_u=AGkAbgBwAHUAdA
BcAHAAdQB6AHoAbABlAC4ASgBQAEc=" "outputpath_u=AG8AdQBwAHUAdABcAHAAdQB6AHoAbABlAC
4ASgBQAEcALgBUAEkARgBG" "outputid=FI_TIFF" "fallbackformat=FI_TEXT" "tiffcolorsp
ace=24BitRGB" "preferoitrendering=false" "tiffcompression=Packbits" "mapbuffersi
ze=8192" "defaultprintfontheight=20" "graphicwidthlimit=0" "reordermethod=off" "
unmappablechar=0x002A" "timezone=0" "graphicheightlimit=0" "defaultmarginleft=14
40" "ssshowheadings=false" "quickthumbnail=false" "graphicoutputdpi=0" "ssdirect
ion=AcrossandDown" "defaultmarginbottom=1440" "ssshowgridlines=false" "dbshowhea
dings=false" "readbuffersize=2" "whattoexport=all" "graphicsizelimit=0" "imagewa
termarkopacity=0" "blue=-1" "handlenewfileinfo=no" "outputid=FI_TIFF" "lzwcompre
ssion=enabled" "usedocpagesettings=true" "defaultmarginright=1440" "numberofstat
callbacks=0" "dbfittopage=NoScaling" "tempbuffersize=2048" "pdffilterreorderbidi
=no" "imagecropping=nocropping" "defaultmargintop=1440" "documentmemorymode=larg
e" "m?
at java.lang.Win32Process.create(Native Method)
at java.lang.Win32Process.<init>(Win32Process.java:66)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at java.lang.Runtime.exec(Runtime.java:491)
at java.lang.Runtime.exec(Runtime.java:457)
at com.outsideinsdk.Export.convert(Export.java:262)
at com.outsideinsdk.ExportTest.convert(ExportTest.java:142)
at com.outsideinsdk.ExportTest.main(ExportTest.java:214)
hope this helps to find the problem.
Thank you

BUG? Keywords (and other changes) made in bridge don't show up in lightroom

When I put keywords to images in Bridge _after_ editing them in lightroom, they never show up in lightroom.
And seems like color labels doesn't change if I try to do it in Bridge. Bridge shows new color label, lightroom shows old one.
and no, image is not open in lightroom when giving keywords in bridge.

I do not have that problem, but I am sympathetic to how much you dislike the LR keywording system. You would think Adobe would adopt a single system for all their related apps?
The best way i found to deal with it is to have both apps write to the xmp suidecars(for RAW)and to make sure there is a copy of ACR 3.7 8bi in the file format folders of all Adobe apps that I interchange files to and from. Presumably, by the time Bridge 2 and PS CS3 are out of Beta, all three apps will be on the same page using ACR 4.
My setup does work without a hitch--but I do not like the LR keywording at all. Like many attributes of LR, it is simplistic and largely designed for the new or casual user (and those that shoot or process the same category of images day in and day out (weddings, etc), rather than for someone with an existing, large DB and established workflow--and hundreds of diverse subject images a day to do!
I do all my keywording, renaming, and initial sorting and culling in Bridge CS3, and it goes at least two to three times faster than using LR for those workflow functions, and that is not due to inexperience with LR, but rather to far better workflow design for those functions in Bridge- tabbed, rather than a slider, driven interface for "developing" in bridge is also part of that better design.
I am using LR for its Develop module only--all the other modules fall far short of what I need and presently use--especially the Library--and doing that simply because Bridge 2 has a terrible memory leak and numerous beta bugs and interfaces more poorly with beta PSCS3 than LR (and that is not to say that LR does a sterling job at at all) for the moment
Maybe Adobe can get the Bridge and LR teams together over lunch and politely (but firmly)tell them to get the best of the common features from each into both.

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

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!

Bridge ACR Conversions Far Superior to LightRoom or Dr. Browns 123 Process?

Similar Messages

Maybe you are looking for