Motion - Bug Report 2013x 09x 28x 182300

BUG: setting minimum_motion_frame to 1 stops image output until restart

I am experimenting with settings to see the effect. I had minimum_motion_frame set as 2, and output was as expected, both movie and image files. Then I changed the value to 1, using the control interface, and on the next event there were no images written. "on_event_end" ran with an event number, but there were no images for that event, only a movie file. After a restart, it was working as expected again

Environment

Motion version: 3.2.12
ffmpeg version:  
Shared libraries: ffmpeg, mysql, postgresql
Server OS:  
-- WilliamPhelps - 28 Sep 2013

Follow up

Fix record

BugReportForm edit

TopicTitle setting minimum_motion_frame to 1 stops image output until restart
BugStatus New
AssignedBugTo
SubmittedBy WilliamPhelps
Topic revision: r1 - 28 Sep 2013, WilliamPhelps
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Please do not email Kenneth for support questions (read why). Use the Support Requests page or join the Mailing List.
This website only use harmless session cookies. See Cookie Policy for details. By using this website you accept the use of these cookies.