1 3/7/2018 12:04:26 PM road2 HW VA not compatible: -3
I agree-- at least on an i7 7700k, I switched all my cameras to h.264, turned on hardware acceleration, and made sure in gpu-z that the intel 630 was being utilized (it was -- being used 70% when BI was running, and only when BI was running). my CPU usage for BI is around 40-45%Just to add to this discussion. I have noticed that the benefits of H.265 (no HW Decode) vs H.264 (HW Decode), such as smaller video clip sizes, far out weigh the lack of HW decoding at the moment. Assuming your CPU usage is decent (within tolerable range), I would suggest running your cameras at H.265 with BI for the time being until they can figure out the HW decode issues.
Is there any point or negative impact, assuming it records anyway, to setting cameras to 265, will it cause BI/PC to work harder or will it auto adjust recording to 264?To my knowledge, the only way to do H.265 hardware acceleration in BI is to use an Nvidia graphics card, but that is super inefficient so not usually a good investment.
Of course there is a difference. A significant one. You can't test a function that doesn't work.Using h.265 without hw acceleration works great. On newer CPUs there is no noticeable difference in utilization in my tests. The benefit of h.265 is smaller file sizes and decreased bandwidth consumption which really helps with wifi cameras.
Even if the h.265 required the same cpu usage as 264, you would still see a difference between ha and no ha.It could be possible if the cameras dont use features of h265 that require significantly more cpu to decode I suppose. My own experiments show little quality difference from h264 to h265 at a given bit rate, on my cams. Many of mine still dont support h265 so I havent been able to do a proper cpu usage test.