5.2.2 - March 20, 2020 Intel hardware H.265 decodingand H.264 encoding

Tinbum

Getting the hang of it
Joined
Sep 5, 2017
Messages
222
Reaction score
36
Location
UK
I have had to go into every camera and reset the hardware accelerated decode as they had all reset to 'NO'

My H265 cameras work on Nvidia, as before, but if I set to Intel they don't. If I set them to New Intel they work, but when I go into settings they have reset to 'NO'

My GPU 0 is showing it's working now.
 

Skinny1

Getting the hang of it
Joined
Jul 10, 2016
Messages
100
Reaction score
10
Mine is doing the samething. Waiting up on the next update.
 

rocky500

n3wb
Joined
Jun 24, 2019
Messages
21
Reaction score
9
Location
Australia
Just downloaded the update again and it is now v5.2.2.2 dated 23/3/20
Can now set all cameras to Intel Acceleration except one which defaults to off for some reason.
With v5.2.2.0 all would default to off. Have 5 cameras.
 

beepsilver

Getting comfortable
Joined
Mar 9, 2014
Messages
556
Reaction score
256
Location
Nebraska
Just downloaded the update again and it is now v5.2.2.2 dated 23/3/20
Can now set all cameras to Intel Acceleration except one which defaults to off for some reason.
With v5.2.2.0 all would default to off. Have 5 cameras.
What brand of cameras work/don't work please?
 

rocky500

n3wb
Joined
Jun 24, 2019
Messages
21
Reaction score
9
Location
Australia
What brand of cameras work/don't work please?
Working cameras - Dahua 4 MP OEM - IPC-T5442TM-AS,
2x IPC-T2231T-ZS 2MP Starlight WDR IR Eyeball IP Camera Motorized vari-focal 2.7mm–13.5mm
Dahua 2MP DH-SD42212T-HN (S2) PTZ

Non Working one only
IPC-B5442E-ZE 4MP WDR IR Bullet AI Network Camera

Windows 10 onboard Intel HD4600 video. Driver 20.19.15.5063
 

bp2008

Staff member
Joined
Mar 10, 2014
Messages
9,560
Reaction score
6,977
Location
USA
I tried the new BETA Intel option for decoding an H.265 cam (Dahua 5231 starlight) but it didn't work at all, logged HW VA not compatible: -22, and reverted to no hardware acceleration on that camera. The old regular Intel option still just decodes one frame and then freezes.

I also tried the BETA Intel option for encoding for the web server, but it just fails instantly every time with HW encode Setup failed: -22 for 'streaming temp 10660955872' and then falls back to regular software encoding so quickly you wouldn't know it had failed except that it logs the error and CPU/GPU utilization is unchanged from normal software encoding.
 

hex52

n3wb
Joined
Apr 18, 2018
Messages
22
Reaction score
22
Tested Intel BETA with IPC-HDW5831R-ZE H.265 and got HW VA not compatible: -12, but it is still streaming and recording... I don't think I was ever able to keep H.265 on the camera.
 

fenderman

Staff member
Joined
Mar 9, 2014
Messages
32,201
Reaction score
11,275
Tested Intel BETA with IPC-HDW5831R-ZE H.265 and got HW VA not compatible: -12, but it is still streaming and recording... I don't think I was ever able to keep H.265 on the camera.
Do you have a 6th gen+ processor?
 

hex52

n3wb
Joined
Apr 18, 2018
Messages
22
Reaction score
22
I suspect HW encoding is not working since my CPU usage is in the upper 30s when it's normally around 20%. But I tried H.265 on 2 cameras and they're both recording fine. That is a step forward!
 

fenderman

Staff member
Joined
Mar 9, 2014
Messages
32,201
Reaction score
11,275
I suspect HW encoding is not working since my CPU usage is in the upper 30s when it's normally around 20%. But I tried H.265 on 2 cameras and they're both recording fine. That is a step forward!
What does taskmanager report for GPU usage? You may have higher cpu usage even if HA was properly working as h265 uses more processing power overall.
 

hex52

n3wb
Joined
Apr 18, 2018
Messages
22
Reaction score
22
I switched everything back to H.264 and it's 45% 1.9/15.8GB

Changed one of the cameras to H.265. There was an I/O error because my default HW accelerated decode is Intel.

Switched to Intel BETA, it automatically changed Hardware accelerated decode to No, but continued to stream.

Checked task manager GPU is at 42% 1.5/15.8GB
 

hex52

n3wb
Joined
Apr 18, 2018
Messages
22
Reaction score
22
Changed the same second camera to H.265, but GPU is now 34-37% and CPU 23-30%

That's quite different from my initial test with the same 2 cameras. Not sure what this means except it fluctuates
 

fenderman

Staff member
Joined
Mar 9, 2014
Messages
32,201
Reaction score
11,275
The release notes have been updated for 5.2.2.4
Video components were updated and the Intel hardware decoding interface was redesigned
and recoded in an attempt to bring some missing features online such as H.265 decoding
and H.264 encoding. The 64-bit version is required for all hardware acceleration, and you
may need to now update your Nvidia drivers if you were using this. New hardware
decoding options include DXVA2 and D3D11VA, but these may still be in “beta.”
 

Tinbum

Getting the hang of it
Joined
Sep 5, 2017
Messages
222
Reaction score
36
Location
UK
5.2.2.4 H.265 seems to be working on my cameras with setting - Intel

Switching 3 of my cameras that are normally on Nvidia to DXVA2 increased the Nvidia GPU from about 3% to 8%
 
Last edited:

hex52

n3wb
Joined
Apr 18, 2018
Messages
22
Reaction score
22
Testing 5.2.2.4 with 8x IPC-HDW5831R-ZE (H.265) and 3x IPC-K35S (H.264)

D3D11VA is working for the 8x H.265 -- or at least there are no " HW VA not compatible" errors

CPU usage went from 20-25% to 45-50%
GPU from 35% to 6% utilization and 1.5 to 0.5GB memory

Doesn't this mean HW acceleration is NOT working?

Edit: I changed it from D3D11VA to Intel and everything above is pretty much the same
 
Last edited:

bp2008

Staff member
Joined
Mar 10, 2014
Messages
9,560
Reaction score
6,977
Location
USA
I've tested my Dahua 5231 against BI 5.2.2.5 just now, using all types of hardware acceleration presented in the dropdown in camera properties > Video. I tested each with both H.264 and H.265.

The good news is, whenever Blue Iris failed to decode with HWVA, it fell back automatically to software decoding and it did not revert the HW VA setting to "No". The bad news is, it only logged some of the failures, and just fell back to software decoding silently (this I determined by watching CPU/GPU usage).

My conclusion is that none of the new HW VA methods are working and we basically have the same working options as a year ago.


HW VAH.264 ResultH.265 Result
NoSoftware decodingSoftware decoding
IntelAcceleration worksSoftware decoding
Intel + VPPAcceleration works, CPU/GPU usage identical to "Intel" mode.Software decoding
NvidiaAcceleration worksAcceleration works
DXVA2Software decodingSoftware decoding
D3D11VASoftware decodingSoftware decoding


It may not be entirely as simple as that. For example when decoding H.265 with "Intel" selected, I did see a tiny amount of extra Video Decode usage reported for the Intel GPU. But CPU usage was not measurably reduced, and the GPU Video Decode usage increase (1-2%) was not enough to suggest that HW VA was actually working (6-7% when it was actually working).
 
Top