Invidia Tesla support in Lightroom?

Does LR 2.1 take advantage of Invidia's Telsa GPU? Tesla allows offloading computations to the GPU.
If yes, has anyone tried a Tesla graphics card?

And, I hope it never does. The mess that Adobe created with CS4 using the
GPU shows that this technology isn't ready for prime time and probably never
will be since a great number of the problems has to do with the video
drivers. Shame really finally something else to use a good video card for
and the video card makers can't put out a good driver.
Robert

Similar Messages

  • "The file is from a camera that is not recognized by the raw format support in lightroom"

    I get this error message every time I try to upload raw files to lightroom 4 on my mac. I have a nikon d600, So the camera is supported by lightroom. Furthermore, I have downloaded these same files, with no problem, on my desktop in lightroom.

    If you are downloading straight from the camera it is fraught with problems.
    Numerous different cameras from different manufacturers don't play nicely with Lightroom (it may be the other way around too).
    If you have been trying to use a card reader ignore this post.
    Tony Jay

  • Panasonic Lumix FZ1000 RAW files support in Lightroom 4

      http://blogs.adobe.com/lightroomjournal/2014/07/camera-raw-8-6-and-dng-converter-8-6-now-a vailable.html
    The above says that Panasonic Lumix FZ1000 RAW files are supported in camera raw 8.6.  I specifically checked before buying the camera.  Everything I have ever read on the Adobe website for some 3+ years said that if a file in supported in Adobe Camera RAW, it is also supported in Lightroom.  Particularly, the above URL did NOT give any warning about the FZ10000 RAW files NOT being supported in Lightroom 4.  I went ahead and purchased the FZ1000, only to find I'm now having problem with Lightroom 4 not recognising the RAW files at all.  I'm really annoyed, as I was so careful to check the Adobe website first.  WHAT THE HELL IS GOING ON WITH CAMERA RAW AND LIGHTROOM?????

    I do appreciate the many RAW file formats being created by the camera manufacturers, as I have had varying cameras with the varying formats, and so am very aware of the whole business of making sure how those formats will fit into my software.  And, as already stated, appreciate Adobe's efforts to deal with all those formats.
    This whole exercise has been upsetting, and there has been some good advice and info provided in this discussion. 
    And unfortunately, some input that has been a little too technical and not particularly helpful.  I feel that some of the input was a little too critical and didn't recognise that maybe some of us aren't so are highly involved and knowledgeable in Adobe products and the technicalities of how the software works, dot versioning of software, executable coding etc. because we don't need to, and shouldn't have to.  I have bothered to learn Lightroom well in terms of its functionality including matters raised by you (eg making LRoom edits visible in other software, knowing that LR is not making changes to the actual files, rather they are in sidecar or xmp files etc.).  I have bothered to learn a reasonable amount of computer-related info to understand things in plain English terms, such as "to have PShop and LRoom to recognise my RAW files, I need to have ACR.  To have them run on my PC, they must be compatible with Windows operating system version xxx.  For many people, this level of knowledge should be enough.
    I have NOT said I expect Adobe to get advance copies of file formats from manufacturers;  I have NOT said that I expect Adobe to support every new camera model immediately.
    The technicalities of the coding and whether Lightroom "uses" the ACR plug in or not is not quite so much the issue, and I don't find the statement that "Lightroom does not use the Camera Raw plug-in" helpful.  I don't think it's really right either.  Lightroom - one way or the other - DOES "USE" ACR as the ability of Lightroom to recognise files is very much dependent on the version of ACR that you have.  LRoom may not use the ACR plug in as PShop/Bridge in the exact same way (eg for the actual editing of files such as exposure, white balance etc.), but Lightroom DOES USE the ACR PLUG IN.... in regard to the file recognition issue.
    And Yes....  I made a mistake.  Somehow, despite what I thought were good efforts to research the Lumix's support in PShop CS6, Bridge, ACR and Lroom 4, I got it wrong.  I will accept that it was my mistake and I'll accept my part in this, but I won't be made to feel that that it's been "totally" my fault, stupidity, whatever. 
    Thanks to all the people who have provided useful comment and input to my original question and subsequent responses throughout this discussion.  I will indeed now consider options like the DNG converter.  I was aware of the whole cloud thing, and had been thinking I would upgrade in perhaps a couple of years time (for both Pshop and LRoom) - I'll have to consider upgrading sooner rather than later. 

  • I have installed Adobe Lightroom CC.  In the process of launching, a popup appears, that says:  "AN INTERNAL ERROR HAS OCCURRED.  Cannot create the required folder:  /Users/(my user name)/Library/Application Support/Adobe/Lightroom/Develop Presets."  So e

    I have installed Adobe Lightroom CC.  In the process of launching, a popup appears, that says:  "AN INTERNAL ERROR HAS OCCURRED.  Cannot create the required folder:  /Users/(my user name)/Library/Application Support/Adobe/Lightroom/Develop Presets."  So even though Lightroom CC is installed, it will not launch.  What do I need to do to allow it to launch?

    The problem was solved today.  Here's the full story.  I'm a Mac user.  At first I installed Lightroom CC on my iMac (desktop).  I had this problem so I called Adobe, and was referred to a "special unit" .  After about an hour the tech solved it for me ... we did a screen sharing and she took control of my computer for a loooong time.  Because of language difficulties, at first I wondered if she knew what she was doing but she eventually solved it.  Although she couldn't explain exactly what she was doing, she summarized it by saying "it was a permissions problem."  I asked if I would have the same issue later when I installed it on my laptop (Macbook Air).  She said probably not.
    But I did.  The same internal error popup arose on launch and launch did not complete on my laptop.  I tried chat but no joy so I eventually called Apple Care.  I had noticed that on my laptop (and the iMac for that matter), that there was no Library folder after my user name.  The Apple tech explained that the Library folder is actually there but it is hidden because it's very easy for users to do some very nasty things to their computer by going astray while in the Library folder.  The folder is actually there, but they hide it.  I did remember seeing that the tech helping me with my iMac had typed the work "Library" while she was controlling my computer.  Basically she had activated the hidden Library folder so she could open the path that Lightroom was trying to follow to create that "Develop Presets" folder.  For some reason, the inability to create that folder in the launch process was preventing launch from being completed.  The Apple tech said she didn't actually have to do that and activated the Library folder by use of the Go selection on the menu bar.  Anyway, once that complete path was replicated and opened, the next step was to go to the Lightroom Permissions field and add my user name to the user categories already there and enable "read and write" permissions to my user name.  Once done, I shut down my laptop, and then rebooted.  I launched Lightroom and then boom, voila, heavens to betsy, etc. it launched and suddenly a dismal weekend turned into a great one. 
    I am not a geek, so I hope this makes some sense.  I also hope Lightroom launches again tomorrow and beyond! 

  • Will there ever be support in Lightroom 4 for Olympus raw files

    Will there ever be support in Lightroom 4 for Olympus raw files?

    Which camera exactly?
    Support varies camera by camera.
    Supported cameras
    Camera Raw plug-in | Supported cameras
    Compatible Adobe software
    Camera Raw-compatible Adobe applications

  • Is there Camera RAW support for Lightroom 4.4 and Canon 7D Mark ii?

    I need Camera RAW support for Lightroom 4.4 and Canon 7D Mark ii.  Is there a Camera RAW version for me? 

    Thanks for your help.  I checked out DNG on YouTube and understand more
    about it.  I downloaded the DNG converter and transferred in files from my
    camera.  Then I imported into Lightroom.  It works!   Thanks again.
    On Wed, Nov 19, 2014 at 5:56 PM, Jeff Schewe <[email protected]>

  • Lens profile support in Lightroom 3 (Panasonic/Leica)

    I'd like to see some "micro four third" lenses, like the standard lens of the Panasonic DMC-GH1-K, supported in lightroom 3, even though the lens shows very little problems only.

    You can check to see if someone else has already created one by searching with the Adobe Lens Profile Downloader.

  • Lack of LAB and CMYK support in Lightroom is plain dumb

    There is a lack of consistency in Lightroom if it allows you to elect to edit an image in Photoshop but then it can't follow through and display either a LAB PSD or a CMYK PSD. Both these file types are widely used by Pro-photographers. Afterall there is a whole bunch of stuff that's easier to do in Lab or CMYK rather than in RGB. The lightroom development team seem to suggest that photographers shouldn't be doing anything more advanced than Lightroom can handle. Well if you look at pre-print sharpening Lightroom is still awful - LOW/MED/HIGH just doesn't cut it and isn't at anything like pro level. To get any sensible preprint sharpening you've almost gotta go to photoshop. For many images sharpening is best done on the L channel of Lab (along with a whole bunch of other adjustment layer corrections). Most people like to keep these layers and so returning a master file to RGB just isn't an option. Sure there is no further need for editing such an image in Lightroom, but as part of Lightroom's function is DAM then its fairly essential to be able to at least preview all your image files - to know where they are and what you have.
    Its just no good boasting about Lightroom's ability to search through images using metadata etc if ultimately it can't find and display your -finished- image versions 'cos they just happen to be Lab or CMYK PSDs.
    If Adobe Lightroom team are promoting Lightroom as a pro-photographers tool them you gotta listen to how pro-photographers work and not get lost in your own ideology based rhetoric of keeping Lightroom pure. I haven't yet found two pro-photographers with identical "pure" workflows.
    Come on Adobe - we don't want to edit them - we just want to be able to preview them in Library ;-)

    Have to say as a working professional who earns his keep from doing raw conversions, proof prints, cutouts etc Lightroom's lack of CMYK support is very much a pain in the a**. I'm not asking for a full set of CMYK editing tools - I've got those in Photoshop thanks very much.
    What I am asking for is at least the ability to round trip files from Lightroom into Photoshop, convert to CMYK and reimport the CMYK version into the catalog alongside the RGB file from which it originated and then to allow me to open the original CMYK file back into Photoshop without any tweaks being applied by Lightroom. This would allow Lightroom to really fill the role of a DAM in our studio and allow us much simpler workflow tracking than at present. As things stand we have to save the files in separate locations from our RGB versions on our server and then catalog them using another application.
    Come on Adobe please listen to your professional user base as I know I'm not alone in these requiements and the studios that I've shown Lightroom to have all ended up asking the question "What about the final CMYK versions?"
    BTW I'm in full agreement with Ian on the other points and without sounding snotty to Don - who I have read many interesting and sensible posts from - maybe if you don't want to cover this ground again just walk a different direction and leave those of us who do NEED this feature to discuss the best way of implenting it. I have also sent this request to Adobe so I'm not just a moaner who sit's here doing nothing about the issues that affect me.
    Cheers for now.
    Jason Hicking
    Replica Imaging Limited - UK

  • CMYK ICC profile support in Lightroom: Workaround?

    Ok, I know this is not the first time someone has brought this up and I know that Lightroom doesn't internally support CMYK printer profiles, and I'm not expecting it to do that given that the documentation specifically says it doesn't work, and it in fact doesn't work.
    I'm using OS X (Lion). I recently profiled a Lexmark C543dn color laser printer with a ColorMunki Photo and the profile works great with Photoshop's "built in" RIP/CMS/whatever, but I can't get ColorSync in the printer settings dialog to recognize the profile. If I use the ColorSync Utility to force the profile on the printer, it also doesn't work.
    What I would have expected for colorspace conversions when printing (from lightroom for example) is something like:
    Melissa RGB -> ProPhoto RGB (or sRGB, Adobe RGB, whatever, using internal lightroom stuff)
    ProPhoto RGB -> LAB (using a generic ProPhoto RGB profile that comes with the system or the software pkg)
    LAB -> printer native CMYK (using the custom printer profile I created)
    native CMYK data -> printer
    So I don't understand why Lightroom or whatever application doesn't "tell" the printer driver that it's getting data in ProPhoto RGB (or whatever) at which point the driver should convert to LAB (or whatever PCS is specified) and then to printer native CMYK with the custom profile.
    Does anyone know of a way to make this happen?

    I'm not a professional, only a hobbyist, so it took me a little longer, but I also have the impression that the new Preview ignores ICC profiles.
    I noticed it when moving images between my iBooks built-in and my external Eizo screen. Since the gamut of the second is much larger, images appear rather different on the two screens. In Tiger's Preview, this resulted in colors changing suddenly during the move, when the center of the image passed from one screen to the other. This effect is gone and yes, the images are over-saturated on the 'good' screen.
    Jethro555, could you find a solution to the problem?

  • Does anyone know when there will be Camera Raw Support in Lightroom 3 for the Olympus E-PL2?

    Just bought the Olympus E-PL2, shot some test shots and came home to open my RAW files to view them and discovered that they won't open in lightroom because the .ORF files for the E-PL@ are not supported. I figured since the E-PL1 was supported this would be too.There are some minor differences between the two like base ISO, etc. I am new to RAW and notices that E-PL1 users experienced the same thing when it first came out. How long does it usually take for Adobe to get new cameras compatible with Camera Raw? The camera is very popular and I imagine people will want to use the program to process their files. Will that speed up Adobe's process? And in the mean time, does anyone have any suggestions on what program I can use to open my .ORF raw files?
    Thank you in advance,
    Anthony

    It isn't a plug in. It is a tool that allows you to read and write to the Exif data. See the web site for how to use
    Keep a copy of your original files. It doesn't cause any problems changing the camera maker name.Usually this is the only thing that has actually changed between each version of the same camera in the RAW file. However until this has been checked by ADobe and they have created a specific colour calibration it Adobe don't support the format. This does not prevent you hacking the format as long as you understand what you are doing and that you keep original copies to import once Adobe support it
    If manufacturers used DNG there would be no problems, but until they do you may have to wait for up to three months for Adobe support. However Adobe do usually issue a RC of the next version of LR and ACR before the full update, that may be any time now. Certainly there is a beta version that includes support for this camera as it has been used by reviewers

  • My Nikon D610 raw is not supported by Lightroom 4.4. How can I get it to work? Is there a plug in to fix it or do I have to upgrade to Lightroom 5?

    I am not using Creative Cloud, just have Lightroom and Photoshop installed on my computer.

    For native file support you should upgrade to LR 5. However, you can read D610 files in LR 4 if you need by converting them to DNG using the latest DNG converter, which is a free download from Adobe.

  • Canon 6d raw support in Lightroom 3.6

    Is there a way to update lightroom 3.6 with a newer version of camera raw that will support a Canon 6d raw file?

    No.
    You can update to LR 4.3 or you can use the free DNG converter to convert your raw files to DNG for 3.6.

  • Scanner NEF not Supported by Lightroom 2?

         I am trying to decide on some workflow options for scanning negatives with a Nikon scanner.  It has been suggested that raw image data from a Nikon scanner can best be processed by having the scanner output in NEF format and using Nikon Capture NX 2 as a raw editor. The basis for this suggestion is that ACR does not support scanner NEF.  Apparently, neither does Lightroom 2, or so I am told.  Having reviewed comments in Adobe forums, some seem to hold the opinion, often vociferously, that scanner NEF is not truly raw data, is a complete waste of time, and scanned images should be output as TIFFs rather than NEFs.  Also, despite the official line that scanner NEF is not supported, scanned images that were output as NEF, and saved as NEF images, seem to be working just fine in Lightroom 2, although I haven't tried a full processing workflow on them yet. (In the interests of full disclosure I hold out the possibility that I may have somehow converted these images into a conventional form of NEF at some point after scanning).
         I apologize for that lengthy introduction.  Here are my questions:  (1)  How is scanner NEF different from "true" raw image data; (2)  what are the consequences for optimization of scanned NEF images in Lightroom 2 -- am I simply using Lightroom tools without getting the full benefit of processing "true" raw information, as in the case of TIFFs and JPEGs;  (3) what does it mean that Lighroom 2 and ACR do not support scanner NEF anyway since I am (apparently) able to open and process them in Lightroom 2;  (4) if  Lightroom 2 does not fully support scanner NEF, is there anything to be gained by outputting to NEF (rather than TIFF) and using Nikon's proprietary RAW editor (which I am told does not officially support scanner NEF either, but still works) instead of LIghtroom 2 for NEFs?

    Short answer - scan the images as TIFF and make life easier for yourself.
    Longer answer:
    1. A true raw file is still in it's mosaiced form whereas a scanner NEF is a fully rendered TIFF with a different extension
    2. Same as editing a TIFF, PSD or JPEG. The adjustments are parametric and therefore only readable in Lightroom and ACR. In order that you can actually open them into Photoshop or another editor it will be necessary to export the files as TIFF, PSD or JPEG.
    3. It means that they aren't treated as true raw files. Refer to above.
    4. There is nothing to be gained.

  • Just purchased Nikon D610. tried to import 3 images and got this message: The files are not recognized by the raw format support in Lightroom. How do I fix this frustrating problem. Have been using Lightroom for years also Nikon products without any prior

    How do I import images. Have a message that says: The files are not recognized by the raw format suppot in Lightroom. Am using a Mac version 10.9.4. the import is from a new Nikon D610. Am using LR 4.4 Please help Adobe is useless as a support.

    Each camera must be supported explicity and your LR version is years older than your camera.
    According to Adobe's Camera-support page, you need at least LR 5.3 to work with your D610 NEFs in LR:
    Camera Raw plug-in | Supported cameras
    If you don't want to upgrade to LR 5, or can't due to your OS being too old, then it might work to use the latest DNG Converter and create DNGs from your NEFs, which should open in LR 4.x.  You can find the DNG Converter here:  http://www.adobe.com/downloads/updates

  • Pentax K-7 support in Lightroom 2.4 not quite complete?

    Hi,
    I have my K-7, and Lightroom 2.4 installed. Lightroom reads K-7 pefs and dngs, but doesn't seem to do anything with the lens aberration info included in the pef files when that feature is enabled. Am I correct, and if so, is this just temporary, or a permanent situation? My understanding is that Lightroom does recognize and use the lens aberration info included in raw files created by the Panasonic DMC LX3 camera.
    I understand that Adobe has updated the DNG standard to support the inclusion of such info in dng files. But no camera currently on the market supports this standard yet of course.
    Just wonderin'
    Mike

    but doesn't seem to do anything with the lens aberration info included in the pef files when that feature is enabled. Am I correct, and if so, is this just temporary, or a permanent situation?
    That is correct. Lightroom cannot read and use any lens aberration info from cameras other than the Panasonic LX3 and Leica that uses the exact same sensor, lens and electronics. This is in there because Panasonic would not allow Lightroom/ACR to render their RAW files without Adobe correcting for the distortion. They were worried people would see that their lens distorts and fringes very strongly if you would just get a straight RAW rendering.
    Nobody knows whether the corrections will will be added to LR/ACR in the future for other cameras, but it would be an obvious next step. Very likely would be automatic LCA correction and barrel/pincushion distortion correction (perhaps not automatic but a simple slider like in the lens distortion correction in Photoshop)
    I understand that Adobe has updated the DNG standard to support the inclusion of such info in dng files. But no camera currently on the market supports this standard yet of course.
    Correct on both. We'll see what Adobe does next.

Maybe you are looking for