4664455596
* Fix issues with vid_control_params handling of depreciated parameters * Moved the comment of calling copy_vid_ctrl to where it actually happens * The if checks for the names were inverse of what they needed to be and ALL depreciated parameters were taking this path copy_vid_ctrl: * make it static like its forward declaration * power_line_frequency is default at -1, so 0 needs to be copied over but anything with a value of 0 was being skipped * Fix handling of depreciated text_double Copying the bool value of text_double directly to text_scale copies a value of 0 for off and 1 for on, which ends up with no text or the default of no upscaling, respectively. We need to handle this with a custom function to translate the bool to 1 (for no upscaling) and 2 (for typical double upscaling). * Update motion-dist.conf.in for text_scale
Motion
Status
The build status from travis-ci for the master branch is: 
Description
Motion is a program that monitors the video signal from one or more cameras and is able to detect if a significant part of the picture has changed. Or in other words, it can detect motion.
Documentation
The documentation for Motion is contained within the file motion_guide.html.
The offline version of this file is available in the doc/motion directory. The online version of the motion_guide.html file can be viewed here
In addition to the detailed building instructions included within the guide, the INSTALL file contains abbreviated building instructions.
Resources
Please join the mailing list here
We prefer support through the mailing list because more people will have the benefit from the answers. A archive of mailing list discussions can be viewed here
License
Motion is mainly distributed under the GNU GENERAL PUBLIC LICENSE (GPL) version 2 or later. See the copyright file for a list of all the licensing terms of the various components of Motion.
The file CREDITS lists the many people who have contributed to Motion over the years.
Contributing
Issues and Patches should be submitted via github and include detail descriptions of the issue being addressed as well as any documentation updates that would be needed with the change.