[Request] Option to render timelapse later instead of immediately

[mwhuss]

Feature Benefits:

Sometimes prints fail or I want to start another print immediately which is not recommended when rendering a timelapse. I'd like the ability to go to "Unrendered Timelapses" and start the render myself instead of it happening immediately after a print finishes.

[philphilphil]

I would like this as well, my rpi1 is soo slow and often it's not even worth rendering when the print fails. Maybe with a new setting "Autostart Timelapse renders" so nothing changes for users who like the auto-start of the render.

If foosel likes this idea i would also be able to implement it :).

[foosel]

An "Autostart timelapse renders" checkbox on the timelapse tab sounds great, feel free to go ahead with that @philphilphil! Just a word of a warning, I'm currently a bit behind with reviewing code changes due to having my hands full with the funding situation, so I don't want to promise to be able to immediately merge it when you send a PR. Sorry in advance for that.

[philphilphil]

@foosel no worries :). I think i'll need some days to finish and test it correctly anyway.

[mwhuss]

@philphilphil let me know if you need any help testing it

[fraternl]

@philphilphil: A lot of days have passed since April 18th ;-)

I just created a ticket that's somewhat related: https://github.com/foosel/OctoPrint/issues/1526

[philphilphil]

@fraternl i kind of forgot about this ticket.. I have already some changes from back in April on my computer, i will review them and finish it, still an important feature i think :)

[fraternl]

@philphilphil do you consider https://github.com/foosel/OctoPrint/issues/1526 as well in your changes?

[fiveangle]

I can see this isn't getting much traction, but for consideration of posterity, a preference to "Automatically delete Cancelled print time lapses" (low hanging fruit) as well as "Render timelapse when not printing" options would be ideal. For the when-not-printing scenario, the script could subscribe to the log file (or port to syslog if not already) to monitor when the job is finished, or cancelled, then automatically kick off the render(s). There would have to be some coordination trigger mechanism so that if OP started a new print job, it would notify the render script to quit or pause render/resume "monitor" mode, waiting for completion, then restart the job after.

[Oninaig]

Any update(s) on this?

[grantx2016]

I would like this also.

[Avrution]

Same. Really not sure why there isn't an option to not render on cancel.

[Avrution]

I can see this isn't getting much traction, but for consideration of posterity, a preference to "Automatically delete Cancelled print time lapses" (low hanging fruit) as well as "Render timelapse when not printing" options would be ideal. For the when-not-printing scenario, the script could subscribe to the log file (or port to syslog if not already) to monitor when the job is finished, or cancelled, then automatically kick off the render(s). There would have to be some coordination trigger mechanism so that if OP started a new print job, it would notify the render script to quit or pause render/resume "monitor" mode, waiting for completion, then restart the job after.

This

[foosel]

Really not sure why there isn't an option to not render on cancel.

Because no one has sent a pull request to do so, and I have my hands full with other stuff 🙂 But I've now marked this as up-for-grabs in the hopes that someone will look into it.