Disappearing slider adjustments

All my photos are jpgs and all my photos are stored in the iPhoto database.
One thing I noticed -- sometimes when I adjust a photo, leave, and then come back, the photo still reflects the adustments, BUT the slides are all not set back to zero/baseline. For instance, if I up saturation to the right, and go away and come back, I find the picture shows the increased saturation, but the slider is now in the middle.
Other times, the sliders keep the position that I left them at. It MIGHT be that the sliders are staying where I left them on my iMac (with Tiger) vs. resetting to the middle on my MB (with Leopard). Today, I was working on both, and that's the difference, though I've seen this behavior before, and I just can't remember if it's always been that clean a split.
Has anyone else seen this behavior? I'd prefer to keep the slides at the position I adjusted them to, so I could reset just that slider, if I wanted to, without have to revert back to the master pic.
Message was edited by: bk1000

All my photos are jpgs and all my photos are stored in the iPhoto database.
So, I wouldn't really know on the RAW shots.
I have some more behavior information, though.
First, let me say something on workflow. I usually crop to reframe the image. If I crop, make adjustments, then come back to the picture and decide I want to twiddle with adjustments -- if the sliders are set back to baseline, then I have to "revert to original" and I lose ALL my cropping, too. If, however, the image retains the slider settings, I can use "reset" on the adjustments HUD, and reset my adjustments without losing my cropping.
Also, thinking more about this -- I edit in full screen. Maybe it's different than other editing options?
Any rate, one thing I did notice on my MB with Leopard -- sometimes when I edit a picture and the navigate to the next picture, I get this dialog box that says "saving" with a progress bar. That's when the sliders revert to baseline. Other times, when I edit I don't get that box, and the sliders stay where I left them. I haven't been able to figure out what triggers this dialogue box and this behavior. It seems to be a bit random. I was getting this "saving" behavior this morning quite a bit, but now it's reverted back to keep my sliders in position. Very frustrating.
Any ideas?

Similar Messages

  • Shortcut for 1 point Slider Adjustments?

    Hello,
    Is there a way to get a shortcut for smaller slider adjustments?  I am using LR 3.5 and the smallest I can get is 10 points at a time.  This is a little too big of a jump for all situations
    Thanks for your help!
    P.S.  Why can't one search individual forums anymore?  It took forever to get this and now it is gone again?

    Unless you are creating Photographic Test Image files set to an exact luminance level for calibrating equipment, there is no need or value in setting Exposure in increments finer than 0.1 or as you say 10 point increments. There are no monitors and/or printers that can come close to holding that degree of  luminace accuracy (0.1 EV), except perhaps in a NASA laboratory environment. You are wasting your time splitting 1/10 of an EV – No one will ever see it!
    "I mainly want small adjustments with the exposure slider as a few points here or there can help skin tones."
    If you are seeing more than the very slightest change in luminace (i.e. brightness) when changing the Exposure slider by a 0.1 (i.e. 10 points), you have either a defective monitor or improper monitor setup and calibration.
    What type of monitor are you using and how are you calibrating it?

  • On Screen Keyboard Glitch in Tablet Mode - On Screen Keyboard minimizes / disappears / slides down

    Hi there -
    New Yoga owner here ( just bought it yesterday) and within minutes of setting the computer up I noticed that the on screen keyboard was malfunctioning when the yoga is in tablet mode. Specifically, it pops up for about a second and then, without me touching or clicking or doing anything, it quickly slides back down. repeated attempts to bring up the keyboard end up, frustratingly, with the same result. what is perplexing to me is the on screen keyboard works fine in laptop mode (when I need it least).
    Someone else already started a post on this BUT it was marked as 'solved' (which it wasn't) so I figured I'd start new thread. The solution on the previous thread was to simply 'refresh' windows to get rid of any new drivers that were downloaded since purchasing the yoga, but I did not download or update anything prior to this problem arising (as I said, the problem seemed to occur within a few minutes of turning the machine on for the first time). In any case, I tried the refresh and it did not work so clearly my problem is not that I downloaded an incompatible or faulty driver. Please Help! I love this machine and I'm trying to see past the other flaws I've noticed so far (subtle screen flickering, inconsistent touch sensitivity etc), but this issue is starting to really undermine my confidence in the product quality and, from a productivity standpoint, it is a real deal breaker to not have full tablet functionality.
    Solved!
    Go to Solution.

    I had the same problem with the disappearing virtual keyboard within hours of starting to use my new Yoga 13.  I read somewhere that it was a problem with an incompatible Synaptics driver, and when I looked in the control panel, it showed that the Synaptics driver had been updated on my Yoga as of the day I bought it.  I think somehow by agreeing to automatic updates of the software, the Synaptics driver is updated to an incompatible version.   So what I did was I removed the Synaptics driver, using the Windows program uninstaller tool, rebooted, and then found the Synaptics driver at the Lenovo site which is specifically labelled as the Yoga 13 driver.  I installed that, and the keyboard is now working fine.    

  • Disappearing slide show...

    I created a page and inserted a lightbox slideshow - using the new software out today.  When I preview on catalyst, the main screen doesn't appear but the thumbnails do.  When I click on a thumbnail they disappear and the main screen comes back. 
    I see no apparent controls for this. 
    Appreciate any ideas.

    This is what a Lightbox slideshow does. The term Lightbox indicates a window that "pops up" over the top of the page to show the image or content over the top of the existing page. It is a common web paradigm, and is what the Lightbox Slideshow is supposed to do. If you don't want this behavior, you can use one of the other slideshow types, or change the options of your existing slideshow by modifying the options. The options are available by selecting the slideshow, and clicking on the little blue arrow that appears next to the selection. In the popup dialog there, you can modify the options of the slideshow, including whether or not it is a Lightbox type slideshow.
    Hope that clears things up.

  • Fine tuning for White Balance has disappeared from adjustments

    Went to edit photos this morning only to find I could not change White Balance.  The label is there, but that is all. I did a hard reset, permissions repair, re-install latest update, restarted numerous times....still not there.

    Yes, other edit options are fine, and I have used Aperture consistently for over two years, have never had this happen before.  Here is what I am looking at.

  • New Mac Pro and 9.2 Hangs on Adjustments?? Old G5 Doesn't

    Hello
    I have what should be a very fast new Mac Pro.  6 core at 3.46Ghz.  48Gb of RAM.  Solid state boot drive.  Software RAID 0 with 2 Hitachi 3TB drives, hardly anything on them yet. Nvidea Quadro 4000 CUDA card.  Everything installed and burned in for the overnight 8 hour test with the MPG workstation program at OWC.  Lion 10.7.2.
    I had approximately 700 in camera photos combined still in camera between an up-to-16MP Sony NEX 5N camera and up-to-24MP pics on a Sony A77, that have already been loaded into my 6-7 year old 2.4Ghz dual core G5 with 6.5Gb RAM and much older version of iPhoto. OS 10.4.7 I believe. 
    Last night I loaded all those same pictures into the new machine and 9.2 version iPhoto.  And then deleted them from the cards on both cameras.  No issues. Smoking fast imports compared to the G5 which wasn't all that bad.
    On the G5 with the picture adjust controls I could use the slider to go deeply into those same photos and see the effects of contrast, sharpness and all the other options.  Like butter.  Make the adjustments while in that deep if desired and then pull back to evaluate the overall picture before saving.  Or back in again if desired. No issues.
    With the new rig I couldn't wait to try all of this, but once I go deep inside and start to move the adjustment slider controls the system every time starts getting hung with the spinning wheel.   Have to wait and wait for them to catch up to the curser on that adjustment.  Most of the time the system then will just get stuck and I have to force iPhoto to quit.
    Please....does anyone know why all this latest powerfull hardware and software is doing that, compared to the old, much less capable G5?  I am really concerned now.  Haven't had a chance to get Photoshop and the other production premium software tested yet.
    And one last question please.  Does anyone know if the "Enhance" feature in the Quick Fixes section adjusts Gamma as well?  There seems to be a lot more going on to give the photos depth (what I always really try to do)   than the sum of the small slider movements in the Adjust section.  With my old system and iPhoto version there was no "Gamma" adjust slider in iPhoto proper......but if I saved a photo first to my Desktop for instance, and then called up the adjustment features, there was a Gamma slider there.  Very handy and appreciated.
    I see similar vast improvements on some photos now with the "Enhance" feature that looks like maybe Gamma has been optimized as well?  There now is no Gamma slider available even if the photo is taken to the desktop first.
    Thanks much
    Ron

    Hello Terence
    Thanks for the tip to try.  Couldn't get to it until late last night.  Seems to still be the same in Library 2.
    Also seems to be worse with 27" Cinema Display at full resolution.  And with several sliders on adjustment.  If I drop the resolution to 1920 x 1080 or 1600 x 900 and move smoothly about it is not as apt to hang up.  With as much horsepower as the new Mac Pro has, should resolution of monitor be an issue in these adjustments deep into the pictures?
    How about the Enhance button?  Is gamma involved?  Everything I read about it on searches only talks about boosting saturation of the color and fine tuning with little other slider adjustments.  But on a picture where it has made a big difference to the good with depth and overall look, if I look at where the sliders were adjusted and then undo the enhance, and go back and manually put the sliders in the same position it doesn't look the same.
    Does anyone know if gamma is being adjusted with this button?  Sure seems like it but can't find it mentioned anywhere.
    Thanks again!

  • Performance gets worse with more adjustments

    LR 3.5, Win7, 64-bit (both OS & LR - and yes, I made sure it is the 64-bit LR running), 8GB ram
    When I start doing adjustments to a photo it's really fast, no problems. But the more adjustments I add (mainly adjustment brush), the slower LR gets, the worse performance gets.  It gets so bad that making a change to a slider can take 6+ seconds to see the change!
    I'm making slider adjustments, using the adjustment brush a lot, and graduated filter adjustments.  I have auto mask turned off, my raw cache is 10GB, the raw file is 16.7MB.
    If I switch to a different photo everything is speedy again.  Switching back and everything is slow.  Closing & reopening LR has no affect, neither does rebooting.  I haven't tried creating a new catalog and putting that one photo there but I doubt that would help.  I do not have Photoshop or any other memory/cpu intensive programs running.  I actually did try to quit everything and that didn't help.
    I asked this on the NAPP forums and someone suggested:
    - Is it a Raw file or Tiff or Jpeg?
    Raw.
    - Cache may be corrupt, try to purge the cache.
    That did make a difference, but it's still quite slow.
    - Delete your history?
    I haven't tried this yet mainly because the I'm still making adjustments to the photo in question and I love being able to go back a bunch rather than having to start over again.  I plan on doing a bunch of similar adjustments to another photo then deleting the history and seeing if that helps.  Still, that's not something I want to be doing WHILE I'm still editing the photo.
    - Open the task manager and watch the cpu/memory.
    Did this and noticed when I made ANY change on a photo with lots of adjustments, both cpu and memory went up - cpu hit 85-95% doing anything and memory climbed from the 1.8GB it had when it started to 2.8GB.  If I go to a new photo cpu stays around 40-50% and memory stays lower, around 2.2-2.4GB.  And again, the more adjustments I added, the highter the cpu and memory went.
    And it isn't just this photo.  I've worked with many photos - both mine and from others - and as I add more and more adjustments (brush, sliders, etc), LR starts slowing down more and more.  I also have LR installed on my work computer and my personal computer, both share the same performance issues.  It's just when I get a LOT of adjustments made that this happens - mostly adjustment brushes.
    Any thoughts?  Thanks very much!!
    From System Info in LR:
    Lightroom version: 3.5 [775451]
    Operating system: Windows 7 Ultimate Edition
    Version: 6.1 [7600]
    Application architecture: x64
    System architecture: x64
    Physical processor count: 2
    Processor speed: 2.6 GHz
    Built-in memory: 8179.8 MB
    Real memory available to Lightroom: 8179.8 MB
    Real memory used by Lightroom: 2732.6 MB (33.4%)
    Virtual memory used by Lightroom: 2806.3 MB
    Memory cache size: 848.9 MB
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1680x1050, 2) 1680x1050
    Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom  3.5
    Library Path: C:\Users\uchytil\Pictures\Lightroom\Lightroom 3 Catalog.lrcat
    Settings Folder: C:\Users\uchytil\AppData\Roaming\Adobe\Lightroom

    Pic4,
    I would think that it's the same problem on Mac. As Lee Jay has explained "Simplistically, it has to redraw all the local adjustments every time you update a slider" these adjustments create o lot of traffic between your hard drive(s) and the memory. So - simplistic - if all the traffic has to go back and forth to the same hard drive, there's congestion. So better, divide the various LR "elements" between different physical hard drives.
    Put your catalog on the external eSata - assuming that LR resides on your internal drive - and make your cache very large.
    I'd like to put in a word about hard drives: Instead of choosing one (1) huge internal drive it would be better to have at least two, or better three internal drives that can be much smaller. I'd say three drives @ 250 GB give you much better performance than one drive with 1 TB.
    With three drives, you'd put LR on drive 1 (C-drive), the LR catalog on drive 2, and the LR cache on drive 3. That way the system does not have to wait for one drive to finish writing before it can be read again (in simplistic terms) but the writing and reading happens simultaneously on three drives. That's the performance gain when you put the catalog, the cache and LR on different drives. It has to be different physical drives, partitions of one drive won't do it.
    I would think that it's the same on a PC or on a Mac.
    WW

  • Lightroom 4 performance issues

    Hello,
    Months ago I switched from Aperture 3 to Lightroom 3 and quickly fell in love with the program.
    I switched due to constant freezing and crashes in Aperture 3. I invested time and money to learn Lightroom 3. Performance in Lightroom 3 was superb. Anything I would do with regards to any type of adjustment gave instant results on the screen. Program never crashed or froze onec. Quite frankly, I was shocked in a very positive way.
    This was on Macbook Pro i5, 8GB RAM, Hi Res Antiglare screen with Snow Leopard.
    I purchased Lightroom 4. I did a clean install of OSX Lion and, clean install of LR4. New catalogs, no importing of anything. LR 4 is sooo slow. It works just like Aperture 3 worked, the  precise reason that made me dump it.
    The longer LR4 is opened, the slower it becomes. The more adjustments are applied, the slower it becomes. I will use brush and I have to wait to see results. I can't use brush. It takes me 15-30 min to brush small part of the image. I will slide adjustments and wait. I will click on crop tool and wait, wait, wait. I really love this program but I just can't work like that.
    Would anyone share some light or advice on what could be done, on what is going on?
    Thank you.

    Rob,
    I am working with NEF files and have done so in LR3. I understand from some reading that one of the benefits from converting files to DNG is that they are faster to work with. So I just copied one of my NEF as DNG and I have been working on it for about 15 minutes applying brush after brush and other adjustments to see if LR4 will slow down. Thus far it has been incredibly faster. I will continue to work on this one image and maybe convert few more to DNG to test but do you think that there might be some issue with NEF format? Another bizzare thing I just noticed is that when I open NEF image, my memory quickly goes up to over 3GB and that's not even during applying adjustments. Working now with DNG, memory is just around 1.3 GB. WHAT IS GOING ON HERE???
    I wonder what type of files are other LR4 users that are reporing performance issues working with.
    Please share your thoughts.
    Thank you.

  • RGB, Luminosity, and Black Point

    I have an image shot in a forest, with a footbridge over a stream and a path in it. It has a lot of green, naturally, and a few blown out places in addition to dark shadows. While I like it, I've always found it a little flat.
    Looking at the histogram under levels adjustment, the left side of the "mountain" is right up against the zero point of the graph, so I never bothered to try tweaking it.
    But yesterday I noticed that, if I use the histogram palette and change the drop-down box to "Luminosity", then the left side of the mountain is a bit to the right of the zero point on the graph. Curious, I switched to the levels adjustment, selected the black eyedropper, and clicked in the darkest part of the image that I could find. The colors became much deeper -- especially the greens -- and even the blown out parts look better. Some of the shadows are maybe a bit too dark, but overall it's a nicer photo. And I noticed that on the histogram palette, the luminosity mountain is up against the zero point of the graph now.
    So, finally my questions. What exactly is luminosity? And is it always preferable to use the black eyedropper rather than the little slider on the levels adjuster, as I had always done before? Is there a way to see a luminosity "mountain" in the levels adjuster, rather than just RGB or the individual colors? And for that matter, what is RGB?

    "What exactly is luminosity?"
    Luminosity is a representation of the brightness of an image separate from the color/hue. A histogram of the luminosity will show a pretty reliable map of the tonal range of an image. Adjusting the range of the red, green and blue histograms so they cover a full range of tone may be a better correction in Levels than using Luminosity mode as the r,g,b sliders will correct for some color casts and shifting that luminosity will not.
    "And is it always preferable to use the black eyedropper rather than the little slider on the levels adjuster, as I had always done before?"
    I would stick with the slider adjustments. The eyedropper is convenient, but not easy to control, and not as accurate.
    "Is there a way to see a luminosity "mountain" in the levels adjuster, rather than just RGB or the individual colors?"
    If I think about this, there might be an easier way, but this will give you the right view of the histogram:
    1. Create two new layers at the top of the layer stack for the image you are working on. Name the bottom of these two layers Commit and the upper Source.
    2. Activate the Source layer and stamp visible to the layer (Ctrl+Alt+Shift+E/Command+Option+Shift+E [PC/Mac]), then set the layer mode to Luminosity. At this point the image will look the same.
    3. Activate the Commit layer and fill it with 50% gray (Use Edit>Fill Layer). After the fill the image will appear to be grayscale.
    4. Activate the Source layer again and merge down. Name the resulting layer Luminosity.
    5. Create a new Levels adjustment layer and view the histogram. You will see that this result is a somewhat different representation than you get from the RGB graph.
    "And for that matter, what is RGB?"
    RGB is red, green and blue...it is a light-based color model where the set of these three colors mixed in different amounts make up the total set of available colors. 100% of red, green and blue is white, 0% of each is black and even amounts of each is gray (at varying brightness depending on the percentage). RGB theory is what much of digital imaging is based on and much of what my book relies on to help people with color and other corrections.
    Richard Lynch

  • Aperture on a Dual 2 Ghz G5?

    What is the performance of Aperture on a Dual 2 Ghz G5? It is outfitted with the GeForce 7800GT video card and currently has 2.5GB RAM. I plan on updating to 4.5 shortly. Will the RAM upgrade speed things up? I have downloaded the trial and w/@1000 D2X RAW files things are not too quick.
    When making slider adjustments there is a very noticable delay before the changes register. In full screen mode the loupe, (which I love) is jerky when viewing modified files, seems smooth on untouched files though.
    Am just wondering if there would be a noticable difference with additional RAM installed?
    Dual 2 Ghz G5 Mac OS X (10.4.8)
    Dual 2 Ghz G5 Mac OS X (10.4.8)
    Mac OS X (10.4.8)

    I use iView Media Pro as my DAM of choice and you can get a 30 day trial. All of my images are referenced on a I TB Maxtor external drive. Both Aperture and iView reference the same drive. Many of my images are 65 MB Tiffs that were scanned from slides and sytem performance is pretty good. You can see I have a G5 dual 2.5 with 5.5 GB RAM. I don't believe processor speed makes that much difference with Aperture. It does appreciate more RAM. If you plan to edit in an external editor at times, or if you normally have several programs open at once the extra RAM will make a noticible difference.
    Jeff

  • Aperture , RAW Engine v6 and X-Trans?

    What do we know, or how can we find out, what Aperture is up to with Fujifilm X-Trans RAW files?
    We “know” that two of Aperture’s weaknesses are the lack of lens correction tools and less-than-state-of-the-art noise reduction control.
    As best I understand it, Fujifilm includes lens correction data in their RAW files and decoding them results in files with Fujifilm’s corrections (distortion, chromatic aberrations, etc.) already fixed. That might be one weakness down. Is it true that Aperture does this?
    The X-Trans sensor has pretty good low noise performance resulting in less noise at fairly high ISOs. So less noise reduction is needed. That looks like another weakness down.
    Is there an objective source of information on how well Aperture handles X-Trans RAW conversions, especially on these two specific points, versus the competition (Lightroom and Capture One, mostly)?
    What do folks on this forum know?

    This post by Eric Chan from Adobe  is very imformative and reveals the reality of processing of raw files  not only from Adobe's perspective but for all software that processes  raw files from digital cameras. The thread is concerning Adobe's  processing raw files from a Panasonic Camera model in comparison to the  Camera's JPEG rendition.
    I guess the same would hold good for the possibility of improved profiles for other cameras including the Fujifilm cameras.
    "Sorry for joining this thread late.
    Unfortunately  this is a limitation of our current color profile process. This  limitation actually applies to all of our camera models that we support,  not just Panasonic. What is happening is that the color transform we've  built is optimized mainly for daylight and incandescent light  conditions, but when applied to scenes with bright light sources  (especially neon lights, and especially blue/purple lights), the  transform will tend to oversaturate and clip those colors.
    My  team is investigating how to build better profiles going forward, but  in the meantime, my main suggestion is to try reducing the  Red/Green/Blue Saturation sliders in the Camera Calibration panel (not  the HSL tab, and not in the Basic panel). This will help to reduce the  oversaturation and clipping, and will give you a better starting point  for further edits (Exposure, Contrast, etc.). As a shortcut, you can  store your Red/Green/Blue Saturation slider adjustments as a preset that  you can then apply quickly to other images you have that show the same  issue."
    Link to the actual thread.
    http://forums.adobe.com/thread/1254354?start=40&tstart=0

  • Develop Module and Preset Application

    I would love a way to apply my general adjustments to a copy of a photo and reset all adjustment sliders so I can then consistantly apply a Develop Preset.  I have a large number of develop presets that provide me with particular "looks" I use a lot, but these are not "relative" to the global adjustments made correcting the original photo, i.e. exposure, brightness, contrast, etc.  If my photo has these global adjustments made to it and then I apply a preset, it never looks the same as the previous photo I used that preset with.  Even if I make a virtual copy the original slider adjustments are maintained rather than reseting them to a neutral starting point.  Right now, I export my photo as a PSD file to PS and immediately close it and then apply my develop preset to the PSD file to get consistant results.  This is the same reason why people have to develop RAW and JPG presets, which is double the work.

    Not sure if you found a solution or an efficient way to "export" your photo to psd (seems like you "edit in photoshop" and just save) but you could build an Export preset with these options
         same folder as original
         check "add to this catalog"
         existing file = choose a new name for the exported file
         filename = custom text + filename (to end up with something like COPY_originalname.psd)
         file settings / format = PSD or TIFF
         rest leave empty (or as per your preference)
    If you have a large number of files to export, you can go for a coffee (or a full lunch) while it exports. Then you can apply your develop presets to the new image.
    Additionnally you can create a smart collection with filter = filename starts with your custom text (i.e. "COPY_" in the example) to access your copies quickly
    Hope this helps

  • Does Camera Raw 5.6 Update work for PSE 6?

    I have a PSE6, and have bought a Canon Powershot G11.
    Camera Raw update 5.6 includes the Canon G11, but the update documentation seems to suggest it can't be applied to PSE 6 on Windows:
    Camera Raw 5.6 update page:
    "The Camera Raw 5.6 plug-in is not compatible with versions of Photoshop earlier than Photoshop CS4, versions of Photoshop Elements earlier than Photoshop Elements 6.0."
    But the ReadMe file says:
    "The Camera Raw 5.6 plug-in is not compatible with versions of Photoshop earlier than Photoshop CS4or versions of Photoshop Elements earlier than Photoshop Elements 7.0 for Windows and Photoshop Elements 6 for Mac."
    Am I right in thinking that my one-year-old copy of PSE6 (Windows version) is no longer functional with a new camera?  Or am I mistaken?
    Advice appreciated -

    Some of the Adobe download links are wrong and often take you to an earlier version of Adobe Camera Raw. The latest version is ACR 5.6 which brings support for the newest camera models such as the
    Canon EOS 7D, PowerShot S90 & G11, Nikon D3S and others.
    So don’t worry it will work. First you will need to exit Photoshop Elements.
    To get the plug-in for PSE6 go to the link below - instructions are for Windows users. They will differ for Mac users.
    http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=4626&fileID=4303
    Download the plug-in for Elements 8
    Open the zip folder you just downloaded and click Extract Files.
    You should see a 64 bit folder and a plug-in file below it. The plug in has a file name: Camera Raw.8bi
    Now drag the plug-in file (or copy it) into the File Formats folder in the following location:
    C:\Program Files\Adobe\Photoshop Elements 6.0\Plug-Ins\File Formats.  See Gotcha
    If running windows Vista you will probably get a pop-up requesting Administrator permission. Assuming you are the Administrator for your computer, simply agree.
    I can confirm it does work as I have recently updated my plug-in for PSE6 using the above method. To test it, go to one of your photo folders, right click on a raw file (NEF, CR2, DNG etc) and select open with Photoshop Elements. The image should automatically open in ACR 5.6 giving you access to the latest slider adjustments, including white balance and exposure.
    Note: If you have an earlier Camera Raw plug-in, I suggest you move it from the File Formats folder to My Documents before you begin. This will prevent it being overwritten by the new Camera Raw file (it will have the same name) and you can always move it back again if the download installation fails.
    If you are using a 64-bit edition of Windows, then move the plug-in file from the unzipped download folder by navigating to:C:\Program Files (x86)\Adobe\Photoshop Elements 6.0\Plug-Ins\File Formats.

  • RAW conversion for Canon 5D Mark II

    I can't open my raw files from my Mark II I have PSE 6 and have upgraded my raw conversion to 5.2 it still won't recongnize my .cr2 raw files from my Mark II it recongnizes my .cr2 from my 40D whats up?

    Some of the Adobe download links are wrong and take you to an earlier version of Adobe Camera Raw. The latest version is ACR 5.6 which brings support for the newest camera models such as:
    Canon EOS 7D, PowerShot S90 & G11, Nikon D3S and others. It’s also backward compatible and will support all earlier models including the EOS5DmkII.
    First you will need to exit Photoshop Elements.
    To get the plug-in for PSE6 go to the link below - instructions are for Windows users. They will differ for Mac users.
    http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=4626&fileID=4303
    Download the plug-in for Elements 8
    Open the zip folder you just downloaded and click Extract Files.
    You should see a 64 bit folder and a plug-in file below it. The plug in has a file name: Camera Raw.8bi
    Now drag the plug-in file (or copy it) into the File Formats folder in the following location:
    C:\Program Files\Adobe\Photoshop Elements 6.0\Plug-Ins\File Formats.  See Gotcha
    If running windows Vista you will probably get a pop-up requesting Administrator permission. Assuming you are the Administrator for your computer, simply agree.
    I can confirm it does work as I have recently updated my plug-in for PSE6 using the above method. To test it, go to one of your photo folders, right click on a raw file (NEF, CR2, DNG etc) and select open with Photoshop Elements. The image should automatically open in ACR 5.6 giving you access to the latest slider adjustments, including white balance and exposure.
    Note: If you have an earlier Camera Raw plug-in, I suggest you move it from the File Formats folder to My Documents before you begin. This will prevent it being overwritten by the new Camera Raw file (it will have the same name) and you can always move it back again if the download installation fails.
    If you are using a 64-bit edition of Windows, then move the plug-in file from the unzipped download folder by navigating to:C:\Program Files (x86)\Adobe\Photoshop Elements 6.0\Plug-Ins\File Formats.

  • Very interesting and informative post-LR/ACR Camera Profiles

    This post by Eric Chan from Adobe is very imformative and reveals the reality of processing of raw files not only from Adobe's perspective but for all software that processes raw files from digital cameras. The thread is concerning Adobe's processing raw files from a Panasonic Camera model in comparison to the Camera's JPEG rendition.
    "Sorry for joining this thread late.
    Unfortunately this is a limitation of our current color profile process. This limitation actually applies to all of our camera models that we support, not just Panasonic. What is happening is that the color transform we've built is optimized mainly for daylight and incandescent light conditions, but when applied to scenes with bright light sources (especially neon lights, and especially blue/purple lights), the transform will tend to oversaturate and clip those colors.
    My team is investigating how to build better profiles going forward, but in the meantime, my main suggestion is to try reducing the Red/Green/Blue Saturation sliders in the Camera Calibration panel (not the HSL tab, and not in the Basic panel). This will help to reduce the oversaturation and clipping, and will give you a better starting point for further edits (Exposure, Contrast, etc.). As a shortcut, you can store your Red/Green/Blue Saturation slider adjustments as a preset that you can then apply quickly to other images you have that show the same issue."
    Link to the actual thread.
    http://forums.adobe.com/thread/1254354?start=40&tstart=0

    My Nikon D80 and D90 don't look the same and I have run comparisons between the Canon 7D and the Nikon D90. Taken together, they all different from each other.
    The biggest difference between the D80 and the D90 seems to lie with the much larger dynamic range of the D90. Compared to the D80 at first glance, the D90 seems washed out at the lower values. This is easily overcome in ACR, but even with that, the subjectivity of the reproduction sometimes gives a nod to one over the other.
    The closest film comparison is Fuji Astia vs Provia. The D90 at default Nikon Camera Standard resembles Astia, while the D80 is a cross between Provia and Velvia. All this is controlable. One slider I use to enrich the D90 presentation is the black slider
    The Canon has other undefined differences which I have simply noted by viewing. I haven't engaged in any tweaking of that camera's images.
    So I'll use both the D80 and the D90 according to what I am wanting to happen. Of course, there are times where the differences simply inform the operator of what may be doable, and then one is tweaked to look much like the other.
    I checked out sprengel's links to the calibrator software. They have stopped at CS3, it seems. How does it perform with CS5? I may want to at least run a calibration of both cameras and look again.
    And, of course, Adobe Standard and Nikon Standard do not agree. At all. So, when is a standard not a standard?
    When there is more than one.
    Looking back at your post, I should specify that the profile I used when making the comparisons have been  the Camera standards, not Adobe Standard.
    Message was edited by: Hudechrome

Maybe you are looking for