Slow Response

[jforkner]

For some reason, my BYE application has become virtually non-responsive.  It loads, connects to the camera (Canon 6D), and seems to function; but the response is so sloooow, it's become impossible to use.  I discovered the problem while trying to record the recent eclipse and had to abandon the program and shoot manually.

 

I'm running Premium Edition 3.0.3, built 2013-12-15 on a Windows XP laptop.  I should mention I also have installed the EOS Utility program.

 

The problem seems most noticeable in the Frame & Focus module.  The image in the Frame/Focus Center window does not react in anything close to real-time when making a focus adjustment on the camera.  While the actual field of view changes relatively quickly with any camera movement (albeit a second or two delay), any focus change takes 15-20 seconds to register in the Zoom Box Center window.  This makes it a real pain to establish a proper focus during a session.

 

I recognize this could be, in part, due to my somewhat anemic computer; but I don't recall this problem last time I used the program, and no significant changes have been made to the computer.  Any suggestions of possible causes will be greatly appreciated.

 

Thanks for any help offered.

 

Jack

[jforkner]

YOU WERE RIGHT, GUYLAIN!  The problem was the AVG software.  After uninstalling it, everything returned to normal as far as BYE is concerned.  Now to find an antivirus program to work with XP.

 

Thank you so much for your help & insight.

 

Jack

[admin]

YOU WERE RIGHT, GUYLAIN!  The problem was the AVG software.  After uninstalling it, everything returned to normal as far as BYE is concerned.  Now to find an antivirus program to work with XP.

 

Thank you so much for your help & insight.

 

Jack

 

This is the 4th solid confirmation in 3 months where AVG was found to be the culprit of system performance issue.

 

I suspect AVG has an in-memory process that does not play nice with memory stream images... which is what live view frames are when being pulled from the camera.  This is just a hunch though.

 

Guylain

[AaronSmall]

Guys,

 

I have used both Avast and Avira anti-virus on my XP machine and have had no problems with BYE.  I still use XP to work with my webcam to set into RAW mode and the mod software (by Martin Burri) doesn't work on newer OSs.

 

 

[admin]

Live view is very demanding on older computers... and if you had just done a planetary recording the video encoding into and AVI will have an impact because this it is CPU intensive.

 

You can increase the live view "throttle" value in Settings.  This will slow down live view.  Increase the value to 100 milliseconds and see what happens.

 

Guylain

[jforkner]

I'll give the Settings-thing a try.

 

FWIW, I had not done any recording prior to attempting to set focus.  During my attempt a focusing on the moon for the eclipse, the image in live view did not change a bit while my telescope's focuser moved the camera limit-to-limit.  I ended up just using the LCD on the camera.

 

Thanks for the quick response.

 

Jack

[admin]

I'll give the Settings-thing a try.

 

FWIW, I had not done any recording prior to attempting to set focus.  During my attempt a focusing on the moon for the eclipse, the image in live view did not change a bit while my telescope's focuser moved the camera limit-to-limit.  I ended up just using the LCD on the camera.

 

Thanks for the quick response.

 

Jack

 

Then it looks like your PC can not handle the demand of live view as a whole.  The throttle setting may be your only chance.

 

Also, it would be good to monitor your CPU and MEMORY usage from other programs while your are doing live view.  I could be that other programs are requesting to much CPU at the same time and you are creating a computer resource contention issue as a result.

 

Guylain

[dts350z]

I've had somewhat similar issues. I have a brand new Dell ultrabook with SSD, i7-4600U 8 GB of RAM. Windows 7 64 bit.

 

T3i/600D.

 

Planetary is functional but clicking on buttons takes time or doesn't work until clicked multiple times (changing modes, turning 5x on and off, etc.).

 

In image mode, I found my preview images didn't always display. 

 

I'm not running any other programs yet, but will be running PHD2.

 

This is the demo program. I'm ready to purchase pro version if we can resolve/understand the slowness.

 

 

 

[admin]

I've had somewhat similar issues. I have a brand new Dell ultrabook with SSD, i7-4600U 8 GB of RAM. Windows 7 64 bit.

 

T3i/600D.

 

Planetary is functional but clicking on buttons takes time or doesn't work until clicked multiple times (changing modes, turning 5x on and off, etc.).

 

In image mode, I found my preview images didn't always display. 

 

I'm not running any other programs yet, but will be running PHD2.

 

This is the demo program. I'm ready to purchase pro version if we can resolve/understand the slowness.

 

 

 

 

Do you have any ASCOM devices connected?

 

Do you have another cable to try?

 

Is the usb cable connected directly in the computer? 

 

Is it a USB 1.1 / 2.0 / 3.0 port on the computer?

 

What is the CPU and memory usage in task manager when you experience slowness?

 

This has not change recently and 3.0.3 has been around for months so we should be able to find the root cause by eliminating one thing at a time.

 

Guylain

 

 

 

[dts350z]

First let me apologize to Guylain for the thread jack but it seemed appropriate. Maybe he can gain some advantage as well.

 

Do you have any ASCOM devices connected?

 

No

Do you have another cable to try?

 

I'll look

Is the usb cable connected directly in the computer?  

 

Through a usb extension, not a hub or anything

Is it a USB 1.1 / 2.0 / 3.0 port on the computer?

 

3.0

 

...

 

I'll try a different cable , without the extension, tonight. I'll take task manager readings as well.

 

Thanks for the quick response.

 

FYI I took 92 GB of planetary data during the eclipse this week, and other than filling up my laptop SSD towards the end (no, the slowness was there before the drive filled up) all the AVIs seem intact.

 

During the full eclipse I was not able to get anything out of planetary or anything live (not enough light even at 6400 bulb) so switched to images. Those also came through fine. The only issue there (other than not having a live picture to help with manual scope alignment) was that the preview images did not always show on the BYEOS display as I mentioned above.

 

 

[admin]

First let me apologize to Guylain for the thread jack but it seemed appropriate. Maybe he can gain some advantage as well.

 

Do you have any ASCOM devices connected?

 

No

Do you have another cable to try?

 

I'll look

Is the usb cable connected directly in the computer?  

 

Through a usb extension, not a hub or anything

Is it a USB 1.1 / 2.0 / 3.0 port on the computer?

 

3.0

 

...

 

I'll try a different cable , without the extension, tonight. I'll take task manager readings as well.

 

Thanks for the quick response.

 

FYI I took 92 GB of planetary data during the eclipse this week, and other than filling up my laptop SSD towards the end (no, the slowness was there before the drive filled up) all the AVIs seem intact.

 

During the full eclipse I was not able to get anything out of planetary or anything live (not enough light even at 6400 bulb) so switched to images. Those also came through fine. The only issue there (other than not having a live picture to help with manual scope alignment) was that the preview images did not always show on the BYEOS display as I mentioned above.

 

 

 

Remove the extension and plug the camera directly into the computer.  And see it that works better.  You need to have a little as possible between the computer and camera.  We need to eliminate unnecessary hardware to find the culprit.

 

Guylain

[admin]

Oh, and if you have another computer try it.  We also need to eliminate your current computer as the source just to make sure.

 

Guylain

[jforkner]

Guylain,

 

In my case, I'm using an 8-year-old Windows XP laptop with a Pentium 1.73GHz processor, 2GB RAM, and an ATI Mobility Radeon X300 video card (screen res 1680 x 1050).  The computer has several USB 2.0 connectors.  Camera is Canon 6D with 24-105L lens, connected via 6-foot USB cable.  Setup inside house for test.

 

Here's my scenario:

    •    Computer-on, NO applications running:  CPU = 0%, Memory avail = 1.44GB

    •    Start BYE:  CPU = 100%, Memory avail = 1.34GB

    •    Connect camera:  CPU = 100%, Memory avail = 1.34GB

    •    Select Frame/Focus:  CPU = 100%, Memory avail = 1.27GB

    •    Adjust focus (Live View very slow to react):  CPU = 100%, Memory avail = 1.27GB

    •    Disconnect camera:  CPU = 100%, Memory avail = 1.34GB

    •    Close BYE:  CPU = 0%, Memory avail = 1.43GB

 

I'm going to assume with the CPU running at 100% as long as BYE is running, that you'll tell me I need a more powerful computer.  I note the System Requirements on your BYE website don't mention a CPU requirement, only an OS and screen resolution one.  What do you recommend as a good, minimum hardware configuration?

 

FWIW, I have no other computer to try.  My other machine is an iMac without Windows capability.  Besides I need a portable system to use with my telescope.

 

Jack

[admin]

Guylain,

 

In my case, I'm using an 8-year-old Windows XP laptop with a Pentium 1.73GHz processor, 2GB RAM, and an ATI Mobility Radeon X300 video card (screen res 1680 x 1050).  The computer has several USB 2.0 connectors.  Camera is Canon 6D with 24-105L lens, connected via 6-foot USB cable.  Setup inside house for test.

 

Here's my scenario:

    •    Computer-on, NO applications running:  CPU = 0%, Memory avail = 1.44GB

    •    Start BYE:  CPU = 100%, Memory avail = 1.34GB

    •    Connect camera:  CPU = 100%, Memory avail = 1.34GB

    •    Select Frame/Focus:  CPU = 100%, Memory avail = 1.27GB

    •    Adjust focus (Live View very slow to react):  CPU = 100%, Memory avail = 1.27GB

    •    Disconnect camera:  CPU = 100%, Memory avail = 1.34GB

    •    Close BYE:  CPU = 0%, Memory avail = 1.43GB

 

I'm going to assume with the CPU running at 100% as long as BYE is running, that you'll tell me I need a more powerful computer.  I note the System Requirements on your BYE website don't mention a CPU requirement, only an OS and screen resolution one.  What do you recommend as a good, minimum hardware configuration?

 

FWIW, I have no other computer to try.  My other machine is an iMac without Windows capability.  Besides I need a portable system to use with my telescope.

 

Jack

 

Jack,

 

Which anti-virus softwre are you using?  I'm willing to bet that is the cause.

 

Turn if off for a minute or 2 and try BYE.  It is still sluggish?

 

Guylain

 

 

 

[jforkner]

Jack,

 

Which anti-virus softwre are you using?  I'm willing to bet that is the cause.

 

Turn if off for a minute or 2 and try BYE.  It is still sluggish?

 

Guylain

 

 

 

Interesting you should mention that---I just changed virus programs due to WinXP support going away.  I'd been running Microsoft Security Essentials, and just changed to AVG Antivirus.

 

Anyway, just did a test with the AVG software turned off and it seemed to make a slight change.  The CPU utilization remained at 100% while BYE was running, but the reaction in Live View window to react to a focus change was only a couple of seconds, and another couple for the effect to appear in the smaller zoom window.  This, with the throttle set at 100ms.

 

Then I turned Live View on in the camera (it had not been on prior) and the BYE Live View was a little more responsive.  And if I zoomed in on the camera's live view (5X or 10X), a corresponding zoom occurred in the BYE Live View window---This was really helpful, I found.

 

Then I turned the AVG software back on, and ran the same tests.  My conclusion is that even with the anti-virus software on, the response is tolerable when the camera's live view is turned on.

 

So...where are we?  I think the best test is with the camera connected to the telescope trying to focus on a star.  Turning the camera's live view on seemed to help a fair amount in my inside-the-house-test, so I'll try that when connected to the telescope.  I do know my laptop is tired and underpowered for what I'm trying to do.  In fact, I suspect the small amount of video memory (64MB) is contributing to the problem, as well.

 

I'll try to get in some telescope tests in the next couple days---we have cloudy weather forecast for a bit.  And I'll report back my findings.  I'm also going to start shopping for a new laptop.  Any recommended minimum requirements?

 

Thanks again for all your help and prompt responses.

 

Jack

[admin]

Jack,

 

Which anti-virus softwre are you using?  I'm willing to bet that is the cause.

 

Turn if off for a minute or 2 and try BYE.  It is still sluggish?

 

Guylain

 

 

 

Interesting you should mention that---I just changed virus programs due to WinXP support going away.  I'd been running Microsoft Security Essentials, and just changed to AVG Antivirus.

 

Anyway, just did a test with the AVG software turned off and it seemed to make a slight change.  The CPU utilization remained at 100% while BYE was running, but the reaction in Live View window to react to a focus change was only a couple of seconds, and another couple for the effect to appear in the smaller zoom window.  This, with the throttle set at 100ms.

 

Then I turned Live View on in the camera (it had not been on prior) and the BYE Live View was a little more responsive.  And if I zoomed in on the camera's live view (5X or 10X), a corresponding zoom occurred in the BYE Live View window---This was really helpful, I found.

 

Then I turned the AVG software back on, and ran the same tests.  My conclusion is that even with the anti-virus software on, the response is tolerable when the camera's live view is turned on.

 

So...where are we?  I think the best test is with the camera connected to the telescope trying to focus on a star.  Turning the camera's live view on seemed to help a fair amount in my inside-the-house-test, so I'll try that when connected to the telescope.  I do know my laptop is tired and underpowered for what I'm trying to do.  In fact, I suspect the small amount of video memory (64MB) is contributing to the problem, as well.

 

I'll try to get in some telescope tests in the next couple days---we have cloudy weather forecast for a bit.  And I'll report back my findings.  I'm also going to start shopping for a new laptop.  Any recommended minimum requirements?

 

Thanks again for all your help and prompt responses.

 

Jack

 

I had 3 report in the past 8 weeks where AVG was the issue.

 

If you like the Microsoft Security Essentials it is still free.  This is what I've been using exclusively for the past 3 years.

 

They call it Windows Defender now.

 

Guylain

 

 

 

 

 

 

 

[jforkner]

Guylain,

 

I, too, had been using Security Essentials for some time; but stopped because according to Microsoft:

 

"Microsoft has also stopped providing Microsoft Security Essentials for download on Windows XP. (If you already have Microsoft Security Essentials installed, you will continue to receive antimalware signature updates for a limited time, but this does not mean that your PC is secure because Microsoft is no longer providing security updates to help protect your PC.)"

 

But I will look for an alternative to AVG.

 

Couple of questions:

1. Do you have a recommended minimum hardware configuration for running BYE?
2. Will BYE run on Windows 8.1?

Thanks.

 

Jack

 

 

 

[admin]

Guylain,

 

I, too, had been using Security Essentials for some time; but stopped because according to Microsoft:

 

"Microsoft has also stopped providing Microsoft Security Essentials for download on Windows XP. (If you already have Microsoft Security Essentials installed, you will continue to receive antimalware signature updates for a limited time, but this does not mean that your PC is secure because Microsoft is no longer providing security updates to help protect your PC.)"

 

But I will look for an alternative to AVG.

 

Couple of questions:

1. Do you have a recommended minimum hardware configuration for running BYE?
2. Will BYE run on Windows 8.1?

Thanks.

 

Jack

 

 

 

The issue is is XP, not Windows Defender!!!

 

Microsoft did not and will not stop proving security update for Vista/W7/W8.  It is their solution for anti-virus and I assure you it is there to stay.

 

Minimum config is on the web site under System Requirement, click [ system requirement ] at the bottom of the page.

http://www.backyardeos.com/product_backyardeos.aspx

 

 

BYE will run on w8 just fine, my entire development environment is W8.1

 

Guylain

 

 

 

 

 

[jforkner]

Guylain,

 

According to my research Windows Defender only removes spyware on a WinXp machine; Security Essentials was used for viruses (http://blogs.msdn.com/b/securitytipstalk/archive/2013/11/14/windows-defender-and-microsoft-security-essentials-which-one-do-i-need.aspx).

 

My machine is running WinXP and is not capable of running Win7 or 8.  So I needed to find something other than Security Essentials for it.

 

I had previously looked at the system requirements on the website, and was really interested on recommendations for CPU & memory recommendations, which the site didn't mention---I guess I should have been specific.

 

Thanks again.

 

Jack

[admin]

Hi Jack,

 

BYE will run on single CPU computer with 1GB RAM... but it will be slow.

 

The minimum acceptable as I see it:

Dual core CPU

2 GB RAM

USB 2 port

 

Oh... and Windows Defender is a full blown anti-virus software.

http://windows.microsoft.com/en-us/windows-8/how-find-remove-virus#1TC=t1

 

Regards,

 

Guylain

 

 

[jforkner]

 

Oh... and Windows Defender is a full blown anti-virus software.

http://windows.microsoft.com/en-us/windows-8/how-find-remove-virus#1TC=t1

 

 

Oh, I know.  Just not on WinXP.

 

And thanks for the hardware info,

 

Jack

[admin]

Oh, I know.  Just not on WinXP.

 

And thanks for the hardware info,

 

Jack

 

Oh, yep that is correct <_>

 

Guylain