Hi Robin,
I did a time lapse of 3h10 this afternoon and I was surprised to see that the .avi (and of course the gif) time stamp started at 13h50 and stopped at 15h06 so only 1h 15... when I was still recording up to 17h10 . Where has the 2 other hours gone ? is it limited to only 1 hour ? It is frustrating because there was ann active protuberance today and I have recorded half the evolution.. despite I stay 3h adjusting the tilt of the capture to get a beautiull video.
if there is a limit of time you should send a warning so we don't miss half the capture.
kind regards
Olivier
timelapse not recorded the total time ?
-
admin
- Site Admin
- Posts: 17378
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: timelapse not recorded the total time ?
Hi,
Ouch, sorry to hear that
There is no time limit that I am aware of, at least not in code I have written. My first thought was that perhaps you hit some sort of size limit on the AVI file, but I just tested and managed to create an 18Gb AVI in normal capture, so there is no limit at 2 or 4Gb.
There are a few things that will stop a timelapse beside pressing the 'Stop' button - I will just list them in case any might be relevant
* Deactivating planetary live stacking or closing the camera (exception : deactivating when 'frozen' will not stop, just pause the timelapse)
* Any change in bit depth/colour space or size of the area being stacked (for instance camera ROI change)
* Any error when writing a frame
* A SharpCap crash/bug report incident - the code will try to finish the timelapse cleanly if this happens before sending the bug report
Most of these will leave traces in the log if they happened, even if the 'finish timelapse' isn't explicitly recorded.
On top of the above, there is also the button that pauses the live stack - that also pauses writing frames to the timelapse, so if the stack was paused and left paused then no new frames would have been added. I don't think this would show up in the log however.
It's probably best for me to have a look through the log to see if anything interesting happened - particularly at the point where the file timestamp stopped being updated. It would also be worth checking the file size/number of frames - I suppose there is just a chance that the file has all the data but the timestamp somehow didn't update after a certain point.
cheers,
Robin
Ouch, sorry to hear that
There is no time limit that I am aware of, at least not in code I have written. My first thought was that perhaps you hit some sort of size limit on the AVI file, but I just tested and managed to create an 18Gb AVI in normal capture, so there is no limit at 2 or 4Gb.
There are a few things that will stop a timelapse beside pressing the 'Stop' button - I will just list them in case any might be relevant
* Deactivating planetary live stacking or closing the camera (exception : deactivating when 'frozen' will not stop, just pause the timelapse)
* Any change in bit depth/colour space or size of the area being stacked (for instance camera ROI change)
* Any error when writing a frame
* A SharpCap crash/bug report incident - the code will try to finish the timelapse cleanly if this happens before sending the bug report
Most of these will leave traces in the log if they happened, even if the 'finish timelapse' isn't explicitly recorded.
On top of the above, there is also the button that pauses the live stack - that also pauses writing frames to the timelapse, so if the stack was paused and left paused then no new frames would have been added. I don't think this would show up in the log however.
It's probably best for me to have a look through the log to see if anything interesting happened - particularly at the point where the file timestamp stopped being updated. It would also be worth checking the file size/number of frames - I suppose there is just a chance that the file has all the data but the timestamp somehow didn't update after a certain point.
cheers,
Robin