QuickStart DPE/VDE/HDE/SDE Encoder / Decoder pair – New FW with neu GUI 2026:  
Example with SDI-IN: Setup scenario – devices can vary…  
TOC  
Starting with the Encoder IP: ............................................................................................................................................2  
The Network settings........................................................................................................................................................5  
On Screen Display .............................................................................................................................................................9  
Recording to NFS.............................................................................................................................................................10  
The different Input Frontends ........................................................................................................................................14  
Encoding Parameters:.....................................................................................................................................................15  
About Preview functions:................................................................................................................................................17  
TS/Multicast settings ......................................................................................................................................................24  
Audio:..............................................................................................................................................................................29  
Other protocols HLS/RTMP:............................................................................................................................................33  
RTSP/HTTP-streaming.....................................................................................................................................................34  
ONVIF ..............................................................................................................................................................................34  
Loki:.................................................................................................................................................................................35  
Others: ............................................................................................................................................................................35  
Annex 4Kp60 decoder/transcoder HDD-276 operation: ................................................................................................38  
The only difference between the VDE, HDE and the SDE SoC Multiprotocol Video encoders is the Input – Frontend:  
VGA, HDMI or SDI and eventually the DPE = Display-Port encoder – depends on HW platform as well.  
And therefore, the DPE/VGA/SDI Versions do not have an EDID entry in its Web-IF because it's not needed.  
Both are equipped with loop-IN -> out connectors, so the Input signal can be cascaded or used for monitoring.  
The HDD Decoder box is available as w/ HD-SDI output or as a 'light' Version w/o SDI.  
We assume, that you are a skilled person which is familiar with the basic IT-network settings and understanding of  
streaming protocols. If not, you can get more information from our website- chapter Tutorials/Know-how:  
https://www.blankom.de/tutorials.html (English) | https://www.blankom.de/anleitungen-deutsch.html German.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
1
Different HW/SW combinations supporting different features and parameters:  
Example: The W-FW supports recording to NFS/Samba network folders, A-Versions might not.  
The encoders almost have 4 encoder engines in 1 chip but limitations are to be considered:  
The Mainstream-Encoder-part can be used to support WebRTC and TRTC while the substreams do not and will be  
disabled. Main and 1st Substream supporting the full resolution encoding while 2nd and 3rd substream engines do 1  
step below and another step below: E.g.: Main and sub will encode in FullHD, so 2nd 3rd supporting the output stream  
only as 720 but this depends from the HW version so the FW as well – please check the datasheets and HW/FW.  
Starting with the Encoder IP:  
Default Login Addresses Encoder: 192.168.1.168 | Decoder: 192.168.1.169 user/password: admin/admin  
The password can be changed according to your own security policy. The username stays as it is because of its  
internal Linux OS to keep the system rights for its operation.  
So, to access both units, your Laptop/PC should be set to the same IP-range as the decoders. For later stream  
checking's we recommend to use only the Network interface and disable another equipped – like WIFI – otherwise  
the computer might not be able to decide which interface to be used for the reception of a stream – in particular for  
Multicasts UDP/RTP.  
If both Network-devices are ON, you can change/set the METRIC Values in your Network-devices as lower value has  
a higher priority: Example for Ethernet: Change from Auto to manual and set the Metric to 10, while the WIFI should  
be set to a higher value e.g., 100.  
New features with the ne GUI version (1.xyA A=Ambarella / 2.yxW W= Hisilicon):  
Network related: IPv6* support, mDNS, HTTPs by certificate,  
NFS or SAMBA-network file systems mounting for mp4/TS Recording*  
Stream-Targets: WebRTC and TRTC, 3x RTMPs – Pushing*, Multi SRT streaming as 'Listener' (No Rendezvous-mode)  
(Rem: VLC supports only 'calling the SRT-IP from the Listener (encoder-streamer))  
*depends on HW and FW  
Example in Windows 11: Give your PC a manual IPv4 address/GW/NM/DNS and it’s Metric:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
2
 
Recommended browsers: Mozilla, EDGE, Chrome or Opera… or any other … but it might have an impact depending  
on the individual browser settings.  
HINT: All of our De- and Encoder of this product family are equipped with a RESET switch accessible through a tiny  
hole at the front or rear site. If you lost your changed IP-Address or password, you can set the unit back to default by  
pressing the RST switch by a needle for at least 10-15 seconds (Green LED and NW-LEDs will go off) -> release the  
button and it will reboot with factory defaults.  
After Login,  
You’ll get following Status-screens:  
Encoder:  
Some info upfront:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
3
In General: The default encoding parameter settings are almost fine to start with. Unless you know what you are  
doing, keep them ;-)  
As Encoder bitrate settings we recommend to set it to 5000-8000 kb/s depending on your needed picture quality or  
even more… you need to find the balance…  
If you use multicast streaming (UDP/RTP) for IPTV hospitality environments, you should assure, that your Ethernet  
Switch supports IGMP to avoid flooding your network with those streams and overload other devices network ports  
in your system.  
Please do not use the same UDP or RTP IP addresses (224.0.0.0 … 239.255.255.255) in your network as IGMP  
manage these addresses in your Ethernet Switch on demand (Query / Snooping):  
Decoder:  
Rem.: Both already with a connected input signal  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
4
The Network settings:  
Recommendation: Use a static IP address is almost better than DHCP. IPv6 is now supported but we recommend to  
concentrate on the IPv4 and let the IPv6 in Automatic mode.  
Please change the DNS values to your local  
needs. If you have a Router in between or  
a Bridge with own DHCP-Address ranges,  
please assure that you set it to non DHCP  
ranges reserved for static IP's and avoid IP  
address-conflicts.  
NTP is almost helpful for time  
synchronisations and e.g. overlay the  
time/date information in the encoded  
Video stream. But you'll need a local NTP  
(some Internet routers are advertising it or  
grab it from the Internet.  
The Port-addresses usually can be kept as they are as defaults or changed if you know what you are doing.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
5
 
The new GUI/FW supports mDNS.  
The Hostname can be changed.  
If you need to use it, you can enable it and the device is  
accessible through its URL:  
Copy it and paste to your browser: Example:  
encoder34728.local  
Needless to say: All changes need to APPLY it.  
Comparison: The HDD-decoder (as a couple encoder -> decoder) settings are nearly similar:  
But actually, no mDNS supported and  
the MTU settings are located here.  
Rem.: If you pass the encoder-  
streams through VLANs in a GbE  
Switch, you might need to increase  
the MTU values to avoid packet loss  
i.e., in UDP streams which you even  
not will recognize except in the  
Stream-Receiver as picture/sound  
disturbances or Makro-blockings.  
The encoder supports MTU  
adjustments it in the Submenu  
Encoder -> Advanced:  
HINT: Also some Network-Switch  
vendors are using proprietary  
functions and non open public  
features… which might cause such  
distortions by packet droppings.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
6
Just a small remark about the APPLY button and its confirmation message  
This mostly does not mean to reboot the units (En- Decoder) but to re-adjust your receiver unit and restart it  
because of essential parameters has been changed by you.  
Example: If you change the codec from h.264 to h.265/HEVC, your receiver might stop decoding:  
This one stopped after changed  
the codec. Restart it:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
7
And e'voila:  
A hint: If you do not have a valid input signal, the encoder is streaming a Test-picture:  
Some decoders or IPTV receivers might see this as a pumping stream.  
To avoid this and the stream does not contain a real 'still-picture' but even small changings in it, you can insert an  
overlay to the Video by inserting a running clock info (see above) by entering the  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
8
On Screen Display OSD -menu and set the 'Time' info to it:  
Up to 4 OSD's can be added as Logos or Text and choosing the regions X/Y colours and transparency (ALPHA):  
A lower APLHA increases the  
transparency:  
For inserting Logos as PNG there are  
some rules -like size max each 500kB - to  
consider for the picture to show it  
correctly.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
9
 
The Logos or advertisement banners can be uploaded in its submenu:  
Recording to NFS  
The new GUI also supports the recording to a NFS-server (v4) or a SAMBA fileserver mounted to it.  
Because of SAMBA is a way more complicated the version is important and should harmonize while Windows-Server  
SMB is mostly not the same issue as with a Linux-Server, we assume, that your IT/Network knowledge should be  
professional or you need to consult your IT techies.  
A simple example to establish a NFS server is the Linux installation here a RaspberryPI5 with the actual Raspbian OS:  
Open a terminal and enter:  
sudo apt-get update  
sudo apt-get install nfs-kernel-server  
sudo mkdir /home/public  
sudo chmod ugo+rwx /home/public makes it open for everyone  
sudo nano /etc/exports  
add this line:  
/home/public *(rw,sync,no_subtree_check,all_squash)  
Save it and reload:  
sudo exportfs -ra  
restart the server:  
sudo service nfs-kernel-server restart  
check the services running:  
sudo rpcinfo -p  
should show many times: portmapper, status, nfs, nlockmgr und mountd,  
Add the IP and mounting folder and 'mount' it.  
Then you see the following if the mounting was successful. If not … search for the problem.  
So, we need to enter into the Recording Settings: <IP-Address>:/home/public/  
And mount it. If the mounting fails, you'll get a message. Remark:  
Mounting an NFS from a Windows11 PC has a different format by opening a CMD/PS as admin of course:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
10  
 
Here as Virtual HD named K (should be a free and not occupied character):  
-> Network:  
You must enter the  
address/path once -> than it  
pops up  
Unmounting from Windows11:  
PS C:\Users\Blank> Remove-PSDrive -Name K  
Back to the Encoder:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
11  
After recording something… Remark: Of course, it needs an input signal…!!! Otherwise recording will not start.  
You'll see the files you have done and can be accessed by your Windows-PC or directly in the Linux-Server or play it  
from Browser (downloading takes some time) … So, you do not need an expensive NVR anymore.  
You can download and play it:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
12  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
13  
The different Input Frontends  
have naturally different encoding parameters. Example for VGA (VDE-265):  
HDMI-Encoder – actual Ambarella Version:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
14  
 
Compared with the VGA and SDI-Versions it has an extra entry for the HDMI Settings:  
The EDID is necessary to simulate different HDMI Input connections to its sources and the  
B-Frame support:  
If B-Frames are supported by the Chipset* /Codec and should be used, it increases the picture quality if necessary  
but might increase latency and bitrate of the stream. Make yourself familiar with the different codec architectures  
please.  
Encoding Parameters:  
Of course, such a Video-Encoder has a lot of parameters to be adjusted to serve worldwide requirements.  
Example: US related countries were working on 60Hz (30 or 60 FPS) or its history is different (NTSC instead of PAL).  
Interlaced or progressive modes are also to be considered.  
E.g.: Full HD can have 1920x1080 i50 (Interlaced) as an Input or like the German public broadcasters sending 720p50  
(progressive) via Satellite while others are transmitting 1920x1080i50.  
Our SoC encoders are taking the interlaced input signals but combine the even and odd half-picture into a Fullscreen  
progressive output: 1080i50 will be 1080p25 (or can even done a p50). The default settings are FPS 30 and GOP 30 –  
which is related to US 60 Hz!!! Usually the IBBP- or IP-frame components in a codec is also used for different  
approaches – so you should also investigate a bit in codec basics?  
So, your first action when configuring the encoder with its menu should be:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
15  
 
Check the input signal value you are getting from the STATUS screen:  
Be patient, it takes some time to update itself.  
Change the encoding parameters in MAIN/Secondary etc…:  
Pay attention to the hints in the web-menu.  
Of course, you can modify the input to a different output frame rate but imagine what happens if you have an input  
of interlaced 50 and output is set to 30 (progressive by chip-default). The encoder must reply/add or delete  
pictures/frames… and therefore the quality will decrease. Recommended: Set the GOP to 2x FPS.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
16  
About Preview functions:  
You can get all/most actual running parameters in Realtime from the STATUS window:  
Here you can check with the web-Interface directly the input signal by clicking the Preview-link (green).  
Upper corner right side of the embedded Video -> you can close it…  
Another STATUS-Page preview function is directly from after the encoder parts Main/Secondary etc:  
Apart from all information you are getting here, you can  
also copy and paste those URL's to your video-Player like  
PC-VLC, Potplayer and FFPLAY as well as IPTV STB's, our  
IP-decoder HDD series TV's with integrated IPTV clients…  
But for the internal Preview player the FLV URL must  
have been enabled.  
Because FLV is an outdated Adobe thing, it works best  
with h.264 codec but h.265-hevc is also supported but no  
control possible  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
17  
 
Fullscreen Browser-Preview can be used with mp4 http address streaming enabled:  
Opens a new browser window and plays  
Remark:  
----------------------------------- back to Encoder parameters:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
18  
It is essential that you know:  
-
-
-
Your input values (i.e., resolution and framerate, maybe audio level and its format PCM/Bitstream)  
If you want to transcode that or keep the input to be streamed simply  
Your target streaming clients and which protocols are supported  
Please note, that there are particular differences between such (System on Chip) SoC based encoders and FPGA  
based professional encoders and that PC's as receivers like using VLC are almost failure tolerant against packet loss  
and other problems.  
This manual cannot explain in details about the different codecs their many different parameters for different  
stream clients – note: Also, the different IPTV receivers like STBs have their different problems, bugs and features  
which might not match.  
We are skipping here the setups of the 1/3 Sub-streams which can be configured for parallel output streaming with  
other encoding parameters – except Audio – this is common for all 4 (or 2 in some encoder types).  
The ideal AV-encoding setup is to first start with following the input parameters from the STATUS Page:  
The input is interlaced (here HDMI from a SAT STB which its  
output setting is fixed to 1080i50 nevertheless the TV service it  
receives might be 720p50…) it should be constant/fixed at the  
input because frequently changings in the HDMI/SDI input might  
cause longer interruptions in the stream and other side effects.  
So, we have 1920x1080i50 and an Audio SR of 48KHz -> we  
should set the encoder parameters accordingly.  
Note the hints from the Encoding web-menu:  
•
H.265 offers better quality than H.264. Use it whenever your decoder supports it. Group of Pictures, keyframe  
interval = GOP / FPS (in seconds)  
•
In VBR mode, the bitrate is limited by the Quality Range. Selecting "Better…Best" or "Best" can result in very high  
actual bitrates, ignoring the target bitrate. Only "Lower…Best" keeps the target bitrate meaningful.  
For DVB systems, "Strong CBR" is required. Minimum: 5000 kbit/s for 1080p; Recommended: 8000kbit/s.  
Key-Frame Interval Settings:  
•
•
If the input frame rate is "N" (e.g., 60, 50, 30, 25), set the key-frame interval to twice the input frame rate (2xN).  
•
In Auto mode, the interval is set to half the input frame rate when N>30; otherwise, it is set to N.  
Some IPTV receiver might only support h.264 – we recommend to start with this and test it:  
MJPEG is for direct MJPEG streaming support and if  
used, the streaming menu changes:  
Enable MJPG and you'll  
get the link in the STATUS  
menu to use  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
19  
But there is no AUDIO support for MJPG…  
Please NOTE: If you set one of the encoder parts (Main-substream1…3) to MJPG, the other streams will be switched  
off. If you accidently enabled MJPG, and have returned, please re-enable your former streaming protocols.  
Same as Input does the same to the  
output e.g.: i50 will be p50 out  
p25 will be p25 out… interlaced will  
become progressive always.  
AUTO means: input i50 = out p25 (best  
choice)  
CUSTOM: you can adjust by yourself but  
be careful…  
Changing to 30, the stream will get 30  
for US-Norm TV's � …  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
20  
We recommend to use that default but you can  
play with the settings. Rem: increasing the quality will increase the latency…  
This is true: VLC does not accept the old Adobe Flash streaming with HEVC codec – only h.264 if you want to check it:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
21  
As you can see, the encoder chip supports  
format changings…  
But see below, now the OSD overlay needs  
new parameters as well.  
Please also have an eye on the correct  
picture settings: 16:9 input -> to keep that  
E.g.: if you set it to 720x576 its 4:3 the  
picture 16:9 will be egg-head formated  
Therefore, we recommend to use input  
follow mode.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
22  
The Ambarella chip supports only Main and High  
profile of the h.264 codec. Using h.265 is only 1 Profile so it cannot be changed:  
A nice overview for that profile stuff can be read here:  
H.264 profiles and levels | Inside & Outside MediaCoder  
High Efficiency Video Coding (HEVC), also known as H.265 and MPEG-H Part 2, is a proprietary video compression  
standard designed as part of the MPEG-H project as a successor to the widely used Advanced Video Coding (AVC,  
H.264, or MPEG-4 Part 10).  
See also: ITU MyWorspace: ITU-T H.265 (V3) (04/2015) - High efficiency video coding  
High Efficiency Video Coding - Wikipedia  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
23  
Bitrate mode:  
CBR is optimal for live streaming because it  
offers reliability in quality and bandwidth  
usage. VBR is optimal for on-  
demand content because it is more  
economical in storage space while  
maintaining better quality per size ratio.  
But increasing latency.  
CBR = stable, predictable upload → best for  
live streaming and platforms that expect a  
steady bitrate (including Dacast live ingest).  
VBR = bitrate flexes by scene complexity →  
best for VOD / uploads where encoding  
time is OK and you want better quality-per-  
MB. We have 10 different stable-Modes you  
can chose from… to match your  
requirements… trial and error…  
Comes from CBR vs VBR: Which Bitrate is Best for Low-Latency Streaming?  
STRONG CBR is mostly useful for DVB-receivers IP SPTS to Multiplexer-Modulators and inserts also a so called Zero-  
packet into the stream which is PID 8191dec in the DVB-tables. In combination with this, the PCR-setting might be  
also adjusted for DVB – IP receivers which per-DVB-Norm are for headends and declares only UDP/RTP Multicast-  
Streams as Inputs for the DVB-Multiplexer-Modulators:  
TS/Multicast settings  
The most important for IPTV Systems/receivers:  
Please consider IGMP for your managing network Switches (Layer3) if you stream multicasts.  
The IP addresses should be always different in a common network!!!, Port numbers should be considered according  
to IANA: IPv4 Multicast Address Space and 50 Common Ports You Should Know - GeeksforGeeks  
SAP/SDP is the 'Session Announcement Protocol' which broadcasts the network multicast streams and is very helpful  
to grab them.  
Session Announcement Protocol - Wikipedia  
Example by VLC (and you can create a mu-file from it … but that’s not the topic here):  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
24  
 
You can directly click and it opens the stream…  
Back to NULL-packet insertion:  
20% should be used  
Example for a CBR stream with Zero-packets injected to bitrate + 20% filling up so the stream gets 8Mb/s:  
While the content is nearly CBR but fluctuations are normal for moving pictures  
Important as well as the PCR interval should be considered for DVB IP receivers: max 40ms are recommended for  
DVB-IP-TS:  
So, it might be worth to play with PCR settings if you face problems with a DVB-IP-receiver.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
25  
System B DVB according to ITU Annex-B is the derivate for US-CATV units and can be enabled if needed for an EDGE  
QAM modulator in DVB-C Annex-B. The rest of the world (except Korea) is using the 'normal DVB-C Annex A/C  
standard.  
You should have knowledge about the DVB-Tables to change the Streaming parameters…:  
The parts which are necessary to have a valid table framework for Multicasts and also Unicasts containing so called  
PID's. The table version should not be changed unless you know what you are doing.  
PAT Program Associating Table is a must have as well as  
SDT = Service descriptor Table  
Video PID  
and Audio PIDs (Audios can be several in a stream if multilanguage and /or Dolby is send)  
Those basic tables containing essential information about the Stream and its components like TS-ID, ONID, links to  
the Audio/Video and their codecs in use and so on.  
DVB: PID 0, 17, 18 EIT, and others are reserved and cannot be changed…  
Comparing with a DekTec analyser makes it visible for you (set to decimal PID-numbers instead Hex):  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
26  
In the SDT above you see the values from the encoder: ONID, TS-ID, Service-ID, types, name of the broadcast (live…).  
The PCR PID comes along with the Video PID and as you can see above, with Strong CBR and 20% zero packets  
inserted, it is in Auto-Mode with 2ms – which is quite perfect.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
27  
Set the encoder to VBR-mode:  
Shows the high variability/fluctuation with the 'BEST' settings as a VBR:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
28  
The TS – part of this Menu  
is for the unicast Transport-Stream as HTTP-Mode which can be inside a UDP while the handling is based on http /  
TCP mode:  
Audio:  
Before we come to the other UNICAST streams, we come to the common AUDIO settings because the encoder sets it  
for all Main and Secondary streams:  
Most encoder types have external 3.5mm Stereo jacks for analogue audio inserting instead using SDI embedded or  
HDMI. VGA or DP encoders always have external inputs. For SDI sand HDMI we recommend to use the Digital in like  
as the default settings – see above.  
We recommend to follow the input (HDMI/SDI).  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
29  
 
Different embedded Codec can be used. For DVB its almost either MPEG1Layer2 Stereo (MP2) or AC3 while AAC will  
work, but the extended AAC + and ++ need to be checked by the stream client in use. Every codec have different  
audio bitrate settings to be considered:  
This needs to be harmonized when changing it. See above, 256000 is not in the AAC++ range.  
But you'll get a hint:  
Volume and Denoise:  
As the web-content shows: The digital Volume increasing might cause audio distortions. You should balance this with  
your input Audio Volume coming form your input source (HDMI/analog/SDI). Use the denoise function if needed.  
G711 Over PTE (which is our proprietary multicast protocol should not be mentioned here.  
As well as ONVIF support – this is a special case for NVR's which are using this to monitor and control Cameras – and  
so our encoders can work like a streaming camera device. More in our www.blankom.de websites-tutorials and so…  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
30  
The Audio Lipsync should be set to automatic in the ADVANCED Menu:  
But if set to resample it might glitch over the time… and maybe manually corrected by the user -2000…+2000 ms.  
Using SRT Listener/Caller modes:  
Rem: VLC only supports the caller mode – so it calls the encoder stream (listener) on demand by entering the simple  
srt://<IP-Address>:9000 (for the main-encoder part as set to default) when enabled.  
The listener mode works vice versa: In the encoder you need to setup the target streaming address  
e.g. a Decoder-IP address:port number in the encoder web-menu:  
The target like the HDD-Decoder or other stream receivers like our Protocol changing device BIG-1050/1100X need  
to assign the port-number and declare it as 'waiting-for a stream pushed by the sender according to FFMPEG  
commands:  
Encoder settings – push mode: Encoder IP-Address is 192.168.1.168, Decoder is 192.168.1.169  
Encoder as Listener needs only these 0.0.0.0* as IP address because it automatic uses its own one as the target from  
the Caller (the receiver-decoder). The port-address can be chosen and should not interfere with other network port  
settings in use.  
Check the status page:  
Pull the Stream by a receiver like VLC (caller from the listener (encoder)):  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
31  
->  
As mentioned before, VLC only supports this mode while the encoder can do both. Here the Push-mode:  
It 'listens' to an incoming stream from the encoder:  
And the encoder STATUS changes from not-connected to connected if the handshake was successful:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
32  
Decoder settings IP=192.168.1.169: Follow the hints given in the web-menu:  
Both can work in Caller or Listener mode. You always have to consider the view-direction from the Source and from  
the Destination (Receiver) as both cannot be caller at the same time or Listener at the same time. If the Streamer is  
set to Listener, the Receiver need to be the caller and vice versa.  
Other protocols HLS/RTMP:  
As HLS and also RTMP(s) are supporting also push and pull modes, mostly used for streaming to a Video-Platform in  
the internet (Youtube/Vimeo, … ) those settings /tokens/certificates/user:passwords need to be clarified with the  
Media-server access before starting to configure:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
33  
 
Maybe worth to mention, that HLS is one of the most Latency adding protocol because of its architecture.  
In Advanced settings those can be adjusted for HLS:  
RTSP/HTTP-streaming  
are the oldest existing streaming protocol while both are handling by TCP and RTSP can use RTP as a on top if UDP  
inside. We do not explain those in detail here but you can have a look to our Website:  
https://www.blankom.de/tutorials.html and https://www.blankom.de/anleitungen-deutsch.html and you might find  
the right documents for those….  
For RTSP you should chose which encoder part to be used for it in Advanced Settings:  
Also, the Transportstream-type content can be assigned:  
as TS or Elementary Stream.  
ONVIF  
Is supported as version 2.8 and maybe higher. Please check the internet about what's best to use like a NVR or the  
free ODM (Onvif Device Manager freeware for Windows):  
https://www.blankom.de/assets/downloads/odm-v2.2.250.msi  
or 'Milestone' as a ONVIF Camera Software tool.  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
34  
   
Location can be set… as it will be shown by ODM…  
And it can be assigned a password for it:  
as well as this can be done also for HTTP and RTSP to 'secure' the streams  
because the dedicated receiver needs to know this to open the stream:  
If enabling, the encoder user:password are taking effect also for  
the streams (default: admin:admin)  
Loki:  
If you need to log all actions of the encoder, you can install a Loki-Server in your net and address it.  
See picture above.  
Others:  
can be adjusted  
This can do a correction if you have e.g., a 16:9 input and do a 4:3 output resolution (Downscaling) to correct it:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
35  
   
Self-explaining:  
Manipulation of the Picture: Rotation, Flip/Mirror and crop it  
If you have more questions, do not hesitate to contact us by sending an email to: contact@blankom.de  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
36  
In the HDD Decoders you can also set the picture output individually:  
Here you can also adjust which Input stream should be placed where…if you use the 4 Inputs and Mosaic to the  
output.  
As well as crop it also:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
37  
Annex 4Kp60 decoder/transcoder HDD-276 operation:  
This unit supports decoding up to 4 input streams to a 4-Mosaic 4K picture on the HDMI-Out and Transcoding to  
stream to an IPTV network output:  
Input from encoder:  
Set to transcode it:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
38  
 
Decoder output stream is now:  
*Depending on model/type --------Technical changes are subject to change w/o notifications  
39