On Windows, V13 and V14 seem to have this feature (not tried V12 as its quite out of date).
I didn't notice the feature until I connected an old USB web cam and expected to need to use a separate timelapse program, but a new tab appeared in the Print dialog, showing the a preview and allowing some setting changes like folder to save to and some colour correction stuff (possibly associated with the camera driver)
However on a print that lasted an hour, the timelapse video only lasted around 10 secs, so I wanted to change how often a picture (frame) was captured.
Looking on GitHub there are various bits of code that seem to control the timelapse.
I've just had a trawl though the code and it looks like this bit of code causes the camer to take a new image
def mcZChange(self, newZ):
self.currentZ = newZ
print 'Z:%f' % newZ
if self.cam is not None:
So I'm no expert, but it appears to be taking a photo every time the Z changes.i.e once per layer, so as my object only has 75 layers and the resultant movie is probably 24 fps, the movie is only just over 3 seconds long (which is a bit short for a 1 hour print :wink:
I suspect that if its not too much overhear, that perhaps it could be put into
e.g around line 458, where it appers to get the print time.
printTime = self.machineCom.getPrintTime() / 60
so we could take a picture every 10 seconds using this code (probably... Note its been a while since I did any python programming :wink:
if self.cam is not None && printTime%10 == 0:
I implemented basically the change I described above, and it appears to work, however I did a print and it hung after about 10 minute.
However I don't think this is necessarily a consequence of taking the timelapse video, as I have issues with power glitches, and in this case I'm fairly sure there was a brownout that hung the print.
So I'll try again today and see if it hangs this time.
Note. Even 10 seconds doesnt give a very long or smooth video, as at 24 fps playback, a photo every 10 secs is 1/240 normal speed, so a 1 hour print is compressed to just 15 seconds, which I think is probably too short, unless the build print is very very long, i.e even a 4 hour print would only produce 1 minute of video.
Probably a better time lapse setting is between 1 and 5 seconds per frame, depending on how long the print is estimated to take.
i.e Perhaps the best way to approach this is to add something to the UI where you enter the desired length of the final video e.g. 1 minute,. and the code calculates how often to take the individual pictures, based on the Estimated Print Time.