ACR 6.3rc

I just installed ACR6.3rc to read some NEF files taken by Nikon D7000.  Everythings appear ok except that the Bridge App can only preview first 18 pictures in a folder.  Is this my system's problem, or a bug in the new ACR?  My system is Win7 (64bits).
Thanks!

Aw, shucks.
Glad it worked for you. Bridge is a bit flaky. It misbehaves a lot. Sometimes it needs a kick up the ****.
If you look at the top toolbars, to the left of the "Sort by" selector, there are two squares and a star. Click on the second square, and you'll see your preview/thumbnail generation options. "Embedded" switches off HQ thumbnail generation in favour of embedded thumbnails, "HQ on demand" generates HQ thumbnails when images are selected, and "Always HQ" generates a full set of HQ thumbnails as soon as you select a folder (and generates the biggest load on your system).

Similar Messages

  • ACR 6.3RC still makes Bridge display some TIFFs & JPGs overexposed

    I had the same problem with TIFFs & JPGs after upgrading from ACR 6.1 to 6.2. My system is Win 7x64 and, of course, PsCS5 and Bridge 4.0.39. This time the upgrade was from ACR 6.1 to 6.3RC. Not all images are affected. The problem seems to be entirely random. The amount of overexposure seems to be in the order of 1 to 2 stops. The problem is limited in this way for me:
    1. All the affected images display correctly exposed when opened in Ps and ACR 6.3RC (and ACR 6.2) hosted by Bridge.
    2. Only TIFFs & JPGs (both B&W and Colour) "derived" ultimately from original TIFF scans (both B&W and Colour) made on a Nikon SuperCoolscan 5000 ED are affected. The original TIFF scans (99.99% are 16-bit) are all unaffected.
    3. The problem does not occur with any TIFF or JPG file derived from native CRW or NEF raw files or from native JPG files produced in-camera (Canon EOS 300D and Nikon D700), all of which are themselves unaffected.
    4. It does not matter were you might be in an image editing process. Some intermediate edits to TIFFs (I never make intermediate JPG edits) are affected, others are not. Editing might start with the TIFF and continue with edits to the TIFF, and only some of the subsequent TIFFs (or final JPGs derived from them) are affected. For example, there might be 6 distinct edits to a TIFF and only edits 3 through 6 are affected. Editing might procede immediately from the original TIFF scan to PSD, finalise with PSD, and then, AND sometimes only, any TIFF or JPG made from the final, flattened PSD produces a file which Bridge will display overexposed. Only some files in a batch of scans, all made at the same time and under exactly the same conditions (almost always with no adjustments made with the Nikon scanning software), are ever affected - never all of them.
    5. Some of the edits to the original TIFF scans (where the edits were kept as TIFFs) were made with Picture Window Pro, some with Lightroom 1.3 (I think), some with ACR 4.x, ACR 5.x, but most were made with PS CS3, CS4 and CS5: it does not matter, there are some affected files from each. The problem certainly does occur with files which have never been opened, let alone edited, in any version of ACR.
    6. I have several instances where simply making a copy of a TIFF scan in another folder (whether the copy was made by Bridge or with Windows Explorer has no influence) results in the copy only and not the original being displayed overexposed.
    7. If a file is affected, all TIFFs AND all JPGs derived from it will be overexposed, never just one or the other.
    The overexposure problem detailed above does not occur with ACR 6.1. All the files affected by ACR 6.2 and 6.3RC are displayed with correct exposure by Bridge when ACR 6.1 is installed.
    I'm at a complete loss to understand what is going on. Any suggestions would be most welcome.
    Has anyone else who was experiencing the Bridge/overexposure problem with either ACR 6.2 or 6.3RC found a solution?

    This will be posted in both the ACR and Bridge User Forums
    I've done some experimentation and found a workaround for, not the solution to, my problem with ACR 6.2 and 6.3RC causing Bridge to display random TIFFs and JPGs overexposed.
    This is a temporary, and, if you have lots of affected files, a very laborious, individual file workaround. Unless Adobe investigates, finds and corrects the cause of the problem, it seems likely to re-occur. Only fixing the cause of the problem (which must lie in the new (different from ACR 6.1) code of ACR 6.2 and 6.3RC) could be be truly regarded as a solution.
    Here is how I enabled Bridge to display my affected TIFFs and TPGs correctly, that is, with no amount of overexposure. These steps apply equally to B&W and Colour images.
    For a 16-bit TIFF, duplicate it in Bridge (Edit/Duplicate) and then open the duplicate in ACR 6.2 or 6.3RC (ACR) hosted by Bridge. Make sure that all the sliders are zeroed in the Main panel and that the Amount slider in the Sharpening section of the Details panel is also set to zero (to avoid unwanted additional sharpening). Then open the image in Photoshop (Ps) and immediately save the image (Save As) over itself (yes, you're replacing the file) back in the folder from which you opened it into ACR, making sure to choose no compression. The resaved duplicate will now be displayed with its proper exposure in Bridge, and any further TIFFs or JPGs (whether 16-bit or 8-bit) derived from this file will also be displayed correctly. Following this procedure, my invariable experience is that I end up with a TIFF either the same size as or smaller than the affected TIFF.
    Why no compression? Strangely, if you choose LZW compression (really the only logical alternative to "None") you end up with a larger file than you get with no compression. I have no idea why. Why not simply fix the affected file instead of a duplicate? No reason really, other than safety. If things go belly-up you still have your original, albeit, affected file. I also intend to keep my affected files for awhile just in case of some possible desire or need to re-examine them in the future.
    For an 8-bit TIFF, although I don't have any which are affected, the procedure would be the same as for a 16-bit TIFF. You will need to conduct your own tests regarding compression/no compression and the resulting file size.
    For a JPG, the procedure is pretty much the same (duplicating, opening in ACR, zeroing all sliders, opening in Ps and then saving over itself) but when saving try choosing Maximum Quality (12) which mostly, for me at least, produces a replacement JPG the same size as the original affected file. Of course, you can choose a greater level of compression if you wish, and my tests show that this will not adversely affect the outcome. You can use the replacement JPG to produce further, derivative 8-bit TIFFs or JPGs and all will display properly exposed in Bridge.

  • ACR 8.3 doesn't work.

    CS6, Vista 64.
    Since the moment I have installed ACR 8.3 RC, ACR has completely stopped working, and ACR doesn't even appear in my list of plug-ins.
    My question is this one :
    Is it possible to remove completely ACR 8.3RC from my system, to be able to reinstall ACR 8.2 ?
    How can I do it ?

    Please email me at [email protected]<mailto:[email protected]>, and I will help you offline to get it up again. Thanks.

  • Cannot "Save in New Location" ACR 6.3

    Hello.
    I just installed the 6.3 ACR beta in order to accomodate the Nikon D7000 I just received today and find that I'm unable to "Save in New Location" in Bridge . I'm only able to save to the original location- The SD card. I set the folder, however nothing shows in the dialog box after folder selection as it usually does.
    I am using CS5 on 32bit Vista Home Premium. Could someone please tell me if this is a bug or if I have perhaps forgotten something? Had no problems up until this 6.3 candidate. Tried also saving files from my D80 but same problem.
    Thanks! 

    Hello David. Thank you very much for responding.
    To answer your questions:
    1). Yes. Mounting SD to computer via internal card reader.
    2). Yes. Navigating via Bridge.
    3). Yes selecting thumbnails on SD card images
    4). Yes. Right clicking for open in CR or double clicking to open in PS CS5.
    5). Yes clicking save image(s) button. When I do, I receive a "The file could not be created"
    meassage in the status dialog.
    6). Yes I am selecting "save to new location". Choosing the destination would always display the path
    next to "Select Folder" button afterwards but not anymore. The only option that will display the path
    is "Save in same location" which now appears to be the default.
    Yes, I have copied the files to my hard drive. I have opened both CR from Bridge as well as Bridge to PS with
    the same results. Another thing, I tried saving some Nikon D80 NEF files first thing this morning and it wouldn't
    save to new location. So it appears that this is not D7000 specific.
    I don't believe this is user error as I have processed tens of thousands of images similarly for the past few years.
    The problem started when I installed ACR 6.3RC.
    Again, thanks much for your response and any assistance you may offer.
    -syo

  • ACR 6.3 rc and PSE 9

    Does ACR 6.3 rc work with Elements 9?  When I try to install it, I get "Update is not applicable."

    f00sion wrote:
    That doesn't  make much sense.  Elements will get the release version of 6.3…
    The version that is eventually released for Elements will be as functionally limited as all other versions of the plug-in have always been when hosted by Elements.
    The RC version is mostly to provide preliminary support for new cameras, not for "testing" purposes in the sense of traditional beta testing prerelease programs, that's a different channel.
    f00sion wrote:
    …What would happen if I moved Elements to another machine already running 6.3 rc with LR and CS5?
    You'd be running ACR 6.2 hosted by Elements.  The install location of ACR 6.3RC for Ps is an entirely different one; Lightroom does not use the ACR plug-in at all and is totally irrelevant to this discussion or to any other topic in this ACR forum.
    Sorry, I replied because I was under the mistaken impression you wanted information, not to argue.
    Wo Tai Lao Le
    我太老了

  • Camera Raw 5.3 RC installs in Japanese

    I have downloaded and installed ACR 5.3RC to fix the problem of magenta highlights in Canon 5d mkii Raw files. The installation gave me no language options and installed in Japanese by default. How can I change the language or re-install in English - bearing in mind I cannot read Japanese (or is it Chinese?) so cannot change any preferecnes from within the installed version.

    I had the same problem on both of my machines (Macbook Pro, Power Mac). Dont know if it was specifically Japanese but it was an Asian version. I couldnt find a way around it via the installer and had to pull a copy of the English plugin from someone elses Mac.
    OSX 10.5.6, CS4 Master Suite, no previous localization issues, LR RC 2.3 running as expected.
    Ive reported it to Adobe.
    Greg

  • JPEGS Overexposed in Bridge but are actually OK

    Using ACR 6.2 & Bridge CS5 (v4.0.3.9)  After the most recent update  I started noticing that various jpegs & tiffs are really overexposed when viewing them in Bridge.  If  I open the file in Camera Raw or Photoshop it displays properly.  I can even open the file in Camera Raw and just hit the "done" button and then go back to bridge and the file will display properly.
    Not sure aht is causing it and I have a quick fix to open the file and close it but its a pain in the butt.  Is anyone else experiencing this?  I'm assuming its an issue with the most recent update because it just started happening after I did that.  It appears to only be a display issue and the actual files are ok but its troublesome when numerous files are displaying like they have been way overexposed.
    Anyone else have this issue or know how to fix permanently fix it?

    dfranzen adobe Employee wrote in post #7:
    "Until a fix is available for this bug, please try the following workaround. After cropping the JPEG in the Camera Raw dialog, select "Export Settings to XMP" from the fly-out menu in the Camera Raw dialog, then click "Done".
    Since you are looking into this ACR-crop-overerxposure problem, can I ask that you you also consider the overexposure problem discussed in the thread entitled "ACR 6.3RC still makes Bridge display some TIFFs & JPGs overexposed" in this Camera Raw thread:
    http://forums.adobe.com/thread/745757?tstart=0
    It seems to me that these problems are more than likely arising from a similar or possibly related cause, and fixing one may well have an influence, but not necessarily a "corrective" influence, upon the other.
    In this current "ACR-crop-overexposure" thread ("JPEGS Overexposed in Bridge but are actually OK"), I experience the same, but also additional, issues as the OP and other the posters, with the same versions of Ps and Bridge, but ACR 6.3RC instead of ACR 6.2, installed.
    In summary, these issues occur with ALL my JPGs and TIFFs, whether colour or B&W, whether native from the camera (Nikon D700 and  Canon EOS 300D) or scanner (16-bit TIFFs from a Nikon Super Coolscan 5000 ED and an Epson Perfection 4990), whether or not the JPG or TIFF has ever been prior-processed in ANY version of ACR, and even any JPG or TIFF produced at any time (intermediate or final) during an editing session where that image is "derived" from a raw file (NEF or CRW), a PSD, or a TIFF.
    1. Opening in ACR hosted by Bridge from Bridge (Ctrl+R), Crop, Done, back to Bridge:
    (a) - thumbnail displays roughly 1 stop (possibly more - difficult to estimate sometimes) overexposed;
    (b) - thumbnail displays the Crop icon (only - not the edited in "ACR icon") in top right corner;
    (c) - Develop Settings/Clear Settings: clears the crop, clears the Crop icon, but overexposure remains AND, WITH A COLOUR IMAGE, the Reds are oversatured - sometimes heavily so;
    (d) - Develop Settings/Previous Conversion (immediately following (c)): eliminates the overexposure, restores the ACR icon (but NOT the Crop icon), does NOT restore the crop, AND, WITH A COLOUR IMAGE, the oversaturated Reds remain.
    2. Opening in ACR hosted by Ps from Ps (File/Open As/Camera Raw), Crop, Done, back to Bridge:
    (a) - thumbnail displays NO overexposure, AND, WITH A COLOUR IMAGE, the Reds are NOT oversatured;
    (b) - thumbnail displays BOTH the Crop icon and the ACR icon in top right corner;
    (c) - Develop Settings/Clear Settings: clears BOTH the Crop and ACR icons, clears the crop, BUT, the thumbnail now displays the 1 stop overexposure;
    (d) - Develop Settings/Previous Conversion (immediately following (c)): eliminates the overexposure, restores the ACR icon but NOT the Crop icon, does NOT restore the crop, and colour images continue to display NO oversaturation of Reds.
    None of the abberant behaviour outlined 1. and 2. above occurs when ACR 6.1 is installed in place of ACR 6.3RC.

  • ACR/LR3.3 and Nikon D7000 - magenta color mismatch?

    I recently purchased the Nikon D7000. The NEF RAW files are not supported in current versions of LR and CS5.
    Downloaded and installed LR 3.3RC. Also downloaded and installed ACR 6.3R1.
    Both work with the D7000 NEF-files with ONE exception. If I shoot a "Multiple Exposure" (one feature of the D7000)  the resulting image in both LR and ACR displays in strong "pink"/magenta. All other images display correctly.
    If I open the pink images in Nikon Capture NX2 2.2.6 they open correctly.
    If I use the White Balance tool (pipette) in LR, I can bring the image back to "almost normal" but the WB values then are Temp: 2150, Tint: -138. Conclusion: the Multi Exposure Image from the D7000 is completely mismatched by LR/ACR. But they are correctly matched by Capture NX2.
    This obviously needs to be corrected before final release.
    Has anyone else expreienced the same? Is there a workaround?

    Might be better to post this over here:  http://forums.adobe.com/community/cameraraw
    -Noel

  • LR/ACR color mismatch with Nikon D7000 NEF files

    I recently purchased the Nikon D7000. The NEF RAW files are not supported in current versions of LR and CS5.
    Downloaded and installed LR 3.3RC. Also downloaded and installed ACR 6.3R1.
    Both work with the D7000 NEF-files with ONE exception. If I shoot a "Multiple Exposure" (one feature of the D7000)  the resulting image in both LR and ACR displays in strong "pink"/magenta. All other images display correctly.
    If I open the pink images in Nikon Capture NX2 2.2.6 they open correctly.
    If I use the White Balance tool (pipette) in LR, I can bring the image back to "almost normal" but the WB values then are Temp: 2150, Tint: -138. Conclusion: the Multi Exposure Image from the D7000 is completely mismatched by LR/ACR. But they are correctly matched by Capture NX2.
    This obviously needs to be corrected before final release.
    Has anyone else expreienced the same? Is there a workaround?

    Can you please supply some sample .NEF images? You can use YouSendIt.com with a target email address of [email protected] Thanks.

  • ACR and SonyA580 - when?

    Hello!
    Several days ago purchased new camera and now wating for new version of ACR. It as very sad that there is no Sony in 6.3RC - wiil it be in fullversion?
    And btw - why so little Sony lenses support frome Adobe - all profiles in my system fan-made - no one from Adobe
    (My lenses - Zeiss 16-80 and SAL 70300G)

    FYI, Apple just released an update for Mac OS x 10.6 (.5) which adds support for the a580 RAW files. So you can check out your RAW files in Apple Preview or iPhoto for the time being. Well, if you're a Mac user

  • Can you temporarily overexpose a pixel in ACR?

    I was working on some images the other day when it occurred to me that I was influencing some of the pixels brightness in several different ways: using the Exposure slider, the Recovery slider, using an exposure Gradient, using the Adjustment Brush, etc., each one making some exposure compensation.
    I assume the order in which the controls are laid out doesn't necessarily represent the order the different controls' process settings are applied, but what started to worry me was a scenario in which one setting pushed exposure over 100% (i.e. clipped) before another brought it back down again (still clipped).
    So, what I'm trying to ask is: is there a combination of exposure settings to avoid? For example, is it a bad idea to boost the exposure in the basic panel only to reduce it again with a gradient - or would it be better to use a negative gradient instead? That's just one example; are there any other potential pitfalls with different combinations, or does ACR work around this problem with some clever jiggerypokery?

    The preview image is re-rendered using the entire combination of settings every time you move a control.
    If you move one control (e.g. Exposure) and that leads to a block of pixels being "whited-out", then you move another control (e.g., Recovery) that undoes that condition, then you haven't "overexposed" anything.
    Move the controls around freely until you like what you see in the preview and histogram, then press Open or Save.  It's really as simple as that.
    -Noel

  • Adobe Bridge CS4 will not launch ACR

    I'm getting this message when trying to open an image from Bridge CS4 in ACR,
    "Camera raw requires that a qualifying product has been launched at least once to enable this feature"
    Any ideas how to cure this, I've downloaded the update 5.2.2., what is the correct location for this? Automatic update is just opening a box withe file in and I cant find the previous.
    By the way ACR opens fine from Photoshop CS4.
    Thanks
    Philip James

    Philip:
    This has been discussed in the Camera Raw Forum: you may need to install the new ACR 5.2 plug-in in the correct place manually.
    Eric Chan, "ACR 5.2 not installing in CS4" #1, 30 Nov 2008 9:17 am

  • Bridge CC and ACR unbearably slow

    Upon researching the issue of a slow Bridge CC I realize I am not alone nor is this a new problem. The thread I read extensively is almost a year old. Despite paying for CC for about 9 months I still use CS6. I had hopes that the new 2014 CC would solve the bridge performance issues.
    I am running a six-core system with 32 GB ram, an SSD for my OS and programs, an empty 1.5 TB drive dedicated to cache, on a win 7 - 64bit OS. Bridge CC and camera raw are so slow I can't use them.  My only comparison is CS6 and using the same settings for both programs.
    When opening bridge CC to the folder that was previously cached and loaded used it took ~51 seconds of "building criteria" before i could view the file types, ratings, and details in the filter box. In other words I do not see any information in the filters box for that time. I made sure that the thumbs were completely loaded into the cache before I closed Bridge CC and opened the program to the same folder. The same folder in Cs6 takes ~4 second to load..
    I have performance issues in ACR too.
    I batch edit in ACR like out lightroom counterparts do but Bridge CC Plus ACR are too slow to work with.
    I selected the same 20 raw files in each case.
    bridge CC camera raw 8.5 took 5 seconds of a watch icon  to load the files into the camera raw dialog after hitting CTRL R
    No edits or changes were made to the files.
    when i click to the next image in the list (still in camera raw) it takes  0.5-1 second of the watch icon to load the next raw photo in the batch.
    in CS6 I selected the same 20 unedited RAW files, CTRL R and they immediately load. I can switch from raw file to RAW file without any hiccup or delay. 5 seconds vs instant. I didn't build a six core system to wait for things to load.
    not exactly scientific but that's the disparity I am seeing. Bridge CC is death to me. To make sure I wasn't crazy I clicked on a recent folder with only 80 raw files, 80 respective small jpgs and a couple video files (4.5 gigs of data). It took so long I freaked out that I had moved the files to a backup location instead of copying them. After 30 seconds I stopped counting, opened windows explorer, browsed the backup folder, copied the files and was about to paste them to what should have been the original location and then Bridge decided that it was ready to work. For that ~ 60-85 seconds there was no watch icon, no spinning circle or "building criteria". It just looked as if I was browsing an empty folder.
    Any suggestions?

    c. Once you post something that's helpful I'm sure someone will give you a thanks, until then stop trolling these boards - your name was all over that thread with useless and unhelpful information
    Well mister Chuck 'know it al', you can congratulate yourself. With just 2 posts in the past year and no points for helpful answers at al you come in hard and call one of the most helpful posters a troll.
    This was the limit for both of us, we had to stand a lot, including no help from Adobe but a more crippled forum website after each major upgrade. No possibility to place FAQs, a lot of people screaming for help without taking the effort to look first for similar problems, almost never providing correct details, crucial for a mixed Mac/Windows forum.
    We had to suffer a lot, getting in unpaid and just plain users like all other guests, only it did cost us a lot of spare time.
    But now we can rest from this task because mister Chuck "know it al" has jumped in to the rescue.
    I wish you good luck and pity your friends and family, it must be a difficult task to live with such a nice person.
    Goodbye to you all!!

  • New update 8.7.1 CS6 ACR not working---(I own hard copy not a Trial or part of CC), I purged cache in bridge, and photoshop. NO photos will open when I double clik, or  will not open again in ACR alone.  When I double clik on raw file I get Sign In requir

    I purged cache in bridge, and photoshop. NO photos will open when I double clik, or  will not open again in ACR alone.  When I double clik on raw file I get Sign In required Notice--We will now register your TRIAL to your Adobe ID-------I am alread a SUBSCRIBER-------------Yes I get this same issue in Creative Cloud and same issue. error: Camera Raw editing is not enabled-----Camera Raw editing requires that a qualifying product has been launched at least once to enable this feature. These errors are happening inside both CS6 Bridge and CCphotoshop Bridge------NOTE----I am ALREADY signed into Creative Cloud and still get those message errors.........Need to fix ASAP.

    When you sign in to Adobe.com with the user ID and Password your using in the Creative Cloud and Photoshop does this link  https://www.adobe.com/account/my-products-services.html show that the account has a subscription?
    Also this is a user forum not a Adobe Customer Services web site.

  • Adobe XMP Files not deleted with Raw Files in ACR

    I am using Photoshop CS3 on a Windows XP platform. My camera raw files are mostly kept on a Windows 2003 file server, which has a gigabit connection to my workstation. However, I have the same problems when using PS CS3 on my Windows XP laptop.
    I take many hundreds of 'technical' photographs using an Olympus E1 and Canon G9 cameras. I usually bracket the exposures on the E1, specially when photographing white painted yachts, and then rate and select the images that I want in ACR 4.1.1. Unwanted images are deleted at this time.
    The problem I am having is that the associated *.xmp files are not always deleted with the camera raw files, with the result that I now have literally thousands of these 'orphaned' files cluttering up the server. The only options I have are to delete the files manually, which is a pain, or to leave them on the server, wasting unnecessary space.
    I have the same issue with Canon and Nikon raw files, so this problem is not specific to Olympus files.
    This is a long standing problem, and I would be grateful if anyone has any answers?
    If any Adobe programmers are watching, it would be handy if you could provide a simple utility to delete orphaned *.xmp files, or at least compress them into some kind of archive.
    Thanks,
    Nigel.

    [quote] As far as Photoshop and ACR go, ALL raw files are treated as read-only.
    Your original raw files remain untouched, no matter what you do to them.
    Any adjustments you make to a raw file are kept only as metadata (flags, if you will) in that XMP side-car file. Every time you want to re-open that raw image file, ACR will reach for the XMP file and apply the adjustments automatically, transparently. [/quote]
    That is not quite correct. Camera RAW files can be permanently deleted from within Adobe Camera Raw. The problem with ACR 4.1 to 4.4 4 was that the XMP files were left behind. This now seems to have been rectified in the latest version (ACR 4.5).
    Thank you Adobe!

Maybe you are looking for