motioneye icon indicating copy to clipboard operation
motioneye copied to clipboard

Cameras not recording

Open rcho5840 opened this issue 1 year ago • 5 comments

I have tried to use motion detection recording and although I see the red outline, there are no videos that are saved. Now, keep in mind that I do not have a flash drive in. My motioneye is setup on a raspberry pi with a microsd card. I also have a flashdrive with a custom path set to the flash drive storage image image

The second issue I noticed was that even with the continuous recording, there is no red outline. I believe this means that it's just not recording in general.

Screenshot 2024-07-01 110953

rcho5840 avatar Jul 01 '24 15:07 rcho5840

@rcho5840 change movies to this

config

change the codec, that was my problem, default didnt work

Martypose avatar Jul 08 '24 14:07 Martypose

@Martypose yup one of the issues was the codec. It seems for my camera, it only wants to use mpeg,

rcho5840 avatar Jul 08 '24 17:07 rcho5840

Recording mode "Continuous recording" should mean just what it says, and it actually does the same as adding emulate_motion on in Extra Motion Options. And it should show the red outline.

Could you @rcho5840 please post the logs (sudo journalctl -u motion) so we can see if there are some underlying issues with your config?

Please also clarify this part:

Now, keep in mind that I do not have a flash drive in. My motioneye is setup on a raspberry pi with a microsd card. I also have a flashdrive with a custom path set to the flash drive storage

Do you mean that you have not connected the flash drive, but you still have the flash drive path set in "File storage" > "Root directory"? That would obviously not work, but maybe I read your words wrong :smiley:

zagrim avatar Jul 22 '24 04:07 zagrim

I also noticed that you'd opened #3025 and I wonder if that was resolved and if these two issues are actually related?

zagrim avatar Jul 22 '24 04:07 zagrim

I came here to raise that OMX doesn't work too.. I got errors from motion saying it couldn't set the codec but ffmpeg does seem to have OMX compiled in:

Results of journalctl -u motioneye:

Dec 04 08:46:35 Camera4 motion[16186]: [1:ml1:Camera4] [ERR] [ENC] ffmpeg_set_codec: Could not open codec Encoder not found
Dec 04 08:46:35 Camera4 motion[16186]: [1:ml1:Camera4] [ERR] [ENC] ffmpeg_open: Failed to allocate codec!
Dec 04 08:46:35 Camera4 motion[16186]: [1:ml1:Camera4] [ERR] [EVT] event_ffmpeg_newfile: Error opening context for movie output.
Dec 04 15:19:40 Camera4 motion[16186]: [1:ml1:Camera4] [ERR] [ENC] ffmpeg_set_codec: Could not open codec Encoder not found
Dec 04 15:19:40 Camera4 motion[16186]: [1:ml1:Camera4] [ERR] [ENC] ffmpeg_open: Failed to allocate codec!
Dec 04 15:19:40 Camera4 motion[16186]: [1:ml1:Camera4] [ERR] [EVT] event_ffmpeg_newfile: Error opening context for movie output.

https://stackoverflow.com/a/66824573 suggests *_v4l2m2m is a suitable alternative to achieve the same aim anyway.. given MMAL is deprecated in Buster+.

Matthew1471 avatar Dec 04 '24 21:12 Matthew1471