Lightroom :: Can No Longer Use Cable With D700 In 4
Apr 6, 2013
When I first purchased my D700, I didn't have a CF card reader, so I've been using a cable with it to import my photos and love doing it that way. All of a sudden, the cable won't work with LR4 anymore. I can still use it to transfer photos to my computer, and THEN import into LR4 but that takes double the amount of time, and it's miserable. I want to keep using my cable, but it doesn't show up with my D700 in the import menu anymore.
I'm trying to import pictures show in raw from my D700 into Lr, but it keeps giving me an "unsupported or damaged" error. This is the second time this happens, the first time I just gave up and imported as .JPG. I've tried importing them from the camera, and from a flashdrive. Neither worked. Running Lightroom 5 on OSX 10.8.4.
I have just loaded the trial for LR4 on my MacBook Pro. When I try to open lightroom I get the error "an error occurred when attempting to change modules" Thereafter I cannot do anything in LR, when I close & reopen I get back to the installation screen asking me if I have a serial no or would like to run a trial.
I have deleted the app and reinstalled. But no difference.
The first time I opened LR it asked me if I wanted to upgrade my photoshop elements library or create a new one. I opted for create a new one.I installed the trial to see how well LR would work on my Mac as I have it on PC and would like to switch completely over to Mac....
I took D700 and D800e with me and planned on saving to portable HDs. I/3 of files could not be saved in LR4, they had ? on each 'slide' location. I bought Nikon NX2 and images came off CF cards fine and were saved to HD. But, when tried to load those files to LR4, the same thing happened... "?" all over again.
3-4 new Lexar Pro CFs and 2 different cameras... Whats up?
I am working on a assembly where a cable wrapped around a drum is animated to rotate with the drum, and there is a longer cable coming off of the rotating cable wrap, this longer piece goes down to another cable on a roller assembly. I have edited the assembly to work without the actual cable drum and without the roller assembly ( I wasnt allowed to share those models ) There are now two cylinders in place of the cable drum, a Grounded center to hold everything in place, a Rotating center which is animated so the wrap can rotate.
My problem is when the part named "Drum to Roller" is a lofted cable with angled ends to meet the "Drum wire wrap" at one end and it meets the "Radius cable ends" at the other end. I need the "Drum to roller" to stay constrained to the "radius cable ends" as well as the "drum wire wrap" ... and after being constrained still animate.
I have set up the animation and you will see that the "Drum wire wrap" is animated to keep the end vertical , the animation is set up to look like the "drum wire wrap' is un-raveling cable and the "drum to roller" is to be what un ravels.
I need to find a way so that the "drum to roller" translates down and over , staying constrained to the "drum wire wrap".. You will see that so far it does not.
I have attached two links below they include the two halfs of my assembly, place all the files in the same folder so you wont have to search for them manually.
I am interested in shooting with my D700 and lightroom 3 tethered. Is it possible for the image to be recored both on the card and on the tethered computer?
I have a Canon 5D Mark III and LR 4.3. I normally import photos using a CF card reader. However, I'm on vacation and only have the USB cable that connects the camera to my Macbook Pro. I've used this successfully in the past to import photos, but I'm now getting the following error:
I get this whether I select one or multiple photos (there are about 195 on the card right now).
Nikon D800 + LR4 import problem with dual card system:
I am transferring files to my computer (OSX, snow leopard) via USB cable. I am using dual card system with my camera: CF and SD. I am using the "backup" option which means that the content of both memory cards is identical. NEF + NEF with identical file names.
When the camera is connected to the computer and LR4 "import" is opened, LR4 does not show "D800 1" or "D800 2" -- it shows only "D800". This means that I cannot select a card which I would like to import the files from (like I can do with D700 or D3). And most of all, LR4 reacts inconsistently on "Don't import suspected duplicates". Usually, it wants to import all images on both cards -- this means that all files would be imported twice.
At the moment, in my D800, I have SD and CF with 3 identical NEF files on both cards. "Don't import suspected duplicates" is selected. In the import window I can see that LR4 wants to import 5 files: 0474+0474 (duplicates), 0475, 0476+0476 (duplicates). So, out from 6 images it recognizes that there is a one duplicate about to be imported, but those two others are not duplicates?
This document has been damaged by a disk error. The most likely causes of this error are: a defective disk drive, a defective disk drive cable, or incorrect peripheral cable termination. Some of the pixels in this document may be invalid.
I've been watching the Luminous Landscape video tutorials on Lightroom 3 and find them immensely useful. However, I've just watched the tutorial on printing and obviously haven't understood it. I've made changes to my print settings and profiles and now find I can't print at all from LR, all that happens is that the paper is fed through the printer, no printing. I'm using Windows 7 32 bit.
revert back to my non messed up print settings/profiles etc?
I just updated to Camera Raw8.3 and now when I'm in LR5.3 and attempt to edit an image in PS5, the image does not move from LR to PS. Should I just go back to a previous CR version?
This is the error message I get when I try to upload my raw files into LR4 from my Canon 5D MarkIII:
"The files are from a camera which is not recognized by the raw format support in LR. (7)
ex file # 5B9A0008.CR2
I recently upgraded from a 5D classic to the MarkIII. Jpeg's upload fine. I've googled, looked in the manual, searched for LR update and nothing has worked.
I am running Lightroom 4.4 with Camera 7.4 and Photoshop CS 6 will no longer let me edit directly from Lightroom. I am on an IMac running the most recent OS, OS X 10.8.3.
I shoot a lot of images with the background blown out (I shoot RAW of course; on my preview the background is flashing like crazy). I do this deliberately!
But LR4 apparently insists om saving me from myself. It automatically pulls back the blown-out areas so they become visible again. And no simple edit brings them back: I have to move whites to +80 to +100 and exposure up by half a stop as well. This is silly - I blow out my backgrounds very deliberately.
Is there a way to stop this behaviour, to turn off this show-stopper compulsory protection?
This image shows it: in the original the bg is 255-255-255 - full blinkies on the LCD. But in the RAW there is, alas, enough detail left ion the bits to bring it back:
I can no longer edit from LR 5 in photoshop CC. When I right click on the DNG image in my filmstrip, choose edit in> Photoshop CC nothing happens. If photoshop is closed, it will launch the program but does not open my image. I haven't changed any settings that I know of.
I have been successfully using Lightroom 4 for several weeks (and the Beta version before that), but today, after downloading the Nik Software Viveza plug in, when I tried to open LR, none of my images were there, and when I clicked on a module, I received an error message saying there was an error trying to change modules. Not sure what to do. I've uninstalled Viveza, but that did not fix the problem. I've rebooted many time, that also didn't solve this issue. I also tried opening a backup from yesterday, but that doesn't work either. I use a MacBook Pro and am running Lion.
I'm thinking I may want to uninstall LR 4 and reinstall..
Everything has worked perfectly until today. Yesterday evening, I received an update notice from Adobe for an update called Adobe CSXS INfrastructure CS6 and I agreed to let install. It installed.
That seems to be where the problem started. Now, when I send an image from LR to Photoshop, it does not open. The "Edit in" command isn't working. PS opens, but the image does not appear.
I just downloaded and reinstalled PS CS6. I then asked PS CS6 to update, which it did. When finished, there was an error saying that Adobe CSXS INfrastructure CS6 could not install. Error code: U44M1P7
The good news is that now it all works again! So, the problem lies in the Infrastructure update, which I will not allow to update again.
Windows 7, 64 bit Photoshop CS6, all updates Lightroom 4.1, all updates
Suddenly LR no longer makes a copy when I select "edit a copy", for example "edit a copy with LR adjustments", in PSCC.
Instead, it sends the MASTER to PSCC.
In the case where I have done no editing in PSCC and simply try to close the PS edit window, I always have to click "Don't Save", whereas before this GLITCH in LR, PSCC would simply close the image since I had done no editing.
Don't know if these two things are related but I have used both for many years and this is the first time I have seen this problem.
I get the "Photo upload failed, but no error string was returned from Facebook" and "Can’t update this collection. Photo upload failed, but no error string was returned from Facebook."
The plugin diagnostics report is as follows:
**** Error 1
This plug-in’s post-processing task did not finish successfully.
Photo upload failed, but no error string was returned from Facebook.
Now I have searched and searched for answers, which is normally it's a permission problem with facebook. Well it's on fb page, it's set to public and app has a permission of public.
I have removed the app from fb, removed authorisation from lightroom, deleted the prefs file, logged out of fb, tried to publish when all access to fb was logged out etc, etc and still no joy.
It doesn't matter if it's a new album, an existing album, my profile or a page!
Error Message is :- Unable to Export :- an internal error has occurred; WIN32 API error 2 (the system cannot find the file specified) when calling ShellexecuteExW fromAgWorkspace.shellexecute.
Photos are exported, but without the EXIF data?
I have tried uninstalling and reinstalling Lightroom. I have also tried Restoring Win 7 to an earlier build, but with no success.
The print resolution is no longer displayed making it difficult to decide if I need to modify the resolution prior to printing. Second, Lightroom 5 no longer generates a print preview. I select this option in my printer interface but sends the image directly to the printer without generating the preview. I did not have these issues with Lightroom 4 or earlier versions.
My edit information ( stack counts, ratings picks etc) is showing in grid view but is no longer showin in the filmstrip even though my settings (view options) are set to show details.
I run Lightroom 4.2 under Windows 7. All went well until this morning the development module showed a greyed out screen and LR stopped working. All other modules seem to work well. I tried a reinstallation but that doesn't work, nor does a return to 4.0 work.
The label for Library, i.e. the word 'Library', no longer shows in the line of module labels along the top panel of my Lightroom 4 window; all the others from Develop to Web are still there. I see they're called Module Picker Buttons (Menu - Lightroom - Identity Plate Setup..). I've just downloaded Lightroom version 4.4 but that hasn't triggered the reappearance of 'Library'. So I now have to use alt-cmd-1 to access the Library module. retrieve 'Library' for the top panel? Have I unknowingly made a keystroke that disabled it? I'm running Lightroom 4.4 on Mac OS 10.6.8.
In the early days of Lightroom there was a problem where if you cancelled a edit on a raw file in Photoshop without changing the file (maybe you opened in error) you still ended up with a tiff or PSD file that then needed manual deletion.
This was corrected in later versions. Now however the problem seems to have returned! Am I missing something or is it a screw up by Adobe?
