🤔FAQ
Last updated
Last updated
In this section, you will learn frequently asked questions:
It’s primarily used for encoding audio and video from HDMI into network signal. The applicable industries are video surveillance like monitoring desktop of PC, live broadcasting and IPTV etc.
The encoder can be compatible with NVRs from Hikvision & Dahua by private protocol and it’s H.265 recording. But for NVRs from other brands, it can only be accessed by ONVIF protocol. Please note that NVR recording usually use audio by G.711, therefore it’s necessary to set G.711 for encoder, then it can be accessed by NVR. Rare NVRs can be compatible with AAC, like TP-LINK.
TS streaming media addresses:
http://192.168.1.120:80/ts/0 (main stream)
http://192.168.1.120:80/ts/1 (sub stream)
RTSP streaming media addresses:
rtsp://192.168.1.120:554/live/0 (main stream)
rtsp://192.168.1.120:554/live/1 (sub stream)
UDP address:
udp://@224.1.2.3:10000
It’s necessary to clear cache after setting the parameters in IE, or else all settings will not be valid; If you wouldn’t like to clear cache, it’s recommended to use Google Chrome instead, it will be valid immediately after clicking Save button. How should we clear cache in IE? Please see 1.3 or below screenshot:
In video surveillance, H.265 encoding can be used when connecting to NVRs from Hikvision and Dahua. Under network transmission, it’s no problem to use H.265 encoding only when streaming video by protocols of TS, RTSP and UDP.
Currently RTMP standard protocol itself support H.264 only and Adobe already announced previously that it will be no more updates and maintenances for RTMP, that’s why H.265 is not available for RTMP. But it’s no problem for TS to do live broadcasting under H.265 encoding, which can be used for IPTV etc. however, the corresponding streaming media servers should be established by customers themselves. Generally, RTMP will be widely used for common live streaming platforms while TS stream will be used for private or self-established streaming platforms like IPTV.
Yes, it can
Around 200ms
12V, it’s recommended to use DC12V 2A power adapter.
Yes, HDMI video encoder with built-in POE can be powered directly by standard PoE switch(48W); But for basic encoders, you can also buy one POE splitter which get it powered by PoE.
Video & audio will be input from HDMI and output by RJ45, that’s why the primary purpose of encoder is to convert HDMI signal into IP signal and transmit it out.
Hi3516D can reach 1080P@50fps while Hi3516A 1080P@60fps
Insert LOGO from Setting->Video/Audio->OSD->Picture osd via Google Chrome. Also LOGO in 200*200 & JPG only can be supported.
YouTube, Facebook Live, Wowza Streaming Engine, Twitch, USTREAM, LiveStream, Wirecast, vMix etc.
What is maximum power consumption?
One channel only.
XP & Win7 as the maintenance services are already stopped by Microsoft, therefore we won’t do more update and support.
There is only one HDMI port for this encoder which doesn’t support video input by SDI and CVBS. But for VGA, you can buy one VGA to HDMI converter cable. For sure, if needed, we can help you with that.
Yes, it can be set from Setting->Network->Multicast.
Only 2 by default: Simplified Chinese and English. And it can automatically recognize your system language and select languages accordingly.
Yes, but it’s necessary to set RTMP addresses respectively.
Main stream means higher resolution, primarily used for CCTV surveillance while sub stream means lower resolution for network transmission.
Yes, RTMP protocol will be used for live streaming while RTSP for surveillance, so it won’t be affected when simultaneously used.
As far as we learned, only NVR from TP-Link can support AAC, while traditional manufacturers only support G.711, not AAC because of intellectual property. Besides, right now our encoder can be compatible with Hikvision’s NVR & CMS (iVMS-4200) and Dahua’s NVR & CMS (SmartPSS) by private Protocol.
