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

Imaging Preview didn't update during an Imaging Session


dkkdwhite

Question

Software version  BYE 3.1.17 Prem. Ed. 1502

Camera Canon T6i

I've been using BYE for several months and like the simple and intuitive interface.  I was imaging at a dark site last night and was 128 frames in (lights and darks, two filters) and was attempting to recenter the target in the Imaging window.  After making directional adjustments with the mount I would take snapshots and check for movement by comparing to the thumbnail of the previous preview image.  The apparent movement abruptly stopped, despite hearing the mount motors as I made adjustments.  I toggled back and forth between imaging and focusing modes to see if there was a software hang up, but still no apparent movement of the target in the images.  As I was packing up to go I noticed the directory had frames after the image I remember being hung up and these frames showed the target movement I was expecting.

Apparently application simply stop downloading the preview images to the Imaging window even though they were being saving in my directory.

Any idea what was going on?

 

Greg

Link to comment
Share on other sites

11 answers to this question

Recommended Posts

  • 0
On 6/13/2019 at 2:37 PM, dkkdwhite said:

Software version  BYE 3.1.17 Prem. Ed. 1502

Apparently application simply stop downloading the preview images to the Imaging window even though they were being saving in my directory.

I see the "preview hang" frequently with BYE 3.1.6 (classic, not premium) and Canon 6D.  I came to the support forum hoping to find an answer.  The problem makes it very difficult to use BYE.  The log file (top left of the screen) shows the capture is complete, and the file is transferred to my laptop fine.  "Frame &f Focus" works fine for both liveview and captures.  I use Canon tools (DPP) to check the framing, but what a pain!

For what it's worth, version 2.0 does not have the bug.  But, 2.x doesn't support my latest camera.

Let me know if there is a fix.

Doug  

Link to comment
Share on other sites

  • 0

Hi Doug, send me the log file and I'll take a look.

In the meantime go to settings -> advance settings and check processor affinity, restart the app and try again.  Let me know if the issue persist with this setting enabled.

Regards, 

 

 

Link to comment
Share on other sites

  • 0
31 minutes ago, admin said:

Hi Doug, send me the log file and I'll take a look.

In the meantime go to settings -> advance settings and check processor affinity, restart the app and try again.  Let me know if the issue persist with this setting enabled.

The logfile from last night was just sent via email.  Image Preview was failing most of the evening, so the problem should be prevalent in the file.

I will also try BYE with processor affinity enabled.  (the option was unchecked previously)

Doug

Link to comment
Share on other sites

  • 0
13 minutes ago, dugpatrick said:

The logfile from last night was just sent via email.  Image Preview was failing most of the evening, so the problem should be prevalent in the file.

I will also try BYE with processor affinity enabled.  (the option was unchecked previously)

Doug

I just tested (10) Previews with Processor Affinity checked, and Preview was working fine.  Perhaps that is the answer.  I won't know for sure without more testing.

Doug

Link to comment
Share on other sites

  • 0
1 hour ago, dugpatrick said:

I just tested (10) Previews with Processor Affinity checked, and Preview was working fine.  Perhaps that is the answer.  I won't know for sure without more testing.

Doug

That could be it.  That is the reason for this feature.  Deep down though this is probably related to a cross-thread issue/bug... and processor affinity solves this by allowing BYE to only use a single CPU core.  With processor affinity enabled, you might want to enable the Background Worker as well (but it's optional).  This will push some long running process into a secondary process which will run on a separate CPU core, thus having 2 cores being used.

Regards,

Link to comment
Share on other sites

  • 0
3 hours ago, dugpatrick said:

The logfile from last night was just sent via email.  Image Preview was failing most of the evening, so the problem should be prevalent in the file.

I will also try BYE with processor affinity enabled.  (the option was unchecked previously)

Doug

I got the email but there was no log file attached.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • 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