{"id":48484,"date":"2021-04-20T11:48:35","date_gmt":"2021-04-20T03:48:35","guid":{"rendered":"https:\/\/www.kiloview.com\/en\/support\/\/docs\/g1\/g-serial-wlan-encoder\/6-2\/%e7%bc%96%e7%a0%81%e5%92%8c%e5%aa%92%e4%bd%93%e6%b5%81\/"},"modified":"2021-04-20T11:48:35","modified_gmt":"2021-04-20T03:48:35","slug":"encoding","status":"publish","type":"docs","link":"https:\/\/www.kiloview.com\/en\/docs\/g-serial-wlan-encoder\/6-2\/encoding\/","title":{"rendered":"Encoding &#038; Steam"},"content":{"rendered":"<h3>Audio encoding parameter setting<\/h3>\n<p>Encoders can set audio encoding parameters. Click \u201cEncoding &amp;stream\u201d, pull downward \u201cAudio Encoding Engine\u201d, then entering into audio parameters setting. Audio encoding channel is forced to enable. Audio encoding modes include AAC and G.711, optional. Audio sampling is chosen according to actual situation. Channels consist of \u201cStereo\u201d and \u201cMono\u201d. Encoding bitrate is adjustable between16K-256K, default is 64Kbps. One more detail: if encoder using TS-UDP protocol or needs using recording, then it needs to choose \u201cWith ADTS header\u201d under AAC format.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image51.png\" alt=\"img\" \/><\/p>\n<blockquote>\n<p>Note: Please do &quot;Quick Reset&quot; to take affect if you changed the &#8216;Resample policy&#8217; or &#8216;Sampling&#8217; parameter.<\/p>\n<\/blockquote>\n<h3>Encoding and stream settings<\/h3>\n<p>Video encoding parameters are adjustable. Click \u201cEncoding &amp;Stream\u201d, pull downward \u201cEncoding and stream settings\u201d to enter below interface. We generally set parameters of \u201cH.264 main stream\u201d, click \u201cSetting\u201d.<\/p>\n<blockquote>\n<p>Note: It is H.264 Main stream, the second setting, not Motion JPEG setting.<\/p>\n<\/blockquote>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image52.png\" alt=\"img\" \/><\/p>\n<p>Click SET, entering into below interface for main streaming encoding parameters setting, as follows:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image53.png\" alt=\"img\" \/><\/p>\n<p>\u201cScaling\u201d has 9 options for choice. Default setting is \u201cDefault size\u201d, that is, the video size after encoding is the same as the input video size.<\/p>\n<p>\u201cColor\u201d has two options: \u201cWith color and monochrome\u201d. Monochrome is black and white color, \u201cwith color\u201d remains the original color. Default setting is \u201cWith color\u201d.<\/p>\n<p>\u201cH.264 Profile\u201d supports High profile\uff0cmain profile\uff0cbaseline, which is set according to platform supported encoding profile. High Profile is the highest compression efficiency, that is, under the same bitrates, image quality is the best; Baseline is the most widely supported; default setting is High Profile.<\/p>\n<p>\u201cBitrate control\u201d has two ways: CBR-Constant bitrate and VBR-Variant bitrate. From literal meaning, CBR is stable and unchanged bitrate, while VBR is constantly changing according to actual content. Generally, network transmission adopts CBR to guarantee transmission quality, while file storage uses VBR to guarantee file quality. Default setting is CBR-Constant bitrate.<\/p>\n<p>\u201cBitrate\u201d supports adjustable 64K-25M. Users could choose default setting, or self-define bitrate size. The higher bitrates, video quality after encoding is better. But specific setting should be based on actual network situation, couldn\u2019t be higher than your own upstream bandwidth.<\/p>\n<p>\u201cFramerate\u201d has three options: FULL (same as input source, HALF (half when source framerate&gt;=50 and customized framerate. \u201cFULL\u201d means framerate after encoding is the same as the framerate of input source; \u201cHALF\u201d means if input video is 1920*1080P50, video framerate after encoding will be 25. This will be a good saving on the consumption of network bandwidth; customized framerate is user assigning framerate after encoding, in theory, it shouldn\u2019t be higher than original framerate.<\/p>\n<p>\u201cGOP size\u201d has five options and supports user-defined adjustment. It is adjustable according to actual situation, default is 60, and normally it could meet the most majority of needs.<\/p>\n<p>\u201cReference frames\u201d has two options: one and multiframes. Theoretically using multiframes can improve encoding quality, but some decoders and players may not support multiframes.<\/p>\n<p><strong>Sub stream parameter setting refers to Main stream configuration.<\/strong><\/p>\n<h3>Streaming media service<\/h3>\n<p>Encoder currently support streaming services include: RTSP, RTMP push, HLS service, TS-UDP push ,SRT push, Onvif service. One code stream can run up to 8 stream services at the same time for the encoder, which means it can push the video stream to 8 different live platforms. There are two code streams (the main stream and sub stream) for the encoder, so the encoder can stream up to 16 different live platforms at the same time. In general, the main stream is enough, and the sub stream is mainly used in the security monitoring field to achieve the docking usage with the NVR.<\/p>\n<h4>Motion JPEG stream<\/h4>\n<p>Encoder has a Motion JPEG stream, it keeps running without stop. It is blank with blue color if without video access. If with a video signal access, Motion JPEG stream will display the content of current flow, \u201cthe video signal lock\u201d displays locked and it will display the current video signal format.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image54.png\" alt=\"img\" \/><\/p>\n<blockquote>\n<p>Note: Motion JPEG stream is a picture preview, refresh every 3 seconds, or click the mouse to refresh, so it is normal to see it is not fluent on the page.<\/p>\n<\/blockquote>\n<h4>RTSP service<\/h4>\n<p>RTSP service cannot stop when encoder runs. It will not have additional load on the encoder if the stream is not pulled for decoding. As shown in the red frame, the RTSP service flow address is &quot;rtsp:\/\/192.168.1.168:554\/ch01&quot;. &quot;192.168.1.168&quot; is the IP address of the encoder, If the for encoder, the IP address is 192.168.2.168, then the RTSP service address is &quot;rtsp:\/\/192.168.2.168:554\/ch01&quot;, if there are several IP encoding device, these IP address can also directly pull RTSP flow accordingly.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image55.png\" alt=\"img\" \/><\/p>\n<p>Normally VLC media player is used to decode and play the video stream. Open VLC media player, select the &quot;media&quot;, and &quot;open network stream&quot;, then enter the RTSP service URL address, you can play the video.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image56.png\" alt=\"img\" \/><\/p>\n<blockquote>\n<p>Note: URL should be copied completely and the punctuation marks should be included.<\/p>\n<\/blockquote>\n<h4>RTMP Pushing (Live streaming)<\/h4>\n<p>Using RTMP pushing, the first thing is to make sure platform providing RTMP pushing address, otherwise our encoders couldn\u2019t do RTMP pushing (Currently some live streaming APP couldn\u2019t provide RTMP pushing address.)<\/p>\n<blockquote>\n<p>Note: The principle of RTMP push stream is that it must be pushed from the encoder to the platform. The computer\/decoder then pulls the RTMP stream from the platform for playback. The encoder cannot directly push the RTMP stream to the computer\/decoder for playback.<\/p>\n<\/blockquote>\n<p><strong>YouTube live streaming<\/strong><\/p>\n<p>\u201cStreaming point\u201d is RTMP address given by platform (Take YouTube as an example). (Other platforms are similar, if any questions please contact platform technical support for help).<\/p>\n<ol>\n<li>\n<p>Login to YouTube, get below address:<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image57.png\" alt=\"img\" \/><br \/>\nStreaming point should be like Server URL+Stream name\/key.<br \/>\nFor example: rtmp:\/\/a.rtmp.youtube.com\/live2\/9ja6-9u28-uz4j-8x6r<\/p>\n<\/li>\n<li>\n<p>After you get the RTMP URL address, you need to set it up in the encoder. In the main stream of H.264, there is a stream service option to be added. By adding a RTMP push, you can get a RTMP push option. Click the settings button on the right side of the RTMP push, and you will enter the interface to fill in the RTMP push configuration. The push address on YouTube platform is filled in the &quot;push point&quot;, and set &quot;Enable pushing&quot; to &quot;Yes&quot;. Click \u201cSave\u201d, then RTMP will stream to YouTube.<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image58.png\" alt=\"img\" \/><br \/>\nIf the platform requires user name and password verification, you also need to fill in the corresponding parameters in the encoder.<\/p>\n<\/li>\n<li>\n<p>On YouTube platform, if the video can be displayed, the push stream is successful; otherwise you need to check the network and other configurations.<\/p>\n<\/li>\n<\/ol>\n<blockquote>\n<p>Note: In the case of RTMPS push mode, fill in RTMPS URL at Push point and set \u2018Use old RTMP version\u2019 to yes, so that it can be supported.<\/p>\n<\/blockquote>\n<h4>TS-UDP Pushing (unicast and multicast)<\/h4>\n<p>Click <img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image59.png\" alt=\"\" \/> to select TS-UDP Pushing, then entering into TS-UDP setting interface.<\/p>\n<p>TS-UDP pushing divides into unicast and multicast. If using unicast, \u201cpushing target address\u201d is device IP address of receiving TS streaming. \u201cTarget port\u201d is any port, but it is better not conflicted with other service port. No need to change Multicast TTL; If using multicast, \u201cpushing target address\u201d needs to write a correct multicast address (224.x.x.x ~ 239.x.x.x). \u201cTarget port\u201d is any port, but it is better not conflicted with other service port.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image60.png\" alt=\"\" \/><\/p>\n<p>After finishing setting, it will come up an URL address from TS-UDP pushing, which could be decoded through VLC or other decoding player. If it is multicast, please remember to close Windows firewall.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image61.png\" alt=\"\" \/><\/p>\n<blockquote>\n<p>Note: When the URL obtained by configuring multicast push mode is udp:\/\/225.225.5.5:5678, if played by VLC Player, it needs to add @ for playing, that is udp:\/\/@225.225.5.5:5678.<\/p>\n<\/blockquote>\n<h4>HLS service<\/h4>\n<p>Using HLS service, the first thing is to \u201cadd a stream service\u201d, then click right-side SET icon of \u201cHLS service\u201d for setting.<br \/>\nBelow is setting interface of HLS service. Very simple, if no special requirements, no need setting, only enable service.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image62.png\" alt=\"img\" \/><\/p>\n<p>Once enabling service, it will get one HLS Publish point. You could watch it through VLC and other players using this address.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image63.png\" alt=\"img\" \/><\/p>\n<h4>SRT-TS pushing<\/h4>\n<ol>\n<li>\n<p>Click \u201cEncoding &amp; Stream\u201d\u2014\u201cEncoding and Stream Settings\u201d \u2013\u201cH.264 main stream\u201d \u2013\u201cAdd a stream\u201d. Choose \u201cSRT-TS pushing\u201d, click \u201cOK\u201d and add a SRT service.<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image64.png\" alt=\"img\" \/><\/p>\n<\/li>\n<li>\n<p>Click the icon <img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image65.png\" alt=\"\" \/>  for SRT configuration.<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image66.png\" alt=\"img\" \/><\/p>\n<\/li>\n<li>\n<p>Fill in the pushing address and port, click \u201cSave\u201d. Then SRT pushing is working.<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image67.png\" alt=\"img\" \/><br \/>\nHandshake mode: Caller\u3001Listener\u3001Rendezvous;<br \/>\nAddress: Set IP address of the receiving port;<br \/>\nPort: Set the listening port corresponding to the receiving port;<br \/>\nTransport delay: Set it based on the performance of the current network, the delay value can be set on both the SRT source device and the SRT target device. The final SRT transmission delay will be the larger one of the two values. Default is 125ms;<br \/>\nAdvanced settings: Open and Close;<br \/>\nEncryption mode: AES-128, AES-192, AES-256;<br \/>\nAES key: encryption AES key can be 10-32 letters or numbers combination;<br \/>\nBandwidth overhead: It is set as the percentage value based on network link quality. Using this value to multiply the total bitrate of the audio and video encoded by the encoder, this will get the occupied maximum bandwidth allowed by Bandwidth Overhead. This value plus the total of video and audio bitrate is the threshold of the current SRT transmission bandwidth, and also the maximum bandwidth that SRT stream can be used. From the perspective of &quot;overhead&quot;, it is the extra &quot;invalid&quot; bandwidth to be used in addition to the media content required for transmission (which can be understood as the payload), but it is different from our common protocol overhead, TCP header overhead, UDP header overhead. The bandwidth overhead here is not a fixed 20\\~60 bytes TCP header overhead or 8 bytes UDP header overhead. It changes in real time according to the network conditions. The worse the network link conditions are, the more overhead needs for normal transmission. The range is 5%\\~100%, and the default overhead is 25%;<br \/>\nLoad size: Sending data packet size, it is optimal that the receiving port should equip with the same size. The default size is 1316, the optimal packet for the codec.<\/p>\n<\/li>\n<\/ol>\n<table>\n<thead>\n<tr>\n<th><strong>Network highest packet loss rate  (%)<\/strong><\/th>\n<th><strong>RTT  Multiplier<\/strong><\/th>\n<th><strong>BW Overhead<\/strong><\/th>\n<th><strong>The lowest SRT delay (when RTT\u226420ms)<\/strong><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\u22641<\/td>\n<td>3<\/td>\n<td>33<\/td>\n<td>60<\/td>\n<\/tr>\n<tr>\n<td>\u22643<\/td>\n<td>4<\/td>\n<td>25<\/td>\n<td>80<\/td>\n<\/tr>\n<tr>\n<td>\u22647<\/td>\n<td>5<\/td>\n<td>20<\/td>\n<td>100<\/td>\n<\/tr>\n<tr>\n<td>\u226410<\/td>\n<td>6<\/td>\n<td>17<\/td>\n<td>120<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<blockquote>\n<p>Note: Below format is the reference delay value under different packet loss. When RTT\uff1e20ms, it requires to increase the delay appropriately.<\/p>\n<\/blockquote>\n<ol start=\"4\">\n<li>Save the settings, then a SRT-TS pushing address will be added. The encoder starts to initiate a handshake connection to the receiving port.<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.kiloview.com\/data\/kv-image\/en\/Encoder\/HD_Video_Encoders_User_Manual_V2.0\/image66.png\" alt=\"img\" \/><\/li>\n<\/ol>\n","protected":false},"featured_media":0,"parent":48358,"menu_order":3,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-48484","docs","type-docs","status-publish","hentry"],"acf":[],"aioseo_notices":[],"comment_count":0,"_links":{"self":[{"href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/docs\/48484","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/types\/docs"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/comments?post=48484"}],"version-history":[{"count":0,"href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/docs\/48484\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/docs\/48358"}],"next":[{"title":"Local recording","link":"https:\/\/www.kiloview.com\/en\/docs\/g-serial-wlan-encoder\/6-2\/local-recording\/","href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/docs\/48485"}],"prev":[{"title":"Video & Audio adjustments","link":"https:\/\/www.kiloview.com\/en\/docs\/g-serial-wlan-encoder\/6-2\/video-adjustment\/","href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/docs\/48483"}],"wp:attachment":[{"href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/media?parent=48484"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.kiloview.com\/en\/wp-json\/wp\/v2\/doc_tag?post=48484"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}