Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

What is the reason for the failure of the GB GB28181 protocol video platform to access the H265 camera for alarm screenshot?

2025-01-19 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Development >

Share

Shulou(Shulou.com)06/03 Report--

This article mainly explains the reason why the GB GB28181 protocol video platform failed to access the H265 camera for alarm screenshot. Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Next, let the editor take you to learn the reason why the GB GB28181 protocol video platform connected to the H265 camera failed to capture the alarm screenshot.

The video structured intelligent analysis platforms EasyGBS and EasyNVR developed by TSINGSEE Blue rhinoceros Video now support the playback of H265 video coding, and you can freely set whether or not to start the H265 player in the configuration center interface.

When testing the connection of EasyGBS to the H265 camera, it appears that the alarm screenshot cannot be taken after the alarm is set by the camera. After entering the database, it is found that the record can be queried, so the situation that the alarm message device has not been delivered is excluded.

Check the code and find that no alarm screenshot code is added when the device access video type is h365, so the alarm screenshot of the H265 device cannot be called, so add the following code to determine that the device access video type is 265 to call the screenshot:

If f.Type = = av.VIDEO_FRAME_I & & msess.Snaping {msess.Snaping = false if err: = msess.doSnap (data, f.Length) Err! = nil {sms_log.Log.Printf ("snap error,% v", err)} module: = utils.Conf (). Section ("module") is_alarm: = module.Key ("is_alarm") .MustBool (false) if! is_alarm {return} if is_alarm {if err: = msess.doAlarmSnap (data, f.Length); err! = nil {sms_log.Log.Printf ("snap error,% v", err)}

After perfecting the EasyGBS code, trigger the alarm again to see if there is a screenshot. The screenshot is displayed normally, and the problem has been solved.

When the equipment contains the alarm layout function, the alarm information of the device can be defined, and the EasyGBS can obtain the alarm information of the device, grab the alarm status recorded by all devices synchronously, and display the alarm level, alarm mode, alarm type and alarm time of the equipment uniformly, which is a very friendly alarm reporting mode. Welcome to understand.

At this point, I believe that "GB GB28181 protocol video platform access to H265 camera alarm screenshot failure is why" have a deeper understanding, might as well come to the actual operation of it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Development

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report