mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
motioneye not updating v4l2 camera size & fps. #2504
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#2504
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 @adminy on GitHub (Mar 10, 2024).
I tried rpicam-vid, everything works, can record in any camera supported resolution. Does not work in motioneye ui though ... same camera selected!
Looks like motioneye is sending only the desired camera size but its not actually doing a
v4l2-ctl -vparameter setting command.@zagrim commented on GitHub (Mar 22, 2024):
Is this Pi camera 3? That requires libcamera support which is still somewhat open question for MotionEye. Motion requires using libcamerify in order to deal with those cameras, but integrating that to ME is still in progress. There have been some proposed workarounds, but some people have had issues with any of them. However, if you are feeling adventurous, see #2425 and the linked issues.
@adminy commented on GitHub (Mar 24, 2024):
I just got a defective camera it seems.