Very slow Liveview

[Jerry_K]

Last night I was experimenting with wide angle photography using moded Canon 450D and 18-55mm kit lens. I have tried to adjust focus on the Moon but when I tried to slew to center of Moon the image in Frame & Focus just sat there for about 5 seconds and than moved quickly off the screen. I was using Candidate 03. Before the image moved at the same time as the mount. What settings have to be adjusted? I know it is not computer or camera, it worked great before with telescope prime focus.

Jerry

[astroman133]

Jerry,

 

In order to confirm that your issue is being caused by RC03, or not.  I would suggest re-creating the issue with RC03 and then immediately shutting down RC03 and trying 3.0.3 to see if it suffers the same slowness.

 

I do not believe that there are any settings for for directly controlling the LiveView frame rate.  It is limited by the camera, the USB connection, and BYE's processing.  Testing with both versions will rule out the camera and USB, if the problem does not occur with the older version.

[Jerry_K]

Rick, I can't duplicate the problem with either version, both now work like they are supposed to. So, I don't know why it behaved like that, I just couldn't slew onto any object without Liveview lagging way behind and in process was useless. I had to switch to DSLR LCD screen by disconnecting USB cable and than re-connect for shooting program.

Beats me what happened, Jerry

 

Jerry,

 

In order to confirm that your issue is being caused by RC03, or not.  I would suggest re-creating the issue with RC03 and then immediately shutting down RC03 and trying 3.0.3 to see if it suffers the same slowness.

 

I do not believe that there are any settings for for directly controlling the LiveView frame rate.  It is limited by the camera, the USB connection, and BYE's processing.  Testing with both versions will rule out the camera and USB, if the problem does not occur with the older version.

[admin]

Rick, I can't duplicate the problem with either version, both now work like they are supposed to. So, I don't know why it behaved like that, I just couldn't slew onto any object without Liveview lagging way behind and in process was useless. I had to switch to DSLR LCD screen by disconnecting USB cable and than re-connect for shooting program.

Beats me what happened, Jerry

 

Jerry,

 

In order to confirm that your issue is being caused by RC03, or not.  I would suggest re-creating the issue with RC03 and then immediately shutting down RC03 and trying 3.0.3 to see if it suffers the same slowness.

 

I do not believe that there are any settings for for directly controlling the LiveView frame rate.  It is limited by the camera, the USB connection, and BYE's processing.  Testing with both versions will rule out the camera and USB, if the problem does not occur with the older version.

 

You can -slow- down the live view frame rate in Settings by increasing the Live view Throttle parameter to 100 ms (default is 50ms) and see if that makes a difference.

 

BUT, from what I can read in your description this seems simply like the classic -too-many-things-the UI-thread-has-to-perform and as a result some UI tasks (Windows or .net) simply took a bit longer to get to them.  Just a hunch.

 

Regards,

 

 

[Jerry_K]

Rick, I can't duplicate the problem with either version, both now work like they are supposed to. So, I don't know why it behaved like that, I just couldn't slew onto any object without Liveview lagging way behind and in process was useless. I had to switch to DSLR LCD screen by disconnecting USB cable and than re-connect for shooting program.

Beats me what happened, Jerry

 

Jerry,

 

In order to confirm that your issue is being caused by RC03, or not.  I would suggest re-creating the issue with RC03 and then immediately shutting down RC03 and trying 3.0.3 to see if it suffers the same slowness.

 

I do not believe that there are any settings for for directly controlling the LiveView frame rate.  It is limited by the camera, the USB connection, and BYE's processing.  Testing with both versions will rule out the camera and USB, if the problem does not occur with the older version.

 

You can -slow- down the live view frame rate in Settings be increasing the Live view Throttle parameter to 100 ms (default is 50ms) and see if that makes a difference.

 

BUT, from what I can read in your description this seems simply like the classic -too-many-things-the UI-thread-has-to-perform and as a result some UI tasks (Windows or .net) simple took a bit longer to get to them.  Just a hunch.

 

Regards,

 

Guylain, I think that you are right. The HD light was going nuts but there were no images being downloaded. I just hate these new OS that run crapload of updates and installations that has nothing to do with task at hand. I have to find a way to stop all un-necessary services being run during imaging session.

Jerry

[s3igell]

I just hate these new OS that run crapload of updates and installations that has nothing to do with task at hand. I have to find a way to stop all un-necessary services being run during imaging session.

Jerry

 

First tool:  TaskManager is your friend.  With the Process and Performance Tabs, you can identify how hard your Laptop is working and on which Processes.  If you recognize the various Processes, you can Google to determine whether they are Safe-to-Abort.  You can also identify whether critical Memory Resources or Disk I/O is bogging down your System.

 

Second Tool:  WinUpdate Settings in Control Panel.  Open the Windows Update Control Panel and along the Left Column of Tasks use "Change Settings" in order to select "Check for Updates but let me choose whether to Download and Instll them."  Now, you are in control of the Windows Updates, but you won't be left open to a serious Bug or Virus.

[Jerry_K]

I just hate these new OS that run crapload of updates and installations that has nothing to do with task at hand. I have to find a way to stop all un-necessary services being run during imaging session.

Jerry

 

First tool:  TaskManager is your friend.  With the Process and Performance Tabs, you can identify how hard your Laptop is working and on which Processes.  If you recognize the various Processes, you can Google to determine whether they are Safe-to-Abort.  You can also identify whether critical Memory Resources or Disk I/O is bogging down your System.

 

Second Tool:  WinUpdate Settings in Control Panel.  Open the Windows Update Control Panel and along the Left Column of Tasks use "Change Settings" in order to select "Check for Updates but let me choose whether to Download and Instll them."  Now, you are in control of the Windows Updates, but you won't be left open to a serious Bug or Virus.

 

Thanks for the tips. I looked in Event Viewer in Control Panel and discovered that I had an automatic defrag running at that time. I am defragging HD while imaging for crying out loud! Needless to say that the automatic timer was disabled.

As far as running processes go I would need a week of intense Googling to find out what each one of them does.

Jerry 

[s3igell]

Thanks for the tips. I looked in Event Viewer in Control Panel and discovered that I had an automatic defrag running at that time. I am defragging HD while imaging for crying out loud! Needless to say that the automatic timer was disabled.

 

That'd do it - Heavy Disk I/O due to Defrag...

 

You could also schedule it to only Defrag once every 28 Days, and that on the Full Moon.  

 

As far as running processes go I would need a week of intense Googling to find out what each one of them does.

 

That is true, but a number of them have names of the App which they are part.  You could catch RealPlayer or your Imaging App scanning your Disk for new Images (RealPlayer is triggered by any Image File Extension including CR2).  These wouldn't take too much to decide whether you "Do Something" or not...

[Jerry_K]

Very good suggestion, Shane. I'll schedule defrag on every Full Moon, I am out howling with local dogs anyway. Next one is Super Moon, man I hate that term.

[Jerry_K]

Thanks for the tips. I looked in Event Viewer in Control Panel and discovered that I had an automatic defrag running at that time. I am defragging HD while imaging for crying out loud! Needless to say that the automatic timer was disabled.

 

That'd do it - Heavy Disk I/O due to Defrag...

 

You could also schedule it to only Defrag once every 28 Days, and that on the Full Moon.  

 

That is true, but a number of them have names of the App which they are part.  You could catch RealPlayer or your Imaging App scanning your Disk for new Images (RealPlayer is triggered by any Image File Extension including CR2).  These wouldn't take too much to decide whether you "Do Something" or not...

I have uninstalled RealPlayer, I don't use it or need it. One thing that I think will help me a lot is to turn off Wi-Fi when imaging. I have just tried it and the HD light is nowhere as busy as when Wi-Fi is on.

Jerry