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 setting s ........................................................................................................................................................5

On Screen Display .............................................................................................................................................................9

Recording to NFS.............................................................................................................................................................1 0

The different Input Frontends ........................................................................................................................................1 4

Encoding Parameters :.....................................................................................................................................................1 5

About Preview functions:................................................................................................................................................1 7

TS/Multicast settings ......................................................................................................................................................2 4

Audio :..............................................................................................................................................................................2 9

Other protocols HLS/RTMP:............................................................................................................................................3 3

RTSP/HTTP-streamin g .....................................................................................................................................................3 4

ONVIF ..............................................................................................................................................................................3 4

Loki :.................................................................................................................................................................................3 5

Others: ............................................................................................................................................................................3 5

Annex 4Kp60 decoder/transcoder HDD-276 operation: ................................................................................................3 8

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 1^stSubstream supporting the full resolution encoding while 2^ndand 3^rdsubstream engines do 1

step below and another step below: E.g.: Main and sub will encode in FullHD, so 2^nd3^rdsupporting 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