Majestic is a video streaming application, the heart of our firmware (in relation to camera/video surveillance functionality). Majestic is configurable via /etc/majestic.yaml file, and has many features/services enabled by default. Unneeded options can be switched off for better security and performance. See /etc/majestic.full for configuration options.
At the moment, the access has two level in system:
root - the main system user, whose name and password are identical when logging into the system via SSH and WEB, there are no restrictions.
viewer - a user with limited rights who is denied access via SSH and WEB. The user can only receive RTSP requiring authorization. Update by 2024.11.08 - in the near future we will also give him the ability to watch all media resources available on the WEB port, and also control the /night/toggle switch, but the login to the interface itself will still be prohibited. We might also add a specific path to the directory of scripts that it will be allowed to execute
adduser viewer -s /bin/false -D -H ; echo viewer:123456 | chpasswd
-HUP restart Majestic (Except Ingenic T21).
-SIGUSR2 SDK Shutdown (For all platforms).
Majestic supports multiple audio, video and still image formats, and more. You can find the full list of available endpoints on this page.
The long JPEG control parameter did not fit into the example on the site and we publish it here:
/image.jpg?width=640&height=360&qfactor=73&color2gray=1
At the moment it is possible to change parameters in the configuration file via the CLI utility.
This allows parameters to be changed with a single line in pseudo-dynamic mode on some platforms simply by forcing a re-read of the configuration file.
cli -s .video0.codec h264 ; cli -s .video0.fps 10 ; killall -HUP majestic
/metrics/isp
/metrics/venc
/metrics/motion
/night/ircut
/night/light
If these variables are used, it is possible to replace the used sandbox scripts. Works only for simple day/night schemes with minimal configuration and in the absence of mentions of irSensorPin in the majestic.yaml configuration file. If the light sensor gpio is set, it will use the default mode.
The settings work like this:
day < [minThreshold] | hysteresis | [maxThreshold] < night
If the sensor gain is 1024 on a bright day the minThreshold could be set to 2000, if the sensor gain is 32000 on a dark night the maxThreshold could be set to 10000.
cli -s .nightMode.minThreshold 10
cli -s .nightMode.maxThreshold 50
Motion detect is supported for Hisilion/Goke, Ingenic and Sigmastar.
When a motion event is detected, majestic invokes a predefined script /usr/sbin/motion.sh with a parameter specifying the object count:
/usr/sbin/motion.sh [count]
Enable motion detection in majestic configuration:
cli -s .motionDetect.enabled true
cli -s .motionDetect.debug true
Reboot the camera and restart majestic in the foreground:
killall majestic; sleep 3; majestic
You should see the script running after motion detection events:
20:37:02 <SED_IVE_DETCTOR> [ motion] motion_update@155 Motion detected: [1163x0] -> [690x475]
20:37:02 <SED_IVE_DETCTOR> [ tools] motion_event@615 Execute motion script: /usr/sbin/motion.sh
To instantly launch a YouTube broadcast, run these commands in the console:
cli -s .video0.codec h264
cli -s .audio.enabled true
cli -s .outgoing.enabled true
cli -s .outgoing.server rtmp://a.rtmp.youtube.com/live2/you-key-here
reboot
Examples of other addresses for different services:
- YouTube
- rtmp://a.rtmp.youtube.com/live2/---KEY---
- Telegram
- rtmps://dc4-1.rtmp.t.me/s/---KEY---
- RuTube
- rtmp://upload.rutube.ru/live_push/---KEY---
- OK and VK
- rtmp://ovsu.mycdn.me/input/---KEY---
We ask that you add information about other popular services here, thank you.
RTMP reconnection and timeout logic works as follows:
0-200 tries = 10 seconds timeout
200-500 tries = 60 seconds timeout
500-1000 tries = 300 seconds timeout
1000+ tries = 600 seconds timeout
outgoing:
enabled: true
server: udp://192.168.1.10:5600
naluSize: 1200
- udp://IP-1:port
- udp://IP-2:port
- unix:/tmp/rtpstream.sock
- rtmps://dc4-1.rtmp.t.me/s/mykey
For basic ONVIF to work correctly, you need to enable it and add a user to the system as shown in the example:
cli -s .onvif.enabled true
adduser viewer -s /bin/false -D -H
echo viewer:123456 | chpasswd
For the purpose of unification and standardization for all platforms, as well as to increase the stability of the streamer, the image size will always be equal to the size on the Video0 channel and a separate setting is not provided.
Detection zones of two types:
motionDetect.roi: 1854x1304x216x606,1586x1540x482x622
motionDetect.skipIn: 960x540x1920x1080
roi - region of interest, when we specify one or more regions whose movements we are interested in.
skipIn - on the contrary, if we are interested in movements on the whole screen, except for some areas (for example, there is a tree in the frame, which is swaying in the wind).
Coordinate format is the same as in osd.privacyMasks: x,y of the top left point, length and width in pixels.
Use convert command from ImageMagick software. Run it like this:
convert -verbose -sampling-factor 4:2:0 -size 1920x1080 -depth 8 image.yuv image.png
where 1920x1080 is the picture resolution of video0, and .png is the target
image format.
Use ffplay utility from ffmpeg package.
ffplay -ar 48000 -ac 1 -f s16le http://192.168.1.10/audio.pcm
ffplay -ar 48000 -ac 1 -f alaw http://192.168.1.10/audio.alaw
ffplay -ar 48000 -ac 1 -f mulaw http://192.168.1.10/audio.ulaw
ffplay -ar 8000 -ac 1 -f alaw http://192.168.1.10/audio.g711a
Using sox program convert any source audio file to PCM 8kbps audio:
sox speech.mp3 -t raw -r 8000 -e signed -b 16 -c 1 test.pcm
curl -u root:12345 --data-binary @test.pcm http://192.168.1.10/play_audio