starred/motioneye

Fork 0

mirror of https://github.com/motioneye-project/motioneye.git synced 2026-03-02 22:57:06 -05:00

Multiple Motion Threads #2052

New issue

Open

opened 2026-02-28 01:02:13 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 01:02:13 -05:00

Owner

Originally created by @dbeckwith01 on GitHub (Oct 17, 2021).

I am evaluating MotionEye to use to monitor multiple IP video cameras around my home. I hoping to run this on my RPI 4B+. I have successfully got MotionEye setup with one RTSP camera but I noticed it's using ~40% of the CPU. Running htop shows a large number of motion process which seem to run across multiple cores. I was hoping that MotionEye would set motion up to use the RPi's hardware encoding.

It is possible to get MotionEye to use the RPI hardware encoder?

Originally created by @dbeckwith01 on GitHub (Oct 17, 2021). I am evaluating MotionEye to use to monitor multiple IP video cameras around my home. I hoping to run this on my RPI 4B+. I have successfully got MotionEye setup with one RTSP camera but I noticed it's using ~40% of the CPU. Running htop shows a large number of motion process which seem to run across multiple cores. I was hoping that MotionEye would set motion up to use the RPi's hardware encoding. It is possible to get MotionEye to use the RPI hardware encoder? <img width="1353" alt="image" src="https://user-images.githubusercontent.com/18648394/137649264-697bad56-b980-42a1-b359-d667b9e24041.png">

deekerman added the

question

Stale No Activity 60 Days

motion

labels

2026-02-28 01:02:13 -05:00

deekerman commented

2026-02-28 01:02:16 -05:00

Author

Owner

@starbasessd commented on GitHub (Oct 17, 2021):

The GPU encoder is used for encoding / decoding the video, not for motion detection. There was a recent issue discovered where when installing motionEye specifically motion motion daemon gets installed and auto starts. If you disable it:
sudo systemctl stop motion
sudo systemctl disable motion
and restart the Pi, it will still use motion, but motionEye will control it as it should.

@starbasessd commented on GitHub (Oct 17, 2021): The GPU encoder is used for encoding / decoding the video, not for motion detection. There was a recent issue discovered where when installing motionEye \(specifically motion\) motion daemon gets installed and auto starts. If you disable it: sudo systemctl stop motion sudo systemctl disable motion and restart the Pi, it will still use motion, but motionEye will control it as it should.

deekerman commented

2026-02-28 01:02:19 -05:00

Author

Owner

@dbeckwith01 commented on GitHub (Oct 17, 2021):

@starbasessd,

Thank you for the quick reply!

Currently I'm not running MotionEye with the Motion settings. I'm just testing streaming and recording. I'm running Motion in Docker at the moment on Balena OS.

I'm using MotionEye 0.42.1 and Motion 4.3.2.

@dbeckwith01 commented on GitHub (Oct 17, 2021): @starbasessd, Thank you for the quick reply! Currently I'm not running MotionEye with the Motion settings. I'm just testing streaming and recording. I'm running Motion in Docker at the moment on Balena OS. I'm using MotionEye 0.42.1 and Motion 4.3.2. <img width="680" alt="image" src="https://user-images.githubusercontent.com/18648394/137653983-28e53130-60ad-4c93-bbc2-05c8d781fc02.png">

deekerman commented

2026-02-28 01:02:19 -05:00

Author

Owner

@starbasessd commented on GitHub (Oct 18, 2021):

Motion daemon is still turned 'on' unless you turn it off and disable it as shown above.
Motion daemon doesn't need to be 'enabled' to be used by motionEye.
If you want to use the GPU encoder, you would want to use an OMX enabled format.
If you want best performance, I would use Pass Through, but then you won't get
video name or time stamp, but you still can get motion detection trigger.

@starbasessd commented on GitHub (Oct 18, 2021): Motion daemon is still turned 'on' unless you turn it off and disable it as shown above. Motion daemon doesn't need to be 'enabled' to be used by motionEye. If you want to use the GPU encoder, you would want to use an OMX enabled format. If you want best performance, I would use Pass Through, but then you won't get video name or time stamp, but you still can get motion detection trigger.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/motioneye#2052

No description provided.

Rows
Columns