motioneye-project/motioneye

Timing/sync on one camera

Open

#2,164 opened on Jul 27, 2021

View on GitHub
 (13 comments) (0 reactions) (0 assignees)Python (636 forks)batch import
help wantedquestiontroubleshooting

Repository metrics

Stars
 (3,533 stars)
PR merge metrics
 (Avg merge 16d 14h) (33 merged PRs in 30d)

Description

Hi, I'm runnning motioneye 0.42.1 on a raspberry pi 3 model B plus rev 1.3 (with raspbian 10) and am having issues with 1 out of my two cameras. One camera is completely fine but the second one is running at a reduced speed. What I mean by this is that the camera's on screen text showing the time starts out the same as the motioneye time overlay but over time becomes further and further behind. It's very strange as it's not conventional lag where it's always x seconds behind, it actually gets worse the longer it runs for. This camera is a higher definition than the first but I've tried dropping all the quality settings, FPS and resolution but none of these have any impact. I would have thought the 3 B plus could handle two cameras at 720p..

Any ideas?

Thanks, Josh

Contributor guide

Research direction
Trace the code path for generating the time overlay on the affected camera and compare with the system clock to identify where the drift originates.
Tech stack
python
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55