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
[1.4.0rc1] Time-lapse fails with libx264 selected - "WARNING - Cannot capture image, image number is unset" #3354
Comments
Same results, same message in OctoPrint.log after switching back to mpeg2. Will try Safe Mode next. |
Failing in safe mode too. This looks suspect:
Full OctoPrint.log here: https://gist.github.com/JohnOCFII/e080c299727c8524bcd7bd81cf025649 |
I've got the exact same issue:
Already tried different encoding format, disable plugins, test the settings. I've got two webcams configured if that is relevant. |
Ah shoot. That looks like an issue due to deprecating something and for some reason not catching all places where it was used. |
Fix should be ready for 1.4.0rc2 |
1.4.0rc2 is out. |
What were you doing?
Printing from OctoPrint to Prusa MK3S with MMU2S. I had configured Time-lapse to use the new libx264 in
Settings.
. No time-lapse was created. No indication of time-lapse activity.What did you expect to happen?
Expected time-lapse to be created
What happened instead?
No time-lapse was created.
Did the same happen when running OctoPrint in safe mode?
Did not test in safe mode, but will switch back to mpeg2 and test again next.
Version of OctoPrint
1.4.0rc1
Operating System running OctoPrint
OctoPi 0.16.0
Printer model & used firmware incl. version
Prusa MK3S with MMU2S with firmware 3.8.1
Browser and version of browser, operating system running browser
macOS Catalina (10.15.1) with Safari 13.0.3
Link to octoprint.log
https://gist.github.com/JohnOCFII/750a3d0d0afc18bfaed0e3fee2c589ef
Link to contents of terminal tab or serial.log
N/A
Link to contents of Javascript console in the browser
N/A
Screenshot(s)/video(s) showing the problem:
N/A
I have read the FAQ.
The text was updated successfully, but these errors were encountered: