Drag from Lightroom 3 to Photodex Producer

I use to be able drag from Media Expressions/Ivew Media Pro to Photodex Producer when building slideshows, it worked fine.
I tried using Lightroom 3 from library module to producer and it did not work.
Is there a way to do this in Lightroom3?
I wanted to use the dam part of lightroom instead of Media Expressions which I don't think Microsoft is going to keep updated.

Thanks for the info.
I found a Lightroom Plugin from Photodex that does it and more.
I will not be using media expressions as that was one reason I upgraded to Lightroom 3, to catalog and play video as well.
I will do everything in lightroom 3 thankfully at last !!!!!!!

Similar Messages

  • Drag and drop from Lightroom into Premiere doesn't work in Windows

    I recently switched from OSX to Windows and noticed that in Windows, I'm unable to drag and drop from LIghtroom into Premiere. In OSX, it worked fine.
    I do this a lot because it's a time saver. I basically use lightroom to find the photo or video clip I need for my editing project and then just drag in right on to the Premiere timeline. Now I have to do the extra step in Lightroom of "show in explorer", then drag the file from explorer to Premiere. Not really a big deal but just curious why it works in OSX and not Windows.
    I'm running latest Windows 8.1, Lightroom 5.4, Camera Raw 8.4, and Premiere Pro CC 7.2.2 (33)
    -Pete

    Hi Pete,
    You can obtain scripts here:
    http://www.robcole.com/Rob/ProductsAndServices/MiscLrPlugins#MiscScripts
    You'll have to edit lua code to adapt for Premiere. Not that hard really (e.g. clone, then change the script name and path to executable..), but may be too intimidating for some folks. If you are one of those folks, go for the plugin instead - it's usable via GUI - no lua code - can probably accomplish the same thing.
    http://www.robcole.com/Rob/ProductsAndServices/OpenInWhateverLrPlugin
    Let me know (outside the forum please) if problems - thanks,
    Rob

  • Photoshop CC 2014 crashes when trying to create a panorama from Lightroom?

    Hi,
    I have both Photoshop and Lightroom CC installed.
    When I pass 6 photos from Lightroom to Photoshop CC to create a panorma, Photoshop goes through the throws, imports the images, generates the panorama then crashes, with a message from Windows saying it is checking for a solution to the problem, then dies.
    I have reviewed the posts, and found one that suggest to increase the cache level to 6... tried this and it still dies.
    Found another workaround to have Photoshop x64 running and pass the images to it rather than have Lr fire up Ps CC. This worked and produced the panorama.
    I am not sure why, but with the use of the CC app, I know have three Ps's on my my machine, x32, x64 and CC..., not even sure what the difference between x64 and CC... ???...
    So my question is...
    Is there are a problem with PS CC?... there certainly was with the focus stacking algorithms.. or is it just me.?.. ;(
    Thanks for any help with this...
    Cheers
    Keith Friend.
    the techy details from PS CC 2014 are as follows, this is the version that Lr fires up..
    Adobe Photoshop Version: 2014.2.2 20141204.r.310 2014/12/04:23:59:59 CL 994532  x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, HyperThreading
    Physical processor count: 4
    Logical processor count: 8
    Processor speed: 2294 MHz
    Built-in memory: 8087 MB
    Free memory: 4027 MB
    Memory available to Photoshop: 7067 MB
    Memory used by Photoshop: 69 %
    3D Multitone Printing: Disabled.
    Windows 2x UI: Disabled.
    Highbeam: Enabled.
    Image tile size: 128K
    Image cache levels: 6
    Font Preview: Medium
    TextComposer: Latin
    Display: 1
    Display Bounds: top=0, left=0, bottom=1080, right=1920
    Display: 2
    Display Bounds: top=-120, left=1920, bottom=1080, right=3840
    OpenGL Drawing: Enabled.
    OpenGL Allow Old GPUs: Not Detected.
    OpenGL Drawing Mode: Advanced
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: True.
    AIFCoreInitialized=1
    AIFOGLInitialized=1
    OGLContextCreated=1
    NumGLGPUs=1
    NumCLGPUs=2
    glgpu[0].GLVersion="3.0"
    glgpu[0].GLMemoryMB=2112
    glgpu[0].GLName="Intel(R) HD Graphics 4000"
    glgpu[0].GLVendor="Intel"
    glgpu[0].GLVendorID=32902
    glgpu[0].GLDriverVersion="8.15.10.2712"
    glgpu[0].GLRectTextureSize=8192
    glgpu[0].GLRenderer="Intel(R) HD Graphics 4000"
    glgpu[0].GLRendererID=358
    glgpu[0].HasGLNPOTSupport=1
    glgpu[0].GLDriver="igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd 32"
    glgpu[0].GLDriverDate="20120326000000.000000-000"
    glgpu[0].CanCompileProgramGLSL=1
    glgpu[0].GLFrameBufferOK=1
    glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="1.30 - Intel Build 8.15.10.2712"
    glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[1447 ]
    glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[8]
    glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[16]
    glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[16]
    glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[16]
    glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
    glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[1024]
    glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[1024]
    glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[41]
    glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
    glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
    glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
    glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=0
    clgpu[0].CLPlatformVersion="1.1"
    clgpu[0].CLDeviceVersion="1.1 CUDA"
    clgpu[0].CLMemoryMB=2048
    clgpu[0].CLName="GeForce GT 650M"
    clgpu[0].CLVendor="NVIDIA Corporation"
    clgpu[0].CLVendorID=4318
    clgpu[0].CLDriverVersion="331.65"
    clgpu[0].CUDASupported=1
    clgpu[0].CUDAVersion="6.0.1"
    clgpu[0].CLBandwidth=4.46455e+010
    clgpu[0].CLCompute=150.537
    clgpu[1].CLPlatformVersion="1.1 "
    clgpu[1].CLDeviceVersion="1.1 "
    clgpu[1].CLMemoryMB=1624
    clgpu[1].CLName="Intel(R) HD Graphics 4000"
    clgpu[1].CLVendor="Intel(R) Corporation"
    clgpu[1].CLVendorID=32902
    clgpu[1].CLDriverVersion="8.15.10.2712"
    clgpu[1].CUDASupported=0
    clgpu[1].CLBandwidth=1.40476e+010
    clgpu[1].CLCompute=84.3036
    License Type: Subscription
    Serial number: 96040231285882737802
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CC 2014\
    Temporary file path: C:\Users\Keith\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
      Startup, 909.7G, 639.9G free
    Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Required\Plug-Ins\
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Plug-ins\
    Installed components:
       A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112  
       ACE.dll   ACE 2014/08/12-23:42:09   79.557478   79.557478
       adbeape.dll   Adobe APE 2013/02/04-09:52:32   0.1160850   0.1160850
       AdbePM.dll   PatchMatch 2014/09/07-21:07:38   79.558079   79.558079
       AdobeLinguistic.dll   Adobe Linguisitc Library   8.0.0  
       AdobeOwl.dll   Adobe Owl   5.2.4  
       AdobePDFL.dll   PDFL 2014/08/18-15:13:12   79.512424   79.512424
       AdobePIP.dll   Adobe Product Improvement Program   7.2.1.3399  
       AdobeXMP.dll   Adobe XMP Core 2014/08/20-09:53:02   79.156797   79.156797
       AdobeXMPFiles.dll   Adobe XMP Files 2014/08/20-09:53:02   79.156797   79.156797
       AdobeXMPScript.dll   Adobe XMP Script 2014/08/20-09:53:02   79.156797   79.156797
       adobe_caps.dll   Adobe CAPS   8,0,0,13  
       AGM.dll   AGM 2014/08/12-23:42:09   79.557478   79.557478
       ahclient.dll    AdobeHelp Dynamic Link Library   1,8,0,31  
       amtlib.dll   AMTLib (64 Bit)   8.0.0.122212002 BuildVersion: 8.0; BuildDate: Wed Jul 30 2014 15:59:34)   1.000000
       ARE.dll   ARE 2014/08/12-23:42:09   79.557478   79.557478
       AXE8SharedExpat.dll   AXE8SharedExpat 2013/12/20-21:40:29   79.551013   79.551013
       AXEDOMCore.dll   AXEDOMCore 2013/12/20-21:40:29   79.551013   79.551013
       Bib.dll   BIB 2014/08/12-23:42:09   79.557478   79.557478
       BIBUtils.dll   BIBUtils 2014/08/12-23:42:09   79.557478   79.557478
       boost_date_time.dll   photoshopdva   8.0.0  
       boost_signals.dll   photoshopdva   8.0.0  
       boost_system.dll   photoshopdva   8.0.0  
       boost_threads.dll   photoshopdva   8.0.0  
       cg.dll   NVIDIA Cg Runtime   3.0.00007  
       cgGL.dll   NVIDIA Cg Runtime   3.0.00007  
       CIT.dll   Adobe CIT   2.2.6.32411   2.2.6.32411
       CITThreading.dll   Adobe CITThreading   2.2.6.32411   2.2.6.32411
       CoolType.dll   CoolType 2014/08/12-23:42:09   79.557478   79.557478
       dvaaudiodevice.dll   photoshopdva   8.0.0  
       dvacore.dll   photoshopdva   8.0.0  
       dvamarshal.dll   photoshopdva   8.0.0  
       dvamediatypes.dll   photoshopdva   8.0.0  
       dvametadata.dll   photoshopdva   8.0.0  
       dvametadataapi.dll   photoshopdva   8.0.0  
       dvametadataui.dll   photoshopdva   8.0.0  
       dvaplayer.dll   photoshopdva   8.0.0  
       dvatransport.dll   photoshopdva   8.0.0  
       dvaui.dll   photoshopdva   8.0.0  
       dvaunittesting.dll   photoshopdva   8.0.0  
       dynamiclink.dll   photoshopdva   8.0.0  
       ExtendScript.dll   ExtendScript 2014/01/21-23:58:55   79.551519   79.551519
       icucnv40.dll   International Components for Unicode 2013/02/25-15:59:15    Build gtlib_4.0.19090  
       icudt40.dll   International Components for Unicode 2013/02/25-15:59:15    Build gtlib_4.0.19090  
       igestep30.dll   IGES Reader   9.3.0.113  
       imslib.dll   IMSLib DLL   7.0.0.154  
       JP2KLib.dll   JP2KLib 2014/06/28-00:28:27   79.254012   79.254012
       libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)  
       libiomp5md.dll   Intel(R) OpenMP* Runtime Library   5.0  
       libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0  
       LogSession.dll   LogSession   7.2.1.3399  
       mediacoreif.dll   photoshopdva   8.0.0  
       MPS.dll   MPS 2014/08/18-23:43:19   79.557676   79.557676
       pdfsettings.dll   Adobe PDFSettings   1.04  
       Photoshop.dll   Adobe Photoshop CC 2014   15.2.2  
       Plugin.dll   Adobe Photoshop CC 2014   15.2.2  
       PlugPlugExternalObject.dll   Adobe(R) CEP PlugPlugExternalObject Standard Dll (64 bit)   5.0.0  
       PlugPlugOwl.dll   Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit)   5.2.0.54  
       PSArt.dll   Adobe Photoshop CC 2014   15.2.2  
       PSViews.dll   Adobe Photoshop CC 2014   15.2.2  
       SCCore.dll   ScCore 2014/01/21-23:58:55   79.551519   79.551519
       ScriptUIFlex.dll   ScriptUIFlex 2014/01/20-22:42:05   79.550992   79.550992
       svml_dispmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0  
       tbb.dll   Intel(R) Threading Building Blocks for Windows   4, 2, 2013, 1114  
       tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   4, 2, 2013, 1114  
       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   8.0.0.14 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   8.0.0.14
       VulcanControl.dll   Vulcan Application Control Library   5.0.0.82  
       VulcanMessage5.dll   Vulcan Message Library   5.0.0.82  
       WRServices.dll   WRServices Fri Mar 07 2014 15:33:10   Build 0.20204   0.20204
       wu3d.dll   U3D Writer   9.3.0.113  
    Required plug-ins:
       3D Studio 15.2.2 (2014.2.2 x001 x003)
       Accented Edges 15.2.2
       Adaptive Wide Angle 15.2.2
       Angled Strokes 15.2.2
       Average 15.2.2 (2014.2.2 x001 x003)
       Bas Relief 15.2.2
       BMP 15.2.2
       Camera Raw 8.7.1
       Camera Raw Filter 8.7.1
       Chalk & Charcoal 15.2.2
       Charcoal 15.2.2
       Chrome 15.2.2
       Cineon 15.2.2 (2014.2.2 x001 x003)
       Clouds 15.2.2 (2014.2.2 x001 x003)
       Collada 15.2.2 (2014.2.2 x001 x003)
       Color Halftone 15.2.2
       Colored Pencil 15.2.2
       CompuServe GIF 15.2.2
       Conté Crayon 15.2.2
       Craquelure 15.2.2
       Crop and Straighten Photos 15.2.2 (2014.2.2 x001 x003)
       Crop and Straighten Photos Filter 15.2.2
       Crosshatch 15.2.2
       Crystallize 15.2.2
       Cutout 15.2.2
       Dark Strokes 15.2.2
       De-Interlace 15.2.2
       Dicom 15.2.2
       Difference Clouds 15.2.2 (2014.2.2 x001 x003)
       Diffuse Glow 15.2.2
       Displace 15.2.2
       Dry Brush 15.2.2
       Eazel Acquire 15.2.2 (2014.2.2 x001 x003)
       Embed Watermark 4.0
       Entropy 15.2.2 (2014.2.2 x001 x003)
       Export Color Lookup Tables NO VERSION
       Extrude 15.2.2
       FastCore Routines 15.2.2 (2014.2.2 x001 x003)
       Fibers 15.2.2
       Film Grain 15.2.2
       Filter Gallery 15.2.2
       Flash 3D 15.2.2 (2014.2.2 x001 x003)
       Fresco 15.2.2
       Glass 15.2.2
       Glowing Edges 15.2.2
       Google Earth 4 15.2.2 (2014.2.2 x001 x003)
       Grain 15.2.2
       Graphic Pen 15.2.2
       Halftone Pattern 15.2.2
       HDRMergeUI 15.2.2
       HSB/HSL 15.2.2
       IFF Format 15.2.2
       IGES 15.2.2 (2014.2.2 x001 x003)
       Ink Outlines 15.2.2
       JPEG 2000 15.2.2
       Kurtosis 15.2.2 (2014.2.2 x001 x003)
       Lens Blur 15.2.2
       Lens Correction 15.2.2
       Lens Flare 15.2.2
       Liquify 15.2.2
       Matlab Operation 15.2.2 (2014.2.2 x001 x003)
       Maximum 15.2.2 (2014.2.2 x001 x003)
       Mean 15.2.2 (2014.2.2 x001 x003)
       Measurement Core 15.2.2 (2014.2.2 x001 x003)
       Median 15.2.2 (2014.2.2 x001 x003)
       Mezzotint 15.2.2
       Minimum 15.2.2 (2014.2.2 x001 x003)
       MMXCore Routines 15.2.2 (2014.2.2 x001 x003)
       Mosaic Tiles 15.2.2
       Multiprocessor Support 15.2.2 (2014.2.2 x001 x003)
       Neon Glow 15.2.2
       Note Paper 15.2.2
       NTSC Colors 15.2.2 (2014.2.2 x001 x003)
       Ocean Ripple 15.2.2
       OpenEXR 15.2.2
       Paint Daubs 15.2.2
       Palette Knife 15.2.2
       Patchwork 15.2.2
       Paths to Illustrator 15.2.2
       PCX 15.2.2 (2014.2.2 x001 x003)
       Photocopy 15.2.2
       Photoshop 3D Engine 15.2.2 (2014.2.2 x001 x003)
       Photoshop Touch 14.0
       Picture Package Filter 15.2.2 (2014.2.2 x001 x003)
       Pinch 15.2.2
       Pixar 15.2.2 (2014.2.2 x001 x003)
       Plaster 15.2.2
       Plastic Wrap 15.2.2
       PLY 15.2.2 (2014.2.2 x001 x003)
       PNG 15.2.2
       Pointillize 15.2.2
       Polar Coordinates 15.2.2
       Portable Bit Map 15.2.2 (2014.2.2 x001 x003)
       Poster Edges 15.2.2
       PRC 15.2.2 (2014.2.2 x001 x003)
       Radial Blur 15.2.2
       Radiance 15.2.2 (2014.2.2 x001 x003)
       Range 15.2.2 (2014.2.2 x001 x003)
       Read Watermark 4.0
       Render Color Lookup Grid NO VERSION
       Reticulation 15.2.2
       Ripple 15.2.2
       Rough Pastels 15.2.2
       Save for Web 15.2.2
       ScriptingSupport 15.2.2
       Shake Reduction 15.2.2
       Shear 15.2.2
       Skewness 15.2.2 (2014.2.2 x001 x003)
       Smart Blur 15.2.2
       Smudge Stick 15.2.2
       Solarize 15.2.2 (2014.2.2 x001 x003)
       Spatter 15.2.2
       Spherize 15.2.2
       Sponge 15.2.2
       Sprayed Strokes 15.2.2
       Stained Glass 15.2.2
       Stamp 15.2.2
       Standard Deviation 15.2.2 (2014.2.2 x001 x003)
       STL 15.2.2 (2014.2.2 x001 x003)
       Sumi-e 15.2.2
       Summation 15.2.2 (2014.2.2 x001 x003)
       Targa 15.2.2
       Texturizer 15.2.2
       Tiles 15.2.2
       Torn Edges 15.2.2
       Twirl 15.2.2
       U3D 15.2.2 (2014.2.2 x001 x003)
       Underpainting 15.2.2
       Vanishing Point 15.2.2
       Variance 15.2.2 (2014.2.2 x001 x003)
       Virtual Reality Modeling Language | VRML 15.2.2 (2014.2.2 x001 x003)
       Water Paper 15.2.2
       Watercolor 15.2.2
       Wave 15.2.2
       Wavefront|OBJ 15.2.2 (2014.2.2 x001 x003)
       WIA Support 15.2.2 (2014.2.2 x001 x003)
       Wind 15.2.2
       Wireless Bitmap 15.2.2 (2014.2.2 x001 x003)
       ZigZag 15.2.2
    Optional and third party plug-ins: NONE
    Plug-ins that failed to load: NONE
    Flash:
       Libraries
       Adobe Color Themes
    Installed TWAIN devices: NONE

    Try a preference reset: Press Cmd+Opt+Shift (Mac) or Ctrl+Alt+Shift (Win) immediately after initiating Photoshop startup. Select "yes" when prompted.

  • Color shift printing from Lightroom 1.3

    Windows Vista, HP officejet Pro L7580 printer, Lightroom 1.3, Photoshop CS3. All that being said and having used Photoshop since ver 5 with a variety of printers I find myself stumped with my latest soup of hardware and software. Screen colors do not print out anywhere close on paper when I try to print from Lightroom. Move the file over via "edit in Photoshop" and print from there and everything is fine. In Photoshop, whether Photoshop or the printer controls the color there is no problem. In Lightroom, however I have no control that I can find. I have no additional profiles so the printer controls the color. Photoshop and the printer are both set to AdobeRGB1998.icc. Other then just printing from Photoshop what am I missing in Lightroom?
    By the way Adobe, in the future think about either Lightroom or Bridge but not both.

    Hi,
    Just a reminder for those who missed that thread (I guess this fix also
    applies to LR 1 although I didn't check):
    [FIX] Darker prints and color shifts when printing from Lightroom 2
    (this is for Windows - Mac users please look here for a similar fix:
    http://www.computer-darkroom.com/lr_13_print/lightroom_print.htm )
    The problem :
    When printing RAW or TIFF files from LR2, you get a printer output that
    is much darker than it should be and that presents various color shifts.
    I'm using an Epson Stylus Pro 3800 with the latest Windows driver
    (6.50 - which is rather old by the way). The workaround described below
    works for me under Windows XP SP3. It should also probably work with
    other systems/printers/drivers. Use at your own (minor) risk.
    The "official" procedure for printing from LR is as follows:
    1. Do not let the printer manage colors and select "Other..." from the
    profile dropdown list and select the ICC/ICM paper/printer profile that
    you want to use.
    2. Click on Print... in LR which opens the Print Settings dialog.
    3. Select the options you need and the paper you're using.
    4. *Disable the color management from the driver's side* (in Epson's
    drivers, "Mode | Custom | No Color Adjustments").
    5. Print
    Unfortunately, *this doesn't work* for many of us and this produces a
    print that is dark and has color shifts as mentioned above. Note that
    the same image prints correctly from QImage or Photoshop CS3 (that is,
    the printer output corresponds to what you see on your calibrated
    display).
    Apparently, although color management has been (allegedly) disabled in
    the driver, there's something wrong between LR and the driver which
    makes that both LR and the driver are still trying to manage colors. In
    other words, the "No Color Adjustements" option of the driver doesn't
    seem to work with LR.
    The workaround (found after hours of hair pulling and paper and
    expensive ink wasting):
    In step #4,
    1. Instead of selecting "No Color Adjustments", set Mode to "Custom |
    ICM
    2. Click Advanced...
    3. Check "Show all profiles".
    4. Select Driver ICM (Advanced)"
    5. Set *both* the "Input profile" and the "Printer profile" fields to
    the very same profile that you specified in LR.
    That is, if you specified Pro38 PGPP (Premium Glossy Photo Paper) in LR,
    then also select Pro38 PGPP in both "Input Profile" and "Printer
    Profile". This has actually the same effect has disabling color
    management in the driver (what "No Color Adjustements" should normally
    take care of).
    That's it. When printing, you'll get exactly the same color results as
    when printing from QImage or Photoshop. No more dark prints. No more
    color shifts.
    One might think that the bug is in the Epson driver but in that case,
    QImage would have the very same problem. So I tend to think that the bug
    is on the Lightroom side.
    Hope this helps.
    Patrick

  • How to get the best from Lightroom with my Nikon D700

    I am having real trouble with the results from Lightroom from my Raw files.
    I love Lightroom but am going to have to use another program unless I can figure out what to do.
    Can anyone give me any advice?
    I have never had to use presets etc. so am in need of basic help please.

    Ed
    I assume you tried to:
    If you are on Mac OS X, drag the "Camera v2 beta" folder to:
    /Library/Application Support/Adobe/CameraRaw/CameraProfiles
    Do you have admin rights on your mac?  Otherwise, I am not to up on macs, and hopefully someone with more expertise can help with the installation.
    Cheers
    Rory

  • Lacking true native "Deferred" or "Promised" file drag from JAVA

    Hello all,
    I have been playing around with the drag and drop APIs for quite some time (about 1.5+ years) and I am having a problem producing functionality similar to dragging network-based files in "Windows Explorer". I am not sure if I have overlooked something or if DnD with the native OS is lacking a huge piece of functionality. I would appreciate hearing people's feedback or experience with similar problems.
    First, some background. My company's applications provide remote access to a central storage of digital assets (read "files"). Our client provides a view of the files on the server. We have C++-based applications running on both Windows and the Macintosh are able to drag from our application to the desktops and Explorer windows. However, in these drag operations, they each employ a mechanism to hold-off providing the native OS file data until the drop has successfully completed. The OS in each case provides a "callback" to notify our application that the drop succeeded and that we should go and transfer the files. In this way, we can pay the price of transferring the files locally ONLY when the drop occurs (same thing can be applied to the Clipboard).
    However, from what I can tell, the AWT/SWING DnD APIs provide no mechanism to do this type of operation. In order to drag files to the native OS, you must explicitly provide the files BEFORE you initiate the drag operation (or place them on the clipboard). This places doing viable native drag and drop from our JAVA applications in serious jeopardy and is causing a great deal of displeasure from our management who are questioning the "readiness" of JAVA.
    Since I can't seem to find a way to accomplish this, I have tried entering enhancement requests (about 8 to date), but I have failed to hear back about a single one. I think that either Sun does not monitor some of their enhancement lists or they do not want to address this heavily-desktop oriented issue (I am not sure if this scenario is even possible on a UNIX machine where most things must be "mounted" locally before they can be viewed -- SMB browsing may be the only exception that comes to mind but I do not know if anyone has done this).
    In the meantime, we have attempted to change the workflow of our application. We have provided a JAVA window that mimics the filesystem so that we can get the drop event and provide the illusion of a "deferred" drag. In addition, we have provided and "export" feature that places the file locally afterwhich they may grad anywhere they desire. Both of these solutions are hacks and leave a very bad taste in our user's mouths. We can try to write JNI pieces, however, there are just too many UI locking issues to contend with to ensure a timely release of our software.
    Has anyone else run into this before? Can anyone provide a more useful workaround? Is it possible to get this issue looked at from SUN? If SUN is looking at it already, what kind of timeframe are we looking at until a potential solution?
    Thank you for your time.
    Michael Macaluso

    I am curious about the verdict for "deferred" file transfers. I have hit the same wall. I have a JAVA client window that allows the user to browse a network file repository. Most of our clients use a Windows platform, so that is my primary interest. I was hoping to: 1)capture the drop event, 2) request the data from the server, and 3) stream it to a temp file/ or to the destination directory, and 4)allow the file system to transfer the temp file. However, I cannot find any documentation regarding this issue.
    So I wanted to swtich tracks and set my transferrable data to represent a file on the central server, but that would require a URL object, and I have failed to set the MIME types correctly for NTFS to recongize the transfer. Sorry I don't have any answers. Any suggestions?

  • Edit in Photoshop CS6 from Lightroom 4.1 fails

    I am using LR 4.1 and PS CS6 on a Win7 64bit system.  Previously with LR3 and LR4 I was able to "Edit in Photoshop" from Lightroom to CS5 and all was well.  Now with LR4.1 and PS CS6 when I "Edit in Photoshop CS6" I get a partial image.  Any image that I try produces various versions of this.  The attached screen capture shows a blank area in the upper left corner.  Other images have shown several smaller blank areas in various positions on the image, and one image contained several blank areas plus a small inset of the image.
    This is quite frustrating, as I generally use LR to crop and make minor adjustments in a photo, then edit some photos in PS.  Now I can no longer edit anything in PS without first exporting the image from LR, work on it in PS, then save it and reimport it into LR.  Very inconvenient.
    Please advise what I am doing wrong or let me know if there is a workaround.
    Thanks in advance,
    -Herschel

    This is probably a video card driver bug which has been reported in the PS forum from time to time. It's a PS problem, not a LR problem.
    Assuming this is Windows, go to the video card maker's website and download an updated driver. Don't rely on Windows update; they're frequently several versions behind. On a Mac it would have to be through OS X updates.

  • From Lightroom to Powerpoint

    I am working with a Professor who has a large image catalog in Lightroom 3 for Windows. She has to develop Powerpoint presentations for lectures. The presentations are just image slideshows, no graphics or text, but I still don't think Lightroom's Slideshow module will be ideal for her because of the widespread use and acceptance of the Powerpoint format -- classroom projectors already set up for Powerpoint format presentations.
    Right now the only way we know to get images from Lightroom to Powerpoint is a) export from Lightroom, b) import into Powerpoint, and then c) eventually delete the images exported (once they are "in" Powerpoint.
    Drag and drop does not seem to work, nor does copy and paste. (I have a feeling these might work under Mac OS but she is strictly Windows-only.)
    Anyone know a better way of getting images directly and easily from Lightroom into Powerpoint?
    Alternatively, anyone know if Lightroom's Slideshow tool can spit out Powerpoint-format presentations, or their functional equivalent?
    Many thanks for any help. Lo

    My impression is that the PDFs exported by Lightroom have fixed slide timings, whereas she needs her presentation to behave like Powerpoint in the sense that she, while lecturing, clicks a clicker or just hits the spacebar to go to the next image.

  • Just got me a new camer canon 5D mark iii and now I can't send the images from lightroom to open in photoshop anymore

    Hi Mark, I have lightroom and Photoshop CS6 and worked with it with my old camera, Canon 60D and had no problem
    now I got me a new one, Canon 5D Mark iii and I can import the images into lightroom but I can't not send it from lightroom to photoshop. Also tried to drag and drop the picture image directly into photoshop but it wouldn't allow me to do so.
    What do I have to do to get that working?

    In Bridge, go to Edit->Preferences->File Type Associations

  • Is it better to print from Lightroom or Photoshop

    Just wondering if one produces better results.

    Hi pipflash ,
    This article will should clear up any doubt, follow the link Should I Print From Lightroom or Photoshop? - Rocky Mountain School of Photography

  • Printing from Aperture, and printing from Lightroom.

    Hello,
    I have noticed when I print from Aperture using my Canon i9950 and a custom paper Colorsync profile, and if I then print from Adobe's Lightroom using the same Colorsync profile and paper, the print from Lightroom is much sharper. The Aperture print is exact in every respect except it is noticeably softer.
    Anyone else notice this? And if so is this a recognised problem that may be fixed in 1.1?
    Kind regards,
    Anil K Solanki
    G4 Dual 867   Mac OS X (10.4.5)  

    Hi Charles, I totally agree with you. Lightroom's printing features are really excellent. In comparison Aperture almost seems like the printing of photographs was something the Aperture dev team bolted on at the last minute.
    I sincerely hope Apple sort out, what for me is inexcusable in a professional commercial app. A few photographers I know are going to use the next release of Aperture as a turning point, if it can't print as good as the Beta Lightroom then they will become Lightroom users and say good bye to Aperture.
    Apertures sorting and logging tools really are second to none, but if the print quality is poor, what is the point. I know for a large number of photographers, producing prints is not high on their list of needs, especially if they are supplying prints for publication or the web. But if I want to do what my old fashioned enlarger can do, which is create great prints, then hey I am not going to get it with Aperture.
    I know Apple can fix this, I just hope they do.
    Anil.

  • Saving PSD files after exporting from Lightroom saves incorrectly

    I've only recently moved to Lightroom from using Photoshop/Bridge together, so I'm not 100% sure how saving files exported from Lightroom should go. But here's what I experience:
    Base edit of file within Lightroom
    In library view, right click on image -> Edit in -> Open as Smart Object in Photoshop
    Perform all my necessary edits and such
    File -> Save As, and save it to another location as a PSD file (totally different HDD)
    Perform more edits....
    Shortcut CTRL+S to save, and it saves it as the TIFF file under the location it was originally in within Lightroom
    Eh...? Am I missing something. It should just save as the original PSD I created when I went "Save As". I have seen on a few occasions, immediately after "Save As", the file name resorts back to TIFF and not as PSD.
    My settings for External Editing in Lightroom are as follows:
    File Format: TIFF
    Color Space: ProPhoto RGB
    Bit Depth: 16 bits/component
    Resolution: 300
    Compression: None
    Does anyone have any ideas what I'm doing wrong? Also, to note, that sometimes I double click on the Smart Object within Photoshop to load Camera Raw and perform some edits, but not often.

    Modesto Vega wrote:
    Replying to your last 3 posts.
    Re Camera Raw being used to pass an image to Photoshop
    a) I am assuming this is independent of the Compatibility level in Preferences\File Handling DNG creation.
    b) Does the same apply to other photo editing software made by Adobe like Elements?.
    Reply: Yes, the principle is the same. Photoshop Elements cannot read raw data either. That's why it has to be converted before it's opened.
    c) Assume that I have LR 5.7.1 and CS5. Is Camera Raw is still used to pass an image to Photoshop? If so, why is there a need to get LR to behave differently?
    Reply: Camera Raw is used IF you choose the option to open anyway. Then Camera Raw will be used to convert the image that's opened in Photoshop. But since it is older than Lightroom some of the new adjustments might not be transferred to Photoshop. That's why there is a need to let the user make the choice.
    d) Sometimes it does seem as if Adobe might be using Camera Raw updates and process version updates to get consumers to change their habits, this includes having to buy subscriptions or having to change workflow to some ideal that somebody at Adobe or working with Adobe might have in mind.
    Reply: The fact is that in the past, when a new version of Photoshop is released then all support and updates cease for the previous version. Since the introduction of the creative cloud, at least users of Photoshop CS6  get support for new cameras. They just don't get the new features. Yes, there's motivation to upgrade. Adobe is a business. What do you really expect?
    Re stacks
    I find impossible to see collapsed stacks on the film strip. Stacks are only visible on the Library module and using a grid view; I don't say clearly visible because they are only recognisable by the label at the top left corner with the image count; I don't even think it is possible to change the colour of that label or the grey colour surrounding an image. Also I cannot name stacks. If I could name stacks, see them as virtual folders underneath a library folder and make them glaringly visible I would use them extensively.
    Reply: The only reason I can think of that you are unable to see collapsed stacks on the filmstrip is if you have the filmstrip reduced in size to the point that Lightroom can't display all the icons. I'm able to see the collapsed stacks in the library grid view and on my filmstrip
    Re storing your Raw files and processed files in separate locations
    Assuming Raw files are negatives and Photoshop files are transparencies or prints, would you want negatives being handled/read on a regular basis? If anything happens to your negatives, you would never be able to produce another print or another transparency again.
    Reply: The raw files or the negatives, as you put it, are never modified by Lightroom. They always remain in their pristine state they were in when they were imported. If I have a backup of that raw file then I can do whatever I want to the one in my working folder. Resetting that raw file so that it looks unaltered is just a click away.
    I have worked extensively with databases and database systems, it is a standard feature of database systems to be able to choose where to store different database objects. I don't see why LR cannot do the same, it is a database after all. I do agree with both the OP and photo.
    Reply: Well, I won't argue that point. If that's what you really want than lobby for it. It just won't get my vote because I don't see any real advantage.
    If you read back through this quoted message you'll find that my replies are included. I don't know how to separate them out so they are highlighted properly. Read through it and think about it. But personally, I don't want to waste anymore time on this discussion because it isn't accomplishing anything in my opinion.

  • Exporting from Lightroom 1.3: Different sort order than defined in Grid view

    Just did an export from Lightroom 1.3 and ended up with a the wrong export order.
    Here is what I did.
    1. Create a collection
    2. Drag the pictures I want to export into that collection
    3. Select: Sort: Import order (In lightroom grid view - the sort order was correct)
    4. Export from Lightroom with "Userdefined name - sequence"
    The result is a total different sort order than I can see in the Lightroom Grid view.
    Very annoying.
    Any ideas?
    Also - in the new export dialog there seems to be no option anymore to CHANGE a user-defined export like in the previous version. What do you do if you want to change something?
    Overwrite with the same name?
    Remove old export and add the new one changed?
    greetings
    gfisch

    Are you seeing this only in Lightroom? They are not 'still in the parent, Germany folder.' only visible their if you have 'Include Photos from Subitems' checked in the Menu/Library of Library.
    Uncheck that you you will only see them in their correct folders.
    Don
    Don Ricklin, MacBook 2Ghz Duo 2 Core running 10.5.1 & Win XP, Pentax *ist D
    See LR Links list at my
    Blog for related sites.

  • How to Publish to Revel from Lightroom using a Facebook Account

    I signed in to my Revel Account using my Facebook Account.  I'm trying to publish from Lightroom but it's not accepting my Facebook ID and Password.  How do I publish from Lightrrom using a Facebook account or how do I switch my Revel Facebook login to my Adobe login?  Any help is appreciated.
    Thanks

    Hello
    To set up publishing to Revel 1.10  is easy in Lightroom 4. I would suggest that you update to Lightroom 4.4 first. You can goto the help menu in Lightroom and then select " Check for updates" then update to version 4.4. Also make sure you have updated to Revel 1.10
    Here is the instructions to do this for Revel as its similar to set it up for Facebook too. It is pretty simple to set up. http://help.adobe.com/en_US/lightroom/using/WS2bacbdf8d487e582-46da1b6f13419e06a64-8000.ht ml
    Here you will see the Lightroom Publishing Manager. Click on the Revel tab and then select Authorize  Revel button. You will then be prompted to sign into your Revel account. If your Facebook account log in information is not working then I would suggest to log in with your Adobe ID. You are best to do that anyway.
    In the image below you can see that I created separate albums for pictures. Then you can drag your photos to these folders and click publish. Then check your Adoberevel.com to see if the images show. Once you see that they uploaded in the upperleft of Lightroom, then you should see the images show in Revel.
    You can publish to Facebook from Lightroom the same way. Just click on the facebook tab on the publishing manager and authorize the Facebook connection with your Facebook log information. You will then be prompted to log into your Facebook account thru a browser.
    http://help.adobe.com/en_US/lightroom/using/WS2bacbdf8d487e582-46da1b6f13419e06a64-8000.ht ml
    Let me know if this helped you out or if you have any questions
    Thanks
    Scott

  • I am trying to import developed images from LightRoom 5 in o Photoshop 6.  I am receiving this message and the images will not open.....'Could not open scratch file because the file is locked, you do not have necessary access permissions or another progra

    I am trying to import developed images from LightRoom 5 Photoshop 6 for further editing.  I am receiving this message and the images will not open.....'Could not open scratch file because the file is locked, or you do not have necessary access permissions or another program is using the file.  Use the 'Properties' command in the Windows Explorer to unlock the file. How do I fix this?  I would greatly appreciate it if you would respond with terms and procedures that a computer ignorant user, such as me, will understand.   Thanks.

    Have you tried restoring the Preferences yet?

Maybe you are looking for

  • Error while loading shared libraries: libjvm.so

    Hi, Hopefully, this is the right list for this problem. I am working on a computer that has Linux 2.6.20-1.2952.fc6. I am trying to deploy a program to a Sun SPOT using over-the-air functionality; however, I get the following message: -pre-suite: -do

  • Can you set a minimum width?

    Is there any way to set a minimum width for any point on the image that you're producing or already produced?

  • . How do I get it to recognize my ipod and regain functionality

    My home computer crashed and I lost ipod program. I have installed on my work computer. How do I get it to recognize my ipod and regain functionality?

  • Audio edit not working. Can't cross fade

    Suddenly when I attempt to select the end of one audio track and the beginning of the other, it does not become high lighted as usual and I can't apply a cross fade. I never had this problem before and it suddenly appeared. If I double click I get an

  • Importing Problem from HD video camera to FCE

    I just bought a macbook pro retina with all the bells and whistles.  Tried importing video from Canon Vixia HD21  which I have been using successfully with my macbook for years.  Set the import to Apple intermediate Codec but machine will not go to F