File target 4.2.15192

[Gfischer]

Hi Robin,

I just installed new version.When opening sc I first had a message stating the target for file saving doesn’t exist. I clicked on use location anyway. I then closed sc and reopened no more warning. Then to check file transfer I ran test button for target location in settings. The test starts but never completed. I just took a quick pic and it transfers no problem. I don’t write my files to computer running sc. I save files to a network computer.
No hurry on this everything runs fine. If I run the test in settings it never completes and locks up sc. thought you might want to know.


George

[admin]

Hi George,

on startup, SharpCap tests the folder set up as the main capture directory, just to check that it exists and you can write a file to it - this gives you an early warning if there is a problem before you try to start capturing. It sounds like this check failed for you at least once, possible because the network drive that you use was briefly unavailable for some reason. Similarly, the disk speed test could take a long time if the network drive was either only available intermittently or the connection was slow for some reason.

So my guess is that this would be due to some sort of temporary network glitch - certainly nothing new in the SharpCap code in those areas for some time.

cheers,

Robin

[Gfischer]

Robin ,
Thanks for the explanation.

I have another question. I’ve been using the histogram tracking during livestacking. When using star color calibration applied once every 2 min the histogram has to be manually adjusted often. I tried applying the old white balance instead and the tracking is excellent. Am I doing something wrong when using star color calibration applied?

Thanks for any ideas you can give.

[admin]

Hi,

when you say 'adjusted often', do you mean that you are regularly adjusting it between the auto calibration happening every two minutes because the drift happens between one auto calibration and the next? Or, alternatively, do you mean that the auto calibration after two minutes is not giving you the image that you want, so each time it calibrates you need to adjust?

cheers,

Robin

[Gfischer]

Robin,
At the beginning of stack I adjust after every auto color stellar correction. As the stack time increases the change of the histogram gets smaller so I don’t need to manually set histogram levels as much. When using the old white balance to color correction the tracking follows the histogram much closer. Of course the color correction is not as good as the stellar color correction.
I was thinking maybe I’ve set something wrong.

[Gfischer]

Robin,
I did some experimenting live stacking last night. I started out imaging m72 with stellar correction applied every 2 minutes. I adjusted histogram to a good view and turned on histogram tracking at 4 min. I then didn't change settings through 30 min integration. The histogram kept moving until at end view was washed out.
I then imaged a small galaxy. This time I only applied stellar color at 4 min one time only. I then set histogram tracking and didn't touch controls for the 30min integration. the view remained the dame though out integration. The histogram tracking followed well.
I think the stellar color causes the histogram tracking to lose the histogram curve due to the quick change of histogram position. The problem with not applying stellar correction is the color balance shifts. I was looking at the settings options in live stacking. If you select applying stellar correction periodically and turning on tracking the view will vary.
I saved some screen shots from last night and my log if that will be of any use.

George

https://drive.google.com/drive/folders/ ... sp=sharing

[admin]

Hi George,

OK, thanks for sharing those screenshots - they really help as I spotted a couple of things that might help explain this...

It looks like the problem is happening with the stretch tracking turned on at the same time as the repeated auto calibrations *and* that the auto calibration is set up not to adjust the stretch. Your analysis is probably correct that the colour balance (and background) adjustments of the repeated calibrations are upsetting the stretch tracking. I mostly leave the option for the calibration to adjust stretch turned on, so I have not seen anything like this, but now I know what to do to try to reproduce and understand the problem

A picture is worth 1000 words!

cheers,

Robin

[Gfischer]

Robin,
Clouds tonight. I think I tried the stretch option with the stellar correction. I remember it being the same as using the lightning bolt auto stretch. I did the same thing in sequencer every 2 min applying stellar correction then auto stretch. On star fields without nebula at large galaxy this worked fine. But not enough contrast for extended targets. What would work great is to set histogram levels after stacking a few frames to get desired look. Then push button to memorize level lines position on histogram. From then on the measurement are applied to histogram when applying auto stretch. Even if just the black level is returned to the same spot on histogram curve when auto stretch would be close. The midtone doesn’t seem to need adjustment as much.

[admin]

Hi,

please try the latest update - 4.2.15217. I found that the stretch tracking was not being applied properly when a calibration was being applied, so that the stretch would track from frame to frame but then each new calibration could throw it further off. Of course if the calibration was also resetting the stretch then you never notice this...

I have now fixed this so that the stretch tracking is applied in those situations. I don't know if it will now work perfectly, but at least it is *trying* to do the right thing now

cheers,

Robin

[Gfischer]

Robin,
Looks like it’s going to be clear tonight. I installed 217 yesterday I’ll give it a try and let you know. Should I use stellar correction without auto stretch? I’ll try it both ways.

Thanks for the help