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

Timelapse capture doesn't start anymore after the first print #1934

Closed
gege2b opened this issue May 24, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@gege2b
Copy link

commented May 24, 2017

Hi there

What were you doing?

Doing many prints in a row, with mjpg server, webcam & timelapse enabled, but timelapse capture start only for the first print

The control tab shows the stream as expected

Prints could be of the same or differents objects, it makes no difference

What did you expect to happen and what happened instead?

Timelapse to start at every print.
But instead, no capture at all after the first print and successfull timelapse (the print is going fine, trough)

If I do a print just after a server restart, the timelapse is captured normally

Branch & Commit or Version of OctoPrint

OctoPrint 1.4.0.dev368+g3e5d82c (devel branch)

Operating System running OctoPrint

current raspbian lite on Raspberry pi 3,
webcam is a "Trust HD" with no more info on it :)

Printer model & used firmware incl. version

Not relevant

Browser and Version of Browser, Operating System running Browser

Windows 10, Firefox 53 x64

Link to octoprint.log

Octoprint log

(but I see nothing about timelapse in it)
Please tell me if you want me to supply different info

Link to contents of terminal tab or serial.log

not relevant

Link to contents of Javascript console in the browser

not relevant

Screenshot(s) or video(s) showing the problem:

not relevant

I have read the FAQ.

@foosel

This comment has been minimized.

Copy link
Owner

commented May 24, 2017

Thanks for reporting this, that was also present in 1.3.3rc2 (well, actually also earlier than that, but covered up by a setting that got changed in 1.3.3rc1), so got caught just in time.

Already fixed on maintenance, soon devel, will go into 1.3.3rc3 I hope to release later today.

@foosel foosel added this to the 1.3.3 milestone May 24, 2017

@foosel

This comment has been minimized.

Copy link
Owner

commented May 24, 2017

Small correction, already fixed on staging/maintenance, soon on maintenance and devel

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.