How
to
Use
ASI
Remux
Terminology:
“ASI
Remux”
refers
to
the
ability
for
an
Adtec
EN
to
accept
a
Transport
Stream
(TS)
via
ASI
input,
and
multiplex
the
incoming
service
or
services
with
it’s
locally
encoded
service.
The
results
is
that
the
transport
stream
output
becomes
a
MPTS
containing
the
services
from
the
ASI
input
in
addition
to
to
the
locally
encoded
service.
“ASI
Reserve”
refers
to
the
bandwidth
the
user
must
define
to
allocate
enough
space
for
the
incoming
services.
“ASI
Input
Reserve”
is
how
the
field
is
displayed
in
the
WebUI
and
should
be
set
to
the
same
or
greater
than
the
aggregate
rate
of
the
services
from
the
Input
ASI
transport
stream.
“Downstream
Device”
refers
to
a
unit
that
is
receiving
an
ASI
transport
stream
and
multiplexing
the
services.
“Upstream
Device”
refers
to
a
unit
that
is
supplying
the
ASI
transport
stream.
Example:
If
my
“Upstream
Device”
is
generating
a
transport
stream
with
2
services
with
an
aggregate
rate
of
50
Mb/s
then
the
“ASI
Reserve”
for
my
“Downstream
Device”
should
be
set
to
50
Mb/s.
The
TMR
of
my
“Downstream
Device”
needs
to
be
configured
to
allow
for
the
incoming
services
as
well
as
it’s
locally
encoded
service.
If
the
user
wanted
to
receive
a
50
Mb/s
ASI
TS
and
encode
it’s
locally
service
at
a
rate
of
30
Mb/s
then
the
TMR
for
the
“Downstream
Device”
should
be
set
to
greater
than
80
Mb/s
50
Mb/s
(ASI
Reserve)
+
30
Mb/s
(Local
Encoding)
=
80
Mb/s
(TMR)
Thing
to
be
aware
of:
●
ASI
Remux
requires
enabling
of
the
ASI
Remux
Feature
Key.
●
Setting
ASI
Input
Reserve
to
zero
disables
ASI
Remux.
●
If
there
is
a
ASI
Input
Reserve
value
set
but
nothing
on
the
input,
then
there
will
be
null
packets
filling
the
bandwidth
allocated
for
the
ASI
Input.
●
If
Upstream
and
Downstream
services
have
PID
or
Service
Number
conflicts
(meaning
they
are
the
same
value)
the
MPTS
of
the
Downstream
EN
can
and
will
be
corrupt.
●
ATSC
tables
are
not
supported
on
the
ASI
input.
DVB
and
MPEG
are.
●
The
downstream
drops
all
Ingress
tables
and
rebuilds
only
PAT,
SDT
and
NIT
with
the
upstream
services
information.
●
Users
should
ensure
that
the
same
table
'types'
are
being
used
(DVB
to
DVB,
MPEG
to
MPEG)
to
reduce
SI
table
packet
incompatibility
issues.
●
If
the
Upstream
Device
is
supplying
more
data
than
is
allocated
by
ASI
Input
Reserve,
then
there
Upstream
services
are
truncated
and
packets
are
lost.
Locally
