Hi, I’m trying to record videos with my Arducam 64MP camera at a resolution of 2312x1736, but every time I launch libcamera it just crashes. I’ve attached screenshots of the error messages.
Funny thing is, the camera works fine when I record at lower resolutions (second screenshot shows that working), but what I actually need is the uncropped video, so those don’t really help me.
I read on a few forums that the newest libcamera-apps version (0.0.10) is supposed to have fixed this issue, but for me it hasn’t fixed anything at all. Still crashes on 2312x1736.
Has anyone else hit this? Any idea what I’m doing wrong?
Hi, thanks for the detailed report and the screenshots.
Let’s start with your environment so I can narrow this down:
Can you confirm which version of libcamera-apps you currently have installed? You mentioned 0.0.10 — is that the version actually being invoked when you run it?
What OS image are you on (Bullseye, Bookworm, etc.) and are you running 32-bit or 64-bit?
Can you paste the exact command you’re using to record at 2312x1736, plus the full console output/error it prints before crashing?
The screenshots help, but a copy/paste of the terminal text would let me see the exact error line.
Version is 0.0.10, yes — I checked with libcamera-vid --version and it reports 0.0.10.
I’ve tried several OS configurations at this point and all of them give me the same problem. I don’t remember every combination off the top of my head but it was a few different installs, same result every time. So it doesn’t seem to be tied to a specific OS setup.
The crash message is exactly what’s in the screenshots I attached — I don’t have a clean text copy right now but the images show it. Basically libcamera dies the moment I try to launch it at 2312x1736.
OK that’s helpful. If it happens across multiple OS configs, that points away from a broken install and more toward something in the pipeline itself.
A couple of things I want to verify:
What exact libcamera-vid command are you running? Something like libcamera-vid --width 2312 --height 1736 -t 10000 -o test.h264? Or are you setting the resolution some other way?
Are you using the Arducam 64MP overlay/driver (the one that gives you the full-resolution modes), or are you running it with the default camera stack?
Does it crash immediately at launch, before it even starts recording?
Also, when you say lower resolutions work — can you confirm which resolutions you tested that were fine?
I’m using the Arducam overlay so I can get the full sensor modes. It crashes right at launch — I don’t even get to the point where it starts recording. Just the error and it dies.
For lower resolutions I tried the usual ones like 1920x1080 and below and those record fine, no crash. It’s specifically the 2312x1736 that kills it.
That actually matches a known limitation I was suspecting.
Here’s what’s going on: the 2312x1736 mode exists on the sensor side, and the capture itself can be configured for it. The part that fails is the encoding stage. The Raspberry Pi’s hardware video encoder is capped at 1080p — that’s a hardware limit of the Pi itself, not something that can be patched in libcamera or libcamera-apps.
So when you ask it to encode 2312x1736, the encoder can’t handle it, and the whole libcamera process falls over at launch instead of gracefully erroring out. That’s why lower resolutions like 1080p and below work fine — those are within the encoder’s supported range.
This also explains why bumping to libcamera-apps 0.0.10 didn’t help you, even though people said it fixed the issue. The fix in 0.0.10 was for something else — it doesn’t raise the hardware encoder’s ceiling. And it lines up with your testing: several different OS configurations, same crash every time, because the limitation lives in the Pi’s encoder hardware, which is the same regardless of which OS you install.
Hmm, that’s disappointing but it does make sense given that every OS setup failed the same way.
So there’s really no way to get the uncropped 2312x1736 video out of this? Is there any setting I can flip, or any mode where libcamera would just capture full resolution without going through the hardware encoder?
I understand the frustration. To be straight with you: no, there isn’t a configuration that gets you 2312x1736 encoded video on this hardware.
The encoder ceiling is at 1080p — that’s the maximum resolution the Raspberry Pi can reach for encoding. Anything above that, including 2312x1736, simply cannot be encoded. So the uncropped full-resolution video recording you’re after isn’t achievable through the normal libcamera recording path on this board.
Lower resolutions within 1080p will keep working, and those are fine because they stay under the encoder’s limit. But that won’t give you the uncropped output you wanted.
So the short version: this is an inherent limitation of the Raspberry Pi hardware encoding capability, not a bug in your setup, your OS, or your libcamera-apps version.
OK, so just to be sure I’m understanding — the sensor can do 2312x1736, libcamera can capture it, but the encoder can’t, so no video file at that resolution. Is that right? And there’s genuinely no workaround at all?
Sensor: supports 2312x1736, that’s not the problem.
Capture: libcamera can be configured for that resolution.
Encode: this is where it breaks. The Raspberry Pi hardware encoder maxes out at 1080p, so 2312x1736 can’t be encoded, and that’s what causes the crash at launch.
And no, there’s no workaround that produces the uncropped 2312x1736 video on this hardware. The limitation is inherent to the Pi’s hardware encoding capability, so anything above 1080p for encoding is out of reach regardless of OS, driver overlay, or libcamera-apps version.
If you need higher-than-1080p video, that would have to happen on a platform whose encoder supports it. On this board, the practical ceiling stays at 1080p.