Logs, is it really an error ERR: Frame send time

Forum for questions and support relating to the 1.25.x releases only.
Locked
caseystone
Posts: 98
Joined: Fri Feb 25, 2005 3:41 am
Location: England

Logs, is it really an error ERR: Frame send time

Post by caseystone »

Hello:

My logs get full of entries, categorized as ERR:

Code: Select all

2011-10-23 01:34:33.763579	zms	11013	ERR	Frame send time 2811 msec too slow, throttling maxfps to 0.29	zm_monitor.cpp	3392
2011-10-23 01:34:31.315417	zms	11007	ERR	Frame send time 3796 msec too slow, throttling maxfps to 0.44	zm_monitor.cpp	3392
2011-10-23 01:34:29.359470	zms	11013	ERR	Frame send time 1842 msec too slow, throttling maxfps to 0.44	zm_monitor.cpp	3392
2011-10-23 01:34:26.286360	zms	11020	ERR	Frame send time 2637 msec too slow, throttling maxfps to 0.66	zm_monitor.cpp	3392
I feel this is more of a feature than an error, and shouldn't be in the logs at all. In earlier versions of Zoneminder in the live view (or montage view) I could choose 'Stills' instead of stream. This helped when watching images from a remote server with something like .6Mbit upload capacity. Now that option is gone, and it seems zms takes note of how long it is taking to send frames to the remote viewer and adjusts the frame-rate accordingly, which is great! Why is it considered a red colored ERR? This really fills up my logs making it harder to find more important errors.

Thanks.
SB G620 on Asus P8H67-M LX, 4GB, WD10EURS 'DVR' drive. Ubuntu 10.04.3 server. System load <=1.

8-port 240fps BTTV capture card, 6 cams. Modect 1 zone blobs of mx area 3, mx blobs 1. Some on alarmed pixels mn5/mx80. Mons not linked.
Locked