4.6.9 - January 31, 2018 H.265 hardware decoding added

Discussion in 'What's New' started by fenderman, Jan 31, 2018.

Share This Page

  1. HankRearden

    HankRearden n3wb

    Joined:
    Nov 16, 2017
    Messages:
    5
    Likes Received:
    2
    Is HW decoding of h.265 working yet?
     
  2. giel

    giel n3wb

    Joined:
    Nov 25, 2017
    Messages:
    24
    Likes Received:
    11
    No.
     
  3. bp2008

    bp2008 Staff Member

    Joined:
    Mar 10, 2014
    Messages:
    8,435
    Likes Received:
    5,394
    Last week I emailed support saying that I didn't know of anyone who had H.265 acceleration working yet, and wondered what was going on with that. Ken got back to me yesterday and it turns out he hasn't been able to test it himself yet because the hardware he tried it on returns a "not implemented" message. Apparently he was testing on a NUC and it might be unclear if the CPU in there supports H.265 hardware acceleration. He wasn't very specific.

    As a software developer myself, I'd say there is a pretty good chance he'll need to buy new hardware to debug on before the error can be tracked down.
     
    fenderman likes this.
  4. bp2008

    bp2008 Staff Member

    Joined:
    Mar 10, 2014
    Messages:
    8,435
    Likes Received:
    5,394
    Note the 4.7.1.0 patch added this line to the change log as a result of my feedback:
    • Incompatible HW decoding will now be caught and logged, and the setting automatically reset to No.
     
  5. aj2600

    aj2600 n3wb

    Joined:
    Jan 31, 2018
    Messages:
    9
    Likes Received:
    4
    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.
     
  6. bp2008

    bp2008 Staff Member

    Joined:
    Mar 10, 2014
    Messages:
    8,435
    Likes Received:
    5,394
    I am indeed getting this message logged when I enable H.265 on one of my Dahua Starlight cams:

    Code:
    1  3/7/2018 12:04:26 PM   road2                HW VA not compatible: -3
    Blue Iris 4.7.1 automatically sets the hardware acceleration for this camera to "No" when that happens.

    Interestingly, the Status window > Messages tab only shows this log entry for a split second, then it disappears and you have to look in the log file to find it. I let Ken know about this.
     
    beepsilver and fenderman like this.
  7. jmg

    jmg Young grasshopper

    Joined:
    Mar 4, 2018
    Messages:
    54
    Likes Received:
    4
    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%

    Using h.265, intel 630 usage is 0% (no surprise), but cpu usage for BI is for all intents and purposes, the same -- around 40-45%, sometimes dipping in the to 50%'s . When I get around to it, I'm switching all cameras back to h.265.
     
  8. afddwfadwfadwf

    afddwfadwfadwf Young grasshopper

    Joined:
    Mar 28, 2016
    Messages:
    69
    Likes Received:
    8
    any update in the past year?
     
  9. bp2008

    bp2008 Staff Member

    Joined:
    Mar 10, 2014
    Messages:
    8,435
    Likes Received:
    5,394
    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.