Tektronix products are covered by U.S. and foreign patents, issued and pending. Information in this publication
supersedes that in all previously published material. Specifications and price change privileges reserved.
TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.
Contacting Tektronix
Tektronix, Inc.
14150 SW Karl Braun Drive
P.O. B o x 5 0 0
Beaverto
USA
For product information, sales, service, and technical support:
n, OR 97077
In North America, call 1-800-833-9200.
Worl dwid e, vis it www.tektronix.com to find contacts in your area.
Release Notes
These release notes provide the following information for version 1.9 of the
MTS400 Series MPEG Test Systems:
Document part numbers
Features in this version
Introdu
ction
Installati
while using the instrument and explanations of how you can minimize or
eliminate the impact on instrument operation
NOTE. To gain access to your version 1.9 MTS400 Series MPEG Test Systems
applications, a software key loaded with version 1.7 permissions (or later) must
be available.
Tektronix has redefined the MPEG analyzer with its ground-breaking MTS400
Series MPEG Test Systems and the MTS400 Series portable analyzer software
option
productivity is provided through many new technical features:
The MT
manufacturing test.
The M
network operations.
The
standalone use on PCs.
on and operational problems or behaviors that you might encounter
s for the MTX100B, RTX100B, and RTX130B instruments. Increased
S430 is well suited for applications in research, development, and
TS415 is equally well suited for applications in broadcasting and
MTS4SA provides the MTS400 Series software applications for
e MTS400P provides the MTS400 Series software applications in a
Th
portable configuration.
he MTX100B, RTX100B, and RTX130B instruments with analysis and
T
generation options are ideal where portability is required.
A wide variety of applications simplify the complex tasks of creating transport
streams for set top box design and manufacturing, as well as triggering and
recording intermittent errors during live broadcasts.
NOTE. Analysis software running on RTX100B/RTX130B instruments can only be
used in deferred time, that is, for analysis of files from disk.
MTS400 Series MPEG Test Systems Release Notes1
Release Notes
The following i
MTS400P, MTX100B, RTX100B, and RTX130B features:
IP and RF Connectivity and Analysis - Acquires transport streams from
the network interface for analysis and recording of streams over IP (internet
protocol), or RF broadcast interfaces (High Performance Network Interface
(MTS415, MTS430, and MTS400P) and RF Interfaces (MTS415 and
MTS430)).
CaptureVu™ -Simplifies the task of triggering, recording, and a nalyzing
events.
High Performance Engine - Measurement throughput up to 400 Mbps.
Intuitive GUI - A simple, yet powerful GUI (graphic user interface) provides
real time analysis and recording, as well as deferred time analysis.
Languages - Microsoft Windows Unicode fonts provide regional language
support.
Hardware/Interfaces (MTS415 and MTS430) - 144 GB of storage, ASI
up to 214 Mbps, fast Intel P4 processor, integrated XGA display, and dual
Ethernet ports for LAN support a nd GigE transport analysis. (For the
equivalent MTS400P, MTX100B, RTX100B, and RTX130B hardware
specifications, refer to the user documentation for those products.)
nformation provides an overview of the MTS400 Series,
Application Packages - Analysis of Audio and Video Elementary Streams,
Packetized Elementary Streams, Transport Streams, and Data Broadcasting
Streams, as well as Multiplexing Audio, Video, and Data Broadcasti
Streams.
International Standards - Support for MPEG-2, ATSC, DVB, and ISDB.
Related User Documentation
The following user documentation supports firmware version 1.9:
MTS400 Series Quick Start User Manual (English), Tektronix part number
071-2607-xx.
MTS400 Series Quick Start User Manual (Japanese), Tektronix part number
071-2608-xx.
MTS400P Quick Start User Manual (English), Tektronix part number
071-2610-xx.
MTS400P Quick Start User Manual (Japanese), Tektronix part number
071-2611-xx.
MTS400 Series Generator Applications User Manual Tektronix part number
077-0204-xx. (Available in PDF format on the Product Documentation
CD-ROM.)
ng
2MTS400 Series MPEG Test Systems Release Notes
Release Notes
MTS400 Series A
077-0205-xx. (Available in PDF format on the Product Documentation
CD-ROM.)
MTS400 Series Carousel Applications User Manual, Tektronix part number
077-0203-xx. (Available in PDF format on the Product Documentation
CD-ROM.)
MTS400 Series Specifications and Performance Verification Technical
Reference, Tektronix part number 077-0207-xx. (Available in PDF format on
the Product Documentation CD-ROM.)
MTS400P Specifications and Performance Verification Technical Reference,
Tektronix p art number 077-0202-xx. (Available in PDF format on the Product
Documentation CD-ROM.)
MTS400 Series Programmer Manual, Tektronix part number 077-0206-xx.
(Available in PDF format on Product Documentation CD-ROM.)
MTS400 Series Declassification Instructions, Tektronix part number
077-0208-xx. (Available in PDF format on the Tektronix Web site.)
MTS400 Series Software Licenses, (Available in PDF format on the
MTS400 Series Product Documentation CD-ROM, Tektronix part number
197-xx.)
063-4
nalyzer Applications User Manual, Tektronix part number
Refer to the MTX100B, RTX100B, and RTX130B Release Notes, Tektronix part
er 077-0195-xx, for information about software issues related to those
numb
instruments.
MTS400 Series MPEG Test Systems Release Notes3
Release Notes
Changes in Sof
Removal of the MDI
(Media Delivery Index)
Functionality
tware Version 1.9
This is a result of the Tektronix decision not to license patented technology
from Ineoquest. Media Delivery Index (MDI) is described in RFC4445 as one
method of mea
of two metrics, Delay Factor (DF) and Loss Rate (LR). Customers wishing to
determine Quality of Service over an Ethernet network are advised to use the
Packet Inter-arrival Time (PIT) graphs and the Continuity Count error (priority
test 1.4) instead.
suring Quality of Service over an Ethernet network. MDI consists
Enhancements - Software Version 1.8
Transport Stream
Compliance Analyzer
PID Filtered Recording: The TSCA can now be set to record only packets
containing selected PIDs.
PTS Processing:
PTS processing for PES Private stream types.
PTS-PCR and DTS-PCR graphs: New graphs have been added for
elementary stream PIDs that plot the difference between PTS/DTS values
and their associated PCRs.
2.5 PTS Test change: This test has been modified to measure the interval
between PTS samples in terms of PTS value. This value interval is also
used to plot the new ‘PTS Value Interval’ graph.
Multiplexer
VBR Delay Factor measurement for RTP streams: A new MDI Delay Factor
measurement has been added that gives better results for variable bit rate
streams; it is only available when the IP flow is transported over RTP
(real-time protocol).
RTP Loss Distribution graph: A new graph is available when analyzing
transport s
IP interface or the internal network interface card) or in file-based analysis
(PCAP).
ATSC:
Support for multiple sections per transport stream packet
Annex A string editing
treams carried over RTP in real-time (using the GbE Video over
EPG displays CC and Ratings information: The TSCA now processes
rating and closed caption information carried in ATSC EITs, and displays
this information in the ATSC EPG view andnexttothevideothumbnails.
A78 Support: Support has been added for the conformance tests defined
in the ATSC A/78 standard (for terrestrial broadcast) and the related cable
standard, SCTE 142.
4MTS400 Series MPEG Test Systems Release Notes
Release Notes
Installation
Using the Cor
Issues (MTS415 and MTS430)
rect Software
Recovery Media
Uninstalling the MTS400
MPEG Player IP Auto
Configur
ation after
Platform Restore
The following issues affect the installation of the MTS400 Series instruments
and/or software on MTS415 and MTS430 platforms only.
Install software version 1.9 only on MTS400 Series instruments with serial
numbers B02xxxx and above.
CAUTION. Installing software version 1.9 on MTS400 Series instruments with
serial num
When uninstalling the MTS400, a dialog box may appear listing a number of
DLLs that
box, and the uninstall will complete successfully.
After restoring an MTS415 or MTS430, running the MpegPlayer for the first
time (w
display. If accepted, the platform will attempt to reboot. The reboot will fail and
you must shutdown and restart the platform manually.
bers below B02xxxxx may cause instrument failures.
cannot be deleted from the registry. Clicking OK will close the dialog
ith the IP interface selected) causes the Auto Configuration dialog box to
New Hardware Wizard
e Found New Hardware Wizard opens after the system has started, you must
If th
complete the wizard before the instrument will operate properly. (See Figure 1.)
orm the following steps to complete the Found New Hardware Wizard:
Perf
1. In the Found New Hardware Wizard window, enable the No, not this time
ion. (See Figure 1.)
opt
2. Click Next to continue.
MTS400 Series MPEG Test Systems Release Notes5
Release Notes
Figure 1: Found New Hardware Wizard page 1
3. On the second page of the wizard, verify that Install the software
automatically (Recommended) is selected. No installation CD or floppy
disk is required. (See Figure 2.)
4. Click Next to continue.
The wizard will search for the required drivers. When the d rivers are found,
the Next button will be enabled.
5. Click Next to proceed.
6MTS400 Series MPEG Test Systems Release Notes
Release Notes
Figure 2:
Figure 3: Wizard searching for drivers
6. When the Completing the Found New Hardware Wizard dialog box, click
Found New Hardware Wizard page 2
Finish.
7. Select Restart from the Start menu to reboot the MTS400 Series system.
MTS400 Series MPEG Test Systems Release Notes7
Release Notes
Figure 4:
Completing the wizard
Restoring the MTS415 and MTS430
The M TS400 Series System restore process is described in t he MTS400 Series
Quick Start Start User Manual.
If, after the system is restored, you are unable to import the SCSI drives, perform
the following steps:
1. Copy the file "SCSIKeyDel.reg" from the restore DVD to C:\.
2. Doub
3. Whe
4. Reboot the instrument.
5. Use the process described in the MTS400 Series Getting Started Manual to
le-click the file name, and when prompted to add information to the
registry, press Yes.
n the process has successfully completed, press OK.
Import the SCSI drives.
8MTS400 Series MPEG Test Systems Release Notes
Release Notes
Installation
Issues (MTX100B, RTX100B, RTX130B, and MTS400P)
MPEG Player Issues
Administrator Rights for
Recording
MPEG Player and TSCA
Application Interaction
For issues affecting the MTX100B, RTX100B, RTX130B, and MTS400P
installation, please refer to the product documentation for those products.
The following issues affect the MTS415, MTS430, and MTS400P. The issues will
also be relevant for the MTX100B, RTX100B, and RTX130B where the MPEG
Player is installed.
TheMPEGPlayerapplicationallowsyoutorecordtoRAM.Youneedlocal
administrator rights on the machine to make a recording.
If the MPEG Player application is playing a stream near its maximum bit rate limit
(214 Mbps simplex or 107 Mbps duplex), and you start the TSCA application,
the instrument may display the message "Mega FIFO empty error" and the
player application may stop. Onc
the stream again.
A workaround is to ensure that the TSCA is started before playing a stream
at high bit rates.
e the TSCA has started, you can start playing
Duplex Support in IP Mode
Maximum IP Playout Bit
Rate
DVB SPI in Port Ignores
the D Valid Setting
Ensure that File Path
is set before Triggered
Recording
The MPEG Player does not support duplex mode (via any interface) when in
IP Playout mode.
The maximum playout bit rate supported by the player is determined by the NIC
interface setting and Windows Network Component settings.
To reach optimal bit rates, the NIC configurations should be optimized and the
Windows ICS service should be turned off.
When recording using the SPI port marked "DVB SPI In", the setting in the
"Ignore Dvalid" check box under the Record > Target dialog box is ignored, and
all data will be recorded with Dvalid active and inactive.
The port marked "DVB SPI Out" is capable of both input and output, and this
setting is applied correctly. However, recordings made using this port will not
be timestamped.
Before performing a triggered recording, ensure that the correct path is set using
the File > Save dialog box. If the path is not set, a File Not Found error will be
generated when the recording starts.
MTS400 Series MPEG Test Systems Release Notes9
Release Notes
Incorrect Ouput Position
Indicator
Software Update Mode
Behavior
Rapid scr
oll bar movement
may stop Player
responding
Burst of IP packets at start
of Playout
If the Fixed ES R
position indicator may not show the correct position.
When the MPEG Player plays out in the Software Update mode, you may observe
the followin
PCR inaccuracy errors might occur at the beginning of every loop.
If PCR errors preexist in a transport stream file, they will continue to exist
across all loops.
Preprocessing the stream with the Make Seamless utility (before playout) prevents
these looping errors.
When the scroll bar is moved rapidly in the Record mode, the MPEG Player may
stop responding. Clicking the Hierarchical window returns the MPEG Player to
the normal state.
When pla
few packets. This may result in the burst mode delays not occurring at correct
intervals.
ying out in IP mode, a delay (above 250 ms) may occur once in the first
ate check box is selected in the Clock dialog box, the output
g:
Simultaneous TSCA and
MPEG Player Triggered
Recording
Data R
ate Auto Converter
for ISDB-Tsb Streams
Player Does Not Use Time
in TDT/TOT Dialog Box
Hierarchical Window Does
Not Always Show Stream
tents
Con
TSCA and the MPEG Player are simultaneously configured to record for
If the
individual triggers events, both the applications are triggered when the first trigger
event occurs.
Setting the Data Rate Auto Converter (Auto Play) value does not update the bit
rate of ISDB-Tsb streams.
During playout, the MPEG Player does not use the time value set in the TDT/TOT
dialog box.
While in record mode, the MPEG Player is unable to display the contents of
the stream onto the hierarchical window for some transport stream fi les (for
example,Test40.mpg) at high bit rates although it is able to receive the transport
stream file.
10MTS400 Series MPEG Test Systems Release Notes
Release Notes
Transport Str
eam Compliance Analyzer Issues
Administrator Righ ts for IP
Analysis
Lost Packe
ts During
Recording on IP Analysis
on Low Specification PCs
Processing may Become
Strained with Script
Validation enabled in Real
Time Mode
RTP Analysis - Transport
Stream Availability Error
Reporte
d for 204 byte
Packet Streams
The following issues affect the MTS415, MTS430, MTS4SA, and MTS400P. The
issues will also be relevant for the MTX100B, RTX100B, and RTX130B where
the Transpor
To perform real-time IP analysis using an NIC (network interface card), you
must have local administrator rights.
On some low-specification PCs ( with old network cards and slower hardware), if
you record a stream that is being analyzed over IP using an NIC, packets might be
lost. This is because of the hardware dropping Ethernet frames.
If you ena
strained. If this occurs, and script validation is required, disable the feature, make
a recording in real time, and then per form a deferred analysis on the recording
with the feature enabled.
When analyzing a 204 byte packet stream over RTP, the transport stream
Availability test will activate at the start of the stream.
t Stream Compliance Analyzer is installed.
ble Script Validation for Real Time Analysis, the TSCA might become
Analyzing RTP Streams
using UDP causes
the TSCA to become
Overwhelmed
Streams Transmitted over
UDP may be recognized as
RTP
IP Packet Interarrival
Timing
When you select an IP session to analyze from the "Browse for UDP flow" dialog
box, the TSCA attempts to identify whether it is RTP or UDP, and automatically
updates the " Use RTP" check box in the Real-time Analysis Open Transport
Stream dialog box. If you manually clear the "Use RTP" and analyze a known
tream, this can cause the TSCA to become overwhelmed and data to be lost.
RTP s
It has been seen very infrequently that UDP sessions are detected as RTP in the
"Browse for UDP flow" dialog box. This is due to specificbytepatternsappearing
he transport stream. If this occurs, clear the "Use RTP" check box manually.
in t
The TSCA uses WinPcap for IP input using an NIC. The timing of WinPcap is
affected by the type of processor, hyper-threading and SMP. See the WinPcap
change log (http://www.winpcap.org/misc/changelog.htm) for more details.
IP Packet timing measurements using an NIC are based on timestamps averaged
over a 40 ms period. You can define an integration period for the graphical d isplay
of average Packet Inter-Arrival Time. The default integration period is 1 second.
MTS400 Series MPEG Test Systems Release Notes11
Release Notes
Ethernet Packet
Timestamp Smoothing
RTP Droppe
d Packet Test
H.264 Thumbnails with
Recovery Points
Concur
rent Analysis
Behaviour
Under certain c
timestamping of Ethernet packets can be delayed within the network interface
kernel mode driver when using an NIC.
To overcome this issue, an Ethernet packet arrival smoothing algorithm has been
implemented in this release to ensure that erroneous jitter does not affect the
transport stream timing measurements. This algorithm results in the smoothing of
the PCR Arrival Interval measurement and the associated graphs when using the
IP interface through an NIC.
The RTP Dropped Packet tests checks the RTP sequence number of packets
leaving the Jitter buffer a fter they have been reordered. The test will fail if the
difference in the RTP sequence number between two subsequent packets is greater
than one
The TSCA thumbnail decoder does not support H.264 Recovery Points.
It is possible to have multiple instances of the TSCA running at the same time.
However, the following behavior should be noted:
.
onditions of heavy network traffic, it has been noted that
nectiontoVLAN
Con
Sessions using a NIC
Triggers are saved on restarting analysis. The effect of setting a trigger in an
instance and restarting analysis will be to cause the trigger to be inherited in
other instances when analysis is restarted in those instances.
When a parameter is modified in one instance, it will be inherited in other
instances when analysis is restarted.
The VLAN tag will not appear in the TSCA analysis because, by default, Intel
adapters strip the VLAN tag b efore passing IP up the stack.
If you n eed to analyze VLAN sessions, you should update to the latest Intel
driver for the NIC, and add a DWORD a registry entry "MonitorModeEnabled"
to a value of 1 within:
- where xx is the instance of the network adapter.
12MTS400 Series MPEG Test Systems Release Notes
Release Notes
Transport Str
Errors Repor
Stops and Starts Quickly
eam Compliance Analyzer IPTV Option Issues
The following issue affects the MTS415, MTS430, and MTS400P where the
Transport Stream Compliance Analyzer IPTV Option is installed.
ted if Session
If a selected session stops and starts quickly, the Transport Stream Analysis
may report transport stream Availability and Continuity Errors, but no errors
will appear in the TrafficTable.
Transport Stream Compliance Analyzer GbE Option Issues
The following issues affect the MTS415 and MTS430, where the GbE Option is
d.
nalysis. This will result in dropped packet and continuity count errors.
Packets with IP Checksum
Errors are Discarded
Interface Card Startup
Time
installe
Packets with IP checksum errors will be discarded by the interface card. The user
will be notified that the checksum errors have occurred, but they will not be passed
on for a
The Interface Card takes around 90 seconds to boot up after the user logs in. No
sessions will be visible during this time.
ah Connection
Cheet
Appears in Network
Connections
Maximum Aggregate Bit
Rates across all Four Ports
Restricted to 3.6 Gbps
ser Active on all Optical
La
SFP Ports during Analysis
A connection called "Cheetah Connection" will appear in the Network
Connections window. Users must not change any of the settings for this
connection, as any modifications will prevent the interface card from operating.
that the IP address specified within the Internet Protocol (TCP/IP) settings
Note
is not the IP address of the ports on the card. This is set through the TSCA user
interface on a port by port basis.
though a user may be analyzing a session through a single port, all four ports
Al
are still active. The maximum total bit rate that the card can handle through all
ports is 3.6 Gbps.
It should be noted that although only one port can be used for analysis, all ports
are active on the card. Therefore, if an optical SFP is plugged into one of the ports
not being used for analysis, the laser will be active.
MTS400 Series MPEG Test Systems Release Notes13
Release Notes
Only Select Active Mode
on Ports with Live
Connections
ES Analyzer Issues
Only Partially Decodes
4:2:2 Pro
Presentation Order is
file@HighLevel
File
Incorrect
Active mode, us
selected on ports with live connections. If active mode is selected for a port
without a live connection, the card will attempt to issue live messages, and will
block until they can be delivered. This will also prevent ARP and IGMP messages
being transmitted on other ports. If you suspect that you have selected a port in
active mode on a connection that is not live, restarting the unit will ensure that
ARP and IGMP
The follow
RTX100B and RTX130B where the ES Analyzer is installed.
4:2:2 Profile@HighLevel files are only partially supported by the ES Analyzer. It
fails to
Sometimes the Presentation Order chart does not present field encoded material in
the correct order.
correctly recognize the 0x82 Profile/Level type.
ed when ARP a nd IGMP support is required, should only be
messages can be transmitted on the live connections.
ing issues affect the MTS415, MTS430, MTS400P, MTX100B,
Buffer Analyzer Issues
The following issues affect the MTS415, MTS430, MTS4SA, and MTS400P. The
issues will also be relevant for the MTX100B, RTX100B, and RTX130B where
the Buffer Analyzer is installed.
When private data is processed and the Show All Graphs button is pressed,
only the event log pops up. However, The TB and MB graphs can be brought
sing the appropriate buttons.
up u
There is no support for streams which have multiple access units per PES
ket.
pac
When System PIDs are analyzed, the MB graph shows the variations and
tails. However, the trace window does not show any details of the analysis.
de
14MTS400 Series MPEG Test Systems Release Notes
Multiplexer Issues
Release Notes
The following issues affect the MTS415, MTS430, MTS4SA, and MTS400P. The
issues will also be relevant for the MTX100B, RTX100B, and RTX130B where
the Multiplexer is installed.
Elementary stream within other containers, such as *.MP4, Fluxmux and
others, are not directly supported.
Incomplete access units (for the last access unit), will be dropped during
multiplexing.
On looping small files, the PAT and PMT table stop time resets to the start
time. The repetition interval then becomes zero because there is only one
occurrence in each of these table sections.
The multiplexer does not consider the start time of the stream when adjusting
the PTS/DTS values of the elementary stream. A workaround for this is to
enter a D
Altering some stream properties (like duration) does not affect other stream
proper
transport stream durations automatically. However, the stream properties
can be set manually.
TS offset for the PID equal to its lag against the PCR PID.
ties. For Example, other PIDs do not automatically adjust to new
The Multiplexer does not support H.264 adaptive field/frame encoding (AFF).
Erroneous DTS and PTS values are likely to be generated for video streams
that incorporate AFF.
MTS400 Series MPEG Test Systems Release Notes15
Release Notes
Support for Generating
Partial Reception Streams
Support for gen
While multiplexing H.264 elementary streams, the Multiplexer puts one
access unit per PES packet. Remultiplexing some H.264 PES, which has more
than one access unit in one PES packet, will result in a slightly increased
bit rate.
The Multiplexer currently expects the PCR to be carried in one of the audio
or video PIDs. However, if you need to generate a separate PCR only PID,
perform the following steps:
a. While creat
the PCR tab.
b. Uncheck the Carry PCR and enter the PCR PID number.
c. Check that you have the right PCR PID on all audio and video streams.
d. Finish the proc ess of adding the streams and tables.
e. You will get an PCR error message here if you are working with the
wizard (no PCR).
f.On the File Examine TS menu, open the reference stream from which you
want to use the PCR from.
g. Drag the PCR PID from the examine TS to the PID tab of the stream
being cr
erating Partial Reception Streams has some limitations:
ing the new TS, in the add program stream dialogue, go to
eated.
h. Check the PID number and click ok.
Select an appropriate stream type when providing an input file to the
Multiplexer. For example, providing a transport stream as input and selecting
PES or ES as the stream type may result in a crash.
When a non-SEI H.264 PES is provided as input, the Multiplexer displays
the detect bit rate dialog box. However, the Detect Bitrate button, Scan
settings button, and frame rate combo box are all grayed out. You will need to
de a bit rate manually.
provi
Support for H.264 in the Make Seamless feature of the Multiplexer and
Seamless Wizard is not available yet.
In ISDB-T (One Segment), ISDB-TB (One Segment) interpretations, NIT/
TOT/ TDT setup screens are not available. However, you can a dd these tables
through the table and section views.
The Multiplexer allows you to create multiple sections of a TDT/ TOT table,
but when the muxed file is opened in Mux again, these multiple sections are
t seen. However, these are present in the stream, evident when the stream
no
is analyzed with the TSCA.
When two TDT sections are added to a stream and both are given two different
start and stop times, the generated stream will have identical sections.
16MTS400 Series MPEG Test Systems Release Notes
Release Notes
MTS400P Issue
s
On the first use of the Pseudo real-time playout, the path for the MPEG Player
application needs to be changed to: