Best Practice for linked channels from Android IP-webcam app?
Posted: Sun Jan 05, 2020 10:27 am
Can we share experience about optimizing the setup of android devices as cams?
My goal is sth like e.g.
960 x 720 x 5 fps H.264 video stream for detection and permanent record
2560 x 1920 snapshots every 10s in alarm case from http://192.168.1.28:8080/photo.jpg
I plan to install a large number (10..20) of cams on my farm premises, so I have to keep resource use per cam to a minimum.
But large area => long distance => need good resolution to get details - in tradeoff for speed
I'm testing with IP Webcam by Pavel Khlebovich from Google playstore,
running on Samsung Galaxy Xcover 2 GT-S7710
After a night of fiddling, this is basically working: "Cam foo bar" ans "szinocam" are dedicated IP-cams just to provide some test envirnonment and background system load
The last two monitors are from the android:
"ip-cam test" is source type ffmpeg from rtsp://192.168.1.28:8080/h264_ulaw.sdp
frame rate is set at 3 fps in the android app.
Storage JPEG disabled, Video writer: X264 Encode
"ip-cam image" is source type Remote from http://192.168.1.28:8080/photo.jpg
It is linked to "ip-cam test".
All FPS fields (Analysis, Maximum, Alarm Maximum) are set to 0.10 .
Storage is JPEG frames only, Video writer disabled.
Warmup frame, Pre Event Images, Post Event Images are all 0,
Alarm frame count is 1
(btw: is there a conscise way to list monitor configs - preferrably as plain text?)
It basically works, but with quite some quirks.
Details will come in seperate posts.
System details:
debian buster (10.2)
2:1.32.3-dmo4+deb10u2
Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
8 GB RAM
tmpfs 4019312 1555272 2464040 39% /dev/shm
My goal is sth like e.g.
960 x 720 x 5 fps H.264 video stream for detection and permanent record
2560 x 1920 snapshots every 10s in alarm case from http://192.168.1.28:8080/photo.jpg
I plan to install a large number (10..20) of cams on my farm premises, so I have to keep resource use per cam to a minimum.
But large area => long distance => need good resolution to get details - in tradeoff for speed
I'm testing with IP Webcam by Pavel Khlebovich from Google playstore,
running on Samsung Galaxy Xcover 2 GT-S7710
After a night of fiddling, this is basically working: "Cam foo bar" ans "szinocam" are dedicated IP-cams just to provide some test envirnonment and background system load
The last two monitors are from the android:
"ip-cam test" is source type ffmpeg from rtsp://192.168.1.28:8080/h264_ulaw.sdp
frame rate is set at 3 fps in the android app.
Storage JPEG disabled, Video writer: X264 Encode
"ip-cam image" is source type Remote from http://192.168.1.28:8080/photo.jpg
It is linked to "ip-cam test".
All FPS fields (Analysis, Maximum, Alarm Maximum) are set to 0.10 .
Storage is JPEG frames only, Video writer disabled.
Warmup frame, Pre Event Images, Post Event Images are all 0,
Alarm frame count is 1
(btw: is there a conscise way to list monitor configs - preferrably as plain text?)
It basically works, but with quite some quirks.
Details will come in seperate posts.
System details:
debian buster (10.2)
2:1.32.3-dmo4+deb10u2
Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
8 GB RAM
tmpfs 4019312 1555272 2464040 39% /dev/shm