Since the latest BI update I tried to use the H.265 on the 2 starlight cams I have. By just switching those 2 cams it bumps up my cpu 7-10 % This is in a 13 cam system all running D2D and usually pretty steady in the 25-30% range. This morning I just happened to notice it was running around 38% with really no motion going on. I rebooted and dbl checked something else wasn't causing the issue, but same result.
I then changed back the 2 cams that I switched to h.265 back to h.264 and bingo, went right back down to 25-30%. I was getting great results as far as file size and quality of the clips, but this cpu spike is kind of a deal breaker for now on the h.265.
I was just curious if anyone else can see this on their setup.
Support data:
Version: Release 4.5.6.2 x64
OS: Windows 10 Pro
CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz [26%]
RAM: 1.21G
I then changed back the 2 cams that I switched to h.265 back to h.264 and bingo, went right back down to 25-30%. I was getting great results as far as file size and quality of the clips, but this cpu spike is kind of a deal breaker for now on the h.265.
I was just curious if anyone else can see this on their setup.
Support data:
Version: Release 4.5.6.2 x64
OS: Windows 10 Pro
CPU: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz [26%]
RAM: 1.21G