Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

BYE Crash when camera disconnects


Grumman

Question

Hello,

 

I have noticed that BYE 3.1 is crashing (white screen and unresponsive) when the camera physically disconnects (ie. low battery, camera turned off from button or cable gets disconnected) while it is still connected on BYE.

It seems that BYE is not handling the camera disconnection gracefully...

I have been down this road quite a few times as I have BYE running and then when I finish my photography session, I shutdown the camera without disconnecting it from BYE as I still want to review photos etc through BYE but at that point it is too late as BYE has already crashed...

 It would be nice if the camera disconnects for BYE without crushing it and just run in a Preview mode as it is when it starts without a camera connected...

Link to comment
Share on other sites

  • Answers 4
  • Created
  • Last Reply

4 answers to this question

Recommended Posts

I got the logfile, the event is fired... but then nothing.  I suspect the camera is starved of power before the Canon SDK is able to properly terminate the session.  Looks like BYE is just in for the ride in this case.  I'll dig into it a little bit but it does look like I won't be able to do much since the camera has no more power before the event is properly processed.

 

Link to comment
Share on other sites

Well, in all my test BYE will disconnect gracefully.

However, physically disconnecting the camera from the computer BEFORE disconnecting from the application is a pretty drastic connection violation (if this can even be said like this).  When the camera disconnects the Canon SDK fires an event and BYE listens to the event and handles it gracefully.  If your crashes I would think it is caused by the event either not being fire by your camera, therefore BYE can't fail gracefully because the Canon SDK itself has gone into a fault state.

Send me the log file and I can look if the event is fired.

 

 

Link to comment
Share on other sites

1 hour ago, admin said:

Well, in all my test BYE will disconnect gracefully.

However, physically disconnecting the camera from the computer BEFORE disconnecting from the application is a pretty drastic connection violation (if this can even be said like this).  When the camera disconnects the Canon SDK fires an event and BYE listens to the event and handles it gracefully.  If your crashes I would think it is caused by the event either not being fire by your camera, therefore BYE can't fail gracefully because the Canon SDK itself has gone into a fault state.

Send me the log file and I can look if the event is fired.

 

 

 

Thank you!

I have sent the log as requested!

Link to comment
Share on other sites

51 minutes ago, admin said:

I got the logfile, the event is fired... but then nothing.  I suspect the camera is starved of power before the Canon SDK is able to properly terminate the session.  Looks like BYE is just in for the ride in the case.  I dig into it a little bit but it does look like I won't be able to do much since the camera as no more power before the event is properly processed.

 

Thank you very much for the swift reply!!

Yes, this happens when I turned off the camera from the switch and then everything stops! ;)

I totally understand now why this happens...

I need to change my workflow and make sure I disconnect the camera from BYE before shutting her down.

Thank you!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use