Motion - Bug Report 2013x 06x 27x 200451
You are here: Foswiki>Motion Web>BugReports>BugReport2013x06x27x200451 (27 Jun 2013, KlausMueller)Edit Attach

BUG: No rollover if target file size is limited

I configured motion to rollover a timelapse file on a daily base. The resolution is 800x600. I tried to capture a survillance video of my cats while away. wink

Problem: The file is truncated at nearly 2 GB of size but motion still captures live image (display over web server). No error message is generated or a new file is generated to capture the video after the 2 GB size limit.

Is it possible to configure a rollover mechanism depending on the size of the video and not based on time. Hourly may generate to much videos. Daily does not work as the file size exceeds the limits.

I use a Raspberry Pi as system with a Logitech pro 9000 webcam and an ext4 file system and the latest Rasbian OS version.
No error message displayed or logged. Video is lost.


Motion version: 3.2.12
ffmpeg version: ffmpeg version 0.8.6-6:0.8.6-1+rpi1
Shared libraries: ffmpeg, mysql, postgresql
Server OS: Linux raspberrypi 3.6.11+ #474
-- KlausMueller - 27 Jun 2013

Follow up

Fix record

Topic revision: r1 - 27 Jun 2013, KlausMueller
Copyright © 1999-2024 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.