Imaging Preview didn't update during an Imaging Session

[dkkdwhite 0]

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

[dugpatrick 0]

On 8/10/2019 at 1:06 PM, admin said:

...  With processor affinity enabled, ...

After setting this option all has been working perfectly.  Thanks!

Doug

[admin 358]

This is very odd.  Looks like the display event was lost or not processed.

If it happens again let me know. 

Regards,

[s3igell 264]

This is something which should have recorded hints to the Log, right??

Meaning that How to submit Log Files for Support Issues might be of help...

[dugpatrick 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  

[admin 358]

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, 

 

 

[dugpatrick 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

[dugpatrick 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

[admin 358]

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,

[admin 358]

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.

[dugpatrick 0]

1 hour ago, admin said:

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

Maybe because of the file size (1.9 MB), which could be over some limit.  I tried again with zip compression, and the file is much smaller.

Doug

[admin 358]

9 hours ago, dugpatrick said:

After setting this option all has been working perfectly.  Thanks!

Doug

Thanks for reporting back Doug!