Request better support skin tone evaluation/measurement

Hello. I am writing this with the intention that it will be read by the folks at Adobe that are involved in the development of Lightroom. I'm pretty new to this forum, however, and I'm a little confused about whether this feature requests thread actually goes to the Adobe Lightroom team, considering that it is in a user-to-user forum. If there is a better avenue to get my feature request to Adobe, I would appreciate if someone could point me in the right direction.
Before I get into my request, I also want to mention that I did my due diligence and searched this thread to make sure this has not been requested before.
I am submitting this request because I do not see any useful way to measure or evaluate skin tone in Lightroom while adjusting white balance (or after adjusting white balance, for that matter). I can do a mouse-over to read RGB values, but I am not aware of any useful way to use RGB values for evaluating skin tones.
I just watched the latest George Jardine video, in which he recommends to use a calibrated monitor and move the Develop controls back and forth until your eye tells you it's correctly adjusted. I enjoyed this video, and I have found that this generally works well for me for tone balance, but I believe an additional tool for measuring or evaluating skin tones would benefit the Lightroom workflow as I will explain below.
I believe that many serious photographers, pro and amateur alike, routinely use the eyedropper in Photoshop for reading CMYK values to confirm the skin tones in their work. Even if they feel like they can usually eyeball pretty well, they find they get greater consistency when they use the eyedropper.
Now I'm not saying that Lightroom necessarily needs CMYK support. Photoshop Elements, for example has a skin tone adjustment even though it doesn't have CMYK support. And I'm also not suggesting that Lightroom necessarily needs skin tone sliders like Photoshop Elements. I'm just suggesting that the Lightroom workflow would benefit from some kind of tool for evaluating skin tone while or after adjustments are being made in the Develop Module. I would like to leave it up to Lightroom to decide exactly how to implement this.
The only way I currently see to do adjust while measuring skin tones is to open the file in Photoshop, make adjustments, and save. Even if there is a way to do this with ACR and have the adjustments saved in the sidecar or in the DNG, it still seems like a time-comsuming and unnecessary step for my workflow.
Now this request is predicated on the assumption that evaluting skin tone is fundamental enough for a basic workflow that it should be included in Lightroom. In my opinion it is, and that is why I am making this feature request. I'm sure that some might not need it for their workflow, but it seems to me that this would be a valuable feature to a great many Lightroom users.
Thanks for lending your ear, Adobe. I look forward to ALL your future versions of Lightroom, and I hope that skin tone evaluation/measurement is included in one of them.
Regards,
Mike

Your post seems to assume that Lightroom is a tool for travel/landscape photography, and other types of photography (e.g., portrait/fashion) should be supported by a "specialized add-on module". I have to disagree with you on that point. Considering many of the examples on the Lightroom marketing are fashion shoots, I would think that they considers portrait/fashion photographers to be an important part of their target audience. They are not a fringe group of specialists.
I'm sure that portrait/fashion photographers would feel the same way about a Lightroom capability that primarily benefits the workflow of a travel/landscape photographer, i.e., when I do do some landscape work, I just edit in Photoshop. But you wouldn't agree to that, would you?
Skin tone measurement can be an incredibly easy tool to implement. It can be something as simple as showing the CMY values alongside the RGB values during a mouseover. Keep in mind, I'm talking about CMY not CMYK, so there should be no need to worry about what ICC profile to use. RGB to CMY is a straightforward transformation. It's embarassingly simple.
There are other ways Adobe can implement skin tone management that would be more powerful but a little more complicated. Those would be great too.
Anyway, thanks for the link to the Adobe feature request page! I will use it.
Regards,
Mike

Similar Messages

  • CS6 Beta questions: skin tones, camera calibration in Camera RAW

    While this is supposed to be a fully functional version, I am missing the Patch and Move content aware tools, the Skin Tones function does not work, there is no camera calibration except for Adobe Standard available under Camera RAW 7.0 and none of the links uder "Help" work.  When I try to look for updates I am assured that I have the latest version.  Does this sound right to you?  Am I just not looking in the right places for these features or are they indeed not available in Beta, in which case it is of course impossible to try them out.

    Thanks very much, Pattie.  I was not holding down the Healing brush.  That all works fine now.  However, what about camera profiles for camera calibration in Camera Raw 7.0 and why don't the skin tones work?  I am using a reasonably new HP laptop with plenty of horsepower and Windows 7.  Here is my system info.  Can you help further?
    Adobe Photoshop Version: 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:10, Stepping:7 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
    Physical processor count: 4
    Logical processor count: 8
    Processor speed: 1995 MHz
    Built-in memory: 4044 MB
    Free memory: 853 MB
    Memory available to Photoshop: 3447 MB
    Memory used by Photoshop: 60 %
    Image tile size: 128K
    Image cache levels: 4
    OpenGL Drawing: Enabled.
    OpenGL Drawing Mode: Advanced
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: True.
    OpenGL Allow Old GPUs: Not Detected.
    Video Card Vendor: ATI Technologies Inc.
    Video Card Renderer: Radeon (TM) HD 6770M       
    Display: 1
    Display Bounds:=  top: 0, left: 0, bottom: 1024, right: 1280
    Video Card Number: 2
    Video Card: Radeon (TM) HD 6770M       
    OpenCL Unavailable
    Driver Version: 8.830.6.2000
    Driver Date: 20110412000000.000000-000
    Video Card Driver: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.d ll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    Video Mode:
    Video Card Caption: Radeon (TM) HD 6770M       
    Video Card Memory: 1024 MB
    Video Rect Texture Size: 16384
    Video Card Number: 1
    Video Card: Mobile Intel(R) HD Graphics
    OpenCL Unavailable
    Driver Version: 8.830.6.2000
    Driver Date: 20110412000000.000000-000
    Video Card Driver: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumdx32,igd10umd32,igd10umd32
    Video Mode: 1280 x 1024 x 4294967296 colors
    Video Card Caption: Mobile Intel(R) HD Graphics
    Video Card Memory: 1024 MB
    Video Rect Texture Size: 16384
    Serial number: Tryout Version
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
    Temporary file path: C:\Users\Michael\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
      Startup, 682.5G, 559.7G free
    Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
    Additional Plug-ins folder: C:\Program Files (x86)\AKVIS\
    Installed components:
       A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112  
       ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
       adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
       AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0  
       AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
       AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
       AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1642  
       AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
       AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
       AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
       adobe_caps.dll   Adobe CAPS   5,0,10,0  
       AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
       ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56  
       aif_core.dll   AIF   3.0   62.490293
       aif_ocl.dll   AIF   3.0   62.490293
       aif_ogl.dll   AIF   3.0   62.490293
       amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
       ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
       AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
       AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
       Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
       BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
       boost_date_time.dll   DVA Product   6.0.0  
       boost_signals.dll   DVA Product   6.0.0  
       boost_system.dll   DVA Product   6.0.0  
       boost_threads.dll   DVA Product   6.0.0  
       cg.dll   NVIDIA Cg Runtime   3.0.00007  
       cgGL.dll   NVIDIA Cg Runtime   3.0.00007  
       CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
       CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
       data_flow.dll   AIF   3.0   62.490293
       dvaaudiodevice.dll   DVA Product   6.0.0  
       dvacore.dll   DVA Product   6.0.0  
       dvamarshal.dll   DVA Product   6.0.0  
       dvamediatypes.dll   DVA Product   6.0.0  
       dvaplayer.dll   DVA Product   6.0.0  
       dvatransport.dll   DVA Product   6.0.0  
       dvaunittesting.dll   DVA Product   6.0.0  
       dynamiclink.dll   DVA Product   6.0.0  
       ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
       FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
       filter_graph.dll   AIF   3.0   62.490293
       hydra_filters.dll   AIF   3.0   62.490293
       icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615  
       icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615  
       image_compiler.dll   AIF   3.0   62.490293
       image_flow.dll   AIF   3.0   62.490293
       image_runtime.dll   AIF   3.0   62.490293
       JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
       libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)  
       libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0  
       LogSession.dll   LogSession   2.1.2.1640  
       mediacoreif.dll   DVA Product   6.0.0  
       MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
       msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1  
       msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1  
       msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1  
       pdfsettings.dll   Adobe PDFSettings   1.04  
       Photoshop.dll   Adobe Photoshop CS6   CS6  
       Plugin.dll   Adobe Photoshop CS6   CS6  
       PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383  
       PSArt.dll   Adobe Photoshop CS6   CS6  
       PSViews.dll   Adobe Photoshop CS6   CS6  
       SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
       ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
       tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406  
       tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406  
       TfFontMgr.dll   FontMgr   9.3.0.113  
       TfKernel.dll   Kernel   9.3.0.113  
       TFKGEOM.dll   Kernel Geom   9.3.0.113  
       TFUGEOM.dll   Adobe, UGeom©   9.3.0.113  
       updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
       WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
       wu3d.dll   U3D Writer   9.3.0.113  
    Required plug-ins:
       3D Studio 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Accented Edges 13.0
       Adaptive Wide Angle 13.0
       ADM 3.11x01
       Angled Strokes 13.0
       Average 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Bas Relief 13.0
       BMP 13.0
       Camera Raw 7.0
       Chalk & Charcoal 13.0
       Charcoal 13.0
       Chrome 13.0
       Cineon 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Collada 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Color Halftone 13.0
       Colored Pencil 13.0
       CompuServe GIF 13.0
       Conté Crayon 13.0
       Craquelure 13.0
       Crop and Straighten Photos 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Crop and Straighten Photos Filter 13.0
       Crosshatch 13.0
       Crystallize 13.0
       Cutout 13.0
       Dark Strokes 13.0
       De-Interlace 13.0
       Dicom 13.0
       Difference Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Diffuse Glow 13.0
       Displace 13.0
       Dry Brush 13.0
       Eazel Acquire 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Embed Watermark 4.0
       Entropy 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Extrude 13.0
       FastCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Fibers 13.0
       Film Grain 13.0
       Filter Gallery 13.0
       Flash 3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Fresco 13.0
       Glass 13.0
       Glowing Edges 13.0
       Google Earth 4 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Grain 13.0
       Graphic Pen 13.0
       Halftone Pattern 13.0
       HDRMergeUI 13.0
       IFF Format 13.0
       Ink Outlines 13.0
       JPEG 2000 13.0
       Kurtosis 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Lens Blur 13.0
       Lens Correction 13.0
       Lens Flare 13.0
       Liquify 13.0
       Matlab Operation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Maximum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Mean 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Measurement Core 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Median 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Mezzotint 13.0
       Minimum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       MMXCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Mosaic Tiles 13.0
       Multiprocessor Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Neon Glow 13.0
       Note Paper 13.0
       NTSC Colors 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Ocean Ripple 13.0
       Oil Paint 13.0
       OpenEXR 13.0
       Paint Daubs 13.0
       Palette Knife 13.0
       Patchwork 13.0
       Paths to Illustrator 13.0
       PCX 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Photocopy 13.0
       Photoshop 3D Engine 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Picture Package Filter 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Pinch 13.0
       Pixar 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Plaster 13.0
       Plastic Wrap 13.0
       PNG 13.0
       Pointillize 13.0
       Polar Coordinates 13.0
       Portable Bit Map 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Poster Edges 13.0
       Radial Blur 13.0
       Radiance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Range 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Read Watermark 4.0
       Reticulation 13.0
       Ripple 13.0
       Rough Pastels 13.0
       Save for Web 13.0
       ScriptingSupport 13.0
       Shear 13.0
       Skewness 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Smart Blur 13.0
       Smudge Stick 13.0
       Solarize 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Spatter 13.0
       Spherize 13.0
       Sponge 13.0
       Sprayed Strokes 13.0
       Stained Glass 13.0
       Stamp 13.0
       Standard Deviation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Sumi-e 13.0
       Summation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Targa 13.0
       Texturizer 13.0
       Tiles 13.0
       Torn Edges 13.0
       Twirl 13.0
       U3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Underpainting 13.0
       Vanishing Point 13.0
       Variance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Variations 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Water Paper 13.0
       Watercolor 13.0
       Wave 13.0
       Wavefront|OBJ 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       WIA Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       Wind 13.0
       Wireless Bitmap 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
       ZigZag 13.0
    Optional and third party plug-ins:
       ArtWork 6.0.1491.8030
       Sketch 13.0.2473.8439
    Plug-ins that failed to load: NONE
    Flash:
       Mini Bridge
       Kuler
    Installed TWAIN devices: NONE

  • [Feature Request] Better support for new buttons in JUNavigationBar

    In my project I use a home made sub-class of JUNavigationBar, which contains some new functionality apart from a new button as well. This button allows me to refresh the currently selected row.
    However, since I added this button though a simple this.add(), some of the functionality in JUNavigationBar may get confused.
    For example, when I have removed some of the standard buttons but left my own button in place (setHasXXX()), the component index (calculated in JToolBar) and the array index for the buttons in JUNavigationBar may not match. This occasionally causes an ArrayIndexOutOfBoundsException.
    In short, what I'm asking for, is a better way to manage buttons on JUNavigationBar. Even making the array of buttons and related methods and such protected in stead of private (so that my sub-class could handle it) would be a good start.

    Hi Arno,
    I had a similar issue with trying to create a Nav bar with dynamic content. My solution was to leave all the standard buttons in place and to use setVisible(x) to make them appear or not as required.
    BTW have you noticed that rollover behaviour isn't consistant ie works for FIRST/LAST etc but not for FIND/QUERY.
    Regards
    Andy

  • Customer request: better support for Flash-heavy web sites!?  Feasible?

    The company I work for (a SUN partner) is currently engaged in a desktop virtualisation project at a customer who is in the health care sector. Of course Sun VDI isn't the only thing they have been looking at. But so far we've always come out on top.
    PanoLogic and their "Pano Cube" thin-clients were looked at but never really considered. The argument being "Nobody is using that!" and they don't want to play "Star Trek" and "boldly buy things nobody has bought before". So it was "Thank you and bye bye PanoLogic". However ... PanoLogic is on their radar now and they might still go back one day ...
    Next up was VMware View. They didn't like what they saw. So for now they will keep their ESX and vSphere servers but VMware View is out of the game for now.
    So right now there is still us with our Sun VDI / Sun SSGD offer and a competitor with their Citrix offerings. So far we've always managed to tip the balance in our favor.
    This Wednesday though we had a few of customer's managers visit us. They wanted to see a Sun VDI 3.1 live demo. All was fine, all was well, and we had the impression that they were so close to giving the "go ahead", when one of the pro-Citrix guys opened two web sites in his VDI demo session:
    http://www.adiacom.ch
    http://www.2advanced.com
    Both sites are extremely extremely Flash-heavy.
    And of course: The performance was sub-optimal. We were running this on a Sun Ray 2, 1600 x 1200 pixels. Even though the sound was tip top in both the Windows XP and in the Linux sessions (they admit that in all the other products they have tried so far the sound was choppy or there was even no sound at all .... ) the video was slightly out of sync. And the web site "2advanced.com" took too long to load.
    So now all of a sudden the ability to play these two web sites "tip top" on a Sun Ray 2 is THE killer argument for them. It doesn't even matter that all other solutions they have looked at can't show those two web sites at all, now it's all of a sudden that Sun Rays and Sun VDI just "aren't good enough" at playing those two web sites.
    Customer is king. Customer is always right.
    So ... anyone here from Sun have any suggestions how we might improve performance of those two web sites inside the VDI sessions? Is there anything we could tweak and tune inside VDI 3.1 to get the max performance out of our setup?
    Or are there any products in the pipeline like new Sun Ray clients with improved multimedia performance that I could tell them about so we could keep them interested in Sun's products ... ?
    Edited by: DJ. on Oct 30, 2009 6:22 AM -- typos corrected.

    Greetings oh Master :)
    We don't have flash acceleration for LinuxI know. And yet the "adiacom.ch" web site performed better on Firefox & Ubuntu than on Win XP-SP3 & MSIE 8.
    only XP and W2K3.I know
    Are you using the MS-RDP severSun VDI 3.1 ... I get the VDI login mask, I login, I pick a Windows XP desktop from the available pools, and Windows XP appears. The desktops are provided via VMware vSphere.
    viewing the site via IEUnder Windows XP, yes.
    and have the Flash acceleration bits installed?I remember installing various multimedia bits that can be found in the "Supplemental" sub-directory of the SRWC 2.2 ZIP file: "SunMMR" and "SunWinUSB". But now that I look at the web page you linked to I am a bit confused .... Did I install an old version? I will have to check that again and make sure this stuff is really really installed.
    Thanks for that link!

  • OLAP Enhancement request to support demographics

    Hi, I'd like to put in an enhancement request to better support demographics in OLAP cubes (see discussion here:
    Demographic Dimensions
    for an example).
    I'd like to request the following:
    1. Enable all attributes (not just long and short descriptions) to be displayed through the BI tools (BI Beans, spreadsheet add-in, etc.). Allow these to be used not only as items you can pick dimension values with (i.e. select all shirts with color attribute = green), but allow them to be used as full "mini-dimensions" - i.e. even through "color" is an attribute of product dim, allow me to use it like a dimension (product dimension going down a report, "color" mini-dimension going across...)
    2. Enable aggregation map technology to do calc-on-the-fly to solve totals for the demographic dimensions
    Having asked for all this, I'd like to find out if anything along these lines is in the works? I know there is functionality coming out (soon?) for "custom aggregates" - where you can take any random group of dimension values and have it calc on the fly and show up like a normal dimension value. That seems to me to be "very close" to some of the functionality needed (although it doesn't address it 100%...if I have 2 attributes on a dimension (say "color" and "size) - I'd like to put 1 as an across dim and 1 as a down dim....
    I know these are not probably "simple" or "quickly achievable" - but I really believe they would add a TON of value to the OLAP functionality.
    Thanks,
    Scott

    Deepak,
    I leave the ER in. Though the article explains how to include tiles, it requires lots of manual configuration, which I think can be automated.
    Functionality wise tiles are similar to the planned region feature (though not 100 % identical)
    Frank

  • Color correction on magenta skin tones / white shirt

    I want to color correct a shot that is very blue/ magenta.
    I would like the skin tones to be less magenta and more orange/yellow.
    I get the best results by adding yellow on the Midtones and Shadows.
    My problem is that the Highlights are going yellow, specially a white shirt. I get a better result by by then adding blue on the Highlights. I'm wondering if it's the right thing to do... Also, some Midtones are still too magenta.
    I could isolate the skin tones as secondaries, but still, I have to color correct other parts of the image.
    Any tip? Should I use the advanced settings?
    I know my question as no miracle answer and that color correction should be done by a pro, but I would appreciate any suggestion, thanks.

    cariocastyle wrote:
    I want to color correct a shot that is very blue/ magenta.
    I would like the skin tones to be less magenta and more orange/yellow.
    I get the best results by adding yellow on the Midtones and Shadows.
    I'm wondering if it's the right thing to do...
    I don't know, what does your eye tell you?
    Before anyone can suggest any sort of solution, you need to provide a still as Mr. Owens asked for and then provide some direction for what you want.
    No 2 people on the face of the earth see exactly the same. Color is entirely subjective. If you like what you're doing (I would ask, how you're seeing anything accurately from an iMac) then who cares what anyone else thinks? Unless, someone is paying you for your talent, then you'd best have the best rig money can buy as anything less is a lie.

  • Skin tone

    I wonder if there's a way to add a 'skin tone' adjustment setting for the Adjustment Brush.  ?  Yes, skin tone varies, but at times, working under mixed lighting, it can be difficult to get something that isn't peachy or orangey. 
    Separate from that:  As a test, I processed some images (from scratch) in LR4 that I'd completed in LR3 for a gig.  The new sliders are cool, but I can see I need to learn how to better use them.  I already see an improvement with Clarity - it seems sharper.    
    Curious - what changes were made to the dng files?
    Will do more testing, and with the other modules as well.
    Thanks.
    Barbara

    @Rob:
    "When you import a bitmap image into Flash, it comes in as one mass of pixels."
    Strictly speaking, any bitmap image is a "mass" of pixels to begin with - hence the name map of bits - 2D array of pixels.
    @Saran:
    Search for "AS3 face recognition" - there are several developers that attacked this task.
    Where Rob is right - it is not an easy objective - you will need to learn in details BitmapData manipulations, filters and, perhaps, shaders (pixel bender). Shaders are the most solid approach. Photoshop, AfterEffect and other Adobe software uses shaders for image editing.

  • Skin tones in LR

    Skin tones in LR often seem to look pasty and flat. I've been reading Lee Varis's book "Skin", and in it he says Caucasian skin tones should have a roughly equal amount of yellow and magenta (with yellow between 1 and 10 points higher) and about 1/4 to 1/3 the amount of cyan.
    Most of the pictures I take of Caucasians and import into LR actually have yellow as the lowest value, with magenta and cyan being roughly equal. These skin tones look pale and somewhat pasty:
    When I adjust this same image in Photoshop using Lee Varis's method, I get the following results:
    Even though the numbers are "correct" in the second version, I think it has gone too far in the other direction.
    In any event, I'd like to know 1) if others have the same problem with the way skin tones appear in LR, 2) if you have found a good way of color correcting for skin in LR without exporting to PS. I'd like to get the color as accurate as possible in LR so I don't have to edit every image in Photoshop.
    Thanks.

    I am a pro, I shoot primarily for magazines in my area, have been doing so for over 10 years now. I shoot A LOT of people. Here are my thoughts for you:
    1) The top photo was shot in an open shade area, this creates a color balance/temperature problem. It is too blue for a daylight setting, yet not blue enough for a cloudy setting.
    2)Using a whibal or other reference card for skin tones is very hit or miss. They will give you a very accurate balance of rgb values, but rarely if ever give the most pleasing skin tones. It is a good stating point however, especially for large groups with mixed ethnicity.
    3) BY the numbers is a good way to go, I have used it often, since learning it way back in the 90's. However I hardly ever work with in the cmyk color space. There for I have adopted the numbers for use in an RGB space.
    Here are my numbers for Caucasian skin tones. This was averaged off of 7 different samples in varying lighting conditions. This is also based on LR's rgb 0-100 scale:
    Green Should be 11% lower than Red
    and Blue should be 13% lower than green
    Example R-------------G ----------- B
    84.6---------78.1----------71.2
    60.3---------52.5----------40.8 measured in shadow
    78.8--------- 70.2---------60.3
    87.2--------- 80.5--------- 74.9
    78----------- 70.2 ---------64.7
    With the exception of the shadow reading above, each came from a slightly different Caucasian skin tone....
    Also skin tones are going to change wildly based on shooting conditions. You almost can not make a preset for skin tones unless you shoot in a controlled studio environment and shoot the exact same way each time.
    Other wise best advice I can give it to use the above number samples as a guide and learn to "see" skin tones. After you "See" them than you will not need the numbers any longer, because you will know what feels right.
    I also tend to back the vibrance slider down 1 or 2 notches if skin tone is very important to the image, but I am sure that is due to me shooting a D60
    Also...Every skin color under the sun can be balanced by the numbers once you know the percentages.....experiment with white balance and hsl until you find what looks right for THAT person.

  • Skin Tones Look Wrong When Printing From iPhoto

    Hi
    I'm having trouble getting the caucasian skin tones to look right on photos printed with my Epson Stylus C86 printer on Epson Premium Semigloss paper. They look too pinky/purple when compared with the screen of the Sony DSC camera I shot them with and also my iMac's monitor. They just look wrong as though the subjects have a combination of bad sunburn, high blood pressure and are blushing at the same time!
    I've tried the following tips synthesised from other threads:
    1. Downloaded the latest set of drivers from Epson's website.
    2. Ensured that they are associated with the printer in ColorSync utility.
    3. Selected the Use ColorSync option when printing from iPhoto's print dialogue box.
    These made no difference to the default behaviour i.e. same color problems.
    Could anyone guide me to a solution? I would rather not have to use another application to print them if possible. I'm not used to my Mac not "just working".
    Thanks

    What color profile do the pics have? Is the printer set to the same profile?
    Regards
    TD

  • Call upon even better support for Unicode

    Hello
    Following some messages I have posted regarding problems I encountered while developing a non-English web application, I would like to call upon an even better support for Unicode. Before I describe my call, I want to say that I consider Berkeley DBXML a superb product. Superb. It lets us develop very clean and maintainable applications. Maintainability is, in my view, the keyword in good software development practices.
    In this message I would like to remind you that the US-ASCII 8-bit set of characters only represents 0.4% of all characters in the world. It is also true to say that most of our software comes from efforts of American developers, for which I am of course very grateful.
    But problems with non US-ASCII characters are very very time consuming to solve. To start with, our operating systems need to be configured especially for unicode, our servers too, our development tools too, our source code too and, finally, our data too. That's a lot of configuring, isn't it? Believe me, as a Flemish french-speaking, danish-speaking developer who develops currently a new application in Portuguese, I know what I am talking about.
    Have you ever tried to write a Java class called Ação.java, that loads an xml instance called Ação.xml that contains something like <?xml version="1.0" charset="utf-8"?></ação variável="descrição"/>? It takes at least the double of time to have all this work right in a web application on a Linux server than it would take to write a Acao.java that loads Acao.xml containing <?xml version="1.0" charset="us-ascii"?></acao variavel="descricao"/> (which is clearly something we do not want in Portugal).
    I have experienced a problem while using the dbxml shell to load documents that have utf-8 encoded names. See difficulties retrieving documents with non ascii characters in name The work around is not to use the dbxml shell, with which I am of course not very happy.
    So, while trying not to be arrogant and while trying to express my very very great appreciation for this great product, I call upon even better support for Unicode. After all, when the rest of us, that use another 65279 characters in our software, will be able to use this great product without problems, will it not contribute to the success of Berkeley DBXML?
    Thank you
    Koen
    Edited by: koenheene on 29/Out/2009 3:09

    Hello John and thank you for replying,
    You are completely correct that it is a shell problem. I investigated and found solutions for running dbxml in a Linux shell. On Windows, as one could expect, no solution so far.
    Here is an overview of my investigation, which I hope will be useful for other developers which also presist writing code and xml in their language.
    difficulties retrieving documents with non ascii characters in name
    I was wondering though if it would not be possible to write the dbxml shell in such a way that it becomes independent from the encoding of the shell. Surely their must be, not? Rewrite dbxml in Java? Any candidates :-) ?
    Thanks again for the very good work,
    Koen

  • Changing skin tones with adjustment layer fails

    Hi,
    I am running PS CC 2014 and all I want to do is to adjust a skin tone to match it to the rest of the bodys skin color.
    I have watched some videos on YouTube but my PS doesnt seem to work that way and I wonder why.
    My workflow:
    Copy background layer.
    Quick select area of body where skin tone has to be changed
    (If necessary: improve selection)
    Now create adjustment layer with gradiation curve
    Select with double click midtone pipette and select one point of the "good skin tone" (also pressing CTRL at the same time when selecting it)
    Confirm with OK.
    Reject box which wants to take over skin tone as standard color.
    Click with pipette in the previously selected skin area which has to be changed.
    Instead of adjusting the color into a good skin color, this area turns into a strange orange color.
    All I can do now is to walk through the single RGB channels to makle adjustments and hope to get anywhere
    near the expected result.
    Where have I gone wrong ? Where does the orange color come from ?
    Any proposals how to get to a reasonable result ?
    Preferably with this workflow. But all other ideas are welcome, too.
    Thx.
    Arnold.

    For what it's worth: I have found that when sculptural modeling is involved, such as the in the hand, working with Curves in LAB (where tone is discrete from color) produces the color change more naturally and provides greater control over local contrast. You may want to consider that alternate approach. In this sample, the left forearm provided the reference color and I chose to lighten the tonal scale a bit.
    One off-topic comment: A shorter than normal focal length lens creates a foreshortening that makes near objects disproportionately large in relation to the rest of the object or scene. In this instance, consider its effect on the hand-head sizes. I would suggest that a focal length at least 1 1/2 times normal would be more appropriate.
    Good luck.

  • Skin tones turn putty after opening in ACDSee & Picasa

    After I export my pictures from Lightroom and save to a folder, I have noticed that skin tones that look wonderful in Lightroom look dreadful in ACDSee and Picasa. They are a dull putty. Actually some landscapes are much darker there too than they are in Lightroom.
    Any idea what is causing this? I hate to send them out to WHCC for printing because I don't know which picture will come back--the lovely one that Lightroom shows or the dreadful one I see in ACDSee. For what it's worth, before I got Lightroom, I never had this problem with ACDSee before (although I did just upgrade to ACDSee 10). Thanks for any help.
    Elise

    Jeff, I believe you are narrowing the problem down. I was sure I was saving from Lightroom in sRGB, but I went and checked for sure. I was indeed, but your post got me thinking. All of the images that have done this have been first brought into LR and then moved over into PSE4 for additional work. I went and checked the color profile for PSE4 and sure enough, it's Pro Photo RGB. It appears that is the ONLY option one has in saving from PSE.
    However, the question now is why is this suddenly happening? I've been using PSE4 for years, and ACDSeehas always been exactly the same in viewing as PSE. The only thing I can think of is that I upgraded to ACDSee 10--but why the upgrade should cause problems when the older version didn't is confusing to say the least. I think a call to ACDSee is in order.
    Thank you for helping me narrow this down.

  • What color value is skin tone?

    If I want to push skin tone in the Colour Board (Apple's rectangular version of the "colour wheel") in a colour adjustment, should I be pushing at 30 degrees?
    The FCPX user manual says in "Vectorscope display options",
    "Show/Hide Skin Tone Indicator: Shows or hides the diagonal line that represents the human skin tone chroma phase, which is between the yellow and red color bar targets."
    It doesn't say if the skin tone indicator is exactly between yellow and red, i.e. pure orange, which would be 30 degrees, or just somewhere between red and yellow.
    I found this in a Larry Jordan article,
    "Regardless which race or ethnic group our actors are a part of, all of us have the same red blood under our skins. This line (skin tone indicator) represents the color of red blood under skin. In general, when you want to make skin tones look normal and believable, you want them within a couple of degrees of this line. Above the line leans ruddy, below the line leans sallow."
    So, is the red blood under our skin pure orange, i.e. 30 degrees in the Colour Board, i.e. exactly mid way between red (zero degrees) and yellow (60 degrees), or is it some other value?

    Many thanks for all your help.  I suppose I am trying to arrive at really nice cinematic looking skin tones, but with my Canon 550d and very limited knowledge of setting up shots and film making, pushing skin tone and playing with the colour board alone will not get me those appealing skin tones.  Attached are some interesting ones, but how to achieve them?  I need to keep learning, and perhaps have a good lot of cash for gear ..

  • Having trouble getting skin tones to print "accurately"

    Hello! This is my first post to a forum, but I am unhappy with the skintones of my portrait shots in the printed results and am driven to seek your collective help. I realize that an image on the monitor will never match exactly to the printed image because the media is entirely different. I am pleased with the image results for everything except the human skintones. Portrait shots can look great on the monitor, but the printed image always has a greenish cast. This happens when shooting outdoors in sunlight and on overcast days. No flash was used.
    I am shooting RAW (uncompressed NEF), using Nikkor lenses on a D200. My printer is an EPSON Stylus Photo 2200. Mac Pro 2x2.66 GHz Dual-Core Intel Xeon processor. RadeonX1900 graphics card. Apple Cinema 24" Display calibrated with SpyderPRO. Epson Premium Glossy Photo paper. Aperture 1.5.3. Lately I have been using a 105mm, 2.8, VR Nikkor lens or the 17-55mm, 2.8 Nikkor lens. (I think I have all the right equipment, now if I could only fix the user!)
    I notice that Aperture has default setting applied to my images in RAW Fine Tuning and the Boost is always set to 1.00. Chroma Blur Radius=2.00 and Auto Noise Redution is checked. Sharpening Intensity=0.5 and Edges-0.73.
    My in camera white balance is set to full sun. Aperture white balance temparature comes in at 4860K.
    What is the Boost and if I change it to 0.00, the skin tones are not as saturated and reddish in the display, but the printed image has a greenish cast. Should I be changing this value at all?
    I see that other folks post fabulous portrait images on the web with lovely creamy skin tones, but I can never achieve that effect. What am I doing wrong?
    Thanks in advance for any help you folks can send my way.

    The Boost slider under the Raw Fine Tuning change the contrast of the image. I set it up to be 0.80 as default, sometimes I lower it even more. Then I use the controls under the exposure section to adjust the exposure and contrast. I finish it with the levels adjustments.
    It's very easy to get reddish faces when the contrast is to high. If that's the case in the color adjustments I lower the saturation of the reds a little bit and move the slider of the hue a little bit to the right, usually a value of 2.0 is enough to make them more orangy.
    It's crucial that you set up the white balance properly. A grey card is a great help to have a neutral tone in the image, then I usually go a bit warmer, around 200-300K more than neutral.

  • Presets sought for fine-tuning skin tones

    Are presets available to fine tune skin tones in Camera Raw, perhaps by tweaking colors and hue/saturation/luminance settings in the HSL/Grayscale menu?
    I like almost everything about ACR except how the default settings render skin tones on my 5D's CR2 files. I bought a copy of Margulis' 'Professional Photoshop' and now can consistently "fix" what I didn't like, but I suspect as much or more could be accomplished with knowledgeable tweaking in the HSL menu.
    I found one preset, after visiting this adobe forums thread:
    http://www.adobeforums.com/webx/.3bbed80a/1
    ... but that's all. I think they'd be a snap for an expert retoucher to create -- e.g., warm_with_pink.xmp, warm_with_yellow.xmp, presets for skin tones of different ethnicities, etc.
    Of course, I've tried to do it myself, by nudging orange, red, yellow and magenta sliders, but ... with limited success, to put it mildly. I'd much rather start out with tweak-the-skin-tones presets from an expert, and then adjust to taste. If I can find 'em.

    Thanks for the links to chromoholics and creativepro. My last experience with creating a custom camera profile wasn't that successful, but that was a long time ago, and I probably shouldn't let that discourage me from trying again. If that's the ultimate solution, you've told me what I need to know.
    For whatever it's worth, though, I've shot with two 5Ds, and can't tell the CR2s they produce apart. ACR at default settings yields the same (to me) objectionable, pale apricot skin tone from the CR2s of both cameras.
    I would fix this in ACR, if I knew how. I don't; I'm not that good with the HSL sliders; I have to do it in Photoshop. But because the 5D is a popular and fairly high end camera, I guessed, or hoped, that professional wedding or fashion photographers who live and die by nuances of skin tone might have sub-directories full of presets to nudge 5D skin tones ... and, further, that they'd generously share said preset collection with the world.

Maybe you are looking for

  • Planned delivery date

    I have following scenario. Vendor Price terms is Exworks. we have planned delivery time in material Master MRP view as Vendor manufacturing time. We may use Air or Ocean for Transit. I want delivery date in PO based on mode of trnasit. Example for a

  • Error while assigning values to Table type

    Hi, I am trying to insert some values to a Collection type , while doing that I am facing an error , " PLS-00306: wrong number or types of arguments in call to 'XXSCP_AVL_CSP_SQR_O_TP' "PFB my collection type declaration and and assignment . Object t

  • Seagate external hard drive is not working since I upgraded to yosemite. Can some one help me?

    I can't connect my seagate external hard drive since I updated to yosemite. Im getting error code 71, can someone help me?

  • [FIX] Yoga 13 auto-rotat​es to portrait on startup after Win 8.1 upgrade

    This was going to be a question post but I just stumbled across the answer on my own, so here's the solution instead! After upgrading the Yoga 13 to Windows 8.1 through the Windows Store app, and even after installing all the new drivers, I found tha

  • CD-R, DVD Drive

    I have some footage on the mini-DVD's.......Do I need some sort of sleeve to play the small sized DVD's or should they just insert into the drive? I tried and it didn't seem to work. I thought I possibly lost the DVD in the drive but it popped out a