Martijn Braam
martijnbraam@fosstodon.org
Aaahg I made the mistake to buy hardware that requires libcamera, and of course it doesn't fucking work.
2
0
0
Martijn Braam
martijnbraam@fosstodon.orgI mean... this is all supported hardware from raspberry pi...
1
0
0
Martijn Braam
martijnbraam@fosstodon.orgI just want to make this an ip camera and somehow even when I get the most popular hardware I have to invent everything myself :<
1
0
0
@martijnbraam Hey, there's someone else who invented everything :>
Hint hint.
More seriously, which module and Pi is that?
I have bought Module 2.0 and a Pi, uh, 4 B I think. Fighting #libobscura to make configurations like these work right now.
1
0
0
@martijnbraam Thanks. Judging by the IPA error, it's probably something about the processing arcitecture in the SoC, so once/if I get there, I should be able to support it.
0
0
0
Unfortunately what you're trying to do there is not needed. libcamerify and the libcamera v4l2-adaption layers are (best effort) implementations to support applications expecting to work with simple cameras, like UVC. Those applications (think of cheese in example) poke at /dev/video0 without knowing anything about the media topology or ISP algorithms. libcamerify ld-preloads the libcamera v4l2-adaption layer to intercept calls to the V4L2 kernel interface, emulating a legacy system while libcamera does the pipeline configuration and ISP algorithms heavy lifting in the background for you.
You can run v4l2-ctl without any library preloading. Utilities from v4l2-utils use the V4L2/MC kernel API and allows you to inspect and configure the single video devices and subdevices in the system. They don't need libcamera to do that.
The libcamera community would be very happy to support you if you want to join our irc channel and the raspberry forums are a precious resource full of interesting content for people getting started with their cameras.
Thanks, all the best and happy hacking!
1
0
1
Martijn Braam
martijnbraam@fosstodon.org@jmondi my end goal obviously isn't running v4l-ctl, it just shows me whatever is going on with the wrapper thing and it the issue was the error from libcamera. Not sure what caused it, something deeply wrong in dietpi apparently as it works in raspbian.
1
0
0
I read you got mediamtx working out of the box. I didn't know about that project but reading its dependencies on pi I'm just glad that libcamera is proving helpful to you there.
https://github.com/bluenviron/mediamtx?tab=readme-ov-file#raspberry-pi-cameras
All the best
0
0
0