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!

Similar Messages

  • 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.

  • 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.

  • 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

  • Color in both Bridge CS5 and ACR look yellow.

    The color in my images are all yellow.  I've seen some posts but so far no answer to the problem. Can anything at all be done to fix this problem. It it very, very frustrating. Because it's so yellow I cant use ACR for anything at all.  Please help
    Igor

    Ok, for anyone having this problem with both Bridge cs5 and ACR. Here is what solved my problem. All images were looking yellow both in bridge and Camera Raw, so after I did a back up of my harddrive as a System Image all problems were gone! I have no idea what happened, but now the colors are just fine. The problem corrected itself. So, there you have it. Problem fixed.

  • Images in Bridge CC too bright

    Why do my images show almost 2 EV too bright in Bridge CC after filing from PS CC, but have a perferct match when opend on Bridge CS6?

    Why do my images show almost 2 EV too bright in Bridge CC after filing from PS CC, but have a perferct match when opend on Bridge CS6?
    Either you have set Auto Tone adjustments set in Camera Raw preferences or have created a custom default ACR setting for this file type which is set to overexposed.

  • Bridge CS6  too bright

    My Bridge CS6 has suddenly become too bright.  Any fixes?

    Glad this solved your problem and no, if don't have trouble with views there is no need for purging cache at the moment.
    Don't use NIK myself but I would choose for uninstall and reinstall the NIK plug ins.
    Search for info before acting, here is a start:
    https://support.google.com/nikcollection/answer/3000951
    Save your custom presets by exporting them (always a good thing before updating or any other changes) and be sure to have the correct serial numbers and registration keys at hand. Then check for the latest versions on the NIK download site and install again.
    And for the part of retrieving original filenames:
    I never make a big deal out of filenames, I start with renaming on import using shot date yyyymmdd and a sequence number but check the option for the original filename being kept in exif. (you can set this as an option but I believe the original raw filename is always preserved, although not sure about this)
    If you need to find (for what ever reason) this previous filename is somewhere in the XMP data of the file info. Either in advanced, Raw data etc.
    And if this info is available there is always some one keen on writing scripts willing to help you with a script to reveal this info and use it as the new filename (there is a dedicated Bridge Scripting forum).
    So in case of 6000 the longest wait would be to find some one to help you and then a bit time to install the script. The running of the script is a piece of cake and does the work for you, same as batch rename in Bridge can do.
    Don't use LR myself that much, can't get used to the library structure and export of results. And prefer the customized UI of Bridge I have in combination with ACR and PS.
    I also think (personal) that combining both LR and Bridge is not the best strategy…

  • Bridge/ACR don't translate settings to batch processed JPGs/PDFs

    I edit a batch of RAW images in ACR via Bridge, hit "done" and then send them to Image Processor to create JPGS or use the Output Module in Bridge CC to make a PDF. Sometimes the settings I just applied in ACR don't translate to the JPGs and/or Output PDFs.

    This forum is actually about the Cloud, not about using individual programs
    Once your program downloads and installs with no errors, you need the program forum
    If you start at the Forums Index http://forums.adobe.com/index.jspa
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll
    http://forums.adobe.com/community/bridge

  • Color Management Discrepencies Between Bridge, ACR & Photoshop

    Hi - I've had a color management issue I can't wrap my head around which is similar to this infamous thread: http://forums.adobe.com/message/3235601#3235601
    I'm hoping with a little more information provided I can get this figured out. The basic problem is that Bridge displays images markedly differently than either ACR or Photoshop. The most common issue is as follows:
    With the external monitor as the primary display (and the laptop monitor as a secondary), I start Bridge. Photos will seem to be in the correct gamut for a moment, but it almost immediately desaturates them as if switching gamuts. Opening the image in ACR or Photoshop shows the correct color. See the below:
    (Note: on my wide-gamut monitor, there's no clipping on the ACR version - that's how it should look)
    There are various permuations to this problem depending on which monitor I have on when I start Bridge, but the above is my general workflow.
    Some background:
    Lenovo ThinkPad T430s w/ integrated Intel HD4000 graphics
    ASUS ProArt Series PA246Q (Wide Gamut)
    Photoshop CS6 (using 16-bit ProPhotoRGB as the standard workspace)
    Datacolor Spyder4 calibrating both monitors
    My settings:
    I know there are a bunch of variables, but does anybody see any glaring issues which might explain my problem?
    Thanks!

    No problem, thanks for the help! On my PC, screen capture using the Prnt Scrn button must be pasted into a program or taken/saved using the snipping tool. Either way the result appears to be untagged.
    Here are a few more examples if you get a chance to look in the future. I'm making sure the proper profiles are embedded correctly (you can confirm in both Photoshop [lower left] and Bridge [upper right]):
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing PSD w/ embedded ProPhoto RGB:
    Secondary, laptop monitor (sample includes embedded profile) - Viewing PSD w/ embedded ProPhoto RGB:
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile:
    Secondary, laptop monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile:
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile:
    Secondary, laptop monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile:
    So the WhackedRGB sample looks ok and the ProPhotoRGB samples look ok here, but it doesn't look like the WhackedRGB or ProPhoto samples have anything outside the sRGB range.
    Note what happens when I edit the WhackedRGB and ProPhoto samples simply by adding colors on the extremes of the gamut...
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile EDITED with gamut extremes:
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile EDITED with gamut extremes:
    The issue is back - the colors are very different! At this point, it's probably a bug, right...?
    Thanks again!

  • File printing and icons for folders in Bridge CS5 - too small to read

    Got CS5 and am trying to use Bridge. The folders are too small to read and the print with them too small. The slider at the bottom of the page enlarges the space but the files and printing stay the same size. If I open one the images will enlarge with the slider but I don't want to waste time opening each file to see what is in them. I want to be able to read wha the file is and open the right one first try.
    Tried calling "tech support" Those jackasses can't speak English. On hold for 3 hours overall after getting someone, getting cut off and having to call again. I hope Pakistan nukes India and solves that problem.
    When I finally got through the guy told me my Photoshop copy was not registered. Funny, it was last week when it had problems. Then I try changing the pasword and it says it did it, but won't accept it.
    I hate computers.
    So, anyone know how to get this damn probram to make the folders and printing big enough to read without my having to get up to the screen with a magnifying glass like Sherlock Holmes? The screen is a 22inch graphic arts monitor and I don't have this problem with any other programs. Not Breezebrowser, Not Auto Pano Pro, not Photo Mechanic. Just Bridge with this overpriced and overhyped photoshiz crap.

    Small, and uncustomizable, fonts has been a com
    plaint in PhotoShop also. 
    Send in a bug report, they do read those, and maybe if enough users complain they will modify the program.

  • 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

  • Win 7-CS4 - Bridge - ACR 5.5 Camera Raw editing not enabled

    I have just migrated to a new Win 7 system. Fresh install of PS CS4, I found I could load CR2's into ACR but not jpg's. Wehn I tried to check Camera Raw preferences in Bridge I got message "Camera Raw not enabled...." even though PS had been started several times. I tried to update to ACR 5.5 but got same message. I installed it manually as per instructions but still same result. Cannot load jpg's into ACR. I do not have this problem on two XP and one XPx64 systems.
    Is this a problem with win 7?
    Thanks,
    Paul

    I don't think you can restore Adobe programs with Time Machine and have them work properly.  Can you uninstall, and install with disks?

  • 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.

Maybe you are looking for