Motion Plugin Config File Discussion Camera Threads

Refactored from MotionPluginConfigFileDiscussion

Camera threads.

Today the camera threads are defined by an option called thread. It calls a thread file and any options inside this thread file belong to the camera. The advantage is that it take one little # or ; in front of thread to disable a camera. The disadvantage is that it is very confusing and you have to open several files to control your camera settings. KennethLavrsen prefers the Samba syntax.

Proposal 1 - Use the Samba config file syntax.

In Samba syntax the camera thread options are all options from the [camera 1] and until the next camera option in []

[camera 1]
videodevice /dev/video0
input 1
text_left CAMERA 1
target_dir /usr/local/apache2/htdocs/cam1
webcam_port 8081
on_picture_save /usr/local/motion-bins/camparse1.pl
on_movie_end /usr/local/motion-bins/mpegparse1.pl

[camera 2]
videodevice /dev/video1
input 1
text_left CAMERA 2
target_dir /usr/local/apache2/htdocs/cam2
webcam_port 8082
on_picture_save /usr/local/motion-bins/camparse2.pl
on_movie_end /usr/local/motion-bins/mpegparse2.pl

Proposal 2 - Use the TAG syntax like in Apache httpd.conf

<camera 1>
videodevice /dev/video0
input 1
text_left CAMERA 1
target_dir /usr/local/apache2/htdocs/cam1
webcam_port 8081
on_picture_save /usr/local/motion-bins/camparse1.pl
on_movie_end /usr/local/motion-bins/mpegparse1.pl
</camera 1>

<camera 2>
videodevice /dev/video1
input 1
text_left CAMERA 2
target_dir /usr/local/apache2/htdocs/cam2
webcam_port 8082
on_picture_save /usr/local/motion-bins/camparse2.pl
on_movie_end /usr/local/motion-bins/mpegparse2.pl
</camera 2>

Camera thread option name.

No matter what we decide above what name should be use. Some proposals

[camera 1]

[thread 1]

[1]

<camera 1> </camera1>

<thread 1> </thread 1>

<1> </1>

-- KennethLavrsen - 08 Oct 2005