Lightroom 2015.3: Tethered shooting with Canon 5D crashing on MacOS 10.11 El Capitan

  • 2
  • Problem
  • Updated 2 years ago
  • Solved
  • (Edited)
Since I have El Capitan my Lightroom keeps crashing while Tethered shoot with Canon 5d mark 2 (and also occurs with Canon 5d).

I am using Lightroom CC 2015.3 (is latest version and reinstalled it last week).

During a day it crashes about 20 times. I went back to using Lightroom 5.7 but that didn't make a difference. So it looks like LR is not so much the problem.

I do notice crashing occurs more often when switching on 'show grid' in 'loupe view' in the library module.
It's definitely worse when using an 'image layout' as an overlay (view > loupe overlay > choose layout image). If that's is switched on you are lucky if you are able to take two photos without a crash.

Big problem with last crash today: the whole folder (used for the tethered shoot) was gone in LR. So I could not see which photos were the picks and all the other metadata was gone as well (color labels, titels, caption etc). In Finder all RAW-files were still there.

Is no fun while shooting for a client and also very unprofessional which I can't afford.
Photo of Harrie

Harrie

  • 9 Posts
  • 0 Reply Likes
  • very frustrated

Posted 2 years ago

  • 2
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13977 Posts
  • 1671 Reply Likes
What does the crash log say in it?

Make sure you submit all your crash logs along with your email address so our engineering team can investigate: https://helpx.adobe.com/photoshop/kb/...
Photo of Harrie

Harrie

  • 9 Posts
  • 0 Reply Likes
I've been sending in many many crash reports. Am I the only one with this problem?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1385 Posts
  • 413 Reply Likes
I've found no crash reports tied to your email. When you submit the crash log to Adobe, could you make sure that you add your email address to the report so that we know it is from you?
Photo of Harrie

Harrie

  • 9 Posts
  • 0 Reply Likes
I'm going to use Capture One Pro in order to tethered shooting. Still not happy with El Capitan 10.11.2 in combination with LR CC. Capture One, I don't like the interface very much but at least it just works flawlessly!
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
i am having the same problem and reported it in a different thread. also have sent in perhaps 50-100 crash reports at this point and adobe could not find ay record of them under my account. i then copied and pasted one of the reports into the thread but got no response or action from adobe following up.

i have purchased a new camera (5Ds) and a new laptop (mac book pro), i have tried different cables and various other things but nothing seems to solve the problem. the immediate precursor to a crash for me happens not on capture, but when i hit either the left or right arrows in grid mode or in preview mode to go to a different image, or sometimes when changing between modules (eg library to develop).

adobe, can you please look in to this and allocate a few more resources to fixing it? this is really unworkable. i like harrie, i have tried capture one which works just fine, but it is not a very compatible platform for a primarily dng based workflow.

please help!!!!!
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
just to follow up... if you want to add yourself to the "me too" count on my thread please do so at:
https://feedback.photoshop.com/photoshop_family/topics/lightroom-crashes-constantly-when-tethered-to...
Photo of Yuhong

Yuhong, Employee

  • 94 Posts
  • 5 Reply Likes
Hi, John, I'd glad to help you with this problem. Would you kindly copy the crash information in the Crash Report before sending it, and attach those information in this forum so that I can take a look? 
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
please remind me where i locate the crash reports? when the crash actually occurs, i always click the "send crash report" option but i am not always on a wifi network.
Photo of Yuhong

Yuhong, Employee

  • 94 Posts
  • 5 Reply Likes
Can you make a screen shot when you observe the Crash Report dialog?  And please kindly share the screen shot to me. Thank you!
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
sure, no problem. i can do this tomorrow. in the meantime, if you can remind me where the crash logs are stored on the computer, i would be happy to send you those. thanks!
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
awesome! thanks so much for looking into it! hope they prove useful in diagnosing the problem... 
Photo of Yuhong

Yuhong, Employee

  • 94 Posts
  • 5 Reply Likes
BTW, I observed that you said that " the immediate precursor to a crash for me happens not on capture, but when i hit either the left or right arrows in grid mode or in preview mode to go to a different image, or sometimes when changing between modules (eg library to develop).". Does that mean Lightroom is able to recoginize the Canon Camera and you can do the capture without any problem?  Does the crash occur only when you preview the images?
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
yes, that seems to be the case. lightroom sees both of the cameras that i use just fine (Canon 5DM3, and Canon 5DS). i can't remember it ever crashing during capture... meaning that i can take a picture, it will load up (typically i am in preview mode ("e" keyboard shortcut), but sometimes in grid mode while making captures), and then i can keep repeating this indefinitely without any problems. if i do nothing but click the shutter, it seems to be stable. sometimes i will even take a burst of several images and they load up successively without any problem (just a slight lag depending on how many exposures there are). it's only when i try to go back to the previous capture, or sometimes when i hit "r" to crop an image, or "d" to develop, or "g" to go back into grid mode from preview mode that the crash happens... and it is intermittent. i would say that the crash happens roughly 25% of the time. so sometimes i am able to switch between captures and modes just fine. and sometimes it will crash the very first time i attempt any of the actions that produce a crash, and sometimes i am able to navigate between a couple images or modes before it crashes. i do notice that after i relaunch, and before i take any more captures, i am always able to navigate with the arrow keys or switch between modes without difficulty. but as soon as i start to make new captures, then i am susceptible to crashes. finally, i think there is a pattern where it tends to happen less frequently if there is no camera tethered and i am simply using lightroom to work on images that already exist... but i am not absolutely sure about this or how much of a difference it makes because i am almost always tethered.

hope that is helpful information... please let me know if you have any other questions.

thanks!!!
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
hi yuhong, i just wanted to follow up and see if you had learned anything from the crash reports i sent last week. please let me know if you have any more questions or if there is anything i can do to help diagnose the problem. i look forward to hearing back from you... thanks!
Photo of Yuhong

Yuhong, Employee

  • 94 Posts
  • 5 Reply Likes
Hi John. Sorry for my late reply. I have tried a bunch of ways to reproduce the crash problem, for instance, doing some bust shootings and then hit ‘r’ to crop the image, or ‘d’ to develop, but I have not had any good progress. 
In terms of the crash report, the crash occurs when Lightroom sending a message "
kEdsCameraStatusCommand_UILock" to Canon SDK. I am not sure if it’s a problem of the current Canon 32 bit SDK. The good news is Canon company is going to ship the new 64 bit SDK soon, and this SDK should support the Mac OS X El Capitan much better. Lightroom will pick up the new SDK as well. 

I have opened a bug to track this problem.  Would you please wait for the latest SDK upgrade? Thanks a lot!
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
hi rick,

thank you for the notification about the release of the latest version. i appreciate the sentiment. however, the overall impression that your message gives me is one of frustration and disappointment. i believe this is the third time over the last year or so that i have received a similar notice about the release of a new upgrade and adobe's affirmation that the problem "should now be fixed". in each instance, there was no improvement whatsoever to the problem. and since adobe has constantly maintained that they have not been able to reproduce the problem or identify the cause from the numerous crash reports that i and others have submitted, it not only seems unlikely that they have fixed something that can't even identify, it moreover undermines faith in adobe, both in their tech team and their customer support. the messages don't seem like personalized responses. it does;t seem like adobe is on top of the problem or working to fix it. what these messages appear to be, most likely, are automated responses that go out to every thread each time a new release is issued regardless of what the problem is. what i would actually appreciate is a real personalized response, or some sort of reassurance that someone (anyone!) is working on it or has actually identified the problem and taken steps to remedy the issue. it has persisted now across multiple version of iOS as well as numerous versions of CC, and even across different computer and camera hardware. clearly the problem is lightroom. PLEASE. PLEASE. PLEASE, devote the resources necessary to fix this problem. i would even be willing to demonstrate the problem in person to adobe technical personnel to help them fix their broken software. i would think they would welcome this opportunity. you are welcome to come to my studio for a demonstration, or i would be happy to meet with adobe somewhere more convenient for them. please let me know if adobe cares enough to want to try and fix this problem or support their customers of which i have been one for over 25 years. i will not even charge you for my time spent working to improve your products. i look forward to hearing back from you.

regards,

john h.

ps this thread is marked as having been "solved" when it is decidedly not. how do i change the status? please advise. thanks.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13932 Posts
  • 1653 Reply Likes
Hi John, I understand your frustration. In the Creative Cloud app, if you click on the gear and choose "Check for App updates" it should update the list of updates available.

We've integrated a new SDK from Canon for 6.6 which fixes a number of issues with Canon cameras. If you're still encountering a problem I will ask a QE to work directly with you.
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
victoria, thanks for your comments. but this thread is about my problem. and i did respond, and it is still marked as "solved". i am guessing adobe and not the author of the thread has control over this status?

to be fair, i received a reply from rikk on a parallel thread that the notice was sent out in error (and it does seem to have disappeared from the history?).

i am eager to see if the problem has been fixed...

jeff, thank you for the tip. i don't know if it is because i am on a mac, but when i click the gear next to lightroom, the only option i am offered is to "uninstall". any other thoughts?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3791 Posts
  • 1252 Reply Likes
Yes, Adobe controls the solved status. You haven't tried it yet, so they're not going to unmark it as solved until you've confirmed you still have a problem. Here's a direct link to the patch if you want to try it now: Mac
Photo of John Horner

John Horner

  • 38 Posts
  • 1 Reply Like
thanks for the link. with regard to the status, it never should have been marked as solved, because it never was solved so they should change it pending confirmation. it is not reasonable for adobe to mark something as solved just because they replied to a post or hope that it "should" be solved. it makes no sense to mark an issue as solved unless it actually is... no?
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3791 Posts
  • 1252 Reply Likes
Consider it "assumed solved".  You'd be surprised how many people never come back to confirm that it's definitely solved for them.