mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
Videos are not saved, neither with motion detection nor normal recording #2390
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#2390
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @backupandforkacc on GitHub (May 12, 2023).
The settings seem ok. I can see the stream online, but no video is saved. Neither in the file on the filesystem nor through the explorer in the frontend of motioneye I can see any recorded videos. I can see the pictures when setting to normal recording, but not with motion detection. The motion detection also triggers, at least I get messages via telegram.
camera-1.conf.txt
motion.conf.txt
motioneye.conf.txt
@MarcelCoding commented on GitHub (May 13, 2023):
I can confirm, since I switched to the
edgedocker tag (a month ago), videos aren't getting saved anymore.@MichaIng commented on GitHub (May 13, 2023):
Thanks for reporting. Is the container reporting any errors messages? I think with plain motionEye installed via
pipit works 🤔.@backupandforkacc commented on GitHub (May 13, 2023):
Sorry, I now indeed have some error, which I have not detected yesterday:
/var/log/motioneye/motion.log shows
Also ffmpeg seems to be ok
@backupandforkacc commented on GitHub (May 14, 2023):
I just installed from scratch as explained here
and still get the error:
@MarcelCoding commented on GitHub (May 15, 2023):
Switching the codec from OMX to V4L made the message in the motion log diapering.
I'll keep you updated if videos are being reported again.
@MichaIng commented on GitHub (May 18, 2023):
Ah that makes perfectly sense. Since Bullseye, on RPi by default the KMS video driver is used, which does not support OpenMAX. We need to change the default at best, also because OpenMAX really is an RPi thing only and now even deprecated.
@MarcelCoding commented on GitHub (May 18, 2023):
Today I got it working using mp4 without omx.