I know what I am doing is mostly outside use case, but I work with what I have. I recently acquired a reolink camera, RLC-822A. I have it up and running great with frigate, except for the viewing of recordings, which are h.265. Every computer in my house is either too old or runs Linux. Viewing recordings on my iphone works great, but was looking for a way to have a permanent viewer, almost like a kiosk.
Using a raspberry pi 4 8gb with Raspi OS I was able to get a version of chromium to stream the h.265 recordings. Works ok, the pi can run for about 18 hours before artifacts start to happen and I have to reboot.
I have a Dell tower with dual xeon silver 4114, 192gb of ram and a quadro p2000. I am passing through the p2000 to frigate on an Ubuntu VM. I want to use this VM and pass through p2000 to run the frigate kiosk. For some reason, even though the hardware supports it, I am unable to get h.265 streaming to work on this VM.
How is it that an ARM based SBC running a version of Debian can decode and play h.265 and an over powered VM with hardware that is known to support that codec can not? Is it an issue with passthrough and decoding? I have nvidia container toolkit, and the p2000 works great with frigate in a docker container. I can watch h.265 through vlc and other apps, but can not get chromium hardware acceleration to work. Any ideas?
Raspi OS has a customized version of chromium in order to maximize the use of its hardware acceleration since the CPU is on the slow side. Probably you need to force-enable hardware decoding on the chromium inside the VM. If that doesn’t work you may need to compile it from scratch or use Firefox instead.
I would rather use firefox, but have not been able to make it work. Hearing yet another person mention it makes me want to give it another shot.