You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to figure out where my recordings are stored.
docker-compose.yml
version: "2.4"
services:
viseron:
image: roflcoopter/viseron:latest
container_name: viseron
volumes:
- /data/media/visreon/recordings:/recordings
- /home/blud/docker/viseron/config:/config
- /etc/localtime:/etc/localtime:ro
ports:
- 8888:8888
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
environment:
- PUID=1000
- PGID=1000
blud@andromeda:~/docker/viseron$ ls -l /data/media/viseron
ls: cannot access '/data/media/viseron': No such file or directory
config.yml
## Start by adding some cameras
ffmpeg:
camera:
camera_1: # This value has to be unique across all cameras
name: deck
host: 10.0.1.180
port: 554
path: /cam/realmonitor?channel=1&subtype=0
username: viewer
password: xx
camera_2: # This value has to be unique across all cameras
name: driveway
host: 10.0.1.181
port: 554
path: /cam/realmonitor?channel=1&subtype=0
username: viewer
password: xx
## Then add an object detector
darknet:
object_detector:
cameras:
camera_1: # Attach detector to the configured camera_1 above
fps: 1
scan_on_motion_only: false # Scan for objects even when there is no motion
labels:
- label: person
confidence: 0.75
trigger_recorder: true
camera_2: # Attach detector to the configured camera_2 above
fps: 1
labels:
- label: person
confidence: 0.75
trigger_recorder: true
## You can also use motion detection
mog2:
motion_detector:
cameras:
camera_2: # Attach detector to the configured camera_2 above
fps: 1
## To tie everything together we need to configure one more component.
nvr:
camera_1: # Run NVR for camera_1
camera_2: # Run NVR for camera_2
Recording list
The text was updated successfully, but these errors were encountered:
Trying to figure out where my recordings are stored.
docker-compose.yml
config.yml
Recording list
The text was updated successfully, but these errors were encountered: