Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] More Timelapse Ending Options - Real Time Post Roll #1624

cinderblock opened this issue Dec 4, 2016 · 1 comment


None yet
3 participants
Copy link

commented Dec 4, 2016

I enjoy the ending extension timelapse feature that was added because of #384.

However, the nice feature of the delta-z based captures where the last frame is repeated for a few seconds is sorely missing from the time based timelapse. It is annoying to wait for many minutes just to get a couple more seconds of data, often after the part has been removed since my hand was in the way.

Even better, in my humble opinion, it would be nice to be able to record the postroll in real time. I've had a few occasions where I messed up the end GCode and that made my nozzle move quickly into my part. This was completely missed by the timelapse video. You could even make it capture at half or variable time.

Branch & Commit or Version of OctoPrint

Version: 1.2.18 (master branch)

I have read the FAQ.


This comment has been minimized.

Copy link

commented Dec 5, 2016

Quoting the change log for 1.3.0rc2 (with 1.3.0rc3 being available on the "Devel RCs" release channel):

  • #1422 - Added option for post roll for timed timelapse to duplicate last frame instead of capturing new frames. That makes for a faster render at the cost of a still frame at the end of the rendered video. See also #1553.

So the last-frame-repetition option for delta-t/timed timelapses is already implemented and will be available in 1.3.0 which I'll hopefully be able to release within the next week.

Recording real time is not possible, at least not without what would probably boil down to a full rewrite of the timelapse component. It only knows how to capture snapshots from a URL (25 snapshots per second won't work) and the rendering of the timelapse does not allow for variable frame rate (which you'd need for a real-time visualization after the print).

@foosel foosel closed this Dec 12, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.