panskat ulphryd zeenia

0 views

Skip to first unread message

Kum Dana

unread,

Aug 2, 2024, 7:52:46 PM8/2/24

to quifiguchor

In the H.265 tests, the h.265 camera were compared to mainstream h.264 cameras from different models and from other brands. The key conclusions of the report came from this comparison, not from the cameras own h.264 performance vs h.265 performance:

So for now it seems H265 has a competitor to "enhanced" H264 methods, but wasn't one benefit of H265 supposed to be you only needed one stream from which you could pull different resolutions, such as high-res for recording and low-res for viewing?

No. I've never heard anyone even claim that before. The 'pulling' different resolutions is a feature of scalable video codecs and H.265 being shipped / implemented is not scalable, just like 'regular' H.264 is not.

Lew, thanks for the feedback. I am curious what the upgrade delivers. I have not heard of any existing NVR appliances being field upgradeable to H.265. I am sure it's possible but generally the increased processing needed to do so makes it impractical for existing units.

I recently installed 4 of the new 4MP value plus cameras and enabled h.264+. I installed them on a Milestone system and noticed a significant delay in the video streams "starting" in the viewing client versus turning h.264+ off. Anyone else try this out in Milestone and experience anything similar? Running the 2016 Smart client on a Core i5 with HW Acceleration enabled. I ended up disabling h264+ for the time being due to the delay being pretty bad at times up to 30 seconds or so when double clicking on a camera to enlarge then going back to a multi-view. CPU wasn't high just a long delay...

Finally got around to testing this. The delay is still present with HW acceleration on and off. I've got these h264 plus cams on a few different systems and all of them still have the same results. They are also noticeably slower to appear in milestone mobile.

The cause of this is probably that the client will have to wait for an I-frame before it can start decoding the rest of the frames. Smart codecs do have higher GOPs when there is no motion on the camera, which means a potentially long wait for the first I-frame. If you generate a lot of motion e.g. aggressively wave your hand in front of the camera, is the delay nearly as long?

Why? Looking at the new models coming out of both Chinese republics, they seem to be mostly h.265. At this point, it probably doesn't cost them much more to use that chip, so I would expect by year's end that pretty much EVERY device they make to be h.265 capable.

The fact that H.265 is more advanced does not mean it has to be successful in business. The same fact happened to MPEG-2, which had been used in the broadcasting industry for super long time, even if MPEG-4 was proved to be much more efficient in coding than MPEG-2.

If no big players like Google/Apple/Microsoft are embracing H.264/HEVC, and making it to be a successful market standard, then I don't see HEVC will soon be widely accepted, and the licensing issue of HEVC may not be quickly solved either.

The history why H.264 license was made to very low or free, was because Microsoft invented VC-1 to be competitor and made H.264 to be at a difficult position. After H.264 becomes cheap or free, it was soon supported by all popular operating systems, Windows, MacOS/iOS and Android.

Because H.265 has no competitor right now, it's hard to see H.265 license issue to be solved soon. so H.265 may be only limited, and use in some 4K or above 4K video only. also H.265 in surveillance market may take a few years to grow to bigger size, that's why H.264+ can be more useful than we thought.