5 ms·
> Raspberry Pi 5 [...] do not support v4l2 hardware encoding I'm not sure I get the point of that... they go through the effort for video decoding, but why do
by nubinetwork 2y ago
> Raspberry Pi 5 [...] do not support v4l2 hardware encoding
I'm not sure I get the point of that... they go through the effort for video decoding, but why doesn't it have an encoder?
- bmh 2y agoThey decided to use the silicon space for other things. The Pi5 CPU is powerful enough to decode most h264 streams in software. The Pi5 has an h265 hardware decoder.
- hcfman 2y agoShame. Cause h265 is problematic wrt licensing etc. I would have preferred that they kick out h265 and used the silicon for h264. And maybe the pi5 has enough cpu to do the decoding. But how much would be left over for more interesting AI tasks ?
- bmh 2y agoI agree 100%
- moffkalast 2y agoWell it's not fast enough for most AI tasks as it is, you'd need to offload that bit to a pcie accelerator.
- hcfman 2y agoNot true actually. If by offloading you mean to a device that uses a really small model with 8-bit quantized weights you are not actually solving anything.
- knowitnone 2y agosure it's powerful enough but I'd rather it built into the hardware for energy efficiency. But I guess we can't have our cake.
- Sean-Der 2y agoMy assumption is the amount of people encoding is much smaller then decoding. overlap exist in encode/decode. When working on a Opus codec I did have a fair amount of code distinct to one path still.