Yesterday, 01:04 PM
DVB-T use MPEG-2 or h.264
DVB-T2 use h.264 or h.265.
The problem is that raspberry pi 5 has only h.265 hardware decoder, in this version of the raspberry they had the brillant idea to drop h.264 hardware decoder and encoder and not include an h.265 encoder.
So in the best case scenario (DVB-T2 using h.265) raspberry pi 5 hardware decode the h.265 video stream and you pass it directly untouched as h.265 without hitting the CPU.
Medium case scenario (DVB-T2 using h.265) raspberry pi 5 hardware decode the h.265 and has to use the CPU to encode in h.264.
In the worst case (DVB-T using MPEG-2 or h.264 or DVB-T2 using h.264) raspberry pi 5 CPU decode the MPEG-2/h.264 video stream and has to use the CPU to encode in h.264 or h.265.
So there is nothing you can do with your hardware to avoid CPU usage.
DVB-T2 use h.264 or h.265.
The problem is that raspberry pi 5 has only h.265 hardware decoder, in this version of the raspberry they had the brillant idea to drop h.264 hardware decoder and encoder and not include an h.265 encoder.
So in the best case scenario (DVB-T2 using h.265) raspberry pi 5 hardware decode the h.265 video stream and you pass it directly untouched as h.265 without hitting the CPU.
Medium case scenario (DVB-T2 using h.265) raspberry pi 5 hardware decode the h.265 and has to use the CPU to encode in h.264.
In the worst case (DVB-T using MPEG-2 or h.264 or DVB-T2 using h.264) raspberry pi 5 CPU decode the MPEG-2/h.264 video stream and has to use the CPU to encode in h.264 or h.265.
So there is nothing you can do with your hardware to avoid CPU usage.