SharpCap Forums

Hi George,

glad to hear it works nicely for you.

Astap doesn't seem to have an equivalent of the 'sigma' setting in Ansvr which allows you to make it more or less sensitive when detecting stars. I suspect that if you increased the sigma (made it less sensitive) then Ansvr would probably fail too near the horizon.

cheers,

Robin

Robin,

Everything worked great with astap tonight. Local plate solves very fast. I have been using your suggestion to use the mount move tool to move the virtual mount to the target coordinates. Then the initial solve goes much quicker.

A minor point when moving mount the object Is copied into file name. Could you have it copy to push to target as well. A minor point but thought I’d mention it.

Just fyi I use the d50 data for astap . 1500 fl with asi183 Mc camera

Really enjoying this push to tool

George

Hi George,

glad it is all working properly now.

For the thing about names, do you mean that it should put the name of the object chosen into the 'Target Name' so that capture files will then be named appropriately, or are you referring to something else?

cheers,

Robin

Robin,
I first use tool to move virtual mount to target this involves finding target in drop down data base. After that window closes I open push to window and then find target again in drop down data again.
A solution to this could be having a button in push to window that lets you select target then moves virtual mount to target coordinates. Then push to solving starts.
Another possibility is to use current move mount tool and transfer the target to the target field in push to do operator won’t have to select target again.

In previous post I mentioned that astap would immediately fail if trying to solve frame blurred by moving scope. Ansvr sometimes tries to solve blurred frame keeping solver working for an extended time then fail. I watch the solver and if it is taking to long I push stop and then start to load new frame

George

I would like to have the last object searched in the search box by default, at least during that session. It wouldn't affect anything and would be very helpful in avoiding search for it again and again when we close the push-to to do other adjustments.

Hi Tiago
Robin has changed the last beta so camera adjustment can be done while in push to window. I like your videos very informative.

George

Hi folks,

thanks for clarifying the ideas - I have a note of them now and will try to implement them (probably not for this week's update though).

cheers,

Robin

Hi robin,
Used push to again it’s working well. Something strange happened. I was live stacking using the auto hide for the window. Somehow the display window shrunk to maybe 1/2 of screen. The display had scroll bars but I couldn’t get window to expand again. I tried various magnification but saw results. I finished stack and closed program. When I restarted everything back to normal. Any idea how I caused this?

Thanks for the help

George

Hi George,

sounds like the layout calculations got into an incorrect state - maybe part of the code thought the stack window was autohide and another part didn't?

Did you use two monitor view? I wonder if the special handling of live stacking in two monitor view doesn't play nicely with auto-hide?

cheers,

Robin

Robin,
I wasn’t using 2 monitor view. I’ll try to find out what I did next session. Unfortunately the clouds are taking over.
George