JustMotion/README.md

# JustMotion #

JustMotion is a simple, lightweight video surveillance application utilizing
the server-client model that doesn't try to re-invent the wheel. The source 
code for both server and client are available this repository and can be 
compliled and/or installed separately.

# JustMotion-Server #

JustMotion-Server is the server portion of this appication that monitors the 
video feeds of any IP or local cameras and records footage that contains 
motion to permanent storage. The main advantage of this is reduced storage 
requirements as opposed to continuous recording because only video footage 
of interest is kept in storage.

The server implements the principle of doing the least as needed, as a result 
it extremely lightweight with the fact it doesn't attempt to re-implement much 
of it's functions internally but will instead rely on external applications 
that already implement the functions very well.

It doesn't have a builtin user interface so instead external applications are 
more than welcome to interface with the buffer/footage directories to 
implement a user interface of any flavor.

# JustMotion-Client #

JustMotion-Client is the client portion of this application that actually 
implement a user interface. Utilizing the same principle of doing the least as 
needed, it uses an external video player to play m3u8 playlist files mounted 
as an ssh filesystem to play live or recorded footage from the server.

### Usage (server) ###

```
JustMotion 1.0

Usage: jmotion <argument>

-h : display usage information about this application.
-d : all valid config files found in /etc/jmotion will be used to
     create camera instances. (this is blocking, meant to run with systemd)
-v : display the current version.
-u : uninstall the entire server from your system, including the service. all
     recorded footage and config files will remain.
-f : force an action without pausing for user confirmation.
-s : view the status of all camera instances.
-q : kill all camera instances.
-r : same as -d except it is non-blocking for starting all camera instances
     via systemd. same as 'systemctl start jmotion'
```

### Config File (server) ###

The config file is a simple text file that contain parameters that dictate the
behavior of the server for each camera located in the /etc/jmotion directory.
The config for each camera can have any unique name within that directory. 
Below is an example of a config file with all parameters supported and 
descriptions.
```
# Motion Watch config file
#
# note all lines in this config file that starts with a '#' are ignored.
# also note to avoid using empty lines. if you're going to need an empty
# line, start it with a '#'
#
recording_uri = rtsp://1.2.3.4:554/h264
# this is the uri to the main stream of the IP camera that will be used
# to record footage. it can be a url to an rtsp stream or a direct device
# path such as /dev/video0.
#
buffer_path = /tmp/jmotion
# this is the work directory the app will use to store live footage and
# image frames. it's recommended to use a ram disk for this since there
# will be large amounts of io occuring here. 1GB of space per camera is
# a good rule of thumb.
#
rec_path = /var/jmotion/footage
# this is video output directory that will be used to store any footage
# that contain any motion events.
#
live_secs = 160
# this is the maximum amount of seconds worth of live footage to keep in
# buffer_path before deleting the oldest 3 seconds worth of footage.
# note: each video clip in buffer_path is typically 3 seconds long.
#
cam_name = cam-1
# this is the optional camera name parameter to identify the camera. this
# name will also be used as the base directory in buffer_path and rec_path. 
# if not defined, the name of the config file will be used.
#
max_events_bytes = 10G
# this is the maximum amount of disk space of video footage that can be 
# recorded in the rec_path directory.
#
max_event_secs = 30
# this is the maximum amount of secs of video footage that can be recorded 
# in a motion event.
#
img_comp_cmd = compare -metric FUZZ &prev& &next& /dev/null
# this is the command line template this application will use when calling 
# the external image comparison application. the external application is
# expected to compare snapshots from the video stream to determine how 
# different the images are from each other. it needs to output a numeric 
# score with the higher values meaning very different while low values 
# mean similar images. the snapshots pulled from the stream will be bitmap 
# formatted so the app will be required to support this format. also avoid 
# outputting any special chars, only numeric chars with a single '.' if 
# outputting a decimal value. magick is the default if not defined in the 
# config file. the special string &prev& will be substituted with the path 
# to the "previous" bitmap image, behind in time stamp to the image path 
# subtituted in &next&.
# 
img_comp_out = stderr
# this is the standard output stream the app defined in img_comp_cmd will
# use to output the comparison score. this can only be stderr or stdout,
# any other stream name is considered invalid.
#
vid_codec = copy
# this is the encoding codec to use when recording footage from the camera. 
# the list of supported codecs entirely depend on the hosts' ffmpeg 
# installation. run 'ffmpeg -codecs' to determine this list. if not 
# defined, 'copy' will be used as in it will just copy the codec format 
# from the camera itself without re-encoding.
#
aud_codec = copy
# this is the audio encoding codec to use when recording from the camera.
# the list of supported audio codes can be determined by running 'ffmpeg
# -codecs' on the host machine. if not defined, 'copy' will be used as in
# it will directly copy the audio stream from the camera if present.
#
stream_ext = .mkv
# this is the file extension that will be used to when recording footage
# from the camera in buffer_path. ffmpeg will also use this to determine 
# what format container to use for the video clips.
#
thumbnail_ext = .jpg
# this the image format that will be used when creating the thumbnails
# for the videos clips recorded to rec_path.
#
rec_ext = .mkv
# this the the file extension that will be used when storing motion footage 
# to rec_path. ffmpeg will also use this to determine what format container 
# to use for the video clips. 
#
img_thresh = 8000
# this parameter defines the score threshold from img_comp_cmd that will
# be considered motion. any motion events will queue up max_event_secs
# worth of video clips to be written out to rec_path.
#
post_secs = 60
# this is the amount of seconds to wait before running the command 
# defined in post_cmd. the command will not run if motion was detected 
# in the space before post_secs elapsed.
#
post_cmd = move_the_ptz_camera.py
# this an optional command to run with post_secs. one great use for this
# is to move a ptz camera to the next position of it's patrol pattern.
# note: the call to this command will be delayed if motion was detected.
# also, motion detection is paused while this command is running.
#
rec_fps = 30
# this sets the recording frames per second for the footage recorded 
# from the camera. this has no affect if using 'copy' as the vid_codec.
#
rec_scale = 1280:720
# this sets the pixel scale of the recorded footage from the camera. it
# uses width, height numeric strings seperated by a colon, eg W:H. this
# has no affect of using 'copy' as the vid_codec.
#
img_scale = 320:240
# this sets the pixel size of the thumbnails for recorded stored in 
# rec_path. it uses width, height numeric strings seperated by a colon, 
# eg W:H.
#
```

### Build/Install ###

This application is currently only compatible with a Linux based operating
systems that are capable of installing python3 and the QT API (QT6.X.X or 
better).

```
./build.py    <--run this first
./install.py  <--run this next
```
```
note 1: the build script will search for the QT api installed in your 
        system. if not found, it will ask you where it is. either way
        it is recommended to install the QT API before running this
        script.
note 2: both scripts assume python3 is already installed.
```