Motion - Motion Release 3x 1x 20snap 2

Motion Snapshot Release 3.1.20_snap2

Release Notes

3.1.20 snap2 - 27 Mar 2005

:scull: Don't use. Buggy

Bugfix Development Release - not recommended for normal use

The netcam code is still under development but we are very interested in getting test reports on these releases from people with Network cameras.

Netcam related bug reports from the snapshot releases can be added as a comment to http://www.lavrsen.dk/twiki/bin/view/Motion/NetcamStabilityPatch

Changes since 3.1.19

snap1
  • Fixed a bug in noise tune which was most visible at very low light. (Joerg Weber and Kenneth Lavrsen)
  • Improvement in the noise-tune algoritm (Joerg Weber)
  • Netcam fixes and debug code by Christopher Price. http://www.lavrsen.dk/twiki/bin/view/Motion/NetcamStabilityPatch
    • Fixed netcam startup race condition.
    • Refactored image handling back to single unified function
    • Refactored reconnection algorithm
    • Jpeg only based connections should now use less cpu time
    • Synced syslog/printf style to new motion standard
    • Added developer debug trace defines/code
    • Defines now used for many constants
    • Fixed support for netcams without content-length header (streaming only)
    • Remove memmem from netcam_wget.[c|h] (no longer used)
    • Several miscellaneous code cosmetic changes
    • Fixed support for non-streaming (image based) netcams without content-length header.
    • TODO: remove tests for memmem from configure
  • Re-arranged many of the const char declarations so that they are always before any statements within a block { }. This is to avoid compiler errors with older but still used gcc versions such as 2.9.5. (Kenneth Lavrsen)
  • Changed the use of %zd to %llu in printf statements of size_t types. This is done to avoid compiler errors with older but still used gcc versions such as 2.95. (Kenneth Lavrsen)

snap2
  • Removed a gcc 2.95 compiler warning (netcam.c:1036: warning: variable `pic' might be clobbered by `longjmp' or `vfork') (Kenneth Lavrsen)
  • Fixed some file descriptor leaks in webcam.c and netcam.c (Christophe Grenier)
  • Initiate cnt->event_nr to 1 to avoid code related to end of events and long mpeg films to be run during startup of Motion. (Kenneth Lavrsen).
  • Added new function in event.c close_anything_open() which is called from send_sms, send_mail and exec_command in order to prevent file descriptor and open sockets to be inherited by the shell causing freezing and instability. Code contributed by Christophe Grenier, Christopher Price and Kenneth Lavrsen. http://www.lavrsen.dk/twiki/bin/view/Motion/BugReport2005x03x21x070534
  • Renamed the top level global context structure to cnt_list so it can be reached from child threads and by above mentioned close_anything_open() (Christophe Grenier).

Next Steps

  • Still open todos on Netcam code. Keep on sending bug reports.
  • Fix open bugs.
  • Check the code for FreeBSD. This snap has not been tested at all in FreeBSD.

Known Problems

  • See the BugReports for open bugs.
  • The pwc-ioctl.h is for pwc version 9.0.1 and 10.0.6. 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.

Download

Bug Reports


-- KennethLavrsen - 27 Mar 2005
I Attachment Action Size Date Who Comment
fix-freebsd-configure.diff.gzgz fix-freebsd-configure.diff.gz manage 884 bytes 27 Mar 2005 - 19:18 AngelCarpintero Removed memmem check in configure , fix version in configure.in.freebsd , fix CPU autodetection in FreeBSD version
motion-3.1.20_snap2.tar.gzgz motion-3.1.20_snap2.tar.gz manage 258 K 27 Mar 2005 - 02:23 KennethLavrsen  
Topic revision: r3 - 27 Mar 2005, AngelCarpintero
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.