Motion - Release Note Motion 3x 2x 3

Motion Release 3.2.3 - Release Notes

Motion release 3.2.3 - 16 Aug 2005

Summary of changes since 3.2.2


Bugfix release only. No new features.


  • Fixed a bug in the http control code that failed to accept a client connecting in some systems (Peter Holik).
  • Fixed a series of bugs where several feature were using the image buffer after text was added for noise tuning, auto_brightness, reference frame update when tracking etc. When a netcam failed to produce an image the text added to the previous image became motion detected also. The code is not changed so that the ring buffer is used for timestamped images and the image used for detection is in a buffer cnt->imgs.image_virgin. (Kenneth Lavrsen).
  • Auto brightness used the first image in ring buffer instead of the latest image and it used an image with time stamping. It now uses the new cnt->imgs.image_virgin buffer.
  • Cleaned out unused code from httpd control (Angel Carpintero).
  • Option switch filter used print_int instead of print_bool when motion.conf was saved (Kenneth Lavrsen).

Known Problems

  • See the for open bugs.
  • The pwc-ioctl.h is for pwc version 9.0.1, 10.0.6 and 10.0.7a. If you still use the pwc 8 series then you need to use the headerfile pwc-ioctl.h-pwc8.0 (copy the pwc-ioctl.h-pwc8.0 over pwc-ioctl.h). This is relevant for USB cameras using Philips chips.
  • Dimensions of camera image must have both height and width that are a multiple of 16. Thís is normally not a problem. All standard sizes like 640, 480, 352, 320, 288, 240, ...etc are multiples of 16.


GPG Signature

Kenneth Lavrsen's public key can be found on keyservers or on this non-wiki webpage.

Signature is for the source tar.gz
Version: GnuPG v1.4.1 (GNU/Linux)


-- KennethLavrsen - 16 Aug 2005
Topic revision: r2 - 16 Aug 2005, KennethLavrsen
Copyright © 1999-2019 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.