Hi,
please can people try build 3.1.5115.
If you have suffered from this problem then please turn on the new option 'Record extra information in the log for troubleshooting' in the general settings before you start stacking. Please also show the log window (from the help menu) and keep an eye on it.
With this new option set there will be a lot of logging when you adjust the live stack histogram - you should see something like
Code: Select all
Received image update request
update already running, setting request flag and ignoring
Received image update request
Received image update request
Re-displaying frame due to image update request
Image update requested while previous was in progress, re-running
FrameProcessor update request received at the ImageProvider - passing on ImageUpdateEvent
Re-displaying frame due to image update request
Every time you move one of the level bars you will get a 'Received image update request' line - many will happen as you drag. Not all of these will result in the display being updated, since often they arrive so quickly that SharpCap is still busy working on the last one when the next arrives. When this happens SharpCap sets a reminder to itself to re-update when the current update is over. At the end, after every movement of the sliders there should be a line that ends with the 'Re-displaying frame due to image update request' message.
If the histogram stops responding it is most likely that the last 're-displaying' message will also stop showing. If that happens, please send me the full log and I can hopefully work out where the request is getting lost or stuck from what other messages are showing. To be honest, if you have the problem happen to you while you have the extra logging turned on then please send me the whole log *and* the time that the problem happened (so that I know where in the log to look!).
Now, having said all that I did find one place where - just maybe - under some odd circumstances the code could get stuck not passing on the requests until you shut down and re-started SharpCap. I fixed that. What I found could not have had an effect that lasted over a restart of SharpCap though.
On the subject of the camera settings being saved over re-install, this is supposed to happen. SharpCap 3.1 auto-saves settings when you close down the camera in a hidden capture profile and re-loads them when you open the same camera. Capture profiles are not deleted on uninstall or upgrades, so this profile is still used after an uninstall and reinstall. You can turn this feature off in the SharpCap settings if it annoys you.
I don't think the settings being restored will bring the problem back, but there are certain camera settings that could have an impact on whether a problem like this shows or not -these are
* Capture Area
* Colour Space
* Exposure Length
* Dark Subtraction
* Flat Correction
I think that other settings are unlikely to have any impact.
Please also check that the Status listed in the 'Information' box in the live stacking area shows as 'Waiting for Next Frame' for most of the time. In the 'waiting' status, SharpCap is able to respond to histogram adjustments. In other states it may not be able to respond due to changes being made to the stack to process the current frame. If the status shows 'Calculating Alignment' most of the time - or some other status the problem is lack of CPU speed or too much CPU in use by other processes or too fast a frame rate.
hope this helps,
Robin
